Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VOIP IPO500 and VLAN configuration help

Status
Not open for further replies.

Ehsaan92

IS-IT--Management
Aug 20, 2015
10
GB
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.
 
The issue has been resolved by changing the trunk port between the PBX and the switch to an access port. After looking a the pcaps i can see the PBX is able receive the tag traffic 802.1q but upon its return it sends it as untagged which goes through the native vlan (data vlan1) and this way it is able to communicate with the phones. this would have worked if the PBX had the capability to tag the traffic upon its leaving port through the trunk, since the PBX is expecting untagged traffic it should have set as an access port on the first place on the switch.

Bodrul
 
Telephone systems like PCs aren't VLAN aware as they don't pass data through themselves as a handset would, beyond routers typically only handsets (and DHCP servers) are VLAN aware on a network. Whoever setup the VLANs on the network cocked this up basically. :)

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top