Comware Based
1753325 Members
5451 Online
108792 Solutions
New Discussion юеВ

Nagios Monitoring CPU on HP5945

 
SOLVED
Go to solution
declan2777
Frequent Advisor

Nagios Monitoring CPU on HP5945

Hi all,

I am looking for advice,; we currently have Nagios set up to monitor cisco devices and all is good. I am setting Nagios to Monitor HP5945 and it is logging to nagios etc however I cannot get CPU information etc. Is there anything specific other than snmp to be configured on the switch? Also, is there any particular config needs to be added to Nagios etc . All help much appreciated

 

Regrds

Dec

5 REPLIES 5
declan2777
Frequent Advisor

Re: Nagios Monitoring CPU on HP5945

Also, the SNMP walk is timing out

Ivan_B
HPE Pro

Re: Nagios Monitoring CPU on HP5945

Hello @declan2777 !

It will be extremely useful, if you provide more information about configuraiton of your switch. May be "display current-config" output (with all sensitive information deleted or obfuscated) will be a good starting point. Also, you can check if snmp-agent is enabled at all - "display snmp statistics". Another test - ping your Nagios server from the 5945 or vice versa and see if they can reach each other on Layer 3.

In general you need to compile appropriate MIBs and import them to Nagios in order to use SNMP protocol with Comware devices. https://h10145.www1.hpe.com/downloads/SoftwareReleases.aspx?ProductNumber=JQ075AComware MIBs_V11-DataCenter But even without MIBs very basic queries like snmp-get .1.3.6.1.2.1.1.1.0 OID should work.

 

 

I am an HPE employee

Accept or Kudo

declan2777
Frequent Advisor

Re: Nagios Monitoring CPU on HP5945

Hi there,

Thanks for getting back to me, I have attached what you asked for below. 

clock timezone EU add 01:00:00
clock protocol ntp
#
irf mac-address persistent timer
irf auto-update enable
undo irf link-delay
irf member 1 priority 32
irf member 2 priority 28
irf member 1 description
irf member 2 description
#
parity-error unrecoverable log enable
#
lldp global enable
#
system-working-mode standard
password-recovery enable

#
scheduler logfile size 16
#
line class aux
user-role network-admin
#
line class vty
user-role network-admin
#

#
line aux 1
user-role network-admin
#
line vty 0 4
authentication-mode scheme
user-role network-admin
user-role network-operator
protocol inbound ssh
#
line vty 5 63
authentication-mode scheme
user-role network-admin
protocol inbound ssh

#
info-center loghost 10.60.82.200
#
snmp-agent
snmp-agent local-engineid 800063A2804CAEA3AF41F400000001
snmp-agent community read cipher $c$3$hZ5BPqiTpugbFzqo/wIrYMbbfm1U7hngVQTxPIY=
snmp-agent community write cipher $c$3$MH4OoBlZFfSSB+/iNH1w5q7y2TCTL+ithR0prg0=
snmp-agent sys-info version all
snmp-agent target-host trap address udp-domain 172.21.0.1 params securityname v2c
snmp-agent trap enable arp
snmp-agent trap enable radius
snmp-agent trap enable stp
snmp-agent trap enable syslog
#
ssh server enable
sftp server enable
#
ntp-service enable
ntp-service unicast-server 10.60.82.6 priority
ntp-service unicast-server 10.60.82.7
#

radius scheme system
user-name-format without-domain
#
domain ecs
#
domain system
#
domain tacacs
#
domain default enable system
#

 

dis snmp-agent statistics
2763809 messages delivered to the SNMP entity.
0 messages were for an unsupported version.
12 messages used an unknown SNMP community name.
0 messages represented an illegal operation for the community supplied.
0 ASN.1 or BER errors in the process of decoding.
2808135 messages passed from the SNMP entity.
0 SNMP PDUs had badValue error-status.
0 SNMP PDUs had genErr error-status.
156 SNMP PDUs had noSuchName error-status.
0 SNMP PDUs had tooBig error-status (Maximum packet size 1500).
22714440 MIB objects retrieved successfully.
1 MIB objects altered successfully.
150582 GetRequest-PDU accepted and processed.
1785354 GetNextRequest-PDU accepted and processed.
827860 GetBulkRequest-PDU accepted and processed.
2763797 GetResponse-PDU accepted and processed.
1 SetRequest-PDU accepted and processed.
44338 Trap PDUs accepted and processed.
0 alternate Response Class PDUs dropped silently.
0 forwarded Confirmed Class PDUs dropped silently.

 

 

 

Ivan_B
HPE Pro
Solution

Re: Nagios Monitoring CPU on HP5945

snmp-agent seems to be working on the switch. What about simple check if Nagios server can communicate with the switch on Layer 3 and by SNMP - try following commands from the host running Nagios (assuming it's a LInux host with net-snmp package installed):

ping <ip_address_of_the_switch>

snmpget -v 2c -c <read_community_string> <ip_address_of_the_switch> 1.3.6.1.2.1.1.1.0

 

I am an HPE employee

Accept or Kudo

declan2777
Frequent Advisor

Re: Nagios Monitoring CPU on HP5945

Hi Ivan,

 

Many thanks found out there was an issue with Nagios..Thanks for all your help