Hello,

I am facing a critical issue here. When i try to do SNMPWALK on the MIB FREERADIUS-NOTIFICATION-MIB::serverGlobal i am getting the below error
"FREERADIUS-NOTIFICATION-MIB::serverGlobal = No Such Object available on this agent at this OID".
The command that i use is snmpwalk -v2c -c public localhost FREERADIUS-NOTIFICATION-MIB::serverGlobal

snmpd.conf file has

rouser public
rwuser public
rocommunity public localhost
rwcommunity public localhost


Please help me to fix this issue.

People still use SNMP?!?

If memory serves, that error is because the MIB table declared that this object would exist, or the table provided for that object indicated that it would have such an extension or logical part of an array for the walk, and the walk failed because the table is incorrect or the arrays offered by this table are incomplete.

I think to really look at this, the MIB table it's trying to browse would be helpful and the specific object where the walk is failing is also helpful. I used to work on telephony network access points and they would provide things like PPTP, L2TP, or IPSec connections, so there were different conditions to encounter for a MIB walk. For instance, just the device and relevant attributes might be one level of extension and that table would be capable of being variable in size, but would be fixed depending on how the device was configured or provisioned; whereas connection based MIB arrays or sub-tables would be variable, and say one list would contain allocated or connected nodes while another list would contain un-connected nodes, and also since our device could service a variety of network tunnel or encryption types, likewise the MIB connection tables for each technology type would vary, meaning they'd be dynamic arrays. So a MIB walk would fail if our software didn't properly account for telling the manager the right size of each array when we responded to the next node.

So my thinking here is one or more devices is simply giving you bad data and causing the MIB walk to fail. Well, in that case I'd identify the specific MIB object, and thus trace it to the exact equipment, the exact endpoint, and determine what the specific complaint is, but after that it would be a matter of diagnosing why that endpoint is causing the walk to fail.

1 members found this post helpful.

Thanks rtmistler for the reply. Actually i am new for SNMP. So this looks more of high level. Please give some suggestions on how to overcome this issue.

When you do a MIB walk, it outputs all the objects logically in a list which follows the tree advertised by the device or group of devices which you are performing the MIB walk on. What output specifically are you getting? Are you saying that you solely get just that one complaint information you originally posted? The first place I'd look is at the RADIUS server and determine if it is operating properly. I know you can remove a node from the walk so that it will skip it and if the full walk does work then the one node or top level tree where this complaint happens is the device causing this problem. Diagnosing exactly what that problem is, may be difficult. Either a full MIB walk worked before, or it hasn't. If it's never worked, then you have little basis to fall back on to note a change in device behavior. However if it worked before and now doesn't work; first action would be to reboot or restart the device providing FREE RADIUS services, a.k.a. whatever RADIUS server you happen to have and then retry the walk. Also check the logs on that RADIUS server and see if it is indicating problems, such as problems which are new, or even problems stating that it was asked to respond to MIB object queries and it didn't or couldn't.

But When i try to do snmpwalk on MIB SNMPv2-MIB::system i get the below results

SNMPv2-MIB::sysDescr.0 = STRING: Linux xxxx 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 EDT 2012 x86_64
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.8072.3.2.10
SNMPv2-MIB::sysUpTime.0 = Timeticks: (648742) 1:48:07.42
SNMPv2-MIB::sysContact.0 = STRING: xxx@radius.com
SNMPv2-MIB::sysName.0 = STRING: xxxx
SNMPv2-MIB::sysLocation.0 = STRING: xxxx
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORID.1 = OID: SNMPv2-SMI::snmpModules.11.3.1.1
SNMPv2-MIB::sysORID.2 = OID: SNMPv2-SMI::snmpModules.15.2.1.1
SNMPv2-MIB::sysORID.3 = OID: SNMPv2-SMI::snmpModules.10.3.1.1
SNMPv2-MIB::sysORID.4 = OID: SNMPv2-MIB::snmpMIB
SNMPv2-MIB::sysORID.5 = OID: SNMPv2-SMI::mib-2.49
SNMPv2-MIB::sysORID.6 = OID: SNMPv2-SMI::mib-2.4
SNMPv2-MIB::sysORID.7 = OID: SNMPv2-SMI::mib-2.50
SNMPv2-MIB::sysORID.8 = OID: SNMPv2-SMI::snmpModules.16.2.2.1
SNMPv2-MIB::sysORID.9 = OID: SNMPv2-SMI::snmpModules.13.3.1.3
SNMPv2-MIB::sysORID.10 = OID: SNMPv2-SMI::mib-2.92
SNMPv2-MIB::sysORDescr.1 = STRING: The MIB for Message Processing and Dispatching.
SNMPv2-MIB::sysORDescr.2 = STRING: The management information definitions for the SNMP User-based Security Model.
SNMPv2-MIB::sysORDescr.3 = STRING: The SNMP Management Architecture MIB.
SNMPv2-MIB::sysORDescr.4 = STRING: The MIB module for SNMPv2 entities
SNMPv2-MIB::sysORDescr.5 = STRING: The MIB module for managing TCP implementations
SNMPv2-MIB::sysORDescr.6 = STRING: The MIB module for managing IP and ICMP implementations
SNMPv2-MIB::sysORDescr.7 = STRING: The MIB module for managing UDP implementations
SNMPv2-MIB::sysORDescr.8 = STRING: View-based Access Control Model for SNMP.
SNMPv2-MIB::sysORDescr.9 = STRING: The MIB modules for managing SNMP Notification, plus filtering.
SNMPv2-MIB::sysORDescr.10 = STRING: The MIB module for logging SNMP Notifications.
SNMPv2-MIB::sysORUpTime.1 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.2 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.3 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.4 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.5 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.6 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.7 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.8 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.9 = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::sysORUpTime.10 = Timeticks: (0) 0:00:00.00

So that's fine what you posted, all looks sensible to me.

You're saying that eventually it runs into the FREE RADIUS MIB and dies, right? On that I say it has either previously worked, or never worked, and if you either restart or disable the RADIUS server (not saying that's a desired action if it's being used) that would either remove that error or help in diagnosing that error. But if you've never successfully done a MIB walk past that RADIUS server's table before, then it may be that the RADIUS server has an inherent problem responding to the next node request.

Or are you asking what all that (shown in your recent post) means?

I was not able to do a walk on MIB FREERADIUS-NOTIFICATION-MIB::serverGlobal from before. I tried restarting the radius as well. But no luck.

Your choices are to investigate further by way of contacting the provider (creator, supplier, vendor, maker) of that RADIUS server, or removing that node from the walk.

thanks rtmistler. I would like to have some more suggestions like people who have faced the same kind of issue.

Hi Guys, Any idea on how to receive the SNMP traps that are sent ?

SNMP Traps are different than a MIB walk. Traps are sent by the agent unsolicited to the management station. A MIB walk is a continued series of get-next requests performed by the management station. Your original complaint was that the agent crapped out responding to a get-next request. You configure the traps in communications via the management station to the agent and you tell the agent to send you specific traps.

Hell Yes.