• September 19, 2020, 05:19:46 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: IP Handsets & PCs sharing single VLAN  (Read 3598 times)

0 Members and 2 Guests are viewing this topic.

Offline ableseaman

  • Jr. Member
  • **
  • Posts: 39
IP Handsets & PCs sharing single VLAN
« on: November 14, 2013, 04:23:05 PM »
Currently looking at the options around an IPT rollout to around 30 sites.

5 of the sites are around 60 - 120 sets. We will be deploying an IP Office at each of these sites. LAN will be ers4550-pwr edge switches with a layer 3 ers5500 core switch. A single ers4550 port will serve an IP set and a PC. IP sets will be on VLAN 100 and PCs will be on VLAN 200. Fairly typical setup.

The rest of the sites are fairly small - ranging from 2 - 20 sets. We are looking at serving these sites directly from the 5 individual larger sites. The IP sets at the smaller sites will register back to the IP Office at their associated larger site. We are looking at deploying ers3526-pwr switches at each of the smaller sites. Again we would plan for a single ers3526 port to serve an IP set and a PC. However our WAN is a managed MPLS based network which only routes a single subnet - the PC based VLAN. This means that to allow the IP sets at the smaller sites to register back to the larger site they need to be placed into the PC VLAN. To allow the option of providing 2 routable VLANs (IPT VLAN and PC VLAN) we would need to install a layer 3 switch, possibly an ers4550. However this would increase the costs fairly considerably per site.

I understand the reasons for splitting the VLANs, all documentation points to this, and this is how we have setup all deployments at the rest of our sites. However does any one have any real world experience of a deployment using a single VLAN? Are we potentially setting ourselves up for possible headaches going forward?

We will be deploying QoS policies to ensure the IP sets are provisioned with the appropriate priority.

Before committing we would look to rollout this setup at a test site but would be nice to have feedback in advance.

Able


Offline TankII

  • Hero Member
  • *****
  • Posts: 556
Re: IP Handsets & PCs sharing single VLAN
« Reply #1 on: November 15, 2013, 03:54:07 PM »
The 35XX series does Static Routing.  So, you point your head-end back to the two IP ranges, and have a default route on the 35XX pointing to the head-end.
Keep ADAC going and QOS in place, and it will work just fine!

TankII

Offline ableseaman

  • Jr. Member
  • **
  • Posts: 39
Re: IP Handsets & PCs sharing single VLAN
« Reply #2 on: November 18, 2013, 05:03:48 PM »
Thanks for the response tank.

Not sure I'm understanding you correctly.

Our data VLAN is the 'known' subnet connecting to our OSPF network. This data VLAN is advertised to the rest of the OSPF network. Now for all our other sites (out with this project) were we have added a voice VLAN we've needed a layer 3 switch to sit in front of the MPLS managed router. The layer 3 switch advertises the voice VLAN to the OSPF network.

Now the data VLAN needs to be visible to all our MPLS sites but the voice VLAN only needs to connect back to one of the larger sites to register with the IPO - although we may use the networking feature of the IPO which may mean the voice VLAN being routable to more than 1 of the larger sites. Can you please explain how you're scenario with static routes will work here as all I can picture is using a layer 3 switch running OSPF to cover this off.

Cheers in advance

Offline TankII

  • Hero Member
  • *****
  • Posts: 556
Re: IP Handsets & PCs sharing single VLAN
« Reply #3 on: November 18, 2013, 09:45:09 PM »
The 3500 series only does Static Routing.   I would architect your MPLS network with a VLAN of say 192.168.200.0/27 to support your devices.
The five sites would be configured with interfaces into this network.  This would be a point-to-point configuration, though I would suggest configuring routing so each site has higher cost routes to all the other sites.  QOS is trusted on all ports connected to the MPLS network.
Main site: 192.168.200.1
First site:  192.168.200.2
Second site: 192.168.200.3
and so on.
These interfaces would be in one VLAN (call it VLAN 200 for the sake of this exercise)
Let's say the main site has two VLANS.  Data is 192.168.1.X/24.  Voice is 192.168.2.X/24.  Static routes point to 192.168.10.0/24 192.168.200.2 : 192.168.11.0/24 192.168.200.3 : 192.168.12.0/24 192.168.200.4 etc.
First site:  Data 192.168.10.1/25  Voice 192.168.10.129/25 with ADAC Call Server Port being the local IP Office port.    Default route is 0.0.0.0 0.0.0.0 192.168.200.1  Route to second site 192.168.11.0/24 192.168.200.3 metric 10.  Route to tertiary site is 192.168.12.0/24 192.168.200.4/24 metric 10.  Etc.
Second site: Data 192.168.11.1/25  Voice 192.168.11.129/25 with ADAC Call Server Port being the local IP Office port.    Default route is 0.0.0.0 0.0.0.0 192.168.200.1  Route to first site 192.168.10.0/24 192.168.200.2 metric 10.  Route to tertiary site is 192.168.12.0/24 192.168.200.4/24 metric 10.  Etc.

That's how I would do it using static routes and ERS3500 switches.
Notes:
Keeping the networks local, both voice and data, keep broadcast domains separate from your MPLS network.
QOS is critical.  I've posted my L-2 guide a while ago for setting ports up to trust qos markings.  The ADAC ports will always be trusting the phones as well as the IP Office since it's a Call-Server Port, but you have to trust your point-to-point links as well for the call quality to be good.
IP Phones, once the call is established, comunicate directly from one phone to another.  If your IP Offices are aware of each other, then calls will need to go the shortest path.  That path on an MPLS design will not be to the main site, but to a peer router in the network.  Hence, having static routes pointing to each other in the example above.

TankII

Offline ableseaman

  • Jr. Member
  • **
  • Posts: 39
Re: IP Handsets & PCs sharing single VLAN
« Reply #4 on: November 19, 2013, 08:37:02 AM »
Thanks for the response Tank.

I think I know what direction you are taking here but I will need to sit down and plan this around our network set-up.

With regards to the QoS around ports, uplinks, etc this is an area where I am happy with the requirements, having set this up at multiple sites in the past.

Cheers Again 

Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 3842
    • michaelfmcnamara
    • Michael McNamara
Re: IP Handsets & PCs sharing single VLAN
« Reply #5 on: November 19, 2013, 10:00:58 AM »
I see no issue in going with a single VLAN for your smaller branch offices (2-20 handsets).

Good Luck!
We've been helping network engineers, system administrators and technology professionals since June 2009.
If you've found this site useful or helpful, please help me spread the word. Link to us in your blog or homepage - Thanks!

Offline ableseaman

  • Jr. Member
  • **
  • Posts: 39
Re: IP Handsets & PCs sharing single VLAN
« Reply #6 on: November 21, 2013, 07:16:46 AM »
Cheers Michael

We have kicked off a pilot at one of the smaller sites using a single VLAN in the last few days, so will see how that develops.............

Able