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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Layer2 sub-interfaces not returned froim junos_facts l2_interfaces resources module. #457

Open
roadracer96 opened this issue Nov 1, 2023 · 0 comments

Comments

@roadracer96
Copy link

SUMMARY

On a JunOS device using SP style configuration of layer-2 interfaces, a vlan id defined as such:

vlans {
timtest {
vlan-id 100;
interface ge-0/0/0.100;
}
}
interfaces {
ge-0/0/0 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 100 {
encapsulation vlan-bridge;
vlan-id 100;
}
}
}

On an MX device, the same basic construct is employed except "bridge-domain" is used in place of "vlans"

ISSUE TYPE
  • Bug Report
COMPONENT NAME

junos_l2_interfaces/junos_facts

ANSIBLE VERSION
N/A
COLLECTION VERSION
# /home/MERIT/denike/.ansible/collections/ansible_collections
Collection            Version
--------------------- -------
junipernetworks.junos 5.0.0  

CONFIGURATION
N/A
OS / ENVIRONMENT

N/A

STEPS TO REPRODUCE

Configure a device with SP style VLAN configuration and run a play using the junos_facts module, querying l2_interfaces.

- name: Get JunOS Facts
  junipernetworks.junos.junos_facts:
    gather_subset: [ hardware,interfaces ]
    gather_network_resources: [ lacp,lacp_interfaces,lag_interfaces,l2_interfaces,l3_interfaces,interfaces]
  register: facts
EXPECTED RESULTS

I would expect the returned dict to be similar in structure to l3_interfaces with the addition of a vlan-id (l3_interfaces should return this in the case of L3 sub-interfaces as well)

ACTUAL RESULTS

Interface not returned at all.


@roadracer96 roadracer96 changed the title Layer2 su Layer2 sub-interfaces not returned froim junos_facts l2_interfaces resources module. Nov 1, 2023
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

1 participant