You can configure routing switches with a static default route, or they can learn it through a dynamic routing protocol. Use this command to:
Create static routes for data traffic in the GRT.
Create static routes for management purposes on VSP 8600 Series:
Use the default VRF context to configure static routes in the GRT for the inband VLAN or loopback interface.
default ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} [dynamic] [enable] [local-next-hop enable] [name] [preference]
ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} enable [next-hop-vrf WORD<1-16>]
ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} local-next-hop enable
ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} name WORD<0-64>
ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} preference <1-255> [next-hop-vrf WORD<1-16>]
ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} weight <1-65535> [local-next-hop enable] [name WORD<0-64>] [next-hop-vrf WORD<1-16>] [preference <1-255>]
no ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} [dynamic] [enable] [local-next-hop enable] [name] [next-hop-vrf WORD<1-16>] [preference]
Note
Do not configure a static interface subnet route with a weight of 1.
None
Global Configuration
The name parameter is not supported on VSP 8600 Series.
VSP 8600 Series uses the routing stack to create static routes for data traffic as well as management purposes. For all other platforms, static routes for the management OOB and management VLAN, if supported, must use the Segmented Management Instance. For more information, see VOSS User Guide. The management CLIP can use the Segmented Management Instance or routes in the associated VRF routing table manager (RTM).