topic Re: snmp trap is not received. in Server Management - Systems Insight Manager

snmp trap is not received.

mikewate — Wed, 31 Jan 2007 23:16:40 GMT

There is a standalone network of Windows2003 and RHEL4.
I installed SIM5.1 on Windows2003 and PSP7.7 was installed in RHEL4.
Each machine writes the computer name in the hosts file, and solves the name.
Each machine connects mutual trust.

The entry was added to /etc/snmp/snmpd.conf of RHEL4.
rwcommunity [community name] [SIM IPaddress]
rwcommunity [communityname] 127.0.0.1　
trapsink [SIM IPaddress]

Disc Threshold was set for the test.
However, SIMServer doesn't receive the trap.

Besides, please teach if there is a necessary setting.

Re: snmp trap is not received.

Rob Buxton — Thu, 01 Feb 2007 14:52:57 GMT

Not totally familiar with RH, but in VMWare the trapsink line includes the community name after the SIM IP Address.

If you can connect to the HP Agent, under Settings -> SNMP WebAgent -> SNMP Configuration there's a Trap send button. That should generate a trap that can be used to test.

The detail in the VMWare snmp.conf is;

rwcommunity [rwname] 127.0.0.1
rocommunity [roname] 127.0.0.1
rwcommunity [rwname] [SIM Server name]
rocommunity [roname] [SIM Server name]
trapcommunity [roname]
trapsink [SIM server anme] [roname]

Re: snmp trap is not received.

David Claypool — Fri, 02 Feb 2007 15:13:02 GMT

Before accusing HP SIM of not receiving the trap, you need to check the originating host to make sure it actually sent a trap. Is there an event in /var/log/messages that corresponds to the threshold?

Secondly, beware that Windows Server 2003 installs SNMP by default to only respond to localhost. If that's the case, SNMP would throw away a trap sent to it.

Re: snmp trap is not received.

mikewate — Tue, 06 Feb 2007 04:03:08 GMT

Thank you for everybody.
I'm sorry that the reply is delayed.

"Test trap" was transmitted from "SNMP configure" of system management homepage.
ï¼ "Net-snmp util" was installed. ï¼
"Test trap" was received by SIM.

The disk threshold can be observed though the machine for the watch was tried as
Windows2003.

I execute this command with RHEL4.
/etc/init.d/hpasm reconfigure
The trap of the disk threshold was sent to SIM immediately after the re-setting.
However, even if the disk threshold exceeds it afterwards, the trap is never sent.

The disk threshold cannot be observed at any time though it seems to be able to receive
the trap.

/var/log/messages
-------------------------
Feb 6 17:42:04 rhel snmpd[14202]: Received TERM or STOP signal... shutting down... Feb 6 17:42:04 rhel snmpd: snmpd shutdown succeeded
Feb 6 17:42:04 rhel snmpd: snmpd startup succeeded Feb 6 17:42:04 rhel snmpd[19255]: cmaX: listening for subagents on port 25375
Feb 6 17:42:04 rhel snmpd[19255]: cmaX: sent ColdStarts on ports 25376 to 25393 Feb 6 17:42:04 rhel snmpd[19255]: NET-SNMP version 5.1.2
Feb 6 17:42:08 rhel smhstart: hpsmhd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
Feb 6 17:42:08 rhel hpsmhd: smhstart startup succeeded
Feb 6 17:42:10 rhel hpasmd[19572]: ProLiant System Health Monitor loading
Feb 6 17:42:11 rhel snmpd[19255]: cmaX: subMIB 1 will be sent on port 25376 to hp Advanced Server Management_Peer
ï½ ï½ ï½
------------------------------

/var/log/snmpd.log
-------------------------
cmaX: listening for subagents on port 25375
cmaX: sent ColdStarts on ports 25376 to 25393
NET-SNMP version 5.1.2
cmaX: subMIB 1 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 2 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 3 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 5 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 6 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 8 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 9 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 10 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 11 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 14 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 15 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 16 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 21 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 22 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 23 will be sent on port 25376 to hp Advanced Server Management_Peer
cmaX: subMIB 18 will be sent on port 25393 to cpqnicd
Received SNMP packet(s) from 127.0.0.1
Received SNMP packet(s) from [SIM IP address]
-------------------------

Re: snmp trap is not received.

Rob Buxton — Wed, 07 Feb 2007 02:07:00 GMT

The trap is only sent at the point the threshold is crossed. The disk space needs to go below the threshold and then back over for a resend.

Restarting the agents while a threshold has been exceeded will also generate a trap.

Re: snmp trap is not received.

mikewate — Sat, 17 Feb 2007 04:19:53 GMT

Thank you!

solved it.
Reset threshold was mistaken and set it.