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.
Ensure that the BE6000 server has been rack mounted, connected to a power supply, connected to the data network, and a monitor and keyboard is connected to the server, as described in the Quick Start Guide.
Follow this procedure to customize the ESXi host (the VMware hypervisor) to enable remote access through the vSphere client.
Some applications on BE6000 require the services of a valid NTP server. Follow these steps to access the ESXi host, configure NTP, configure fault tolerance for network interface cards (NICs) using the NIC teaming feature, and browse the datastore to verify the preloaded collaboration application software.
Deploy virtual machines.
Cisco BE6000 is shipped with some selected Collaboration software, license files and Open Virtualization Archive (OVA) files that are preloaded on the datastore. Consider the following points for a basic understanding of the file types that are preloaded in the datastore:
An ISO file is a DVD image that was used to distribute application software in the past.
Open Virtualization Archive (OVA), a file with the ".ova" extension, is used to package and distribute the virtual machine template.
Some OVA files may also have application software preinstalled on the virtual machine. In this case, an ISO image is not needed (for example, cpc-provisioning-9.5.0-245-small.ova, listed in the Preloaded Files for Cisco Business Editition 6000 Export Restricted K9 Software here: http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cucm/BE6000/releasenotes/BE6000SoftwareLoadSummary-9X10X-K9-01.pdf ).
Some OVA files do not have application software preinstalled. In this case, you must install the software using the ISO file that is provided on datastore (for example, cucm_9.1_vmv8_v1.7.ova and associated ISO file Bootable_UCSInstall_UCOS_9.1.2.10000-28.sgn.iso, listed in the Preloaded Files for Cisco Business Editition 6000 Export Restricted K9 Software here: http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cucm/BE6000/releasenotes/BE6000SoftwareLoadSummary-9X10X-K9-01.pdf) .
Note | For pre-loaded files in the Export Restricted version 9X10X-K9 and Export Unrestricted version 9X10X-XU, refer to the relevant Release Note here: http://www.cisco.com/c/en/us/support/unified-communications/business-edition-6000/products-release-notes-list.html. |
Follow this procedure to deploy virtual machines for applications that are listed in the Preloaded Files for Cisco Business Editition 6000 Export Restricted K9 Software here: http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cucm/BE6000/releasenotes/BE6000SoftwareLoadSummary-9X10X-K9-01.pdf. The OVA template file defines the virtual machine for specific applications.
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 Preloaded Files for Cisco Business Editition 6000 Export Restricted K9 Software here: http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cucm/BE6000/releasenotes/BE6000SoftwareLoadSummary-9X10X-K9-01.pdf. |
Step 3 | Continue to click Next to accept license agreements and default values. |
Step 4 | Configure your deployment: |
Step 5 | For VCS and Paging server, provide a meaningful name. |
After deploying all required virtual machines, install individual collaboration applications.
Follow this procedure to install and set up the applications on their designated virtual machines.
The approximate time that is required for each application is as follows:
Note |
Step 1 | Contact the data network administrator and make sure that you collect the network information that is described in "Preparation." | ||
Step 2 | Plan the sequence of installing the applications to minimize the time that is required. | ||
Step 3 | On the vSphere
client, select an application’s virtual machine. The client changes the panel
name to application name, and adds one more tab named
"Getting
Started". Compare Figure 12 and Figure 13. Right click to open the action
menu as shown in Figure 13.
| ||
Step 4 | For VMs that
are deployed using blank OVA templates, you need to edit the settings of
virtual machines to connect the ISO image of application software at power on.
Note that Unified Communications Manager and Cisco Unity Connection use same
ISO file (see
Preloaded Files for Cisco Business Editition 6000 Export
Restricted K9 Software here:
http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cucm/BE6000/releasenotes/BE6000SoftwareLoadSummary-9X10X-K9-01.pdf).
| ||
Step 5 | Select
Edit
Settings… from the right-click menu as shown in Figure 13.
The Virtual Machines Properties editing screen appears, as shown in Figure 14. | ||
Step 6 | To begin
installation of each application, follow these steps: Installation will
continue automatically for the time listed in Step 2.
|
After installing all required applications, access applications using a web browser and perform initial setup of some applications.
The following are steps to install Cisco Unified Communications Manager (a blank OVA) and Cisco Video Communications Server (a preinstalled OVA).
Step 1 | Power on and open the console of the virtual machine, as illustrated in Figure 13. | ||
Step 2 | On the DVD Found window, select No for media check. | ||
Step 3 | In the Product Deployment Selection window, select Cisco Unified Communications Manager, then select OK. Finally, select Yes in the next Proceed with Install window.
| ||
Step 4 | Perform the following steps: | ||
Step 5 | Select No for DHCP. The Static Network Configuration window appears. | ||
Step 6 | Enter the hostname, (such as CUCM), IP address, IP mask, and gateway address; then select OK. Select Yes for DNS Client, followed by entering DNS server information in next window. | ||
Step 7 | The next two windows prompt you to set up administrative login information and organization information, followed by confirming whether the server is the first node; in most cases, select Yes. | ||
Step 8 | In the next windows, select No for network connectivity test, and again provide the hostname, IP address and security password. Finally, provide a valid reachable NTP server. | ||
Step 9 | The next two windows prompt you to set a security password and SMTP server information. Finally, application user information is required, followed by the last window Platform Configuration Confirmation. Select OK to continue the installation, which will last for approximately 60 minutes without any user interaction on the console. After you see the login prompt on the console, access the Unified Communications Manager IP address in a web browser. |
Step 1 | Power on and open the console of the virtual machine, as illustrated in Figure 13. |
Step 2 | At the login prompt, enter admin for username and TANDBERG for the password. |
Step 3 | At the Run Install Wizard prompt, type Y and press Enter. |
Step 4 | To change password, type Y and press Enter, and at the prompt type the new password and click Enter. |
Step 5 | The next series of prompts are for network information. Select the IP Protocol (the default is IPv4), provide the IP address, subnet mask, and default gateway address. Finally, select the ethernet speed of the LAN (the default is auto). |
Step 6 | For the Run SSH (Secure shell) daemon, type Y and press Enter. |
Step 7 | At the Restart Now prompt, type Y and press Enter. |
Step 8 | After the system reboots, access the Cisco Video Communication Server in a web browser. |