RFC1269-MIB

All MIBs › RFC1269-MIB

Category: IETF Standards

Description: Defines BGP version 3 routing protocol management objects for peer and path monitoring per RFC 1269.

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 RFC1269-MIB?

RFC1269-MIB is the IETF standards-track Border Gateway Protocol version 3 (BGP-3) Management Information Base, an early routing-protocol MIB that predates the now-standard BGP-4 MIB. It defines objects for BGP peer session configuration, per-peer state, and path/route attribute information exchanged between BGP speakers. It is used to monitor the software-level health of the BGP routing process: peer/session state objects reveal whether a BGP peering is established or has dropped, and path attribute counters help diagnose route flapping or unexpected route withdrawals, rather than tracking any physical device hardware. It is superseded in modern deployments by the BGP4-MIB (RFC 1657/4273), and both build on the general SNMPv2-SMI framework rather than depending on other routing MIBs directly. It would be deployed on legacy IP routers running the now-obsolete BGP version 3 protocol, mostly of historical interest in modern networks that have all migrated to BGP-4. Engineers can download the RFC1269-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in RFC1269-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
legacy IP routers running BGP version 3

Monitoring Examples

No sample_objects were provided for this module, so specific object names cannot be cited with confidence; based on the well-documented structure of RFC 1269, an operator would be expected to poll the BGP peer table for per-peer connection state to detect a peering session dropping from Established to Idle, but exact identifiers used here are not confirmed from available source data.

What Can Be Monitored

BGP peer session state
BGP peer configuration
route/path attribute counters

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

Counter
IpAddress
NetworkAddress

From RFC1213-MIB

mib-2

OIDs

OID symbolic	OID numeric	Type	Access	Description
bgp	1.3.6.1.2.1.15
NTF bgpBackwardTransition	1.3.6.1.2.1.15.0.2			The BGPBackwardTransition Event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state.
NTF bgpEstablished	1.3.6.1.2.1.15.0.1			The BGP Established event is generated when the BGP FSM enters the ESTABLISHED state.
IP bgpIdentifier	1.3.6.1.2.1.15.4	IpAddress	read-only	The BGP Identifier of local system.
INT bgpLocalAs	1.3.6.1.2.1.15.2	INTEGER	read-only	The local autonomous system number.
OCT bgpPathAttrASPath	1.3.6.1.2.1.15.5.1.4	OCTET STRING	read-only	The set of ASs that must be traversed to reach the network. ( This object is probably best represented as SEQUENCE OF INTEGER. For SMI compatibility, though, it is represented as OCTET STRING. Each AS is represented as a pair of octets according to the following algorithm: first-byte-of-pair = ASNumber / 256; second-byte-of-pair = ASNumber & 255;
IP bgpPathAttrDestNetwork	1.3.6.1.2.1.15.5.1.2	IpAddress	read-only	The address of the destination network.
bgpPathAttrEntry	1.3.6.1.2.1.15.5.1		not-accessible	Information about a path to a network.
IP bgpPathAttrInterASMetric	1.3.6.1.2.1.15.5.1.6	IpAddress	read-only	The optional inter-AS metric. If this attribute has not been provided for this route, the value for this object is 0.
IP bgpPathAttrNextHop	1.3.6.1.2.1.15.5.1.5	IpAddress	read-only	The address of the border router that should be used for the destination network.
INT bgpPathAttrOrigin	1.3.6.1.2.1.15.5.1.3	INTEGER	read-only	The ultimate origin of the path information.
IP bgpPathAttrPeer	1.3.6.1.2.1.15.5.1.1	IpAddress	read-only	The IP address of the peer where the path information was learned.
INT bgpPeerAdminStatus	1.3.6.1.2.1.15.3.1.3	INTEGER	read-write	The desired state of the BGP connection. A transition from 'stop' to 'start' will cause the BGP Start Event to be generated. A transition from 'start' to 'stop' will cause the BGP Stop Event to be generated. This parameter can be used to restart BGP peer connections. Care should be used in providing write access to this object without adequate authentication.
bgpPeerEntry	1.3.6.1.2.1.15.3.1		not-accessible	Information about a BGP peer connection.
IP bgpPeerIdentifier	1.3.6.1.2.1.15.3.1.1	IpAddress	read-only	The BGP Identifier of this entry's BGP peer.
CTR bgpPeerInTotalMessages	1.3.6.1.2.1.15.3.1.12	Counter	read-only	The total number of messages received from the remote peer on this connection. This object should be initialized to zero when the connection is established.
CTR bgpPeerInUpdates	1.3.6.1.2.1.15.3.1.10	Counter	read-only	The number of BGP UPDATE messages received on this connection. This object should be initialized to zero when the connection is established.
OCT bgpPeerLastError	1.3.6.1.2.1.15.3.1.14	OCTET STRING	read-only	The last error code and subcode seen by this peer on this connection. If no error has occurred, this field is zero. Otherwise, the first byte of this two byte OCTET STRING contains the error code; the second contains the subcode.
IP bgpPeerLocalAddr	1.3.6.1.2.1.15.3.1.5	IpAddress	read-only	The local IP address of this entry's BGP connection.
INT bgpPeerLocalPort	1.3.6.1.2.1.15.3.1.6	INTEGER	read-only	The local port for the TCP connection between the BGP peers.
INT bgpPeerNegotiatedVersion	1.3.6.1.2.1.15.3.1.4	INTEGER	read-only	The negotiated version of BGP running between the two peers.
CTR bgpPeerOutTotalMessages	1.3.6.1.2.1.15.3.1.13	Counter	read-only	The total number of messages transmitted to the remote peer on this connection. This object should be initialized to zero when the connection is established.
CTR bgpPeerOutUpdates	1.3.6.1.2.1.15.3.1.11	Counter	read-only	The number of BGP UPDATE messages received on this connection. This object should be initialized to zero when the connection is established.
IP bgpPeerRemoteAddr	1.3.6.1.2.1.15.3.1.7	IpAddress	read-only	The remote IP address of this entry's BGP peer.
INT bgpPeerRemoteAs	1.3.6.1.2.1.15.3.1.9	INTEGER	read-only	The remote autonomous system number.
INT bgpPeerRemotePort	1.3.6.1.2.1.15.3.1.8	INTEGER	read-only	The remote port for the TCP connection between the BGP peers. Note that the objects bgpLocalAddr, bgpLocalPort, bgpRemoteAddr and bgpRemotePort provide the appropriate reference to the standard MIB TCP connection table.
INT bgpPeerState	1.3.6.1.2.1.15.3.1.2	INTEGER	read-only	The bgp peer connection state.
bgpPeerTable	1.3.6.1.2.1.15.3		not-accessible	The bgp peer table.
bgpRcvdPathAttrTable	1.3.6.1.2.1.15.5		not-accessible	The BGP Received Path Attribute Table contains information about paths to destination networks received by all peers.
OCT bgpVersion	1.3.6.1.2.1.15.1	OCTET STRING	read-only	Vector of supported BGP protocol version numbers. Each peer negotiates the version from this vector. Versions are identified via the string of bits contained within this object. The first octet contains bits 0 to 7, the second octet contains bits 8 to 15, and so on, with the most significant bit referring to the lowest bit number in the octet (e.g., the MSB of the first octet refers to bit 0). If a bit, i, is present and set, then the version (i+1) of the BGP is supported.

RFC description

BGP (Border Gateway Protocol) MIB for managing BGP peer connections and routing protocol parameters.

Start monitoring vendor-neutral, standards-based MIB, legacy IP routers running BGP version 3 (obsolete) 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 RFC1269-MIB

What Is RFC1269-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description