Overview
Retrieve the OIDs for a particular
Enterprise MIB by running the
snmpwalk
command in Linux. You can also retrieve the OIDs through the MIB browser or any SNMP manager. SNMP uses five basic messages for communication between the manager and agent, one of which is the GET request that is used to query for information on or about a network entity. The
snmpwalk
command uses Getnext request. The SBC responds with a Get response that includes the index and the value of the next object.
The OIDs are indexes in the MIB tables, and indexes are not readable using SNMP GET requests. The SNMP GETNEXT requests are used to find out what indexes are currently present in the MIB tables. An SNMP GETNEXT request can return all rows in a MIB table, depending on what OID is requested. The getNext response contains the OID from that table with the index values encoded into the OID.
Example
Code Block |
---|
-- tagpath /system/memoryUtilIntervalStatistics
sonusSystemMemoryUtilIntervalStatisticsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SonusSystemMemoryUtilIntervalStatisticsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "
The memory utilization for the
'n' number of intervals.
"
::= { sonusSystem 20 }
-- tagpath /system/memoryUtilIntervalStatistics
sonusSystemMemoryUtilIntervalStatisticsEntry OBJECT-TYPE
SYNTAX SonusSystemMemoryUtilIntervalStatisticsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION ""
INDEX { sonusSystemMemoryUtilIntervalStatisticsNumber, sonusSystemMemoryUtilIntervalStatisticsCeName }
::= { sonusSystemMemoryUtilIntervalStatisticsTable 1 }
SonusSystemMemoryUtilIntervalStatisticsEntry ::=
SEQUENCE {
sonusSystemMemoryUtilIntervalStatisticsNumber Unsigned32,
sonusSystemMemoryUtilIntervalStatisticsCeName String,
sonusSystemMemoryUtilIntervalStatisticsIntervalValid INTEGER,
sonusSystemMemoryUtilIntervalStatisticsTime Unsigned32,
sonusSystemMemoryUtilIntervalStatisticsAverage Unsigned32,
sonusSystemMemoryUtilIntervalStatisticsHigh Unsigned32,
sonusSystemMemoryUtilIntervalStatisticsLow Unsigned32,
sonusSystemMemoryUtilIntervalStatisticsAverageSwap Unsigned32,
sonusSystemMemoryUtilIntervalStatisticsHighSwap Unsigned32,
sonusSystemMemoryUtilIntervalStatisticsLowSwap Unsigned32
}
|
The table sonusSystemMemoryUtilIntervalStatisticsTable has indexes sonusSystemMemoryUtilIntervalStatisticsNumber and sonusSystemMemoryUtilIntervalStatisticsCeName. Thus, there will be a row in this table for each combination of interval number and CE name. An HA pair will have two CEs or servers, each with a unique name.
If we perform a getNext request for this table using snmpwalk we get the following result:
Code Block |
---|
snmpwalk -c admin -v 2c sbx140-1:161 1.3.6.1.4.1.2879.2.8.5.1.20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.3.28.6.83.66.88.49.52.48 = INTEGER: 1
iso.3.6.1.4.1.2879.2.8.5.1.20.1.3.28.6.83.66.88.49.52.51 = INTEGER: 1
iso.3.6.1.4.1.2879.2.8.5.1.20.1.3.29.6.83.66.88.49.52.48 = INTEGER: 1
iso.3.6.1.4.1.2879.2.8.5.1.20.1.3.29.6.83.66.88.49.52.51 = INTEGER: 1
iso.3.6.1.4.1.2879.2.8.5.1.20.1.3.30.6.83.66.88.49.52.48 = INTEGER: 1
iso.3.6.1.4.1.2879.2.8.5.1.20.1.3.30.6.83.66.88.49.52.51 = INTEGER: 1
iso.3.6.1.4.1.2879.2.8.5.1.20.1.3.31.6.83.66.88.49.52.48 = INTEGER: 1
iso.3.6.1.4.1.2879.2.8.5.1.20.1.3.31.6.83.66.88.49.52.51 = INTEGER: 1
iso.3.6.1.4.1.2879.2.8.5.1.20.1.4.28.6.83.66.88.49.52.48 = Gauge32: 365862
iso.3.6.1.4.1.2879.2.8.5.1.20.1.4.28.6.83.66.88.49.52.51 = Gauge32: 365862
iso.3.6.1.4.1.2879.2.8.5.1.20.1.4.29.6.83.66.88.49.52.48 = Gauge32: 366761
iso.3.6.1.4.1.2879.2.8.5.1.20.1.4.29.6.83.66.88.49.52.51 = Gauge32: 366761
iso.3.6.1.4.1.2879.2.8.5.1.20.1.4.30.6.83.66.88.49.52.48 = Gauge32: 367661
iso.3.6.1.4.1.2879.2.8.5.1.20.1.4.30.6.83.66.88.49.52.51 = Gauge32: 367661
iso.3.6.1.4.1.2879.2.8.5.1.20.1.4.31.6.83.66.88.49.52.48 = Gauge32: 368561
iso.3.6.1.4.1.2879.2.8.5.1.20.1.4.31.6.83.66.88.49.52.51 = Gauge32: 368561
iso.3.6.1.4.1.2879.2.8.5.1.20.1.5.28.6.83.66.88.49.52.48 = Gauge32: 20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.5.28.6.83.66.88.49.52.51 = Gauge32: 14
iso.3.6.1.4.1.2879.2.8.5.1.20.1.5.29.6.83.66.88.49.52.48 = Gauge32: 20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.5.29.6.83.66.88.49.52.51 = Gauge32: 14
iso.3.6.1.4.1.2879.2.8.5.1.20.1.5.30.6.83.66.88.49.52.48 = Gauge32: 20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.5.30.6.83.66.88.49.52.51 = Gauge32: 14
iso.3.6.1.4.1.2879.2.8.5.1.20.1.5.31.6.83.66.88.49.52.48 = Gauge32: 20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.5.31.6.83.66.88.49.52.51 = Gauge32: 14
iso.3.6.1.4.1.2879.2.8.5.1.20.1.6.28.6.83.66.88.49.52.48 = Gauge32: 20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.6.28.6.83.66.88.49.52.51 = Gauge32: 14
iso.3.6.1.4.1.2879.2.8.5.1.20.1.6.29.6.83.66.88.49.52.48 = Gauge32: 20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.6.29.6.83.66.88.49.52.51 = Gauge32: 14
iso.3.6.1.4.1.2879.2.8.5.1.20.1.6.30.6.83.66.88.49.52.48 = Gauge32: 20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.6.30.6.83.66.88.49.52.51 = Gauge32: 14
iso.3.6.1.4.1.2879.2.8.5.1.20.1.6.31.6.83.66.88.49.52.48 = Gauge32: 20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.6.31.6.83.66.88.49.52.51 = Gauge32: 14
iso.3.6.1.4.1.2879.2.8.5.1.20.1.7.28.6.83.66.88.49.52.48 = Gauge32: 20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.7.28.6.83.66.88.49.52.51 = Gauge32: 14
iso.3.6.1.4.1.2879.2.8.5.1.20.1.7.29.6.83.66.88.49.52.48 = Gauge32: 20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.7.29.6.83.66.88.49.52.51 = Gauge32: 14
iso.3.6.1.4.1.2879.2.8.5.1.20.1.7.30.6.83.66.88.49.52.48 = Gauge32: 20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.7.30.6.83.66.88.49.52.51 = Gauge32: 14
iso.3.6.1.4.1.2879.2.8.5.1.20.1.7.31.6.83.66.88.49.52.48 = Gauge32: 20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.7.31.6.83.66.88.49.52.51 = Gauge32: 14
iso.3.6.1.4.1.2879.2.8.5.1.20.1.8.28.6.83.66.88.49.52.48 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.8.28.6.83.66.88.49.52.51 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.8.29.6.83.66.88.49.52.48 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.8.29.6.83.66.88.49.52.51 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.8.30.6.83.66.88.49.52.48 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.8.30.6.83.66.88.49.52.51 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.8.31.6.83.66.88.49.52.48 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.8.31.6.83.66.88.49.52.51 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.9.28.6.83.66.88.49.52.48 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.9.28.6.83.66.88.49.52.51 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.9.29.6.83.66.88.49.52.48 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.9.29.6.83.66.88.49.52.51 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.9.30.6.83.66.88.49.52.48 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.9.30.6.83.66.88.49.52.51 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.9.31.6.83.66.88.49.52.48 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.9.31.6.83.66.88.49.52.51 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.10.28.6.83.66.88.49.52.48 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.10.28.6.83.66.88.49.52.51 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.10.29.6.83.66.88.49.52.48 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.10.29.6.83.66.88.49.52.51 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.10.30.6.83.66.88.49.52.48 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.10.30.6.83.66.88.49.52.51 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.10.31.6.83.66.88.49.52.48 = Gauge32: 0
iso.3.6.1.4.1.2879.2.8.5.1.20.1.10.31.6.83.66.88.49.52.51 = Gauge32: 0 |
The snmpwalk performs getNext requests of table iso.3.6.1.4.1.2879.2.8.5.1.20, which is the OID for sonusSystemMemoryUtilIntervalStatisticsTable. It returns the values of sonusSystemMemoryUtilIntervalStatisticsNumber and sonusSystemMemoryUtilIntervalStatisticsCeName encoded in the OID.
Code Block |
---|
snmpwalk -c admin -t 10 -v 2c sbx140-1:161 1.3.6.1.4.1.2879.2.8.5.1.20
iso.3.6.1.4.1.2879.2.8.5.1.20.1.3.28.6.83.66.88.49.52.48 = INTEGER: 1
iso.3.6.1.4.1.2879.2.8.5.1.20.1.3.28.6.83.66.88.49.52.51 = INTEGER: 1 |
- The iso.3.6.1.4.1.2879.2.8.5.1.20 is the OID for sonusSystemMemoryUtilIntervalStatisticsTable. The next octet in the OID is the value for sonusSystemMemoryUtilIntervalStatisticsEntry, which is ".1” in this case.
- The next octet is for the first non-index object. In this case it is “.3” for sonusSystemMemoryUtilIntervalStatisticsIntervalValid.
- The next octet is for the sonusSystemMemoryUtilIntervalStatisticsNumber index. In this case it is “28” for the 28th interval.
- The next set of octets is for sonusSystemMemoryUtilIntervalStatisticsCeName. In this case it is “6.83.66.88.49.52.51”. As sonusSystemMemoryUtilIntervalStatisticsCeName is a string, it is encoded as a length followed by the ASCII characters for the CE name. In this case the length is “6” and the next 6 octets are “SBX140” encoded in ASCII.
- The second getNext response has iso.3.6.1.4.1.2879.2.8.5.1.20.1.3.28.6.83.66.88.49.52.51 for the objects sonusSystemMemoryUtilIntervalStatisticsIntervalValid, sonusSystemMemoryUtilIntervalStatisticsNumber 28, and sonusSystemMemoryUtilIntervalStatisticsCeName “SBX143”. The rest of the getNext responses are for all the objects and rows in the table.
Retrieving OIDs
Execute the snmpwalk
command in the following Linux operating system to retrieve the OIDs:
Linux:
Code Block |
---|
|
snmpwalk -v 2c -c <community string> <sbc ip> <oid> |
Solaris:
code/usr/sfw/bin/snmpwalk -v 2c -c <community string> <sbc ip> <oid>
|
Note |
---|
SBC SWe is running on various hardware platforms. Thus, the timeout value must be adjusted based on the hardware type if snmpwalk command is used for SBC SWe. |
For more information on SNMP, refer to the RFC 3411 http://www.rfc-editor.org/rfc/rfc3411.txt.
Retrieving OIDs Using
company Insight EMS
Noprint |
---|
Click to view : Toggle Cloak |
---|
id | Retrieving OIDs by Using EMS |
---|
|
|
Cloak |
---|
id | Retrieving OIDs by Using EMS |
---|
|
To run the snmppwalk command in from the EMS model3: Register - Login to model3 and register the SBC node
on the company Insight Element Management System. For more information, refer to .- .
Run the following command from the EMSthe model3. The number sequence "1.3.6.1.4.1.2879.2.8.5 " represents the sonusSystemMIB OID. none The following output displays Example results:
|
Retrieving OIDs Using a Linux Server
Noprint |
---|
Click to view : Toggle Cloak |
---|
id | Retrieving OIDs by Using a Local Server |
---|
|
|
Cloak |
---|
id | Retrieving OIDs by Using a Local Server |
---|
|
Copy the MIBs to the Linux server and execute the following commands in the server to retrieve the OIDs: :none::none |
Retrieving OIDs Using SNMP Browser
Noprint |
---|
Click to view : Toggle Cloak |
---|
id | Retrieving OIDs by Using SNMP Browser |
---|
|
|
Cloak |
---|
id | Retrieving OIDs by Using SNMP Browser |
---|
|
Retrieve the OIDs using the SNMP browser. A few examples showing the OIDs for company Enterprise MIBs are shown below. Example 1 FigureRetrieving the OIDs for Address Context MIBBLOCK
Most of the Ribbon MIB tables use strings for their indexes. A string in SNMP is a series of OID values. The first OID is the length of the string. The following OIDs are the characters encoded in ASCII. Therefore, a string is encoded as a length followed by ASCII characters. To decode the values, refer to ASCII table. Use the GETNEXT request in an SNMP browser to retrieve the OIDs further: - 1.3.6.1.4.1.2879.2.10.2.9.1.1.7.100.101.102.97.117.108.116.4.76.73.70.49
- 1.3.6.1.4.1.2879.2.10.2.9.1.1.7.100.101.102.97.117.108.116.4.76.73.70.50
Use the ASCII table to decode the OIDs: - 1.3.6.1.4.1.2879.2.10.2.9.1.1.7(length of 7).100(d).101(e).102(f).97(a).117(u).108(l).116(t).4(length of 4).76(L).73(I).70(F).49(1)
- 1.3.6.1.4.1.2879.2.10.2.9.1.1.7(length of 7).100(d).101(e).102(f).97(a).117(u).108(l).116(t).4(length of 4).76(L).73(I).70(F).50(2)
Example 2 FigureRetrieving the OIDs for System MIBBLOCK
Most of the Ribbon Enterprise MIB tables use strings for their indexes. A string in SNMP is a series of OID values. The first OID is the length of the string. The following OIDs are the characters encoded in ASCII. Therefore, a string is encoded as a length followed by ASCII characters. To decode the values, refer to ASCII table. Use the GETNEXT request to retrieve the OIDs further: Use the ASCII table to decode the OID: - 1.3.6.1.4.1.2879.2.8.5.1.5.1.3.5(length of 5).72(H).111(o).110(n).100(d).97(a).0(NUL)
|