Users Guide

NOTE: Weight for a static route can be added only for
the destination address and not for the route pointing to
destination a interface.
Defaults None
Command Modes CONFIGURATION
Command History
This guide is platform-specific. For command information about other platforms, see
the relevant Dell Networking OS Command Line Reference Guide.
Version Description
9.10(0.1) Introduced on the S6010-ON and S4048T-ON.
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) Added support for VRF. Also included the weight parameter to
support weighted ECMP feature. Introduced on the S6000-ON.
9.2(1.0) Introduced on the Z9500.
9.0.0.0 Introduced on the Z9000.
8.3.19.0 Introduced on the S4820T.
8.3.7.0 Introduced on the S4810.
8.5.1.0 Added support for 4-port 40G line cards on the E-Series.
8.2.1.0 Introduced on the E-Series.
7.8.1.0 Introduced on the C-Series and S-Series.
7.4.1.0 Introduced on the E-Series.
Usage Information
When the interface goes down, Dell Networking OS withdraws the route. The route is
re-installed, by Dell Networking OS, when the interface comes back up. When a
recursive resolution is “broken,” Dell Networking OS withdraws the route. The route is
re-installed, by Dell Networking OS, when the recursive resolution is satisfied.
After an IPv6 static route interface is created, if an IP address is not assigned to a peer
interface, the peer must be manually pinged to resolve the neighbor information.
You can specify a weight for an IPv4 or IPv6 static route. If the weight value of a path is
0, then that path is not used for forwarding when weighted ECMP is in effect. Also, if a
path corresponding to a static route (destination) has a non-zero weight assigned to it
and other paths do not have any weight configured, then regular ECMP is used for
forwarding.
You can specify the weight value only to destination address and not on the egress
port.
IPv6 Basics 1075