fsMplsSimulateFailure

This object is for Testing purpose. 
If the object is set to testBandwidthReservationFailure (1)
         then the bandwidth reservation will fail 
         irrespective of Available bandwidth.
If the object is set to testClassTypeZero (2)
         then the path message will carry the class Type object
         of type zero.
If the object is set to testNoLabelRequest (3)
         then the path message will not have Label Request
         object.
If the object is set to testNoSessionObject (4)
         then the path message will not contain Session Object 
         sessiontype.
If the object is set to testUnknownCNumForClassType (5)
          then the path message will have unknown C Num in class
          Type object.
If the object is set to testUnknownCTypeForClassType (6)
          then the path message will have unknown C Type in class
          Type object.
If the object is set to testMultipleClassType (7),
           then the path message will have multiple class Type
           objects.
If the object is set to testLspTnlIfIdClassType1 (8),
           then the paths message will have the LSP_TNL_IF_ID
           of class type 1.
If the object is set to testNoRestartCapObj (9),
           then the hello message will not have restart cap object.
If the object is set to testNoILMEntries (10),
           then the node will remove the forwarding table when it
           is restarted.
If the object is set to testNoSuggestedLblObj (11),
           then the path message will not have suggested label object.
If the object is set to testNoSuggestedLbl (12),
           Then the path message will have invalid suggested label in
           suggested label object.
If the object is set to testNoRBitInCapabilityObj (13),
           Then the hello message will have R bit - 0 
           in capability object. 
If the object is set to  testNoAckMsg (14),
           Then Ack message will not be sent after receiving the RSVP messages.
If the object is set to  testNoAckMsg (15),
           Then Nack message will be sent after receiving the RSVP messages.
If the object is set to testRestartTime (16),
           Then hello message will have capability object with restart time 0.
If the object is set to testRecoveryTime (17),
           Then hello message will have capability object with recovery time 0.
If the object is set to testLdpMplsFwdStateLost (18),
            Then Recover Time Fault Tolerance Session TLV of Initialization 
            message will be filled with zero.
If the object is set to testLdpSendNewLbl (19),
            Then the helper node will send the different label upon 
            Graceful Restart.
If the object is set to testLdpBlockLblMap (20),
             Then the Label mapping message will not be sent.
If the object is set to testLdpQueueFull (21),
             Then the scenario of LDP Queue will be simulated.
If the object is set to testNoSupportForCrLspFecTlv (22),
             Then FEC for CRLSP will not be supported.
If the object is set to testNoSupportForDODLabelDistMethod (23),
             Then DownstreamonDemand mode of Label Distribution will not be 
             supported.
If the object is set to testNoSupportForDULabelDistMethod (24),
             Then DownstreamUnSolicited mode of Label Distribution will not be 
             supported.
If the object is set to testLdpMaxPduLengthAs500 (25),
             Then PDU Size will be set to exact 500. Anything above or below   
             will not be supported.
If the obejct is set to testLdpLblMrgCapable (26),
             Then Label merge capability is enabled in the LSR.
If the obejct is set to testLdpLblReqMrgCapable (27),             
             Then Label Request merge capability is enabled in the LSR
If the obejct is set to testLdpEnableWildCardFec (28),
             Then LSR will send label release/label withdraw message
             with wildcard fec. 
If the obejct is set to testLdpPropagateLblRelMsg (29),
             Then intermediate LSR will forward the received label release
             message.
If the obejct is set to testLdpPropagateLblAbrtReqMsg (30),
             Then intermediate LSR will forward the received label abort
             request message. 
If the obejct is set to testLdpDisableProxyEgress (31),
             Then the LSR will not act as proxy egress.
If the obejct is set to testNoSupportForGenFecTlv (32),
             Then GEN FEC will not be supported.
If the obejct is set to testWrongCBitStatusCode (33)
             Then wrong c bit status code will be set as
             0x20000002 as per RFC 4906
If the obejct is set to testLdpL2vpnEnableWildCardFec (34),
           Then LSR will send label release/label withdraw message
           with wildcard fec for targetted session.
If the object is set to testPwControlWordMandatory (35),
           Packet will be sent with PW-Control word.
If the object is set to testLdpAcceptLblMapForSamePrefixAndNextHop (36),
           LSR will also accept the label mapping message when both
           FEC and Nexthop are same.
If the object is set to testL2vpnEnableWdrawNotSupport (37),
           LSR does not support Label Withdraw method

MIB

SUPERMICRO-MPLS-MIB

OID

.1.3.6.1.4.1.10876.101.1.13.1.9.1

Type

scalar

Access

readwrite

Status

current

Parent

fsMplsTestObjects

Siblings

4