starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Unable to assign vlan on LAG with 802.1Q mode "Tagged all" #2515

New Issue
Closed
opened 2025-12-29 18:19:34 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:19:34 +01:00
Owner
Copy Link

Originally created by @gil-obradors on GitHub (Apr 12, 2019).

Environment

  • Python version: 3.5.2
  • NetBox version: 2.5.9

Steps to Reproduce

1.Switch with interfaces, physical and Link aggregations
2. Editing Link aggregations, I set to 802.1Q mode Tagged ALL
3.Save and continue editing is OK
4.802.1Q mode saved correctly
5.Adding VLANS at 802.1Q last frame-box
6.Selecting one or more VLANS (with tagged checkbox)
7.Netbox returns to port info page, without saving tagged vids
image

Expected Behavior

Save all assigned vlans for a LAG port from Switch. ( as Tagged all mode)

Observed Behavior

Not saved.
Tested with access and trunk 802.1Q port mode, and working. Only affects with LAG Tagged all

At the same time I was configuring other 1g type ports, from other device, and working with Acces, Tagged and Tagged All

Originally created by @gil-obradors on GitHub (Apr 12, 2019). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: <!-- Example: 3.5.4 --> 3.5.2 * NetBox version: <!-- Example: 2.5.2 --> 2.5.9 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a wrapper like pynetbox. --> ### Steps to Reproduce 1.Switch with interfaces, physical and Link aggregations 2. Editing Link aggregations, I set to 802.1Q mode Tagged ALL 3.Save and continue editing is OK 4.802.1Q mode saved correctly 5.Adding VLANS at 802.1Q last frame-box 6.Selecting one or more VLANS (with tagged checkbox) 7.Netbox returns to port info page, without saving tagged vids ![image](https://user-images.githubusercontent.com/6016929/56021440-ba1c0c80-5d09-11e9-82bc-660355738387.png) <!-- What did you expect to happen? --> ### Expected Behavior Save all assigned vlans for a LAG port from Switch. ( as Tagged all mode) <!-- What happened instead? --> ### Observed Behavior Not saved. Tested with access and trunk 802.1Q port mode, and working. Only affects with LAG Tagged all At the same time I was configuring other 1g type ports, from other device, and working with Acces, Tagged and Tagged All
adam closed this issue 2025-12-29 18:19:34 +01:00
adam commented 2025-12-29 18:19:35 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Apr 21, 2019):

This is the expected behavior. Tagged all means all VLANs are tagged, so there is no need to assign specific VLANs.

This is equivalent to saying members all on Junos or allowed vlan all on Cisco.

@lampwins commented on GitHub (Apr 21, 2019): This is the expected behavior. Tagged all means all VLANs are tagged, so there is no need to assign specific VLANs. This is equivalent to saying `members all` on Junos or `allowed vlan all` on Cisco.
adam commented 2025-12-29 18:19:35 +01:00
Author
Owner
Copy Link

@gil-obradors commented on GitHub (Apr 21, 2019):

Ok, thanks!

@gil-obradors commented on GitHub (Apr 21, 2019): Ok, thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2515
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?