What is the additional number in OID when using SNMP with OneView Monitor?

Document ID : KB000113745
Last Modified Date : 13/09/2018
Show Technical Document Details
Question:
I have configured SNMP Agent in our 3 Policy Servers, and when I run a snmpget query on the Policy Server running the OneView Monitor, I get the values for each Policy Server, however I do see an additional number being added to the answer returned. For example:

The command:
snmpwalk -v 2c -c public 10.10.10.10:8001 1.3.6.1.4.1.2552.200.300.1.3.1.3 
Returns:
SNMPv2-SMI::enterprises.2552.200.300.1.3.1.3.1 = IpAddress: 10.10.10.10
SNMPv2-SMI::enterprises.2552.200.300.1.3.1.3.4 = IpAddress: 10.10.10.11 
SNMPv2-SMI::enterprises.2552.200.300.1.3.1.3.6 = IpAddress: 10.10.10.12


For each Policy Server I get the correct value, but the OID has an additional number at the end. As we are using scripts to monitor this, we need to know if this additional number can change if the Policy Server is restarted?

 
Answer:
The string SNMPv2-SMI::enterprises.2552.200.300.1.3.1.3 refers to the OID for policyServerHostID. It is fixed as per the MIB and SNMP schema and not bound to change.  But the last number (like 2552.200.300.1.3.1.3.6 seen in this case) is a temporary OneView Monitor indexing number which gets changed every time that particular Policy Server restarts. 

Below is a sample case of a test done with 3 servers configured to One View Monitor:

PS1 = 10.10.10.49 
PS2 = 10.10.10.50 
PS3 = 10.10.10.51 

Added PS1 to OVM 
snmpwalk -v:2c -c:public -r:10.10.10.49 -p:8001 -os:1.3.6.1.4.1.2552.200.300.1.3.1.3 | findstr 1.3.1.3 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.1, Type=IpAddress, Value=10.10.10.49 


Added PS2 to OVM 
snmpwalk -v:2c -c:public -r:10.10.10.49 -p:8001 -os:1.3.6.1.4.1.2552.200.300.1.3.1.3 | findstr 1.3.1.3 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.1, Type=IpAddress, Value=10.10.10.49 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.2, Type=IpAddress, Value=10.10.10.50 


Added PS3 to OVM 
snmpwalk -v:2c -c:public -r:10.10.10.49 -p:8001 -os:1.3.6.1.4.1.2552.200.300.1.3.1.3 | findstr 1.3.1.3 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.1, Type=IpAddress, Value=10.10.10.49 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.2, Type=IpAddress, Value=10.10.10.50 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.3, Type=IpAddress, Value=10.10.10.51 


Stopped PS2 and PS3:
snmpwalk -v:2c -c:public -r:10.10.10.49 -p:8001 -os:1.3.6.1.4.1.2552.200.300.1.3.1.3 | findstr 1.3.1.3 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.1, Type=IpAddress, Value=10.10.10.49 


Started PS3 (Note that the last portion of PS3 changed to 4, earlier it was 3):
snmpwalk -v:2c -c:public -r:10.10.10.49 -p:8001 -os:1.3.6.1.4.1.2552.200.300.1.3.1.3 | findstr 1.3.1.3 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.1, Type=IpAddress, Value=10.10.10.49 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.4, Type=IpAddress, Value=10.10.10.51 


Started PS2 (Note that the last portion of PS2 changed to 5, earlier it was 2):
snmpwalk -v:2c -c:public -r:10.10.10.49 -p:8001 -os:1.3.6.1.4.1.2552.200.300.1.3.1.3 | findstr 1.3.1.3 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.1, Type=IpAddress, Value=10.10.10.49 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.4, Type=IpAddress, Value=10.10.10.51 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.5, Type=IpAddress, Value=10.10.10.50 


The index resets whenever the OVM restarts. So when it is checked after restarting the OVM:
snmpwalk -v:2c -c:public -r:10.10.10.49 -p:8001 -os:1.3.6.1.4.1.2552.200.300.1.3.1.3 | findstr 1.3.1.3 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.1, Type=IpAddress, Value=10.10.10.49 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.2, Type=IpAddress, Value=10.10.10.50 
OID=.1.3.6.1.4.1.2552.200.300.1.3.1.3.3, Type=IpAddress, Value=10.10.10.51