Templates for HP Servers

[cyrill]

nobody know ?

[fmangeant]

Can you check that HP Insight agents are running ?

[cyrill]

hum ! I don't now if this agent running.

Can you give me the name of the service ? If I check my services, there are 4 HP services running.

- HP Proliant Remote Monitor Service
- HP Proliant System shutdown Service
- HP Smart Array SAS/Sata Event Notification Service
- HP System Management HomePage

[fmangeant]

Sorry, I don't use HP servers...

[cyrill]

no problem. thanks for your help.

[cyrill]

This graph template works well with old server HP (DL380 G4) but no with a new DL380 G5 !!!

The owner of this graph template could be update his template ???

[ugob]

I'm not the author but I tried, but I can't find where the OID are in the config.

[Cova]

This graph template works well with old server HP (DL380 G4) but no with a new DL380 G5 !!!

The owner of this graph template could be update his template ???

Sorry for being so late - I haven't really had time to play with Cacti lately. I'm not sure what your problem is - I've got multiple 380G5's here and they all work fine with the templates, I never had to change anything.

I can say though that if snmpwalk is not giving you any data, then the problem is definitely not with the templates. I've had a lot of issues with the HP SNMP agents on the servers - sometimes they just stop giving me data, sometimes the snmp service locks up and needs to be restarted, etc. and I haven't gotten any good resolution for it yet. You can try updating your insight agents, but I can't promise it'll help (I've had issues with every release so far). Once you can get the snmp data through snmpwalk, then if the templates don't deal with the data correctly I'll take another look and make sure theres no problems with them.

[ugob]

What version of PHP are you using? 5?

[ugob]

<deleted>

[ugob]

Cova, are you running Windows on the servers? On my linux servers, I can get all the templates ok, except the logical drives, but only on RHEL5. On RHEL3, I can get the data fine. Any idea why?

Debug mode on RHEL3:

Code: Select all

+ Running data query [17].
+ Found type = '3' [snmp query].
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/hpDrvArray-LogicalDrive.xml'
+ XML file parsed ok.
+ Executing SNMP walk for list of indexes @ '.1.3.6.1.4.1.232.3.2.8.1.1.1'
+ Located input field 'hpIDALogicalDrvIndex' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.232.3.2.8.1.1.1'
+ Found item [hpIDALogicalDrvIndex='0'] index: 0.1.1 [from value]
+ Located input field 'hpIDALogicalDrvInstance' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.232.3.2.8.1.1.2'
+ Found item [hpIDALogicalDrvInstance='1'] index: 0.1.1 [from value]
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/hpDrvArray-LogicalDrive.xml'
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/hpDrvArray-LogicalDrive.xml'
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/hpDrvArray-LogicalDrive.xml'
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/hpDrvArray-LogicalDrive.xml'

On RHEL5

Code: Select all

+ Running data query [17].
+ Found type = '3' [snmp query].
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/hpDrvArray-LogicalDrive.xml'
+ XML file parsed ok.
+ Executing SNMP walk for list of indexes @ '.1.3.6.1.4.1.232.3.2.8.1.1.1'
+ Located input field 'hpIDALogicalDrvIndex' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.232.3.2.8.1.1.1'
+ Found item [hpIDALogicalDrvIndex='1'] index: 1.1.1 [from value]
+ Found item [hpIDALogicalDrvIndex='1'] index: 1.2.1 [from value]
+ Found item [hpIDALogicalDrvIndex='1'] index: 1.3.1 [from value]
+ Found item [hpIDALogicalDrvIndex='1'] index: 1.4.1 [from value]
+ Found item [hpIDALogicalDrvIndex='4'] index: 4.1.1 [from value]
+ Found item [hpIDALogicalDrvIndex='4'] index: 4.2.1 [from value]
+ Found item [hpIDALogicalDrvIndex='4'] index: 4.3.1 [from value]
+ Found item [hpIDALogicalDrvIndex='4'] index: 4.4.1 [from value]
+ Found item [hpIDALogicalDrvIndex='4'] index: 4.5.1 [from value]
+ Found item [hpIDALogicalDrvIndex='4'] index: 4.6.1 [from value]
+ Located input field 'hpIDALogicalDrvInstance' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.232.3.2.8.1.1.2'
+ Found item [hpIDALogicalDrvInstance='1'] index: 1.1.1 [from value]
+ Found item [hpIDALogicalDrvInstance='2'] index: 1.2.1 [from value]
+ Found item [hpIDALogicalDrvInstance='3'] index: 1.3.1 [from value]
+ Found item [hpIDALogicalDrvInstance='4'] index: 1.4.1 [from value]
+ Found item [hpIDALogicalDrvInstance='1'] index: 4.1.1 [from value]
+ Found item [hpIDALogicalDrvInstance='2'] index: 4.2.1 [from value]
+ Found item [hpIDALogicalDrvInstance='3'] index: 4.3.1 [from value]
+ Found item [hpIDALogicalDrvInstance='4'] index: 4.4.1 [from value]
+ Found item [hpIDALogicalDrvInstance='5'] index: 4.5.1 [from value]
+ Found item [hpIDALogicalDrvInstance='6'] index: 4.6.1 [from value]
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/hpDrvArray-LogicalDrive.xml'
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/hpDrvArray-LogicalDrive.xml'
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/hpDrvArray-LogicalDrive.xml'

[ugob]

Oh, I forgot to say. There is another important difference between the 'working' and the 'not working' systems. The working systems are RHEL3, x86, while the not-working ones are RHEL5, 64-bit.

I'll try to see with HP if they have a list of MIB.

[Khan]

Is anyone using this template (or any other template) to monitor SAN volumes attached to their DL380's? It's great to see all of the local disks being graphed however, I need to be able to see the I/O of my SAN disks, too. Thanks.

[ugob]

What is the SAN you're using? You may want to check with the manufacturer or your SAN to see if they have OID that you could query to get the same result.

[Khan]

The SAN is a EMC Clariion MX-80. I guess I should clarify that what I am looking for is the I/O via the HBA for the LUN assigned to the Windows server and not necessarily the I/O of the drives on the SAN itself. Does that make sense?