CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB-----B - crepSegmentPreemptStatus

MIBs list

With IPHost Network Monitor you can run simple snmp requests against a Cisco device in your network.

crepSegmentPreemptStatus

crep Segment Preempt Status
1.3.6.1.4.1.9.9.601.1.3.1.1.6

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.

Back to CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB-----B MIB page.

IPHost Network monitor allows you to monitor crepSegmentPreemptStatus on Cisco device via the SNMP protocol. Download IPHost Network Monitor (500 monitors for 30 days, 50 monitors free forever) to start monitoring Cisco wireless switches right now.

Easy monitoring of crepSegmentPreemptStatus with IPHost tools

MIBs list