Linux DHCP

[BoyRacer1001]

Has anyone managed to get a Linux DHCP server to issue an alternate gatekeeper address in the DHCP offering?

We have the setup working fine for a single MCIPADD address, but the scope appears to be ignored if we add a second address to the scope.
ie

option option-242 MCIPADD=192.168.0.1,HTTPSRVR=192.168.0.2,L2Q=0,L2QVLAN=0";

but

option option-242 MCIPADD=192.168.0.1, 192.168.0.3,HTTPSRVR=192.168.0.2,L2Q=0,L2QVLAN=0";

Does not work at all.

 

[telecomturner]

Did you try removing the space after the comma? 192.168.0.1, 192?

 

[Mitch672]

yes, telecomturner is correct, NO spaces allowed inthe DHCP option 176 or 242 strings. Also, if the 2nd address is a CLAN card, that's fine, if your 2nd address in an LSP, that won't work. You need to setup a node name for the LSP, and on the "IP-Network-Region" form, put any LSP's IP's in that. When the phone registers to the CLAN/PE, the phones gatekeepr list is updated.. If you put an LSP IP in the DHCP scope, it will try to register to it, and if not in LSP mod,e it will fail.

Mitch


AVAYA Certified Specialist

 

[BoyRacer1001]

Thanks, tried without the space and no difference. Seems to ignore the 242 scope completely.

Mitch,
The second address is an LSP, but is required to be there in case the phone reboots during an outage of the primary server.
If the main server is active, the phone should register to that before trying the IP address of the LSP. It will get the LSP address via RCF only once registered.

Don't know if there are any other notations that might be required on the Linus side?

Thanks again.

 

[Mitch672]

BoyRacer1001, sorry, you are wrong about the 2nd address being needed for an LSP. That IP is supposed to ONLY be listed in the "IP-Network-Region" form, under "survivable-gatekeepers" on page 2. The issue with putting it in the DHCP scope is, the phone doesn't know that the 2nd IP is only active while the LSP is active, and you can get your phones in a state where they WON'T be able to register to the main switch, under normal conditions.

Once the phone logs into the main switch, it gets it's gatekeepr list updated from CM, and the LSP address is then put on the list. That's how it works.

It will never work properly putting an LSP address on the "MCIPADD=" list, sorry to say. If your phones lose power, during a main server outage, you are S.O.L., but that's unlikely to happen.

mitch


AVAYA Certified Specialist

 

[Mitch672]

http://www.nacr.com/uploadedFiles/Services/Avaya_Network_Regions_October-2005.pdf

This is old, but check page 18, 2nd half of the page.

mitch


AVAYA Certified Specialist

 

[sjforcum]

Mitch is correct on this...

The gatekeeper list is pushed out to the phones during registration.

SJF

 

[BoyRacer1001]

Thanks for the doc link, haven't seen that one before, very useful.

We have this setup working fine with Windows servers, meaning phones can boot during a WAN outage and register to the LSP OK, and haven't noticed any adverse affects when doing it this way.
The Avaya doc "Avaya IP Telephony Implementation Guide" states this on page 55:

"However, in addition to the list of C-LAN
addresses, the v80 and v90 scopes should also include the S8300 LSP address at the end of the list. This
is because the LSP can take over as the call server for the branch if the WAN link fails. The LSP only
accepts registrations when it is active, so having the LSP in the list does not result in inadvertent
registrations to the LSP"

And unfortunately we have some customers who require this.....

Only other possibility may be the string length being greater than 127 characters, which I will check tonight.