The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the tasks that you must perform to install software on your Business Edition 6000S server. It contains two main task flows that describe how to install software on the server.
For Customized deployments, use the tasks in this chapter to configure VMware and install application software on your server.
For Pre-configured deployments, or if your server was ordered via the Config To Order Portal, your server is already installed with VMware and UC applications.
In addition to pre-configured virtual machines, Cisco Business Edition servers are shipped with selected Collaboration application software that is pre-loaded on the datastore. Following is a breakdown of the file types for application installs:
ISO Files—An ISO file is a DVD image containing application install files (for example, Bootable_UCSInstall_UCOS_11.0.1.20000-2.sgn.iso). An ISO file is present for a UC application only if the OVA file for that application does not include the application software.
OVA Files—Each UC application has an associated Open Virtualization Archive (OVA) file, which is used to package and deploy the virtual machine. There are two types of OVAs for Business Edition servers:
Some OVAs deploy the VM, but do not include any application software. For those applications, there is an associated ISO file in the datastore (for example, cucm_11.0_vmv8_v1.0.ova and associated ISO file Bootable_UCSInstall_UCOS_11.0.1.20000-2.sgn.iso). For the installation, you must deploy the OVA template and install the software using the associated ISO file.
Other OVA files deploy the VM and install the application software (for example, cpc-provisioning-11.0.0-815-small.ova). For these applications, there is no ISO file. You can deploy the VM and install the software using the OVA file.
For information on which ISO and OVA files are pre-loaded in your server's datastore, refer to the preload summary for your server at http://www.cisco.com/c/en/us/support/unified-communications/business-edition-6000/products-release-notes-list.html.
Perform the following tasks to install software on your Cisco Business Edition 6000S server.
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | Initial Configuration
|
Initial configuration of BE6000S server. | ||
Step 2 | Configure Cisco Integrated Management Controller
|
Configure CIMC for your Business Edition 6000 server. | ||
Step 3 | Configure ESXi Virtualization Hypervisor
|
Configure the ESXi Virtualization Hypervisor host on the Business Edition 6000 server. | ||
Step 4 | Delete Unused Pre-configured VMs
|
Delete any pre-configured VMs that you do not require.
| ||
Step 5 | Deploy Virtual Machines
|
Deploy virtual machine OVAs for each UC application that you want to install. | ||
Step 6 | Customize VM for Cisco Unity Connection Installation
|
If your Business Edition 6000 deployment includes Cisco Unity Connection, customize the Unity Connection VM. | ||
Step 7 | Associate Application ISO Files to VM
|
For UC application installations that require an ISO file, mount the ISO file on the application VM.
| ||
Step 8 | Install UC Applications Using Touchless Installation
|
Optional. Use touchless installation to install any of the following core UC applications:
| ||
Step 9 | Install UC Applications Manually
|
Use the manual interactive process to install any remaining UC applications. |
Cisco BE6000S ships with pre-configured applications that use addressing from the 172.27.199.0/26 network, as shown in the following diagram.
Cisco Integrated Management Controller (CIMC) is the management interface for the Cisco UCS Server. CIMC runs within the server, allowing remote administration, configuration, and monitoring of the server via web or SSH command line access.
Complete the following tasks to configure CIMC on a Business Edition 6000 server for customized and pre-configured deployments.
Note | If you ordered your server via the Config To Order Portal, CIMC is already set up on your server. Skip to Configure ESXi Virtualization Hypervisor. |
Command or Action | Purpose | |
---|---|---|
Step 1 | Power On and Initial CIMC Setup
|
Power on the server and configure basic CIMC IP addressing details. |
Step 2 | Complete the CIMC Configuration
|
Configure DNS and NTP settings for the CIMC interface. |
Use this procedure to power on the server and begin basic Cisco Integrated Management controller (CIMC) configuration.
Ensure that the BE6000 server has been rack-mounted, connected to a power supply, connected to the data network, and that a monitor and keyboard are connected to the server, as described in the Quick Start Guide.
Use this procedure to configure DNS and NTP settings in the CIMC interface.
Complete the following tasks to set up ESXi Virtualization Hypervisor.
Command or Action | Purpose | |
---|---|---|
Step 1 | Customize Virtualization Hypervisor Remote Access
|
Customize your Virtualization Hypervisor to allow remote access using vSphere client. |
Step 2 | Access and Configure Virtualization Hypervisor
|
Configure your Virtualization Hypervisor with NTP settings and fault tolerance. |
Follow this procedure to customize the Virtualization Hypervisor (VMware vSphere Hypervisor) to enable remote access from your PC using the vSphere client.
Note | For servers ordered via the Config To Order Portal, skip to Step step 5. |
Step 1 | When the
hypervisor boots, the ESXi Direct Console User Interface displays on the
monitor as shown in the following figure
|
Step 2 | Press
F2 to enter the System Customization menu as shown
in the following figure.
|
Step 3 | Choose
Configure Password to change the password.
If your applications are preconfigured, skip to Step step 5. |
Step 4 | To assign a
static IP address, select the
Configure Management Network menu, and follow the
instructions on screen to change
"IP
Configuration" as shown in the figure below.
|
Step 5 | Connect your
PC to the data network, and browse to the new hypervisor IP address. Verify the
web page as shown in the figure below.
|
Step 6 | If not already installed on your PC, download and install the vSphere client. The vSphere client can be downloaded from the internet, or accessed in the datastore. |
Some Business Edition applications require the host to have a valid time reference. Follow these steps to access the ESXi host to configure NTP as well as configure fault tolerance for network interface cards (NICs) using the NIC teaming feature, view preinstalled applications, and browse the datastore to verify the preloaded collaboration application software.
If you want a custom install of a pre-configured application, you must delete the pre-configured image before you can install that application. Use this procedure to delete any pre-configured images that you are not using.
Note | If your server was ordered via the Config To Order Portal, you can skip this step as your server does not have pre-configured images. |
Step 1 | Log in to vSphere Client. |
Step 2 | Locate the
pre-configured virtual machine that you wish to delete.
|
Step 3 | If the VM has a green triangle, right-click the icon and select The green arrow disappears as the VM powers off. . |
Step 4 | Right-click the VM and select Delete From Disk. |
Step 5 | Repeat this procedure for each virtual machine that you wish to remove. |
For each application that you want to install, deploy the appropriate virtual machine OVA file.
Note | If you are not custom installing any applications, you can skip to Customize VM for Cisco Unity Connection Installation. |
Note | The OVA template file defines the virtual machine for specific applications. OVA templates are deployed in seconds, while a packaged OVA may take longer minutes to deploy. |
Step 1 | On the vSphere
Client, navigate to
.
The Deploy OVF Template screen is launched. |
Step 2 | Browse and select the source OVA template file on your PC. For application and filename mapping, see the Build summaries here: http://www.cisco.com/c/en/us/support/unified-communications/business-edition-6000/products-release-notes-list.html. |
Step 3 | If prompted to accept license agreements, continue to click Next. |
Step 4 | Specify a meaningful name for the virtual machine. |
Step 5 | Select the appropriate virtual machine size for your deployment. |
Step 6 | Set the remaining parameters, as required. |
Step 7 | If prompted for the Disk Format, specify Thick Provision Lazy Zero. |
Step 8 | Deploy VMs for all of your UC applications before proceeding to the next task. |
If your system includes Cisco Unity Connection, Customize VM for Cisco Unity Connection Installation.
Otherwise, Associate Application ISO Files to VM.
For Customized installations, use this procedure to configure your Cisco Unity Connection virtual machine settings to ensure optimum performance.
For Customized installations of Cisco Unity Connection, you must deploy the VM with high latency sensitivity and configure VM parameters. If the server is a BE6000S, you must also set your resource reservations.
Note | If using two CPUs for Unity Connection, you may need to disable, or not use one of the other supported applications. The total number of CPUs used by active virtual machines must not exceed six. |
Step 1 | From the virtual machine inventory in the vSphere client, right click the Unity Connection entry and select Edit Settings. |
Step 2 | Click the Options tab. |
Step 3 | Select the Configuration Parameters. menu, and click |
Step 4 | Click Add Row and complete the following details: |
Step 5 | If you want to use Unity Connect Unified or Integrated Messaging, do the following: |
Step 6 | For customized installs, if you are installing Unity Connection with one CPU, do the following: |
If you have deployed a new VM template for any of the following applications, use this procedure to associate the ISO installation files that will be used to complete the installation. Otherwise, you can proceed to the installation tasks.
Note | For an up to date list of installation files for your server, see the Preload Summary for your server at: http://www.cisco.com/c/en/us/support/unified-communications/business-edition-6000/products-release-notes-list.html |
Step 1 | In the vSphere client, select the UC application virtual machine. |
Step 2 | Select . |
Step 3 | From the Hardware tab, select CD/DVD Drive. |
Step 4 | Select Datastore ISO File. |
Step 5 | Browse to the datastore and locate the application ISO file. |
Step 6 | Select the file and click OK. |
Step 7 | Under Device Status, enable the Connected and Connect at power on option. |
Step 8 | Repeat this procedure for each application that you want to install that includes an ISO file. |
Install your UC applications using either of the following procedures:
Touchless installation allows you to install multiple UC applications simultaneously, across hosts if required, without having to interact with the system while the install process runs. While you must prepare the system, touchless installation can save time, particularly if you want to install multiple applications. If you are installing only one or two applications, you may prefer to follow the manual procedure in the following section.
Note | If you are not custom installing any applications, you can skip this section. |
Use touchless installation to install the following applications:
Command or Action | Purpose | |
---|---|---|
Step 1 | Generate Answer Files
|
Generate answer files (AFG files) for UC applications. |
Step 2 | Create Virtual Floppy Images
|
Use your AFG files to create virtual floppy images. |
Step 3 | Upload Virtual Floppy Images to Datastore
|
Upload your virtual floppy images to the datastore. |
Step 4 | Mount Virtual Floppy on VM
|
Mount each virtual floppy on the corresponding UC application VM. |
Step 5 | Run Touchless Installation
|
Run the touchless installation of your UC applications. We recommend that you run your installations simultaneously. |
Use this procedure to generate answer files for the touchless installation of your UC applications.
Tip | We recommend that you create application-specific folders (for example, UCM, IMP, CUC) in which to save the generated files so that you do not get the files mixed up. |
Step 1 | Go to the online answer file generator at: www.cisco.com/web/cuc_afg/. |
Step 2 | From the Product drop-down menu, select the UC application for which you want to generate answer files. |
Step 3 | Select the Version that you want to install. |
Step 4 | Complete the remaining fields with the installation details that you want to configure on the server. For example, you can assign items such as passwords, IP addressing, and DNS settings. |
Step 5 | Click Generate Answer Files to generate the platformConfig.xml file for that UC application. Each UC application generates a platformConfig.xml file. Cisco Unified Communications Manager also generates a clusterConfig.xml file. |
Step 6 | Save the generated answer files as follows: |
Step 7 | Repeat these steps for each UC application for which you want to use touchless installation. |
Use this procedure to create virtual floppy images from the answer files. You will use the virtual floppy images in your touchless installation.
Tip | We recommend that you follow the recommended naming conventions for your .flp files. |
You can use Winimage to create the virtual floppy images. You can download Winimage from http://www.winimage.com/download.htm. You can also use other tools, such as BFI, to create virtual floppy images.
Step 1 | In Winimage, select . |
Step 2 | From the Standard format, select 1.44 MB and click OK. |
Step 3 | Drag the platformConfig.xml file for the UC application onto the Winimage window. |
Step 4 | When prompted to inject the file into Winimage, click Yes. |
Step 5 | Cisco Unified Communications Manager only. Drag the clusterConfig.xml file onto the Winimage window. |
Step 6 | Select . |
Step 7 | Save the file as a virtual floppy image (.flp file) using the following naming conventions: |
Step 8 | Repeat this procedure for each UC application for which you want to use touchless installation. |
Use this procedure to upload the virtual floppy images to the datastore.
Step 1 | Start the vSphere client. |
Step 2 | Select the Configuration tab. |
Step 3 | Select Storage. |
Step 4 | Right-click on a datastore and Browse the datastore. |
Step 5 | Navigate to the destination directory and click the Upload files to this datastore icon. |
Step 6 | Upload the vFloppy images to the AFG folder. |
Step 7 | At the Upload/Download warning, click Yes. |
Step 8 | Close the Datastore Browser window. |
Use this procedure to mount the UC application virtual floppy images on their corresponding VM.
Step 1 | In the vSphere client, select the UC application virtual machine. |
Step 2 | Select . |
Step 3 | From the Hardware tab, select Floppy drive. |
Step 4 | Select Use existing floppy image in datastore. |
Step 5 | Browse to the datastore and locate the virtual floppy image. |
Step 6 | Select the file and click OK. |
Step 7 | Under Device Status, enable the Connected and Connect at power on option. |
Step 8 | Repeat this procedure for each UC application for which you want to perform touchless installation. |
Step 1 | Right-click the VM and select Edit Settings. |
Step 2 | Click the Options tab. |
Step 3 | Under Boot Options, check Force entry to BIOS. |
Step 4 | Click OK. |
Step 5 | In vSphere client, right-click the VM and select Open Console. A console window opens. |
Step 6 | Click the Power On icon in the console toolbar to power on the virtual machine. |
Step 7 | When the BIOS screen appears, configure the following boot order: |
Step 8 | Save the settings and exit the console. The UC application installation commences immediately. |
Step 9 | Repeat these steps for each UC application that you want to install. |
Step 10 | Once the installations are complete, remove the vFloppy configurations from the virtual machines. |
Use the manual method to install any remaining UC applications:
Use this procedure to follow the interactive install process to install any UC applications that do not have a touchless install option such as Cisco Emergency Responder.
Note | For details specific to Cisco Prime Collaboration Provisioning, refer to: |
Note | If you want to use this method to install both Cisco Unified Communications Manager and IM and Presence Service, you must first complete installation of the Unified Communications Manager publisher. |
Step 1 | In vSphere Client, power on the VM for the application that you want to install. |
Step 2 | Right-click the VM, and choose Open Console. A console window appears. |
Step 3 | Follow the screen prompts to install the application from the console. |
Step 4 | If you are using the manual method to install both Cisco Unified
Communications Manager and IM and Presence Service, once the Cisco Unified
Communications Manager publisher node installation completes, do the following:
|
Step 5 | Repeat this procedure for each UC application that you want to install. |
Use this procedure to install Cisco Prime Collaboration Provisioning.
Step 1 | In vSphere client, power on the VM that you deployed for Prime Collaboration Provisioning. |
Step 2 | Right-click the VM and choose Open Console. A console window appears. |
Step 3 | At the login prompt, type setup. |
Step 4 | At the prompts, enter each network configuration detail, and press Enter. |
Step 5 | At the Installation Mode prompt, enter 1 for Standard Prime Collaboration Provisioning. |
Step 6 | Follow the prompts to complete the installation. |