02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

• PA Index (f10BgpM2PathAttrIndex field in various tables) is used to retrieve specific attributes from<br />

<strong>the</strong> PA table. The Next-Hop, RR Cluster-list, Originator ID attributes are not stored in <strong>the</strong> PA Table<br />

and cannot be retrieved using <strong>the</strong> index passed in. These fields are not populated in<br />

f10BgpM2PathAttrEntry, f10BgpM2PathAttrClusterEntry, f10BgpM2PathAttrOriginatorIdEntry.<br />

• F10BgpM2PathAttrUnknownEntry contains <strong>the</strong> optional-transitive attribute details.<br />

• Query <strong>for</strong> f10BgpM2LinkLocalNextHopEntry returns default value <strong>for</strong> Link-local Next-hop.<br />

• RFC 2545 and <strong>the</strong> f10BgpM2Rfc2545Group are not supported.<br />

• An SNMP query will display up to 89 AS paths. A query <strong>for</strong> a larger AS path count will display as<br />

"…" at <strong>the</strong> end of <strong>the</strong> output.<br />

• SNMP set <strong>for</strong> BGP is not supported. For all peer configuration tables<br />

(f10BgpM2Peer<strong>Configuration</strong>Group, f10BgpM2PeerRouteReflectorCfgGroup, and<br />

f10BgpM2PeerAsConfederationCfgGroup), an SNMP set operation will return an error. Only SNMP<br />

queries are supported. In addition, <strong>the</strong> f10BgpM2CfgPeerError, f10BgpM2CfgPeerBgpPeerEntry, and<br />

f10BgpM2CfgPeerRowEntryStatus fields are to hold <strong>the</strong> SNMP set status and are ignored in SNMP<br />

query.<br />

• The AFI/SAFI is not used as an index to <strong>the</strong> f10BgpM2PeerCountersEntry table. The BGP peer's AFI/<br />

SAFI (IPv4 Unicast or IPv6 Multicast) is used <strong>for</strong> various outbound counters. Counters corresponding<br />

to IPv4 Multicast cannot be queried.<br />

• The f10BgpM2[Cfg]PeerReflectorClient field is populated based on <strong>the</strong> assumption that<br />

route-reflector clients are not in a full mesh if BGP client-2-client reflection is enabled and that <strong>the</strong><br />

BGP speaker acting as reflector will advertise routes learned from one client to ano<strong>the</strong>r client. If<br />

disabled, it is assumed that clients are in a full mesh, and <strong>the</strong>re is no need to advertise prefixes to <strong>the</strong><br />

o<strong>the</strong>r clients.<br />

• High CPU utilization may be observed during an SNMP walk of a large BGP Loc-RIB.<br />

• To avoid SNMP timeouts with a large-scale configuration (large number of BGP neighbors and a large<br />

BGP Loc-RIB), <strong>Force10</strong> recommends setting <strong>the</strong> timeout and retry count values to a relatively higher<br />

number. e.g. t = 60 or r = 5.<br />

• To return all values on an snmpwalk <strong>for</strong> <strong>the</strong> f10BgpM2Peer sub-OID, use <strong>the</strong> -C c option, such as<br />

snmpwalk -v 2c -C c -c public .<br />

• An SNMP walk may terminate pre-maturely if <strong>the</strong> index does not increment lexicographically.<br />

<strong>Force10</strong> recommends using options to ignore such errors.<br />

• Multiple BPG process instances are not supported. Thus, <strong>the</strong> F10BgpM2PeerInstance field in various<br />

tables is not used to locate a peer.<br />

• Multiple instances of <strong>the</strong> same NLRI in <strong>the</strong> BGP RIB are not supported and are set to zero in <strong>the</strong><br />

SNMP query response.<br />

• F10BgpM2NlriIndex and f10BgpM2AdjRibsOutIndex fields are not used.<br />

• Carrying MPLS labels in BGP is not supported. F10BgpM2NlriOpaqueType and<br />

f10BgpM2NlriOpaquePointer fields are set to zero.<br />

• 4-byte ASN is supported. f10BgpM2AsPath4byteEntry table contains 4-byte ASN-related<br />

parameters based on <strong>the</strong> configuration.<br />

Traps (notifications) specified in <strong>the</strong> BGP4 MIB draft are not<br />

supported. Such traps (bgpM2Established and bgpM2BackwardTransition) are supported as part of RFC<br />

1657.<br />

474 Border Gateway Protocol (BGP)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!