Inverted IP addresses 1

[Manie3]

HI All

I have an issue at site where by the ip addresses come back inverted. For instance 192.168.XXX.XXX shows on the handsets as XXX.XXX.168.192. They get stuck in discover mode as you can imagine. When you statically assign the handsets it goes through correctly. I have checked the network switch which has LLDP and DHCP settings for the handsets and this all seems correct.

lldp vendor-specific call-server 1 192.168.XXX.XXX
lldp vendor-specific file-server 1 192.168.XXX.XXX
ip dhcp-server pool Voice option-242 mcipadd 192.168.XXX.XXX httpsrvr 192.168.XXX.XXX

Current solution for the system is Hosted Server edition select. version 10.1 build 1. Traffic runs over a VPN to a Fortigate firewall. On site they two 48 port Avaya/Extreme switches with 60 odd 9611s.

If anyone has any pointers or experienced this issue before and has an idea where to check it would be much appreciated.

Thank you

ACSS

Just another day in the life of ME

 

[RocketJTech]

Does the DHCP Server assign addresses to anything that is NOT an Avaya phone? If not, try connecting a device (laptop, etc), so that it gets its IP Address from the same source. Then, check the assign ed IP Address in the command prompt.

If other devices ARE assigned IP Addresses from the same source, does the same thing happen on those devices? If yes, the problem is in the DHCP server. If not, you may have a corrupt file giving bad information to the phones.

If/when you resolve this, I'd love to know the outcome.

Thanks to technology, we can instantly communicate across the world, but it still doesn't help us know what to say.

 

[TheSmash]

Hi Manie,

I'd suggest trying using either LLDP or DHCP Options to provide the call and file servers. Not sure you need both. Can't say that this is what is causing your issue but worth a try. Are you using ADAC on the switches? I found this to be a little flakey.

Alternatively, switch is all off and put in a temp DHCP server and see if this solves your issue. If it does, escalate the problem to Extreme.

Anyway, I'm on hols so won't be back to check how you are getting on! ;-)

ACSS (SME)

 

[Manie3]

@RocketJTech @TheSmash

I made a site visit the other day to try determine what is happening.All ports on the GUI only have VLAN ID 3 assigned to them which is the correct VLAN. the handset that have come up incorrectly with an inverted IP address display VLAN ID 0 however looking at the switch config, there is no VLAN id associated. Even in the VLAN table you can see it is assigning the VLAN to 3 to the same mac address of the handset that is coming up incorrectly. When the handset boots up and you log in the handset goes to discover. if i break into the phone all the DHCP settings are correct apart from the call svr and HTTP svr these come back inverted. I scroll down to the VLAN id which is set to 0 change this to 3. The handset reboots and it comes up as you would expect it. I have tested various ports on the switch and it doesn't happen to all of them. i had to set up a port mirror so i can run a pcap.

Will keep you posted on what happens next.

Thank you both for your advice.

ACSS

Just another day in the life of ME

 

[Manie3]

@TheSmash @RocketJTech

Just to let you know that Extreme have identified this as a bug in the software from 6.0 to 6.1 and will be resolved in 6.2 released in October!!!!



ACSS

Just another day in the life of ME