trap problem

[Domenico Viggiani]

We have installed hp agent on some servers.
On just one server DL385 with RH4 64 bit we can't receive trap on SIM.
server manually discovery is ok. trap is sent, but we don't receive mail, and trap is not displayed on SIM. We have test other server DL385 with RH4 64 bit and all is ok.
The server is in different subnet and domain,
and it have 2 network adapter with 2 internet address.
Any ideas?
thanks in advance

[Frank Köhler]

Hi Domenico Viggiani,
be sure that your "DL385 with RH4 64 bit" reaches the appropriate smtp-server (ping by name and ping by IP-address). Ensure that the following services run perfectly: TCPIP, SNMP (with right community), SNMP-trap.

F.K.

[Domenico Viggiani]

No, none of these problems.
Only difference respect to working servers is that this server is multihomed.

[Carlsberg]

Hey ,
Two basic things I'd check since it's multihomed
1. Name resolution from the managed server,
Make sure it resolves the HP SIM server
2. Routing and firewall.
Make sure that you routing your snmp traffic via the correct interface.

[Domenico Viggiani]

By a sniffer, we was able to see the trap leaving the managed server and arriving to the SIM workstation. But no event was generated.

[Maurice Skubski_1]

you can enabel in SIM to see unregistered events. if you do this can you see the event? if yes there is a MIB missing. If not there is a problem with the SNMP Stack. regards maurice

[Domenico Viggiani]

Event is not generated even if I enable "unregistered events".
Perpahs there is a problem with SNMP stack: system is correctly discovered but after a few minutes I get "Data collection timeout".

[Rob Buxton]

Does HPSIM have both subnets in the discovery range.
You might want to add one of the IP Addresses to the discovery exclusion range.
Just wondering if the trap is arriving from one IP but HPSIM has discovered the other or at least has resolved the name for one but not the other and is getting confused.

[Domenico Viggiani]

Rob gives an useful suggestion: peraphs source address of the trap is the other NIC of managed server (that has not DNS name, it is a card dedicated to iSCSI).
I will check asap.