Unsolved
This post is more than 5 years old
5 Posts
0
3034
July 14th, 2019 19:00
iDRAC switch configuration
Hi All,
Current setup for our iDRAC 9 is configured at switch on vlan 10 and assigned with IP 10.101.10.xx connected to HP Procurve 2810 which set as untagged for vlan 10.
Based on HP configuration all end device must use untagged unless the end device is aware or configured with vlan.
However in my case the iDRAC 9 was not configured with any vlan and in order for gateway or other vlan to communicate or access the iDRAC9 port is the port at switch must be configured as tagged instead of untagged.
Does anyone encounter same issue or this is by designed for iDRAC 9 confguration fo vlan?. Thanks
No Events found!
Daniel My
12 Elder
•
6.2K Posts
0
July 15th, 2019 10:00
Hello
If you have the iDRAC set to VLAN 10 then it will ignore any frames that are not tagged with VLAN 10. You will need to configure the interface on the switch to pass tagged frames. If the interface is sending untagged frames then don't set the iDRAC to a VLAN. If the iDRAC is using a management network on VLAN 10 but is sending untagged frames then you don't need to let the iDRAC know it is on VLAN 10. You should only configure the VLAN setting on the iDRAC if you have the interface configured to send tagged frames.
http://www.dell.com/idracmanuals/
Thanks
Azwanarif06
5 Posts
0
July 15th, 2019 17:00
np-mast
3 Posts
0
July 16th, 2019 03:00
Hi,
when you set the iDRAC NIC to VLAN 10, it is now listening only to tagged frames/packets.
However, as your switch is configured to VLAN 10 untagged (mode access on cisco) on iDRACs port, the most simple thing is to set iDRAC to not use any VLAN. It is now the switches´ task to put it in the correct VLAN.
In general, when using the dedicated iDRAC NIC, I don´t see any real reason to use iDRAC tagged VLAN. This feature is more appropriate when using a shared NIC with the OS.