Dell Command Line Reference Guide for the S4048–ON System



Redistribute routes into BGP.

redistribute {connected | static} [route-map map-name]

To disable redistribution, use the no redistribution {connected | static} command.

Enter the keyword connected to redistribute routes from physically connected interfaces.

Enter the keyword static to redistribute manually configured routes.

These routes are treated as incomplete routes.

route-map map-name

(OPTIONAL) Enter the keyword route-map then the name of an established route map.

Only the following ROUTE-MAP mode commands are supported:

If the route map is not configured, the default is deny (to drop all routes).

Not configured.
Command Modes
Command History

This guide is platform-specific. For command information about other platforms, see the relevant Dell EMC Networking OS Command Line Reference Guide.

Introduced on the S6010-ON and S4048T-ON.
Introduced on the S3148.
Introduced on the S6100-ON.
Introduced on the S3100 series.
Introduced on the Z9100–ON.
Introduced on the S4048-ON.
Introduced on the S3048-ON.
Introduced on the S6000–ON.
Introduced on the Z9500.
Introduced on the S6000.
Introduced on the S4820T.
Introduced on the Z9000.
Introduced on the S4810.
Introduced the ability to substitute IGP cost for MED when a peer/peer-group outbound route-map is set as internal.
Introduced on the S-Series.
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 (, 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.

It is possible to keep only one locally originated route in the BGP database. Network command has preference over the re-distributed routes. When the locally originated route is no longer present in the database the other route is automatically installed.

Related Commands

Rate this content

Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\