Cisco Prime Central for Hosted Collaboration Solution 9.1.1 Installation Guide
Chapter 3: Preparing for Installation
Downloads: This chapterpdf (PDF - 221.0KB) The complete bookPDF (PDF - 2.43MB) | Feedback

Preparing for Installation

Table Of Contents

Preparing for Installation

Creating VMs Using OVA File

Using Appropriate vCenter Credentials

Setting up an NTP Server

Setting up Hostname and Domain Name

Downloading the required RPMs

Setting up Installer Code and Media

Integrating DMA-IM with Prime Central for HCS


Preparing for Installation


This section describes how to set up the environment for installation. This installation process requires Python 2.4 or later. By default, RHEL 5.5 ships with Python 2.4.

You need to complete the following steps to set up the right environment for the installation:

1. Creating VMs Using OVA File

2. Using Appropriate vCenter Credentials

3. Setting up an NTP Server

4. Setting up Hostname and Domain Name

5. Downloading the required RPMs

6. Setting up Installer Code and Media

7. Integrating DMA-IM with Prime Central for HCS

Creating VMs Using OVA File

HCS VMware image is packaged as an OVA (open virtualization archive) file. Run the OVA file (hcs-sa.ova) that is available in the installer media to create VMs. Before you begin creating the VM, ensure that you have a machine with the required configuration. These items typically consist of a virtual machine description file (.ovf), a manifest file (.mf), and virtual hard drive file (*.vmdk). A directory called ova  contains the ova files. This directory is located inside the root media directory in the same location as the scripts directory.

Follow the procedure given below to create VMs; use a vSphere client to install OVA. The procedure has to be run once for every virtual machine. We recommend that you maintain the same VM root password across all VMs.


Step 1 Launch VMware vSphere Client and choose File > Deploy OVF Template.

The Deploy OVF Template page appears.

Step 2 Choose Browse and locate the HCS OVA file. Click Next.

After the OVA file is selected, VMware ESX/ESXi reads the OVA file attributes. The OVF Template Details page appears.

Step 3 In the OVF Template Details page, click Next.

The Name and Location page appears.

Step 4 In the Name and Location page, provide the name of the VM and Inventory Location for the deployed template and click Next.

The Deployment Configuration page appears.

Step 5 In the Deployment Configuration page, from the Configuration drop-down list, choose the VM that you want to create, and click Next.

The Datastore page appears.

Step 6 In the Datastore page, select the datastore where you want to store the virtual machine files and click Next.

The Disk Format page appears.

Step 7 In the Disk Format page, choose the Thick provisioned format radio button. Click Next.

The Network Mapping page appears.

Step 8 In the Network mapping page, select the network that the deployed template will use and click Next.

The Ready to Complete page appears.

Step 9 In the Ready to Complete page, check all the given options and click Finish.

After the virtual machine has been built, it appears on the left-hand side of the window.

Step 10 Power the virtual machine on.

Step 11 Install RHEL 5.5. Accept the defaults when installing RHEL. When you begin the installation, a boot prompt appears at the bottom of the screen. At the linux boot prompt, type the following command and press Enter.

linux ks=hd:sdb1:hcs.ks


Note To create partitions that are SAN aligned, you must perform the steps explained in the section Performing SAN Alignment.



Using Appropriate vCenter Credentials

Prime Central for HCS 9.1.1 monitors vCenter after you add the vCenter credentials to HCM-Fulfillment. You must ensure that the vCenter user in HCM-Fulfillment is an administrator.

Setting up an NTP Server

Before you install Prime Central for HCS 9.1.1, you must provision an NTP server that all VMs will connect to. As part of the installation or upgrade procedure, the VMs will automatically set the correct time and date on the VMs.

Setting up Hostname and Domain Name

Ensure that the appropriate hostname and domain name are set correctly on the machine. The hostname needs to be resolvable to the correct IP address.


Note The length of the hostname must be between 2 and18 characters. The hostname must not contain the character _. It must start and end with alphabetic or a numerical character. Hostname must contain only lowercase characters.



Step 1 To set it up, edit the /etc/hosts file; set it up in the format IP-Address hostname.domain-name hostname.

For example, if

hostname is hostname123

domain name is cisco.com

IP address is 1.1.1.1.

Set up the details like so:

127.0.0.1   localhost.localdomain   localhost
::1     localhost6.localdomain6 localhost6
1.1.1.1 hostname123.cisco.com hostname123

Tip If installation on VMs fail to launch, and displays an error such as ?Hostname 'localhost' missing from '/etc/hosts' file.?., it is indicates a missing localhost entry in the /etc/hosts file. Verify if you have a localhost entry in the file. A correct/incorrect /etc/hosts file may resemble the following:

Correct Version:
# Do not remove the following line, or various programs that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
1.1.1.1 hcm-test.cisco.com hcm-test

Incorrect Version:
# Do not remove the following line, or various programs that require network functionality will fail.
127.0.0.1 hcm-linux-staging localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6


Step 2 Ensure the /etc/resolv.conf file is set up properly for the DNS server. For example, from the above example:

domain cisco.com
nameserver 1.1.1.1

Note The DNS server configured in resolv.conf file should be in reachable state.


Step 3 Ensure the hostname, fully qualified domain name (FQDN), and IP address are fully resolvable on the target VM.

The following example is used to verify if the hostname is "hostname123", domain name is "cisco.com", and IP address is "1.1.1.1".


Note nslookup will only work if DNS is set up.


[root@hostname123 ~]# hostname
hostname123
[root@hostname123 ~]# nslookup hostname123.cisco.com
Server:         1.1.1.1
Address:        1.1.1.1#53
 
Name:   hostname123.cisco.com
Address: 1.1.1.2
 
[root@hostname123 ~]# nslookup hostname123
Server:         1.1.1.1
Address:        1.1.1.1#53
 
Name:   hostname123.cisco.com
Address: 1.1.1.2
 
[root@hostname123 ~]# nslookup 1.1.1.2
Server:         1.1.1.1
Address:        1.1.1.1#53
 
130.10.16.172.in-addr.arpa      name = hostname123.cisco.com.
 
[root@hostname123 ~]#ping -c1 hostname123
PING hostname123.cisco.com (1.1.1.2) 56(84) bytes of data.
64 bytes from hostname123.cisco.com (1.1.1.2): icmp_seq=1 ttl=64 time=0.013 ms
 
--- hostname123.cisco.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.013/0.013/0.013/0.000 ms
 
[root@hostname123 ~]# ping -c1 hostname123.cisco.com
PING hostname123.cisco.com (1.1.1.2) 56(84) bytes of data.
64 bytes from hostname123.cisco.com (1.1.1.2): icmp_seq=1 ttl=64 time=0.011 ms
 
--- hostname123.cisco.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.011/0.011/0.011/0.000 ms
 
[root@hostname123 ~]# ping -c1 1.1.1.2
PING 1.1.1.2 (1.1.1.2) 56(84) bytes of data.
64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 time=0.011 ms
 
--- 1.1.1.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.011/0.011/0.011/0.000 ms
 
   

Step 4 Ensure the HOSTNAME argument is set properly in /etc/sysconfig/network file. Below is an example with "hostname123" as the hostname and "10.10.10.10" as the gateway:

NETWORKING=yes
NETWORKING_IPV6=no
HOSTNAME=hostname123
GATEWAY=10.10.10.10

Downloading the required RPMs

The install media, by default, ships with the required RPMs for the RHEL 5.5. However, if you prefer to use the yum command option, you must register with the RedHat site. The yum install command must be able to connect to the Red hat mirrors to install packages onto Linux. Registration ensures that you receive security updates, thus preventing any damage to OS. We recommend that you register your VMs with RedHat server; registration must be done in production environment to receive the latest security updates from RedHat.


Note When you register with Redhat, you have option of upgrading your software. Do not select `kernel' upgrade. This will upgrade the OS from version 5.5 to version 5.8.


If you used yum at any time during the set up of the VM, it must be used during the time of installation as well.

For instructions on registration, visit the RedHat site: http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/5.3/html/Reference_Guide/ch-register.html

If you are in a proxy environment, set up your proxy as specified at http://www.softpanorama.org/Commercial_linuxes/RHEL/Registration/
rhel5_registration.shtml

Setting up Installer Code and Media

Access the installers placed in the DVD; alternatively, you can also download the software from Cisco.com.


Note We recommend that you use the remote installation method. Alternatively, you could move the installers to the local server, and then begin the installation from the server; however, you may encounter issues if the user account used to the files to the target server is different from the user account used for installation.


To be able to access the installers and run them, you need a central server with at least 34 GB free disk space. This server should be able to contact all the virtual machines on which you are going to install the various installers. Create a directory in this server on which you want all the files placed.


Caution This directory must have execute permission for all users (for example, 755 permission) and must not be any specific user directory (such as, /root, /home, /users). The recommended directory location for the media is /opt.

Run the following command on the server:


Step 1 Log in as root user.

Step 2 Extract the media to the desired location; follow the instructions on the DVD.


Integrating DMA-IM with Prime Central for HCS

DMA-IM is a service that runs on the HCM-Fulfillment that allows for automated configuration of monitors in the HCS Solution. Infrastructure Monitoring (IM) serves as a monitor of domain managers. DMA-IM configures IM of the following monitors: CUOM, CUCDM, CCDM, and Vcenter.


Step 1 The following information is required for DMA-IM to provision a device in IM. Ensure that the following credentials are available:

For Infrastructure Monitoring

Credential with type—CLI type must be root OS user and password on IM [This allows DMA-IM to log into IM's CLI (ssh/shell access)]

Credential with type—ADMIN type must be sysadmin OS user and password on IM (sysadmin password is the --admin-password argument) (DB2 credentials that allows DMA-IM to issue TACMD CLI commands.)

Network address with space—"Service Provider"

Step 2 Add Prime Central to HCM-Fulfillment with the following information:

Credential with type—CLI type must be root OS user and password on PC

Network address for Prime Central for HCS must be specified.

Step 3 Add the CUOM, CUCDM, vCenter and other domain managers to HCM-Fulfillment. Ensure that the following information is available:

Device must have a hostname

SNMPv1 credentials

For vCenter, ensure that 'admin' and 'snmp' credentials are specified

For other domain managers, ensure that 'snmp', 'admin' and 'operator' credentials are specified

Network address with space—"Service Provider"

Step 4 Ensure that the following services have been activated on HCM-F

Cisco HCS Fulfillment Service

Cisco HCS DMA-CUOM Service

Cisco HCS DMA-IM Service