crepSegmentPreemptStatus

• 1.3.6.1.4.1.9.9.601.1.3.1.1.6
• Access readonly
• Type none(1), preemptSuccessful(2), preemptFailure(3), preemptTrigger(4), preemptTriggerFailure(5) ?

  none(1), preemptSuccessful(2), preemptFailure(3), preemptTrigger(4), preemptTriggerFailure(5)

  This type is not a standard SMI/SNMP base type and is not defined as a documented TEXTUAL-CONVENTION in this MIB.

  It was extracted as raw syntax from the source MIB file and could not be resolved to a known type definition.

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.