SNMP Auto-discovery

[Ulrik Ivers]

We are running IM7 and have turned off all automatic discovery except "SNMP Trap Auto-discovery".

Sometimes we are having problems to get a sever to be discovered. All SNMP settings are correct and I've tried to
A. Restart SNMP service (and all agents)
B. Send Test trap from control panel applet

I have NOT tried to reboot server, I'm hoping to avoid that.

Any ideas to how I can generate a trap (other than the test trap) to see if that get the server to appear?

How can I see if the test trap reaches the IM server, I can't see it when I run the "Informational Events" query.

[Andrei Khairetdinov]

To see if IM7 server got the test trap go to the device link in IM7 on the bottom-left there is a link "All Events associated with this Device". Follow the link and will see if there was any test trap recieved by IM7. Ohter test: on the same device page there is a link SNMP explorer - try to read device any variable, thus check the SNMP communication in opposite direction.

[Ulrik Ivers]

Thank you for the response.

However - your answer assumes that the device is present in IM. My problem is to get it there using SNMP Trap Auto-discovery.

[Jadrice Toussaint]

Hi -

Make sure that SNMP is enabled in IM7. Go to Settings -> Server -> Protocols. Under the SNMP settings category, make sure that the Enable SNMP checkbox is selected and the Default Control Community String matches what the clients read/write security settings <-- this is located by double clicking on the SNMP service on the client side and by clicking on the security tab.


Let me know if that helps.

[Ulrik Ivers]

SNMP is enabled, configured and working.

We have run this IM7 server set up with only SNMP Trap Auto-discovery for some time now and mostly it works fine.

I've pinpointed the problems to when:

A. The server has been installed without configuring SNMP, been started up and THEN configuring SNMP correctly. Restarting SNMP servive (and agents) doesn't help.

or

B. The server is installed and configured correctly but at boot time the network connection to the IM server is unavailable.

I'm hoping to not have to reboot servers or adding them manually to IM - we're running a a 24/7 shop.

[Jadrice Toussaint]

Is the server that you are trying to auto discover included in the ip range for the auto discovery?

[Ulrik Ivers]

If you mean "Ping Inclusion Ranges" on Settings->Automatic Discovery page, the answer is no. But this range is only used for ping-discoveries, yes? Is there a similar IP range specification somewhre else that is used for SNMP Trap auto-discovery?

[David Claypool]

If the trap is received by IM7, it should appear as an event even if the device isn't subsequently discovered and added to the database. If the trap is not being received, keep in mind that SNMP is not guaranteed delivery. That's why status polling is so important in addition to SNMP trap events.

Once that trap is received, all IM7 knows is the device name and IP address. To add the device to the database the "Initial Device Discovery" task is called. This initiates a series of inquiries across all of the enabled protocols and attempts to classify the device. If IM7 is not able to resolve that this is a ProLiant server, it may be being discarded if discovery filters are enabled.

I know you don't want to use 'Automatic Discovery,' but as a troubleshooting measure, go in there and add only the IP address of this errant device and force a discovery. This should help you determine whether IM7 can resolve the device or not.

[Jadrice Toussaint]

Ulrik -

I agree with David, I would also check the discovery filters and make sure that it is not enabled. Furthermore, the device should definitely be part of the ping inclusion range for SNMP discovery to work per HP's documentation.

[Ulrik Ivers]

Hi,

If I do a ping discovery everything works as acharm. But I still can't SNMP Trap Auto-Discovery to work...

[Andrei Khairetdinov]

Could it be because of the way the device link is specified? I mean what if you change Settings ->Security->Device links to other setting and try to Trap Autodiscovery again ? Just an idea..