CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB

All MIBs › CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2011-01-11

Category: Cisco Devices, VLAN and Bridging

Description: Manages REP (Resilient Ethernet Protocol) ring segment topology and failure recovery on Cisco switches.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB?

CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB manages Cisco's Resilient Ethernet Protocol (REP), a proprietary alternative to Spanning Tree Protocol that controls loops and speeds failure recovery within a ring or segment of switch ports. It exposes segment-level configuration (which two interfaces form the endpoints of a segment, preemption settings) and per-interface REP configuration, along with a notification branch for REP-related events and conformance groups. Its monitoring value is fault/topology-oriented: administrators check crepSegmentComplete to confirm a REP segment/ring is fully formed with no breaks, monitor crepSegmentPreemptStatus to see if manual or automatic preemption has altered the ring's blocking point, and rely on ciscoRepMIBNotifs traps to be alerted immediately to link failures or topology changes within the segment, which is critical since REP is often used for fast failover in place of STP. It depends on the standard IF-MIB ifIndex convention (crepIfIndex) to map REP configuration to physical interfaces. It is typically deployed on Cisco switches in ring topologies such as industrial, metro, or access-ring networks requiring sub-second failover. Network engineers researching Cisco Resilient Ethernet Protocol (REP) ring topology reference this MIB to monitor segment/port state via SNMP.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco switches configured for Resilient Ethernet Protocol (REP) rings

Monitoring Examples

An operator would poll crepSegmentTable / crepSegmentEntry keyed by crepSegmentId to check crepSegmentComplete, confirming the ring formed by crepSegmentInterface1 and crepSegmentInterface2 has no break, and check crepSegmentPreemptStatus for the current preemption state. A segment where crepSegmentComplete flips to false, especially accompanied by a ciscoRepMIBNotifs trap, indicates a link failure in the ring that triggered REP's failover mechanism.

What Can Be Monitored

REP segment completeness (ring integrity)
segment endpoint interfaces
preemption configuration and status
per-interface REP segment membership
REP topology-change notifications

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From CISCO-TC

CiscoVlanList

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero

From Q-BRIDGE-MIB

VlanId

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using crepLslRxPdus OID:

Select a Cisco switches configured for Resilient Ethernet Protocol (REP) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type crepLslRxPdus into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. This object indicates the number of link status layer PDUs received on the port. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoRepGlobalGroup	1.3.6.1.4.1.9.9.601.2.2.1			A collection of global objects for use with the REP feature.
ciscoRepInterfaceGroup	1.3.6.1.4.1.9.9.601.2.2.2			A collection of interface specific objects for use with the REP feature.
ciscoRepMIBCompliance	1.3.6.1.4.1.9.9.601.2.1.1			The compliance statement for CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB.
ciscoRepMIBCompliances	1.3.6.1.4.1.9.9.601.2.1
ciscoRepMIBConform	1.3.6.1.4.1.9.9.601.2
ciscoRepMIBGroups	1.3.6.1.4.1.9.9.601.2.2
ciscoRepMIBNotifs	1.3.6.1.4.1.9.9.601.0
ciscoRepMIBObjects	1.3.6.1.4.1.9.9.601.1
ciscoRepNotificationGroup	1.3.6.1.4.1.9.9.601.2.2.3			A collection of notifications for use with the REP feature.
ciscoRepSegmentGroup	1.3.6.1.4.1.9.9.601.2.2.4			A collection of segment specific objects for use with the REP feature.
ciscoResilientEthernetProtocolMIB	1.3.6.1.4.1.9.9.601			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.
VLA crepAdminVlan	1.3.6.1.4.1.9.9.601.1.1.2	VlanId	read-write	The administrative VLAN used by REP to transmit its hardware flooding layer messages. If the VLAN does not already exist, set operation does not create the VLAN. The administrative VLAN cannot be the RSPAN VLAN.
OCT crepBlockPortIdInfo	1.3.6.1.4.1.9.9.601.1.2.1.1.15	OCTET STRING	read-create	This object specifies the port identifier of the port in the segment to be blocked for VLAN load balancing. 'crepIfPortID' object of the corresponding port provides the port identifier. This value is only effective on the device acting as the REP primary edge and has relevance only if crepLoadBalanceBlockPortType = 'portId'.
I32 crepBlockPortNumInfo	1.3.6.1.4.1.9.9.601.1.2.1.1.14	Integer32	read-create	This object specifies the offset of the port in the segment to be blocked for VLAN load balancing. Positive numbers indicate the offset from the primary edge port and negative numbers indicates the downstream neighbor from the secondary edge port. [Sw E1]E1---NE1[Sw 1]NE2---NE1[Sw 2]NE2......... . . [Sw E2]E2---NE2[Sw N]NE1---NE2[Sw N-1]NE1....... Sw : Switch. E : Edge port. NE : Non-Edge port. E1/E2: Edge switches. E1 and E2 can either be same or different switches. In the segment depicted above, consider port E1 on 'Sw E1' is the primary edge and E2 on 'Sw E2' is the secondary edge. Value 1 for this object indicates primary edge port, 2 indicates NE1 on 'Sw 1', 3 indicates NE2 on 'Sw 1' and so on. Value -1 indicates secondary edge port, -2 indicates NE2 on 'Sw N', -3 indicates NE1 on 'Sw N' and so on. Usage of value 0 is invalid. This value is only effective on the device acting as the REP primary edge and has relevance only if crepLoadBalanceBlockPortType = 'offset'.
C32 crepBpaStcnHflRxPackets	1.3.6.1.4.1.9.9.601.1.2.2.1.10	Counter32	read-only	This object indicates the number of segment topology change notifications received as blocked port advertisement through hardware flood layer.
C32 crepBpaStcnHflTxPackets	1.3.6.1.4.1.9.9.601.1.2.2.1.11	Counter32	read-only	This object indicates the number of segment topology change notifications transmitted as blocked port advertisement through hardware flood layer.
C32 crepBpaStcnLslRxPackets	1.3.6.1.4.1.9.9.601.1.2.2.1.8	Counter32	read-only	This object indicates the number of segment topology change notifications received as blocked port advertisement through link status layer.
C32 crepBpaStcnLslTxPackets	1.3.6.1.4.1.9.9.601.1.2.2.1.9	Counter32	read-only	This object indicates the number of segment topology change notifications transmitted as blocked port advertisement through link status layer.
C32 crepBpaTlvRxPackets	1.3.6.1.4.1.9.9.601.1.2.2.1.6	Counter32	read-only	This object indicates the number of blocked port advertisement TLVs received on the port.
C32 crepBpaTlvTxPackets	1.3.6.1.4.1.9.9.601.1.2.2.1.7	Counter32	read-only	This object indicates the number of blocked port advertisement TLVs transmitted on the port.
TIM crepCounterDiscontinuityTime	1.3.6.1.4.1.9.9.601.1.2.2.1.1	TimeStamp	read-only	The value of sysUpTime on the most recent occasion at which REP counters suffered a discontinuity on this interface. If no such discontinuities have occurred since the first initialization of REP, then this object contains the sysUpTime value of first initialization.
C32 crepEpaCommandTlvRxPackets	1.3.6.1.4.1.9.9.601.1.2.2.1.14	Counter32	read-only	This object indicates the number of end port advertisement command TLVs received that are used to authorize a port to takeover the segment for the purpose of VLAN load balancing.
C32 crepEpaCommandTlvTxPackets	1.3.6.1.4.1.9.9.601.1.2.2.1.15	Counter32	read-only	This object indicates the number of end port advertisement command TLVs transmitted that are used to authorize a port to takeover the segment for the purpose of VLAN load balancing.
C32 crepEpaElectionTlvRxPackets	1.3.6.1.4.1.9.9.601.1.2.2.1.12	Counter32	read-only	This object indicates the number of end port advertisement election TLVs received that are used for determining the role, namely primary edge or secondary edge.
C32 crepEpaElectionTlvTxPackets	1.3.6.1.4.1.9.9.601.1.2.2.1.13	Counter32	read-only	This object indicates the number of end port advertisement election TLVs transmitted that are used for determining the role, namely primary edge or secondary edge.
C32 crepEpaInfoTlvRxPackets	1.3.6.1.4.1.9.9.601.1.2.2.1.16	Counter32	read-only	This object indicates the number of end port advertisement information TLVs received on the port. These messages are sent by the end ports (configured edge port, or port which is down or port which does not have internal peer) to discover the segment information.
C32 crepEpaInfoTlvTxPackets	1.3.6.1.4.1.9.9.601.1.2.2.1.17	Counter32	read-only	This object indicates the number of end port advertisement information TLVs transmitted on the port. These messages are sent by the end ports (configured edge port, or port which is down or port which does not have internal peer) to discover the segment information.
crepGlobalInfo	1.3.6.1.4.1.9.9.601.1.1
U32 crepGlobalRepNotifsRate	1.3.6.1.4.1.9.9.601.1.1.4	Unsigned32	read-write	This object specifies the maximum rate at which the system will generate notifications defined by this MIB module. If this object value is 0, then the system will not impose a limit on the rate at which it will generate notification defined by this MIB module.
C32 crepHflRxPdus	1.3.6.1.4.1.9.9.601.1.2.2.1.4	Counter32	read-only	This object indicates the number of hardware flood layer PDUs received on the port.
C32 crepHflTxPdus	1.3.6.1.4.1.9.9.601.1.2.2.1.5	Counter32	read-only	This object indicates the number of hardware flood layer PDUs transmitted on the port.
REP crepIfAdminEdgePortType	1.3.6.1.4.1.9.9.601.1.2.1.1.6	RepPortType	read-create	This object specifies the configured edge port type for the interface.
CIS crepifBlockedVlans1k	1.3.6.1.4.1.9.9.601.1.2.1.1.9	CiscoVlanList	read-create	This object specifies the list of VLANs configured to be blocked at the alternate port for VLANs with values of 0 through 1023. If the bit is set to '1', then the VLAN is marked for blocking. This value is only effective on the device acting as the REP primary edge. In addition, this value is effective only if 'crepLoadBalanceBlockPortType' is not 'none'.
CIS crepifBlockedVlans2k	1.3.6.1.4.1.9.9.601.1.2.1.1.10	CiscoVlanList	read-create	This object specifies the list of VLANs configured to be blocked at the alternate port for VLANs with values of 1024 through 2047. If the bit is set to '1', then the VLAN is marked for blocking. This value is only effective on the device acting as the REP primary edge. In addition, this value is effective only if 'crepLoadBalanceBlockPortType' is not 'none'. This object is only instantiated on devices that support the extended VLANs.
CIS crepifBlockedVlans3k	1.3.6.1.4.1.9.9.601.1.2.1.1.11	CiscoVlanList	read-create	This object specifies the list of VLANs configured to be blocked at the alternate port for VLANs with values of 2048 through 3071. If the bit is set to '1', then the VLAN is marked for blocking. This value is only effective on the device acting as the REP primary edge. In addition, this value is effective only if 'crepLoadBalanceBlockPortType' is not 'none'. This object is only instantiated on devices that support the extended VLANs.
CIS crepifBlockedVlans4k	1.3.6.1.4.1.9.9.601.1.2.1.1.12	CiscoVlanList	read-create	This object specifies the list of VLANs configured to be blocked at the alternate port for VLANs with values of 3072 through 4095. If the bit is set to '1', then the VLAN is marked for blocking. This value is only effective on the device acting as the REP primary edge. In addition, this value is effective only if 'crepLoadBalanceBlockPortType' is not 'none'. This object is only instantiated on devices that support the extended VLANs.
ROW crepIfConfigRowStatus	1.3.6.1.4.1.9.9.601.1.2.1.1.20	RowStatus	read-create	This object is used to manage the creation, deletion, and modification of rows in this table. A row may be created using the 'CreateAndGo' option. When the row is successfully created, the agent would set the RowStatus to 'active'. 'crepIfSegmentId' should be specified for the successful creation of the row. A row may be deleted by setting this object to 'destroy'. All writeable columns in this row can be modified when the value of this object is 'active'.
NUM crepIfIndex	1.3.6.1.4.1.9.9.601.1.2.1.1.1	InterfaceIndex	not-accessible	This object identifies the ifIndex-value assigned to the interface.
REP crepIfOperEdgePortType	1.3.6.1.4.1.9.9.601.1.2.1.1.7	RepPortType	read-only	This object indicates the actual edge port type for the interface. Value 'edge' indicates that the port is secondary edge port.
INT crepIfOperStatus	1.3.6.1.4.1.9.9.601.1.2.1.1.3	INTEGER	read-only	This object indicates the current operational link state of the REP port. If a REP configured interface is down, it will be in 'initDown' state. 'none' - REP is not operational on the interface. This value is used when sending the crepLinkStatus notification when REP configuration is removed from the interface. 'initDown' - initial REP link state. 'noNeighbor' - state in which REP is yet to discover its neighbor. 'oneWay' - the state in which messages have been received from the neighbor but the link has not been declared to be twoWay yet. 'twoWay' - the fully operational state for REP. 'flapping' - the state in which there is a mismatch in the received port information (either local or remote) for the neighbor. 'wait' - the forced transient state before REP starts discovering its neighbor. 'unknown' - the link state cannot be determined.
OCT crepIfPortID	1.3.6.1.4.1.9.9.601.1.2.1.1.5	OCTET STRING	read-only	This object indicates the REP port identifier automatically assigned by REP when enabled.
INT crepIfPortRole	1.3.6.1.4.1.9.9.601.1.2.1.1.4	INTEGER	read-only	This object indicates the role or state of a REP port depending on its link status and whether it is forwarding or blocking traffic. 'failedPort' - a port with a non-operational link status, such that no traffic is forwarded on it. 'alternatePort' - a port forwarding traffic only for a subset of VLANs, for the purpose of VLAN load balancing. 'openPort' - a port forwarding traffic for all VLANs. 'failedPortNoNeighbor' - a port with a non-operational link status and does not have a external neighbor. 'failedPortLogicalOpen' - a port with a non-operational link status and does not have a external neighbor but is in forwarding state for traffic.
I32 crepIfPreemptDelayTimer	1.3.6.1.4.1.9.9.601.1.2.1.1.16	Integer32	read-create	This object specifies the interval of time that REP waits before triggering preemption after the segment is complete. The value -1 is used to indicate that no time delay is configured and the preemption will happen manually. This value is only effective on the device acting as the REP primary edge.
T/F crepIfPreferredConfig	1.3.6.1.4.1.9.9.601.1.2.1.1.8	TruthValue	read-create	This object specifies if port should get preference to become the alternate port among other equal ports in the segment. Setting this value to true does not guaranty that the port will become the alternate port. 'crepIfPortRole' should be checked for the actual status.
REP crepIfSegmentId	1.3.6.1.4.1.9.9.601.1.2.1.1.2	RepSegmentId	read-create	This object specifies the segment that the interface is part. This object can be modified when crepIfConfigRowStatus is 'active'. The valid range is from crepMinSegmentId to crepMaxSegmentId.
NUM crepIfStcnPropagateToIf	1.3.6.1.4.1.9.9.601.1.2.1.1.19	InterfaceIndexOrZero	read-create	This object specifies the interface to which the REP edge should propagate the segment topology change notifications. The interface should be of type ifType = 'ethernetCsmacd' or an ethernet based virtual port with ifType = 'propVirtual'. '0' specifies that the device should not propagate STCNs to any interface. This value is only effective on the device acting as the REP primary edge.
REP crepIfStcnPropagateToOtherSegs	1.3.6.1.4.1.9.9.601.1.2.1.1.18	RepSegmentList	read-create	This object specifies the list of segments to which the REP edge propagates the segment topology change notifications. This value is only effective on the device acting as the REP primary edge.
T/F crepIfStcnPropagateToSTP	1.3.6.1.4.1.9.9.601.1.2.1.1.17	TruthValue	read-create	This object specifies if the REP edge propagates the segment topology change notifications to the spanning tree network. This value is only effective on the device acting as the REP primary edge.
crepInterfaceConfig	1.3.6.1.4.1.9.9.601.1.2
crepInterfaceConfigEntry	1.3.6.1.4.1.9.9.601.1.2.1.1		not-accessible	An entry exists for each interface, if REP is configured on it. On a system that supports REP, all ports with ifType = 'ethernetCsmacd' and those ethernet based virtual ports with ifType = 'propVirtual' also support REP. REP can be configured or unconfigured or modified directly on the agent as well. Dynamically created rows are expected to be non-volatile such that they persist after an agent restarts.
crepInterfaceConfigTable	1.3.6.1.4.1.9.9.601.1.2.1		not-accessible	This table provides REP configuration for interfaces in the device. This table contains one entry for each interface running REP.
crepInterfaceStatsEntry	1.3.6.1.4.1.9.9.601.1.2.2.1		not-accessible	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.
crepInterfaceStatsTable	1.3.6.1.4.1.9.9.601.1.2.2		not-accessible	A table for REP interfaces statistics. This table augments the crepInterfaceConfigTable.
NTF crepLinkStatus	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.
INT crepLoadBalanceBlockPortType	1.3.6.1.4.1.9.9.601.1.2.1.1.13	INTEGER	read-create	This object specifies the method defined to identify the alternate port in the segment that takes part in VLAN load balancing by blocking a subset of VLANs after preemption. 'none' - no method is specified to identify the alternate port. In this case, the primary edge blocks all VLANs after preemption. 'offset' - identification is done by a number which indicates the offset of the port from an edge port. 'crepBlockPortNumInfo' defines the value. 'portId' - identification is done by the port identifier of the port. 'crepBlockPortIdInfo' defines the value. 'prefFlag' - to select the port in the segment that is configured as the preferred alternate port for VLAN load balancing. While setting the value to 'offset' or 'portId', corresponding values for the value defining objects (mentioned along with the corresponding descriptions above) should also be provided, along with. Additionally, at least one of objects that define the VLANs to be blocked (crepifBlockedVlans1k, crepifBlockedVlans2k, crepifBlockedVlans3k, crepifBlockedVlans4k) should be provided with a non-empty value, when setting the value to anything other than 'none'. This value is only effective on the device acting as the REP primary edge.
C32 crepLslRxPdusEx	1.3.6.1.4.1.9.9.601.1.2.2.1.2	Counter32	read-only	This object indicates the number of link status layer PDUs received on the port.
C32 crepLslTxPdus	1.3.6.1.4.1.9.9.601.1.2.2.1.3	Counter32	read-only	This object indicates the number of link status layer PDUs transmitted on the port.
REP crepMaxSegmentId	1.3.6.1.4.1.9.9.601.1.1.6	RepSegmentId	read-only	This object indicates the maximum segment identifier that can be configured on the device.
REP crepMinSegmentId	1.3.6.1.4.1.9.9.601.1.1.5	RepSegmentId	read-only	This object indicates the minimum segment identifier that can be configured on the device.
T/F crepNotifsEnable	1.3.6.1.4.1.9.9.601.1.1.3	TruthValue	read-write	This object specifies whether the system will generate REP notifications. This object affects the generation of all REP notifications defined in this MIB module.
NTF crepPortRoleChange	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'.
NTF crepPreemptionStatus	1.3.6.1.4.1.9.9.601.0.2			This notification indicates the status of the preemption triggered on REP primary edge.
T/F crepSegmentComplete	1.3.6.1.4.1.9.9.601.1.3.1.1.4	TruthValue	read-only	This object indicates if the segment is complete such that no port in the segment is in failed state.
crepSegmentConfig	1.3.6.1.4.1.9.9.601.1.3
crepSegmentEntry	1.3.6.1.4.1.9.9.601.1.3.1.1		not-accessible	A list of REP segment entries. The number of segments configured on the device determines the number of entries. An entry is created when a segment identifier value is configured on an interface and no matching entry exists already. The entry is deleted once the segment ceases to exist on the device.
REP crepSegmentId	1.3.6.1.4.1.9.9.601.1.3.1.1.1	RepSegmentId	not-accessible	This object identifies the segment identifier.
NUM crepSegmentInterface1	1.3.6.1.4.1.9.9.601.1.3.1.1.2	InterfaceIndex	read-only	This object indicates the ifIndex-value assigned to the first interface that is part of the segment.
NUM crepSegmentInterface2	1.3.6.1.4.1.9.9.601.1.3.1.1.3	InterfaceIndexOrZero	read-only	This object indicates the ifIndex-value assigned to the second interface that is part of the segment. The value of zero means that the InterfaceIndex is not known. The reasons for value being zero might include the second interface might not yet been configured for this segment and the device may be the edge of the segment.
T/F crepSegmentPreempt	1.3.6.1.4.1.9.9.601.1.3.1.1.5	TruthValue	read-write	This object should be set to true by NMS for triggering manual preemption. This may cause a momentary traffic disruption. Though this can be done for any node in the segment, it is only effective on the device acting as the REP primary edge. Setting this object false has no effect. This object always returns false when read.
INT crepSegmentPreemptStatus	1.3.6.1.4.1.9.9.601.1.3.1.1.6	INTEGER	read-only	This object indicates the status of the last preemption trigger. 'none' - preemption trigger is not executed. 'preemptSuccessful' - preemption action for the previous trigger is successful. 'preemptFailure' - preemption trigger was successful. However, preemption failed due to some problem on the segment. 'preemptTrigger' - preemption is triggered successfully and the result is awaited. 'preemptTriggerFailure'- preemption on the segment is not performed as the preemption trigger failed. The failure could be due to invalid port ID or neighbor number specified in 'crepBlockPortNumInfo' or 'crepBlockPortIdInfo' respectively, when the value of 'crepLoadBalanceBlockPortType' is 'offset' or 'portId' respectively. In addition, reason for failure can be that crepLoadBalanceBlockPortType = 'prefFlag' and there is no REP port in the segment configured as preferred port. The value should be 'none' on all agents other than the one serving as the primary edge for the segment. The value will be 'none' on the agent serving as the primary edge for the segment if preemption trigger is not executed yet. If the device is not capable of assessing the final outcome of preemption trigger, then the state should remain in 'preemptTrigger' state.
crepSegmentTable	1.3.6.1.4.1.9.9.601.1.3.1		not-accessible	This table specifies REP segments configured on the device.
I32 crepVersion	1.3.6.1.4.1.9.9.601.1.1.1	Integer32	read-only	This object indicates the version of REP being used.

RFC description

Manages Resilient Ethernet Protocol (REP) for network loop prevention and fault recovery on Cisco switches.

Start monitoring Cisco switches configured for Resilient Ethernet Protocol (REP) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB