System Manager 6.3 OVA Installation

Workaround: Modify post-install script

This workaround involves interrupting the initial boot up of the System Manager virtual machine and then modifying the post-install script so that the date is set to the 20th February 2015 before the post installation begins to run.

The steps to accomplish this are below:

  1. Deploy the System Manager 6.3 GA OVA. For instructions on how to deploy the System Manager 6.3 OVA please refer to “Deploying Avaya Aura System Manager on VMWare in Virtualized Environment” document which is available on the support site.
    IMPORTANT: Before you power on the deployed System Manager VM for the first time read step 2.
  2. Connect to the console of the deployed System Manager VM and then start the VM. As soon as you start the VM you will see a message which says
    Booting Centos (2.6.18-308.16.1.el5) in “x” seconds…
    You must hit the space key or any key before the countdown reaches zero to enter the boot menu.

Note: You must be quick. If you cannot get into the boot menu then power off the System Manager VM and try again. What we want to achieve is to login into the System Manager VM in single user mode so that we can modify a file before the VM actually gets configured. If you proceed without modifying the file, the deployment will fail.

  1. Once you get into the boot menu you will see 2 options. Make sure the first option which says “Centos (2.6.18-308.16.1.el5)” is selected and press “e” to edit the entry.
  2. Once you press “e” it will display 3 options. Press “c” on your keyboard which will give you the “grub” prompt. Click on the escape (ESC) button on your keyboard (without doing anything) to come back to the previous screen which displayed you the 3 options.
    Select the 2nd option which starts with “kernel…” and press “e” to edit it.
  3. You will see “<00/LogVol00 rhgb quiet” – after the word “quiet”enter a space and type “single” so the line now looks like
    <00/LogVol00 rhgb quiet single
    then hit enter. DO NOT hit the escape button as that will not save the changes
  4. After you hit enter you will come back to the previous screen which had the 3 options. Make sure the line starting with “kernel…” is selected and hit the “b” button on your keyboard to boot the VM in single user mode
  5. The box will now boot up and stop with the message which reads “Give root password for maintenance (or type Control-D to continue)” – here enter the root password (root01) after which you will be logged in to the VM as root user.
  6. Edit the file /opt/vsp/post_install_sp.sh using the vi command-line editor and make sure the first 3 lines in the file are as shown below:
    #!/bin/bash
    vmware-toolbox-cmdtimesync disable
    date --set="20 Feb 2015"
    ###########################################################################
  7. Save the changes and then reboot the VM by entering ‘reboot’ and pressing enter. Then let the post installation of the VM continue in the normal way.

IMPORTANT:While filling in the System Manager Information for deploying the OVA DO NOT fill in the NTP server details. If you fill in the NTP server details it would fail the deployment.

  1. Once the System Manager installation is complete, log in to System Manger web console using the admin account to confirm successful installation.
    Note: You will be prompted to change the “admin” user password on the first log in to System Manager web console.
  2. Once you have confirmed that everything is working as expected login to System Manager command line interface as admin user and execute the following command:
    vmware-toolbox-cmdtimesync enable
  3. Then reboot the System Manager VM.
  4. To ensure that the system date is set back to the current date perform the following steps:
  5. Login to System Manager VM via SSH and run the “date” command to see if the current date is being displayed
  6. Configure the NTP server on System Manager. Instructions to configure an NTP server on System Manager can be found in “Deploying Avaya Aura System Manager on VMWare in Virtualized Environment” which is available on the support site.