OID reference

fsBfdSessRole

1.3.6.1.4.1.29601.2.53.2.1.1.1

Description

This object specifies whether the system is playing the active(1) role or the passive(2) role for this BFD session. BFD session will not come up if both the ends of a path are configured to be passive. In case of MPLS and MPLS-TP LSP, it is expected to configure the BFD session in the ingress of the LSP as Active. Eve…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.29601.2.53.2.1.1 (fsBfdSessionEntry)
Node code
1
Node name
fsBfdSessRole
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.29601.2.53.2.1.1.1
URN notation
urn:oid:1.3.6.1.4.1.29601.2.53.2.1.1.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 29601 2 53 2 1 1 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 fsBfd(53) fsBfdObjects(2) fsBfdSessionTable(1) fsBfdSessionEntry(1) fsBfdSessRole(1)}
OID-IRI notation
  • /1/3/6/1/4/1/29601/2/53/2/1/1/1
  • /ISO/Identified-Organization/6/1/4/1/29601/2/53/2/1/1/1
  • /ISO/3/6/1/4/1/29601/2/53/2/1/1/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/identified-organization/dod/internet/private/enterprises/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/identified-organization/dod/internet/private/vendor-objects/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/org/dod/internet/private/enterprise/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/org/dod/internet/private/enterprises/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/org/dod/internet/private/ldap-enterprise/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/org/dod/internet/private/vendor-objects/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/iso-identified-organization/dod/internet/private/enterprise/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/iso-identified-organization/dod/internet/private/enterprises/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/iso-organization/dod/internet/private/enterprise/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/iso-organization/dod/internet/private/enterprises/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole
  • /iso/iso-organization/dod/internet/private/vendor-objects/29601/2/fsBfd/fsBfdObjects/fsBfdSessionTable/fsBfdSessionEntry/fsBfdSessRole

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-create
Status in MIB
current
Default value
active

Enumerated values

ValueName
1active
2passive

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published AUGMENTS row: bfdSessEntry. Check that row's index definition for the instance suffix.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.29601.2.53.2.1.1.1

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

fsBfdSessRole  OBJECT-TYPE
        SYNTAX      INTEGER {
                      active(1),
                      passive(2)
                    }
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION
          "This object specifies whether the system is playing the 
           active(1) role or the passive(2) role for this BFD session.
           BFD session will not come up if both the ends of a path are
           configured to be passive. In case of MPLS and MPLS-TP LSP, 
           it is expected to configure the BFD session in the 
           ingress of the LSP as Active. Even in the case of static 
           provisioning of discriminators, it is recommended to 
           configure the BFD session as Active at the ingress and 
           as Passive at the egress. In the case of PW, BFD session
           at both the ends should be Active." 
        REFERENCE
            "RFC 5880, Section 6.1"
        DEFVAL { active }
    ::= { fsBfdSessionEntry 1 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

This object specifies whether the system is playing the active(1) role or the passive(2) role for this BFD session. BFD session will not come up if both the ends of a path are configured to be passive. In case of MPLS and MPLS-TP LSP, it is expected to configure the BFD session in the ingress of the LSP as Active. Even in the case of static provisioning of discriminators, it is recommended to configure the BFD session as Active at the ingress and as Passive at the egress. In the case of PW, BFD session at both the ends should be Active.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 1

fsBfdSessRole · currentBelden, GarrettCom and Hirschmann IT official standalone MIBs1 source

Status in source: current.

Names: fsBfdSessRole

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsBfdSessRole",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "active",
    "(",
    "1",
    ")",
    ",",
    "passive",
    "(",
    "2",
    ")",
    "}",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object specifies whether the system is playing the active(1) role or the passive(2) role for this BFD session. BFD session will not come up if both the ends of a path are configured to be passive. In case of MPLS and MPLS-TP LSP, it is expected to configure the BFD session in the ingress of the LSP as Active. Even in the case of static provisioning of discriminators, it is recommended to configure the BFD session as Active at the ingress and as Passive at the egress. In the case of PW, BFD session at both the ends should be Active.\"",
    "REFERENCE",
    "\"RFC 5880, Section 6.1\"",
    "DEFVAL",
    "{",
    "active",
    "}",
    "::=",
    "{",
    "fsBfdSessionEntry",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "active",
            1
          ],
          [
            "passive",
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object specifies whether the system is playing the active(1) role or the passive(2) role for this BFD session. BFD session will not come up if both the ends of a path are configured to be passive. In case of MPLS and MPLS-TP LSP, it is expected to configure the BFD session in the ingress of the LSP as Active. Even in the case of static provisioning of discriminators, it is recommended to configure the BFD session as Active at the ingress and as Passive at the egress. In the case of PW, BFD session at both the ends should be Active."
    ],
    [
      "REFERENCE",
      "RFC 5880, Section 6.1"
    ],
    null,
    null,
    [
      "DEFVAL",
      "active"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.29601)

Arpna Gupta

Siblings (12)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.29601.2.53.2.1.1.2 fsBfdSessMode00
1.3.6.1.4.1.29601.2.53.2.1.1.3 fsBfdSessRemoteDiscr00
1.3.6.1.4.1.29601.2.53.2.1.1.4 fsBfdSessEXPValue00
1.3.6.1.4.1.29601.2.53.2.1.1.5 fsBfdSessTmrNegotiate00
1.3.6.1.4.1.29601.2.53.2.1.1.6 fsBfdSessOffld00
1.3.6.1.4.1.29601.2.53.2.1.1.7 fsBfdSessEncapType00
1.3.6.1.4.1.29601.2.53.2.1.1.8 fsBfdSessAdminCtrlReq00
1.3.6.1.4.1.29601.2.53.2.1.1.9 fsBfdSessAdminCtrlErrReason00
1.3.6.1.4.1.29601.2.53.2.1.1.10 fsBfdSessMapType00
1.3.6.1.4.1.29601.2.53.2.1.1.11 fsBfdSessMapPointer00
1.3.6.1.4.1.29601.2.53.2.1.1.12 fsBfdSessCardNumber00
1.3.6.1.4.1.29601.2.53.2.1.1.13 fsBfdSessSlotNumber00