Unsolved
This post is more than 5 years old
1 Rookie
•
18 Posts
0
1571
March 5th, 2017 09:00
First time setting up VLANs across interconnected N5000 & N3000 switches, connecting to different ports on SonicWALL - is there more to it than this?
At my company, we have a stack of PowerConnect N3000 switches for our core (stacked with mini-sas cables in the back) and then they connect to switches in various closets throughout the building via LAG groups. I have about four closets that have N5548 & 5524P PowerConnects. We have a flat network and our gateway is the X2 port on our SonicWALL firewall (NSA3600). We currently have no VLANs except the default.
We also have a parallel physical network for wireless (made up of D-Link switches), which connects all the access points back to another X port on the SonicWALL. My plan is to go ahead and create a VLAN for wireless on the main network and then get rid of the D-Links.
I've never set up VLANs before but I do get the concept. I also spent the day reading the PowerConnect manual sections on VLANs as well as google, and then I used three extra N5000 switches to test on and I seem to have gotten it working, but I just want to make sure that I've not missed anything.
So, using the web front-end, I just need to do these steps:
1. Create VLAN 2 (named wireless) on all switches
2. Select the ports on each switch where the end points will connect to and then:
a. Put them in Switchport mode: Layer 2 (the default)
b. Put them in Port VLAN mode: access
c. Add '2' from the VLAN list (and only that)
3. Go to LAG settings under the VLAN menu and select each LAG group on the switch
a. Put them in Switchport mode: Layer 2 (the default)
b. Put them in Port VLAN mode: Trunk
c. Verify that all LAG groups are listed in the VLAN list
4. Save configuration
5. Connect wifi access points to VLAN access ports
6. Connect one access port to the appropriate X port on the SonicWALL for the wireless
Is this correct? I tried this on my test switches and connected some laptops (with a different IP scheme) and was able to ping each other on the ports designated for the VLAN. I also tested to make sure I couldn't ping if one was connected to VLAN 1 and the other to VLAN 2.
I just want to make sure I'm not missing anything. Also, is this something I can do during work hours without any possible network disruptions?
DELL-Josh Cr
Moderator
•
9.6K Posts
•
42.2K Points
0
March 6th, 2017 10:00
Hi,
It looks like you have everything planned out well. It should be the easy to switch over. You will probably want to save the current config to a file in case something goes wrong and doing it after hours would be safer, but if everything works as expected there should not be any downtime on the switch side, clients may need to get new IP addresses.
dheet
1 Rookie
•
18 Posts
0
March 6th, 2017 12:00
Thanks. Is that all there is to this? I haven't over-looked any obscure setting? I don't have to do anything special since I have different switch models?
Thanks
DELL-Josh Cr
Moderator
•
9.6K Posts
•
42.2K Points
0
March 6th, 2017 13:00
Voice vlan is for voip when you have both a computer and phone connected on the same Ethernet cable, so it puts the phone in a tagged vlan and the computer in an untagged vlan. It just has additional configuration over the normal vlan config.
DELL-Josh Cr
Moderator
•
9.6K Posts
•
42.2K Points
0
March 6th, 2017 13:00
There shouldn’t be any other settings in this case since you didn’t say you were doing a voice vlan. The different models will handle VLANs the same way.
dheet
1 Rookie
•
18 Posts
0
March 6th, 2017 13:00
Well what's the difference if I was doing a voice vlan? And what is voice anyway, voip? We currently have our phones connected to our existing powerconnects on the default vlan and I don't think we did anything special, as they just work since voice data is the same as regular data... Say I wanted to put the phones on a 3rd VLAN, what would I need to do differently?
Thanks again.
dheet
1 Rookie
•
18 Posts
0
March 6th, 2017 14:00
I see. Thanks for the help!