All MIBs › DC-RTM-MIB › rtmEntityUseUnidirectionalLinks
rtmEntityUseUnidirectionalLinks
Module: DC-RTM-MIB
OID (symbolic): DC-RTM-MIB::rtmEntityUseUnidirectionalLinks
OID (numeric): 1.2.826.0.1.1578918.5.61.1.1.1.1.39
Node type: OBJECT-TYPE
Type: TruthValue
Access: read-create
Description: Are unidirectional links usable for the FIB maintained by this instance of DC-RTM?
If set to 'false' then unidirectional interfaces reported over the I3 and IGP shortcuts reported over the RPI are discarded.
If set to 'true' then unidirectional interfaces can be used for next hops reported over the Active Routes Interface. Note in particular that IGP shortcuts through TE-tunnel next hops are reported over the Active Routes Interface in addition to native adjacency next hops.
If the active route consumers of this FIB cannot use unidirectional links then this field should be set to 'false'. An example of such an active route consumer is DC-PIM. Because DC-PIM uses paths for Reverse Path Forwarding, it cannot use unidirectional links.
If this field is changed while DC-RTM is active, DC-RTM deactivates and then reactivates in order to refresh all routing information.
OID Breakdown
Upper-level ancestors (2 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.2 | member_body | IEEE802dot11-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.2.826.0.1.1578918.5.61.1 | rtmMib | DC-RTM-MIB |
| 1.2.826.0.1.1578918.5.61.1.1 | rtmObjects | DC-RTM-MIB |
| 1.2.826.0.1.1578918.5.61.1.1.1 | rtmEntityTable | DC-RTM-MIB |
| 1.2.826.0.1.1578918.5.61.1.1.1.1 | rtmEntityEntry | DC-RTM-MIB |
| 1.2.826.0.1.1578918.5.61.1.1.1.1.39 | rtmEntityUseUnidirectionalLinks | DC-RTM-MIB |