OID reference

bgpPeerConfAltLocalAs

1.2.826.42.1.1578918.5.65.1.3.1.1.1.96

Description

An alternative local AS number that can be used to establish a session with this peer. This is used when merging two ASs into a single AS. A value of zero means 'not configured'. If an alternative local AS number is configured then the peering session can be established using the alternative local AS instead of the pr…

Full description and source information

Identification

Identifier and names

Parent
1.2.826.42.1.1578918.5.65.1.3.1.1.1 (bgpPeerEntry)
Node code
96
Node name
bgpPeerConfAltLocalAs
Category
SNMP management object
Numeric OID
1.2.826.42.1.1578918.5.65.1.3.1.1.1.96
URN notation
urn:oid:1.2.826.42.1.1578918.5.65.1.3.1.1.1.96
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 2 826 42 1 1578918 5 65 1 3 1 1 1 96}

  • {iso(1) member-body(2) gb(826) 42 1 1578918 5 65 bgpMib(1) bgpPeer(3) bgpPeerData(1) bgpPeerTable(1) bgpPeerEntry(1) bgpPeerConfAltLocalAs(96)}
  • {iso(1) memberBody(2) gb(826) 42 1 1578918 5 65 bgpMib(1) bgpPeer(3) bgpPeerData(1) bgpPeerTable(1) bgpPeerEntry(1) bgpPeerConfAltLocalAs(96)}
OID-IRI notation
  • /1/2/826/42/1/1578918/5/65/1/3/1/1/1/96
  • /ISO/Member-Body/GB/42/1/1578918/5/65/1/3/1/1/1/96
  • /ISO/Member-Body/826/42/1/1578918/5/65/1/3/1/1/1/96
  • /ISO/2/826/42/1/1578918/5/65/1/3/1/1/1/96
Named path variants
  • /iso/member-body/gb/42/1/1578918/5/65/bgpMib/bgpPeer/bgpPeerData/bgpPeerTable/bgpPeerEntry/bgpPeerConfAltLocalAs
  • /iso/memberBody/gb/42/1/1578918/5/65/bgpMib/bgpPeer/bgpPeerData/bgpPeerTable/bgpPeerEntry/bgpPeerConfAltLocalAs

SNMP properties

Value type
BgpAutonomousSystemNumber
Maximum access defined by MIB
read-create
Status in MIB
current
Default value
0

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.

bgpPeerConfAltLocalAs OBJECT-TYPE
    SYNTAX      BgpAutonomousSystemNumber
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION "An alternative local AS number that can be used to
                 establish a session with this peer.  This is used when
                 merging two ASs into a single AS.

                 A value of zero means 'not configured'.

                 If an alternative local AS number is configured then the
                 peering session can be established using the alternative
                 local AS instead of the primary local AS number specified
                 by bgpRmEntLocalAs.

                 Setting an alternative local AS number allows the primary
                 local AS number to be changed without reconfiguring the
                 peer at the same time.  Later the peer can be reconfigured
                 to establish the session using the new remote AS number
                 and the alternative local AS number can be reset to zero.

                 An alternative local AS number should only be used as an
                 intermediate step on one side of a BGP session.  Do not
                 configure an alternative local AS number on both sides of
                 a BGP session - configure the correct remote AS numbers
                 instead.

                 If this is an IBGP peer then bgpPeerRemoteAs must have the
                 same value as bgpRmEntLocalAs.  In this case the IBGP
                 session can be established using either
                 bgpRmEntLocalAs/bgpPeerRemoteAs or bgpPeerConfAltLocalAs.

                 If this is an EBGP peer then bgpPeerRemoteAs must specify
                 the remote peer's AS number, and bgpRmEntLocalAs,
                 bgpPeerConfAltLocalAs and bgpPeerRemoteAs must all be
                 different.  In this case the EBGP session can be
                 established using bgpRmEntLocalAs or bgpPeerConfAltLocalAs
                 as the local AS number, but the remote AS number must
                 match bgpPeerRemoteAs.

                 The bgpPeerConfAltLocalAsMode field controls detailed
                 operation of the alternative local AS number, including
                 whether the peering session can be established using
                 bgpRmEntLocalAs or only using bgpPeerConfAltLocalAs.

                 Use of alternative local AS numbers is not supported if
                 the router is a member of a confederation.

                 The constraints explained above mean that this field is
                 only used if the following conditions are all met:
                 -  bgpRmEntConfederationId = 0
                 -  bgpPeerConfAltLocalAs != 0
                 -  bgpPeerConfAltLocalAs != bgpRmEntLocalAs
                 -  bgpPeerConfAltLocalAs != bgpPeerRemoteAs.

                 This field can be changed at any time.  However, if the
                 field is changed while the peer is admin_status UP, the
                 change will only take effect after the peer has been
                 cycled admin_status DOWN and then UP, thus forcing the
                 peer session to be restarted.  In this case, until the
                 peer is set admin_status DOWN, the peer will be marked as
                 out of date (as reported by the config_state field in the
                 AMB_BGP_PEER_STATUS row for the peer)."
    DEFVAL      { 0 }
    ::= { bgpPeerEntry 96 }

Meaning

Descriptions

1 unique

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

An alternative local AS number that can be used to establish a session with this peer. This is used when merging two ASs into a single AS. A value of zero means 'not configured'. If an alternative local AS number is configured then the peering session can be established using the alternative local AS instead of the primary local AS number specified by bgpRmEntLocalAs. Setting an alternative local AS number allows the primary local AS number to be changed without reconfiguring the peer at the same time. Later the peer can be reconfigured to establish the session using the new remote AS number and the alternative local AS number can be reset to zero. An alternative local AS number should only be used as an intermediate step on one side of a BGP session. Do not configure an alternative local AS number on both sides of a BGP session - configure the correct remote AS numbers instead. If this is an IBGP peer then bgpPeerRemoteAs must have the same value as bgpRmEntLocalAs. In this case the IBGP session can be established using either bgpRmEntLocalAs/bgpPeerRemoteAs or bgpPeerConfAltLocalAs. If this is an EBGP peer then bgpPeerRemoteAs must specify the remote peer's AS number, and bgpRmEntLocalAs, bgpPeerConfAltLocalAs and bgpPeerRemoteAs must all be different. In this case the EBGP session can be established using bgpRmEntLocalAs or bgpPeerConfAltLocalAs as the local AS number, but the remote AS number must match bgpPeerRemoteAs. The bgpPeerConfAltLocalAsMode field controls detailed operation of the alternative local AS number, including whether the peering session can be established using bgpRmEntLocalAs or only using bgpPeerConfAltLocalAs. Use of alternative local AS numbers is not supported if the router is a member of a confederation. The constraints explained above mean that this field is only used if the following conditions are all met: - bgpRmEntConfederationId = 0 - bgpPeerConfAltLocalAs != 0 - bgpPeerConfAltLocalAs != bgpRmEntLocalAs - bgpPeerConfAltLocalAs != bgpPeerRemoteAs. This field can be changed at any time. However, if the field is changed while the peer is admin_status UP, the change will only take effect after the peer has been cycled admin_status DOWN and then UP, thus forcing the peer session to be restarted. In this case, until the peer is set admin_status DOWN, the peer will be marked as out of date (as reported by the config_state field in the AMB_BGP_PEER_STATUS row for the peer).

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; representative source files are shown for each definition.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

bgpPeerConfAltLocalAs · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: bgpPeerConfAltLocalAs

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bgpPeerConfAltLocalAs",
    "OBJECT-TYPE",
    "SYNTAX",
    "BgpAutonomousSystemNumber",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"An alternative local AS number that can be used to establish a session with this peer. This is used when merging two ASs into a single AS. A value of zero means 'not configured'. If an alternative local AS number is configured then the peering session can be established using the alternative local AS instead of the primary local AS number specified by bgpRmEntLocalAs. Setting an alternative local AS number allows the primary local AS number to be changed without reconfiguring the peer at the same time. Later the peer can be reconfigured to establish the session using the new remote AS number and the alternative local AS number can be reset to zero. An alternative local AS number should only be used as an intermediate step on one side of a BGP session. Do not configure an alternative local AS number on both sides of a BGP session - configure the correct remote AS numbers instead. If this is an IBGP peer then bgpPeerRemoteAs must have the same value as bgpRmEntLocalAs. In this case the IBGP session can be established using either bgpRmEntLocalAs/bgpPeerRemoteAs or bgpPeerConfAltLocalAs. If this is an EBGP peer then bgpPeerRemoteAs must specify the remote peer's AS number, and bgpRmEntLocalAs, bgpPeerConfAltLocalAs and bgpPeerRemoteAs must all be different. In this case the EBGP session can be established using bgpRmEntLocalAs or bgpPeerConfAltLocalAs as the local AS number, but the remote AS number must match bgpPeerRemoteAs. The bgpPeerConfAltLocalAsMode field controls detailed operation of the alternative local AS number, including whether the peering session can be established using bgpRmEntLocalAs or only using bgpPeerConfAltLocalAs. Use of alternative local AS numbers is not supported if the router is a member of a confederation. The constraints explained above mean that this field is only used if the following conditions are all met: - bgpRmEntConfederationId = 0 - bgpPeerConfAltLocalAs != 0 - bgpPeerConfAltLocalAs != bgpRmEntLocalAs - bgpPeerConfAltLocalAs != bgpPeerRemoteAs. This field can be changed at any time. However, if the field is changed while the peer is admin_status UP, the change will only take effect after the peer has been cycled admin_status DOWN and then UP, thus forcing the peer session to be restarted. In this case, until the peer is set admin_status DOWN, the peer will be marked as out of date (as reported by the config_state field in the AMB_BGP_PEER_STATUS row for the peer).\"",
    "DEFVAL",
    "{",
    "0",
    "}",
    "::=",
    "{",
    "bgpPeerEntry",
    "96",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "BgpAutonomousSystemNumber"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "An alternative local AS number that can be used to establish a session with this peer. This is used when merging two ASs into a single AS. A value of zero means 'not configured'. If an alternative local AS number is configured then the peering session can be established using the alternative local AS instead of the primary local AS number specified by bgpRmEntLocalAs. Setting an alternative local AS number allows the primary local AS number to be changed without reconfiguring the peer at the same time. Later the peer can be reconfigured to establish the session using the new remote AS number and the alternative local AS number can be reset to zero. An alternative local AS number should only be used as an intermediate step on one side of a BGP session. Do not configure an alternative local AS number on both sides of a BGP session - configure the correct remote AS numbers instead. If this is an IBGP peer then bgpPeerRemoteAs must have the same value as bgpRmEntLocalAs. In this case the IBGP session can be established using either bgpRmEntLocalAs/bgpPeerRemoteAs or bgpPeerConfAltLocalAs. If this is an EBGP peer then bgpPeerRemoteAs must specify the remote peer's AS number, and bgpRmEntLocalAs, bgpPeerConfAltLocalAs and bgpPeerRemoteAs must all be different. In this case the EBGP session can be established using bgpRmEntLocalAs or bgpPeerConfAltLocalAs as the local AS number, but the remote AS number must match bgpPeerRemoteAs. The bgpPeerConfAltLocalAsMode field controls detailed operation of the alternative local AS number, including whether the peering session can be established using bgpRmEntLocalAs or only using bgpPeerConfAltLocalAs. Use of alternative local AS numbers is not supported if the router is a member of a confederation. The constraints explained above mean that this field is only used if the following conditions are all met: - bgpRmEntConfederationId = 0 - bgpPeerConfAltLocalAs != 0 - bgpPeerConfAltLocalAs != bgpRmEntLocalAs - bgpPeerConfAltLocalAs != bgpPeerRemoteAs. This field can be changed at any time. However, if the field is changed while the peer is admin_status UP, the change will only take effect after the peer has been cycled admin_status DOWN and then UP, thus forcing the peer session to be restarted. In this case, until the peer is set admin_status DOWN, the peer will be marked as out of date (as reported by the config_state field in the AMB_BGP_PEER_STATUS row for the peer)."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      0
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.2.826)

The UK Name Registration Authority

Current Registration Authority (inferred from ancestor 1.2.826)

Mark Barratt or Vanessa Tatler

Siblings (130)

OIDNameDirect childrenDescendantsDescription
1.2.826.42.1.1578918.5.65.1.3.1.1.1.52 bgpPeerMinRouteWithdrawInterval00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.53 bgpPeerStalePathTime00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.54 bgpPeerCheckNextHop00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.55 bgpPeerLocalAddrScopeId00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.56 bgpPeerMaxOrfEntries00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.57 bgpPeerOrfEntryCount00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.58 bgpPeerPeeringType00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.59 bgpPeerSoftResetWithStoredInfo00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.60 bgpPeerAllowLocalAs00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.61 bgpPeerDisableSenderLoopDetect00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.62 bgpPeerDisableRouteRefresh00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.63 bgpPeerFlapStatsClearStat00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.64 bgpPeerFlapStatsClearMap00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.65 bgpPeerLastErrorRcvd00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.66 bgpPeerLastErrorRcvdTime00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.67 bgpPeerLastErrorSent00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.68 bgpPeerLastErrorSentTime00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.69 bgpPeerLastState00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.70 bgpPeerLastEvent00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.71 bgpPeerCapsSent00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.72 bgpPeerCapsRcvd00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.73 bgpPeerCapsNegotiated00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.74 bgpPeerRstrSupport00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.75 bgpPeerRstrFamily00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.76 bgpPeerRstrRestarting00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.77 bgpPeerRstrStatus00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.78 bgpPeerRstrRemTime00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.79 bgpPeerRcvdMsgElapsedTime00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.80 bgpPeerIdleHoldRemTime00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.81 bgpPeerRouteRefrSent00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.82 bgpPeerRouteRefrRcvd00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.83 bgpPeerNxtHopSlf00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.84 bgpPeerThirdPtyNxtHop00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.85 bgpPeerNxtHopPeer00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.86 bgpPeerTrapPrefix00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.87 bgpPeerConfigThreshold00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.88 bgpPeerMaxPrfxHold00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.89 bgpPeerSelectedLocalAddrType00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.90 bgpPeerSelectedLocalAddr00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.91 bgpPeerSelectedLocalPort00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.92 bgpPeerSelectedRemotePort00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.93 bgpPeerBfdDesired00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.94 bgpPeerBfdStatus00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.95 bgpPeerCeaseErrorSubcode00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.97 bgpPeerSelectedLocalAs00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.98 bgpPeerSelectedRemoteAs00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.99 bgpPeerInPrfxes00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.100 bgpPeerOutPrfxes00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.101 bgpPeerOutPrfxesAdvertised00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.102 bgpPeerTrapGrHelperState00