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
when using cisco.cml.cml_lab_facts and cisco.cml.inventory playbooks, The resulted facts doesn't have ipv4_address data:
we have two nodes in our topology:
1.nxos
2.external connector
On nxos we have configured ip address on management interface that should come as part of facts of nxos node. which is not coming.
IP address was configured via DHCP from the external connector.
And also the /labs/{ lab_id }/layer3_addresses endpoint also does not return this data.
R1(config)# show ip interface brief vrf management IP Interface Status for VRF "management"(2)Interface IP Address Interface Statusmgmt0 192.168.255.217 protocol-up/link-up/admin-up R1(config)#
The CML layer3_addresses endpoint can sometimes stop working and will cause the behavior you are seeing. Restarting the CML services will usually restore the L3 functionality.
OS / ENVIRONMENT
CML version - 2.5.1
virl2-client-2.6.1
STEPS TO REPRODUCE
when using cisco.cml.cml_lab_facts and cisco.cml.inventory playbooks, The resulted facts doesn't have ipv4_address data:
we have two nodes in our topology:
1.nxos
2.external connector
On nxos we have configured ip address on management interface that should come as part of facts of nxos node. which is not coming.
IP address was configured via DHCP from the external connector.
And also the /labs/{ lab_id }/layer3_addresses endpoint also does not return this data.
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: