Configure a static route to destination IPv6 address prefixes. 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.
Create static routes for management purposes on VSP 8600 Series:
Use the mgmtRouter VRF context to configure static routes for the OOB port.
default ipv6 route WORD<0-46>
default ipv6 route WORD<0-46> enable next-hop WORD<0-46>
default ipv6 route WORD<0-46> enable port {slot/port[/sub-port]}
default ipv6 route WORD<0-46> enable vlan <1-4059>
default ipv6 route WORD<0-46> preference
default ipv6 route WORD<0-46> preference next-hop WORD<0-46>
default ipv6 route WORD<0-46> preference port {slot/port[/sub-port]}
default ipv6 route WORD<0-46> preference vlan <1-4059>
ipv6 route WORD<0-46> cost <1-65535>
ipv6 route WORD<0-46> cost <1-65535> next-hop WORD<0-46>
ipv6 route WORD<0-46> cost <1-65535> port {slot/port[/sub-port]}
ipv6 route WORD<0-46> cost <1-65535> preference <1-255>
ipv6 route WORD<0-46> cost <1-65535> vlan <1-4059>
ipv6 route WORD<0-46> enable
ipv6 route WORD<0-46> enable next-hop WORD<0-46>
ipv6 route WORD<0-46> enable port {slot/port[/sub-port]}
ipv6 route WORD<0-46> enable vlan <1-4059>
ipv6 route WORD<0-46> preference <1-255>
ipv6 route WORD<0-46> preference <1-255> next-hop WORD<0-46>
ipv6 route WORD<0-46> preference <1-255> port {slot/port[/sub-port]}
ipv6 route WORD<0-46> preference <1-255> vlan <1-4059>
no ipv6 route WORD<0-46>
no ipv6 route WORD<0-46> enable
no ipv6 route WORD<0-46> enable next-hop WORD<0-46>
no ipv6 route WORD<0-46> enable port {slot/port[/sub-port]}
no ipv6 route WORD<0-46> enable vlan <1-4059>
no ipv6 route WORD<0-46> next-hop WORD<0-46>
no ipv6 route WORD<0-46> port {slot/port[/sub-port]}
no ipv6 route WORD<0-46> vlan <1-4059>
The default state for a new static route is enable.
VRF Router 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).