Validation rule checking if access port is associated with just single network

[mkilar123]

Related Issue(s)

Fixes #695

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

Adding a validation rule which checks if an access interface is mapped to maximum one network:
Checked conditions:

• If the access interface has "access_vlan" defined - it cannot be associated with any network_attach_group
• If the access interface has no "access_vlan" defined - it can be associated with maximum one network_attach_group
• If network_attach_group contains an access port - it can be associated with maximum one network
  The checks also apply to interfaces on TORs

Test Notes

Tests run:

• access interface without "access_vlan" defined referenced max once in network_attach_groups

• access interface with"access_vlan" defined not referenced in any network_attach_groups

• TOR access interface without "access_vlan" defined referenced max once in network_attach_groups

• TOR access interface with"access_vlan" defined not referenced in any network_attach_groups

• access interface with"access_vlan" defined referenced only once in network_attach_groups

• TOR access interface with"access_vlan" defined referenced only once in network_attach_groups

• access interface without "access_vlan" defined referenced multiple times in network_attach_groups

• TOR access interface without "access_vlan" defined referenced multiple times in network_attach_groups

• network_attach_group containing access port referenced by one network

• network_attach_group containing access port referenced by multiple networks

• • network_attach_group without access port referenced by multiple networks

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