Skip to content

IPv6 Route

IPv6 routes provide manually configured routing entries for IPv6 destination prefixes, supporting VRF-aware deployments on NX-OS for both default and non-default routing instances. Each route can specify one or more next-hop addresses with configurable preferences, tags, route names, and object tracking for conditional route installation based on reachability. Static route BFD sessions (ipv6 route static bfd) are configured per VRF under ipv6_route_static_bfds and track next-hop reachability through a pinned interface. IPv6 routes are commonly used for default gateway configuration, stub network reachability, and management traffic steering in dual-stack or IPv6-only network environments.

IPv6 routes provide manually configured routing entries for IPv6 destination prefixes, supporting VRF-aware deployments on NX-OS for both default and non-default routing instances. Each route can specify one or more next-hop addresses with configurable preferences, tags, route names, and object tracking for conditional route installation based on reachability. IPv6 routes are commonly used for default gateway configuration, stub network reachability, and management traffic steering in dual-stack or IPv6-only network environments.

NameTypeConstraintMandatoryDefault Value
devicesListdevicesNo
device_groupsListdevice_groupsNo
globalClassglobalNo
templatesListtemplatesNo

NameTypeConstraintMandatoryDefault Value
configurationClassconfigurationNo

NameTypeConstraintMandatoryDefault Value
configurationClassconfigurationNo

NameTypeConstraintMandatoryDefault Value
configurationClassconfigurationNo

NameTypeConstraintMandatoryDefault Value
configurationClassconfigurationNo

NameTypeConstraintMandatoryDefault Value
routingClassroutingNo

NameTypeConstraintMandatoryDefault Value
ipv6_routesListipv6_routesNo
ipv6_route_static_bfdsListipv6_route_static_bfdsNo

NameTypeConstraintMandatoryDefault Value
ipv6_routesListipv6_routesNo

ipv6_routes (nxos.devices.configuration.routing)

Section titled “ipv6_routes (nxos.devices.configuration.routing)”
NameTypeConstraintMandatoryDefault Value
vrfStringNo
prefixIPYes
preferenceIntegermin: 1, max: 255No
tagIntegermin: 0, max: 4294967295No
next_hopsListnext_hopsNo

ipv6_routes (nxos.devices.configuration.routing)

Section titled “ipv6_routes (nxos.devices.configuration.routing)”
NameTypeConstraintMandatoryDefault Value
vrfStringNo
prefixStringYes
preferenceIntegermin: 1, max: 255No
tagIntegermin: 0, max: 4294967295No
next_hopsListnext_hopsNo

ipv6_route_static_bfds (nxos.devices.configuration.routing)

Section titled “ipv6_route_static_bfds (nxos.devices.configuration.routing)”
NameTypeConstraintMandatoryDefault Value
vrfStringNo
interface_typeChoiceethernet, loopback, mgmt, port-channel, vlan, vniYes
interface_idAnyString or Integer[min: 0]Yes
next_hopIPYes

next_hops (nxos.devices.configuration.routing.ipv6_routes)

Section titled “next_hops (nxos.devices.configuration.routing.ipv6_routes)”
NameTypeConstraintMandatoryDefault Value
interface_typeChoiceethernet, loopback, mgmt, port-channel, vlan, vniNo
interface_idAnyString or Integer[min: 0]No
addressIPNo
vrfStringNo
trackIntegermin: 0, max: 4294967295No
preferenceIntegermin: 0, max: 255No
tagIntegermin: 0, max: 4294967295No
nameStringNo

Example 1: IPv6 default route for management VRF

nxos:
devices:
- name: LEAF1
configuration:
routing:
ipv6_routes:
- vrf: management
prefix: "::/0"
next_hops:
- address: "2001:db8:ffff::1"
name: MGMT-GW-V6

Example 2: Multiple IPv6 routes — default VRF and tenant VRF with tagged routes

nxos:
devices:
- name: SPINE1
configuration:
routing:
ipv6_routes:
# Default VRF — IPv6 default route
- prefix: "::/0"
tag: 500
next_hops:
- address: "2001:db8:ffff::1"
name: UPSTREAM-V6-GW
# Route to IPv6 monitoring infrastructure
- vrf: management
prefix: "2001:db8:100::/48"
next_hops:
- address: "2001:db8:ffff::1"
name: TO-INFRA-V6

Example 3: VRF-aware IPv6 routes on a border leaf with floating backup and object tracking

nxos:
devices:
- name: BORDER-LEAF1
configuration:
routing:
ipv6_routes:
# Tenant VRF BLUE — dual next-hop with failover
- vrf: BLUE
prefix: "::/0"
tag: 1000
next_hops:
- address: "2001:db8:1::1"
name: FW-PRIMARY-V6
track: 10
- address: "2001:db8:1::2"
name: FW-SECONDARY-V6
preference: 10
track: 11
# Tenant VRF GREEN — route to shared services
- vrf: GREEN
prefix: "2001:db8:100::/48"
next_hops:
- address: "2001:db8:2::1"
name: TO-SHARED-SVC-V6
# Management VRF default
- vrf: management
prefix: "::/0"
next_hops:
- address: "2001:db8:ffff::1"

Example 4: IPv6 static BFD session for a next hop in a tenant VRF

nxos:
devices:
- name: BORDER-LEAF1
configuration:
feature:
bfd: true
routing:
ipv6_route_static_bfds:
- vrf: BLUE
interface_type: ethernet
interface_id: 1/10
next_hop: "2001:db8:10::2"

Example 1: IPv6 default route for management VRF

nxos:
devices:
- name: LEAF1
configuration:
routing:
ipv6_routes:
- vrf: management
prefix: "::/0"
next_hops:
- address: "2001:db8:ffff::1"
name: MGMT-GW-V6

Example 2: Multiple IPv6 routes — default VRF and tenant VRF with tagged routes

nxos:
devices:
- name: SPINE1
configuration:
routing:
ipv6_routes:
# Default VRF — IPv6 default route
- prefix: "::/0"
tag: 500
next_hops:
- address: "2001:db8:ffff::1"
name: UPSTREAM-V6-GW
# Route to IPv6 monitoring infrastructure
- vrf: management
prefix: "2001:db8:100::/48"
next_hops:
- address: "2001:db8:ffff::1"
name: TO-INFRA-V6

Example 3: VRF-aware IPv6 routes on a border leaf with floating backup and object tracking

nxos:
devices:
- name: BORDER-LEAF1
configuration:
routing:
ipv6_routes:
# Tenant VRF BLUE — dual next-hop with failover
- vrf: BLUE
prefix: "::/0"
tag: 1000
next_hops:
- address: "2001:db8:1::1"
name: FW-PRIMARY-V6
track: 10
- address: "2001:db8:1::2"
name: FW-SECONDARY-V6
preference: 10
track: 11
# Tenant VRF GREEN — route to shared services
- vrf: GREEN
prefix: "2001:db8:100::/48"
next_hops:
- address: "2001:db8:2::1"
name: TO-SHARED-SVC-V6
# Management VRF default
- vrf: management
prefix: "::/0"
next_hops:
- address: "2001:db8:ffff::1"