ProCurve 2600 Switches and VLAN traffic

I've a need to add a vlan to an existing network, and I'm having some difficulty going at it the "best" way.  Allow me to paint a picture of the existing setup.

Firewall to the external world is an ISA 2006 appliance.
Internally at site A we have three switches, the ProCurve 2810-24, and two ProCurve 26-10-48's.  Site A also has an MPLS router to connect to Site B.  All web traffic goes through Site A.

Site A's internal addressing is 192.168.1.x
Site B's internal addressing is 192.168.2.x

What I hope to accomplish is to create a vlan for our voip phones so that I can build some QoS into the routers.

Here are some of the issues I've run into.

I've found that the ProCurve switches can act as routers.  However, I have three of these switches, and the vlan ip configured on each switch should be different, correct?
Example:
ProCurveA
   - vlan 1 (main) - ip 192.168.1.3 (since 1.1 is the isa firewall and 1.2 is our mpls router)
   - vlan 2 (voip) - ip 192.168.10.1
ProCurveB
  - vlan 1 (main) - ip 192.168.1.4
  - vlan 2 (voip) - ip 192.168.10.2
ProCurveC
  -vlan 1 (main) - ip 192.168.1.5
  -vlan 2 (voip) - ip 192.168.10.3

If this is true, how should the routing be configured so that traffic can reach the 10.x network?

Second, since I need to establish some QoS on both the mpls router and the external routers, these two routers also need some routing information to be able to find those networks.  So where should the gateway for those networks exist?

I have a feeling that in the course of reading up on what vlan's are and how they're implemented, I may have made the problem more complicated than it needs to be.  Hopefully someone can give me some clarity.  Also, since I didn't give much detail above, I'm happy to give a little more detail or answer other questions in search of answers.
rickolsonAsked:
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.

khyer123Commented:
Typically, you only need one IP address per switch, usually on a management VLAN - it's just for accessing the switch for management purposes.

Where is this 10.x network? I assume connected to your router? In any case, in order for VLANs to talk to each other, you must route between them - so you need a trunk port from one of your switches into the router, set up subinterfaces (which do need IP addresses by the way), and you're good to go.
0
rickolsonAuthor Commented:
Think I had a typo, the 10.x network was supposed to be written as 192.168.10.x

Our voip phones are all over the place on the switches, and some phones have built-in bridging where computers are plugged in to as well, and it is because of this that I can't simply assign ports to vlans.

So if I'm understanding your comment correctly, I would set up a single trunk port from one switch to the router.  This trunk port would have perhaps the ip of 192.168.10.1 (I assume then perhaps that this would be the gateway used for the network?)

What about the other two switches?  Would each switch need a trunk directly to the router?  The switches are currently chained in such a way such that the router goes directly into our 2800, and each 2600 comes off the 2800 (hopefully that makes sense!)
0
flyingskyCommented:
I feel you got some concepts mixed together.
When talking about vlan, we are talking about Layer 2 stuff (OSI model). When talking about routing, we are talking about Layer 3 stuff.
Let's take your switch A as an example. When you group the ports into two vlans (main and voip), you are seperating the ports so they cannot "see" each other from layer 2's point of view. Now, you need to decide where the layer 3 routing is going to happen. In your case, the Procurve switch and ISA can both do the job (of course, the MPLS router can do it too). If you are using Procurve for this (which means it is your default gateway), you will need to configure trunk port ( a port belongs to both vlans) then configure the routing stuff. If you are using ISA for this (which means ISA is your default gateway), then you don't need to worry about configuring routing on the Procurve, the ISA appliance will take care of it.
Hope this help.
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
Become a Microsoft Certified Solutions Expert

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

khyer123Commented:
Alright, let's start from the core - the router.

On the router, you configure a port with two subinterfaces. The interface itself gets no IP address, but each subinterface needs an ip address on its subnet (ie fa0/1.1 would have ip 192.168.1.1, fa0/1.10 would have ip 192.168.10.1)

You would then need to configure a trunk from one switch to the router (I believe procurve supports dot1q encapsulation for trunks)

You could daisy chain your other switches, so that switch A connects to the router, switch B connects to Switch A, switch C connects to Switch B - and each switch connects to each other via a trunk line, so that all VLANs can reach the next switch, and get to the router. There's no need to plug each switch directly into the router - in fact, I'm not sure you're allowed to do that.  
0
rickolsonAuthor Commented:
Thanks guys, that "trunking" terminology definitely helped.  Let me hammer away at it and I'll see what I can come up with.
0
khyer123Commented:
Procurves do trunking differently than Cisco switches

Here are a couple of pages with people explaining trunking/vlans:
http://www.tek-tips.com/viewthread.cfm?qid=1250872&page=1
http://www.experts-exchange.com/Networking/Network_Management/Q_24071414.html
0
rickolsonAuthor Commented:
Thanks guys, you were both helpful so I split the points up.  I'm going to do a little more research and get my facts straight before I take another whack at it.
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 Architecture

From novice to tech pro — start learning today.