Avaya J179 VLan's & IP Office 1

[DominicE]

Hi,

Would someone kindly be able to clarify the best practice for assigning the voice and data vlan's on a J179 phone with a computer attached to the secondary network port. Although there seems to be a lot of information on Google a lot of it is contradictory or partial.

I am currently using the IP Office to assign the J179 IP addresses, which I would like to keep using. At the moment data and voice are on the same vlan, which I now want to split. As far as I can see there is no way to configure the DHCP server on the IP office UI to assign the different data and voice IP's (option 242 string), although there is a vlan drop down, but I can't find anywhere how to change this to another other than not present or disabled, so I'm not really sure what that is for?

The Avaya doc's say using DHCP is the preferred option for assigning the vlans, but if I'm going to carry on using the IP office for DHCP I assume this is not going to be possible?

The next option then I assume is to using the settings text file and do is that way, assign the voice and the data vlan in there and then set the port switch to trunk? Which is probably my preferred option.

Or thirdly use the auto vlan feature on the switch against the MAC of the IP photos, which would probably be easier but I'm not convinced the best.

Appreciate there's probably a lot of posts on this, but I can't quite pull it all together to form a decent answer.

Thanks for your help.

 

[TouchToneTommy]

Are you using the IPO as the DHCP Server and Internet gateway for your computers??


Normally, you add the option string to your existing DHCP server on the Data VLAN, which instructs the phone to reboot and connect to the Voice VLAN. The IPO is on a port that is only a member of the Voice VLAN and untagged, so that it will become the DHCP server for the phones.

I usually connect the LAN-1 port to the Data VLAN, and the WAN (LAN-2) port to the Voice VLAN, and configure LAN-2 as DHCP server for the phones

 

[DominicE]

Thanks for the reply.

I am just using lan port 1, which connects to the network and serves the IP addresses to the phone. It's not an internet gateway for computers, I'm not sure what I said to imply I was doing that.

So the recommendation is to not use the Avaya DHCP to solely serve the phones, but to in fact have one DHCP setting the voice vlan ID, wait for them to reboot and then use the Avaya IP DHCP from within that - seems a fairly convoluted way to do it.

It does sound like it'll work, but I thought there would be an option to only use the one lan port and not effectively connect the wan port up again within the same switch. It was my understanding that the wan point is effectively internet facing if you thought that was a good idea, so if that was the case I'm not sure how connecting both up within the same switch would work.

If that's the best way to do it, I will try that. I was hoping there would be way to carry on using just the 1 lan port.

Thanks,

 

[jamie77]

If your VLANs are properly routable, then you only need the 1 port and put that in the voice VLAN. Customer will need to setup DHCP from thier server to act in both VLANs or you can still use the IPO.

Its really all about QoS, so make sure the voice VLAN has priority over the rest. Thats the real point. VLAN is just 1 way of acheiving QoS.

Although it is physically named as a WAN port on the back, never use it as one. Its a second LAN port. Keeep the IP Office from the public internet at all costs.

Let the customer Networking team design the network and work with them and advise.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[IPGuru]

sslp on the switches should make it reasonably simple

cust dchp server for data lan, assign IPO fixed address on one of the lan ports (DHCP Disabled)
IPO DHCP server for Voice Vlan using the other IP Office Lan Port

ensue the pots the IPO lan ports are fixed to the correct Vlan

(apologies for terminology I am not a data switch engineer but this is how we recommend custs configure their network, it also matches what Avaya recommend in their installation guide for their data switches)

your installer /maintainer should be advising on this to ensue things go smoothly, if they wont or cant then I would suggest finding a competent installer



Do things on the cheap & it will cost you dear

 

[DominicE]

Hi,

Thanks all for the replies, does this sound like a reasonable solution:

Two vlan's, vlan10 for data, vlan20 for voice.
LAN port 1 of the IP Office connected to LAN (don't use wan port), with a PVID assigned to the port, vlan20.
On vlan10 (default vlan) dhcp server, add the voice vlan20, which causes the phone to reboot onto that one.
IP Office on the vlan20 IP range, ready to offer the dhcp request to phone that join vlan20.
Set the appropriate trunk ports.
Add a route between vlan10 and vlan20 for management of the IPO from the router.

Having read a fair few articles on this, this seems like best practice if you don't want to plug both lan and wan into the same network - does that sound reasonable and like it will work?

Thanks,

 

[IPGuru]

sounds perfectly reasonable to me


Do things on the cheap & it will cost you dear

 

[DominicE]

Following a test last night:

DHCP worked getting the phone onto the correct VLAN
IP Office was fine communicating with the phones that then appeared on the VLAN and the new IP range/gateway.
So for all intents and purpose it was segreted correctly with voice on a seperate VLAN and a route to communicate between the two for management of the IPO.

The only problem was, it increased the round trip delay on a call from 20ms on average to about 50ms - so I've reverted it pending further investigation out of hours.

Thanks