CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB

        This MIB module defines objects required for managing
Resilient Ethernet Protocol (REP).
        
Resilient Ethernet Protocol (REP) is a Cisco proprietary 
protocol that provides an alternative to Spanning Tree 
Protocol (STP) to control network loops, handle link 
failures and improve convergence time. 
        
REP controls a group of ports connected in a segment; 
ensures that the segment does not create any bridging loops, 
and responds to link failures within the segment. 
        
The following diagram depicts a REP segment:
        
[Sw E1]E---NE[Sw 1]NE---NE[Sw 2]NE.........
                                          .
                                          .
[Sw E2]E---NE[Sw N]NE---NE[Sw N-1]NE.......
        
Sw : Switch.
E  : Edge port.
NE : Non-Edge port.  
E1/E2: Edge switches.  E1 and E2 can either be same or 
different switches.
        
A REP segment is a chain of ports connected to each other 
and configured with a segment identifier.  Each segment 
consists of standard (non-edge) segment ports and up to
two edge ports.  A device can have only two ports that 
belong to the same segment, and each segment port can have
only one external neighbor. 
        
One edge port in a REP segment acts as the primary edge
port; the other as the secondary edge port.  It is the primary 
edge port that always participates in VLAN load balancing in 
a REP segment.  REP VLAN load balancing is achieved by blocking
some VLANs at a configured alternate port and all other VLANs at
an edge port.  The execution (preemption) of VLAN load balancing
is triggered by manually enforcing it or after a pre-defined
delay, after the REP segment is complete.
        
When segment is completed, all ports will be in open state
except one port that can be in alternate state that is used for
VLAN load balancing as explained above.
    
Source file
CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB
Last revised
Identity
ciscoResilientEthernetProtocolMIB
Base OID
1.3.6.1.4.1.9.9.601
Imported Objects
CISCO-SMI ciscoMgmt
CISCO-TC CiscoVlanList
IF-MIB InterfaceIndex InterfaceIndexOrZero
Q-BRIDGE-MIB VlanId
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC RowStatus TEXTUAL-CONVENTION (no object page) TimeStamp TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/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::ciscoResilientEthernetProtocolMIB'
Walk the MIB 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::ciscoResilientEthernetProtocolMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (64)
.1.3.6.1.4.1.9.9.601
.1.3.6.1.4.1.9.9.601.0
.1.3.6.1.4.1.9.9.601.1
.1.3.6.1.4.1.9.9.601.1.1
.1.3.6.1.4.1.9.9.601.1.1.1
.1.3.6.1.4.1.9.9.601.1.1.2
.1.3.6.1.4.1.9.9.601.1.1.3
notifications per secondUnsigned32
.1.3.6.1.4.1.9.9.601.1.1.4
.1.3.6.1.4.1.9.9.601.1.1.5
.1.3.6.1.4.1.9.9.601.1.1.6
.1.3.6.1.4.1.9.9.601.1.2
.1.3.6.1.4.1.9.9.601.1.2.1
.1.3.6.1.4.1.9.9.601.1.2.1.1
.1.3.6.1.4.1.9.9.601.1.2.1.1.1
.1.3.6.1.4.1.9.9.601.1.2.1.1.10
.1.3.6.1.4.1.9.9.601.1.2.1.1.11
.1.3.6.1.4.1.9.9.601.1.2.1.1.12
Enumeration
.1.3.6.1.4.1.9.9.601.1.2.1.1.13
Integer32
.1.3.6.1.4.1.9.9.601.1.2.1.1.14
OctetString
.1.3.6.1.4.1.9.9.601.1.2.1.1.15
delay in secondsInteger32
.1.3.6.1.4.1.9.9.601.1.2.1.1.16
.1.3.6.1.4.1.9.9.601.1.2.1.1.17
.1.3.6.1.4.1.9.9.601.1.2.1.1.18
.1.3.6.1.4.1.9.9.601.1.2.1.1.19
.1.3.6.1.4.1.9.9.601.1.2.1.1.2
.1.3.6.1.4.1.9.9.601.1.2.1.1.20
Enumeration
.1.3.6.1.4.1.9.9.601.1.2.1.1.3
Enumeration
.1.3.6.1.4.1.9.9.601.1.2.1.1.4
OctetString
.1.3.6.1.4.1.9.9.601.1.2.1.1.5
.1.3.6.1.4.1.9.9.601.1.2.1.1.6
.1.3.6.1.4.1.9.9.601.1.2.1.1.7
.1.3.6.1.4.1.9.9.601.1.2.1.1.8
.1.3.6.1.4.1.9.9.601.1.2.1.1.9
.1.3.6.1.4.1.9.9.601.1.2.2
.1.3.6.1.4.1.9.9.601.1.2.2.1
.1.3.6.1.4.1.9.9.601.1.2.2.1.1
.1.3.6.1.4.1.9.9.601.1.2.2.1.10
.1.3.6.1.4.1.9.9.601.1.2.2.1.11
.1.3.6.1.4.1.9.9.601.1.2.2.1.12
.1.3.6.1.4.1.9.9.601.1.2.2.1.13
.1.3.6.1.4.1.9.9.601.1.2.2.1.14
.1.3.6.1.4.1.9.9.601.1.2.2.1.15
.1.3.6.1.4.1.9.9.601.1.2.2.1.16
.1.3.6.1.4.1.9.9.601.1.2.2.1.17
.1.3.6.1.4.1.9.9.601.1.2.2.1.2
.1.3.6.1.4.1.9.9.601.1.2.2.1.3
.1.3.6.1.4.1.9.9.601.1.2.2.1.4
.1.3.6.1.4.1.9.9.601.1.2.2.1.5
.1.3.6.1.4.1.9.9.601.1.2.2.1.6
.1.3.6.1.4.1.9.9.601.1.2.2.1.7
.1.3.6.1.4.1.9.9.601.1.2.2.1.8
.1.3.6.1.4.1.9.9.601.1.2.2.1.9
.1.3.6.1.4.1.9.9.601.1.3
.1.3.6.1.4.1.9.9.601.1.3.1
.1.3.6.1.4.1.9.9.601.1.3.1.1
.1.3.6.1.4.1.9.9.601.1.3.1.1.1
.1.3.6.1.4.1.9.9.601.1.3.1.1.2
.1.3.6.1.4.1.9.9.601.1.3.1.1.3
.1.3.6.1.4.1.9.9.601.1.3.1.1.4
.1.3.6.1.4.1.9.9.601.1.3.1.1.5
Enumeration
.1.3.6.1.4.1.9.9.601.1.3.1.1.6
.1.3.6.1.4.1.9.9.601.2
.1.3.6.1.4.1.9.9.601.2.1
.1.3.6.1.4.1.9.9.601.2.2
Dependencies (19) 7 direct · 12 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (3)
Enumeration
notEdge(1)
edge(2)
edgePrimary(3)
edgeNoNeighbor(4)
edgeNoNeighborPrimary(5)
Unsigned32
OctetString
Conformance Groups (4)
A collection of global objects for use with the REP feature.
.1.3.6.1.4.1.9.9.601.2.2.1
A collection of interface specific objects for use with the REP
feature.
.1.3.6.1.4.1.9.9.601.2.2.2
A collection of notifications for use with the REP feature.
.1.3.6.1.4.1.9.9.601.2.2.3
A collection of segment specific objects for use with the REP feature.
.1.3.6.1.4.1.9.9.601.2.2.4
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.601.2.1.1
The compliance statement for
CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB.
Required groups
Object refinements
ObjectAccessSyntaxDescription
crepIfConfigRowStatus readonly
active(1), createAndGo(4), destroy(6)
Support for createAndWait, notReady and notInService values are
not required.
crepNotifsEnable readonly
read-write access is not required.
crepGlobalRepNotifsRate readonly
read-write access is not required.
Notifications / Traps (3)
NameOIDDescription
.1.3.6.1.4.1.9.9.601.0.1
This notification is sent when a REP interface has entered or
left REP link operational status. The link is considered
operational when 'crepIfOperStatus' is 'twoWay'.
'crepIfOperStatus' would be 'none' if the
crepInterfaceConfigEntry entry has been removed.
.1.3.6.1.4.1.9.9.601.0.2
This notification indicates the status of the preemption
triggered on REP primary edge.
.1.3.6.1.4.1.9.9.601.0.3
This notification is sent when the role of a Port changes
that are indicated by 'crepIfPortRole'.