SNMP Community Name Other Than public or private Does Not Respond in the Solaris 10 SEA snmpdx Subagent
(Doc ID 1484641.1)
Last updated on JUNE 29, 2018
Applies to:Solaris Operating System - Version 10 3/05 to 10 1/13 U11 [Release 10.0]
Information in this document applies to any platform.
A program that is a SNMP subagent that utilizes the Solaris 10 SEA libraries to register with snmpdx, will not respond to snmpget or snmpwalk queries when a community name other than public or private is used. It can return a error such as the following example where the community name of "test" was used.
# /usr/sfw/bin/snmpget -v 1 -c test xxx.xxx.xxx.xxx sysDescr.0 Error in packet Reason: (noSuchName) There is no such variable name in this MIB. Failed object: SNMPv2-MIB::sysDescr.0
It at times can also return a NULL response.
Solaris 10's SMA's snmpd is running as a master agent and SEA's snmpdx is running as a subagent, proxy agent. In this situation there was a third party subagent that would register and communicate with snmpd. It had a developed SNMP subagent written for the SEA and usings its librariees. This may have been via the SEA Toolkit suipplied several years ago.
It was noted that a snmpget can be done when using the community name of public. Once it was configured to use a unique community name in addition to public and private, it fails to respond to its OID. It can return a Error in packet.. messages or a response of NULL:
Successful query example:
# /usr/sfw/bin/snmpget -v 1 -c test localhost .22.214.171.124.126.96.36.199.188.8.131.52 SNMPv2-SMI::enterprises.184.108.40.206.1.0 = STRING: "Version 1.2.6"
Unsuccessful query example:
#/usr/sfw/bin/snmpget -v 1 -c test localhost .220.127.116.11.18.104.22.168.22.214.171.124 SNMPv2-SMI::enterprises.126.96.36.199.1.0 = NULL
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document