Default VLAN issues on a Powerconnect 6200

Brent387
Brent387 used Ask the Experts™
on
Hi All,

I am trying to add a port on a Powerconnect 6200 to a new VLAN, which I am able to do fine. There is one problem though, under the default VLAN (1) it sets itself to F (Forbidden) which then blocks all access. If I try to remove the port from the default VLAN, I receive an error stating "Error! Cannot set default VLAN to static"

Any ideas?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Commented:
So you are adding an additional VLAN to a trunk?  Or are you trying to switch from vlan1 to a new vlan on an access port?  

Author

Commented:
Essentially I am trying to take port 1, make it my web access(management port) and leave the remainder of the ports (2-24) on the default VLAN. I do not want traffic from port 1 interacting with the other ports.

Commented:
Are you using the command "switchport access vlan <vlan-id>" on port 1.
Why Diversity in Tech Matters

Kesha Williams, certified professional and software developer, explores the imbalance of diversity in the world of technology -- especially when it comes to hiring women. She showcases ways she's making a difference through the Colors of STEM program.

Author

Commented:
I was actually just doing it through the management console. I was setting port 1 to general with a PVID of 5(the VLAN I want it on). Then I was setting it to Untagged under VLAN 5.

Commented:
When you untagged it under VLAN5 did it automatically take it off untagged on VLAN1?  You wouldn't be able to have a port with two untagged VLANs.

Author

Commented:
When I change it to untagged under VLAN5, it remains untagged under the default VLAN(1) if I have the port set to General. If I change the port to Access, VLAN5 becomes untagged, but under the default VLAN(1) it becomes forbidden.

Commented:
VLAN1 is forbidden just for that port right?  Which is probably right, you wouldn't want vlan 1 access just vlan 2 correct?

Author

Commented:
Correct, but then I lose access to that port. IE I can no longer ping the IP of the switch

Commented:
Is the IP of the switch on a different subnet?  What device do you have routing between the VLANs?

Author

Commented:
There will be two seperate networks on the switch, port 1 will be a management LAN which will allow me to manage the switch via internal web. The other ports will be used for iscsi traffic only.

Commented:
And the IP is in the same subnet as VLAN 5 not 1?

Author

Commented:
There is only one network cable plugged in to the switch, IP's shouldn't matter at this point in time.

Commented:
It does matter...

If you have an IP of 10.10.10.1/24 and you are trying to ping the switch's management address in a different subnet, lets say 10.10.20.1/24, you wouldn't be able to unless there was something routing between the subnets.

I am just making sure that your IP on your machine and the switch's management IP are on the same subnet/VLAN.
Commented:
Yes, in fact the machine I am using has access to all of our subnets. If i take the network cable out of port 1, which is VLAN5, and plug it into port 2 which is on the default VLAN, I can connect just fine. I am just unable to connect to the management console if the cable is in port 1

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial