![Dell S6000-ON Скачать руководство пользователя страница 174](http://html.mh-extra.com/html/dell/s6000-on/s6000-on_configuration-manual_84557174.webp)
• High CPU utilization may be observed during an SNMP walk of a large BGP Loc-RIB.
• To avoid SNMP timeouts with a large-scale configuration (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
field 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
fields are not used.
• Carrying MPLS labels in BGP is not supported. The
f10BgpM2NlriOpaqueType
and
f10BgpM2NlriOpaquePointer
fields are set to zero.
• 4-byte ASN is supported. The
f10BgpM2AsPath4byteEntry
table contains 4-byte ASN-related
parameters based on the configuration.
• If a received update route matches with a local prefix, then that route is discarded. This behavior
results from an incorrect BGP configuration. To overcome this issue, you can trigger a route refresh
after you properly configure BGP.
Traps (notifications) specified in the BGP4 MIB draft
<draft-ietf-idr-bgp4–mibv2–05.txt>
are not
supported. Such traps (
bgpM2Established
and
bgpM2BackwardTransition
) are supported as part of RFC
1657.
Configuration Information
The software supports BGPv4 as well as the following:
• deterministic multi-exit discriminator (MED) (default)
• a path with a missing MED is treated as worst path and assigned an MED value of (0xffffffff)
• the community format follows RFC 1998
• delayed configuration (the software at system boot reads the entire configuration file prior to sending
messages to start BGP peer sessions)
The following are not yet supported:
• auto-summarization (the default is no auto-summary)
• synchronization (the default is no synchronization)
BGP Configuration
To enable the BGP process and begin exchanging information, assign an AS number and use commands
in ROUTER BGP mode to configure a BGP neighbor.
By default, BGP is disabled.
By default, Dell Networking OS compares the MED attribute on different paths from within the same AS
(the
bgp always-compare-med
command is not enabled).
174
Border Gateway Protocol IPv4 (BGPv4)
Содержание S6000-ON
Страница 1: ...Dell Configuration Guide for the S6000 ON System 9 9 0 0 ...
Страница 505: ...Figure 60 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 505 ...
Страница 508: ...Figure 62 Inspecting a LAG Port on BRAVO Using the show interface Command 508 Link Aggregation Control Protocol LACP ...
Страница 509: ...Figure 63 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 509 ...
Страница 552: ...mac address table static multicast mac address vlan vlan id output range interface 552 Microsoft Network Load Balancing ...
Страница 557: ...Figure 80 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 557 ...
Страница 558: ...Figure 81 Configuring PIM in Multiple Routing Domains 558 Multicast Source Discovery Protocol MSDP ...
Страница 562: ...Figure 83 MSDP Default Peer Scenario 1 562 Multicast Source Discovery Protocol MSDP ...
Страница 563: ...Figure 84 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 563 ...
Страница 564: ...Figure 85 MSDP Default Peer Scenario 3 564 Multicast Source Discovery Protocol MSDP ...
Страница 665: ...Policy based Routing PBR 665 ...
Страница 672: ...ip pim bsr border Remove candidate RP advertisements clear ip pim rp mapping 672 PIM Sparse Mode PIM SM ...
Страница 818: ...Figure 110 Single and Double Tag TPID Match 818 Service Provider Bridging ...
Страница 819: ...Figure 111 Single and Double Tag First byte TPID Match Service Provider Bridging 819 ...
Страница 995: ...Figure 140 Setup OSPF and Static Routes Virtual Routing and Forwarding VRF 995 ...