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
Discussed with some network engineers that adding VLAN support is probably a good thing. My thinking is that for NC-SI deployments 802.1x should probably be the best way to split VLANs for BMC and the host, but I can sympathize that you might want to configure your BMC to use a specific VLAN.
My thinking is a persistent file that's read before interface up (e.g. /etc/vlan-id) that configures the VLAN.
This allows serial console access to simply rm /etc/vlan-id; shutdown -r to clear the configuration as well.
The text was updated successfully, but these errors were encountered:
Discussed with some network engineers that adding VLAN support is probably a good thing. My thinking is that for NC-SI deployments 802.1x should probably be the best way to split VLANs for BMC and the host, but I can sympathize that you might want to configure your BMC to use a specific VLAN.
My thinking is a persistent file that's read before interface up (e.g. /etc/vlan-id) that configures the VLAN.
This allows serial console access to simply
rm /etc/vlan-id; shutdown -r
to clear the configuration as well.The text was updated successfully, but these errors were encountered: