Allow DHCP servers to be configured without having to define a VRF. This is allowed in ND 3.2 and 4.1. #556
Description
Community Note
- 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
Description
When configuring an overlay network in NDFC, you are able to add a DHCP server without having to specify a VRF. This is true for ND 3.2 and 4.1. This is not the case with ND 3.1.
New or Affected modules(s):
- dcnm_network
DCNM version
- V 3.2.x
- V 4.1.x
Potential ansible task config
---
- name: Ensure networks exist with desired parameters
hosts: dcnm_controllers
gather_facts: false
tasks:
- name: Create Network NaC-Net01
tags: nac_net01
cisco.dcnm.dcnm_network:
fabric: nac-fabric-m83
state: replaced
config:
- net_name: NaC-Net01
vlan_name: NaC-Net01_vlan2301
is_l2only: true
net_id: 130001
vlan_id: 2301
deploy: false
dhcp_srvr1_ip: 192.168.12.11
dhcp_srvr2_ip: 192.168.12.12
dhcp_srvr3_ip: 192.168.12.13
register: response
- name: Create Network NaC-Net02
tags: nac_net02
cisco.dcnm.dcnm_network:
fabric: nac-fabric-m83
state: replaced
config:
- net_name: NaC-Net02
vrf_name: NaC-VRF02
net_id: 130002
vlan_id: 2302
gw_ip_subnet: 192.168.12.1/24
deploy: false
dhcp_servers:
- srvr_ip: 192.168.12.20
- srvr_ip: 192.168.12.21
- srvr_ip: 192.168.12.23
register: responseReferences
Additional context
