ProCurve 2600 Switches and VLAN traffic

Posted on 2009-07-14
Last Modified: 2012-05-07
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?
   - vlan 1 (main) - ip (since 1.1 is the isa firewall and 1.2 is our mpls router)
   - vlan 2 (voip) - ip
  - vlan 1 (main) - ip
  - vlan 2 (voip) - ip
  -vlan 1 (main) - ip
  -vlan 2 (voip) - ip

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.
Question by:rickolson
  • 3
  • 3

Expert Comment

ID: 24853870
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.

Author Comment

ID: 24853925
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 (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!)
LVL 18

Accepted Solution

flyingsky earned 250 total points
ID: 24853966
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.
Live: Real-Time Solutions, Start Here

Receive instant 1:1 support from technology experts, using our real-time conversation and whiteboard interface. Your first 5 minutes are always free.


Expert Comment

ID: 24853973
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, fa0/1.10 would have ip

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.  

Author Comment

ID: 24854029
Thanks guys, that "trunking" terminology definitely helped.  Let me hammer away at it and I'll see what I can come up with.

Assisted Solution

khyer123 earned 250 total points
ID: 24854116
Procurves do trunking differently than Cisco switches

Here are a couple of pages with people explaining trunking/vlans:

Author Comment

ID: 24861307
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.

Featured Post

Gigs: Get Your Project Delivered by an Expert

Select from freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely and get projects done right.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

There are times where you would like to have access to information that is only available from a different network. This network could be down the hall, or across country. If each of the network sites have access to the internet, you can create a ne…
Security is one of the biggest concerns when moving and migrating your data from your on-premise location to the Public Cloud.  Where is your data? Who can access it? Will it be safe from accidental deletion?  All of these questions and more are imp…
After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

813 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now