Cisco Cisco IPCC Web Option Wartungshandbuch
Disk Failure
A disk failure requires additional steps. If a disk failure disables one side of the Central Controller
database, the disk must be repaired or replaced.
database, the disk must be repaired or replaced.
Note: Contact your Unified ICM support provider if a disk failure occurs.
Step 1
Rebuild the database structure from scratch on the new disks.
Step 2
Restore the configuration data, either from:
a.
A snapshot of the on-line database.
b.
The most recent backup tape.
c.
A backup tape taken from the on-line side of the Central Controller database.
d.
ICMDBA tool using a synchronization operation with the other side of the Logger.
At the time of the state transfer, any missing configuration data will be restored. Historical data
is restored by the Recovery process, which is run automatically each time the Node Manager
process starts on the Logger, or by loading the data from a backup tape.
is restored by the Recovery process, which is run automatically each time the Node Manager
process starts on the Logger, or by loading the data from a backup tape.
Software Failure
Cases of software failure that leave a Central Controller database unavailable are handled in
the same way as a disk failure (if the failure cannot be repaired by existing software tools).
Contact your Unified ICM support provider if such a failure occurs.
the same way as a disk failure (if the failure cannot be repaired by existing software tools).
Contact your Unified ICM support provider if such a failure occurs.
Network Interface Controllers
The NIC has four physical controllers on each side of the Central Controller. Each of these
controllers can simultaneously handle calls from the signaling network. Typically, each physical
NIC handles part of the total call routing load for the system software.
controllers can simultaneously handle calls from the signaling network. Typically, each physical
NIC handles part of the total call routing load for the system software.
The NIC processes are implemented as non-synchronized process pairs (one process on each
side of the Central Controller). The NIC runs as a process on the CallRouter machine.
side of the Central Controller). The NIC runs as a process on the CallRouter machine.
As a non-synchronized process pair, the NICs operate without knowledge of each other. They
are managed by the Node Manager and communicate with other CallRouter processes via the
Message Delivery Service (MDS). The following figure shows how fault tolerance is
implemented for various NICs.
are managed by the Node Manager and communicate with other CallRouter processes via the
Message Delivery Service (MDS). The following figure shows how fault tolerance is
implemented for various NICs.
Administration Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted Release 8.x
27
Chapter 2: Fault Tolerance
Network Interface Controllers