Unexpected Port profile behavior

[reymonlu]

Hello,

This is not a bug but an unintended behaviour when using the raw_eos_cli directive in a profile port with the application on a port-channel

Python

Python 3.8.10 (default, Nov 14 2022, 12:59:47)
[GCC 9.4.0] on linux

AVD

TASK [arista.avd.eos_designs : Verify Requirements]
AVD version 4.4.0

Configuration

port_profiles:
  - profile: PP_CLUSTER-XXX
    parent_profile: PP_DEFAULTS_ACCESS
    enabled: true
    mode: trunk
    vlans: "1128,2128,1050,2050,4001,20,27,38,45,67,89,99,133,149,203,255,314,324,2001"
    raw_eos_cli: switchport vlan translation 3000-3499 dot1q-tunnel 4001
servers:
  - name: MA-XX-SWAG1
    adapters:
    - endpoint_ports: [ te1/0/37,te1/0/37 ]
      switch_ports: [ Ethernet32, Ethernet34 ]
      switches: [ MA-XXX-LEAF-004,MA-XXX-LEAF-004 ]
      description: "VIRT-MA1: INTERCO LEGACY"
      profile: PP_CLUSTER-MA1-MIGRATION
      port_channel:
        channel_id: 48
        description: "VIRT-MA1: INTERCO LEGACY"
        mode: active

Unexpected generation

interface Ethernet32
   description VIRT-XXX: INTERCO LEGACY
   no shutdown
   channel-group 48 mode active
   switchport vlan translation 3000-3499 dot1q-tunnel 4001  -> I do not want it here
!
interface Ethernet34
   description VIRT-XXX: INTERCO LEGACY
   no shutdown
   channel-group 48 mode active
   switchport vlan translation 3000-3499 dot1q-tunnel 4001 -> I do not want it here
!
interface Port-Channel48
   description VIRT-XXX: INTERCO LEGACY_VIRT-XXX: INTERCO LEGACY
   no shutdown
   mtu 9214
   switchport
   switchport trunk allowed vlan 4001,20,27,38,45,67,89,99,133,149,203,255,314,324,2001
   switchport mode trunk
   storm-control broadcast level 1
   storm-control multicast level 1
   storm-control unknown-unicast level 1
   -> I want it here. I know that i could add raw_eos_cli: switchport vlan translation 3000-3499 dot1q-tunnel 4001 under my port-channel configuration but I would prefer to use the profile.

Do you guys know how to do it the right way ?

Thanks

[ClausHolbechArista]

The port_profiles are deep-merged with the adapter config, so you can just add

port_channel:
  raw_eos_cli: whatever

to your port profile. It would require you to have a profiel for portchannels and one for non-portchannels, but we have parent_profile which can help you avoiding to repeat stuff.

[reymonlu]

Hello,

Thank you for your reply. Do you think it would make sense to add the possibility of selective QinQ on profile ports? This would eliminate the need for "raw_eos_cli".

regards

[ClausHolbechArista]

If you need it, someone else will too. So yes a first class feature is better that the workaround. I do not know if this is supported in eos_cli_config_gen yet.

[reymonlu]

I've already looked a bit to avoid going directly via the eos_cli but I haven't found any existing configuration. Should I make a feature request ? I even found it hard to find out how to make selective QinQ in the OS documentation...

[ClausHolbechArista]

Yes please submit an issue for the config you would like to build, and if you have a suggestion on the data model under the adapters, please include that as well.
I cannot promise that we will pick this up, so if you have time and interest in adding some of this, let us know. We are happy to help you get started.

[reymonlu]

I will definitely try ;) It looks like a good opportunitie to start with !

Thank you