The amount of time required to activate customer options depends on the number of options, the number of ACDs, and other parameters.
Before you begin
Ensure that the mount point used for backups is accessible.
If you are upgrading a VMware system, download the CMS upgrade ISO file from the Avaya Support website.
Procedure
To begin the activation process, log in to the CMS server with root privileges.
Copy the CMS upgrade ISO file to the CMS server and run the following command to mount the ISO file:
cd /
mount <UpgradeISOPath> /mnt
Tip:
If the mount fails, you can run the following commands:
cd /
unmount /mnt
mount <UpgradeISOPath> /mnt
Run cd /mnt to switch to the mount location.
Run the ./cvue_activate command.
Run the tail -f /var/log/cvuelog command from the local console during the copy and activation process to view the upgrade log file.
Tip:
When you finish viewing the /var/log/cvuelog file, press Delete to break out of the command.
Review the messages displayed to verify if the process is successful.
If the copying is successful, CMS starts activating customer options. A message such as the following is displayed:
Starting running scripts from /adminsave/init.d directory
S00Sethostname Start Time -> <timestamp>
S00Sethostname End Time -> <timestamp>
. . .
. . .
If the copying is not successful, you are prompted to run the cvue_copy process again. For more information about performing this copying process, see Copying customer data.
Verify the messages displayed to ensure that serial printers are readministered.
After the upgrade, network printers must also be administered.
Enter the option for the type of backup device you are using.
Optional If the S21checkdevices check fails, ensure that the default backup path in the /cms/db/cms.install file is correct.
This problem can occur because the default backup path in the /cms/db/cms.install file is a tape drive or the path does not exist. If this problem occurs, do the following:
Make a note of the default backup device currently defined in the /cms/db/cms.install file and make a copy of the file.
Modify the original file so the default backup device path is the mount point being used for the extract device.
Save the file and exit the editor.
Run the ./cvue_activate script again.
Review the command output messages to ensure that the activation process is proceeding as expected.
If the new system was deployed as described in the chapter Deploying a new CMS server, you should not see prompts about setting up WebLM, EASG, or the encryption passphrase. However, if you are prompted to provide this information, messages such as the following are displayed. Set up these options now or later.
You are required to set the WebLM host name before proceeding.
. . .
. . .
EASG User Access
. . .
. . .
Would you like to enable Avaya EASG? (Recommended) [yes/no]:
. . .
. . .
Continue monitoring the messages displayed to ensure that CMS set is completed successfully.
The following is an example of the output displayed:
. . .
. . .
Customer CMS data successfully initialized <time stamp>
..............................................
Computing space requirements and dbspace availability.
Setup completed successfully.
S80cmssetup End Time -> <time stamp>
. . .
. . .
Note:
If you are looking at the /var/log/cvuelog file during CMS setup, ignore any messages about SQL database failure.
CMS setup takes a few minutes to complete.
Ensure that the activation process is completed successfully.
