Phones get stuck on "Initializing" despite getting an ip

[onealcatel]

Hello,

We had a problem with our Alcatel, that is hosted on another site than our production. So there's an IPSEC tunnel between our production site and our Alcatel.

Today we had a very short outage of our IPSEC tunnel, which made the phones being disconnected from the Alcatel.

And then the problem started, the phone were stuck on "Initializing" for a while, then reboot, and stay on "Initialazing" again and again.

The workaround we found to make the phones working again was to put a IP reservation for each phone, with an IP that waas not used by the DHCP. (Which means than going to leases --> Add reservation does not work. We have to delete the lease, create a new IP reservation with an IP outside the scope of the leases already assigned, or the phone will not work).

So for example, the phone that had the IP 172.24.1.1 before the ISPEC disconnect, would not work until I make a new reservation for this phone with an IP like 172.24.1.200 (Outside of the leases scope).

We saw this kind of messages on our Alcatel logs :

Code: Select all

02/10/14 12:38:58 000003M|002/00/0/053|=4:0382=Init of IP set: No response from de set 00:80:9f:58:80:80,11124403
02/10/14 12:38:59 000003M|002/00/0/053|=4:0386=Sig. on IP set: No response from de set 00:80:9f:58:80:80,11124403
02/10/14 12:38:59 000003M|002/00/0/053|=4:0383=Init of IP set: IP Link down 00:80:9f:58:80:80,11124403

Problem is that from the Alcatel, we can ping the IP of this phone, before it reboots and get stuck on "Initializing". This should not be a network problem as we have every other phones workign after we did the workaround above, but we were getting this message for every mac address.

I looked at the ARP cache on our edge switch, and the MAC/IP association were correct.

Any idea on what the problem could be, or how to digg a little bit more to try to find the cause ? I am far from being an expert on Alcatel so I am even not sure where/what to check exactly... Any help would be greatly appreciated

Thanks !

[enio.eltz]

Hi

It seems a LAN issue, but traces would be your friend to discover the cause.
Try to get wireshark traces from the whole process of IP touch initialization and post here.

Best regards.