Lucent Technologies CentreVu Release 3 Version 8 High Availability User Manual page 12

Introduction
Overview
CentreVu CMS R3V8 High Availability User Guide
The CMS HA option allows the following server switch-over options:
1. No switch-over
If you do not require continuous access to your CMS data, you can
elect not to switch-over to the secondary server after the primary
server experiences a major failure event. When the primary server
goes down, uninterrupted collection of call data will continue on the
secondary server, but you may not be able to access that data until
the primary server is restored.
2. Customized software switch-over
If the HA primary and secondary servers connect to CMS clients
and other peripherals, such as NTS servers, printers, etc. over the
same network subnet, LAN traffic on this "user" network can be
automatically redirected from the primary to the secondary server by
means of customized scripting tools set up by the Lucent
Professional Services Organization (PSO). The scripts create an
alias for the IP address of the primary server on the secondary
server.
3. Manual server switch-overs
If your HA servers do not connect to your user network over the
same subnet, the custom software switch-over solution offered by
the PSO can not be implemented. If you still require uninterrupted
access to CMS data, the server switch-over must be performed
manually.
At a minimum, manual switch-over entails the individual editing of
host configuration files on the secondary server and re-
administration of CMS supervisor clients by their individual users in
order to redirect them from the primary to secondary server. Also, if
the primary server is connected to one or more NTS servers,
significant effort may be required to manually switch the NTS
devices over to the secondary server. For more information about
manual server switch-overs, see
Fails".
"What to do if a CMS Server
1-2