crepInterfaceStatsEntry
CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB ·
.1.3.6.1.4.1.9.9.601.1.2.2.1
Object
row
The counter entries are not persistent. This is because once REP is un-configured on the interface the row would be deleted and hence they will restart if REP is configured once again on the interface. NMS need to check for 'crepCounterDiscontinuityTime' to see if the counters have restarted.
Context
- MIB
- CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB
- OID
.1.3.6.1.4.1.9.9.601.1.2.2.1- Type
- row
- Status
- current
- Parent
- crepInterfaceStatsTable
- Table
- crepInterfaceStatsTable
- Children
- 17
Net-SNMP examples
How SNMP and these commands workUse a bulk walk to inspect objects and instances beneath this OID.
Walk the subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB::crepInterfaceStatsEntry'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB::crepInterfaceStatsEntry'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.