Multiple Static Routes?

[theotherguy2175]

Looking at the examples of AVD for the static_routes example it only ever shows 1 route. But I tried doing this code to get many static routes:

ipv6_static_routes:

• vrf: default
  destination_address_prefix:
  • ::/0
  • 2001::32
    gateway:
  • 2001:xx
  • 2001:xx

And got this error and generated config:

[WARNING]: [border102.iub]: 'Validation Error: ipv6_static_routes[0].gateway': ['2001:xx', '2001:xx'] is not of type 'str'

ipv6 route ['::/0', '2001::32'] ['2001:xx', '2001:xx']

Also on another note this code is for ipv6, which does generate config,

however I have identical config for ipv4, and it never generates 1 or more static routes. Just the default route I defined in my Fabric.yml. Any reason why?

[ClausHolbechArista]

Hi @theotherguy2175,

Please refer to the documentation here and make sure to adhere to the data types described.

Your example should look something like:

ipv6_static_routes:
  - vrf: default
    destination_address_prefix: "::/0
    gateway: "2001:xx"
  - vrf: default
    destination_address_prefix: "2001::32"
    gateway: "2001:xx"

[theotherguy2175]

Thanks! That worked great. Do you know why IPv4 wouldn't work with the same config?

[theotherguy2175]

I figured it out. I removed the mgmt_gateway config from fabric and now it works.

[ClausHolbechArista]

The mgmt_gateway feature interferes with your static_routes key, because static_routes is an eos_cli_config_gen data model.

Read more about the variable ordering and custom_structured_configuration_ here: https://avd.arista.com/4.3/roles/eos_designs/docs/how-to/custom-structured-configuration.html.

Specifically this snip mentions this issue:

A caveat is that in the inventory, group_vars, host_vars,… you can define some variables that are 
used by eos_designs and others that are used by eos_cli_config_gen roles. And while it is perfectly 
acceptable, the behavior can sometimes be confusing. If the key name for an eos_cli_config_gen 
variable in the variable files is the same as one of the key name of a variable generated by 
eos_designs steps, only the value from eos_designs step will be configured. However if there is no 
clash, then the value of the variable will be the one defined in the variable files.

[theotherguy2175]

That also helped out a ton. I was going crazy trying to figure out the hierarchy.