This section contains the important considerations, frequently asked questions, and preinstallation tasks that you must perform to ensure that you can successfully install Unified CCX.
Unified CCX is the backbone of the Cisco Unified Contact
Center environment, comprising:
First node: Required in all deployments of Unified CCX.
Second node: The second node provides fault tolerance to the
system and provides standby capabilities if the first node goes down. The
second node, also called the high availability (HA), node is optional. The first and
second nodes can be split across the local area network (LAN) and wide area
network (WAN).
Unified CCX 9.0(1) is an appliance application similar to
Unified CM. It must be installed on dedicated servers, which must be either
Media Convergence Servers (MCS) or UCS servers (B-series or C-series). For details on the server requirements, see Server requirements.
Pre-installation tasks
Perform all pre-installation tasks
to ensure that you successfully install Cisco Unified Contact Center Express.
Procedure
Step 1
Read this entire document to familiarize yourself with the
installation procedure.
Step 2
Verify the integrity of any new server hardware (such as hard
drives and memory) by running any manufacturer-provided utilities.
Step 3
Ensure that your servers are listed as supported hardware and
sized appropriately to support the load of the cluster. Make sure to account
for any growth that has occurred since initial system configuration.
Step 4
If you are installing a cluster or adding a node, verify that the
links between servers meet the 80-ms round-trip time (RTT) requirement and that
you have enough bandwidth to support database replication.
For more information on the 80-ms RTT requirement, see
Cisco Unified Contact Center Express Solution Reference Network Design, available at http://www.cisco.com/en/US/products/sw/custcosw/ps1846/products_implementation_design_guides_list.html.
Step 5
If you are getting the system time from an NTP server (mandatory
for VMware deployments), verify that
the first node can synchronize with the NTP server before you install a
subsequent node. Log into the
Command Line Interface on the first node and enter the following command:
utils ntp status
Note
To avoid potential compatibility, accuracy, and network jitter
problems, the external NTP servers that you specify for the primary node must
be NTP v4 (version 4). If you are using IPv6 addressing, external NTP servers
must be NTP v4.
If the first node fails to synchronize with an NTP server,
installation of a subsequent node can also fail.
Step 6
If your firewall is not in the routing path, disable the firewall
between nodes, if possible. Also, increase the firewall timeout settings until
after you complete the installation.
To temporarily allow network traffic in and out of the nodes (for
example, setting the firewall rule for these nodes to
IP any/any) does not always suffice. The
firewall might still close necessary network sessions between nodes due to
timeouts.
Step 7
Do not run Network Address Translation (NAT) or Port Address
Translation (PAT) between
Unified CCX nodes.
Step 8
Record the network interface card (NIC) speed and duplex settings
of the switch port to which you will connect the new server.
You should
configure the same NIC settings on the server and on the switch port. For GigE
(1000/FULL), you should set NIC and switch port settings to Auto/Auto; do not
set hard values.
Enable PortFast on all switch ports that are connected to Cisco
servers. With Portfast enabled, the switch immediately brings a port from the
blocking state into the forwarding state by eliminating the forwarding delay
[the amount of time that a port waits before changing from its Spanning-Tree
Protocol (STP) learning and listening states to the forwarding state].
Step 9
Verify that all servers on which you plan to install Unified CCX are properly registered in
DNS.
Record the configurations settings for each server that you plan
to install.
Step 12
For Unified CCX, configure any subsequent
nodes on the first node before you install a subsequent node.
From
Unified CCX Administration on the first node, choose
System > Server
and configure the IP address for the subsequent nodes. For more information,
see Cisco Unified CCX Administration Guide.
Important considerations before installation
Carefully read the information that follows before you proceed with the installation:
Be aware that when you install on an existing server, the hard drive gets formatted, and all existing data on the drive gets overwritten.
Installing Unified CCX 9.0(1) on an existing server will format the hard drive and permanently remove the existing Unified CCX data. It also upgrades the system Basic Input Output System (BIOS), firmware, and Redundant Array of Inexpensive Disks (RAID) configuration if found outdated.
Ensure to connect each Unified CCX node to an uninterruptible power supply (UPS) to protect the Unified CCX server from unexpected power failure that may damage the physical media and to avoid reinstallation of Unified CCX.
Install the Unified CCX software on the first node or publisher node first and then on the subsequent nodes.
Verify that the first node is reachable (through LAN or WAN) from the second node before you start installing the second node.
Make a note of the security password that you specified while installing the first node, because it is required during the installation of second node.
Note
DNS configuration is mandatory for Unified CCX installation. Both Forward and Reverse records are required.
All servers in a cluster must run the same release of Unified CCX. The only exception is during a cluster software upgrade, during which a temporary mismatch is allowed.
Configure the server by using a static IP address so that the server IP address remains unchanged.
Do not attempt to perform any configuration tasks during the installation.
Do not install any Cisco-verified applications until you complete the installation.
Be aware that the field values (namely hostname and passwords) that you enter while you are running the installation program are case-sensitive.
Use the same Maximum Transmission Unit (MTU) value for all servers in the cluster.
If you are already running Unified CCX 7.x and planning to install Unified CCX 9.0(1), use the Cisco Unified CCX Pre-Upgrade Tool to back up all of the data from your existing system and restore this data on the upgraded Unified CCX 9.0(1) system.
Install the Unified CCX software during off-peak hours or a maintenance window to avoid service interruptions.
When you insert or remove a USB drive, you might see error messages on the console similar to “sdb: assuming drive cache: write through.” You can safely ignore these messages.
Carefully read the information that follows before you proceed with the installation.
Unified CCX 9.0(1) is packaged with the Linux-based Unified Communications Operating System (UCOS). It is an appliance model developed by Cisco. This appliance model provides a collection of frameworks, such as installation, serviceability, and service management, so that Unified CCX installed on this platform can leverage more out of this in terms of integration, communication and administration in coordination with Cisco Unified Communications Manager (Unified CM).
To install Unified CCX on approved servers (MCS, B-series, and C-series), following hardware requirements must be met.
Hardware—Approved MCS, B-series, and C-series servers
Hard disk—146 GB minimum
RAM—4 GB minimum
For a list of approved MCS, B-series, and C-series servers, see the Cisco Unified Contact Center Express Software and Hardware Compatibility Guide available here:
To prevent unpredictable behavior or loss of Unified CCX configuration and user data due to power failure, ensure uninterrupted power supply to the Unified CCX servers at all times.
Browser requirements
You can access the Unified CCX 9.0(1) web applications from a remote system using the following browsers:
Microsoft Internet Explorer Version 8.x or later
Mozilla Firefox Version 3.x or 4.x
Note
The Cisco Unified CCX 9.0(1) Web Chat Application can be accessed only using Microsoft Internet Explorer Version 8.x.
Cisco does not support or test on any other web browsers.
Unified CCX licenses
Licensing helps manage Unified CCX licenses and enforces the licenses for Unified CCX components and nodes. In Unified CCX 9.0(1), all the licenses are node-locked, which means the use of the license is restricted to only one particular node based on the License MAC address of that node. Typically, a Unified CCX 9.0(1) license is based on the License MAC of the first node only. This section provides information on obtaining licenses for new Unified CCX nodes as well as for Unified CCX nodes that have been upgraded from various releases.
The Unified CCX 9.0(1) Installation DVD comes bundled with four demo licenses; one each for Unified IP IVR, STD, ENH, and PRE package. Because ordering actual licenses may take a while, you can start using the demo licenses by uploading them to the system using the Unified CCX 9.0(1) Administration web interface. A demo license is valid for initial 30 days only. You can use these demo licenses to familiarize yourself with the capabilities of the applications available on the Unified CCX 9.0(1) Installation DVD during the initial 30 days. Using the demo licenses helps you understand the capabilities of each package.
New licensing mechanism
The Unified CCX 9.0(1) system uses a new licensing
mechanism. The licenses are based on a string called the License MAC, which is
different from the physical MAC address of a system. The License MAC string is
generated during installation and is based on various input fields, such as the
hostname and IP address. If any of these fields change after fresh
installation, the License MAC becomes invalid and you must request new
licenses. You can generate the License MAC before or after installation.
License MAC appears during system install. You
must make a note of the License MAC for ordering license files. To obtain License MAC
after installing Unified CCX 9.0(1), complete the following steps:
Procedure
Step 1
Log in to the Unified CCX 9.0(1) system command line interface
(CLI) using Unified CCX Administrator credentials.
Step 2
Run
show status command. Output of this command contains the
License MAC.
Obtain License MAC before installation
To obtain License MAC before you install Unified CCX
9.0(1), complete the following steps:
Fill in all the configuration information used for installation,
such as IP address, hostname, and more on that site.
The answer file that is generated can be used for unattended Unified
CCX 9.0(1) installation. You can also use this answer file to generate the
License MAC (based on given parameters) so you can order the license before you build the machine.
Step 4
After the answer file is generated, this page enables you to obtain
the License MAC.
Caution
If you change any of the parameters or configuration information
after ordering the license, License MAC will be changed and the ordered license
file may become invalid.
Step 5
To obtain a node license file for new Unified CCX servers and to obtain additional node-locked licenses, perform the following steps:
Enter the Product Authorization Key (PAK) that you received with your Unified CCX or phone order in the License Registration web tool at:
http://www.cisco.com/go/license.
Click Submit.
Follow the system prompts. You must enter the License MAC of the
first node of the Unified CCX cluster. You must enter a valid email address as
well as the number of nodes for which you want licenses.
The system sends the license files to you through email by using the
email ID that you provided. The format of a license file specifies unified
ccx_90_<timestamp>.lic. If you retain the .lic extension, you can rename
the license file. You cannot use the license if you edit the contents of the
file in any way.
Note
Unified CCX 9.0(1) supports only node-locked licenses. However,
Unified CCX 9.0(1) continues to recognize the existing licenses used for
Unified CCX versions earlier than 9.0(1) on an upgraded system only if an upgrade license is also present.
You must upload the license file to the server with the matching
License MAC address that you provided in Step 3. This server then takes on the
functionality of the license manager.
For more information on how to upload a license file and view
license information, see Cisco Unified Contact Center Express Administration
Guide available here:
For Unified CCX HA setup, a Warm Standby License is issued to
enable this feature. The process of ordering such a license is the same as that
of a single node standalone license.
What to Do Next
The Unified CCX 9.0(1) Warm Standby license and all other licenses
are node-locked to the License MAC address of the first node (typically the
Database Publisher node) of a Unified CCX cluster. When a second node is added,
it is verified that the first node has the valid add-on Warm Standby License.
After the cluster is set up, the licenses will be valid on both the nodes in a
cluster.
License MAC is dependent on some system parameters. Modifying any
of these parameters can change License MAC thereby invalidating current License
files. Here are the parameters on which the validity of a License MAC depends:
Time zone
NTP server 1 (or none)
NIC speed (or auto)
Hostname
IP Address
IP Mask
Gateway Address
Primary DNS
SMTP server
Certificate Information (Organization, Unit, Location, State,
Country)
License grace period
If your License MAC becomes invalid, you must request a new license. The system however continues to operate for 30 days without a new license. After the 30-day grace period ends, the system shuts down until you upload a new license using the updated License MAC. After you obtain rehosted licenses, these licenses can be uploaded through Add License page of the Unified CCX 9.0(1) Administration web interface.
Cisco Unified CCX disk space usage
This section provides information about determining disk
space usage and requirements when you install the Unified CCX. The historical
reporting (HR) database (DB) size of the Unified CCX depends on the size of
the hard disk on which it is stored. The table below provides an example of
disk space usage for these DB types.
Table 1 Cisco Unified CCX Disk Space Usage
Sever Type
Server Disk Size
HR DB Size
Repository DB Size
Agent Db Size (rascal)
Configuration DB Size
7816
1x160 GB
11 GB
3.0 GB
0.5 GB
0.5 GB
1x250 GB
11 GB
3.0 GB
0.5 GB
0.5 GB
7825
2x160 GB
12 GB
3.0 GB
0.5 GB
0.5 GB
2x250 GB
12 GB
3.0 GB
0.5 GB
0.5 GB
7835
2x146 GB
13 GB
3.0 GB
0.5 GB
0.5 GB
7845
4x146 GB
20 GB
3.0 GB
0.5 Gb
0.5 GB
4x300 GB
26 GB
3.0 GB
0.5 GB
0.5 GB
Server configuration information for installation
Use
Table 1
to record the information about your server that both the Answer File Generator
and the basic installation wizard prompt you to enter. Gather this information
for each Unified CCX 9.0(1) server that you install. You may not need to obtain
all the information; gather only the information that is pertinent to your
system and network configuration. You should make copies of this table and
record your entries for each server in a separate table so it is easy to
configure your system.
Note
Because some of the fields are optional, they may not apply to your
configuration. For example, if you choose not to set up an SMTP host during
installation, the parameter still displays, but you do not need to enter a
value.
Caution
You cannot change some of the fields after installation without
reinstalling the software, so be sure to enter the values that you want.
The last column in the table shows whether you can change a field
after installation, and if you can, it provides the appropriate CLI command.
Caution
Changing some of these configuration parameters result in changes to
your current License MAC. In such as case, you need to rehost the Unified CCX
9.0(1) licenses. For more information, see
New licensing mechanism.
Table 2 Node configuration table
Parameter
Description
Can Entry Be Changed Postinstallation?
Administrator ID
This field specifies the administrator account user ID that
you use for secure shell access to the CLI, for logging in to Unified
Communications Operating System Administration and for logging in to the
Disaster Recovery System.
No, you cannot change the entry after installation.
Note
After installation, you can create additional administrator
accounts, but you cannot change the original administrator account
user ID.
Your entry:
Caution
Avoid creating administrator account user IDs (for CLI
access or OS administration) starting with "uccx" or "UCCX" because such user
IDs may conflict with system account names used internally within the Unified
CCX server.
Administrator Password
This field specifies the password for the Administrator
account, which you use for secure shell access to the CLI, for logging in to
Unified Communications Operating System Administration and for logging in to the
Disaster Recovery System. Ensure the password is at least six characters long;
it can contain alphanumeric characters, hyphens, and underscore.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set password
admin
Application User Name
You use the Application User Name as the default user name for
accessing applications that are installed on the system except Unified Communications Operating System Administration and Disaster Recovery System.
Yes, you can change the entry after installation by using the
following CLI command:
CLI >
utils
reset_ui_administrator_name
Your entry:
Application User Password
You use the Application User Password as the default password
or accessing applications that are installed on the system except Unified Communications Operating System Administration and Disaster Recovery System.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > utils
reset_ui_administrator_password
Your entry:
Country
From the list, choose the appropriate country for your
installation.
Note
The value you enter gets used to generate a Certificate
Signing Request (CSR) and self-signed certificates.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set
web-security
Your entry:
DNS Primary
Enter the IP address of the DNS server that you want to
specify as the primary DNS server. Enter the IP address in dotted decimal
format as ddd.ddd.ddd.ddd.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set network
dns primary
Your entry:
DNS Secondary (optional)
Enter the IP address of the DNS server that you want to
specify as the optional secondary DNS server.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set network
dns secondary
Your entry:
Domain
This field represents the name of the domain in which this
machine is located.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set network
domain
Your entry:
Gateway Address
Enter the IP address of the network gateway.
If you do not have a gateway, you must still set this field to
255.255.255.255. Not having a gateway may limit you to communicating only with devices on your subnet.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set network
gateway
Your entry:
Hostname
Enter a hostname that is unique to your server.
The hostname can comprise up to 64 characters and can contain
alphanumeric characters and hyphens.
No, hostname change is not supported in Cisco Unified CCX
9.0(1).
For more information, see the Cisco Unified Contact Center
Express Administration Guide available here:
For information on how to change the IP Address for Unified
CCX, see the Cisco Unified Contact Center Express Administration Guide or Cisco
Unified Serviceability Administration Guide available here:
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set network
ip eth0
Your entry:
MTU Size
The maximum transmission unit (MTU) represents the largest
packet, in bytes, that this host will transmit on the network.
Enter the MTU size in bytes for your network. If you are
unsure of the MTU setting for your network, use the default value.
Default: 1500 bytes
The MTU setting must be the same on all nodes in a cluster.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set network
mtu
Your entry:
NIC Duplex
Choose the duplex mode for the network interface card (NIC),
either Full or Half.
Note
This parameter is displayed only when you choose not to use
Automatic Negotiation.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set network
nic
Your entry:
NIC Speed
Choose the speed for the NIC, either 10 megabits per second or
100 megabits per second.
Note
This parameter is displayed only when you choose not to use
Automatic Negotiation.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set network
nic
Your entry:
NTP Server
Enter the hostname or IP address of one or more network time
protocol (NTP) servers with which you want to synchronize.
Note
To avoid potential compatibility, accuracy, and network jitter problems, the external NTP servers that you specify for the primary node must be NTP v4 (version 4). If you are usingIPv6 addressing, external NTP servers must be NTP v4.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > utils ntp
config
Your entry:
Security Password
Servers in the cluster use the security password to
communicate with one another.
The password must contain at least six alphanumeric
characters. It can contain hyphens and underscores, but it must start with an
alphanumeric character.
Note
Save this password. You will be asked to enter the same
security password while installing the second node to form a cluster.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set password
user security
To avoid losing communications between nodes, you must change
the Security password on both nodes in a cluster and reboot both the nodes. For
more information, see the description of this command in the Cisco Unified
Communications Operating System Administration Guide, available here:
Enter the hostname or IP address for the SMTP server that is
used for outbound email.
The hostname can contain alphanumeric characters, hyphens, or
periods, but it must start with an alphanumeric character.
Note
You must fill in this field if you plan to use electronic
notification.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set
smtp
Your entry:
Organization
Enter the name of your organization.
Note
The value you enter gets used to generate a Certificate
Signing Request (CSR).
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set
web-security
Your entry:
Unit
Enter the name of the business unit of your organization.
Note
The value you enter gets used to generate a Certificate
Signing Request (CSR).
Yes, you can change the entry after installation by using the
following CLI command:
CLI
> set
web-security
Your entry:
Location
Enter the location of the server. The system uses this
information to generate certificate signing requests (CSRs), which are used to
obtain third-party certificates.
You can enter any location that is meaningful within your
organization.
Examples include the state or the city where the server is
located.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set
web-security
Your entry:
State
Enter the state where the server is located.
Note
The value you enter gets used to generate a Certificate
Signing Request (CSR).
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set
web-security
Your entry:
Country
From the list, choose the appropriate country for your
installation.
Note
The value you enter gets used to generate a Certificate
Signing Request (CSR) and self-signed certificates.
Yes, you can change the entry after installation by using the
following CLI command:
CLI > set
web-security
Your entry:
Time Zone
This field specifies the local time zone and offset from
Greenwich Mean Time (GMT).
Choose the time zone that most closely matches the location of
your machine.
Yes, you can change the entry after installation by using the
following CLI command:
You must perform all software installations and upgrades by
using Unified Communications Operating System Administration. The system can
upload and process only software that is approved by Cisco.
You cannot install or use third-party or Windows-based
software applications that you may have been using with a previous version of
Unified CCX with Unified CCX 9.0(1).
Usernames and passwords
Note
The system checks your passwords for strength. For guidelines on creating a strong password, see the Strong passwords.
During the installation, you must specify the following usernames and passwords:
You use the Administrator username and password to log in
to the following areas:
Unified Communications Operating System Administration
Disaster Recovery System
Command Line Interface
To specify the Administrator user name and password, follow
these guidelines:
Administrator username—The Administrator username must start
with an alphabetic character and can contain alphanumeric characters, hyphens
and underscores.
Administrator password—The Administrator password must be at least
six characters long and can contain alphanumeric characters, hyphens, and
underscores. See the
Strong passwords for
additional information on how to create a strong password.
You can change the Administrator password or add a new
administrator by using the command line interface. For more information, see
the Cisco Unified Communications Operating System Administration Guide, available here:
You use the Application username and password to access
applications that are installed on the system, along with external tool Cisco Unified
Real-Time Monitoring Tool (Unified RTMT).
To specify the Application username and password, follow
these guidelines:
Application username—The Application username must start with an
alphabetic character and can contain alphanumeric characters, hyphens and
underscores.
Application user password—The Application user password must be at
least six characters long and can contain alphanumeric characters, hyphens, and
underscores. See the
Strong passwords for
additional information on how to create a strong password.
You can change the Application username and password by
using the command line interface. For more information, see Command Line
Interface Reference Guide for Cisco Unified Communications Solutions, available
at:
The system uses this password to authorize communications
between nodes, and you must ensure that this password is identical on both the
nodes in a cluster.
The Security password must be at least six characters long
and can contain alphanumeric characters, hyphens, and underscores. See the
Strong passwords for
additional information on how to create a strong password.
Strong passwords
To create a strong password, follow these recommendations:
Mix uppercase and lowercase letters.
Mix letters and numbers.
Include hyphens and underscores.
Remember that longer passwords are stronger and more secure than
shorter ones.
Avoid the following types of passwords:
Do not use recognizable words, such as proper names and dictionary
words, even when combined with numbers.
Do not invert recognizable words.
Do not use word or number patterns, such as aaabbb, qwerty,
zyxwvuts, 123321, and so on.
Do not use recognizable words from other languages.
Do not use personal information of any kind, including birthdays,
postal codes, names of children or pets, and so on.
Unified Communications Answer File Generator
Unified Communications Answer File Generator, a Web application, generates answer files for unattended installations of Unified CCX 9.0(1) or later. Individual answer files (platformConfig.xml) are copied to the root directory of a USB key or a floppy diskette and are used in addition to the Unified CCX DVD during the installation process.
The Web application supports the following features:
Allows simultaneous generation and saving of answer files for unattended installation on the publisher node and the subscriber node.
Provides syntactical validation of data entries.
Provides online help and documentation.
However, the Web application supports only basic installations and not upgrades.
You can access the Unified Communications Answer File Generator at the following URL:
The Unified Communications Answer File Generator supports Internet Explorer Version 6.0 or later and Mozilla Version 1.5 or later.
Note
Cisco requires that you use USB keys that are compatible with Linux 2.4. It is important that you use USB keys that are preformatted to be compatible with Linux 2.4 for the configuration file. These keys will have a W95 FAT32 format.
Network errors during installation
During the installation process, the installation program verifies that the server can successfully connect to the network by using the network configuration that has been entered. If the installer fails to connect, a relevant message is displayed prompting you to select one of the following options:
RETRY—The installation program tries to validate networking again. If validation fails again, the error dialog box displays again.
REVIEW (Check Install)—This option allows you to review and modify the networking configuration. When an error is detected, the installation program returns to the network configuration windows.
Networking gets validated after you complete each networking window, so the message might display multiple times.
HALT—The installation halts. You can copy the installation log files to a USB disk to aid troubleshooting of your network configuration.
IGNORE—The installation continues. The networking error gets logged. In some cases, the installation program validates networking multiple times, so this error dialog box might display multiple times. If you choose to ignore network errors, the installation may fail.
Installation options
The installation process of Unified CCX 9.0(1) allows you to
perform a basic installation, factory installation, installation using Answer
File Generator, patch upgrade to a newer service release during the
installation, and upgrade from Unified CCX 7.x to Unified CCX 9.0(1).
For a more detailed description of the different
installation types, see below.
Table 3 Installation options
Installtion Type
Description
Basic
This option allows you to install the Unified CCX 9.0(1)
software from the installation disc and configure it simultaneously.
Factory
This option allows you to obtain a MCS hardware from Cisco,
preinstalled with the Unified CCX 9.0(1) software, which you need to configure
upon receiving in order to complete the installation.
Use Answer File Generator
This option allows you to install the Unified CCX 9.0(1)
software unattended if you provide the pre-existing configuration information
on a USB key or floppy disk.
Apply Patch (upgrade during installation)
This option allows you to apply a patch in order to upgrade
the software available on the installation disc. You can only apply one patch
during the installation process.
Note
Ensure that you have the upgrade patch available on a DVD or
on a remote server before you choose this option.