You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Currently, when using ToR switches in the NDFC framework, ToR pairing must be configured manually via the GUI. This is the only step in the workflow that cannot be automated when working with ToR switches.
Problem:
The framework does not support ToR pairing forpre-provisioned switches (i.e., switches definedin the fabric before POAP).
Even if ToR pairing is included in the fabric intent, it cannot be applied until after the switches have been POAP’d.
This creates a challenge when trying to build a fully automated and scalable solution that works for both pre-provisioned and POAP’d devices.
Would this be a new feature requiring a new role?
Enable support forToR pairing of pre-provisioned switchesin NDFC, ideally by allowing intent-based pairing configuration to be staged and automatically pushed once the switch is POAP’d.
Which section of the data model is the new feature related?
vxlan.topology
Would this be a new feature requiring a new addition to the data model?
Yes, it should be defined in the vxlan.topology.
New or Affected Documentation for New Feature
Potential Ansible Task Config
create
Ansible Version
Ansible Collection Versions
Cisco NDFC Version
12.2.2.241
Cisco NX-OS Version
The text was updated successfully, but these errors were encountered:
Which role would this new feature be associated?
cisco.nac_dc_vxlan.dtc.create
New feature description:
Would this be a new feature requiring a new role?
Which section of the data model is the new feature related?
vxlan.topology
Would this be a new feature requiring a new addition to the data model?
Yes, it should be defined in the vxlan.topology.
New or Affected Documentation for New Feature
Potential Ansible Task Config
create
Ansible Version
Ansible Collection Versions
Cisco NDFC Version
Cisco NX-OS Version
The text was updated successfully, but these errors were encountered: