Fix for fex

[skaszlik]

The current "310" rule checks for breakout interfaces, but the algorithm also matches FEX interfaces (Ethernet[101-199]/1/[1-99]). The proposed solution is to use regex to determine if the interface is a FEX; if it is, then skip processing that interface.

Related Issue(s)

#203

Related Collection Role

• cisco.nac_dc_vxlan.validate
• cisco.nac_dc_vxlan.dtc.create
• cisco.nac_dc_vxlan.dtc.deploy
• cisco.nac_dc_vxlan.dtc.remove
• other

Related Data Model Element

• vxlan.fabric
• vxlan.global
• vxlan.topology
• vxlan.underlay
• vxlan.overlay
• vxlan.overlay_extensions
• vxlan.policy
• vxlan.multisite
• defaults.vxlan
• other

Proposed Changes

Test Notes

Cisco Nexus Dashboard Version

Checklist

• Latest commit is rebased from develop with merge conflicts resolved
• New or updates to documentation has been made accordingly
• Assigned the proper reviewers

[miguecor]

@skaszlik you could use the following regex:

• For ethernet interfaces with breakout:
  ^(?:Ethernet)(?:[1-9]|1[0-6])\/(?:[1-9]|[1-9]\d|[1-4]\d{2}|50[0-9]|51[0-2])(?:\/[1-4])?$
• For FEX interfaces:
  ^(?:Ethernet)(?:10[1-9]|1[1-9]\d)\/1\/(?:[1-9]|[1-3]\d|4[0-8])$

These regex will match the exact FEX, slot, port number ranges available for each case.