Feature |
Product |
Release introduced |
---|---|---|
For configuration details, see VOSS User Guide. |
||
Static routing |
5520 Series |
VOSS 8.2.5 |
VSP 4450 Series |
VSP 4000 4.0 |
|
VSP 4900 Series |
VOSS 8.1 |
|
VSP 7200 Series |
VOSS 4.2.1 |
|
VSP 7400 Series |
VOSS 8.0 |
|
VSP 8200 Series |
VSP 8200 4.0 |
|
VSP 8400 Series |
VOSS 4.2 |
|
VSP 8600 Series |
VSP 8600 4.5 |
|
XA1400 Series |
VOSS 8.0.50 |
Note
VSP 8600 Series uses the Layer 3 configuration for management static routes as well as for packet forwarding. For all other platforms, management static routes must use Segmented Management.
A static route is a route to a destination IP address that you manually create.
Create static routes to enhance network stability. Use the local next hop option to configure a static route with or without local next hop.
You can configure static routes with a next hop that is not directly connected, but that hop must be reachable. Otherwise, the static route is not enabled.
Layer 3 redundancy supports only address resolution protocol (ARP) and static route. Static ARP must configure the nonlocal next-hop of static routes. No other dynamic routing protocols provide nonlocal next-hop.
Note
Static ARP entries are not supported for NLB Unicast or NLB Multicast operations.
You can use a default static route to specify a route to all networks for which no explicit routes exist in the forwarding information base or the routing table. This route has a prefix length of zero (RFC1812). You can configure the switch with a route through the IP static routing table.
To create a default static route, you must configure the destination address and subnet mask to 0.0.0.0.
Note
Do not configure static routes on a DvR Leaf node unless the configuration is for reachability to a management network using a brouter port.
Also, configuring the preference of static routes is not supported on a Leaf node.