Administrator Guide

BGP4 Management Information Base (MIB)
The FORCE10-BGP4-V2-MIB enhances Dell Networking OS BGP management information base (MIB) support with many new
simple network management protocol (SNMP) objects and notications (traps) dened in
draft-ietf-idr-bgp4-mibv2-05. To see
these enhancements, download the MIB from the Dell website.
NOTE: For the
Force10-BGP4-V2-MIB
and other MIB documentation, refer to the Dell iSupport web page.
Important Points to Remember
The f10BgpM2AsPathTableEntry table, f10BgpM2AsPathSegmentIndex, and f10BgpM2AsPathElementIndex are used to retrieve
a particular ASN from the AS path. These indices are assigned to the AS segments and individual ASN in each segment starting
from 0. For example, an AS path list of {200 300 400} 500 consists of two segments: {200 300 400} with segment index 0 and
500 with segment index 1. ASN 200, 300, and 400 are assigned 0, 1, and 2 element indices in that order.
Unknown optional transitive attributes within a given path attribute (PA) are assigned indices in order. These indices correspond
to the f10BgpM2PathAttrUnknownIndex eld in the f10BgpM2PathAttrUnknownEntry table.
Negotiation of multiple instances of the same capability is not supported. F10BgpM2PeerCapAnnouncedIndex and
f10BgpM2PeerCapReceivedIndex are ignored in the peer capability lookup.
Congure inbound BGP soft-reconguration on a peer for f10BgpM2PrexInPrexesRejected to display the number of prexes
ltered due to a policy. If you do enable BGP soft-reconfig, the denied prexes are not accounted for.
F10BgpM2AdjRibsOutRoute stores the pointer to the NLRI in the peer's Adj-Rib-Out.
PA Index (f10BgpM2PathAttrIndex eld in various tables) is used to retrieve specic attributes from the PA table. The Next-Hop,
RR Cluster-list, and Originator ID attributes are not stored in the PA Table and cannot be retrieved using the index passed
in command. These elds are not populated in f10BgpM2PathAttrEntry, f10BgpM2PathAttrClusterEntry, and
f10BgpM2PathAttrOriginatorIdEntry.
F10BgpM2PathAttrUnknownEntry contains the optional-transitive attribute details.
Query for f10BgpM2LinkLocalNextHopEntry returns the default value for Link-local Next-hop.
RFC 2545 and the f10BgpM2Rfc2545Group are not supported.
An SNMP query displays up to 89 AS paths. A query for a larger AS path count displays as "" at the end of the output.
SNMP set for BGP is not supported. For all peer conguration tables (f10BgpM2PeerCongurationGroup,
f10BgpM2PeerRouteReectorCfgGroup, and f10BgpM2PeerAsConfederationCfgGroup), an SNMP set operation returns an
error. Only SNMP queries are supported. In addition, the f10BgpM2CfgPeerError, f10BgpM2CfgPeerBgpPeerEntry, and
f10BgpM2CfgPeerRowEntryStatus elds are to hold the SNMP set status and are ignored in SNMP query.
The AFI/SAFI is not used as an index to the f10BgpM2PeerCountersEntry table. The BGP peer’s AFI/ SAFI (IPv4 Unicast or IPv6
Multicast) is used for various outbound counters. Counters corresponding to IPv4 Multicast cannot be queried.
The f10BgpM2[Cfg]PeerReectorClient eld is populated based on the assumption that route-reector clients are not in a full
mesh if you enable BGP client-2-client reflection and that the BGP speaker acting as reector advertises routes
learned from one client to another client. If disabled, it is assumed that clients are in a full mesh and there is no need to advertise
prexes to the other clients.
High CPU utilization may be observed during an SNMP walk of a large BGP Loc-RIB.
To avoid SNMP timeouts with a large-scale conguration (large number of BGP neighbors and a large BGP Loc-RIB), Dell
Networking recommends setting the timeout and retry count values to a relatively higher number. For example, t = 60 or r = 5.
To return all values on an snmpwalk for the f10BgpM2Peer sub-OID, use the -C c option, such as snmpwalk -v 2c -C c -
c public<IP_address><OID>
.
An SNMP walk may terminate pre-maturely if the index does not increment lexicographically. Dell Networking recommends using
options to ignore such errors.
Multiple BPG process instances are not supported. Thus, the f10BgpM2PeerInstance eld in various tables is not used to locate
a peer.
Multiple instances of the same NLRI in the BGP RIB are not supported and are set to zero in the SNMP query response.
The f10BgpM2NlriIndex and f10BgpM2AdjRibsOutIndex elds are not used.
Carrying MPLS labels in BGP is not supported. The f10BgpM2NlriOpaqueType and f10BgpM2NlriOpaquePointer elds are set to
zero.
4-byte ASN is supported. The f10BgpM2AsPath4byteEntry table contains 4-byte ASN-related parameters based on the
conguration.
Border Gateway Protocol IPv4 (BGPv4)
163