B179 Conf phone will not pull an IP address on one VLAN but will on another? 2

[avayatech2018]

OK I'm going to throw this out there to the more experienced folks! Had a user open a ticket because his B179 stopped working. He's on the first floor on say VLAN 21. Brought it to my desk on the second floor on VLAN 22 and it worked fine. When connected on the first floor's VLAN it will not pull an IP.

I grabbed a new B179 out of the box and programmed it up. Same thing. It will grab an IP on one VLAN but not the other. I have a 3560 switch at my desk. So I had my network team setup switch ports on both VLAN's so I could test. I ran Wireshark and I can see it requesting an IP from DHCP but gets no response on the bad VLAN. I see everything normal for DHCP on the good VLAN. These are running Ver. 2.3.0 Sep 17, 2012 firmware. I've about Googled my fingers off looking for answers. So if anyone has any input at all that would be great. TIA

40 years in Telecom. 2 months on Avaya! Go easy.

 

[avayaguy23]

Factory reset the device.

 

[Wanebo]

Have your network team look at their DHCP helper for that VLAN.

 

[gwebster]

Have you looked at the ReadMe files for more current versions to see if this an identified resolved issue?

 

[avayatech2018]

Avayaguy same results.

Wanebo Network team says all good there.

Gwebster I did see something about a DHCP issue when it's been upgraded from 2.3.0 to a newer version.

Thanks for all the replies so far. I may go ahead and update to the latest firmware and see what happens.

40 years in Telecom. 2 months on Avaya! Go easy.

 

[dialtonebone]

If you go to the same switch and assign a port natively to the voice VLAN in question and then plug your laptop in, do you get an IP? If not, then it's definitely back on the network.

 

[jimbojimbo]

Have had the same issue. It appears to be related to port traffic. Mirror the port and get a Wireshark Trace. I believe there are some LLDP/CDP issues when the phone first comes up on port. Upgraded to latest did not clear the issue. Ended up connecting to a different data switch. Customer was replacing the old switch anyway. Of course assuming you are not using 802.1x.

 

[avayatech2018]

Well just an update. I am getting closer. Did my Wiresharks and saw my Discover was making it to the DHCP server but no Offer coming back. Finally got the server team to send me the DHCP logs. Here's the message:
Packet dropped because of Client ID hash mismatch or standby server

So now I'm working to figure out what this means. I'll post more when i know more.

Thanks

40 years in Telecom. New to Avaya! Go easy.

 

[avayatech2018]

Solved!! I suspected an issue with the configuration of the DHCP Failover options. I had requested screenshots to look over. She sent me the screenshots and stated she "Replicated the scopes". That fixed the issue. I'm able to boot two different units on vlan 17 now. Thanks for everyone's input on this.

40 years in Telecom. New to Avaya! Go easy.