What am I missing here?
The switch already has vlan1, vlan10, vlan50
I telnet to my switch
I type menu
I go to the vlan menu
I add a vlan with name vlan30 and id 30
I go Port Assignment and change my ports to no for every vlan except vlan 30 which I set to untagged (this is how the other working vlans are done)
What else do I need to do, because when I do this the ports dont work.
The machines in the vlan aren't tagging their traffic are they?
I've no idea to be honest how would I find out?
They work fine on those ports if they're set to use one of the other vlans on that switch just not any of the ones I add in.
Have a look in your clients network driver properties for anything that mentions '802.1Q'
@mrforgetful: If you are changing all the ports, the management connection might be getting broken before the job can complete.
Try doing the same thing using a serial connection.... don't forget to check the settings for the management interface to make sure it is in the correct vlan.
The NIC does have a VLAN ID property but it's not set. Thing is the PC works no matter what it's plugged into.
I'm only changing 6 ports, two to ID 20, two to 30 and two to 60.
I think I'll just move them to another switch lol.
Thanks anyways
Which Model switch are you using? I tend to set up Vlans using the CLIOriginally Posted by mrforgetful
Forgot that bit lol, it's a 2650.
I use the cli on the Ciscos.
I assume you only want the ones on each vlan to talk to eachother. You will need to route the vlans if you want them to talk to anything else.
They want to talk to everything.
How do I set up a route? A point to some documentation would be fine
Try using they CLI the commands are almost identical to IOS.
Are you remembering to save the config at the end? I know it's basic but it's possible.
What exactly are you trying to achieve?
Unless you have a 'special' setup, you want to configure all the ports for your new vlan as untagged; except for the uplink port(s) which will need to be tagged. The switch at the other end of the uplink will then need the vlan creating & tagging as well as untagged on any other ports with machines in the new vlan on. Then same on any other switches elsewhere.
That will create you a 'new' network, across multiple switches - but unless you have either another router or you configure ipforwarding (or whatever HP might call it - assuming your switches are layer3) to forward layer3 traffic you won't be able to talk to anything except your new network.
Are you sure you actually want a new VLAN? What's the purpose of it here?
It's not a new vLAN it's just new to this switch.
We have the following vLAN arrangement
1 - Servers
3 - Printers
10 - ITRoom1
20 - ITRoom2
30 - ITRoom3
40 - ITRoom4
50 - ITRoom5
60 - ITRoom6
70 - ITRoom7
80 - F and G floord
90 - C,D,E Floors
110 - A and B Floors
110 - H Floor and Library
I've added two new computers to to each of the rooms 2, 3 and 6 but the switch they are patched into only has vLANs 10, 50 and 70 on it. I just wanted to include the relevant vLANs for the new PCs.
I've now just patched them into other switches so they're working.
Does your backbone switch deliver the relavant "tagged" vlan packets to the switch. The port with your uplink in must have Vlans 20 30 and 60 tagged for both the switch with the "untagged" computers on and the upstream switch.
If you want to check it works you can allocate the switch an ip address and see where you can ping it from. (though be careful about subnets it can get very fussy).
As a general rule all data traveling between switches when you are using VLANs should be tagged and all data to worksation untagged (unless you want to configure multi homes in networking).
I hope this helps
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks