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.
Step 1 | Verify that the monitor and keyboard are connected as described in the Quick Start Guide. | ||
Step 2 | Power on the monitor. | ||
Step 3 | Verify that
power is connected and the Power LED status, as shown in
Figure 1
and
Figure 2.
| ||
Step 4 | Push the power button (3) and verify that the power button LED the disk LED disk drive change to green. | ||
Step 5 | Watch the boot process on the monitor. | ||
Step 6 | (Optional)
Press
F8 to open the CIMC Configuration window when
prompted. In the CIMC Configuration window, reset the CIMC password, configure
the management interface IP address, and then exit.
| ||
Step 7 | (Optional) If you are using CIMC for remote console access, browse to the IP address that you configured and do one of the following: | ||
Step 8 | If you use the
default username and password to log in to the Cisco Integrated Management
Controller screen, the system prompts you to change the password. Changing the
password is mandatory.
The CIMC screen in Figure 3 offers various tasks, such as turning On Locater LED and launching KVM Console.
|
Follow this procedure to customize the Hypervisor (VMware vSphere Hypervisor) to enable remote access from your PC using the vSphere client.
Some Business Edition applications 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, view preinstalled applications, and browse the datastore to verify the preloaded collaboration application software.
Step 1 | Launch the
vSphere client application and type the IP address of the
Virtualization
Hypervisor.
| ||||
Step 2 | Use the login credentials that you previously configured. | ||||
Step 3 | (Optional) If
you order BE7000 with factory-preloaded embedded license, then the
BE7000 Virtualization
Hypervisor license is
preinstalled and is therefore ready for use on
delivery. If you need to reapply the license, follow these steps:
| ||||
Step 4 | Configure NTP:
| ||||
Step 5 | Configure
fault tolerance by using
the NIC teaming feature in VMware:
The Hypervisor is now ready to host virtualized collaboration applications. Virtual machines for five of the most commonly used collaboration applications are predeployed on the hypervisor for you. Software for these collaboration applications and additional applications are also preloaded in the datastore for your convenience. | ||||
Step 6 | Browse the
datastore:
| ||||
Step 7 | (Optional) Cisco recommends that you archive the OVA-ISO directory locally. If a server fails, the replacement product does not include preloaded content. |
Install virtual machines.
In addition to a number of predeployed virtual machines, Cisco Business Edition servers are shipped with selected Collaboration application software preloaded on the datastore. Consider the following points for a basic understanding of the preloaded file types:
An ISO file is a DVD image containing application install files.
Open Virtualization Archive (OVA) is used to package and distribute the virtual machine.
Some OVA files may include a prepared disk that includes preinstalled software (for example, cpc-provisioning-10.6.0-1015-medium.ova ).
Other OVA files do not include application software preinstalled. In this case, you must deploy the OVA template and then install the software using the ISO file that is provided on datastore (for example, cucm_10.5_vmv8_v1.9.ova and associated ISO file Bootable_UCSInstall_UCOS_10.5.2.10000-5.sgn.iso) .
Note | For details of which files ship with each server, see the relevant Release Note here: http://www.cisco.com/c/en/us/support/unified-communications/business-edition-7000/products-release-notes-list.html. |
To simplify the installation of the BE7000, a number of the most popular application virtual machines have been predeployed, ready for you to add configuration information to complete the installation.
To complete this process, launch the hypervisor console for the virtual machine you wish to use, power on and follow the instructions.
Some collaboration applications (such as Unified Communications Manager, Unity Connection, UCM Instant Messaging and Presence Service and Unified Contact Center Express) also accept a configuration file to automate this process. To use this feature, follow these steps:
Step 1 | Create an answer file for your application using the online tool at www.cisco.com/web/cuc_afg/. |
Step 2 | Add this file to a virtual floppy (vFloppy) image. Name the file as UCM.flp, CUC.flp, IMP.flp or CCX.flp based on the application. |
Step 3 | Copy this file to the AFG folder in the hypervisor datastore. |
Step 4 | Power on the virtual machine. The application completes the installation automatically. |
Follow this procedure to deploy additional virtual machines for applications that are listed in the preloaded files. For preloaded files in the Export Restricted or Export Unrestricted software, see the relevant Release Note here: http://www.cisco.com/c/en/us/support/unified-communications/business-edition-7000/products-release-notes-list.html.
The OVA template file defines the virtual machine for specific applications.
Note | In Release 10.5(1) and later, five applications are preinstalled. If you are deploying virtual machines using any of these five applications, you can skip the following procedure. |
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 Release Note here:
http://www.cisco.com/c/en/us/support/unified-communications/business-edition-7000/products-release-notes-list.html.
| ||
Step 3 | Continue to click Next to accept license agreements if prompted. | ||
Step 4 | Select the appropriate virtual machine size for your deployment. | ||
Step 5 | Specify a meaningful name for the virtual machine. |
After deploying all the required virtual machines, complete installation where required and set up applications that are ready for use.
To install Unified Communications applications, including Cisco Unified Communications Manager, Cisco Unified Communications Manager IM and Presence Service, Cisco Unity Connection, Cisco Emergency responder, and Cisco Unified Contact Center Express you can either use answer files to automate the installation process, or opt for manual installation. The following procedure describes both these options to install and set up the virtualized applications that are ready for use.
The following table describes the approximate installation time for each application:
Application |
Approximate Installation Time (In Minutes) |
---|---|
Cisco Unified Communications Manager |
60 |
Cisco Unity Connection |
60 |
Cisco Unified Communications Manager IM and Presence Service |
45 |
Cisco Prime Collaboration Provisioning |
15 |
Cisco Emergency Responder |
45 |
Cisco Unified Contact Center Express and Cisco Unified IP Interactive Voice Response |
60 |
Cisco Expressway |
30 |
Cisco TelePresence Video Communication Server Control |
30 |
Cisco TelePresence Conductor |
30 |
Cisco TelePresence Server Virtual Machine |
15 |
Cisco TelePresence Management Suite |
60 |
Cisco Paging Server |
15 |
Cisco TelePresence Content Server |
60 |
Note | You can install multiple applications concurrently to save time. |
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 | If you want
to use the answer files, follow this step to prepare the required files. Select
Edit
Settings from the right-click menu as shown in Figure 14. The
Virtual Machines Properties editing screen appears, as shown in the Figure 15.
| ||
Step 4 | Using 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". Right click to open the action menu as shown in the figure below.
| ||
Step 5 | For VMs that
are deployed using blank OVA templates, you need to edit the virtual machine
CD/DVD drive settings to connect the application software ISO image from the
datastore at power on. This step is not required for
preloadedpredeployed applications. Cisco
Unified Communications Manager and Cisco Unity Connection use same ISO file
(see the preloaded files for Cisco Business Edition 7000 here:
http://www.cisco.com/c/en/us/support/unified-communications/business-edition-7000/products-release-notes-list.html).
| ||
Step 6 | To begin
installation of each application, follow these steps:
|
After installing all required applications, access applications using a web browser. Add licenses and configure features as required.