Unsolved
This post is more than 5 years old
1 Message
0
4703
November 17th, 2008 09:00
Powerconnect VLAN design advice
Hello all. I recently purchased several Powerconnect switches to upgrade my network from flat and dumb, to VLAN capable. Two 6248s and a 6224 to stack together for a core, and a few 3524s and a 3548 for out in the wiring closets. I know what I want the end result to be but I feel like I'm already stuck right off the bat, hoping someone can offer some guidance. Apologies in advance if I'm asking a dumb, noob, inappropriate, etc question.
Right now all my pcs, servers, and other devices are using 10.23.184.0/24 addresses. .1 is the inside interface on a Sonicwall firewall, used as the gateway. My parent company installed a VPN router, 192.168.153.254/24 inside address and they are committed to using that range. Pretty sure they have an acl set up that assumes all traffic coming from my network is 192.168.153.0/24 They won't make an exception for me and my existing 10 network. So I tried hanging that router off of one of the other interfaces on the Sonicwall, and tried various things (NAT, routing, etc) but it won't work reliably. Started looking like my only option was going to be a hard cutover and reassign everything 192 addresses. (Total nightmare as I have an old mainframe that I'm afraid to touch, and several dozen printers with static IP addresses.) Then I realized, why couldn't I do it with VLANs? Make the 10 network a VLAN and leave the mainframe and the printers there, make the 192 network a VLAN and move desktops that need to hit the VPN there, make sure both VLANs can see each other (so the desktops can still hit the mainframe), and then route outbound traffic to either the internet gateway (10.23.184.1) or the VPN router (192.168.153.254) as necessary.
So I guess my big question is would this scenario work? And my possibly dumb, right off the bat stuck question, is when I run through the initial setup on the core switch, what addressing would be best to use for the default VLAN?
Sorry for the tolstoy, thanks in advance for any and all suggestions.
Duane Pittman
BrandonSchultz
13 Posts
0
November 25th, 2008 20:00
You could probably make that work just fine with multiple VLAN's and IP routing turned on. You should know that the default gateway of each of your machines in the 192.168.153.0 network will need to use the IP of the routed VLAN interface. So, you will probably need to make a static route in your firewall so that your machines can get back out on the web. The other thing to consider is the kind of traffic going in and out of your mainframe. You might do well to look into UDP relay if that machine uses broadcasts and needs to communicate through a routed interface.
Honestly, the documentation in the Dell manuals for the 62xx family of switches isn't very good. I would setup a test environment and experiment. Good luck to you.
B. Schultz