Lucent Technologies Release 3 Version 8 Basic Configuration Rules, Manual server switch-overs

Page 14

 

Connecting HA Servers to the Switch

CentreVu CMS R3V8 High Availability

 

 

 

Connectivity, Upgrade and Administration

 

 

Overview

2-2

 

 

 

 

 

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. The scripts, which are set up by PSO, create an alias for the IP address of the primary server on the secondary server.

3.Manual server switch-overs

Basic

Configuration

Rules

If the customer is unable to connect the two HA servers to the “user” network via a common network subnet, the custom software switch- over solution offered by the PSO can not be implemented.

Therefore, if the customer still desires uninterrupted access to their CMS data, the server switch-over must be performed manually.

At a minimum, manual switch-over entails 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.

Depending on the nature of the customer network, additional measures may be required, such as re-administration (or duplication) of NTS servers, physical reconnection of peripheral devices, etc. Customers considering the manual switch-over option must be strongly encouraged to consult with their TSO and/or PSO representatives in order to discuss logistical issues associated with manual server switch-overs.

CMS HA servers must be physically located in the same building, and ideally, should be directly adjacent to each other in order to facilitate ease of maintenance.

CMS HA computers can collect data from up to eight different ACDs. Mixed ACD links, in which the server is connected to both single (standard CMS) ACD links and HA dual links, is not supported. If implemented, mixed ACD links could potentially result in significant call data loss, and could also fill up system error logs with meaningless data.

Link connections are implemented only by the TCP/IP over ethernet LAN communications protocol, and connections must run over LAN facilities local to the switch.

Each CMS HA server should be connected to a separate UPS on a separate protected power circuit.

Page 13 Page 15
Image 14
Page 13 Page 15
Contents CentreVu Call Management System Comments Table of Contents Page Page Page Introduction OverviewSupported Definity Switches Supported CMS Platform CombinationsRequired and Optional Software Chapter Task Technician Special Upgrade ConsiderationsGeneral Roles and Responsibilities Software CustomerCustomer-Specific Roles and Responsibilities CentreVu CMS Helplines Technician Support for U.S. and CanadaServer Switch-Over Options No switch-overManual server switch-overs Basic Configuration RulesCustomized software switch-over Connecting Blocks Planning for LAN Switch Links Overview Connectivity Options Connecting to the Definity SwitchOverview Ethernet Ports on a CMS ComputerConnecting with a 10Base-T Hub Quantity Description Comcode RJ45 UTP Category 5 modular cordCabling Diagram LAN via 10Base-T Hub HA Upgrade Scenarios Upgrading CMS to the High Availability OptionHA Upgrade Scenarios Overview HA Upgrade Procedure HA Upgrade Scenarios HA Upgrade Scenarios Tape Verification Procedure Verifying the Tape Drive on an Enterprise 3000 ServerPerforming a Cmsadm Backup PrerequisitesBackup Filesystem Pkginstall Xxxxxxx blocks Performing a Cmsadm Backup Performing a Full Maintenance Backup Performing a Maintenance Backup Administration Data Only System responds Setting Up CMS on an HA Server Overview PrerequisitesSetting Authorizations OverviewProcedure Program respondsPurchased version is R3V8. Is this correct? y/n Authorize use of external application feature? y/n Default n Switch Agent Number of Split or Skill Members Purchased Non-EASCapabilities/capacities authorized date/time Setting Up Data Storage Parameters Overview ProcedureSetting Up CMS on an HA Server Setting Up CMS on an HA Server Setting Up a LAN for Switch Connections PrerequisitesProcedures EditingFile Overview Prerequisites Setting Up the CMS ApplicationSetup Methods Procedure OverviewEnter 4 to select Setup option If system setup has already been done, the program respondsPress enter to accept the default. The program responds Is Vectoring enabled on the switch? y/n Enter the local port assigned to switch Enter 2 to select TCP/IP Program responds Enter the number of shifts. The program responds Number of trunk groups Enter the number of vectors. The program responds Tail /cms/install/logdir/admin.log Setting Up CMS Using a Unix Flat File Editing the FileCms3 192.168.2.2 0800AM # Definity-G3V5/Definity-R6/R7/Definity-R8 Flat File Enter 2 to select the flat file option. The program responds Tail -f /cms/install/logdir/admin.log Overview Prerequisites Procedure Installing Feature PackagesInstalling Forecasting Package Authorizations on Select the pkginstall option. The program responds Forecasting package installed date/time Installing External Call History Package R3V Backup Filesystem backup Pkginstall Printers, and Modems 585-215-874. The program responds Number of call segments to buffer for ACD xxxxx Package on Setting Up the Remote Console Hardware Platform Port a Port BRedirecting the Remote Console Port to the Modem Redirect the console back to the local console by entering Configuring Setting Up the Alarm OriginatorSetting Up the NTS Eeprom configuration information Flash self-boot image Enter 1 to erase EEPROM. The program responds Enter N. The program returns to the monitor prompt For the 64- port NTS, the boot file name is Creating an Alternate Boot Device for Mirrored Systems Migrating CMS System Administration Data to the New ServerMigrating CMS System Administration Data to the New Server Checking the Archive Interval Administering the Switch Performing an Incremental Maintenance BackupUpgrade the Original CMS Server Migrating CMS Historical Data to the New HA Server Migrating Administration Data Back Onto the Original Server Migrate Administration DataMigrating Administration Data Back Onto the Original Server Performing a New Full Maintenance Backup and Restore These error messages can be ignored Performing Cmsadm Backups on the HA Servers Setting Up Version and Release Values Multiple ACDs Switches on HA SystemsAdministration Overview Determining Switch/CMS CompatibilityDefinity Switch Administration Adjunct CMSSetting the Switch Version Field DefinitionSetting the Call Center Release Call Center Optional FeaturesSetting Adjunct CMS Release Call Center System Parameters Agent and Call SelectionOverview Administering LAN Connection Administering the Definity SwitchSetting Up the Link on the CMS Computer Form Purpose Adding a Second Packet Interface Administering the Definity Switch Adding Node Names and IP Addresses Node NamesProcedure. See CentreVu CMS Software Adding a C-LAN IP Interface LAN Adding an Ethernet Data Module Adding Processor Interface Channels Processor Channel AssignmentAdding IP Routing From a gateway for example, a router to a networkAdministering the Switch for CMS High Availability Systems Administering the Switch for CMS High Availability Systems Index IndexIN-2
Top Page Image Contents