Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies Centrevu Release 3 Version 8 High Availability Connectivity, Upgrade And Administration Manual
Lucent Technologies Centrevu Release 3 Version 8 High Availability Connectivity, Upgrade And Administration Manual
Have a look at the manual Lucent Technologies Centrevu Release 3 Version 8 High Availability Connectivity, Upgrade And Administration Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability Connectivity, Upgrade and Administration Installing Feature Packages3-51 Procedure31. Access the CMS Services menu by entering: cmssvc The program responds: 2. Enter 1 to select the auth_display option. The program responds by displaying the current authorizations (for example): 3. Verify that the system is authorized for the External Call History package. If External Call History is not authorized but should be, go to “Setting Authorizations” on Page 3-15 (this procedure can only be performed by CMS provisioning personnel). Lucent Technologies CentreVu(R) Call Management System Services Menu Select a command from the list below. 1) auth_display Display feature authorizations 2) auth_set Authorize capabilities/capacities 3) run_cms Turn CentreVu CMS on or off 4) setup Set up the initial configuration 5) swinfo Display switch information 6) swsetup Change switch information 7) patch_inst Install a single CMS patch from CD 8) patch_rmv Backout an installed CMS patch 9) load_all Install all CMS patches found on CD 10) back_all Backout all installed CMS patches from machine Enter choice (1-10) or q to quit: Version purchased: R3VX Capability/Capacity Authorization ------------------- ------------- vectoring authorized forecasting installed graphics authorized external call history authorized expert agent selection authorized external application authorized More than 2000 VDNs measured authorized Lucent Technologies CentreVu(R) Supervisor authorized Lucent Technologies CentreVu(R) Report Designer authorized Maximum number of split/skill members 10000 Maximum number of ACDs 2 Simultaneous CentreVu Supervisor logins 250 NOTE
Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability Connectivity, Upgrade and Administration Installing Feature Packages3-52 4. Access the CMS Administration menu by entering: cmsadm The program responds: 5. Select the pkg_install option. The program responds: The system displays only feature packages that are authorized but not yet installed. 6. Enter the number that corresponds to the External Call History package (in this example, 2). The program responds: Lucent Technologies CentreVu(R) Call Management System Administration Menu Select a command from the list below. 1) acd_create Define a new ACD 2) acd_remove Remove all administration and data for an ACD 3) backup Filesystem backup 4) pkg_install Install a feature package 5) pkg_remove Remove a feature package 6) run_pkg Turn a feature package on or off 7) run_cms Turn CentreVu CMS on or off 8) port_admin Administer Modems, Terminals, and Printers Enter choice (1-8) or q to quit: The CMS Features that can be installed are 1) forecasting 2) external call history Enter choice (1-2) or q to quit: NOTE Enter name of computer to which to send call records (up to 256 characters):
Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability Connectivity, Upgrade and Administration Installing Feature Packages3-53 7. Enter the name of the computer where call records will be collected. The program responds: 8. Press Enter. The program responds: 9. Press Enter. The program responds: 10. Enter the password for nuucp of the receiving computer that was administered in uucp. The program responds: 11. Enter the CMS port administered for the Call History Reporting machine. This port can either be on one of the 64-port NTS patch panels or on one of the 8- or 16-port NTSs. For more information on administering the ports on the NTS, see CentreVu® CMS Terminals, Printers, and Modems (585-215-874). The program responds: Enter full path of the program to transmit the external call history files: (default: /cms/dc/chr/uucp_copy) Enter full path of the program to check the external call history file transmission: (default: /cms/dc/chr/uucp_check) Enter password for nuucp login on computer (up to 8 characters) Enter CMS port for connection to computer (s_pdevxxx): Select a speed for this connection 1) 19200 2) 38400 Enter choice (1-2):
Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability Connectivity, Upgrade and Administration Installing Feature Packages3-54 12. Enter the speed that the connection between the CMS and Call History Reporting machine will be using. The program responds: 13. Enter the number of call records to be held in the buffer if the Call History machine cannot accept the data. (This step reserves disk space; therefore, sufficient disk space must be available.) This step is repeated for each administered ACD. The program responds: If the setup determines that you do not have enough file space, you will get the following warning message: Number of call segments to buffer for ACD xxxxx (0-99999): NOTE Computing space requirements and file system space availability. External Call History package installed. Failed to find sufficient file space for CMS data. WARNING: You do not currently have sufficient file space for your existing CMS data. At this point you should turn on CMS, go to the “Data Storage Allocation” screen, and verify/modify the administration, or go to the “Free Allocation” screen and verify your existing free space. External call history package installed with warnings.
Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability Connectivity, Upgrade and Administration Installing Feature Packages3-55 14. Verify that the installation completed successfully by entering: tail /cms/install/logdir/admin.log If the External Call History package is installed successfully, the program responds: You may edit this file in order to add comments about the packages that were installed or authorized. If you need to install Forecasting, go to “ Installing the Forecasting Package” on Page 3-46. If you are not installing any other feature packages, do the following to turn on CMS: 1. Access the CMS Services menu by entering cmssvc. The menu appears. 2. Enter 3 to select the run_cms option. 3. Enter 1 to turn on CMS. CMS turns on. External Call History package installed (date/time )
Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability Connectivity, Upgrade and Administration Setting Up the Remote Console3-56 Setting Up the Remote ConsoleC OverviewCThis section describes how to redirect the remote console port on the new HA server using the Solaris software package. Remote access is required for both the primary and secondary servers. Redirecting the console allows the TSC to dial in and do remote maintenance. Since the X.25 communications protocol is not supported on HA systems, either port can be used for the remote console. However, the standard provisioning convention is to use Port A for Enterprise 3000 and 3500 platforms and Port B for Ultra 5 platforms. Platform Considerations C •All platforms. Administering the Remote Console Port C To administer the remote console port on the back of the CMS computer, do the following: 1. Remove the current port administration by entering: /cms/install/bin/abcadm -r ttyX (where X is “a” or “b”) The program responds:Hardware Platform Port A Port B Enterprise 3000 Enterprise 3500 Remote Console Not used Ultra 5 Not usedRemote Console ttyX is currently set to be incoming Are you sure you want to change it? [y,n,?]
Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability Connectivity, Upgrade and Administration Setting Up the Remote Console3-57 2. Enter y. The program responds: 3. Enter the following to administer the remote console port: /cms/install/bin/abcadm -i -b 9600 ttyX (where X is “a” or “b”) The program responds: The remote console port has been administered. Redirecting the Remote Console Port to the Modem C Use the remote console port functions on a CMS computer by: •redirecting the console from the local console to the remote console •redirecting the console back to the local console 1. Dial in from the remote console to the remote console modem on the CMS computer and log in as root. 2. Remove the port monitor by entering: /cms/install/bin/abcadm -r ttyX (where X is “a” or “b”) The program responds: ttyX administration removed ttyX set to incoming port 9600 baud # ttyX is currently set to be incoming Are you sure you want to change it? [y,n,?]
Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability Connectivity, Upgrade and Administration Setting Up the Remote Console3-58 3. Enter y. The program responds: 4. Redirect the console to the remote console port by entering the following: /cms/install/bin/abcadm -c -b 9600 ttyX The program responds: 5. Enter y. The system will automatically reboot, and the remote console port will come up as the console. As the system reboots, shut down messages appear on the local console. When the system starts to come back up, the local console should go blank and the system boot diagnostics should appear on the remote console. When the system is restarted, a login prompt should appear on the remote console. 6. Log in to the remote console as root. If you enter Control-D from the remote console to exit the system without first redirecting control back to the local console, you may lock yourself from using the console locally or remotely. 7. Redirect the console back to the local console by entering: /cms/install/bin/abcadm -c local The program responds: ttyX administration removed This change requires a reboot to take affect Are you ready to reboot? [y,n,?] !CAUTION: Console set to local This change requires a reboot to take affect Are you ready to reboot? [y,n,?]
Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability Connectivity, Upgrade and Administration Setting Up the Alarm Originator3-59 8. Enter y. The system automatically reboots and the remote console port comes up as a regular dial-in port with the login: prompt displayed. As the system reboots, the shutting-down messages appears on the remote console. When the system starts to come back up, the system boot diagnostics should appear on the local console. After the system reboots, a login prompt should appear on the local console. 9. Log into the local console as root. The console has been redirected from the remote console to the local console. Setting Up the Alarm Originator3 For information on setting up the alarm origination manager on the HA servers, see “CentreVu CMS R3V8 Alarm Origination Manager (585-215- 884). Setting Up the NTSC For information about setting up the NTS, see “Setting up the NTS”, in Chapter 2 of “CentreVu Call Management System R3V8 Software Installation and Setup” (585-210-941). Configuring the NTS 3 This procedure is performed on NTS devices when: •the NTS is newly installed, or •the NTS requires reconfiguration during a manual HA server switch- over after the HA server to which the NTS was initially connected has experienced a failure event 1. Connect a dumb terminal to the Console Port on the rear of the NTS using the console cable and adapter that came with the NTS. On the 8- and 16-port NTSs, the Console Port is port #1. You will need the following for the 8- and 16-port units: •Console Cable •Adapter - comcode 407361823 •Null Modem - comcode 407122043.
Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability Connectivity, Upgrade and Administration Setting Up the NTS3-60 You will need the following for the 64-port unit: •Console Cable •Adapter - part number 06-988-260-20. The terminal options should be set to 9600 bps, 8 bits, no parity or space parity, and a stop bit. 2. Turn on the NTS, and within 15 seconds push the Test Switch on the front of the NTS (see the following figure). 3. The NTS goes through its hardware diagnostics, and the following prompt should appear: 4. Enter the erase command. There are two types of information that can be erased: •EEPROM (configuration information) •FLASH (self-boot image). If only one type of information is present, the program begins to erase it. If there are two types of information, the program prompts you to select the information you want to erase. Erase both the EEPROM and the FLASH information. NOTE: Monitor:: NOTE: