Reset Search
 

 

Article

KB43644 - Inconsistent SNMP results for ifAdminStatus and ifOperStatus on the "sit0" and "lo" interfaces

« Go Back

Information

 
Last Modified Date7/16/2018 5:59 PM
Synopsis
This article describes an issue where SNMP results are inconsistent for ifAdminStatus and ifOperStatus on the "sit0" and "lo" interfaces.
Problem or Goal
It is observed that SNMP polling of the loopback (lo) and the 6to4tunnel (sit0) interfaces returns inconsistent results with ifAdminStatus and ifOperStatus being reported as up and down over time.
Cause
The loopback and 6to4 tunnel interfaces have the following OIDs for ifAdminStatus and ifOperStatus:

ifDescr

.1.3.6.1.2.1.2.2.1.2.1 = STRING: "lo"            (loopback)
.1.3.6.1.2.1.2.2.1.2.2 = STRING: "sit0"          (6to4 tunnel)

 ifAdminStatus

.1.3.6.1.2.1.2.2.1.7.1 = INTEGER: 1
.1.3.6.1.2.1.2.2.1.7.2 = INTEGER: 2

ifOperStatus

.1.3.6.1.2.1.2.2.1.8.1 = INTEGER: 1
.1.3.6.1.2.1.2.2.1.8.2 = INTEGER: 2
If the ifAdminStatus or ifOperStatus are queried they can return a value of either 1 (up) or 2 (down). These interfaces are created by the operating system kernel, the sit0 is not used by the PCS/PPS system and the lo interface is used internally and is not accessible externally.
Solution
The results of the ifAdminStatus and ifOperStatus of the lo and sit0 interfaces can be ignored and should not be monitored. While the kernel can change the status of these between up and down, it has no impact on the operation of the device.
Related Links
Attachment 1 
Created ByMatthew Spiers

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255