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 2.10.5
DCNM Collection 1.1.1
DCNM version
V 11.5.1
Affected module(s)
dcnm_network
Ansible Playbook
- name: Create a Network and Attach to Switchesdcnm_network:
fabric: multisite_domain_fabricstate: replacedconfig:
- net_name: VLAN10vrf_name: VXLAN_OVERLAYvlan_id: 10gw_ip_subnet: '192.168.10.1/24'net_id: 30000deploy: trueattach:
- ip_address: 10.60.66.131
Debug Output
TASK [Create a Network and Attach to Switches]
*******************************************************************
fatal: [dcpod_dcnm]: FAILED! => {"changed": false, "msg": "Invalid parameters in playbook: ports : Required parameter not found"}
Expected Behavior
The VLAN (and SVI) should be configured on the switch specified without any errors and without the requirement to assign it to a port.
Actual Behavior
The DCNM module has specified that ports is a mandatory attribute for attaching the network to a switch. This behavior does not match the DCNM GUI behavior.
It's also a case of DRY (don't repeat yourself) in that you have to define allowed VLANs on trunk or access VLANs when configuring portchannel, VPC, or other trunk interfaces. So, customers (and myself) prefer defining VLAN members on the actual interfaces and not on the networks.
The text was updated successfully, but these errors were encountered:
@gve-vse-tim As @praveenramoorthy suggested you can leave the ports: setting empty but we will make a change to the module so that the ports: setting is NOT mandatory.
Community Note
Ansible Version and collection version
Ansible 2.10.5
DCNM Collection 1.1.1
DCNM version
Affected module(s)
Ansible Playbook
Debug Output
Expected Behavior
The VLAN (and SVI) should be configured on the switch specified without any errors and without the requirement to assign it to a port.
Actual Behavior
The DCNM module has specified that ports is a mandatory attribute for attaching the network to a switch. This behavior does not match the DCNM GUI behavior.
It's also a case of DRY (don't repeat yourself) in that you have to define allowed VLANs on trunk or access VLANs when configuring portchannel, VPC, or other trunk interfaces. So, customers (and myself) prefer defining VLAN members on the actual interfaces and not on the networks.
The text was updated successfully, but these errors were encountered: