Reference Guide

● match ip address
● set community
● set local-preference
● set metric
● set next-hop
● set origin
● set weight
If the route map is not configured, the default is deny (to drop all routes).
Defaults Not configured.
Command Modes ROUTER BGP
Command
History
This guide is platform-specific. For command information about other platforms, see the relevant Dell
EMC Networking OS Command Line Reference Guide.
Version Description
9.10(0.1) Introduced on the S6010-ON and S4048T-ON.
9.10(0.0) Introduced on the S3148.
9.10(0.0) Introduced on the S6100-ON.
9.8(2.0) Introduced on the S3100 series.
9.8(1.0) Introduced on the Z9100–ON.
9.8(0.0P5) Introduced on the S4048-ON.
9.8(0.0P2) Introduced on the S3048-ON.
9.7(0.0) Introduced on the S6000–ON.
9.2(1.0) Introduced on the Z9500.
9.0.2.0 Introduced on the S6000.
8.3.19.0 Introduced on the S4820T.
8.3.11.1 Introduced on the Z9000.
8.3.7.0 Introduced on the S4810.
8.3.1.0 Introduced the ability to substitute IGP cost for MED when a peer/peer-group
outbound route-map is set as internal.
7.8.1.0 Introduced on the S-Series.
7.7.1.0 Introduced on the C-Series.
Usage
Information
You can use the redistribute command to advertise the IGP cost as the MED on redistributed
routes. When you set the route-map with metric-type internal and applied outbound to an EBGP peer/
peer-group, the advertised routes corresponding to those peer/peer-groups have the IGP cost set as
MED.
If you do not configure the default-metric command, in addition to the redistribute command,
or there is no route map to set the metric, the metric for redistributed static and connected is “0”.
To redistribute the default route (0.0.0.0/0), configure the neighbor default-originate
command.
As BGP does not query next-hop information corresponding to locally originated routes, a local route with
an unreachable next-hop is chosen as the best route.
When a combination of locally originated and peer originated routes occurs, both these routes will exist
in the RTM. However, only the best route is kept active in the RTM and the remaining route is rendered
in-active.
394 Border Gateway Protocol