4610SW Phones registration problem using multiple CLANs

[rbr123]

Hi Everyone!

I have 4610SW IP phones (mix versions of 2 and 2.2) previously working then suddenly gets bad IP address error. I validated the DHCP scope (option 176) then finally make it work after removing 4 CLAN IP addresses from the scope(I have 5 CLANs). Eventhough I have 1 CLAN board assigned, other phones are still connecting to the rest of the CLAN boards... and I guess because they share the same network region #. Can someone help me explain why this thing is happening? I am also concerned that if the CLAN board assigned to the DHCP scope goes down, the other phones connected to the rest of the CLAN boards that are not in the DHCP scope might disconnect as well. Please help.

Thanks!

 

[84Mike]

The system usually will automatically balance the load across all available CLANs.

 

[Dunstan]

If the CLANS share the same network region then you cannot specify which one will be used by each phone due to dynamic load balancing.

When a phone first registers it gets a list of potential CLAN boards available for that Network Region. So in theory if you lose one the phones attached to it will look for the next one in their respective IP-Network_region.

 

[JayNEC]

BUT if the phone(s) reset, and that 1 CLAN is down, the switch cannot tell the phone about the other 4 CLAN's. That occurs during registration, and the phone can't contact the switch in the first place.

You should have 2 clan's in the DHCP scope. If the 1st is gone, then the phone itself will try the second. Then the switch will load balance among those remaining three boards.

 

[rbr123]

Thank you everyone! But still, my problem is the DHCP is not allowing me to add more CLANs. It somehow limiting me to one CLAN and if I add one more, the phone will get a bad address error.

 

[Dunstan]

Post your option 176 setting in your DHCP server scope...Maybe one of us can see the issue.

 

[rbr123]

Dunstan,

Here's the setting of the current settings on option 176

Data VLAN 72:
L2Q=1,L2QVLAN=206

Voice VLAN 206: MCIPADD=10.0.203.203,MCPORT=1719,TFTPSRVR=10.3.35.22,10.3.35.20,10.3.35.21,L2QVLAN=206

Appreciate all your help!

 

[JayNEC]

Ok, but post the option that is causing you problems.
This one is working for you right?

 

[rbr123]

Data VLAN 72:
L2Q=1,L2QVLAN=206

Voice VLAN 206: MCIPADD=10.0.203.203,10.16.0.51,10.16.0.50,10.16.3.10,10.16.3.11,MCPORT=1719,TFTPSRVR=10.3.35.22,10.3.35.20,10.3.35.21,L2QVLAN=206

 

[JayNEC]

So, do you get an error if you only put two CLAN's on the list instead of all four?

 

[JayNEC]

You could also strip down the TFTPSRVR. It might be that the string is too long.
The TFTP server is not usually absolutely necessary for operation. The phone will timeout on the TFTP if it's not up and go on and register. It will just take a little longer.

 

[rbr123]

JayNEC,

I get errors if I add more CLANs (more than one). This is really weird as this was running before and we already checked the network as well as the DHCP server and all are running fine.

I'll try to remove the other TFTP server IP address as suggested. If this thing doesn't work, do you have other suggestions?

Thanks!

 

[rbr123]

We actually have around 1,900 running IP phones and this is the only time we experienced this kind of issue.

 

[stlouis1]

If you still have the problem you might want to do an SNMP query to the phone's IP address. You'll find the MIB on Avaya's support site. Look at the MCIP list - how does it compare to what is in your DHCP tag? This isn't a definitive check - I've seen bad option 176 tags and still the SNMP list looks ok. Also, if this is only one phone may be it is soft failure in the phone memory - I've asked Avaya on similar kinds of failures if they could give me a checksum of a load or run a memory test and they had nothing to offer.

 

[Dunstan]

You could also use the IP boot test program available from Avaya. This will show you a verbose attempt at accessing the 176 options....it may lead you to the issue.

 

[rbr123]

Dunstan,

Does AVAYA IP boot test support multiple VLANs?

 

[Dunstan]

It has some limitations with respect to Vlans....Hit this link for a more detailed explanation. Scroll down to the *known issues* section.

I am not sure this will work in your environment but it cannot hurt

http://support.avaya.com/BootTest/instructions.html

 

[FSI]

and each of the CLAN addresses alone works? so you only receive the error if 2 or more are entered while each one on its own works fine?

Regards

Frank

 

[vamosalavaya]

Hi,

What's your netmask for Ip-Phones and Clan ?
Does all your ip range (10.3.x.x. / 10.16.x) are set in ip-network-map to assigned your phone in right ip-network-region ?


Have you tried to ping ip-phone from each clan and all clan from an ip-phone ?
are you routing the traffic from you clan to ip-phone trhough firewall or layer 2 gateway ?
regards
Michael

 

[rbr123]

Thanks to all who replied on this concern. We have resolved the issue. We met the maximum character that should be defined under Option 176 field. We just removed some of the CLAN IP add defined in this field and eft 2 addresses.