iPXE VLAN tagging on HPE DL360G9

[frct1]

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).

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

Screenshots

Additional context Nothing to add

[antonym]

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.

[frct1]

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.

[antonym]

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