multiple SVP devices

[pbxNewb]

Can anyone tell me if its possible to have two SVP devices (Nortel 2245 WLAN controllers) operating at the same time but in different VLANs? I have to migrate all my 6140 wireless phones to new APs, basically a whole different network. The APs are in place alongside my existing access points. The new APs will be using a different SSID and IP scheme.

My thought was to purchase a second 2245, create a new VLAN, configure the 2245 the same as the original except with its own IP and alias IP ranges to work with the new VLAN. Then I would move the wireless phones over one by one with no global system downtime, continuing to run them both in parallel until the migration is complete. Then I would unplug the original 2245 and keep it as a spare.

Is this possible? I've got it all setup and configured, but my wireless phones are saying NO SVP followed by the IP address of the original SVP source. I statically assigned the phones with the new SVP IP address but they are somehow getting the old IP? Does this come from somewhere in the PBX? I looked in my DHCP scope, and there is no SVP address anywhere, just my NODE IP and a few other nortel things in the deployment options. Where do the phones get the SVP address from if not DHCP?

Sorry for all the questions, but any help would be appreciated. This is on a Nortel CS1000 rel 4.5. Thanks!

 

[allenmac]

The phones get the SVP address from DHCP - I believe it is in option 51 (I could be wrong), so that is why they are pointing to the original.

You should be able to run both at the same time. You will have to adjust your DHCP server so that the new phones receive the IP address of the new server.

 

[Wings08]

I have done this when I converted all my sets from WEP to WPA2. The WAN guys setup the new network. Actually, when you are completed with moving your sets you can add the other svp to your network. If you have the latest firmware on your svps, the wireless sets will load balance between them. If you added enough alais IP addresses between the SVPs you will have a failover if one goes belly up. Just a thought.

Your phones (6100 series) will attempt to connect to the SVP eight times then they will fault over to the last SVP address stored in NVRAM of the phone. I recently just found this because of an issue with a new DHCP server. The phones could get the address from DNS is those options are configured. look for a DNS entry SLNKSVP2. You can pull up additional info by searching the net for Nortel DHCP options.

 

[pbxNewb]

Same issue, new problems. As it stands now, my phones are NOT getting the new SVP address via DHCP. I have it setup in the scope under option 151. The phones are getting DHCP information from the scope (we can ping them even though they stop and hang on No SVP Response xxx.xxx.xxx.xxx). They get an IP in the correct range, but without the SVP information, they cannot get an alias IP and so don't work. If I flash them with a static IP configuration, then switch them back to DHCP they work fine. I'm assuming this is because they "remember" the last successfuly SVP source from the static config and continue using it.

The odd thing is that the IP it is not getting a response from is 049.048.046.050. NO WHERE in the system is this even a valid IP address, I think its in the public range. I checked the 2245, and its not there, nor is it in DHCP anywhere in the company. Is this a default value programmed by Nortel/Avaya when these devices are flashed at the factory?

 

[Wings08]

That address is exactly the same SVP address we are getting. What DHCP server are you using. I have found a work around to get phones up. Grab a usable physical IP address designate for your phones. Use the config tool and program as static. Fill in all the pertanent server info. burn to the phone and boot up. once it connects turn off and go into config mode of the phone and change to DHCP and Full Dhcp. Let the phone boot up. It might boot twice. This is been a pain to figure out. Our WAN guys have been working on this for several days. Still no resolution yet.

 

[pbxNewb]

Thats the work around I've figured out through some trial and error. Works fine, just takes a little bit longer. Wish those network guys could figure this out, they just want to keep blaming the 2245 or the phones themselves. Typical pass the buck, you're out of luck.

 

[Wings08]

Do you know what they are using for their DHCP server?