BGP4-OPT-PARAMETERS-MIB
AI MIB Summary
The BGP4-OPT-PARAMETERS-MIB enables monitoring of optional BGP-4 parameters, including capability advertisements and extended attributes, within Border Gateway Protocol sessions. This module facilitates the verification of negotiated session capabilities and the detection of non-standard or vendor-specific BGP extensions during peer establishment.
The extension of the MIB module for BGP-4 for optional parameters.
Main OID:
bgp4OptParametersMIB.1.3.6.1.4.1.41916.14.1.9
15
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
15 total| Object Name |
|---|
bgp4OptParametersMIBThe extension of the MIB module for BGP-4 for
optional parameters. MODULE-IDENTITY .1.3.6.1.4.1.41916.14.1.9 |
bgpAuthenticationTableThe BGP-4 Authentication Table contains information
about BGP Authentication Options on a per-peer basis. SEQUENCE OF BgpAuthenticationPeerEntry .1.3.6.1.4.1.41916.14.1.9.1 |
bgpAuthenticationPeerEntryInformation about Authentication on a per-peer basis. BgpAuthenticationEntry .1.3.6.1.4.1.41916.14.1.9.1.1 |
bgpAuthenticationEntryInformation about BGP-4 Authentication. BgpAuthenticationEntry .1.3.6.1.4.1.41916.14.1.9.1.1.2 |
bgpAuthenticationDirectionThis variable indicates whether authentication
information is either being sent by the BGP
speaker or has been been received by the BGP
speaker. It also serves as the index into the
table of authentication information for the
direction of authentication. Integer32 { sent (1), -- Authorization is being sent received (2) -- Authorization is being received } .1.3.6.1.4.1.41916.14.1.9.1.1.2.1 |
bgpAuthenticationCodeThis is the AuthenticationCode used.
This value is set to -1 if Authentication is
not present.rw Integer32 (-1 | 0..255) .1.3.6.1.4.1.41916.14.1.9.1.1.2.2 |
bgpAuthenticationDataLengthThis value is derived from the optional
parameter length minus one (the size of
bgpAuthenticationCode). This value may be no
larger than 252 due to overhead. This value
is set to -1 if Authentication is not present.rw Integer32 (-1 | 0..252) .1.3.6.1.4.1.41916.14.1.9.1.1.2.3 |
bgpAuthenticationDataContentsThis is the Authentication payload. The
semantics of this variable are interpreted
according to the authentication code.rw OCTET STRING .1.3.6.1.4.1.41916.14.1.9.1.1.2.4 |
bgpCapabilitySupportAvailableThis variable determines whether BGP-4
capabilities are supported in this
implementation. This variable may be set to
false to disable capability support.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.41916.14.1.9.2 |
bgpSupportedCapabilitiesVector of BGP-4 capabilities that are
supported in this implementation. Capabilities
are identified via the string of bits within
this object. The first octet contains bits
0 to 7, the second octet contains bits 8 to 15
and so on. If a bit, i, is present and set,
then the capability (i+1) is supported.
When capabilities are not supported, all bits
must be zero.ro OCTET STRING .1.3.6.1.4.1.41916.14.1.9.3 |
bgpPeerCapabilitiesTableThis table contains contains the capabilities
that are supported for a given peer. SEQUENCE OF BgpPeerCapabilitiesEntry .1.3.6.1.4.1.41916.14.1.9.4 |
bgpPeerCapabilitiesEntryThese entries are keyed by a BGP-4 peer's remote
address and port combination over which the
peering session has been established. BgpPeerCapabilitiesEntry .1.3.6.1.4.1.41916.14.1.9.4.2 |
bgpPeerCapabilitiesAnnouncedThis bit vector identifies which capabilities
have been announced to a BGP-4 speaker.
Capabilities are identified via the string of
bits within this object. The first octet
contains bits 0 to 7, the second octet contains
bits 8 to 15 and so on. If a bit, i, is present
and set, then the capability (i+1) is supported.
When capabilities are not supported, all bits
must be zero.ro OCTET STRING .1.3.6.1.4.1.41916.14.1.9.4.2.1 |
bgpPeerCapabilitiesReceivedThis bit vector identifies which capabilities have
been announced by the remote BGP-4 speaker.
Capabilities are identified via the string of bits
within this object. The first octet contains bits 0
to 7, the second octet contains bits 8 to 15 and so
on. If a bit, i, is present and set, then the
capability (i+1) is supported.
When capabilities are not supported, all bits must
be zero.ro OCTET STRING .1.3.6.1.4.1.41916.14.1.9.4.2.2 |
bgpProtocolExtensionsRegistration point for MIB Modules for BGP
Protocol Extensions.
The Capabilities Advertisement RFC delineates
IANA registered capability code numbers, 0-127
and private use capability code numbers, 128-255.
The first sub-identifier will be the enterprise
number of the registering entity. This is used
to remove the ambiguity of the private use
portion of the capability code assignments. For
IANA registered capability codes 0-127, the first
sub-identifier will be 0.
The second sub-identifier will be the capability
code for the advertised capability.
For example, the MPBGP-MIB would be assigned as
{ bgpProtocolStandardExtensions 0 1 } since it
has been assigned capability code number 1 and
is an IETF assigned (IANA registered) capability
extension.ro AutonomousType (SNMPv2-TC) .1.3.6.1.4.1.41916.14.1.9.5 |