Unsolved
This post is more than 5 years old
1 Message
0
551
July 28th, 2016 20:00
Powerconnect 5324 (3) and a sonicwall NSA220
Hoping the community can help me with a config for 3 powerconnect 5324 switches and a NSA220.
I've inherited this environment and looking to make some improvements. Everything is stock currently. VLAN1 and nothing else.
Switch 1 has g1 to x0 (lan) on the nsa220, switch 1 has g24(fiber) to switch 3, switch 1 has g2 to switch 2.
I'd like to isolate voip traffic on vlan, iscsi on a vlan, wireless guest on vlan and internal wireless on another vlan.
I've read many posts and misc config docs but some it contradicts others. I'm weak on the network side.
I started by building vlans on the sonicwall. All good.
vlan13 192.168.13 wireless guest
vlan15 192.168.15 wireless internal
vlan17 192.168.17 voip
vlan40 192.168.40 iscsi
The sonicwall is 192.168.1.5. After the vlans are setup on the sonicwall I can ping the respective .1 interfaces.
Then I started to config the vlans on switch 2. I built the vlans using the web interface then tried to config access and lost control of the switch. I have ordered a usb null modem cable to re-gain control. Traffic for connected hosts is still working but I can't access the admin interface.
Should switch g2 be access or trunk. Many of switch ports are utilized by voip phones with a connection to a laptop or workstation. So binding a switch port to a particular vlan seems like a problem to me. How can I isolate workstation and voip if they share the same switch port?
Flame away ... trying to learn and thanks in advance.

