VOIP IPO500 and VLAN configuration help

[Ehsaan92]

Hi everyone,

First I would like to apologize if my questions has been already answered on tek-tips but so far I couldn't find any info on this regard.

Before I jump into the questions and what I want to achieve, I would like to give you an overview of our current configuration for the AVAYA IPO 500.

The Avaya IP Office unit has 2 interfaces. One (LAN1) on the 192.168.0.0/24 network and one on the (LAN2) 172.25.2.0/24 network. LAN1 should be used for communication between the current site unit and the remote unit. LAN2 is used for the handsets themselves to communicate with the IP Office.

The current configuration for the switch ports people use in the office is configured as follows. Port mode is set as access but the port is set using 2 VLANs: Data VLAN1 and Voice VLAN 10.
The ‘data’ VLAN1 is what all the hosts on the domain network use. The ‘phones’ VLAN10 is what all the handsets use.
The Avaya IP Office has LAN1 plugged in to the Juniper EX4200 switch port on Access VLAN1 (192.168.0.100/24) and LAN2 plugged into the Juniper switch port as trunk, voice VLAN10 as the member and VLAN1 is set as the Native VLAN. Everything works perfectly fine with this config.

Now the problems and challenges:

I have created a new Data VLAN which is VLAN 101 for a new department in the building, on the same juniper switch i have allocated couple of ports and assigned VLAN 101 in access mode, i have also added the voice VLAN 10 on the same port, I have also predefined option 242 on the VLAN 101 DHCP server which contains the info about the VLAN 10, callserver and other VOIP details, committed the change. Next I plugged an AVAYA IP phone 1600 series on the new vlan port, phones boots up detects the Voice VLAN 10 info and that's it, doesn't go any further, keeps on looking for the callserver and dhcp.

Now as you know I would like to have the VOIP phones to work on both data VLAN but with this current config it is not possible, I figured that part out. so my question to you experts is that what additional configuration needs to be done in order to achieve this?

Do I need to setup inter-VLAN routing here? but to me it just doesn't make sense to setup routing here as Voice VLAN 10 is not being altered here, only thing we are adding to the network is data VLAN 101.

Only way the phone works on the new port configured with vlan 101 is to change the trunk port native vlan 1 to VLAN 101 on the switch connected to interface LAN2 on the PBX but that will disconnect phones on the vlan1 and vlan 10. I've done a network simulation on GNS3 and packet tracer with similar configuration, everything seems to work regardless how many data VLAN you add beside the same voice VLAN. it seems like there's some correlation between the Data VLAN1 and voice VLAN10 but so far it's not making any sense to me.

I've tried many other things but don't want to make this post too long.

any suggestion will be much appreciated.

 

[amriddle01]

The DHCP response in the data VLANs should contain the correct VLAN info only, nothing else, so no call server or file server etc. Only in VLAN 10 do you enter the full string

 

[Ehsaan92]

@amriddle01 Thanks for your input. I think I have alreaady tried that but I will give another go. On the Avaya office options 176 and 242 are ticked as the AVAYA IPO is the DHCP server for the phone on VLAN10, is there anything else needs to be configured there?

And also it's worth to mention that even if i set the phone up manually it still unable to reach the Avaya server.

 

[amriddle01]

Then you also have routing issues

 

[amriddle01]

Or your VLAN configuration is wrong, probably more likely.....

 

[Ehsaan92]

Can you explain why routing is required? since the IP phones and the callserver are on the same VLAN.
VLAN 101 seems to able to talk to other VLANs just fine, i have Palo alto 3050 firewall which routes the traffic between vlans if need be and it doesn't read vlan header and junper does the tagging. I mmean I can create another data vlan and test it out.

 

[derfloh]

There should not be any routing necessary. I assume the voice VLAN has a gap somewhere. Like configuring a new switch with the new data VLAN and the old voice VLAN but the voice VLAN is not member of the uplink port between switches. So the phone gets it's VLAN info from DHCP but cannot reach IPO because of the gap...

 

[Ehsaan92]

Hi derfloh,

hmm if this is the case than how come phones on data vlan1 and VLAN10 working just fine? there are stack of two juniper switch with virtual chassis and phones on the bboth switch works fine but not when access port data vlan 1 is changed.

However your assumption does indicate that there's some issue with the voice vlan as the phone is able to get the DHCP details from VLAN 101 but fails to connect to vlan 10 call server.

 

[amriddle01]

I can guarantee one thing, this isn't the system or the handsets at fault

 

[Ehsaan92]

Ok Riddle01,

Your given guarantee is not my solution

I don't know who actually configured this box as I have only started to work for this company just recently.

Ok On LAN 2 on the PBX i can see on the DHCP pool default gateway is not defined, the callserver is on VLAN 10 172.25.2.1/24 and file server is on VLAN 1 192.168.0.16/24, now it seems like the phone has to have data communication between vlan1 and vlan 10!. what does your brain say Riddle? and do you have Avaya in your production environment, why don't you tell me how's everything setup on your end?

 

[amriddle01]

The companies file server is not what the phones need, they get their files from the IP Office (unless you have a specific file server for the handsets on that address) and the system will give it's own address as gateway with that field empty and is not needed if your VLANs are configured correctly as they would all be in the same subnet. My setup is irrelevant to you, but rest assured it works fine

 

[Ehsaan92]

File server is on IP office and it's for Phone only, therefore i am asking the question whether the callserver and file serve should be on the same subnet? From what I understand is the when Phone boots up on the current working configuration is it talks to the file server through data vlan 1 and call server via voice vlan 10. H

 

[amriddle01]

No, that would be silly, it just gets it files from the system in the voice VLAN, the fact you have another interface in the data VLAN is irrelevant to the handsets

 

[Ehsaan92]

ok but on the phone it clearly displays it's contacting file server http 192.168.0.16 and there it shows 'no file server' and stucks on 'Discovery 172.25.2.1'

 

[amriddle01]

Then something is telling it that address in a DHCP response or it's statically assigned. Discover means it can't see that address at all, again no configuration in the handsets or system will solve this, it's the way your VLANs/network are/is configured.

 

[Ehsaan92]

Alright so the phone and the system is not culprit here.

I might be setting up everything from scratch, do you know is there any documentation out there which help do the following: 3 Data VLANS for three different department, one voice VLAN to be used by all the three department. Switch port will be configured with Data VLAN 50, Voice VLAN 10 for Finance, Data VLAN 60, Voice VLAN 10 for Marketing and Data VLAN 70, Voice VLAN 10 for Technical. I am sure there's no in inter vlan routing involved here but can you advise or point to me any resources where i can take refuge and set this up as I am losing my hair everyday on this BS. thanks

 

[gwebster]

If you have three different voice VLANs, then all three of those VLANs are going to need to be routed to/from the IP Office. You are also going to need routing BETWEEN those VLANs if you want users on one VLAN to talk to users in another VLAN (since voice packets, by default, are routed directly between two IP phones).

 

[Ehsaan92]

Hi Gwebster,

I wan't to avoid the routing here, that's why I am looking for solution to use single voice vlan associated with different data vlans. The data vlans will route through my PALO 3050 firewall as untagged and then Juniper will re-tag the packets upon the firewall egress interface.

Is this possible to have a single Voice VLAN to work around different data VLANs?

 

[gwebster]

My mistake on reading your email. You did state a single voice VLAN. You need to configure things such that the IP Phones get redirected to the single VLAN.

 

[amriddle01]

You're asking networking questions in a telephone system forum, an Avaya may be involved but has nothing to do with your questions, best place would be a Juniper forum really