Configure a static route for a VRF. Use this command to:
Create static routes for data traffic in a specific VRF context for any platform.
Create static routes for a VRF associated with a Segmented Management Instance CLIP interface.
default ip route {A.B.C.D} {A.B.C.D} {A.B.C.D}
default ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} dynamic
default ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} enable
default ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} local-next-hop enable
default ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} preference
ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} enable
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 <0-64>
ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} preference <1-255>
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>
ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} weight <1-65535> local-next-hop enable
ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} weight <1-65535> name <0-64>
ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} weight <1-65535> next-hop-vrf WORD<1-16>
ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} weight <1-65535> preference <1-255>
no ip route {A.B.C.D} {A.B.C.D} {A.B.C.D}
no ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} dynamic
no ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} dynamic next-hop-vrf WORD<1-16>
no ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} enable
no ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} enable next-hop-vrf WORD<1-16>
no ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} local-next-hop enable
no ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} next-hop-vrf WORD<1-16>
no ip route {A.B.C.D} {A.B.C.D} {A.B.C.D} preference
Note
Do not configure a static interface subnet route with a weight of 1.
This command does not apply to all hardware platforms.
None
VRF Router Configuration