PN: 1725-36033-001_G.doc
37
Swapping/Adding/Deleting SVP
Servers
Whenever an SVP Server is removed from the system, wireless
telephones that are using the SVP Server will be affected and calls
may be lost. If the removal of the SVP Server is intentional, the
administrator should lock and idle the system prior to removing an
SVP Server.
Load balancing enables a locked SVP Server to distribute idle
handsets to other SVP Servers in the cluster. Existing calls will not
be interrupted and the SVP Server will become idle once all calls
are ended and idle phones are transferred to another SVP Server.
Adding an SVP Server
A new SVP Server is detected within two seconds of being added to
the system (booted/configured/connected). When detected, wireless
telephones not active in a call will gradually be forced to reboot and
check in again. Any wireless telephone in a call will immediately
switch to the SVP Server that should provide its "timing" function.
This switch should not be noticeable to the user since it is similar to a
normal handoff between APs. When the wireless telephone ends the
call, it will eventually be forced to reboot and check in again. Only a
few handsets at a time are rebooted to prevent excessive check in
traffic on the network. Handsets scheduled to be rebooted can still
make calls and will be rescheduled for reboot when the call is ended.
Removing an SVP Server
The preferred method for removing an SVP Server from an active
system is to first lock the SVP Server. When an SVP Server is locked
for removal from the system, load balancing enables the locked SVP
Server to distribute idle handsets to other SVP Servers in the cluster.
Active calls will not be interrupted. The locked SVP Server will
4
