BGP4V2-TC-MIB

Description: Defines textual conventions and address family types used by the IETF BGP-4 version 2 standard MIB.

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.

BGP4V2-TC-MIB is a vendor-neutral IETF textual-conventions MIB that defines shared data types, such as address-family identifiers, used by the newer multiprotocol BGP-4 version 2 MIB framework intended to succeed the original RFC 4273 BGP4-MIB with IPv6 and multi-address-family support. As a textual-conventions-only module it does not define any runtime object instances, tables, or counters of its own; it purely standardizes types that other companion BGP MIB modules import. Consequently it exposes no monitorable hardware or software status data on its own — no uptime, peer state, or performance counters — its role is entirely as a shared dependency. Its explicit purpose is to be imported by a companion BGP4V2 peer/route MIB that uses these conventions to build actual monitorable tables. It would appear on a device only indirectly, wherever a router implements the newer multiprotocol BGP MIB framework built on top of it, as specified in the BGP4V2-TC-MIB RFC that defines these shared conventions.

BGP4V2-TC-MIB is a textual-conventions-only module with no runtime data objects of its own, so there is no concrete monitoring scenario to describe. It exists solely to define types, such as address-family enumerations, that dependent BGP MIB modules import to build their actual peer and route tables.

Textual conventions for BGP-4 routing protocol data representation.