CLAN Socket Connections Prioritization Algorythm

[CChambleeJr]

I need some help understanding how the AGL list is built and prioritized.

Assuming:

IP-NETWORK-MAP ENTRIES ARE:
192.168.1.0 to 192.168.1.255 /24 NR14
192.168.2.0 to 192.168.2.255 /24 NR15
192.168.3.0 to 192.168.3.255 /24 NR16

IP-NETWORK-REGION:
Regions 1, 14, 15 and 16 are connected to each other via direct WAN, no limits.

IP-I:
procr NR1
CLAN 01A02 NR14
CLAN 01B02 NR14
CLAN 02A02 NR15
CLAN 02B02 NR15
CLAN 03A02 NR16
CLAN 03B02 NR16

The MCIPADD in the DHCP scope option 242 is set to the IP address for CLAN 01A02.

If IP phone at address 192.168.1.10 boots up, upon registration, what will it's AGL look like?

If IP phone at address 192.168.2.10 boots up, upon registration, what will it's AGL look like?

If IP phone at address 192.168.3.10 boots up, upon registration, what will it's AGL look like?

I hope that I have given enough assumptions and info for the answers to be determined.


===
Chuck Chamblee
ACSS (CM) | CTP | A+ ce | Security+ ce

 

[jimbojimbo]

If you utilize numbers instead of 'all' in the IP-Network-Regions then you can status the phones and the AGL list will be on one of the status pages.

You may want to search for "Alternate Gatekeeper and C-LAN Load Balancing Configuration for Avaya IP Telephones.....". This is an old document from 2002 but will give you the basic premise of the CLAN connectivity algorithm.

Another good document is the "Avaya IP Telephony Implementation Guide Communication Manager 3.0" from 2005.

Last document is "Administrable Alternate Gatekeeper List for IP Endpoints using Avaya Communication Manager" from 2008 which goes into the changes introduced starting in CM5.1.

If you are on older software you may find you have some odd behavior when it comes to CLANs and failover. There were differences in capacity on the older phones and how many CLAN addresses would fit in the AGL on the phone. With a large number of CLANs this would potentially prevent the LSPs from being included (fixed somewhere around 2.3 if I'm not mistaken).

As a side note, you may want to review the changes Avaya introduced related to the Enhanced Media Selection Algorithm in CM5.2.1 SP12/CM6.0.1 SP8 and CM6.2 SP1.