avd: eos_designs incorrectely adds mtu 9214 for Mlag interface Vlan4094 on CCS-722/750
Issue Summary
switch models 722 and 750 do not support MTU settings per interface, but only global.
for example:
eos_designs adds mtu 9214
to MLAG peer-interface VLAN4094, which is not supported on these platforms.
It throws an error message and MLAG will stay inactive.
Which component(s) of AVD impacted
eos_designs
How do you run AVD ?
Ansible CLI (with virtual-env or native python)
Steps to reproduce
just render mlag setting and push ist against two CCS-750/722 switches.
Relevant log output
interface Vlan4094
description MLAG_PEER
mtu 9214
no autostate
ip address 172.29.31.82/31
access-04-111-01.LAN.MU__14:23:34(config-if-Vl4094)#mtu 9214% Unavailable command (not supported on this hardware platform)
domain-id : ACCESS-04-111_01_02
local-interface : Vlan4094
peer-address : 172.29.31.83
peer-link : Port-Channel51
peer-config :
MLAG Status:
state : Inactive
negotiation status : Connecting
peer-link status : Up
local-int status : Up
system-id : 00:00:00:00:00:00
dual-primary detection : Disabled
dual-primary interface errdisabled : False
### Contributing Guide
- [X] I agree to follow this project's Code of Conduct
About this issue
- Original URL
- State: open
- Created 10 months ago
- Comments: 21 (20 by maintainers)
I guess we should set the global mtu setting instead, to whatever value we have in
p2p_uplinks_mtu
.@kmueller68 Thank you for sharing your concerns here. I agree 100%, but the issue is that this issue concerns a subset of several platform families. It depends on the internal chip. I will talk to the team and get back.
Ok, I can add it under platform settings too. It was too big to fit into the docs, so we opted for an alternative approach with the tooling at hand.