VLAN questions for Point to Point(metro ethernet) across switches

Hi Folks,

We are getting a new point to point link(metro ethernet) via Time Warner to start up a new 2nd office. Basically a L2 connection that I can VLAN across. I want this office to have it's own broadcast network for both their new data net and voice network so I want to subnet this new office on it's own /24 net for each(our current production network /24 net is getting pretty full) and I want to do this at the switch Level and not have a router in place.

My HQ currently has basically 2 VLANS's VLAN1 and VLAN2 (Yes I know, Im stuck with VLAN1 for the moment) Vlan1 is default, Vlan2 is for voice(Mitel 3300 system).

My Main site hase a several procurves today (2648's&24's)

My main HQ switch which is the only switch currently with ip routing enabled let's say is 10.10.70.1(for VLAN 1 interface) and 192.168.20.1 (for VLAN2)

The new switch that I am briging in for the new office location on the other side of the point 2 point link is a 2910AL-48POE. I want the two subnets at this new office to be 10.10.74.X for their Data net (default VLAN) and 10.10.75.X for voice.

I also want to have the 2 new vlans to have the same VLAN ID as their network number(74 & 75). So then my interfaces for each VLAN on the new office switch would be 10.10.74.1 and 10.10.75.1.

So what's the best way to do this? I was originally thinking that I would have to have an ip address from my current productin net on VLAN 1(10.10.70.10) on the port where the P2P comes in on the new switch(lets say port 1). I was going to have it untagged on VLAN1 for port 1 and all other ports would be untagged on VLAN 74 and Tagged on VLAN 75. I would then apply appropriate QOS policies for voice on the VLAN level and globally with DSCP values.

I would then need to set my default route on this new office switch to point to the HQ office switch(10.10.70.1) and then create the necessary routes in the HQ switch back to this switch for both

nets(10.10.74 and 10.10.75.):

ip route 10.10.74.0 255.255.255.0 10.10.70.10
ip route 10.10.75.0 255.255.255.0 10.10.70.10

But then I got to thinking that I would really not have QOS on the Point2point because I am basically just doing ip routing at that point?

OR is it better to also bring down(tag) VLAN 2 from main switch across the point2point and then setup VLAN 2 on the new switch and just enable routing on this switch and do the routing between subnets there?

I dont know. I think I am over thinking this.

Thanks for your time! Let me know if this is not clear enough.

-Scott

 

[cajuntank]

But then I got to thinking that I would really not have QOS on the Point2point because I am basically just doing ip routing at that point?"

QoS will work just fine across routed networks as non-routed as long as you have control end to end. QoS is not bound to work in only layer 2 networks, so your thought process of setting up routing is fine. With such a small (from what you defined) network, you could setup static routing like you are talking about, but you could also do RIP (v1 or v2). Your 2600 series and 2910al support both. RIP will just make it easier instead of manually entering all of the routes; especially if you add additional VLANs and corresponding subnets in the future.

I have my network setup the same way using Metro Ethernet circuits, but I have mine going into 5400 series chassis and running OSPF as my routing protocol of choice.

As far as the QoS config and policies, check out this link

http://h17007.www1.hp.com/docs/interoperability/Mitel/4AA2-1398EEE.pdf

You will enable the "voice" command under the VLAN2 interface to turn on LLDP-MED. LLDP-MED is automatically turned on on the Mitel handsets and they will dictate the necessary QoS priority to the switch which the switch will follow and use since it also has LLDP-MED enabled (using the "voice" command).
If you are using the phone's switchport to then connect your computer, you will tag the ports on the switch under the VLAN 2 interface, then untag those same ports under whatever your DATA\USER VLAN might be. The pdf link will also go into 802.1x security, but unless you are doing that, then you can skip that part. Your Mitel vendor might have you do a little more QoS tweaking to ensure a few things...I use Avaya products and while they too support LLDP-MED, I had to tweak a few things to follow Avaya best practices. Assigning a priority 6 to DSCP codepoint 101110, then assign the QoS value to the Avaya IP-PBX equipment.

So for example:
Procurve Switch(config)# qos type-of-service diff-services
ProCurve Switch(config)# qos dscp-map 101110 priority 6
Procurve Switch(config)# qos protocol ARP priority 4
ProCurve Switch(config)# qos device-priority 10.40.40.1 priority 6 (or whatver IP address your Mitel switch is)

Hope that helps.

 

[cajuntank]

Just re-read a little and missed on something that you stated about creating your network between your locations. I would create a completely different VLAN and subnet for your circuit connection.
So lets say your MetroE connects to both switches their repective port 24. Then create a new VLAN, VLAN 100 for example, name it MetroE, untag port 24, and assign an ip address of say 10.10.1.1 with mask of 255.255.255.252, then the other switch across the MetroE, do the same VLAN 100, untag it's port 24, but the IP will be 10.10.1.2 with mask 255.255.255.252

This will give you what you are looking to do. Also under that VLAN 100 interface on both switches, add the command
Procurve Switch(config)# qos dscp 101110

Then follow the other QoS commands as I stated in previous post.

 

[scott53326]

Thanks Cajuntank. I appreciate the info and your time. One last question. So on the switch at the new remote office my default route on the switch will be to 10.10.1.1(the other end of the point2point at main office)?

Thanks!
-Scott

 

[cajuntank]

That's right, whatever the next hop is and in my example, 10.10.1.1 is the next hop.