OID reference
1.3.6.1.3.114.1.1.1.11
If the link is unnumbered, the outgoing interface identifier is set to the outgoing interface identifier chosen for the TE link by the advertising LSR.
Identification
{1 3 6 1 3 114 1 1 1 11}
Definitions may combine these properties differently.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Available source records contain 2 distinct definitions; some records may not include a definition.
Extracted from a source document.
teLinkFlooding OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object only has significance for link bundles which
encoding type is not clear. For these link bundles, this object
identifies the TE link on which to restrict flooding. If the
value is zero, then flooding must be done on all TE links
within the link bundle."
REFERENCE
"draft-ietf-ospf-isis-flood-opt-01.txt - Flooding optimization
in link-state routing protocols, A. Zinin, M. Shand,
March 2001."
DEFVAL { 0 }
::= { teLinkEntry 11 }Extracted from a source document.
teLinkFlooding OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object only has significance for link bundles which
encoding type is not clear. For these link bundles, this object
identifies the TE link on which to restrict flooding. If the
value is zero, then flooding must be done on all TE links
within the link bundle."
REFERENCE
"[FLOOD]"
DEFVAL { 0 }
::= { teLinkEntry 11 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
Parsed from LINK-BUNDLING-MIB-mpls-00.txt · ietf_drafts · LINK-BUNDLING-MIB
Source file: Download LINK-BUNDLING-MIB-mpls-00.txt
Description 2
This object only has significance for link bundles which encoding type is not clear. For these link bundles, this object identifies the TE link on which to restrict flooding. If the value is zero, then flooding must be done on all TE links within the link bundle.
IETF historical Internet-Draft definitions
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: teLinkFlooding
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"teLinkFlooding",
"OBJECT-TYPE",
"SYNTAX",
"InterfaceIndexOrZero",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"This object only has significance for link bundles which encoding type is not clear. For these link bundles, this object identifies the TE link on which to restrict flooding. If the value is zero, then flooding must be done on all TE links within the link bundle.\"",
"REFERENCE",
"\"draft-ietf-ospf-isis-flood-opt-01.txt - Flooding optimization in link-state routing protocols, A. Zinin, M. Shand, March 2001.\"",
"DEFVAL",
"{",
"0",
"}",
"::=",
"{",
"teLinkEntry",
"11",
"}"
],
"syntax_tree": [
[
"row",
"InterfaceIndexOrZero"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object only has significance for link bundles which encoding type is not clear. For these link bundles, this object identifies the TE link on which to restrict flooding. If the value is zero, then flooding must be done on all TE links within the link bundle."
],
[
"REFERENCE",
"draft-ietf-ospf-isis-flood-opt-01.txt - Flooding optimization in link-state routing protocols, A. Zinin, M. Shand, March 2001."
],
null,
null,
[
"DEFVAL",
0
]
]
}Module: LINK-BUNDLING-MIB
See published definition above
{'IF-MIB': ['InterfaceIndexOrZero', 'ifIndex'], 'OSPF-MIB': ['RouterID'], 'SNMPv2-TC': ['TruthValue', 'RowStatus', 'StorageType'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'experimental', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}Source data warning: Historical Internet-Draft draft-ietf-mpls-bundle-mib-03; current Datatracker states: Replaced, Dead, WG Document. An Internet-Draft is not an RFC or proof of final registration. Its numbers and descriptions may be provisional or obsolete; the SMI STATUS field describes the source object, not the publication status. Consult the exact draft and the relevant device or protocol edition.
· Download draft-ietf-mpls-bundle-mib-03 — Link Bundling Management Information BaseRelated source files and packages:
Status in source: current.
Names: teLinkFlooding
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"teLinkFlooding",
"OBJECT-TYPE",
"SYNTAX",
"InterfaceIndexOrZero",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"This object only has significance for link bundles which encoding type is not clear. For these link bundles, this object identifies the TE link on which to restrict flooding. If the value is zero, then flooding must be done on all TE links within the link bundle.\"",
"REFERENCE",
"\"[FLOOD]\"",
"DEFVAL",
"{",
"0",
"}",
"::=",
"{",
"teLinkEntry",
"11",
"}"
],
"syntax_tree": [
[
"row",
"InterfaceIndexOrZero"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object only has significance for link bundles which encoding type is not clear. For these link bundles, this object identifies the TE link on which to restrict flooding. If the value is zero, then flooding must be done on all TE links within the link bundle."
],
[
"REFERENCE",
"[FLOOD]"
],
null,
null,
[
"DEFVAL",
0
]
]
}Module: LINK-BUNDLING-MIB
See published definition above
{'IF-MIB': ['InterfaceIndexOrZero', 'ifIndex'], 'OSPF-MIB': ['RouterID'], 'SNMPv2-TC': ['TruthValue', 'RowStatus', 'StorageType'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'mib-2', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}Source data warning: Historical Internet-Draft draft-ietf-mpls-bundle-mib-04; current Datatracker states: Replaced, Dead, WG Document. An Internet-Draft is not an RFC or proof of final registration. Its numbers and descriptions may be provisional or obsolete; the SMI STATUS field describes the source object, not the publication status. Consult the exact draft and the relevant device or protocol edition.
Source data warning: Qualified interim interpretation: this draft leaves the permanent root as { mib-2 xxx }, but explicitly says experimental 114 can be used in the interim. The earlier -03 draft independently declares that experimental root. This record follows only that published experimental alternative; no permanent mib-2 allocation is inferred. The original unassigned clause and both editions remain available.
· Download draft-ietf-mpls-bundle-mib-04 — Link Bundling Management Information BaseRelated source files and packages:
Historical records
teLinkOutgoingIfId OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If the link is unnumbered, the outgoing interface identifier is
set to the outgoing interface identifier chosen for the TE link
by the advertising LSR."
REFERENCE
"draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
February 2001."
::= { teLinkEntry 11 }
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.3.114.1.1.1.1 | teLinkNumberingType, teLinkIpAddrType | 0 | 0 | The TE link identifier type (numbered or unnumbered). |
| 1.3.6.1.3.114.1.1.1.2 | teLinkIpAddrType, teLinkIpAddr | 0 | 0 | Indicates whether the TE link address is IPv4 or IPv6 (numbered link). |
| 1.3.6.1.3.114.1.1.1.3 | teLinkIpAddr, teLinkRemoteIpAddr | 0 | 0 | For numbered links, this object represents the IP address associated with the TE link. |
| 1.3.6.1.3.114.1.1.1.4 | teLinkRemoteIpAddr, teLinkMetric | 0 | 0 | The remote IP address associated with the TE link (numbered links). |
| 1.3.6.1.3.114.1.1.1.5 | teLinkMetric, teLinkMuxCapability | 0 | 0 | The traffic engineering metric for the TE link is derived from its data-bearing channels. All data-bearing channels within the TE… |
| 1.3.6.1.3.114.1.1.1.6 | teLinkMuxCapability, teLinkProtectionType | 0 | 0 | This attribute specifies link multiplex capability of the TE link, which is derived from its data-bearing channels. All data-bear… |
| 1.3.6.1.3.114.1.1.1.7 | teLinkProtectionType, teLinkWorkingPriority | 0 | 0 | This attribute specifies link protection type of the TE link. |
| 1.3.6.1.3.114.1.1.1.8 | teLinkWorkingPriority, teLinkResourceClass | 0 | 0 | This object represents a priority value such that a new connection with a higher priority, i.e. numerically lower than this value… |
| 1.3.6.1.3.114.1.1.1.9 | teLinkResourceClass, teLinkIncomingIfId | 0 | 0 | This attribute specifies the TE link resource class. The resource class is a 32 bit bitfield. The resource class for a link bundl… |
| 1.3.6.1.3.114.1.1.1.10 | teLinkIncomingIfId, teLinkOutgoingIfId | 0 | 0 | For unnumbered links, the incoming interface is set to the outgoing interface identifier chosen by the neighboring LSR for the re… |
| 1.3.6.1.3.114.1.1.1.12 | teLinkFlooding, teLinkRowStatus | 0 | 0 | This object only has significance for link bundles which encoding type is not clear. For these link bundles, this object identifi… |
| 1.3.6.1.3.114.1.1.1.13 | teLinkRowStatus, teLinkStorageType | 0 | 0 | This variable is used to create, modify, and/or delete a row in this table. |
| 1.3.6.1.3.114.1.1.1.14 | teLinkStorageType | 0 | 0 | This variable indicates the storage type for this object. |