Ruijie RG-S29 Series, Command Reference Manual

Page: 848 / 1510

Command Reference NSM Commands
The default weight of the static route is 1. To view the static route of non-default weight, execute the
show ip route weight command. The parameter weight is used to enable WCMP. When there are
load-balanced routes to the destination, the device assigns data flows by their weights. The higher the
weight of a route is, the more data flow the route carries. WCMP limit is generally 32 for routers.
However, WCMP limit varies by switch models for their chipsets support different weights. When the
sum of the weights of load balanced routes is beyond this weight limit, the excessive ones will not
take effect.
Enablement/disablement shows the state of the static route. Disablement means the static route is
not used for forwarding. The forwarding table used the permanent route until administrator deletes it.
When you configure the static route on an Ethernet interface, do not set the next hop as an interface,
for example, ip route 0.0.0.0 0.0.0.0 Fastethernet 0/0. In this case, the switch may consider that all
unknown destination networks are directly connected to the Fastethernet 0/0. So it sends an ARP
request to every destination host, which occupies many CPU and memory resources. It is not
recommended to set the static route to an Ethernet interface.
Association between a static route and a track object can be specified. When association between a
static route and a specified track object is configured and the advertised track object status is inactive,
the static route does not take effect. If the advertised track object status is active, the static route
takes effect based on another status. With association between a static route and a track object, the
third-party status concerned by the track object is mainly used to determine whether the static route
takes effect. Association between a static route and a track object cannot be used for routes with the
permanent attribute.
Association between a static route and an ARP object can be specified. When association between a
static route and an ARP object is configured and the ARP object corresponding to the next hop and
egress of the route does not exist, the static route does not take effect. When the ARP object
corresponding to the next hop and egress of the route exits, the static route takes effect based on
another status. Association between a static route and an ARP object cannot be used for routes with
the permanent attribute.
Association between a static route and a track object cannot be used together with association
between a static route and an ARP object.
Examples
The following example adds a static route to the destination network of 172.16.100.0/24 whose next
hop is 192.168.12.1 and administrative distance is 15.
ip route 172.16.199.0 255.255.255.0 192.168.12.1 155
If the static route has not a specific interface, data flows may be sent thought other interface in case
of interface failure. The following example configures data flows to be sent through fastehternet 0/0
to the destination network of 172.16.100.0/24.
ip route 172.16.199.0 255.255.255.0 fastethernet 0/0 192.168.12.1
Related
Commands N/A
5.5 ip routing
Use this command to enable IP routing in the global configuration mode. Use the no or default form of this