We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
show ip interface brief command properly shows the applied ip address virtual command for an interface configured as such, but eos_facts does.
show ip interface brief
eos_facts
2.10.5
<empty>
Arista EOS 4.22.6M, 4.23.5M, & 4.24.3M
interface config:
interface Vlan100 description test ip address virtual 10.0.0.1/16
- name: eos_facts arista.eos.eos_facts: gather_subset: all gather_network_resources: all
<omitted output before this> ansible_net_interfaces: Vlan100: bandwidth: 0 description: test ipv4: address: 10.0.0.1 masklen: 16 lineprotocol up macaddress: aa:aa:aa:aa:aa:aa mtu: 1500 operstatus: up type: routed
<omitted output before this> ansible_net_interfaces: Vlan100: bandwidth: 0 description: test ipv4: address: 0.0.0.0 masklen: 0 lineprotocol up macaddress: aa:aa:aa:aa:aa:aa mtu: 1500 operstatus: up type: routed
The text was updated successfully, but these errors were encountered:
l3_interfaces also just show the ipv4 address as virtual instead of actually showing the IP.
virtual
virtual addresses should likely be handled in manner similar to first hop redundancy protocols given many devices share the same IP.
Sorry, something went wrong.
GomathiselviS
Successfully merging a pull request may close this issue.
SUMMARY
show ip interface brief
command properly shows the applied ip address virtual command for an interface configured as such, but eos_facts does.ISSUE TYPE
COMPONENT NAME
eos_facts
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
Arista EOS 4.22.6M, 4.23.5M, & 4.24.3M
interface config:
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: