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.
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
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).