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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Ansible Version and collection version
ansible [core 2.17.2]
dcnm collection ver 3.4.3
DCNM version
12.2.2.238
Affected module(s)
dcnm_vrf
Ansible Playbook
- name: Create and attach VRFs to switches in {{ defaults.msd.fabric_name }} fabriccisco.dcnm.dcnm_vrf:
fabric: '{{ defaults.msd.fabric_name }}'state: '{{ state | default("merged") }}'config: '{{ extra_vrfs }}'tags: vrfs
This is a sample VRF. Border leaves are 154.16 and 154.17
The task is still successful:
PLAY RECAP *****************************************************************************************************************************************************************************************************
cpoc-xxxxxx : ok=3 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
CSCwh23123 describes what that "Failed" message actually means. The configuration between the two peers is inconsistent.
Same Failed message then using the state deleted.
Expected Behavior
Changes to the VRF are added to the NDFC DB and finally pushed to the switches
Actual Behavior
VRF is configured in the NDFC DB but not attached to the border leaf that renders the error. Because it is not attached, configuration is consistent between the switch and NDFC DB and it will never be pushed to the leaf.
Steps to Reproduce
Ran into this issue while trying to create a new attachment for the VRF.
Create a VRF and delete it. Run the task while the VRF is in Delete Holddown state in the border leaf.
BSLEAF101# show vrf
VRF-Name VRF-ID State Reason
default 1 Up --
egress-loadbalance-resolution- 3 Up --
guest 17 Down Delete Holddown
infra 12 Up --
iot 18 Down Delete Holddown
management 2 Up --
References
The text was updated successfully, but these errors were encountered:
Community Note
Ansible Version and collection version
ansible [core 2.17.2]
dcnm collection ver 3.4.3
DCNM version
Affected module(s)
Ansible Playbook
This is a sample VRF. Border leaves are 154.16 and 154.17
The playbook as such is more or less irrelevant. Anything that creates a VRF would work.
Debug Output
CSCwh23123 describes what that "Failed" message actually means. The configuration between the two peers is inconsistent.
Same Failed message then using the state deleted.
Expected Behavior
Changes to the VRF are added to the NDFC DB and finally pushed to the switches
Actual Behavior
VRF is configured in the NDFC DB but not attached to the border leaf that renders the error. Because it is not attached, configuration is consistent between the switch and NDFC DB and it will never be pushed to the leaf.
Steps to Reproduce
Ran into this issue while trying to create a new attachment for the VRF.
Create a VRF and delete it. Run the task while the VRF is in Delete Holddown state in the border leaf.
References
The text was updated successfully, but these errors were encountered: