Enterprise License Manager User Guide, Release 9.1(1)
Enterprise License Manager installation and upgrade
Downloads: This chapterpdf (PDF - 1.32MB) The complete bookPDF (PDF - 2.34MB) | Feedback

Enterprise License Manager Installation and Upgrade

Enterprise License Manager Installation and Upgrade

Enterprise License Manager Installation

Enterprise License Manager is installed automatically as part of the installation of Unified CM, Unity Connection, or both, as well as Unified Communications Manager Business Edition 5000 and Unified Communications Manager Business Edition 6000. You may choose to run Enterprise License Manager on one of these servers in a co-resident configuration, or you may opt to run Enterprise License Manager in a standalone configuration.

For a standalone configuration, Enterprise License Manager must be installed separately. This installation follows the same installation framework as Unified CM and Unity Connection, as described below.

Important:

A standalone Enterprise License Manager supports the same OVA or MCS server types that are supported for Unified CM 9.X or Unity Connection.

Important:

In a virtual environment, Enterprise License Manager requires a static MAC address to function properly.

Install Standalone Enterprise License Manager

This section describes how to install Enterprise License Manager on a standalone server or virtual machine. You install the operating system and application by running one installation program. This document divides the procedure for using this installation program into the following major topics:

  • Start installation
  • Enter configuration information
  • Perform basic installation
  • Configure the first node

Navigate installation wizard

For instructions on how to navigate within the installation wizard, refer to the following table.

Table 1 Installation Wizard Navigation

To Do This

Press This

Move to the next field

Tab

Move to the previous field

Alt-Tab

Select an option

Space bar or Enter

Scroll up or down in a list

Up or down arrow

Go to the previous window

Space bar or Enter to select Back (when available)

Get help information on a window

Space bar or Enter to select Help (when available)

Start Installation

Procedure
    Step 1   Insert the installation DVD into the tray and restart the server, so it boots from the DVD. After the server completes the boot sequence, the DVD Found window displays.
    Step 2   To perform the media check, select Yes or, to skip the media check, select No.

    The media check checks the integrity of the DVD. If your DVD passed the media check previously, you might choose to skip the media check.

    Step 3   If you select Yes to perform the media check, the Media Check Result window displays. Perform these tasks:
    • If the Media Check Result displays Pass, select OK to continue the installation.
    • If the media fails the Media Check, either download another copy from Cisco.com or obtain another DVD directly from Cisco.
    Step 4   The system installer performs the following hardware checks to ensure that your system is correctly configured. If the installer makes any changes to your hardware configuration settings, you will get prompted to restart your system. Leave the DVD in the drive during the reboot:

    First, the installation process checks for the correct drivers, and you may see the following warning:

    No hard drives have been found. You probably need to manually choose device drivers for install to succeed. Would you like to select drivers now?
    Step 5   To continue the installation, select Yes.

    The installation next checks to see whether you have a supported hardware platform. If your server does not meet the exact hardware requirements, the installation process fails with a critical error. If you think this is not correct, capture the error and report it Cisco support.

    The installation process next verifies RAID configuration and BIOS settings.

    Note    If this step repeats, select Yes again.

    If the installation program must install a BIOS update, a notification appears telling you that the system must reboot. Press any key to continue with the installation.

    After the hardware checks complete, the Product Deployment selection window displays.

    Step 6   In the Product Deployment selection window, select Cisco Enterprise License Manager.
    Step 7   If software is currently installed on the server, the Overwrite Hard Drive window opens and displays the current software version on your hard drive and the version on the DVD. Select Yes to continue with the installation or No to cancel.

    Caution: If you select Yes on the Overwrite Hard Drive window, all existing data on your hard drive gets overwritten and destroyed.

    The Platform Installation wizard displays. You may begin the install configuration.

    Step 8   Select one of the following options:
    • To enter your configuration information manually and have the installation program install the configured software on the server, select Proceed and continue with this procedure.
    • To install the software before manually configuring it, select Skip and continue with the "Enter Configuration Information" procedure. In this case the installation program installs the software, then prompts you to configure it manually. You can select Skip if you want to pre-install the application on all your servers first and then enter the configuration information at a later time. This method might cause you to spend more time performing the installation than the other methods.
    • To cancel the installation, select Cancel.
    Step 9   In the Basic Install window, select Continue to install the software version on the DVD or configure the pre-installed software. Continue with the "Perform the Basic Installation" section.

    Enter Configuration Information

    Start here if you chose Skip in the Platform Installation Wizard window.

    Procedure
      Step 1   After the system restarts, the Preexisting Installation Configuration window displays.
      Step 2   To continue with the Platform Installation Wizard, select Proceed.
      Step 3   In the Basic Install window, select Continue. Continue with the "Perform the Basic Installation" section.

      Perform Basic Installation

      Procedure
        Step 1   When the Timezone Configuration displays, select the appropriate time zone for the server and then select OK.

        The Auto Negotiation Configuration window displays.

        Step 2   The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) by using automatic negotiation. You can change this setting after installation.
        • To enable automatic negotiation, select Yes and continue with Step 5.

        The MTU Configuration window displays.

        To use this option, your hub or Ethernet switch must support automatic negotiation.

        • To disable automatic negotiation, select No and continue with Step 3.

        The NIC Speed and Duplex Configuration window displays.

        Step 3   If you chose to disable automatic negotiation, manually select the appropriate NIC speed and duplex settings now and select OK to continue.

        The MTU Configuration window displays.

        Step 4   In the MTU Configuration window, you can change the MTU size from the operating system default. The maximum transmission unit (MTU) represents the largest packet, in bytes, that this host will transmit on the network. If you are unsure of the MTU setting for your network, use the default value, which is 1500 bytes.

        Caution: If you configure the MTU size incorrectly, your network performance can be affected.

        • To accept the default value (1500 bytes), select No.
        • To change the MTU size from the operating system default, select Yes, enter the new MTU size, and select OK.

        The DHCP Configuration window displays.

        Step 5   For network configuration, you can select to either set up a static network IP address for the node or to use Dynamic Host Configuration Protocol (DHCP). Static IP addresses are recommended. If you select the DHCP option, an IP address is dynamically assigned by the DHCP server.
        • If you have a DHCP server that is configured in your network and want to use DHCP, select Yes. The network restarts, and the Administrator Login Configuration window displays. Skip to Step 8.
        • If you want to configure a static IP address for the node, select No. The Static Network Configuration window displays.
        Step 6   If you chose not to use DHCP, enter your static network configuration values and select OK. See Installing Cisco Unified Communications Manager for Node Configuration Data.

        The DNS Client Configuration window displays.

        Step 7   To enable DNS, select Yes, enter your DNS client information, and select OK. See Installing Cisco Unified Communications Manager for information on the field descriptions of node configuration data.

        The network restarts by using the new configuration information, and the Administrator Login Configuration window displays.

        Step 8   Enter your Platform Administrator login and password. See Installing Cisco Unified Communications Manager for information on the field descriptions of node configuration data.

        The Platform Administrator login must start with an alphabetic character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. You will need the Platform Administrator login to log in to Cisco Unified Communications Operating System Administration, the command line interface, and the Disaster Recovery System.

        The Certificate Information window displays.

        Step 9   Enter your certificate signing request information and select OK.
        Step 10   The Network Time Protocol Client Configuration window displays.

        Cisco recommends that you use an external NTP server to ensure accurate system time on the first node. Ensure the external NTP server is stratum 9 or higher (meaning stratums 1-9). Subsequent nodes in the cluster will get their time from the first node.When you install Cisco Unity Connection on a virtual machine, you must specify an external NTP server.

        Step 11   Choose whether you want to configure an external NTP server or manually configure the system time.
        • To set up an external NTP server, select Yes and enter the IP address, NTP server name, or NTP server pool name for at least one NTP server. You can configure up to five NTP servers, and Cisco recommends that you use at least three. Select Proceed to continue with the installation.

        The system contacts an NTP server and automatically sets the time on the hardware clock.

        Note: If the Test button displays, you can select Test to check whether the NTP servers are accessible.

        • To manually configure the system time, select No and enter the appropriate date and time to set the hardware clock. Select OK to continue with the installation.

        The Security Configuration window displays.

        Step 12   Enter the Security password. See Installing Cisco Unified Communications Manager for information on the field descriptions of node configuration data.

        Note: The Security password must start with an alphanumeric character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. The system uses this password to authorize communications between nodes, and you must ensure this password is identical on all nodes in the cluster.

        Step 13   Select OK. The Application User Configuration window displays.
        Step 14   Enter the Application User name and password (see Installing Cisco Unified Communications Manager). Enter the password again to confirm.
        Step 15   Select OK. The Platform Configuration Confirmation window displays.
        Step 16   To continue with the installation, select OK; or to modify the platform configuration, select Back.

        The system installs and configures the software. The DVD drive ejects, and the server reboots. Do not reinsert the DVD.

        Step 17   When the installation process completes, you are prompted to log in by using the Administrator account and password.
        Step 18   Complete the post-installation tasks that are listed in the "Post-Installation Tasks" section.
        Step 19   Once complete, a message appears indicating that the Enterprise License Manager install has completed successfully.

        Upgrade Information

        Use the following information to upgrade software in a standalone configuration.

        Upgrade Software Through Platform GUI

        This section provides procedures for upgrading, via the platform GUI, using one of the following methods:

        • Upgrade from a local source
        • Upgrade from a remote source

        Note


        Do not use the browser controls, such as Refresh/Reload, while you are accessing Cisco Unified Operating System Administration. Instead, use the navigation controls that are provided by the interface.

        Upgrade From Local Source

        Procedure
          Step 1   If you do not have a Cisco-provided upgrade disk, create an upgrade disk by burning the upgrade file that you downloaded onto a DVD as an ISO image.
          Note   

          Just copying the .iso file to the DVD will not work. Most commercial disk burning applications can create ISO image disks.

          Step 2   Insert the new DVD into the disc drive on the local server that is to be upgraded.
          Step 3   From the Administration Settings > OS Admin page, log in to Cisco Unified Communications Operating System Administration.
          Step 4   Navigate to Software Upgrades > Install/Upgrade.

          The Software Installation/Upgrade window displays.

          Step 5   From the Source list, select DVD.
          Step 6   Enter a slash (/) in the Directory field.
          Step 7   To continue the upgrade process, click Next.
          Step 8   Choose the upgrade version that you want to install and click Next.
          Step 9   In the next window, monitor the progress of the download.
          Step 10   If you want to install the upgrade and automatically reboot to the upgraded partition, select Switch to new version after upgrad (system reboots). The system restarts and is running the upgraded software.
          Step 11   If you want to install the upgrade and then manually reboot to the upgraded partition at a later time, do the following steps:
          1. Select Do not switch to new version after upgrade (no system reboots).
          2. Click Next. The Upgrade Status window displays the Upgrade log.
          3. When the installation completes, click Finish.
          4. To restart the system and activate the upgrade, select Settings > Version; then, click Switch Version.

          The system restarts running the upgraded software.


          Upgrade From Remote Source

          To upgrade the software from a network location or remote server, use the following procedure.

          Procedure
            Step 1   Put the upgrade file on an FTP or SFTP server that the server that you are upgrading can access.
            Step 2   Log in to Cisco Unified Communications Operating System Administration.
            Step 3   Navigate to Software Upgrades > Install/Upgrade.

            The Software Installation/Upgrade window displays.

            Step 4   From the Source list, select Remote Filesystem.
            Step 5   In the Directory field, enter the path to the directory that contains the patch file on the remote system. If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path. For example, if the upgrade file is in the patches directory, you must enter /patches If the upgrade file is located on a Windows server, remember that you are connecting to an FTP or SFTP server, so use the appropriate syntax, including:
            • Begin the path with a forward slash (/) and use forward slashes throughout the path.
            • The path must start from the FTP or SFTP root directory on the server, so you cannot enter a Windows absolute path, which starts with a drive letter (for example, C:).
            Step 6   In the Server field, enter the server name or IP address.
            Step 7   In the User Name field, enter your user name on the remote server.
            Step 8   In the User Password field, enter your password on the remote server.
            Step 9   Select the transfer protocol from the Transfer Protocol field.
            Step 10   To continue the upgrade process, click Next.
            Step 11   Choose the upgrade version that you want to install and click Next.
            Step 12   In the next window, monitor the progress of the download.

            If you lose your connection with the server or close your browser during the upgrade process, you may see the following message when you try to access the Software Upgrades menu again:

            Warning: Another session is installing software, click Assume Control to take over the installation.

            If you are sure you want to take over the session, click Assume Control.

            If Assume Control does not display, you can also monitor the upgrade with the Real Time Monitoring Tool.

            Step 13   If you want to install the upgrade and automatically reboot to the upgraded partition, select Switch to new version after upgrad (system reboots). The system restarts and runs the upgraded software.
            Step 14   If you want to install the upgrade and then manually reboot to the upgraded partition at a later time, do the following steps:
            1. Select Do not switch to new version after upgrade (no system reboots).
            2. Click Next. The Upgrade Status window displays the Upgrade log.
            3. When the installation completes, click Finish.
            4. To restart the system and activate the upgrade, select Settings > Version; then, click Switch Version.

            The system restarts and is running the upgraded software.


            Upgrade Standalone Enterprise License Manager Using CLI

            To initiate an upgrade from a local or remote source using CLI commands, use the following procedures.

            Upgrade From Local Source

            Before You Begin

            If you do not have a Cisco-provided upgrade disk, create an upgrade disk by burning the upgrade file that you downloaded onto a DVD as an ISO image.

            Just copying the .iso file to the DVD will not work. Most commercial disk burning applications can create ISO image disks.

            Procedure
              Step 1   Insert the new DVD into the disc drive on the local server that is to be upgraded.
              Step 2   Enter the utils system upgrade initiate command, as shown in the following example.

              Example:
              admin:utils system upgrade initiate
              The following options appear:
              Warning: Do not close this window without first exiting the upgrade command. Source: 1) Remote Filesystem via SFTP 2) Remote Filesystem via FTP 3) Local DVD/CD q) quit Please select an option (1 - 3 or "q" ):
              Step 3   Select option 3. 1) CiscoPrimeLM_64bitLnx_10.0.0.98030-1.sgn.iso q) quit
              Step 4   Select option 1 to download upgrade file. Accessing the file. Please wait... Checksumming the file... Validating the file... A system reboot is required when the upgrade process completes or is canceled. This will ensure services affected by the upgrade process are functioning properly. Downloaded: CiscoPrimeLM_64bitLnx_10.0.0.98030-1.sgn.iso File version: 10.0.0.98030-1 File checksum: c4:13:ad:95:7b:c8:c1:01:1b:91:bb:da:8d:84:09:ea
              Step 5   Enter yes to automatically switch versions if the upgrade was successful.
              Automatically switch versions if the upgrade is successful (yes/no): yes
              Step 6   Enter yes to start installation.
              Start installation (yes/no): yes

              Upgrade From Remote Source

              Before You Begin

              You need to place the ISO on a network location or remote drive that is accessible from Cisco Prime License Manager prior to starting this procedure.

              Procedure
                Step 1   Enter the utils system upgrade initiate command, as shown in the following example.

                Example:utils system upgrade initiate The following options appear:
                • Warning: Do not close this window without first canceling the upgrade.
                • 1) Remote Filesystem via SFTP
                • 2) Remote Filesystem via FTP
                • 3) Local DVD/CD
                • q) quit
                • Please select an option (1 - 3 or "q" ):
                Step 2   Select option 1.
                Step 3   Enter Directory, Server, User Name, and Password information when prompted.
                • Please select an option (1 - 3 or "q" ): 1
                • Directory: /auto/ipcbu-builds2-published/ELM/10.0.0.98030-1
                • Server: se032c-94-61
                • User Name: bsmith
                • Password: ********
                • Checking for valid upgrades. Please wait...
                Step 4   Enter SMTP Host Server (optional) to receive email notification once upgrade is complete. The following options appear:
                • Available options and upgrades in "se032c-94-61:/auto/ipcbu-builds2-published/ELM/10.0.0.98030-1":
                • 1) CiscoPrimeLM_64bitLnx_10.0.0.98030-1.sgn.iso
                • q) quit
                Step 5   Select option 1 to download upgrade file. The following messages appear:
                • Accessing the file. Please wait...
                • Validating the file...
                • Downloaded 935 MB.
                • Checksumming the file...
                • A system reboot is required when the upgrade process completes or is canceled. This will ensure services affected by the upgrade process are functioning properly.
                • Downloaded: CiscoPrimeLM_64bitLnx_10.0.0.98030-1.sgn.iso
                • File version: 10.0.0.98030-1
                • File checksum: c4:13:ad:95:7b:c8:c1:01:1b:91:bb:da:8d:84:09:ea
                Step 6   Enter No when asked to automatically switch versions if the upgrade is successful. Automatically switch versions if the upgrade is successful (yes/no): no
                Step 7   Enter Yes to start installation. Start installation (yes/no): yes

                License Management CLI Commands

                Important: To use Enterprise License Manager CLI commands, you need a privilege level of 0 or higher.

                The following CLI commands are available for Enterprise License Manager:

                • license management list users
                • license management change user { name | password }

                For detailed information on these commands, and additional CLI information, see Command Line Interface Reference Guide for Cisco Unified Solutions.

                Post-Upgrade Tasks

                After the upgrade, perform the following tasks:

                • Check the version number in the About box to verify that it is the expected upgraded version.

                • Perform a synchronization by selecting Inventory > Product Instances > Synchronize Now.

                • Check the Dashboard to verify that there are no alerts.

                Install COP Files

                Use the following procedure to install Cisco Option files (COP) files. COP files are used to enable additional functionality (for example: localization).

                Procedure
                  Step 1   Obtain and store the COP file from Cisco.com by selecting Product/Technology Support > Download Software .
                  Step 2   Place the COP file on an FTP or SFTP server that the server that you are upgrading can access.
                  Step 3   Log in to Cisco Unified Communications Operating System Administration.
                  Step 4   Navigate to Software Upgrades > Install/Upgrade.

                  The Software Installation/Upgrade window displays.

                  Step 5   From the Source list, select Remote Filesystem.
                  Step 6   In the Directory field, enter the path to the directory that contains the patch file on the remote system. If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path. For example, if the upgrade file is in the patches directory, you must enter /patches If the upgrade file is located on a Windows server, remember that you are connecting to an FTP or SFTP server, so use the appropriate syntax, including:
                  1. Begin the path with a forward slash (/) and use forward slashes throughout the path.
                  2. The path must start from the FTP or SFTP root directory on the server, so you cannot enter a Windows
                  Step 7   In the Server field, enter the server name or IP address.
                  Step 8   In the User Name field, enter your user name on the remote server.
                  Step 9   In the User Password field, enter your password on the remote server.
                  Step 10   Select the transfer protocol from the Transfer Protocol field.
                  Step 11   Select the COP file that you want to install from Software Location, Options/Upgrades and click Next.
                  Step 12   In the next window, monitor the progress of the download.

                  If you lose your connection with the server or close your browser during the upgrade process, you may see the following message when you try to access the Software Upgrades menu again:

                  Warning: Another session is installing software; click Assume Control to take over the installation.

                  If you are sure you want to take over the session, click Assume Control.

                  Step 13   Once the download is complete, confirm the file checksum details and click Next.
                  Step 14   In the next window, monitor the progress of the installation.
                  Note    The installation of a COP file may require a system restart. This restart requirement will be stated in the output section of the log. Cisco recommends that you perform this restart during an off-peak period.