Unfortunately, I am not familiar with the web interface, and I do not have a simulator for it. I did locate a post where someone encountered the same issue as you and a suggestion was made:
Go to Switch -> Port Based Authentication -> Authentication Method -> Set to NONE.
The error indicates that the ports you are attempting to assign to VLAN 10 are in a state that does not allow them to become a VLAN member. Clearing the configuration on those interfaces should allow them to become a member. The post also includes the CLI commands for creation and assignment of a VLAN.
Unfortunately that menu structure does not exist on the web interface I have.
From a bit of playing around it appears to be something to do with the way the ports are assigned.
On Vlan 1 all the interfaces are set to "U" (untagged)
On Vlan10 when I click on port 48 to assign it to the new vlan, the first option is "T" (tagged) and saving this does not work. However if I click it again it goes to "U" and this can be saved.
Being a bit of a switch / vlan noob, am I right in saying that I will be wanting Vlan10 to be tagged as the interface so traffic will be picked up by the correct interface on the gateway, in this case eth0.10 instead of the default eth0?
Thanks for the instructions re setting the VLAN via the web interface, I had managed that (as with first post) but can only set it untagged this way. As you suggested, I think firmware update is the first port of call as it is woefully out of date!
Then we'll see how I fare with the web-interface, or I may just man up and go CLI after that.
# show bootvar Image Filename Version Date Status ----- --------- --------- --------------------- ----------- 1 image-1 2.0.0.29 13-Jan-2009 17:42:37 Active* 2 image-2 2.0.0.29 13-Jan-2009 17:42:37 Not active
Daniel My
10 Elder
•
6.2K Posts
0
July 6th, 2012 10:00
Hello rberg77
Unfortunately, I am not familiar with the web interface, and I do not have a simulator for it. I did locate a post where someone encountered the same issue as you and a suggestion was made:
http://en.community.dell.com/support-forums/servers/f/866/p/18869336/19349609.aspx
The error indicates that the ports you are attempting to assign to VLAN 10 are in a state that does not allow them to become a VLAN member. Clearing the configuration on those interfaces should allow them to become a member. The post also includes the CLI commands for creation and assignment of a VLAN.
Thanks
rberg77
6 Posts
0
July 16th, 2012 03:00
Unfortunately that menu structure does not exist on the web interface I have.
From a bit of playing around it appears to be something to do with the way the ports are assigned.
On Vlan 1 all the interfaces are set to "U" (untagged)
On Vlan10 when I click on port 48 to assign it to the new vlan, the first option is "T" (tagged) and saving this does not work. However if I click it again it goes to "U" and this can be saved.
Being a bit of a switch / vlan noob, am I right in saying that I will be wanting Vlan10 to be tagged as the interface so traffic will be picked up by the correct interface on the gateway, in this case eth0.10 instead of the default eth0?
rberg77
6 Posts
0
July 17th, 2012 05:00
Thanks for the instructions re setting the VLAN via the web interface, I had managed that (as with first post) but can only set it untagged this way. As you suggested, I think firmware update is the first port of call as it is woefully out of date!
Then we'll see how I fare with the web-interface, or I may just man up and go CLI after that.
# show bootvar
Image Filename Version Date Status
----- --------- --------- --------------------- -----------
1 image-1 2.0.0.29 13-Jan-2009 17:42:37 Active*
2 image-2 2.0.0.29 13-Jan-2009 17:42:37 Not active
Now to schedule downtime.....