CISCO-BGP4-MIB: View SNMP OID List / Download MIB

An extension to the IETF BGP4 MIB module defined in RFC 1657. Following is the terminology associated with Border Gateway Protocol(BGP). UPDATE message UPDATE messages are used to transfer routing information between BGP peers. An UPDATE message is used to advertise a single feasible route to a peer, or to withdraw multiple unfeasible routes from service. Adj-RIBs-In The Adj-RIBs-In store routing information that has been learned from inbound UPDATE messages. Their contents represent routes that are available as an input to the Decision Process. Loc-RIB(BGP table) The Loc-RIB contains the local routing information that the BGP speaker has selected by applying its local policies to the routing information contained in its Adj-RIBs-In. Adj-RIBs-Out The Adj-RIBs-Out store the information that the local BGP speaker has selected for advertisement to its peers. The routing information stored in the Adj-RIBs-Out will be carried in the local BGP speaker's UPDATE messages and advertised to its peers. Path Attributes A variable length sequence of path attributes is present in every UPDATE. Each path attribute is a triple of variable length. Network Layer Reachability Information(NLRI) A variable length field present in UPDATE messages which contains a list of Network Layer address prefixes. Address Family Identifier(AFI) Primary identifier to indicate the type of the Network Layer Reachability Information(NLRI) being carried. Subsequent Address Family Identifier(SAFI) Secondary identifier to indicate the type of the Network Layer Reachability Information(NLRI) being carried.

The BGP cbgpFsmStateChange notification is generated for every BGP FSM state change. The bgpPeerRemoteAddr value is attached to the notification object ID.

The cbgpBackwardTransition Event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state. The bgpPeerRemoteAddr value is attached to the notification object ID.

The cbgpPrefixThresholdExceeded notification is generated when prefix count exceeds the configured warning threshold on a session for an address family. The bgpPeerRemoteAddr, cbgpPeerAddrFamilyAfi and cbgpPeerAddrFamilySafi values are attached to the notification object ID.

The cbgpPrefixThresholdClear notification is generated when prefix count drops below the configured clear threshold on a session for an address family once cbgpPrefixThresholdExceeded is generated. This won't be generated if the peer session goes down after the generation of cbgpPrefixThresholdExceeded. The bgpPeerRemoteAddr, cbgpPeerAddrFamilyAfi and cbgpPeerAddrFamilySafi values are attached to the notification object ID.

The cbgpPeer2EstablishedNotification notification is generated when the BGP FSM enters the established state.

The cbgpPeer2BackwardTransNotification notification is generated when the BGP FSM moves from a higher numbered state to a lower numbered state.

The cbgpPeer2FsmStateChange notification is generated for every BGP FSM state change.

The cbgpPeer2BackwardTransition notification is generated when the BGP FSM moves from a higher numbered state to a lower numbered state.

The cbgpPeer2PrefixThresholdExceeded notification is generated when prefix count exceeds the configured warning threshold on a session for an address family.

The cbgpPeer2PrefixThresholdClear notification is generated when prefix count drops below the configured clear threshold on a session for an address family once cbgpPeer2PrefixThresholdExceeded is generated. This will not be generated if the peer session goes down after the generation of cbgpPrefixThresholdExceeded.

This table contains information about routes to destination networks from all BGP4 peers. Since BGP4 can carry routes for multiple Network Layer protocols, this table has the Address Family Identifier(AFI) of the Network Layer protocol as the first index. Further for a given AFI, routes carried by BGP4 are distinguished based on Subsequent Address Family Identifiers(SAFI). Hence that is used as the second index. Conceptually there is a separate Loc-RIB maintained by the BGP speaker for each combination of AFI and SAFI supported by it.

Information about a path to a network received from a peer.

Represents Address Family Identifier(AFI) of the Network Layer protocol associated with the route. An implementation is only required to support IPv4 unicast and VPNv4 (Value - 1) address families.

Represents Subsequent Address Family Identifier(SAFI) of the route. It gives additional information about the type of the route. An implementation is only required to support IPv4 unicast(Value - 1) and VPNv4( Value - 128) address families.

Represents the type of Network Layer address stored in cbgpRoutePeer. An implementation is only required to support IPv4 address type(Value - 1).

The Network Layer address of the peer where the route information was learned. An implementation is only required to support an IPv4 peer.

A Network Address prefix in the Network Layer Reachability Information field of BGP UPDATE message. This object is a Network Address containing the prefix with length specified by cbgpRouteAddrPrefixLen. Any bits beyond the length specified by cbgpRouteAddrPrefixLen are zeroed.

Length in bits of the Network Address prefix in the Network Layer Reachability Information field.

The ultimate origin of the route information. Enumeration: 'egp': 2, 'incomplete': 3, 'igp': 1.

The sequence of AS path segments. Each AS path segment is represented by a triple . The type is a 1-octet field which has two possible values: 1 AS_SET: unordered set of ASs a route in the UPDATE message has traversed 2 AS_SEQUENCE: ordered set of ASs a route in the UPDATE message has traversed. The length is a 1-octet field containing the number of ASs in the value field. The value field contains one or more AS numbers, each AS is represented in the octet string as a pair of octets according to the following algorithm: first-byte-of-pair = ASNumber / 256; second-byte-of-pair = ASNumber & 255;

The Network Layer address of the border router that should be used for the destination network.

Indicates the presence/absence of MULTI_EXIT_DISC attribute for the route.

This metric is used to discriminate between multiple exit points to an adjacent autonomous system. The value of this object is irrelevant if the value of of cbgpRouteMedPresent is false(2).

Indicates the presence/absence of LOCAL_PREF attribute for the route.

The degree of preference calculated by the local BGP4 speaker for the route. The value of this object is irrelevant if the value of cbgpRouteLocalPrefPresent is false(2).

Whether or not the local system has selected a less specific route without selecting a more specific route. Enumeration: 'lessSpecificRouteNotSelected': 1, 'lessSpecificRouteSelected': 2.

The AS number of the last BGP4 speaker that performed route aggregation. A value of zero (0) indicates the absence of this attribute.

Represents the type of Network Layer address stored in cbgpRouteAggregatorAddr.

The Network Layer address of the last BGP4 speaker that performed route aggregation. A value of all zeros indicates the absence of this attribute.

An indication of whether or not this route was chosen as the best BGP4 route.

One or more path attributes not understood by this BGP4 speaker. Size zero (0) indicates the absence of such attribute(s). Octets beyond the maximum size, if any, are not recorded by this object. Each path attribute is a triple of variable length. Attribute Type is a two-octet field that consists of the Attribute Flags octet followed by the Attribute Type Code octet. If the Extended Length bit of the Attribute Flags octet is set to 0, the third octet of the Path Attribute contains the length of the attribute data in octets. If the Extended Length bit of the Attribute Flags octet is set to 1, then the third and the fourth octets of the path attribute contain the length of the attribute data in octets. The remaining octets of the Path Attribute represent the attribute value and are interpreted according to the Attribute Flags and the Attribute Type Code.

BGP peer table. This table contains, one entry per BGP peer, information about the connections with BGP peers.

Entry containing information about the connection with a BGP peer.

Number of Route prefixes received on this connnection, which are accepted after applying filters. Possible filters are route maps, prefix lists, distributed lists, etc.

Counter which gets incremented when a route prefix received on this connection is denied or when a route prefix is denied during soft reset of this connection if 'soft-reconfiguration' is on . This object is initialized to zero when the peer is configured or the router is rebooted

Max number of route prefixes accepted on this connection

Counter which gets incremented when a route prefix is advertised on this connection. This object is initialized to zero when the peer is configured or the router is rebooted

Counter which gets incremented when a route prefix is suppressed from being sent on this connection. This object is initialized to zero when the peer is configured or the router is rebooted

Counter which gets incremented when a route prefix is withdrawn on this connection. This object is initialized to zero when the peer is configured or the router is rebooted

Implementation specific error description for bgpPeerLastErrorReceived.

The BGP peer connection previous state. Enumeration: 'established': 6, 'none': 0, 'openconfirm': 5, 'opensent': 4, 'idle': 1, 'connect': 2, 'active': 3.

This table contains the capabilities that are supported by a peer. Capabilities of a peer are received during BGP connection establishment. Values corresponding to each received capability are stored in this table. When a new capability is received, this table is updated with a new entry. When an existing capability is not received during the latest connection establishment, the corresponding entry is deleted from the table.

Each entry represents a capability received from a peer with a particular code and an index. When a capability is received multiple times with different values during a BGP connection establishment, corresponding entries are differentiated with indices.

The BGP Capability Advertisement Capability Code. Enumeration: 'routeRefresh': 2, 'gracefulRestart': 64, 'multiProtocol': 1, 'routeRefreshOld': 128.

Multiple instances of a given capability may be sent by a BGP speaker. This variable is used to index them.

The value of the announced capability. This MIB object value is organized as given below, Capability : Route Refresh Capability Null string Capability : Multiprotocol Extensions +----------------------------------+ | AFI(16 bits) | +----------------------------------+ | SAFI (8 bits) | +----------------------------------+ Capability : Graceful Restart +----------------------------------+ | Restart Flags (4 bits) | +----------------------------------+ | Restart Time in seconds (12 bits)| +----------------------------------+ | AFI(16 bits) | +----------------------------------+ | SAFI (8 bits) | +----------------------------------+ | Flags for Address Family (8 bits)| +----------------------------------+ | ... | +----------------------------------+ | AFI(16 bits) | +----------------------------------+ | SAFI (8 bits) | +----------------------------------+ | Flags for Address Family (8 bits)| +----------------------------------+

This table contains information related to address families supported by a peer. Supported address families of a peer are known during BGP connection establishment. When a new supported address family is known, this table is updated with a new entry. When an address family is not supported any more, corresponding entry is deleted from the table.

An entry is identified by an AFI/SAFI pair and peer address. It contains names associated with an address family.

The AFI index of the entry. An implementation is only required to support IPv4 unicast and VPNv4 (Value - 1) address families.

The SAFI index of the entry. An implementation is only required to support IPv4 unicast(Value - 1) and VPNv4( Value - 128) address families.

Implementation specific Address Family name.

This table contains prefix related information related to address families supported by a peer. Supported address families of a peer are known during BGP connection establishment. When a new supported address family is known, this table is updated with a new entry. When an address family is not supported any more, corresponding entry is deleted from the table.

An entry is identified by an AFI/SAFI pair and peer address. It contains information associated with route prefixes belonging to an address family.

Number of accepted route prefixes on this connection, which belong to an address family.

This counter is incremented when a route prefix, which belongs to an address family, received on this connection is denied. It is initialized to zero when the connection is undergone a hard reset.

Max number of route prefixes accepted for an address family on this connection.

Prefix threshold value (%) for an address family on this connection at which warning message stating the prefix count is crossed the threshold or corresponding SNMP notification is generated.

Prefix threshold value (%) for an address family on this connection at which SNMP clear notification is generated if prefix threshold notification is already generated.

This counter is incremented when a route prefix, which belongs to an address family is advertised on this connection. It is initialized to zero when the connection is undergone a hard reset.

This counter is incremented when a route prefix, which belongs to an address family is suppressed from being sent on this connection. It is initialized to zero when the connection is undergone a hard reset.

This counter is incremented when a route prefix, which belongs to an address family, is withdrawn on this connection. It is initialized to zero when the connection is undergone a hard reset.

BGP peer table. This table contains, one entry per BGP peer, information about the connections with BGP peers.

Entry containing information about the connection with a BGP peer.

Represents the type of Peer address stored in cbgpPeer2Entry.

The remote IP address of this entry's BGP peer.

The BGP peer connection state. Enumeration: 'established': 6, 'openconfirm': 5, 'opensent': 4, 'idle': 1, 'connect': 2, 'active': 3.

The desired state of the BGP connection. A transition from 'stop' to 'start' will cause the BGP Manual Start Event to be generated. A transition from 'start' to 'stop' will cause the BGP Manual 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. Enumeration: 'start': 2, 'stop': 1.

The negotiated version of BGP running between the two peers. This entry MUST be zero (0) unless the cbgpPeer2State is in the openconfirm or the established state. Note that legal values for this object are between 0 and 255.

The local IP address of this entry's BGP connection.

The local port for the TCP connection between the BGP peers.

The local AS number for this session.

The BGP Identifier of this entry's BGP peer.

The remote port for the TCP connection between the BGP peers. Note that the objects cbgpPeer2LocalAddr, cbgpPeer2LocalPort, cbgpPeer2RemoteAddr, and cbgpPeer2RemotePort provide the appropriate reference to the standard MIB TCP connection table.

The remote autonomous system number received in the BGP OPEN message.

The BGP Identifier of this entry's BGP peer. This entry MUST be 0.0.0.0 unless the cbgpPeer2State is in the openconfirm or the established state.

The number of BGP UPDATE messages received on this connection.

The number of BGP UPDATE messages transmitted on this connection.

The total number of messages received from the remote peer on this connection.

The total number of messages transmitted to the remote peer on this connection.

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, and the second byte contains the subcode.

The total number of times the BGP FSM transitioned into the established state for this peer.

This timer indicates how long (in seconds) this peer has been in the established state or how long since this peer was last in the established state. It is set to zero when a new peer is configured or when the router is booted.

Time interval (in seconds) for the ConnectRetry timer. The suggested value for this timer is 120 seconds.

Time interval (in seconds) for the Hold Timer established with the peer. The value of this object is calculated by this BGP speaker, using the smaller of the values in cbgpPeer2HoldTimeConfigured and the Hold Time received in the OPEN message. This value must be at least three seconds if it is not zero (0). If the Hold Timer has not been established with the peer this object MUST have a value of zero (0). If the cbgpPeer2HoldTimeConfigured object has a value of (0), then this object MUST have a value of (0).

Time interval (in seconds) for the KeepAlive timer established with the peer. The value of this object is calculated by this BGP speaker such that, when compared with cbgpPeer2HoldTime, it has the same proportion that cbgpPeer2KeepAliveConfigured has, compared with cbgpPeer2HoldTimeConfigured. If the KeepAlive timer has not been established with the peer, this object MUST have a value of zero (0). If the of cbgpPeer2KeepAliveConfigured object has a value of (0), then this object MUST have a value of (0).

Time interval (in seconds) for the Hold Time configured for this BGP speaker with this peer. This value is placed in an OPEN message sent to this peer by this BGP speaker, and is compared with the Hold Time field in an OPEN message received from the peer when determining the Hold Time (cbgpPeer2HoldTime) with the peer. This value must not be less than three seconds if it is not zero (0). If it is zero (0), the Hold Time is NOT to be established with the peer. The suggested value for this timer is 90 seconds.

Time interval (in seconds) for the KeepAlive timer configured for this BGP speaker with this peer. The value of this object will only determine the KEEPALIVE messages' frequency relative to the value specified in cbgpPeer2HoldTimeConfigured; the actual time interval for the KEEPALIVE messages is indicated by cbgpPeer2KeepAlive. A reasonable maximum value for this timer would be one third of that of cbgpPeer2HoldTimeConfigured. If the value of this object is zero (0), no periodical KEEPALIVE messages are sent to the peer after the BGP connection has been established. The suggested value for this timer is 30 seconds.

Time interval (in seconds) for the MinASOriginationInterval timer. The suggested value for this timer is 15 seconds.

Time interval (in seconds) for the MinRouteAdvertisementInterval timer. The suggested value for this timer is 30 seconds for EBGP connections and 5 seconds for IBGP connections.

Elapsed time (in seconds) since the last BGP UPDATE message was received from the peer. Each time cbgpPeer2InUpdates is incremented, the value of this object is set to zero (0).

Implementation specific error description for bgpPeerLastErrorReceived.

The BGP peer connection previous state. Enumeration: 'established': 6, 'none': 0, 'openconfirm': 5, 'opensent': 4, 'idle': 1, 'connect': 2, 'active': 3.

This table contains the capabilities that are supported by a peer. Capabilities of a peer are received during BGP connection establishment. Values corresponding to each received capability are stored in this table. When a new capability is received, this table is updated with a new entry. When an existing capability is not received during the latest connection establishment, the corresponding entry is deleted from the table.

Each entry represents a capability received from a peer with a particular code and an index. When a capability is received multiple times with different values during a BGP connection establishment, corresponding entries are differentiated with indices.

The BGP Capability Advertisement Capability Code. Enumeration: 'gracefulRestart': 64, 'multiProtocol': 1, 'addPath': 69, 'routeRefreshOld': 128, 'routeRefresh': 2, 'fourByteAs': 65.

Multiple instances of a given capability may be sent by a BGP speaker. This variable is used to index them.

The value of the announced capability. This MIB object value is organized as given below, Capability : Route Refresh Capability 4-Byte AS Capability Null string Capability : Multiprotocol Extensions +----------------------------------+ | AFI(16 bits) | +----------------------------------+ | SAFI (8 bits) | +----------------------------------+ Capability : Graceful Restart +----------------------------------+ | Restart Flags (4 bits) | +----------------------------------+ | Restart Time in seconds (12 bits)| +----------------------------------+ | AFI(16 bits) | +----------------------------------+ | SAFI (8 bits) | +----------------------------------+ | Flags for Address Family (8 bits)| +----------------------------------+ | ... | +----------------------------------+ | AFI(16 bits) | +----------------------------------+ | SAFI (8 bits) | +----------------------------------+ | Flags for Address Family (8 bits)| +----------------------------------+ Capability : Additional Paths +----------------------------------+ | AFI(16 bits) | +----------------------------------+ | SAFI (8 bits) | +----------------------------------+ | Send/Receive (8 bits) | +----------------------------------+

This table contains information related to address families supported by a peer. Supported address families of a peer are known during BGP connection establishment. When a new supported address family is known, this table is updated with a new entry. When an address family is not supported any more, corresponding entry is deleted from the table.

An entry is identified by an AFI/SAFI pair and peer address. It contains names associated with an address family.

The AFI index of the entry. An implementation is only required to support IPv4 unicast and VPNv4 (Value - 1) address families.

The SAFI index of the entry. An implementation is only required to support IPv4 unicast(Value - 1) and VPNv4( Value - 128) address families.

Implementation specific Address Family name.

This table contains prefix related information related to address families supported by a peer. Supported address families of a peer are known during BGP connection establishment. When a new supported address family is known, this table is updated with a new entry. When an address family is not supported any more, corresponding entry is deleted from the table.

An entry is identified by an AFI/SAFI pair and peer address. It contains information associated with route prefixes belonging to an address family.

Number of accepted route prefixes on this connection, which belong to an address family.

This counter is incremented when a route prefix, which belongs to an address family, received on this connection is denied. It is initialized to zero when the connection is undergone a hard reset.

Max number of route prefixes accepted for an address family on this connection.

Prefix threshold value (%) for an address family on this connection at which warning message stating the prefix count is crossed the threshold or corresponding SNMP notification is generated.

Prefix threshold value (%) for an address family on this connection at which SNMP clear notification is generated if prefix threshold notification is already generated.

This counter is incremented when a route prefix, which belongs to an address family is advertised on this connection. It is initialized to zero when the connection is undergone a hard reset.

This counter is incremented when a route prefix, which belongs to an address family is suppressed from being sent on this connection. It is initialized to zero when the connection is undergone a hard reset.

This counter is incremented when a route prefix, which belongs to an address family, is withdrawn on this connection. It is initialized to zero when the connection is undergone a hard reset.

Indicates whether the specific notifications are enabled. If notifsEnable(0) bit is set to 1, then the notifications defined in ciscoBgp4NotificationsGroup1 are enabled; If notifsPeer2Enable(1) bit is set to 1, then the notifications defined in ciscoBgp4Peer2NotificationsGroup are enabled. Bits: 'notifsEnable': 0, 'notifsPeer2Enable': 1.

The local autonomous system (AS) number.

The compliance statement for entities which implement the Cisco BGP4 MIB

The compliance statement for entities which implement the Cisco BGP4 MIB

The compliance statement for entities which implement the Cisco BGP4 MIB

The compliance statement for entities which implement the Cisco BGP4 MIB

A collection of objects providing information about routes received by BGP speaker.

A collection of objects providing information about routes received by BGP speaker.

The collection of notifications related to BGP.

A collection of objects providing information about a BGP peer.

The collection of notifications related to BGP.

A collection of objects providing information about a BGP peer.

A collection of notifications related to BGP.

A collection of global objects related to BGP.