Issue Summary
In a dual stack underlay with ISIS-SR, without setting the v4/v6 node segment indexes with structured_config, AVD is rendering the same index for both, causing a race condition and some routes to be invalid depending on which wins.
Example from customer config output:
#sh run int lo0
interface Loopback0
description ROUTER_ID
ip address
ipv6 address
node-segment ipv4 index 19
node-segment ipv6 index 19
isis enable CORE
isis passive
Manually setting this per node via structured_config is cumbersome. AVD should generate a different index for ipv6, such as node id prefixed with 6.
Which components of AVD are impacted
eos_designs
AVD version
6.1
Ansible version
No response
Python version
No response
How do you run AVD ?
AVD container
Steps to reproduce
Build a dual stack underlay with ipv4 and ipv6 utilizing ISIS-SR.
Relevant log output
Contributing Guide
Issue Summary
In a dual stack underlay with ISIS-SR, without setting the v4/v6 node segment indexes with structured_config, AVD is rendering the same index for both, causing a race condition and some routes to be invalid depending on which wins.
Example from customer config output:
#sh run int lo0
interface Loopback0
description ROUTER_ID
ip address
ipv6 address
node-segment ipv4 index 19
node-segment ipv6 index 19
isis enable CORE
isis passive
Manually setting this per node via structured_config is cumbersome. AVD should generate a different index for ipv6, such as node id prefixed with 6.
Which components of AVD are impacted
eos_designs
AVD version
6.1
Ansible version
No response
Python version
No response
How do you run AVD ?
AVD container
Steps to reproduce
Relevant log output
Contributing Guide