cisco 3550 intervlan routing

Hey guys,

I have a sonicwall firewall with a dmz interface of 192.168.45.254, and i have one device connected at 192.168.45.232.

Now i need to add one more subnet (192.168.0.x) on this interface for a different device, so i am connecting a Cisco L3 3550 Switch.

I need to setup this config properly, so that i can still have my device at 192.168.45.232 and then also have another device at 192.168.0.x and they can go online.
LVL 4
Cobra25Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

giltjrCommented:
Here is configuration guide for doing that from Cisco's site:

http://www.cisco.com/c/en/us/support/docs/lan-switching/inter-vlan-routing/41260-189.html

You need to use VLAN's no matter what.  If both subnets/VLAN's need to be on the same interface of the firewall and 3350, then on the 3550 you need to configure the interface as a trunk with at least one of the VLAN's being tagged.

On the firewall you need to configure the interface so that both VLAN's are active on the interface and at least one of them needs to be tagged.
0
Cobra25Author Commented:
so i can make 2 vlans - 192.168.45.x and 192.168.0.x thats fine

Now the conenction between the switch and the sonicwall, what ip's should i use there?
0
giltjrCommented:
How is the sonicwall connected to your network right now?
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Cobra25Author Commented:
WAN --> Sonicwall

Not sure what you are asking here.
0
giltjrCommented:
So the Sonicwall is just connected to your WAN?  No LAN connections?  If there is only a WAN, what are you using it for?

Also, does the Sonicwall need to have an IP address on the 192.168.0.x subnet (I am assuming that is is 192.168.0.0/24).
0
Cobra25Author Commented:
Of course there is a LAN, i said this is a DMZ interface im working on. Yes the sonicwall is the gateway for the DMZ so of course it needs an IP.
0
giltjrCommented:
How is the sonicwall connected to your network right now?   Meaning , a managed switch or non-managed switch.

Do you plan to replace the current switch with the 3350, or are you just sticking the 3350 in-between the Sonicwall and the current switch.
0
Cobra25Author Commented:
there is just one device connected directly to the sonicwall on that interface. No switch.
0
giltjrCommented:
O.K, so currently you have a single host directly connected to the Sonicwall and you want to add a second device in a different subnet.

You have a couple of options.  One would be to let the 3350 just be a switch.  On the Sonicwall put the current subnet into a VLAN and add the new subnet into a new VLAN.   Define both VLAN's on the 3550 and setup the port that is connected to the Sonicwall as a trunk port.  I personally would set the native VLAN to a VLAN without anything on it and tag both VLAN's.  If hosts on each subnet need to talk to each other, you can either have the Sonicwall do the routing or setup the 3350 to do the routing.  If you need to filter traffic between the two, I would use the Sonicwall just so that all filtering is done in one location.  If the traffic does not need to be filtered, then enable routing on the 3350 and let it do it.  That way you have less traffic hitting the firewall.

Another option would be to create a 3rd subnet, put that on a network between the 3350 and the Sonicwall.  Then put the current subnet and new on both on the 3550 and let the 3350 route traffic to/from the Sonicwall.  Something like:

                                                     IP Subnet #2
                                                            /\
                                                             |
                                                            \/
Sonicwall <-- IP Subnet#1 -->  3550
                                                            /\
                                                             |
                                                            \/
                                                     IP Subnet #3
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
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
Switches / Hubs

From novice to tech pro — start learning today.