No events generated

[Ingo Dettmar]

We have a problem that after migration from Insight Manager 7 we get no events anymore apart from system reachable/unreachable. If I plug out a redundant power supply for example, the system status changes accordingly, but there is no event generated.

Any hints?

[John Jorgensen]

I have allmost the same problem, after migration from CIM 7-SP2.
Traps from other servers in the same IP subnet are working fine, but traps from servers through VPN tunnel do not work.
With the program SNMP Trap Watcher, i can monitor all traps. Tried restarting, checking community string and so on. Stil the same. Discover and browsing agents and system management in alle servers works grat.
Any idea?

[jim goodman]

Make sure the SNMP settings for the community strings are set in SIM, Options-->Global Settings-->Protocol Settings and in the SNMP Properties on the respective managed servers try setting the Trap destination to the CMS IP address and double check the community strings are R-W with the appropriate community name.

Also on the Device System page (click on the name) Next Protocols: make sure you see SNMP listed as one of the them.

- Jim

[Ingo Dettmar]

I have found the problem, the trap configuration was set to the hostname and the hostname wasn't reachable by DNS...

Thanks for the suggestions anyway.

[John Jorgensen]

Happy Ingo - My problem not solved.

Checked and double checked every SNMP setting. About 100 servers are listed in our system. As mentioned, I can browse them all, discover new systems, ping to servers from CMS and from servers to CMS, but no events from systems in other subnets are generated. Local systems works fine.
Tried changing trap destination from hostname to IP adress. All serves used in HP IM 7-SP2 without problems.

[Ivan KOVAC]

hello

Check up Event Filter Settings, maybe is there the IP address ranges of systems whose
traps you can receive or ignore.

i.

[John Jorgensen]

Already checked. Gone through all settings with colleague today, and all seams to be the right settings.

John,

[Ivan KOVAC]

Hello

Maybe is a SNMP Agent port (161) and Trap listener port (162) disabled on those subnets.

Check if you have enabled Send test SNMP trap under SNMP propertis, tab security. And if traps reach trap destination your HPSIM server. In All event list must be a informational event.

I.

[John Jorgensen]

Thanks for all input. It seems to be a problem in the way HP SIM 4.1 handles the traps comming through a VPN tunnel. We are currently discussing the problem with HP. I will post the answer here when the problem is solved. Maybe a patch from HP will help.

Thanks

John,

[Rob Buxton]

I cannot see how HPSIM would handle traps any differently depending on where they came from.

There's a Trap Send option from the HP Agents GUI. That should generate a trap that should get picked up by HPSIM as generic trap.

You should be able to detect if they're making it through the VPN.
Do you have any address translations going on? perhaps HPSIM cannot determine where the trap has come from.

[Ken W]

I have exactly the same problem. It just started happening over this past weekend. I have been working with IM7/SIM4 for sometime (without problems) and have never seen this. Does anyone have any ideas as to what could cause this?

Thanks!

[jim goodman]

Have your network folks made any changes like is SNMP traffic being filtered or the SNMP port closed, on the VPN router?

- Jim

[jim goodman]

I forgot to add that an access-list on a switch can also block ports.

- Jim

[Joel Rubenstein]

Your problem may be related to where SIM looks in an incoming trap for the IP address.

HPSIM 4.1 is defaulted to use the address from the trap PDU.

This setting may be changed by modifying the globalsettings.props file.

To make this change -

1) Stop HPSIM
2) Modify the following line in globalsettings.props:
AllowAltIpForTrap=enabled
to
AllowAltIpForTrap=disabled
3) Restart HPSIM

After the restart, HPSIM will use the address from the IP header.

[Ken W]

I made this modification to the globalsettings.props file without success. BTW: I have had SIM4 up and running successfully since about 6/1/2004.
There were no changes to the network over this past weekend. It just stopped working properly for no apparent reason. There's no errors, just no events.
Thanks.

[jim goodman]

Well at this point I would say you need to open a case with support and see what they have to say then have them escalate the issue.

There is no reason it should just up a quit, if nothing changed. And if it did I would sure like to know why and I bet the developers would as well.

- Jim

[John Jorgensen]

Rob, you are right, it has nothing to do with the VPN tunnel itself, but with NAT in the VPN tunnel.

HP advised me to change the settings mentioned by joel.

HP wrote:

HPSIM 4.1 is defaulted to use the address from the trap PDU.

This setting may be changed by modifying the globalsettings.props file.

To make this change -

1) Stop HPSIM
2) Modify the following line in globalsettings.props:
AllowAltIpForTrap=enabled
to
AllowAltIpForTrap=disabled
3) Restart HPSIM

And now every thing works fine. Thanks everybody for inputs.

Special thanks to Gene Raymer, HP Services

John,

[Brian Charlton]

I have been tearing my hair out over this, works a treat you are truly a god