Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

vrf lite configuration does not honor the auto deploy both flag #65

Closed
dsx1123 opened this issue Apr 30, 2021 · 0 comments
Closed

vrf lite configuration does not honor the auto deploy both flag #65

dsx1123 opened this issue Apr 30, 2021 · 0 comments
Assignees

Comments

@dsx1123
Copy link
Collaborator

dsx1123 commented Apr 30, 2021

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

Ansible Version and collection version

DCNM version

  • V 11.5.1

Affected module(s)

  • dcnm_vrf

Ansible Playbook

# Copy-paste your anisble playbook here 
---
- name: Configure external connectivity
  hosts: dcnm
  gather_facts: false
  vars_files:
    - vars.yml
  collections:
    - cisco.dcnm
  tasks:
    - name: external | attach vrf blue to border leaf {{ border[0].name }}
      dcnm_vrf:
        fabric: "{{ fabric }}"
        config:
          - vrf_name: blue
            attach:
              - ip_address: "{{ border[0].ip }}"
                vrf_lite:
                  - peer_vrf: blue

And vrf lite configuration of fabric is set as below:
image

Debug Output

debug output

Expected Behavior

external fabric that connected to border should also be deployed

Actual Behavior

external fabric is not deployed

Steps to Reproduce

  1. set vrf lite setting of fabric as below
    image
  2. run the playbook
  3. check the deployment result, the auto deploy is set to false which cause the external fabric is not deployed:
    image

References

Checked the code, looks like we did not get auto deploy flag from fabric, but instead, it is set to false no matter what:

                    vrflite_con['VRF_LITE_CONN'][0]['IPV6_NEIGHBOR']=a_l['neighbor_ipv6']
                    vrflite_con['VRF_LITE_CONN'][0]['AUTO_VRF_LITE_FLAG']='false'
                    vrflite_con['VRF_LITE_CONN'][0]['PEER_VRF_NAME']=a_l['peer_vrf']
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants