BGP4-OPT-PARAMETERS-MIB

All MIBs › BGP4-OPT-PARAMETERS-MIB

Organization: IETF IDR Working Group

Last Updated: 2001-02-23

Description: IETF IDR extension MIB covering BGP-4 optional parameters including TCP MD5 authentication and capabilities advertisement (RFC 2842) on BGP routers

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is BGP4-OPT-PARAMETERS-MIB?

BGP4-OPT-PARAMETERS-MIB is an IETF (IDR working group) standards-track extension to the base BGP4-MIB, adding management objects for BGP-4 optional parameters defined in RFC 2842, specifically TCP MD5 authentication configuration and capability advertisement/negotiation between BGP peers. It exposes configuration and per-peer capability state rather than interface, environmental, or hardware data. Its monitoring value centers on protocol/software configuration status: confirming whether MD5 authentication is configured correctly on a peering session and which optional capabilities a peer has advertised or negotiated, helping diagnose BGP session flaps caused by authentication mismatches or capability incompatibility. It explicitly extends and depends on the base BGP4-MIB (RFC 1657/4273) for its peer table structure. It is deployed on any vendor's BGP-speaking routers that support this IETF extension for troubleshooting inter-AS or peering-session establishment issues. Engineers implementing or auditing this functionality typically reference the BGP4-OPT-PARAMETERS-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in BGP4-OPT-PARAMETERS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer
BGP-4 speaking routers

Monitoring Examples

No sample object or table names were provided in the source data for this MIB, so specific instances cannot be cited; however, per RFC 2842 the module would typically extend the BGP4-MIB peer table with per-peer objects for MD5 authentication key configuration and capability advertisement/negotiation flags, which an operator would poll alongside the standard bgpPeerTable to correlate an authentication or capability mismatch with a peering session that fails to establish or repeatedly resets.

What Can Be Monitored

TCP MD5 authentication configuration per peer
advertised/negotiated BGP capabilities per peer

Imported Objects

From BGP-MIB

bgp	MODULE-IDENTITY
bgpPeerEntry	OBJECT-TYPE
bgpPeerRemoteAddr	OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
mib-2

From SNMPv2-TC

AutonomousType
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
bgp4OptParametersMIB	1.3.6.1.2.1.15.9			The extension of the MIB module for BGP-4 for optional parameters.
bgpAuthenticationTable	1.3.6.1.2.1.15.9.1		not-accessible	The BGP-4 Authentication Table contains information about BGP Authentication Options on a per-peer basis.
bgpAuthenticationPeerEntry	1.3.6.1.2.1.15.9.1.1		not-accessible	Information about Authentication on a per-peer basis.
INT bgpAuthenticationDirection	1.3.6.1.2.1.15.9.1.1.1	INTEGER	not-accessible	This 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.
I32 bgpAuthenticationCode	1.3.6.1.2.1.15.9.1.1.2	Integer32	read-write	This is the AuthenticationCode used. This value is set to -1 if Authentication is not present.
I32 bgpAuthenticationDataLength	1.3.6.1.2.1.15.9.1.1.3	Integer32	read-write	This 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.
OCT bgpAuthenticationDataContents	1.3.6.1.2.1.15.9.1.1.4	OCTET STRING	read-write	This is the Authentication payload. The semantics of this variable are interpreted according to the authentication code.
T/F bgpCapabilitySupportAvailable	1.3.6.1.2.1.15.9.2	TruthValue	read-write	This variable determines whether BGP-4 capabilities are supported in this implementation. This variable may be set to false to disable capability support.
OCT bgpSupportedCapabilities	1.3.6.1.2.1.15.9.3	OCTET STRING	read-only	Vector 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.
bgpPeerCapabilitiesTable	1.3.6.1.2.1.15.9.4		not-accessible	This table contains contains the capabilities that are supported for a given peer.
bgpPeerCapabilitiesEntry	1.3.6.1.2.1.15.9.4.2		not-accessible	These entries are keyed by a BGP-4 peer's remote address and port combination over which the peering session has been established.
OCT bgpPeerCapabilitiesAnnounced	1.3.6.1.2.1.15.9.4.2.1	OCTET STRING	read-only	This 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.
OCT bgpPeerCapabilitiesReceived	1.3.6.1.2.1.15.9.4.2.2	OCTET STRING	read-only	This 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.
OID bgpProtocolExtensions	1.3.6.1.2.1.15.9.5	AutonomousType	read-only	Registration 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.

RFC description

IETF MIB for managing BGP-4 optional parameters and capabilities in routing implementations.

Start monitoring BGP-speaking routers with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download BGP4-OPT-PARAMETERS-MIB

What Is BGP4-OPT-PARAMETERS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description