SNMP Polling issue

[aalicea]

Hi I need some help monitoring an SNMP device without using traps.

After I create a remote_snmp network component with a custom OID, assigned to a group and a template... the newly created agent does not seem to "poll" the data from the monitored device.
I ran tcpdump in the server to see if there are any SNMP packets in flow but nothing shows up.  SNMP walk does work when editing/assigning the module.

Am I missing something on the backend?

Adam

[Manuel Arostegui]

What if you run snmpget -v 1 -c “community” IP OID from the pandora server to the agent you want to get information from?
Does it work fine?

[aalicea]

What if you run snmpget -v 1 -c “community” IP OID from the pandora server to the agent you want to get information from?
Does it work fine?

I ran it and it gave me the information I needed (INT) value was 72 which is the temperature in the room.  I also tried with some other standard OIDs and worked with no issues.   I noticed that when I go to the data tab in the agent "view" area, it claims it has no modules, however if I go to the modules in the "manage" area, they are showing there.

[aalicea]

A bit more of information...
I seem to have a similar problem as posted on the topic titled "SNMP Module not working" (sorry can't post links as of yet)


I am using Fedora Core 7 instead.

[Manuel Arostegui]

It's normal, that it says it has no modules but on the other hand you can see them in the manage area, that's normal. It doesn't show modules till it has any data to show.

Let's check again the configuration, try do not using the template.
Doesn't it work either if you create the module by hand, setting up the IP, the OID and the community? (remote_snmp, type, of course)

[aalicea]

ok, I created another Agent, this time with a manual setup component  using group "General", remote_snmp interval 60 sec (for test only), the OID in question, the community and still no show on data.  The agent_keepalive module was added automatically (expected).

[Manuel Arostegui]

Silly question, the IP too, right?

Also, another question, the agent the module is in...it has a network server assigned, right?

[aalicea]

silly me for not posting it.

Yes the IP is there and the network server is pandora_Net

[Sancho Lerena]

silly me for not posting it.

Yes the IP is there and the network server is pandora_Net

Quick checklist:

1. Check that your pandora network server is UP and running fine.
2. Check that SNMP perl dependencies for your pandora network system is fine.
3. Check that parameters like IP address, OID and snmp community dont have any blank space in it.
4. Recheck OID, and make sure that system that are running pandora network server has network visibility on port 161/UDP (snmp) to the destination.
5. Check that this agent has assigned your network server in agent setup.
6. Check SNMP tyle (is not the same to get a remote_snmp or to get a remote_snmp_inc module type).

[aalicea]

1. Check that your pandora network server is UP and running fine.
-- Checked it, it shows on my ps -A as running (pandora_network)

2. Check that SNMP perl dependencies for your pandora network system is fine.
-- Re-ran the setup scripts, no warnings

3. Check that parameters like IP address, OID and snmp community dont have any blank space in it.
-- Checked
4. Recheck OID, and make sure that system that are running pandora network server has network visibility on port 161/UDP (snmp) to the destination.
-- Ran the same OID with snmpget from the server, no problem, returns expected value

5. Check that this agent has assigned your network server in agent setup.
-- Checked, ok

6. Check SNMP tyle (is not the same to get a remote_snmp or to get a remote_snmp_inc module type).  
-- Checked, certainly using remote_snmp (the value is just a simple INT value)

I ran tcpdump again after all these checks to see if the pandora server would generate udp packets while requesting snmp information from the device and I saw no packets.  When I ran snmpget, I did see all the conversation between the server and the device (eliminating the networking issue).  It feels like if Pandora is not spawning the "snmpget" process (my wild guess).

Thanks for helping...

[Sancho Lerena]

1. Check that your pandora network server is UP and running fine.
-- Checked it, it shows on my ps -A as running (pandora_network)

2. Check that SNMP perl dependencies for your pandora network system is fine.
-- Re-ran the setup scripts, no warnings

Check status on "View server" option. Should be on Green and updated. You should not have more than one network server....

I ran tcpdump again after all these checks to see if the pandora server would generate udp packets while requesting snmp information from the device and I saw no packets.  When I ran snmpget, I did see all the conversation between the server and the device (eliminating the networking issue).  It feels like if Pandora is not spawning the "snmpget" process (my wild guess).

Thanks for helping...

Mmm, weird. Pandora don't create a new process, it calls a snmp library function to get values using the native perl function.

What version of Pandora are you running ?, in what linux distro ?

[aalicea]

Pandora 1.3 on Fedora Core 7

[aalicea]

are you refering to the sub pandora_query_snmp routine?

Is there a way to turn on detailed logging so I can capture if the routine executes?

[aalicea]

Ok I think I am getting closer...

Found this error in the /var/log/pandora/pandora_server.error file:

A thread exited while 6 threads were running.
thread failed to start: Can't locate object method "new" via package "SNMP::Session" (perhaps you forgot to load "SNMP::Session"?) at /usr/bin/pandora_network line 415

I checked to see if CPAN Net::SNMP was ok:
CPAN: Storable loaded ok (v2.15)
Going to read /root/.cpan/Metadata

  Database was generated on Tue, 19 Feb 2008 11:30:48 GMT
Net::SNMP is up to date (v5.2.0).

Are there any other modules I might be missing?

[Manuel Arostegui]

Ummm can please paste the perl* and snmp* packages you installed in your fedora? (rpm -qa | grep -i perl) (rpm -qa | grep -i snmp )

We're getting closer and closer to the error, I'm sure we'll sort it out