IP Office 412 setup w/ seperate VLAN for voice traffic,1 DHCP Server 1

[ipo412]

I did this setup today and thought I would document it and share it for anyone that is looking to do the same thing. I think this is fairly comprehensive but let me know if you feel if I have left anything out.

Setting up IP Office in a separate VLAN for Voice Traffice Using One DHCP server

IP Office (412) Config

LAN1:
192.168.1.20 /24
GW: 192.168.1.2

LAN2:
192.168.5.20 /24
GW: 192.168.5.2


DHCP Server (Win 2003 Server)
DHCP Server w/ two NICs
NIC 1: 192.168.1.10 (Data network)
NIC 2: 192.168.5.10 (Voice VLAN)

DHCP Scopes:
192.168.1.0 /24
192.168.5.0 /24

192.168.1.0 Scope:
Option 176: L2Q=1,L2QVLAN=2

192.168.5.0 Scope:
Option 176: MCIPADD=192.168.5.20,MCPORT=1719,TFTPSRVR=192.168.5.21,L2Q=1,L2QVLAN=2,VLANSEP=1,PHY2PRIO=1

VMPro Server (also TFTP Server)
VMPRO server w/ two NICS
NIC 1: 192.168.1.21 (Data Network)
NIC 2: 192.168.5.21 (Voice VLAN)


Switches
All Switches are configured with 2 VLANs:
Main Switch (VLAN 1 IP: 192.168.1.2 | VLAN 2 IP: 192.168.5.2)
This switch is a Layer 3 switch that has route statements built in, though you can do the same setup without a Layer 3 switch if it is a small enviroment

VLAN ID: 1 (DEFAULT_VLAN)
VLAN ID: 2 (VOIP) * Tagged on all ports (see exceptions below)

*DHCP Server NIC 1 has VLAN 1 UnTagged on the corresponding switch port
*DHCP Server NIC 2 has VLAN 2 UnTagged on the corresponding switch port

**** IMPORTANT*****
Both ports on the switch for the DHCP server should NOT be tagged with any VLANs, only UnTagged to the appropriate VLAN (if you do not do this you will receive DHCP ACK errors when the phones boot into VLAN 2)
*********************

*Lan 1 IP Office port Untagged to VLAN 1 (NOT tagged to VLAN 2)
*Lan 2 IP Office port Untagged to VLAN 2 (NOT tagged to VLAN 1)

*NIC 1 VMPRO Untagged to VLAN 1 (NOT tagged to VLAN 2)
*NIC 2 VMPRO Untagged to VLAN 2 (NOT tagged to VLAN 1)


This worked like a charm for me, hope this helps someone.

-T

 

[ipo412]

I knew I forgot something, the switch has an "ip helper-address" setup on VLAN 2 that points to 192.168.5.10. Somehting like:

vlan 2> ip helper-address 192.168.5.10

 

[PotNoodleBoy]

Thanks for the info.

A couple of questions:

I'm likely to try this on a IP406 which would mean I'd need logical lans. I'm assuming in this scenario I would only need to connect the IPO to the network once, not twice like you would with a 412 which has 2 distinct network interfaces.

Also I assume the DHCP server will only give out addresses on NIC1 which match the interface IP. So NIC1 is on subnet 1 meaning it automatcially knows to only supply addresses from the 192.168.1.x scope on that interface. Basically I'm assuming you don't have to manually associate a particular DHCP scope with a particular network interface.

Also I can't see a reason for the VM Pro server to be loaded on the DHCP server - can you? We often end up in this situation as we supply servers too. It makes more sense to load VM on a new shiny server which gets backed up each night than sticking it on a PC

 

[ipo412]

robwalker,

The reason that I needed the two interfaces was because I am using Integrated Messaging and Phone Manager. I dont believe you would need them for any other reason, though I could be wrong.

You are correct about the NICs only handing out address that they are associated with, you do not need to bind a specific scope to a specific NIC.

**The key is the tagging an untagging of the switch ports**

I cannot think of any reason that the VMPRO box needs to be a DHCP server.

If you need to use IMS or Phone Manager, this is where you need to get into Layer 3 swithing (routing). Though this is a bit of a grey area for me.

-T

 

[PotNoodleBoy]

I'd come to the same conclusion regarding 2 interfaces and phone manager. All our installs will have phone manager so we'll definitely need this. I'm a network engineer by trade so routing should be fairly straight forward for us.

One other thing, you obviously have two default gateways (one on each subnet). How did you accomplish this? Some sort of router with multiple interfaces or with clever with routing on the switches. I'm guessing it would be possible to route the traffic on to the other VLAN and out on to the internet/other network using just one actual gateway.

Thanks again for the info.

 

[ipo412]

You are correct. You can setup a route on the VOIP VLAN to head out the default one. Additionally, you can go the other way as well (I believe), this is how you would do the PHone Manager thing I think.

HTH -T