View Single Post
  #1  
Old 09-12-2016, 03:36 PM
rteluk rteluk is offline
Member
 
Join Date: Sep 2016
Posts: 6
rteluk has 10 reputation points
Default 9608 Phones stuck at discover when using DHCP

I'm hoping someone might be able to give me some additional insight on this.

We have an Avaya IP Office 500v2 on the network with 2 HP 1920 Switches.

We have a data VLAN (1) and and voice VLAN (20).

LAN1 of the IPO is on vlan 1
LAN2 of the IPO is on an ip address associated with VLAN 20, the switch port it is plugged into is tagged VLAN 20 and PVID 20 (this port has been changed to untagged 20 as well with no change)

All other ports are tagged 20 and untagged 1 with a PVID of 1.

The router (watchguard) has internet on port 0, LAN (vlan1) on port 1 and vlan20 on port 2.
Port 1 and Port 2 of the watchguard are plugged into the same switch at different ports. The router does dhcp for vlan 20. The watchguard can communicate to the IPO on both lan1 ip and lan2 ip.

I have a 9608 that is getting DHCP from router and then sits at Discover 192.168.20.1 (this is the ip of the IPO on LAN2). The only way for phones to boot up when on the 192.168.20.x network is to make the default gateway 192.168.20.1 (which is the lan2 ip address of the IPO). The default gateway and the switches can communicate (ping and trace route) to 192.168.20.1 with no issues, I am not sure what I am missing here, any insight would be greatly appreciated.
Reply With Quote