Looking for advice regarding VLAN configurations

I have a cluster of computers that I want to stick on a VLAN for logical separation mainly, and another network of IP phones that I want on one because apparently having the dedicated broadcast domain knocks out intermittent echoes during voice calls. I've been banging my head trying to figure it out, which will soon be the topic of another post, but I want to first make sure that I'm not doing the work for nothing. Here's what I'm trying to do:

pfSense
+--------+
| LAN    |---[172.16.0.1]----[172.16.0.0/16]    Dell PowerConnect Switch
|        |                                      +--------+
| VLAN20 |---[192.168.0.1]---[192.168.0.2]------| VLAN20 |--[192.168.0.0/24]
|        |                                      +--------+
| VLAN30 |--+
+--------+  |                                   +--------+
            +-[192.168.1.1]---[192.168.1.2]-----| VLAN30 |--[192.168.1.0/24]
                                                +--------+
                                                Dell PowerConnect Switch

Open in new window


For each VLAN in the pfSense router an IP (*.1) is given to the interface, and on the switch side an IP is given for a management IP (*.2). The switch complains about having the VLAN management IP on the same subnet that it was already given from the DHCP at the router but that's easily fixed by putting VLAN1 on the switch onto a dummy network.

My question is pretty simple, or complicated, I'm not really certain. Is what I'm doing here with the VLANs and interface IP assignments sensible? This seemed most logical to me when I started the VLAN setup from pfSense, now that I'm into the switches I'm not so sure.

Thanks.
LVL 3
coandaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Henk van AchterbergSr. Technical ConsultantCommented:
It is sensible but normally a switch would have only one IP for management. A "Layer3" switch which performs routing can have multiple IP's.

For voice you can execute special  "voice vlan" commands on the switch so the phones can pick it up and pass trough your normal LAN.

http://networkingnerd.net/2012/05/09/switchport-voice-vlan-post/
0
Soulja53 6F 75 6C 6A 61 Commented:
Yes, you don't need multiple ip addresses on a layer 2 switch. Only one will be used for management. In your dhcp, exclude the switch ip from the dhcp scope so you don't get the complaints. Other than that, create the two vlans on the L2 switch, assign which ports you want and make sure your trunk to the router carries both vlans.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
coandaAuthor Commented:
I think I probably made a few things unclear in my initial diagram, the intention was that each of the VLANs occupied every port on their own independent switch. I've done an updated and simplified diagram and explanation in a different post that has more to do with the implementation at http://www.experts-exchange.com/Hardware/Networking_Hardware/Switches/Q_28236045.html.

Thanks for the comments so far, I'm at least a little comforted that no one told me I was doing something entirely stupid.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Network Management

From novice to tech pro — start learning today.