 Feedback
|
Table Of Contents
BGP 4 MIB Support for per-Peer Received Routes
Restrictions on BGP 4 MIB Support for Per-Peer Received Routes
Information About BGP 4 MIB Support for Per-Peer Received Routes
BGP 4 MIB Support for Per-Peer Received Routes Overview
BGP 4 per-Peer Received Routes Table Elements and Objects
Network Address Prefix Descriptions for the NLRI Field
Benefits of BGP 4 MIB Support for Per-Peer Received Routes
Feature Information for BGP 4 MIB Support for per-Peer Received Routes
BGP 4 MIB Support for per-Peer Received Routes
First Published: 12.0(21)SLast Updated: July 27, 2010This module describes the BGP 4 MIB Support for per-Peer Received Routes feature, introduces a new table in the CISCO-BGP4-MIB that provides the capability to query (by using Simple Network Management Protocol [SNMP] commands) for routes that are learned from individual Border Gateway Protocol (BGP) peers.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for BGP 4 MIB Support for per-Peer Received Routes" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Restrictions on BGP 4 MIB Support for Per-Peer Received Routes
•
•
Restrictions on BGP 4 MIB Support for Per-Peer Received Routes
BGP 4 MIB Support for per-Peer Received Routes supports only routes that are contained in IPv4 AFIs and unicast SAFIs in the local BGP RIB table. The BGP 4 MIB Support for per-Peer Received Routes enhancement is supported only by BGP Version 4.
Information About BGP 4 MIB Support for Per-Peer Received Routes
•
•
•
BGP 4 MIB Support for Per-Peer Received Routes Overview
BGP 4 MIB Support for per-Peer Received Routes introduces a new table in the CISCO-BGP4-MIB that provides the capability to query (by using SNMP commands) for routes that are learned from individual BGP peers.
Before this new MIB table was introduced, a network operator could obtain the routes learned by a local BGP-speaking router by querying the local BGP speaker with an SNMP command (for example, the snmpwalk command). The network operator used the SNMP command to query the bgp4PathAttrTable of the CISCO-BGP4-MIB. The routes that were returned from a bgp4PathAttrTable query were indexed in the following order:
•
•
•
Because the bgp4PathAttrTable indexes the prefixes first, obtaining routes learned from individual BGP peers will require the network operator to "walk through" the complete bgp4PathAttrTable and filter out routes from the interested peer. A BGP Routing Information Base (RIB) could contain 10,000 or more routes, which makes a manual "walk" operation impossible and automated walk operations very inefficient.
BGP 4 MIB Support for per-Peer Received Routes introduces a Cisco-specific enterprise extension to the CISCO-BGP4-MIB that defines a new table called the cbgpRouterTable. The cbgpRouterTable provides the same information as the bgp4PathAttrTable with the following two differences:
•
–
–
–
The search criteria for SNMP queries of local routes are improved because peer addresses are indexed before prefixes. A search for routes that are learned from individual peers is improved with this enhancement because peer addresses are indexed before prefixes. A network operator will no longer need to search through potentially thousands of routes to obtain the learned routes of a local BGP RIB table.
•
Note
BGP 4 per-Peer Received Routes Table Elements and Objects
The following sections describe new table elements, AFI and SAFI tables and objects, and network address prefixes in the Network Layer Reachability Information (NLRI) fields that have been introduced by the BGP 4 MIB Support for per-Peer Received Routes enhancement.
MIB Tables and Objects
Table 1 describes the MIB indexes of the cbgpRouterTable.
For a complete description of the MIB, see the CISCO-BGP4-MIB file CISCO-BGP4-MIB.my, available through Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Table 1 MIB Indexes of the cbgpRouterTable
cbgpRouteAfi
Represents the AFI of the network layer protocol that is associated with the route.
cbgpRouteSafi
Represents the SAFI of the route. It gives additional information about the type of the route. The AFI and SAFI are used together to determine which local RIB (Loc-RIB) contains a particular route.
cbgpRoutePeerType
Represents the type of network layer address that is stored in the cbgpRoutePeer object.
cbgpRoutePeer
Represents the network layer address of the peer from which the route information has been learned.
cbgpRouteAddrPrefix
Represents the network address prefix that is carried in a BGP update message.
See Table 2 for information about the types of network layer addresses that can be stored in specific types of AFI and SAFI objects.
cbgpRouteAddrPrefixLen
Represents the length in bits of the network address prefix in the NLRI field.
See Table 3 for a description of the 13 possible entries.
AFIs and SAFIs
Table 2 lists the AFI and SAFI values that can be assigned to or held by the cbgpRouteAfi and cbgpRouteSafi indexes, respectively. Table 2 also displays the network address prefix type that can be held by specific combinations of AFIs and SAFIs. The type of network address prefix that can be carried in a BGP update message depends on the combination of AFIs and SAFIs.
Table 2 AFIs and SAFIs
ipv4(1)
unicast(1)
IPv4 address
ipv4(1)
multicast(2)
IPv4 address
ipv4(1)
vpn(128)
VPN-IPv4 address
ipv6(2)
unicast(1)
IPv6 address
Note
Network Address Prefix Descriptions for the NLRI Field
Table 3 describes the length in bits of the network address prefix in the NLRI field of the cbgpRouteTable. Each entry in the table provides information about the route that is selected by any of the six indexes in Table 1.
Benefits of BGP 4 MIB Support for Per-Peer Received Routes
•
•
Additional References
Related Documents
Configuring MIBs for BGP
BGP commands
Configuring SNMP Support
SNMP Commands
"SNMP Commands" in Cisco IOS Network Management Command Reference
Standards
MIBs
•
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
RFC 1657
BGP-4 MIB
RFC 1771
A Border Gateway Protocol 4 (BGP-4)
RFC 2547
BGP/MPLS VPNs
RFC 2858
Multiprotocol Extensions for BGP-4
Technical Assistance
Feature Information for BGP 4 MIB Support for per-Peer Received Routes
Table 4 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Releases 12.2(1), 12.0(3)S, 12.2(27)SBC, 12.2(33)SRB, 12.2(33)SXH, or later release appear in the table.
For information about a feature in this technology that is not documented here, see the "Cisco BGP Features Roadmap."
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Glossary
AFI—Address Family Identifier. Carries the identity of the network layer protocol that is associated with the network address.
BGP—Border Gateway Protocol. An interdomain routing protocol that exchanges reachability information with other BGP systems. It is defined by RFC 1163, A Border Gateway Protocol (BGP). The current implementation of BGP is BGP Version 4 (BGP4). BGP4 is the predominant interdomain routing protocol that is used on the Internet. It supports CIDR and uses route aggregation mechanisms to reduce the size of routing tables.
MBGP—multiprotocol BGP. An enhanced version of BGP that carries routing information for multiple network layer protocols and IP multicast routes. It is defined in RFC 2858, Multiprotocol Extensions for BGP-4.
MIB—Management Information Base. A group of managed objects that are contained within a virtual information store or database. MIB objects are stored so that values can be assigned to object identifiers and to assist managed agents by defining which MIB objects should be implemented. The value of a MIB object can be changed or retrieved using SNMP or CMIP commands, usually through a GUI network management system. MIB objects are organized in a tree structure that includes public (standard) and private (proprietary) branches.
NLRI—Network Layer Reachability Information. Carries route attributes that describe a route and how to connect to a destination. This information is carried in BGP update messages. A BGP update message can carry one or more NLRI prefixes.
RIB—Routing Information Base (RIB). A central repository of routes that contains Layer 3 reachability information and destination IP addresses or prefixes. The RIB is also known as the routing table.
SAFI—Subsequent Address Family Identifier. Provides additional information about the type of the Network Layer Reachability Information that is carried in the attribute.
SNMP—Simple Network Management Protocol. A network management protocol used almost exclusively in TCP/IP networks. SNMP provides a means to monitor and control network devices and to manage configurations, statistics collection, performance, and security.
snmpwalk—The snmpwalk command is a Simple Network Management Protocol (SNMP) application that is used to communicate with a network entity MIB using SNMP.
VPN—Virtual Private Network. Enables IP traffic to travel securely over a public TCP/IP network by encrypting all traffic from one network to another. A VPN uses a tunnel to encrypt all information at the IP level.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2004-2010 Cisco Systems, Inc. All rights reserved.
