Juniper: support for interfaces inside vlan definition #4999
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #4985
Add support for interfaces declared inside of vlan, like
set vlans LAB-3 interface ge-0/0/20.0
. On an interface inACCESS
mode, this sets the (vendor-specific) access vlan name. On an interface inTRUNK
mode, this adds the vlan to the trunk members.Set switchport mode
ACCESS
when interface is added tofamily ethernet-switching
for the first time.Move setting of VI allowed vlans into the trunk handling conversion code.
Fix native vlan-id for trunks (1 -> drop untagged frames by default).
Fix reference tracking for vlan l3-interface