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
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.
The text was updated successfully, but these errors were encountered:
roadracer96
changed the title
Layer2 su
Layer2 sub-interfaces not returned froim junos_facts l2_interfaces resources module.
Nov 1, 2023
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
COMPONENT NAME
junos_l2_interfaces/junos_facts
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
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.
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.
The text was updated successfully, but these errors were encountered: