The main reason of this error is a mismatch on SNMP community name. When a SNMP query is sent, the community name is checked with the one from the SNMP agent.
There are three possible reasons for the mismatch :
- a) Netmaster has not sent the correct community name
To resolve this problem, do the following:
- Enter the '/IPADMIN' shortcut and select 'S - Maintain SNMP Host Details'
- From this screen, select the MASK that you would like to change, eg.:
=======================================================================
*.*.*.* V1 Express Setup by XXXXXX - XXXX(0002)
1.2.*.* V2C hi
1.2.3.4 V2C hi
=======================================================================
- In the 'U=Update' selection you can change the SNMP options:
=======================================================================
Identify the SNMP Host
IP Address/Mask............ *.*.*.*
Description ............... Express Setup by XXXXXX - XXXX(0002)
SNMP Version to Use ....... V1 (V1 V2C or V3)
Community Names (For SNMP V1 or SNMP V2C)
SNMP GET Community Name ... public
SNMP SET Community Name ...
=======================================================================
The SNMP GET Community Name is the value required for read privileges on the remote host, and the SNMP SET Community Name is the value required to change values on the remote host.
- Change the Community Name to the one you use. When you change any values, do a 'PF4' to SAVE it.
- Re-run the SELFTEST.
- b) The SNMP Agent is configured with an incorrect community name -
- To resolve this problem, do the following:
Update the TCPIP PROFILE and check the name found from
SACONFIG COMMUNITY xxxxxx AGENT 161
SACONFIG ENABLED SETSENABLED
The xxxxxx represents the community name and must match the one from PWSRC.
- c) An error has occurred during SNMP Agent initialization (OSNMPD, SNMPD) reported in the Joblog.
Review and correct the error. The SNMP Agent should start successfully.