[GH-ISSUE #1183] iPXE VLAN tagging on HPE DL360G9 #1864

Open
opened 2026-03-01 18:36:58 +03:00 by kerem · 3 comments
Owner

Originally created by @frct1 on GitHub (Dec 13, 2022).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1183

Describe the bug
In realworld we setting multiple vlan tags to all of our production switch ports but when we deploying new hardware we have to set access vlan mode for this ports due to issues with netboot.

To Reproduce
Steps to reproduce the behavior:

  1. Hpe dl360g9 with configured pre-network vlan tag (for PXE).
    image

Expected behavior
Vlan is setup right and everything is worked as in case of access switch port

Screenshots
chrome_bpQFzuy4Y1

Additional context
Nothing to add

Originally created by @frct1 on GitHub (Dec 13, 2022). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1183 **Describe the bug** In realworld we setting multiple vlan tags to all of our production switch ports but when we deploying new hardware we have to set access vlan mode for this ports due to issues with netboot. **To Reproduce** Steps to reproduce the behavior: 1. Hpe dl360g9 with configured pre-network vlan tag (for PXE). ![image](https://user-images.githubusercontent.com/25178244/207405647-9edbe964-c3f2-4364-b568-e816de17de67.png) **Expected behavior** Vlan is setup right and everything is worked as in case of access switch port **Screenshots** ![chrome_bpQFzuy4Y1](https://user-images.githubusercontent.com/25178244/207405287-f87f8fa0-c772-492f-bcd8-d35c59268345.png) **Additional context** Nothing to add
Author
Owner

@antonym commented on GitHub (Dec 13, 2022):

I would attempt to reproduce with basic iPXE and open up an issue upstream with iPXE. All we're doing in netboot.xyz is leveraging the VLAN tagging feature in iPXE to set the tag

It sounds like the tag is being set in the BIOS so would that be the default tag the machine is using once loading? I don't have access to any branded gear to validate/test with.

<!-- gh-comment-id:1349254587 --> @antonym commented on GitHub (Dec 13, 2022): I would attempt to reproduce with basic iPXE and open up an issue upstream with iPXE. All we're doing in netboot.xyz is leveraging the VLAN tagging feature in iPXE to set the tag It sounds like the tag is being set in the BIOS so would that be the default tag the machine is using once loading? I don't have access to any branded gear to validate/test with.
Author
Owner

@frct1 commented on GitHub (Dec 13, 2022):

I would attempt to reproduce with basic iPXE and open up an issue upstream with iPXE. All we're doing in netboot.xyz is leveraging the VLAN tagging feature in iPXE to set the tag

It sounds like the tag is being set in the BIOS so would that be the default tag the machine is using once loading? I don't have access to any branded gear to validate/test with.

Hi
I think tag that we set in BIOS is used only to get initial PXE, because even when loaded into netboot there is error about "failed accessing" . I guess this happen because vlan tag is not used when network devices is up from netboot.

<!-- gh-comment-id:1349300240 --> @frct1 commented on GitHub (Dec 13, 2022): > I would attempt to reproduce with basic iPXE and open up an issue upstream with iPXE. All we're doing in netboot.xyz is leveraging the VLAN tagging feature in iPXE to set the tag > > It sounds like the tag is being set in the BIOS so would that be the default tag the machine is using once loading? I don't have access to any branded gear to validate/test with. Hi I think tag that we set in BIOS is used only to get initial PXE, because even when loaded into netboot there is error about "failed accessing" . I guess this happen because vlan tag is not used when network devices is up from netboot.
Author
Owner

@antonym commented on GitHub (Dec 28, 2022):

There were some recent vlan patches that went into iPXE upstream:

https://github.com/ipxe/ipxe/commits/master

Did any of those help if you use a development build of netboot.xyz? https://s3.amazonaws.com/dev.boot.netboot.xyz/8b7e48bdbb89851ffbf6b4c1df63faa60fe38f9f/index.html

<!-- gh-comment-id:1366763974 --> @antonym commented on GitHub (Dec 28, 2022): There were some recent vlan patches that went into iPXE upstream: https://github.com/ipxe/ipxe/commits/master Did any of those help if you use a development build of netboot.xyz? https://s3.amazonaws.com/dev.boot.netboot.xyz/8b7e48bdbb89851ffbf6b4c1df63faa60fe38f9f/index.html
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/netboot.xyz#1864
No description provided.