H3C License Server. Installation Guide. Hangzhou H3C Technologies Co., Ltd. Document version: 5W

Transcription

1 H3C License Server Installation Guide Hangzhou H3C Technologies Co., Ltd. Document version: 5W

2 Copyright 2015, Hangzhou H3C Technologies Co., Ltd. and its licensors All rights reserved Trademarks No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Hangzhou H3C Technologies Co., Ltd. H3C,, H3CS, H3CIE, H3CNE, Aolynk,, H 3 Care,, IRF, NetPilot, Netflow, SecEngine, SecPath, SecCenter, SecBlade, Comware, ITCMM and HUASAN are trademarks of Hangzhou H3C Technologies Co., Ltd. Notice All other trademarks that may be mentioned in this manual are the property of their respective owners The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.

3 Preface This installation guide describes the procedures for installing, logging in to, and removing the H3C license server. This preface includes the following topics about the documentation: Audience. Conventions. About the H3C license server documentation set. Obtaining documentation. Technical support. Documentation feedback. Audience This documentation is intended for: Network planners. Field technical support and servicing engineers. Network administrators working with H3C license server. Conventions This section describes the conventions used in the documentation. Command conventions Convention Boldface Italic Description Bold text represents commands and keywords that you enter literally as shown. Italic text represents arguments that you replace with actual values. [ ] Square brackets enclose syntax choices (keywords or arguments) that are optional. { x y... } [ x y... ] { x y... } * [ x y... ] * &<1-n> Braces enclose a set of required syntax choices separated by vertical bars, from which you select one. Square brackets enclose a set of optional syntax choices separated by vertical bars, from which you select one or none. Asterisk marked braces enclose a set of required syntax choices separated by vertical bars, from which you select at least one. Asterisk marked square brackets enclose optional syntax choices separated by vertical bars, from which you select one choice, multiple choices, or none. The argument or keyword and argument combination before the ampersand (&) sign can be entered 1 to n times. # A line that starts with a pound (#) sign is comments.

4 GUI conventions Convention Boldface Description Window names, button names, field names, and menu items are in Boldface. For example, the New User window appears; click OK. > Multi-level menus are separated by angle brackets. For example, File > Create > Folder. Symbols Convention WARNING CAUTION IMPORTANT NOTE TIP Description An alert that calls attention to important information that if not understood or followed can result in personal injury. An alert that calls attention to important information that if not understood or followed can result in data loss, data corruption, or damage to hardware or software. An alert that calls attention to essential information. An alert that contains additional or supplementary information. An alert that provides helpful information. About the H3C license server documentation set The H3C license server documentation set includes the following categories of documents: Category Documents Purposes Installation guide Troubleshooting guide Log message H3C license server installation guide H3C license server troubleshooting guide H3C license server operation log messages reference H3C license server system log messages reference Provides a complete guide to H3C license server installation. Provides troubleshooting methods for problems with H3C license server. Explains the operation log messages. Explains the system log messages. Obtaining documentation Access the most up-to-date H3C product documentation on the World Wide Web at Click the following links to obtain different categories of product documentation: [Technical Documents] Provides hardware installation, software upgrading, and software feature configuration and maintenance documentation. [Products & Solutions] Provides information about products and technologies, as well as solutions. [Software Download] Provides the documentation released with the software version.

5 Technical support Documentation feedback You can your comments about product documentation to We appreciate your comments.

6 Contents Overview 1 Preparing for installation 2 Network requirements 2 Server or VM requirements 2 Hardware requirements 2 Software requirements 2 Client requirements 3 Pre-installation checklist 3 Installing the license server 4 Obtaining the license server installation package 4 Installing the license server 4 Verifying the installation 4 Opening related license server's ports in the firewall 5 Logging in to the license server 7 Removing the license server 8 Upgrading the license server 9 i

7 Overview H3C license server is license management software developed by H3C. It provides centralized management on licensing and provides licensing for services on the network. This simplifies licensing workflow and automates services licensing. The license server provides the following features: Allows you to apply for licenses based on the hardware of the server or virtual machine (VM) where the license server resides. Allows you to install and store the licenses on the license server. 1

8 Preparing for installation Network requirements Before you install a license server, plan your network. Make sure the server or VM where the license server resides is accessible in the network. Server or VM requirements Hardware requirements You can install a license server on a physical server or virtual machine (VM). H3C recommends that you install a license server on a physical server. Table 1 shows the minimum hardware requirements for a server or VM to host the license server. Table 1 Minimum hardware requirements Item CPU Memory size Available disk space NIC speed Minimum requirements X86-64 (Intel 64/AMD 64), quad cores 8 GB 64 GB for the partition where the root directory resides 1 to 10 Gbps Software requirements Table 2 shows the software requirements for a server or VM to host a license server. Table 2 Software requirements Item Requirements Operating system CentOS 7 64-bit If you want to install the operating system on a VM, H3C recommends that you use one of the following VM management software: H3C CAS cloud computing manager. ESXi or later. KVM or later. The CentOS system might have bugs such as Shellshock bugs. Note the officially released CentOS system updates. 2

9 Client requirements You do not need to install a client for logging in to the license server. You can log in to the license server through a Web browser. The license server supports the following Web browsers: Mozilla Firefox 34 and later. Internet Explorer 8 and later. If the host uses Java 7, install the Java SE Runtime Environment 7u25 patch. You can download the patch from IMPORTANT: Do not install the Java SE Runtime Environment 7u40 patch. Earlier Java 7 versions have an SSL connection bug. The Java SE Runtime Environment 7u25 patch rectifies this bug but the Java SE Runtime Environment 7u40 patch reintroduces this bug. Pre-installation checklist Table 3 Pre-installation checklist Item Network Physical server or VM Hardware Software Requirements You have planned the network. Make sure the server or VM where the license server resides is accessible in the network. Hardware, including CPU, memory, disk, NIC, meets the requirements. Operating system: CentOS 7 64-bit. Whether the physical server or VM has a license server installed. Host If the server or VM has a license server installed, remove the license server. For more information, see "Removing the license server." Make sure the Web browser version is as required and the host has the Java 7 patches installed as required. 3

10 Installing the license server Obtaining the license server installation package The license server installation package is provided in the DVD-ROM. Copy the installation package (.rpm file) to the license server installation directory on the server or VM. If you use FTP or TFTP to upload the installation package to the directory, use the binary mode to avoid damaging the installation package. Installing the license server 1. Access the directory where the license server installation package (.rpm file) resides and install the installation package. The license server installation package is named in the format of VCF_CONTROLLER_LICS-version.rpm, where version represents the version number of the license server installation package. The following example uses the /root directory. ~] rpm ivh VCF_CONTROLLER_LICS-E2172.rpm Preparing... ################################# [100%] 2. Enter the service port number at the prompt: Type the license service port ( , default:5555) : Make sure the service port number is not used. If you press Enter directly, the default port number 5555 is used. 3. Enter Y or N as needed when you are prompted whether to restore the configuration by using the backup file. Do you want to restore the configuration from /opt/licserver/backup/lics_backup. tar? (y/n, default:n) : Y Verifying the installation 1. Identify whether the license server is successfully installed at the CLI. If the command output displays correct version information for the license server, the installation succeeds. [root@localhost ~]# rpm -qa grep lics vcf-controller-lics el7.centos.x86_64 2. Identify whether the license server Core, Monitor, and Tomcat services are started. If the command output displays that these services are started, the license server service is started. [root@localhost ~] service licscore status Redirecting to /bin/systemctl status licscore.service licscore.service - LICS Core Loaded: loaded (/etc/systemd/system/licscore.service; disabled) Active: active (running) since Thu :53:40 CST; 2min 51s ago 4

11 ~]# service licsmonitor status Redirecting to /bin/systemctl status licsmonitor.service licsmonitor.service - LICS Monitor Loaded: loaded (/etc/systemd/system/licsmonitor.service; disabled) Active: active (running) since Thu :15:36 CST; 49s ago [root@localhost ~]# service tomcat status tomcat is running Opening related license server's ports in the firewall After the installation, for the license server to operate correctly, make sure related license server's ports are opened if the firewall is enabled. These ports are HTTP port 8090 for the Web login and the license service port. To open related license server's ports in the firewall: 1. Verify that the firewall is enabled. The output active (running) indicates that the firewall is enabled. [root@localhost ~]# service firewalld status Redirecting to /bin/systemctl status firewalld.service firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled) Active: active (running) since Thu :33:26 CST; 20s ago 2. Examine whether the license service port (this example uses 5555) and HTTP port 8090 are blocked by the firewall. The output no indicates that the port is blocked. [root@localhost ~]# firewall-cmd --query-port=5555/tcp no [root@localhost ~]# firewall-cmd --query-port=8090/tcp no 3. Open the license service port and HTTP port 8090 in the firewall by using either of the following methods: (Recommended.) Permanently open the ports. The configuration can survive a reboot. The output success indicates that the operation succeeds. [root@localhost ~]# firewall-cmd -permanent --add-port=5555/tcp success [root@localhost ~]# firewall-cmd -permanent --add-port=8090/tcp success Open the ports this time. The configuration cannot survive a reboot. The output success indicates that the operation succeeds. [root@localhost ~]# firewall-cmd --add-port=5555/tcp success [root@localhost ~]# firewall-cmd --add-port=8090/tcp success 5

12 4. Verify that the ports are successfully opened. The output yes indicates that the ports are opened. ~]# firewall-cmd --query-port=5555/tcp yes ~]# firewall-cmd --query-port=8090/tcp yes 6

13 Logging in to the license server 1. Enter the login address in the Web browser's address bar in the format, for example, Then press Enter. The lics_ip_address argument represents the IP address of the server or VM that hosts the license server is the default port number. 2. On the login page, enter the username and password and click Login. The default username is admin and password is admin. Figure 1 license server login page 3. To change the password, perform the following steps: a. Select System Management > Operators. Then click the Operation icon. b. On the Edit Operator page, enter the original password and the new password. Then confirm the new password and click OK. 7

14 Removing the license server When you remove the license server, you can choose to back up the configuration file or not. If you back up the configuration file, you are prompted whether to restore the configuration by using the backup configuration file when you reinstall the license server. The license file remains after you remove the license server. It is automatically uploaded when you reinstall the license server. To remove the license server: 1. Remove the license server installation package. ~] rpm -e vcf-controller-lics 2. Enter Y or N as needed when you are prompted whether to remove the installation package. Then press Enter. This example uses Y. Do you really want to uninstall LICS? (y/n, default:y) :Y 3. You are promoted whether to back up the configuration file. To back up the configuration file, enter Y. Not to back up the configuration file, enter N. To back up the configuration file: Do you want to backup the configuration to /opt/licserver/backup/lics_backup.tar? (y/n, default:n) : Y./db/./db/licm/./db/licm/system_configs.data To not back up the configuration file: Do you want to backup the configuration to /opt/licserver/backup/lics_backup.tar? (y/n, default:n) :N Uninstalling vcf-controller-lics... Stopping tomcat (via systemctl): [ OK ] 8

15 Upgrading the license server License server upgrade includes the following tasks: 1. Remove the old version of the license server (see "Removing the license server"). 2. Install the new version of the license server (see "Installing the license server"). You can use one of the following methods to upgrade the license server: Upgrade with configuration file backed up Back up the configuration file when you remove the old version. When you install the new version, choose to restore the configuration from the backup file. H3C recommends that you use this method. IMPORTANT: The license server will automatically reconnect to the clients after the upgrade. The license services obtained by the clients during the upgrade will not be disrupted. When you use this method, H3C recommends that you not disconnect the clients from the license server. The manual disconnection will cause the license server to reclaim all licenses from the clients, which causes license-based services cannot run correctly on the clients. Upgrade without backing up configuration file Remove the old license server without backing up the configuration file. When you install the new license server, choose to not restore the configuration from the backup file. 9