CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB :: crepSegmentPreemptStatus

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-RESILIENT-ETHERNET-PROTOCOL-MIBcrepSegmentPreemptStatus

crepSegmentPreemptStatus

Module: CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB

OID (symbolic): CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB::crepSegmentPreemptStatus

OID (numeric): 1.3.6.1.4.1.9.9.601.1.3.1.1.6

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: 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.

What is crepSegmentPreemptStatus?

Read-only status reporting the outcome of the last preemption trigger for the REP segment, such as none, successful, or failed.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.601.1.3.1.1.6
snmpwalk -v2c -c public <target> CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB::crepSegmentPreemptStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.601.1.3.1.1.6.1
snmpget -v2c -c public <target> CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB::crepSegmentPreemptStatus.1

Start monitoring Cisco switches configured for Resilient Ethernet Protocol (REP) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB::crepSegmentPreemptStatus OID value, configure state conditions and alerts, and monitor any Cisco switches configured for Resilient Ethernet Protocol (REP) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.601ciscoResilientEthernetProtocolMIBCISCO-RESILIENT-ETHERNET-PROTOCOL-MIB
1.3.6.1.4.1.9.9.601.1ciscoRepMIBObjectsCISCO-RESILIENT-ETHERNET-PROTOCOL-MIB
1.3.6.1.4.1.9.9.601.1.3crepSegmentConfigCISCO-RESILIENT-ETHERNET-PROTOCOL-MIB
1.3.6.1.4.1.9.9.601.1.3.1crepSegmentTableCISCO-RESILIENT-ETHERNET-PROTOCOL-MIB
1.3.6.1.4.1.9.9.601.1.3.1.1crepSegmentEntryCISCO-RESILIENT-ETHERNET-PROTOCOL-MIB
1.3.6.1.4.1.9.9.601.1.3.1.1.6crepSegmentPreemptStatusCISCO-RESILIENT-ETHERNET-PROTOCOL-MIB