
•
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).
NOTE: In Dell Networking OS, all newly configured neighbors and peer groups are disabled. To enable a neighbor or peer
group, enter the
neighbor {ip-address | peer-group-name} no shutdown
command.
The following table displays the default values for BGP on Dell Networking OS.
Table 12. BGP Default Values
Item
Default
BGP Neighbor Adjacency changes
All BGP neighbor changes are logged.
Fast External Fallover feature
Disabled
Graceful Restart feature
Disabled
Local preference
100
MED
0
184
Border Gateway Protocol IPv4 (BGPv4)
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...