SNMP error????

[Reshma Malusare]

Jul 29 04:10:08 aoepdas1 /usr/lib/snmp/snmpdx: [ID 702911 daemon.error] agent_process() : bad community from 160.92.240.20
Jul 29 04:10:08 aoepdas1 /usr/lib/snmp/snmpdx: [ID 702911 daemon.error] agent_process() : bad community from 160.92.240.20
Jul 29 04:10:13 aoepdas1 /usr/lib/snmp/snmpdx: [ID 702911 daemon.error] local pdu process error
Jul 29 04:10:13 aoepdas1 /usr/lib/snmp/snmpdx: [ID 702911 daemon.error] local pdu process error
Jul 29 04:10:13 aoepdas1 /usr/lib/snmp/snmpdx: [ID 702911 daemon.error] session_send_loopback_request() failed
Jul 29 04:10:13 aoepdas1 /usr/lib/snmp/snmpdx: [ID 702911 daemon.error] session_send_loopback_request() failed


what is this error & how to resolve it?

[Torsten.]

This could be the reason:

bad community from 160.92.240.20

bad community means a wrong SNMP "password".

[Anshumali]

check your Mgmt Server and the SNMP string being sent, received.
Check /etc/snmpd.conf

get-community-name: XXXXX
#set-community-name: # enter community name
#contact: # enter contact person for agent
#location: # enter location of agent
#max-trap-dest: # enter max no. of trap-dest entries to be maintained.
trap-dest: XXXXXXX

[Reshma Malusare]

The Solstice Enterprise Agent master agent process snmpdx sometimes deletes a subagent from the internal list of registered subagents even though the subagent process is still running. This problem occurs when SNMP managers use wrong community strings. It is often indicated by the error message in /var/adm/messages:

error("agent_process() : bad community from %sn,
ip_address_string (&(address->sin_addr)));

If a subagent receives a request with a bad community string, it is obliged to discard the string and not respond. However, the master agent process snmpdx cannot distinguish between a subagent that is no longer functioning and a subagent that has a discarded string. The master agent attempts to ping the subagent with a private packet containing a public community string. If the subagent does not accept the public community strings and thus does not respond to the ping, it is deleted from the agent table after it has been sent 5 consecutive bad community strings by the management application. Consequently, all subsequent polling or snmpget operations the subagent fail.

[Reshma Malusare]

Solution: Start snmpdx by using the -f 0 flag. This flag sets the number of timeouts from operations performed by a master on a subagent to infinity. The default value of five is overridden and the subagent is not deleted from the agent table if it is cannot respond to an internal snmpdx ping packet with the public community string.

i restarted :
K07snmpdx
S76snmpdx
S77dmi

also i checked /etc/init.d/init.snmpdx..


But its still not working....

I know this error is because
1]manager delete the subagent from subagent table..
or 2]160.92.240.20 is giving wrong community name.

we checked all..but still not getting solution.