Revision History

Chapter 1. Preparation

Introduction

Installation and Migration Scenarios

System Requirements

External Media for Cisco Collaboration Applications

Requirements for Cisco Tested Reference Configuration Installation

Chapter 2. Installation and Configuration

Install Cisco UCS B-Series Tested Reference Configurations

Install Cisco UCS C-Series and E-Series Tested Reference Configurations

Install Cisco UCS C-Series or E-Series Server

Configure Cisco Integrated Management Controller

RAID Configuration

Configure RAID with Preboot CLI (UCS C-Series M2 or M3 Servers)

Configure RAID with GUI (UCS C-Series M3 Servers)

Configure RAID with GUI (UCS C-Series M4 Servers)

Configure RAID with GUI (UCS E-Series M2 Servers)

Configure BIOS

Install Cisco HyperFlex HX-Series Tested Reference Configurations

Install and Configure VMware ESXi

Download Virtual Machine Templates (OVA Templates)

ISO and VM Template Delivery

Use vSphere to Create the VM for Servers with Optical Drives

Use vSphere to Create the VM for Servers Without Optical Drives

Install Cisco Collaboration Applications on VMs

Chapter 3. Migration

Migration from Nonvirtual Servers to Virtual Servers

Chapter 4. Administration

Rack-Mount Server Daily Operations

Monitoring From Virtual Machine

Monitoring From Cisco Integrated Management Controller

Monitoring From vSphere Client and vCenter

Server Health Monitoring From ESXi

Disk Management for Cisco UCS Rack-Mount Servers

Automatic Update Statistics

New Identity

Run New Identity Process

New Identity Caveats

Deploy Cluster Nodes Using Templates

Related Documentation

Copyright Page

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.

The following information is for FCC compliance of Class B devices: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If the equipment causes interference to radio or television reception, which can be determined by turning the equipment off and on, users are encouraged to try to correct the interference by using one or more of the following measures:

- Reorient or relocate the receiving antenna.

- Increase the separation between the equipment and receiver.

- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

- Consult the dealer or an experienced radio/TV technician for help.

Modifications to this product not authorized by Cisco could void the FCC approval and negate your authority to operate the product

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED "AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)

Revision History

Date

Revision History

March 22, 2018

Fixed all the broekn links in the guide.

Chapter 1. Preparation

- Introduction

- Installation and Migration Scenarios

- System Requirements

- External Media for Cisco Collaboration Applications

- Requirements for Cisco Tested Reference Configuration Installation

Introduction

This book provides an overview of how to install and migrate to virtual servers for Cisco Collaboration applications using Tested Reference Configurations.

Note

For Cisco Business Edition 6000 and 7000 appliance servers, do not follow the procedures in this document as the appliance servers ship with factory-setup hardware and factory-preloaded software and you will overwrite the preloaded software. Instead, use the Cisco Business Edition 6000 or 7000 Installation Guide at Click Here or Click Here . Follow this document only if you must rebuild your appliance server from scratch, such as after hardware replacement or recovering from a catastrophic event.

Installation and Migration Scenarios

For ordering information and part numbers, see the Business Edition datasheets at Click Here or Click Here and the Tested Reference Configurations at Click Here .

UCS C-Series Tested Reference Configurations (TRCs)

TRC Capacity

Form Factor

TRC Name*

Appliance Based on this TRC**

Extra-Large TRC

2RU rack-mount server

UCS C260 M2 TRC#1 (End of Sale)

N/A

Large TRC

2RU rack-mount server

UCS C240 M4SX TRC#1

Cisco Business Edition 7000H (M4)

UCS C240 M3S TRC#1 (End of Sale)

N/A

Medium TRC

2RU rack-mount server

UCS C240 M4S2 TRC#1

Cisco Business Edition 7000M (M4)

UCS C240 M3S TRC#2 (End of Sale)

Cisco Business Edition 7000M (M3)

1RU rack-mount server

UCS C220 M3S TRC#1 (End of Sale)

N/A

2RU rack-mount server

UCS C210 M2 TRCs #1,2,3 (End of Sale)

N/A

UCS C210 M1 TRCs #1,2,3,4 (End of Sale)

N/A

Small Plus TRC

1RU rack-mount server

UCS C220 M4S TRC#2

Cisco Business Edition 6000H (M4)

UCS C220 M3S TRC#3 (End of Sale)

Cisco Business Edition 6000H (M3)

Small TRC

1RU rack-mount server

UCS C220 M4S TRC#1

Cisco Business Edition 6000M (M3)

UCS C220 M3S TRC#2 (End of Sale)

Cisco Business Edition 6000M (M2)

UCS C200 M2 TRC#1 (End of Sale)

Cisco Business Edition 6000M (M4)

* When purchased as a UC on UCS TRC, there is no factory-setup or factory-installation of the hardware or software. Follow instructions in this doc for first time setup or rebuilds.

** When purchased as a Cisco Business Edition solution, the hardware is factory-setup and the software is factory-installed. For first-time setup, DO NOT follow the instructions in this doc or you will overwrite the preload. Instead, follow the Cisco Business Edition Installation Guides at either Click Here or Click Here . Follow the instructions in this document only if you have to rebuild a BE6000 or BE7000 server from scratch.

UCS B-Series Tested Reference Configurations (TRCs)

TRC Capacity

Form Factor

TRC Name

Extra-Extra-Large Blade TRC

Full-width blade server

UCS B440 M2 TRC#1 (End of Sale)

Extra-Large Blade TRC

Half-width blade server

UCS B230 M2 TRC#1 (End of Sale)

Large Blade TRC

Half-width blade server

UCS B200 M4 TRC#1

UCS B200 M3 TRC#1 (End of Sale)

Medium Blade TRCs

Half-width blade server

UCS B200 M2/M1 TRCs (End of Sale)

UCS E-Series Tested Reference Configurations (TRCs)

TRC Capacity

Form Factor

TRC Name

Appliance Based on this TRC**

Extra-Small TRC

Single-wide blade server for Cisco Integrated Services (Cisco ISR)

UCS E160S M3 TRC#1

N/A

Extra-Small TRC

Double-wide blade server for Cisco Integrated Services (Cisco ISR)

UCS E160D M2 TRC#1

Blade server component of Cisco Business Edition 6000S (M2) appliance

Note:
Cisco Business Edition 6000S appliance is End of Sale.

* When purchased as a UC on UCS TRC, the hardware definition is only for the UCS E-Series blade server and not for the Cisco ISR router housing the server. There is also no factory-setup or factory-installation of the hardware or software. Follow instructions in this doc for first-time setup or rebuilds of the blade server. See Click Here for documentation on Cisco ISR routers.

** When purchased as a Cisco Business Edition solution, the Cisco ISR router and UCS E-Series blade server hardware are factory-setup and the software is factory-installed. For first-time setup, DO NOT follow the instructions in this doc or you will overwrite the preload. Instead, follow the Cisco Business Edition 6000 Installation Guides at Click Here . Follow the instructions in this document only if you have to rebuild a BE6000 or BE7000 server from scratch.

HyperFlex HX-Series Tested Reference Configuration (TRC)

TRC Capacity

Form Factor

TRC Name

Large HyperFlex TRC

2RU rack-mount HyperFlex node

HX240c M4SX TRC#1

System Requirements

- This document is for virtualized Cisco UCS servers configured as Tested Reference Configurations (TRCs) for the UC on UCS. For more information see Click Here .

- For newly purchased/installed Cisco Business Edition 6000 and 7000 appliance servers, do not follow the procedures in this document because your server ships with factory-setup hardware and preloaded software. If you follow the procedures in this document, you will overwrite the preloaded software and licensing. Instead, use the Cisco Business Edition 6000 or 7000 Installation Guide at Click Here or Click Here . Follow this document only if you must rebuild your server from scratch such as recovering from a catastrophic event.

- If you want to deploy Cisco Collaboration on a virtualized 3rd-party Specs-based server or Cisco UCS Specs-based server, see the application support information at Click Here , and the Specs-based support information at Click Here . Installation procedures will vary from this document and can be found at vmware.com, Click Here , or the 3rd-party server vendor's website.

- Additional detail on supported virtualization software vendors, products, versions and features can be found at Click Here .

To run Cisco UCS servers or HyperFlex nodes, your system must meet the requirements listed in the following table.

System Requirements

Parameter

Value

Supported Application Co-residency and Virtual-to-Physical Sizing

See the application links at Click Here .

See sizing information at Click Here and Click Here .

Supported Virtual Machine Configuration

Refer to the documentation at: Click Here

To ensure that the VMs are correctly configured, use the Cisco-provided OVA template to create VMs. Refer to Download Virtual Machine Templates (OVA Templates)

For more information about VM configurations, refer to the documentation at: Click Here .

Supported virtualization software vendors, products, versions and features

See Click Here .

Supported hardware

See Click Here and Click Here .

CPU and RAM over subscription

None

Storage capacity and IOPS requirements

See Click Here and the application links at Click Here

To operate Cisco UCS servers successfully, you should have the experience and skills to manage a host server running VMware ESXi.

External Media for Cisco Collaboration Applications

Cisco UCS servers use "soft media" such as ISO or FLP (virtual floppy) for procedures that require external media (such as installation and upgrade). Physical external devices such as USB drives are not supported.

Note

Backup and restore for Cisco Collaboration applications are not supported on soft media.

The virtual USB interface is not supported for Cisco Collaboration applications running on VMware. The following are examples of differences in external media support between non-virtualized Cisco Media Convergence servers and virtualized Cisco UCS servers:

- Install logs cannot be dumped to a USB key. These logs are dumped to a file through the serial port of the VM.

- The answer file that is generated by the Answer File Generator (platformConfig.xml) cannot be read from a USB key to perform an unattended installation. Instead, you must put the answer file into an FLP image to be mounted in the floppy drive.

- USB tape drive backup is not supported. Use SFTP instead.

- Music On Hold through a USB connection is not supported. Use multicast MOH instead.

Requirements for Cisco Tested Reference Configuration Installation

This section describes how to prepare to install a Cisco UCS Server in a standalone configuration (it is not in a datacenter).

Caution

If your server is ordered as a Cisco Business Edition 6000 or Cisco Business Edition 7000 appliance, the server ships with factory-setup hardware and factory-preloaded software. DO NOT follow the configuration procedures that are outlined in this document or you will overwrite the preloaded software. Follow this document only if you must rebuild your server from scratch. Unless you are rebuilding your server from scratch, such as recovering from a catastrophic situation, use the Installation Guides for Cisco Business Edition 6000 or 7000 at Click Here or Click Here .

Cisco suggests that you allocate the following resources before installation:

- Space in a rack to receive the Business Edition appliance, Cisco C-Series rack-mount server, HX-Series HyperFlex nodes (with their UCS 6200 Fabric Interconnect Switches), Cisco ISR housing UCS E-Series blade server, or UCS 5100 Blade Server Chassis housing UCS B-Series blade server (and its UCS 6300/6200/6100 Fabric Interconnect Switches).

- Ethernet ports on a switch close to the Cisco UCS Server or HyperFlex node. For port details specific to your hardware, see the table that follows.

- An IP address for Cisco IMC or UCS Manager management. If the dedicated port is used, attach it to the appropriate LAN.

- A VLAN ID and IP address for the host. This address is the Cisco UCS Server ESXi management address.

- A hostname and configured DNS, if desired, for the hostname.

- VLAN IDs and IP addresses for the VMs.

Ethernet Port Allocations for Tested Reference Configurations (TRCs)

Cisco UCS Server

Ethernet Port Allocation

HX240c M4SX TRC1 (Large HyperFlex TRC)

For each node:

- One motherboard CIMC management port (not used)

- Two motherboard LOM ports

- Two 10-Gigabit ports (Cisco VIC)

Minimum system requires four nodes and two 6200 Fabric Interconnect switches.

UCS C240 M4SX TRC1 (Large TRC / BE7000H M4)

Eleven ethernet ports:

- One port for dedicated CIMC management

- Eight ports for quad-port Intel NICs

- Two ports for the LOM, if required.

UCS C240 M4S2 TRC1 (Medium TRC / BE7000M M4)

Eleven ethernet ports:

- One port for dedicated CIMC management

- Eight ports for quad-port Intel NICs

- Two ports for the LOM, if required.

UCS C220 M4S TRCs (Small TRC / BE6000M M4 and Small Plus TRC / BE6000H M4)

For Small TRC:

Three ethernet ports:

- One port for dedicated CIMC management

- Two ports for the LOM, if required.

For Small Plus or Medium TRC:

Seven ethernet ports:

- One port for dedicated CIMC management

- Four ports for quad-port Intel NICs

- Two ports for the LOM, if required.

UCS E160D M2 TRC1 (Extra-Small TRC / BE6000S M2)

3 "external" (front of E160D M2) ethernet ports:

- One "M" port for dedicated CIMC management (CIMC is also accessible via the "internal" ports described below)

- Two ports for LAN access

- The two "internal" ports of the UCS E-Series server are to ISR backplane for connectivity to other ISR interfaces.

UCS E160S M3 TRC1(Extra-Small TRC)

3 "external" (front of E160D M2) ethernet ports:

- One "M" port for dedicated CIMC management (CIMC is also accessible via the "internal" ports described below)

- Two ports for LAN access

- The two "internal" ports of the UCS E-Series server are to ISR backplane for connectivity to other ISR interfaces.

(End of Sale) UCS C260 M2 TRC1 (Extra-Large TRCs)

Ten ethernet ports:

- One port for dedicated Cisco Integrated Management Controller (CIMC) management

- Four ports for quad-port Intel NICs

- Two ports for the LAN on Motherboard (LOM)

- Two 10-Gigabit Modular LOM

(End of Sale) UCS C240 M3S TRC1 (Large TRC)

Eleven ethernet ports:

- One port for dedicated CIMC management

- Eight ports for quad-port Intel NICs

- Two ports for the LOM, if required.

(End of Sale) UCS C240 M3S TRC2 (Medium TRC / BE7000M M3)

Eleven ethernet ports:

- One port for dedicated CIMC management

- Eight ports for quad-port Intel NICs

- Two ports for the LOM, if required.

(End of Sale) UCS C210 M2/M1 TRCs (Medium TRCs)

Seven ethernet ports:

- One port for dedicated CIMC management

- Four ports for quad-port Intel NICs

- Two ports for the LOM

(End of Sale) UCS C220 M3S TRCs (Small TRC / BE6000M M3, Small Plus TRC / BE6000H M3 and Medium TRC)

For Small TRC:

Three ethernet ports:

- One port for dedicated CIMC management

- Two ports for the LOM, if required.

For Small Plus or Medium TRC:

Seven ethernet ports:

- One port for dedicated CIMC management

- Four ports for quad-port Intel NICs

- Two ports for the LOM, if required.

(End of Sale) UCS C200 M2 TRC1 (Small TRC / BE6000M M2)

Three ethernet ports:

- One port for dedicated CIMC management

- Two ports for the LOM

Chapter 2. Installation and Configuration

Caution

The Extra-Small TRC (UCS E160D M2 TRC1), Small TRCs (UCS C220 M3S TRC2, UCS C240 M4S TRC1) and the Small Plus TRCs (UCS C220 M3S TRC3, UCS C220 M4S TRC2) are preloaded with software if purchased as a Cisco Business Edition 6000 appliance.

Certain Medium TRCs (UCS C240 M3S TRC2, UCS C240 M4S2 TRC1) and Large TRCs (UCS C240 M4SX TRC1) are preloaded with software if purchased as a Cisco Business Edition 7000 appliance.

HyperFlex TRC (HX240cM4SX TRC1) is preloaded with virtualization and HyperFlex software.

- Install Cisco UCS B-Series Tested Reference Configurations

- Install Cisco UCS C-Series and E-Series Tested Reference Configurations

- Install Cisco HyperFlex HX-Series Tested Reference Configurations

- Install and Configure VMware ESXi

- Download Virtual Machine Templates (OVA Templates)

- Use vSphere to Create the VM for Servers with Optical Drives

- Use vSphere to Create the VM for Servers Without Optical Drives

- Install Cisco Collaboration Applications on VMs

Install Cisco UCS B-Series Tested Reference Configurations

Procedure

Step 1

Ensure that your UCS Mini or Fabric Interconnect Switches, Blade Server Chassis, and Fabric Extenders are installed in the rack.

Step 2

Ensure that the network connections of your UCS Mini or Fabric Interconnect Switches are connected to their designated, trunked, switch ports.

Step 3

Ensure that your Fabric Interconnect Switches are properly connected to your Fabric Extenders.

Step 4

Ensure that you are able to access the blade remotely using UCS Manager software.

Step 5

For the remaining server installation, see Cisco documentation at Click Here .

Install Cisco UCS C-Series and E-Series Tested Reference Configurations

Perform the following tasks to install and configure a virtual machine on a Cisco UCS server.

Before You Begin

Review the “Preparation” chapter in this guide for the installation requirements for your server.

Procedure

Command or Action

Purpose

Step 1

Install Cisco UCS C-Series or E-Series Server

Install the Cisco UCS Server.

Step 2

Configure Cisco Integrated Management Controller

Power on the server and configure Cisco Integrated Management Controller (CIMC) for remote management.

Step 3

Configure RAID using one of the following procedures:

- Configure RAID with Preboot CLI (UCS C-Series M2 or M3 Servers)

- Configure RAID with GUI (UCS C-Series M3 Servers)

- Configure RAID with GUI (UCS C-Series M4 Servers)

- Configure RAID with GUI (UCS E-Series M2 Servers)

- Configure RAID with GUI (UCS C-Series M3 Servers)

Configure the RAID settings on your server using either the Preboot CLI or GUI indicated above.

Step 4

Configure BIOS

Configure the BIOS boot order.

Step 5

Install and Configure VMware ESXi

Install and configure the VMware ESXi and the vSphere client.

Step 6

Download Virtual Machine Templates (OVA Templates)

Download an OVA for collaboration application software, such as Cisco Unified Communications Manager, onto your virtual machine.

Step 7

Use vSphere to create the VM on the server:

- Use vSphere to Create the VM for Servers with Optical Drives

- Use vSphere to Create the VM for Servers Without Optical Drives

Use vSphere to create the VM on the server. Map the OVA to the VM.

Step 8

Install Cisco Collaboration Applications on VMs

Install Collaboration applications such as Cisco Unified Communications Manager on the virtual machine.

- Install Cisco UCS C-Series or E-Series Server

- Configure Cisco Integrated Management Controller

- RAID Configuration

- Configure BIOS

Install Cisco UCS C-Series or E-Series Server

Procedure

Step 1

If UCS C-Series, install the server in the rack. If UCS E-Series, install the Cisco ISR in the rack and installe the UCS E-Series blade server into the ISR

Step 2

Attach the Cisco Integrated Management Controller (Cisco IMC) of the Cisco UCS C-Series or E-Series management port to the designated switch port.

Step 3

Attach the UCS C-Series LAN on Motherboard (LOM) or NIC ports (or the UCS E-Series external ethernet ports if used instead of internal ethernet ports) to their designated, trunked switch ports

Step 4

Attach a VGA console, or a KVM to the VGA and keyboard ports. This step is necessary until Cisco IMC is configured.

Step 5

Attach UCS C server or Cisco ISR for UCS E server to power supply

What to Do Next

Configure Cisco Integrated Management Controller

Configure Cisco Integrated Management Controller

Configuring the Cisco IMC allows you to perform all subsequent configuration and installation using the Cisco IMC console. In addition, the Cisco IMC provides a measure of hardware monitoring.

Note

Virtualized Collaboration Applications does not prescribe any specific version of BIOS. The current version is assumed to be compatible with the latest release of ESXi. Business Edition appliances ship with BIOS version, configuration and settings that are compatible with the factory-preloaded release of ESXi at time of appliance build. Non-appliance servers, or appliances that have been in the field for extended period of time, may require modification of these settings. See the UCS Release, CIMC version or firmware package in UCS Interoperability Matrix as well as UCS OS drivers for ESXi.

Before You Begin

Install Cisco UCS C-Series or E-Series Server

Procedure

Step 1

Power on server.

Step 2

During boot, press indicated function key (e.g. F8 for a UCS C-Series) to enter Cisco IMC configuration.

Step 3

In the Cisco IMC configuration screen, under IPV4 (Basic):

1. Uncheck the DHCP enabled check box using the spacebar.

2. Enter values for the Cisco IMC IP, Subnet mask, and Gateway.

Step 4

Leave VLAN (Advanced) unchecked.

Step 5

Under Default User (Basic), enter the default Cisco IMC user, admin, and a password.

Note:   The Cisco IMC username is not configurable and the setting is "admin."

Step 6

Press indicated function key (e.g. F10 for a UCS C-Series) to save your settings.

Step 7

After it is configured, the Cisco IMC is accessible using http. Point a browser to the IP address configured above and log in as admin, using the password configured above.

What to Do Next

Review the table in RAID Configuration

Configure RAID using one of the following methods:

- Configure RAID with Preboot CLI (UCS C-Series M2 or M3 Servers)

- Configure RAID with GUI (UCS C-Series M3 Servers)

- Configure RAID with GUI (UCS C-Series M4 Servers)

- Configure RAID with GUI (UCS E-Series M2 Servers)

RAID Configuration

Caution

To be supported as a Tested Reference Configuration instead of UCS Specs-based, the RAID must be set up exactly as indicated below. Do not change the RAID configuration on a server ordered as Cisco Business Edition 6000 or Cisco Business Edition 7000.

Refer to the following table for the RAID specifications for the type of virtual machine that you want to configure.

TRC

Information

UCS C220 M4S TRC1 (Small TRC / BE6000M M4)

- One virtual drive with a RAID-5 array

- Six 300-GB hard drives

UCS C220 M4S TRC2 (Small Plus TRC / BE6000H M4)

- One virtual drive with RAID-5

- Eight 300-GB hard drives

UCS C240 M4S2 TRC1 (Medium TRC / BE7000M M4)

- Two virtual drives (VDs) with RAID-5

- Each VD has six 300-GB hard drives

UCS C240 M4SX TRC1 (Large TRC / BE7000H M4)

- Four virtual drives (VD) with RAID-5

- Each VD has five 300-GB hard drives.

(End of Sale) UCS C240 M3S TRC1 (Large TRC)

- Two virtual drives (VD) with RAID-5 arrays

- Eight 300 GB hard drives for each VD

(End of Sale) UCS C240 M3S TRC2 (Medium TRC / BE7000M M3)

- Two virtual drives (VD) with RAID-5 arrays

- Six 300-GB hard drives for each VD

(End of Sale) UCS C220 M3S (Medium TRC)

- One virtual drive with a RAID-5 array

- Eight 300-GB hard drives

(End of Sale) UCS C220 M3S TRC3 (Small Plus TRC / BE6000H M3)

- One virtual drive with a RAID-5 array

- Eight 300-GB hard drives

(End of Sale) UCS C220 M3S TRC2 (Small TRC / BE6000M M3)

- One virtual drive with a RAID-10 array

- Four 500-GB hard drives

UCS E160S M3 TRC1 (Extra-Small TRC)

- One virtual drive with a RAID-1 array- Two 900-GB hard drives

(End of Sale) UCS E160D M2 TRC1 (Extra-Small TRC / BE6000S M2)

- One virtual drive with a RAID-5 array

- Three 600-GB hard drives

(End of Sale) UCS C260 M2 TRC1 (Extra-Large TRC)

- Two virtual drives (VD) with RAID-5 arrays

- Eight 300 GB hard drives for each VD

(End of Sale) UCS C210 M2/M1 TRCs (Medium TRC)

- First 2 drives are RAID-1 (mirrored) drives with the ESXi installation.

- Remaining drives are RAID-5 with UC application VMs.

(End of Sale) UCS C200 M2 TRC1 (Small TRC / BE6000M M2)

- One virtual drive with a RAID-10 array

- Four 1 TB hard drives

Important:
If required, use the following settings for the Read and Write policies:

If UCS C-Series, do these settings:

- Set Read Policy to read ahead = always.

- Set Write Policy to one of the following:

- write back with bbu – if you are using a RAID card with SuperCap (for example, RAID-9266CV).

Note

This write policy is not available on the C240 M3 rack-mount server TRC2.

- always write back – if you are using a RAID card with legacy Battery Backup (BBU) instead of SuperCap (for example, RAID-9266). This option helps prevent a UC application performance impact if the BBU goes into learning mode or the battery dies. Whenever possible, use the new RAID cards with SuperCap and make sure the UCS is attached to an Uninterruptible Power Supply (UPS).

If UCS E-Series M3, do these settings:

- Strip Size = 64KB

- Drives per Span = 2 (due to E160S M3 TRC1 shipping with two physical disks)

- Span Depth = 1 (due to E160S M3 TRC1 using single LV, 2-disk RAID1)

- Access Policy = Read-Write

- Cache Policy = Direct

- Read Ahead Policy = None

- Requested Write Cache Policy = Write Through

- Current Write Cache Policy = Write Through

- Disk Cache Policy = Unchanged

- Allow Background Init = true

- Auto Snapshot = false

- Auto Delete Oldest = true

- Configure RAID with Preboot CLI (UCS C-Series M2 or M3 Servers)

- Configure RAID with GUI (UCS C-Series M3 Servers)

- Configure RAID with GUI (UCS C-Series M4 Servers)

- Configure RAID with GUI (UCS E-Series M2 Servers)

Configure RAID with Preboot CLI (UCS C-Series M2 or M3 Servers)

Follow this procedure to configure a RAID array using the preboot CLI for M2 or M3 servers.

Before You Begin

Configure Cisco Integrated Management Controller

Procedure

Step 1

Check your current RAID configuration:

- To use the Preboot CLI to configure RAID, enter Ctrl-Y.

- Type the following commands:

1. TRC

Command

End of Sale UCS C260 M2 TRC1 (Extra-Large TRC)

- -ldinfo -l0 -a0

- -ldinfo -l1 -a0

End of Sale UCS C240 M3S TRC1 (Large TRC)

- -ldinfo -l0 -a0

- -ldinfo -l1 -a0

End of Sale UCS C240 M3S TRC2 (Medium TRC / BE7000M M3)

End of Sale UCS C220 M3S TRC1 (Medium TRC)

-ldinfo -l0 -a0

End of Sale UCS C220 M3S TRC3 (Small Plus TRC / BE6000H M3)

End of Sale UCS C220 M3S TRC2 (Small TRC / BE6000M M3)

End of Sale UCS C210 M2/M1 TRCs (Medium TRC)

End of Sale UCS C200 M2 TRC1 (Small TRC / BE6000M M2)

This command displays the number of drives, RAID level, and so forth for the specified logical drive.

Step 2

Use the following sequence of commands to set the recommended RAID configuration:

1. Enter CTRL-Y to enter the Preboot CLI when prompted during boot

2. Enter the following Preboot CLI command to clear configuration:

TRC

Command

End of Sale UCS C260 M2 TRC1 (Extra-Large TRC)

-cfgclr -l0

End of Sale UCS C240 M3S TRC1 (Large TRC)

-cfgclr -a0

End of Sale UCS C240 M3S TRC2 (Medium TRC / BE7000M M3)

End of Sale UCS C220 M3S TRC1 (Medium TRC)

End of Sale UCS C220 M3S TRC3 (Small Plus TRC / BE6000H M3)

End of Sale UCS C220 M3S TRC2 (Small TRC / BE6000M M3)

End of Sale UCS C210 M2/M1 TRCs (Medium TRC)

End of Sale UCS C200 M2 TRC1 (Small TRC / BE6000M M2)

Step 3

To determine the enclosure ID and drive numbering, which is required before you can configure RAID, run the following commands:

TRC

Command

End of Sale UCS C260 M2 TRC1 (Extra-Large TRC)

-encinfo -l0 -page 20

End of Sale UCS C240 M3S TRC1 (Large TRC)

-encinfo -a0 -page 20

End of Sale UCS C240 M3S TRC2 (Medium TRC / BE7000M M3)

End of Sale UCS C220 M3S TRC1 (Medium TRC)

End of Sale UCS C220 M3S TRC3 (Small Plus TRC / BE6000H M3)

End of Sale UCS C220 M3S TRC2 (Small TRC / BE6000M M3)

End of Sale UCS C210 M2/M1 TRCs (Medium TRC)

End of Sale UCS C200 M2 TRC1 (Small TRC / BE6000M M2)

Note:   This command can generate more than one page of output, so enter -page 20 to look at 20 lines at a time. Look for the Device ID of the enclosure that has a nonzero Number of Physical Drives. Use this Device ID (also called Enclosure ID) in the following commands.

Step 4

The Cisco UCS Rack-Mount Server enclosure ID is not predictable, so you need to substitute the Device ID acquired above for <encl> in the commands below. When all drives are in a single enclosure, the slot numbering starts at zero. This may not be true in all cases, so verify the slot numbering with the following command:
-pdinfo -physdrv [<encl>:0] -a0

If this command generates meaningful output, the drives start at zero. If it generates an error, the drives start at one.

Step 5

Use the following command to set up RAID on the existing drives on each RAID controller:

TRC

Command

End of Sale UCS C260 M2 TRC1 (Extra-Large TRC)

-cfgldadd -r5 [<encl>:1 <encl>:2, <encl>:3, <encl>:4, <encl>:5, <encl>:6, <encl>:7, <encl>:8 -a0

-cfgldadd -r5 [<encl>:9 <encl>:10, <encl>:11, <encl>:12, <encl>:13, <encl>:14, <encl>:15, <encl>:16 -a0

End of Sale UCS C240 M3S TRC1 (Large TRC)

-cfgldadd -r5 [<encl>:0, <encl>:1, <encl>:2, <encl>:3, <encl>:4, <encl>:5, <encl>:6, <encl>:7] -a0

–cfgldadd –r5 [<encl>:9, <encl>:10, <encl>:11, <encl>:12, <encl>:13, <encl>:14, <encl>:15, <encl>:16] –a0

End of Sale UCS C240 M3S TRC2 (Medium TRC / BE7000M M3)

End of Sale UCS C220 M3S TRC1 (Medium TRC)

-cfgldadd -r5 [<encl>:0, <encl>:1, <encl>:2, <encl>:3, <encl>:4, <encl>:5, <encl>:6, <encl>:7] -a0

End of Sale UCS C220 M3S TRC3 (Small Plus TRC / BE6000H M3)

End of Sale UCS C220 M3S TRC2 (Small TRC / BE6000M M3)

End of Sale UCS C210 M2/M1 TRCs (Medium TRC)

- If your drives start at slot zero, run this command:

-cfgldadd -r1 [deviceID:0, deviceID:1] -a0

- If your drives start at slot one, run this command:

-cfgldadd -r1 [deviceID:1, deviceID:2] -a0

- If your server contains 6 total disk drives, enter the following command to configure the second RAID array:

-cfgldadd -r5 [deviceID:2, deviceID:3, deviceID:4, deviceID:5] -a0

- If your server contains 10 total disk drives, configure the second RAID array by entering one of the following commands, depending on the starting slot number:

- If your drives start at slot zero, run this command:

-cfgldadd -r5 [deviceID:2, deviceID:3, deviceID:4, deviceID:5, deviceID:6, deviceID:7, deviceID:8, deviceID:9] -a0

- If your drives start at slot one, run this command:

-cfgldadd -r5 [ deviceID:3, deviceID:4, deviceID:5, deviceID:6, deviceID:7, deviceID:8, deviceID:9, deviceID:10] -a0

End of Sale UCS C200 M2 TRC1 (Small TRC / BE6000M M2)

-CfgSpanAdd -r10 -Array0[enclosureID:0,enclosureID:1] -Array1[enclosureID:2,enclosureID:3] -a0

Note:   To clear data on previously used drives and initialize a new array, use the -ldinit -start -full -l0 command. Allow command to finish before exiting the Preboot CLI.

Step 6

Set the Strip Size to 128 KB with the following command-line option on -cfgldadd command lines in step 5 above : -strpsz 128. Also set required Read Policy and Write Policy described above via appropriate command line options. E.g. -cfgldadd -r5 [26:1, 26:2, 26:3, 26:4, 26:5, 26:6, 26:7, 26:8] WB RA Cached NoCachedBadBBU -strpsz 128 -a0.

Step 7

The following commands are not necessary for new drives that have not been used.

- Use the -ldinit -start -l0 -a0 and –ldinit –start –l1 –a0 commands to perform a fast initialize.

- To clear data on previously used drives and to slow (or full) initialize a new array, use the -ldinit -start -full -l0 -a0 and -ldinit -start -full -l1 -a0 commands. Allow the commands to finish before exiting the Preboot CLI. When both commands, –ldinit –showprog –l0 –a0 and –ldinit –showprog –l1 –a0, show that initialization is not running, it is safe to exit the Preboot CLI.
Note:
We have noticed that a slow initialize can take up to 95 minutes or more to fully complete for array sizes of 1 TB+ that are used in a UCS C240 M3 Rack-Mount Server TRC1 deployment.

Step 8

After you configure the logical volume, exit the Preboot CLI by entering q.

Note:   The LSI adapter has factory default values for the drive rebuild rate, patrol read rate, and other settings. Cisco recommends leaving the default values unchanged.

What to Do Next

Configure BIOS

Configure RAID with GUI (UCS C-Series M3 Servers)

Use this procedure to configure a RAID array for a virtual drive on M3 servers. For servers with more than one virtual drive, perform these steps for each virtual drive.

Before You Begin

Configure Cisco Integrated Management Controller

Procedure

Step 1

During the boot process, ensure that Quiet Boot is disabled, and press Ctrl-H at the LSI screen when prompted. The MegaRaid BIOS Configuration utility opens and displays the LSI MegaRAID SAS adapters. Select Adapter 0 to begin and click Start.

Step 2

Select New Configuration and click Next.

Step 3

Select Manual Configuration.

Step 4

On the next screen, you need to add drives to a Drive Group. Select one drive and then select all others by holding down Shift and the Down Arrow key. Click Add to Array.

Step 5

Click Accept DG.

Step 6

Add the drive group to a span. Select DG0 and click Add to Span.

Step 7

After the drive group is part of a span, you can configure RAID on it.

1. Select RAID 5 or RAID 10 from the list of available options.

2. Cisco recommends that you select 128KB from the Strip Size drop-down list.

Step 8

Set Read Policy to read ahead = always.

Step 9

Set Write Policy to one of the following:

- - write back with bbu–if you are using a RAID card with SuperCap (RAID-9266CV), for example.

- - always write back–if you are using a RAID card with legacy Battery Backup (BBU) instead of SuperCap (for example, RAID-9266). This option helps prevent a UC application performance impact if the BBU goes into learning mode or the battery dies.

Note:
When possible, use the new RAID cards with SuperCap and make sure the UCS is attached to an Uninterruptible Power Supply (UPS).

Step 10

Click Update Size to finalize the RAID 5 volume and to determine the size of the resulting volume. A warning relating to BBU appears. Click Yes to accept a possible performance degradation if the BBU is over-tasked.

Step 11

Click Next on the next screen to accept the Virtual Drive you just created (VD 0).

Step 12

Click Next. At the next screen, you are presented with the option to initialize the array. Click:

1. Fast Initialize

2. Go

3. Set Boot Drive

4. Go

Step 13

The RAID configuration is now complete for the first RAID controller. Go back to the controller selection by clicking on Controller selection. This time, select Adapter 1.

Step 14

Repeat all the steps that you performed for Adapter 0 with this new Adapter to set up the second RAID 5 array.

What to Do Next

Configure BIOS

Configure RAID with GUI (UCS C-Series M4 Servers)

Use this procedure if you have an M4 server and want to configure a RAID 5 Array on a virtual drive. For servers with more than one virtual drive, perform these steps for each virtual drive.

Before You Begin

Configure Cisco Integrated Management Controller

Procedure

Step 1

At the LSI screen, press CTRL-R. The Virtual Drive Management screen displays the list of unconfigured hard drives for the virtual drive.

Step 2

Under Virtual Drive Management screen, highlight the controller, and press F2 for Operations.

Step 3

If the drives are unconfigured (and the Create Virtual Drive option is not selectable), perform the following from the F2 menu:
Note:   You can skip this step if the Create Virtual Drive option is selectable.

1. Select Clear Configuration, then press Yes to clear the configuration.

2. Select Make JBOD (Just a Bunch Of Drives).

3. Select Make Unconfigured Good.

Step 4

Select Create Virtual Drive and press Enter.

Step 5

For the RAID Level option, select RAID 5.

Step 6

Tab to the Drives area. For each hard drive that you want to add to this virtual drive, select the hard drive by pressing the space bar. When the drive is selected, an X appears in the ID box.

Step 7

Enter any name for the RAID.

Step 8

Select Advanced.

Step 9

Set Read Policy to read ahead = always.

Step 10

For the Write Policy, select Write Back with BBU.
We recommend that you select 128-KB from the Strip Size drop-down list.

Step 11

For the I/O Policy, select Cached.

Step 12

For the Disk Cache Policy, select Enable.

Step 13

Tab to the Initialize option and select the option by pressing the space bar. An X displays in the Initialize box.

Step 14

Select OK. Press Enter. When the Initialization is complete, a popup appears.

Step 15

Select OK and press Enter. The Virtual Drive Management screen appears.

Step 16

Press Ctrl-N twice to go to Ctrl Mgmt tab.

Step 17

Press TAB, until the Boot Device field is selected, then press Enter.

Step 18

Select the drive that you want to use to boot the virtual drive.

Step 19

Press TAB multiple times to highlight Apply, then press Enter. The Back Initialization process begins. It may take several minutes to initialize the virtual drive.

Step 20

Press Ctrl-N until the VD Mgmt screen is displayed.

Step 21

If your server has more than one virtual drive, repeat this process for each virtual drive.

What to Do Next

Configure BIOS

Configure RAID with GUI (UCS E-Series M2 Servers)

Use this procedure if you have an M2 server and want to configure a RAID 5 Array on a virtual drive.

Configure the UCS E160D M2 for RAID5. At the time of this writing, follow the instructions in the GUI Configuration Guide for Cisco UCS E-Series Servers and the Cisco UCS E-Series Network Compute Engine Integrated Management Controller located at Click Here

Before You Begin

Configure Cisco Integrated Management Controller

Procedure

Step 1

In the Integrated Management Controller Navigation pane, click the Server tab.

Step 2

2. On the Server tab, click RAID.

Step 3

3. In the tabbed menu of the Storage Cards area, click the Virtual Drive Info tab.

Step 4

4. In the Actions area of the Virtual Drive Info tab, click Create.

Step 5

5. Complete the following fields:

1. Click and drag all 3 disk drives from Available Drives table to Selected Drives table. If you don’t have three disk drives, your hardware configuration does not match the Tested Reference Configuration.

2. In RAID Level drop-down list, select RAID 5.

3. Set Strip Size to 64 KB.

4. Set Drive Cache to Disable.

5. Set Access Policy to Read-Write.

6. Check/enable Set this Virtual Drive Bootable.

7. Uncheck/disable Use the Remaining Drive as Hot Spare.

Configure BIOS

You cannot select the hard drive in the BIOS Boot Order menu until the first logical volume has been defined. After RAID is configured, you need to make the second boot device the hard drive, as described in the following procedure:

Before You Begin

Configure RAID with one of the following methods:

- Configure RAID with Preboot CLI (UCS C-Series M2 or M3 Servers)

- Configure RAID with GUI (UCS C-Series M3 Servers)

- Configure RAID with GUI (UCS C-Series M4 Servers)

- Configure RAID with GUI (UCS E-Series M2 Servers)

Procedure

Step 1

Press indicated function key (e.g. F2 for a UCS C-Series) during boot to enter BIOS setup.

Step 2

Move the cursor to Boot Options.

Step 3

Verify that the CD ROM, or Cisco Virtual CD/DVD (Virtual CD/DVD drive), is selected for Boot Option #1.

Step 4

Verify that the hard drive (the RAID 5 Array) is selected for Boot Option #2.

Step 5

Verify that virtual threading is enabled in advanced CPU options.

Step 6

Verify that VT I/O Redirection is disabled in the CPU options.
The server will now try to boot the CD ROM drive first and the hard drive second.

What to Do Next

Install and Configure VMware ESXi

Install Cisco HyperFlex HX-Series Tested Reference Configurations

An example deployment including physical node placement, cabling, VLAN/subnet/IP address planning, and VM placement is available at Click Here .

Note

This TRC setup process assumes HX Release 1.8 and VMware vSphere ESXi 6.5.

Before You Begin

For installation requirements, review System Requirements and Requirements for Cisco Tested Reference Configuration Installation. Also refer to the “Installation Prerequisites” chapter of the Cisco HyperFlex Systems Getting Started Guide, Release 1.8, available at Click Here .

Perform the following tasks to install and configure a virtual machine on a Cisco HyperFlex TRC node.

Procedure

Step 1

Verify installation readiness, set up your 6200 Fabric Interconnect Switches, and prepare for HyperFlex node installation.

Follow instructions in the Cisco HyperFlex Systems Getting Started Guide, Release 1.8 at Click Here .

Step 2

Set up each HyperFlex node. Follow instructions in the Cisco HX240c M4 HyperFlex Node Installation Guide, Release 1.8 at Click Here .

Step 3

Complete procedure Download Virtual Machine Templates (OVA Templates).

Step 4

Download an OVA for collaboration application software, such as Cisco Unified CM onto your virtual machine.

Step 5

Use vSphere to create the VM on the server:

1. Use vSphere to Create the VM for Servers Without Optical Drives.

Step 6

Install Cisco Collaboration Applications on VMs.

Step 7

Install Collaboration applications such as Cisco Unified CM on the virtual machine.

Install and Configure VMware ESXi

The following sections provide a sequence of steps for bringing ESXi into service at the customer site.

Preparation for ESXi Installation

Before you install ESXi , make sure these tasks are completed:

- The BIOS boot order is configured to boot the CD-ROM or virtual CD/DVD first..

- Each virtual drives on your servers has been configured with a RAID array. For RAID configuration details for your, see RAID Configuration

For additional information about ESXi storage configurations, see Click Here .

For servers ordered as Cisco Business Edition 6000 or Cisco Business Edition 7000, these steps have been performed by the factory prior to shipping.

Install ESXi

- To determine which ESXi version is required for the application you are intending to deploy, see Click Here

- Install ESXi on one of the RAID arrays. If there are multiple RAID arrays, any is acceptable but we recommend that you install ESXi on the first.

Note

You can install ESXi on the first RAID array. It is not required that you install ESXi on both arrays.

- ESXi Installation takes less than 5 minutes. After installation is complete, remove the install CD or the virtual DVD and reboot the machine.

- Following a reboot, a gray and yellow ESXi console is displayed with two options:

- F2 to customize the system

- F12 to restart or halt the system

- At this point, press F2 and configure the system in accordance with your network.

Install vSphere Client

Once the host is on the network, you can browse to its IP address to bring up a web-based interface. The vSphere client is Windows-based, so the download and install must be performed from a Windows PC.

This installation proceeds like any other Windows application installation, and takes only a few minutes to perform. After the vSphere client is installed, you can bring it up and log into the host using the hostname or IP address, the root login ID, and the password configured above.

The host may also be joined to a vCenter if available and if you wish to manage the host through vCenter.

Configuring LAN on Motherboard (LOM) NICs and Virtual Switches

The following options may be configured:

- Simple vSwitch0 (default VMware virtual switch)

- For larger data centers using vCenter, you can configure distributed virtual switches (for example, distributed vSwitch or the Nexus 1000V distributed virtual switch)

- For all options, you must define a port group for each VLAN running on the virtual switch. These port groups are selected when configuring a Virtual Machine network adapter, to place the virtual machine on a given LAN.

What to Do Next

Download Virtual Machine Templates (OVA Templates)

Download Virtual Machine Templates (OVA Templates)

The configuration of a Cisco Collaboration application virtual machine must match a supported virtual machine template.

Before You Begin

Install and Configure VMware ESXi

Procedure

To download OVAs for Cisco Collaboration applications, go to Click Here .

What to Do Next

Create the VM for your server type:

- Use vSphere to Create the VM for Servers with Optical Drives

- Use vSphere to Create the VM for Servers Without Optical Drives

- ISO and VM Template Delivery

ISO and VM Template Delivery

Depending on the servers and virtualization licenses that you purchase, virtualization software and Cisco application software can be delivered either physically or electronically.

Use vSphere to Create the VM for Servers with Optical Drives

Cisco provides templates on a URL to download and transfer to a host. Use the following procedure to use vSphere create the VM for servers with optical drives.

Before You Begin

Download Virtual Machine Templates (OVA Templates)

Procedure

Step 1

Deploy a blank virtual machine from the OVA template for your application using the Cisco.com URL as the source.

Step 2

Make the CD-ROM drive available to the newly deployed VM.

Step 3

Click on Options > Boot Options the next time the virtual machine boots, force entry into BIOS Setup Screen.

Step 4

Insert the application installation DVD from the media kit in the system CD-ROM drive.

Step 5

Power on the VM, select Boot and promote CD-ROM to boot before the hard drive.

Step 6

Save the BIOS settings and boot. The installation screens for your application appear at this point.

What to Do Next

Install Cisco Collaboration Applications on VMs

Use vSphere to Create the VM for Servers Without Optical Drives

Cisco provides templates on a URL to download and transfer to a host. Use the following procedure to use vSphere create the VM for servers without optical drives.

Before You Begin

Download Virtual Machine Templates (OVA Templates)

Procedure

Step 1

Deploy a blank virtual machine from the appropriate OVA template for your application using the cisco.com URL as the source.

Step 2

Associate the bootable application installation ISO file with the newly deployed VM.

Step 3

Set up the BIOS boot order. For instructions, see the release notes for the OVA that you are deploying.

Step 4

Map the ISO-format application installer file from the media kit to the physical or virtual CD/DVD drive..

Step 5

Save the BIOS settings and boot. The normal installation screen for your application opens.

What to Do Next

Install Cisco Collaboration Applications on VMs

Install Cisco Collaboration Applications on VMs

Installing Cisco Unified Communications Manager

For details on how to install Cisco Unified Communications Manager, refer to the Installation Guide for Cisco Unified Communications Manager at the following URL:

Click Here

Installing Cisco Business Edition 6000

For details on how to install Cisco Business Edition 6000, refer to the Installation Guide for Cisco Business Edition 6000 at the following URL:

Click Here

Installing Cisco Business Edition 7000

For details on how to install Cisco Business Edition 7000, refer to the Installation Guide for Cisco Business Edition 7000 at the following URL:

Click Here

Chapter 3. Migration

- Migration from Nonvirtual Servers to Virtual Servers

Migration from Nonvirtual Servers to Virtual Servers

Migration of Collaboration applications from nonvirtual servers to virtualized servers uses different procedures depending on whether or not there is also an application version upgrade. For more information, see the following documents.

For systems migrating to Cisco Collaboration System Release 12.0:

- Installation Guide for Cisco Unified Communications Manager and IM and Presence Service, Release 12.0(1)

- Upgrade and Migration Guide for Cisco Unified Communications Manager and IM and Presence Service, Release 12.0(1)

- Prime Collaboration Deployment Administration Guide, Release 12.0(1a)

For systems migrating to Cisco Collaboration System Release 11.5:

- Click Here or higher.

- Cisco Prime Collaboration Deployment Administration Guide, Release 11.5(1) or higher.

- Installation Guide for Cisco Unified Communications Manager and IM and Presence Service, Release 11.5(1) or higher.

- Administration Guide for Cisco Unified Communications Manager and IM and Presence Service, Release 11.5(1)SU1 or higher.

For systems migrating to Cisco Collaboration System Release 10.5:

- Upgrade and Migration Guide for Cisco Unified Communications Manager and IM and Presence Service, Release 10.5(x) or higher.

- Cisco Prime Collaboration Deployment Administration Guide, Release 11.5(1) or higher.

- Installation Guide for Cisco Unified Communications Manager and IM and Presence Service, Release 10.5(2) or higher.

- Configuration and Administration of IM and Presence Service on Cisco Unified Communications Manager, Release 10.5 or higher.

Chapter 4. Administration

- Rack-Mount Server Daily Operations

- Monitoring From Virtual Machine

- Monitoring From Cisco Integrated Management Controller

- Monitoring From vSphere Client and vCenter

- Server Health Monitoring From ESXi

- Disk Management for Cisco UCS Rack-Mount Servers

- Automatic Update Statistics

- New Identity

- Related Documentation

Rack-Mount Server Daily Operations

At this point the application is installed and in operation. Daily operations for applications are similar to an installation on a physical server, including:

- Application configuration and integration with other applications

- RTMT performance monitoring

- SNMP monitoring and alarms

- DRS backup and restore

- CDR collection

- Device, trunk, gateway configuration and monitoring

Monitoring From Virtual Machine

Applications running in a VM have no ability to monitor the physical hardware. Any hardware monitoring must be done from the Cisco Integrated Management Controller, ESXi plugins, vCenter or by physical inspection (for flashing LEDs, and so on).

Monitoring of hardware is the customer's responsibility. It is assumed the customer is familiar with virtualized environments and knows how to manage hardware in these environments.

Monitoring From Cisco Integrated Management Controller

The Cisco Integrated Management Controller (Cisco IMC) provides the following hardware monitoring:

- An overview of CPU, memory, and power supply health

- An overview of hardware inventory, including CPUs, Memory, Power Supplies, and Storage

- Monitoring of sensors for Power Supplies, Fans, Temperature, Voltage, and Current

- A system event log that contains BIOS and Sensor entries

- LSI MegaRAID controller information, which includes physical and virtual drive layout and Battery Backup Unit information from the Inventory > Storage tab. This information was usually accessible for earlier UCS servers only by installing the MegaRAID plugin from ESXi.

For additional details, go to Click Here .

Monitoring From vSphere Client and vCenter

The vSphere Client provides the following monitoring:

- Hardware and system alarms defined under the Alarms tab in the vSphere Client when logged in to vCenter.

- VM resource usage under the Virtual Machines tab in the vSphere Client, as well as under the Performance tab for each VM.

- Host performance and resource usage under the Performance tab for the host.

For more information, go to Click Here .

Server Health Monitoring From ESXi

You can monitor server health from ESXi by logging into the ESXi console and inspecting system /var/log/messages for telltale entries.

Disk Management for Cisco UCS Rack-Mount Servers

For details on the drive specifications for your Cisco UCS server, refer to RAID Configuration.

Disks are hot-swappable. This does not mean that you will be able to swap drives ad-hoc after a failure. A process exists to swap drives. When a drive fails, you need to follow these steps:

Note

If you have an M4 server, refer to Click Here .

1. Reboot and enter the Preboot CLI.

2. Mark the defective drive for removal using -PdPrpRmv -physdrv [<encl>:<slot>] -a0.

3. Replace the drive.

The RAID array is rebuilt automatically when the replacement disk is inserted.

Note

Although Preboot CLI is recommended, you can also perform this task through the LSI MegaRaid GUI, where you can swap drives out without having to power-cycle the server to get into the preboot CLI. However, this method requires you to procure a separate machine (Windows or Linux) on the same subnet as the ESXi host, installed with the LSI MegaRaid utility.

Automatic Update Statistics

Communications Manager uses Automatic Update Statistics, an intelligent statistics update feature that monitors the changes made in the database tables and updates only tables that need statistic updates. This feature saves considerable bandwidth, especially on VMware deployments of Communications Manager. Automatic Update Statistics is the default indexing method.

For more information about database services, see the Cisco Unified Serviceability Administration Guide.

New Identity

Cisco supports the New Identity process for use with Cisco Unified Communications Manager. The New Identity process is designed to start with a Communications Manager application that is fully installed and configured with common settings. Often, the initial VM is saved as a VMware template and cloned as new Communications Manager publisher nodes come online.

The New Identity process copies the VMware template and changes a set of primary settings, such as the IP address and hostname, to give a new VM a unique identity in the network.

- Run New Identity Process

- New Identity Caveats

- Deploy Cluster Nodes Using Templates

Run New Identity Process

Procedure

Step 1

Create a new VM instance from the template of the deployed Unified CM application.

Step 2

Run the CLI command utils import config.
For more information about CLI commands, see the documentation at Click Here .

New Identity Caveats

When you run the New Identity process, note the following:

- Although you can provide a new OS administrator user ID in the XML file, you cannot change the OS administrator user ID during the New Identity process.

- Each cloned VM has the same network configuration as the VMware template. The network must be functional during the New Identity process. If you run the cloned VMs on the same LAN there can be duplicate IP addresses. Ensure that you do not run the VMware template, or multiple VMs from the initial template, at the same time on the same LAN.

- The NTP server must be accessible before you can configure it on the Unified CM application. Ensure that the VM has access to the new NTP server.

- If DNS is used, DNS servers must be accessible when you run the New Identity process.

- For Cisco Unity Connection, you must set the SMTP domain address after you run the New Identity process.

- For Cisco Unified Presence, you must set the postinstallation steps that configure the Unified CM system with which Cisco Unified Presence communicates after you run the New Identity process.

Deploy Cluster Nodes Using Templates

Procedure

Step 1

Perform a skip install.

Step 2

When prompted for the floppy/USB drive in the Pre-existing Configuration Information window, power down the VM.

Step 3

Clone or convert the VM into a VM template.

Step 4

For a new node, deploy the template and mount a virtual floppy drive that contains the configuration file from the AFG tool.

Related Documentation

- Cisco UCS documentation: Click Here

- Cisco HyperFlex documentation: Click Here

- The official list of supported servers for Cisco Unified Communications Manager releases is available at the following URL: Click Here

- Technical specifications of Cisco Unified Communications virtualized servers are available at the following URL: Click Here

- TCP and UDP ports for vCenter Server, ESX hosts, and other management access for other network components are listed in article 1012382 at the following URL:

Click Here

- The Cisco Unified Communications Virtualization docwiki, which discusses deployment of other Cisco Unified Communications products on virtualized servers, is available at the following URL: Click Here

Full Cisco Trademarks with Software License

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)