ipcc server services
TRANSCRIPT
© 2002, Cisco Systems, Inc. All rights reserved.
Functional Description
© 2002, Cisco Systems, Inc. All rights reserved. 2
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-3
CallRouterA LoggerA
IP
IP IP IP
PG1 PG2a PG3aACD1 ACD2
vru1
IXC Network NIC
CMS
AW2 PG2b PG3b
vru3
vru4vru2
1
2
3
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-4
CallRouterA LoggerA
IP
IP IP
PG1 PG2aACD1 ACD2
IXC Network NIC
CMS
AW2 PG2b PG3bPG3a
vru1IP
vru4vru2
vru3
4
5
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-5
CallRouterA LoggerA
IP
IP IP IP
PG1 PG2a PG3aACD1 ACD2
vru1
IXC Network NIC
CMS
AW2 PG2b PG3b
vru3
vru4vru2
1
2 3 4
5
6
7
8
9
10
11
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-6
Prefix Process Name Description
Ccag CCAGENT Central Controller DMP Agent. Device Management
Protocol Agent that manages session layer
communications with ICR nodes.
Dbag DBAGENT Central Controller Database Agent. Communications
process that validates access to the central database.
Dbw DBWORKER Host Database Lookup. Process that queries external
databases and uses resulting data in call routing.
Mds MDSPROC Message Delivery Service. Process that provides
reliable message delivery between ICR processes.
Nm NODEMAN Node Manager. Process that manages, restarts, and
initializes processes on each ICR Node
Nmm NMM Node Manager Manager. Process that manages,
restarts, and initializes the Node Manager process on
each ICR Node.
Rtr ROUTER Call Router. Process that receives call routing requests,
determines call destinations, and collects information
about the entire system.
Mcia, mcib MCINIC MCI Network Interface Controller process. Interface
between the CallRouter and the MCI signaling
network. Others would be Sprint NIC; INAP NIC, etc.
CIC Netwrkcic Network ICR process that connects to Customer ICR
ICRPNIC process. Passes the route request to another
ICR system
AGI Appgw Application Gateway. Allows a routing script to pass
data to an external application and receive data in
return which can be used in routing decisions.
Rts RTSERVER Real Time Server. Process that takes real-time data
retrieved from PGs and forwards it to Admin
Workstations
Router Processes
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-7
Prefix Process Name Description
Csfs CSFS Customer Service Forwarding Service. Handles
communications with various services like SNMP,
RAS, and Serial Event Feed.
Dtp DTP Customer Support Data Transfer Process (Dials The
Phone). Transfers events from the Logger to the
GeoTel Customer Support Center (CSC)
Lgr LOGGER Database Logger. Process that stores historical data and
information about the entire system in the central
database.
Nm NODEMAN Node Manager. Process that manages, restarts, and
initializes processes on each ICR node.
Nmm NMM Node Manager Manager. Process that manages,
restarts, and initializes the Node Manager process on
each ICR Node.
Rcv RECOVERY Central Database Recovery. Recovers central database
historical data.
SNMP SNMP The SNMP Extension Agent receives an event feed
from the CSFS process and communications with the
Windows NT SNMP Agent to generate SNMP traps
when certain alarmable events occur.
Logger Processes
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-8
Prefix Process Name Description
Abs ABS Application Bridge Server. A server process that
operates between the PG and the Aspect CallCenter
ACD. The Application Bridge Server monitors
disconnect and transfer messages between the PG and
application running on the Aspect CallCenter
Application Bridge.
CGI CTIServer CTI Gateway Service. Optional component that allows
an external CTI application to communicate with a
Peripheral Gateway. Can be installed on the same
machine as the PG software or on a separate machine.
Mds MDSPROC Message Delivery Service. Process that provides
reliable message delivery between ICR processes.
Nm NODEMAN Node manager. Process that manages, restarts, and
initializes processes on each ICR node
Nmm NMM Node Manager Manager. Process that manages,
restarts, and initializes the Node Manager process on
each ICR Node.
Opc OPC Open Peripheral Controller. Interface between the PIM
and the CallRouter. Supplies the CallRouter with
uniform message sets from different PG types.
Pgag PGAGENT Peripheral Gateway DMP Agent. The Device
Management Protocol Agent that manages session
layer communications between the PG and the
CallRouter.
Pim1 Varies. ex: Aspect
EventLink PIM, is
seen as ASPEVPIM
Peripheral Interface Manager. The GeoTel proprietary
interface between a peripheral and the PG.
Pim2, Pim3,
Pim4
PG Processes
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-9
Prefix Process Name Description
WebLink WebLink Enabled when WebView is enabled. In ICM 5.0
WebView will be installed for Reporting.
Nm NODEMAN Node manager. Process that manages, restarts, and
initializes processes on each ICR node.
Nmm NMM Node Manager Manager. Process that manages,
restarts, and initializes the Node Manager process on
each ICR Node.
Rtc RTCLIENT Real Time Client. Admin Workstation process that
receives real-time data from the Real-Time Distributor
Rtd RTDIST Real Time Distributor. Distributes real-time data to
Admin Workstations.
UAW UpdateAW UpdateAW. Monitors the CallRouter, looking for
configuration updates. If an AW sends up
configuration changes, all other AW’s note the
difference, and pull back the changes.
Lgr LOGGER Database Logger. Process that manages Real-Time and
Five-Minute data and information about the entire ICR
system. This process is similar to the Logger process on
the main loggers.
Replication Replication When AW is a Distributor and an HDS is installed this
process will be enabled to replicate the historicalData
from the Logger to the local HDS.
AW Processes
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-10
Node Manager
• Installed as a standard NT service
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-11
• Installed as a standard NT service
• One Node Manager per ICM Node (e.g. router, logger, PG,
CG, AW)
Node Manager
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-12
• Installed as a standard NT service
• One Node Manager per ICM Node (e.g. router, logger, PG,
CG, AW)
• Starts processes as specified by its registry config
Node Manager
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-13
• Installed as a standard NT service
• One Node Manager per ICM Node (e.g. router, logger, PG,
CG, AW)
• Starts processes as specified by its registry config
• Each process has Node Manager registry key under
– software\geotel\icr\<cust>\<node>\NodeManager\CurrentVersion\Proce
sses
Node Manager
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-14
• Installed as a standard NT service
• One Node Manager per ICM Node (e.g. router, logger, PG,
CG, AW)
• Starts processes as specified by its registry config
• Each process has Node Manager registry key under
– software\geotel\icr\<cust>\<node>\NodeManager\CurrentVersion\Proce
sses
• Node Manager must be restarted to read changes to registry
Node Manager
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-15
• Installed as a standard NT service
• One Node Manager per ICM Node (e.g. router, logger, PG,
CG, AW)
• Starts processes as specified by its registry config
• Each process has Node Manager registry key under
– software\geotel\icr\<cust>\<node>\NodeManager\CurrentVersion\Proce
sses
• Node Manager must be restarted to read changes to registry
• Monitors processes and restarts them if they fail or hang
Node Manager
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-16
• Installed as a standard NT service
• One Node Manager per ICM Node (e.g. router, logger, PG,
CG, AW)
• Starts processes as specified by its registry config
• Each process has Node Manager registry key under
– software\geotel\icr\<cust>\<node>\NodeManager\CurrentVersion\Proce
sses
• Node Manager must be restarted to read changes to registry
• Monitors processes and restarts them if they fail or hang
• Can request system reboot if critical process fails (or fails
repeatedly)
Node Manager
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-17
Router Startup
• All processes start and wait for MDS to go “In Service”
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-18
• All processes start and wait for MDS to go “In Service”
• MDS initializes and goes “In Service”
Router Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-19
• All processes start and wait for MDS to go “In Service”
• MDS initializes and goes “In Service”
• Router loads state from its peer if available. Otherwise
router requests config from logger
Router Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-20
• All processes start and wait for MDS to go “In Service”
• MDS initializes and goes “In Service”
• Router loads state from its peer if available. Otherwise
router requests config from logger
• ccagent accepts connections from DMP devices (PGS, AT&T
NICS and BTNUP NICS)
Router Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-21
• All processes start and wait for MDS to go “In Service”
• MDS initializes and goes “In Service”
• Router loads state from its peer if available. Otherwise
router requests config from logger
• ccagent accepts connections from DMP devices (PGS, AT&T
NICS and BTNUP NICS)
• Router responds to requests for configuration from PGS and
NICS
Router Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-22
• All processes start and wait for MDS to go “In Service”
• MDS initializes and goes “In Service”
• Router loads state from its peer if available. Otherwise
router requests config from logger
• ccagent accepts connections from DMP devices (PGS, AT&T
NICS and BTNUP NICS)
• Router responds to requests for configuration from PGS and
NICS
• rtsvr accepts connections from real time distributors
Router Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-23
• Logger and Recovery processes start and connect to
database.
Logger Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-24
• Logger and Recovery processes start and connect to
database.
• Logger connects to MDS on same side router and waits for
MDS to go “In Service.
Logger Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-25
• Logger and Recovery processes start and connect to
database.
• Logger connects to MDS on same side router and waits for
MDS to go “In Service.
• Recovery attempts to connect to its peer and sync up
historical data.
Logger Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-26
• Logger and Recovery processes start and connect to
database.
• Logger connects to MDS on same side router and waits for
MDS to go “In Service.
• Recovery attempts to connect to its peer and sync up
historical data.
• When logger sees MDS go in service it loads its state from
its peer if available. Otherwise it waits for instructions from
the router.
Logger Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-27
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
NMM
NM
1
2
NMM
NM
3
4
5
6
7
In
Service
Private Network
Visible / Public Network
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-28
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
8
9
Private Network
Visible / Public Network
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-29
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
10
Private Network
Visible / Public Network
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-30
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
11
Private Network
Visible / Public Network
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-31
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
1
2
3
5
4
Private Network
Visible / Public Network
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-32
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
6
Private Network
Visible / Public Network
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-33
IP Network Configuration for ICM
• Each synchronized ICM System (CC or PG) uses two
independent data networks:
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-34
• Each synchronized ICM System (CC or PG) uses two
independent data networks:
– Private Network carries synchronization traffic
• Can be a WAN or Ethernet
IP Network Configuration for ICM
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-35
• Each synchronized ICM System (CC or PG) uses two
independent data networks:
– Private Network carries synchronization traffic
• Can be a WAN or Ethernet
– Visible Network carries traffic between each side of the
synchronized system and foreign systems
• Can be a WAN or Ethernet
IP Network Configuration for ICM
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-36
CallRouterB LoggerBCallRouterA LoggerA
IP IP
IP IP
IP IP IP
PG1 PG2a PG3aACD1 ACD2
vru1
IXC Network
NICNIC
AW1
CMS
AW2 PG2b PG3b
vru3
vru4vru2
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-37
Goals of ICM Fault Tolerance
• Minimize time periods during which system is
unresponsive to call routing requests.
• Eliminate single points of failures that could cause the
system to stop.
• Provide disaster protection by allowing the system
components to be geographically separated.
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-38
Overview of ICM Fault Tolerance
• All critical parts of the system can be physically
duplicated.
• Communication paths between critical
components can also be duplicated.
– Critical Components
• Central Controller (Router & Logger
• PGs
• NIC’s
• Provide disaster protection by allowing the system
components to be geographically separated.
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-39
ICM Approaches to Fault Tolerance
• ICM uses multiple approaches to Fault Tolerance
– ICM is “Self-Healing”
– Node Manager
– Hot Standby
– Synchronized Execution
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-40
• Node Manager (nm)
– “First Line of Defense”
– Each Component in the ICM includes a Node Manager process.
• As shown earlier it is in Charge of starting other ICM Processes
• If a process fails, NM will restart it.
• NM can reboot an ICM node in the event of a critical failure.
• NM Properties are established in ICM Setup.
• NM process is managed by the NMM process, Node Manager
Manager.
ICM Approaches to Fault Tolerance
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-41
Hot Standby
• One set of processes is called the Primary or Active
– Active node or process does ALL the work
• One set of processes is called the Backup or
Standby
– Standby node or process watches and waits for the active
process to fail
• PGs and NICs primarily use Hot Standby Fault Tolerance
• PGs also use Synchronized Execution for certain processes.
ICM Approaches to Fault Tolerance
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-42
ICM Fault Tolerance Basics
• Synchronized Processes
1. Synchronized process pairs base ALL action on message input
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-43
• Synchronized Processes
1. Synchronized process pairs base ALL action on message input
2. All inputs (messages) received in same order by both
processes
ICM Fault Tolerance Basics
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-44
• Synchronized Processes
1. Synchronized process pairs base ALL action on message input
2. All inputs (messages) received in same order by both processes
3. Both processes compute same internal state and same outputs
ICM Fault Tolerance Basics
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-45
• Synchronized Processes
1. Synchronized process pairs base ALL action on message input
2. All inputs (messages) received in same order by both
processes
3. Both processes compute same internal state and same outputs
4. Main examples are Router, Logger, OPC
ICM Fault Tolerance Basics
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-46
• Synchronized Processes
1. Synchronized process pairs base ALL action on message input
2. All inputs (messages) received in same order by both
processes
3. Both processes compute same internal state and same outputs
4. Main examples are Router, Logger, OPC
5. When a duplexed synchronized process starts up it attempts to
receive state from its partner. If it can’t receive state, then it
attempts to initialize in simplexed mode.
ICM Fault Tolerance Basics
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-47
• Synchronized Processes
1. Synchronized process pairs base ALL action on message input
2. All inputs (messages) received in same order by both processes
3. Both processes compute same internal state and same outputs
4. Main examples are Router, Logger, OPC
5. When a duplexed synchronized process starts up it attempts to
receive state from its partner. If it can’t receive state, then it
attempts to initialize in simplexed mode.
6. When a synchronized process receives a request to transfer its
state to its peer it takes a snapshot of its entire synchronized
state. While it is taking the snapshot, new messages are queued.
When it has finished taking the snapshot, it resumes processing
messages while the state data is transferred in the background.
ICM Fault Tolerance Basics
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-48
• Synchronized Processes
1. Synchronized process pairs base ALL action on message input
2. All inputs (messages) received in same order by both processes
3. Both processes compute same internal state and same outputs
4. Main examples are Router, Logger, OPC
5. When a duplexed synchronized process starts up it attempts to receive state from its partner. If it can’t receive state, then it attempts to initialize in simplexed mode.
6. When a synchronized process receives a request to transfer its state to its peer it takes a snapshot of its entire synchronized state. While it is taking the snapshot, new messages are queued. When it has finished taking the snapshot, it resumes processing messages while the state data is transferred in the background.
7. While a synchronized process is in the processing of receiving state from its peer, new messages are queued. After the process has received and processed the entire state, it resumes processing messages.
ICM Fault Tolerance Basics
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-49
• MDS (Message Delivery Service)
– Provides message delivery between “local” processes
ICM Fault Tolerance Basics
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-50
• MDS (Message Delivery Service)
– Provides message delivery between “local” processes
– Handles splitting and synchronization of messages
ICM Fault Tolerance Basics
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-51
• MDS (Message Delivery Service)
– Provides message delivery between “local” processes
– Handles splitting and synchronization of messages
– Handles duplicate output messages (with agent processes)
ICM Fault Tolerance Basics
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-52
• MDS (Message Delivery Service)
– Provides message delivery between “local” processes
– Handles splitting and synchronization of messages
– Handles duplicate output messages (with agent processes)
– All messages sent from one “local” process to another go
through MDS
ICM Fault Tolerance Basics
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-53
• MDS (Message Delivery Service)
– Provides message delivery between “local” processes
– Handles splitting and synchronization of messages
– Handles duplicate output messages (with agent processes)
– All messages sent from one “local” process to another go
through MDS
– One MDS process is enabled the other is disabled
ICM Fault Tolerance Basics
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-54
• MDS (Message Delivery Service)
– Provides message delivery between “local” processes
– Handles splitting and synchronization of messages
– Handles duplicate output messages (with agent processes)
– All messages sent from one “local” process to another go
through MDS
– One MDS process is enabled the other is disabled
– MDS processes are said to operate in “paired” or “isolated”
mode
ICM Fault Tolerance Basics
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-55
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-56
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
Running
Alone
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-57
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-58
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
I’m duplexed.
Is my partner
still alive?
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-59
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-60
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
Yes.
I’m Enabled
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-61
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
Request State
Transfer
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-62
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
(Build State)
Here’s the
State!
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-63
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
Is my Config
up-to-date?
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-64
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
Yes or No.
If no, here is
the updated
info.
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-65
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
Am I missing
any historical
data?
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-66
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
Yes.
Here it is...
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-67
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-68
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-69
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-70
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-71
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-72
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-73
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-74
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-75
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-76
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-77
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-78
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-79
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-80
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-81
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-82
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-83
MDSEnabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
MDSDisabled Synchronizer
Router Logger
RCVDBA
NICRTS SQL
CCAG
Synchronized
Zone
IP IP
AW
PG1 PG2 PG3
IP IP
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-84
PG Startup
• All processes start and wait for MDS to go “In
Service”
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-85
• All processes start and wait for MDS to go “In
Service”
• MDS initializes and goes “In Service”
PG Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-86
• All processes start and wait for MDS to go “In
Service”
• MDS initializes and goes “In Service”
• OPC loads state from its peer if available. Otherwise
OPC sends initialize request to one pgagent
PG Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-87
• All processes start and wait for MDS to go “In Service”
• MDS initializes and goes “In Service”
• OPC loads state from its peer if available. Otherwise OPC sends initialize request to one pgagent
• pgagent attempts to establish an active path to one side of the central controller (and an idle path to the other side).
PG Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-88
• All processes start and wait for MDS to go “In Service”
• MDS initializes and goes “In Service”
• OPC loads state from its peer if available. Otherwise OPC sends initialize request to one pgagent
• pgagent attempts to establish an active path to one side of the central controller (and an idle path to the other side).
• Once active path to central controller is established, OPC sends request to the router asking to be told its configuration information.
PG Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-89
• All processes start and wait for MDS to go “In Service”
• MDS initializes and goes “In Service”
• OPC loads state from its peer if available. Otherwise OPC sends
initialize request to one pgagent
• pgagent attempts to establish an active path to one side of the
central controller (and an idle path to the other side).
• Once active path to central controller is established, OPC sends
request to the router asking to be told its configuration
information.
• Once OPC successfully receives its config from the router it
attempts to activate the configured PIMS. This causes the PIMS to
connect to the ACDs. If this is successful the PG reports
“Peripheral Online” to the router.
PG Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-90
PIM1 PGAGPIM2
MDSEnabled Synchronizer
OPC
IP Router
ACD2ACD1
PGnANMM
NM
12 In Service
3
4
5
6
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-91
PIM1 PGAGPIM2
MDSEnabled Synchronizer
OPC
IP Router
ACD2ACD1
PGnA
7
8
8
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-92
PIM1 PGAGPIM2
MDSEnabled Synchronizer
OPC
IP Router
ACD2ACD1
PGnA
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-93
IP Router
ACD2ACD1
Idle
PIM1
Idle
PGAG
Active
PIM2
MDSEnabled Synchronizer
OPC
PGnA
Active
PIM1
Active
PGAG
Idle
PIM2
MDSDisabled Synchronizer
OPC
PGnB
Idle Data Connection
to Side A CallRouter. PGAG
sends and receives
heartbeats
and acknowledgments.
Active Data connection to
Side B CallRouter. PGAG sends
and receives Data & Heartbeats.
Synchronized
Zone
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-94
IP Router
ACD2ACD1
Idle
PIM1
Idle
PGAG
Active
PIM2
MDSEnabled Synchronizer
OPC
PGnA
Active
PIM1
Active
PGAG
Idle
PIM2
MDSDisabled Synchronizer
OPC
PGnB
Idle Data Connection
to Side A CallRouter. PGAG
sends and receives
heartbeats
and acknowledgments.
Active Data connection to
Side B CallRouter. PGAG sends
and receives Data & Heartbeats.
Synchronized
Zone
Are you
there?
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-95
IP Router
ACD2ACD1
Idle
PIM1
Idle
PGAG
Active
PIM2
MDSEnabled Synchronizer
OPC
PGnA
Active
PIM1
Active
PGAG
Idle
PIM2
MDSDisabled Synchronizer
OPC
PGnB
Idle Data Connection
to Side A CallRouter. PGAG
sends and receives
heartbeats
and acknowledgments.
Active Data connection to
Side B CallRouter. PGAG sends
and receives Data & Heartbeats.
Synchronized
Zone
State
Transfer
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-96
IP Router
ACD2ACD1
Idle
PIM1
Idle
PGAG
Active
PIM2
MDSEnabled Synchronizer
OPC
PGnA
Active
PIM1
Active
PGAG
Idle
PIM2
MDSDisabled Synchronizer
OPC
PGnB
Idle Data Connection
to Side A CallRouter. PGAG
sends and receives
heartbeats
and acknowledgments.
Active Data connection to
Side B CallRouter. PGAG sends
and receives Data & Heartbeats.
Synchronized
Zone
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-97
IP Router
ACD2ACD1
Idle
PIM1
Idle
PGAG
Active
PIM2
MDSEnabled Synchronizer
OPC
PGnA
Active
PIM1
Active
PGAG
Idle
PIM2
MDSDisabled Synchronizer
OPC
PGnB
Idle Data Connection
to Side A CallRouter. PGAG
sends and receives
heartbeats
and acknowledgments.
Active Data connection to
Side B CallRouter. PGAG sends
and receives Data & Heartbeats.
Synchronized
Zone
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-98
IP Router
ACD1
Idle
PIM1
Idle
PGAG
Active
PIM2
MDSEnabled Synchronizer
OPC
PGnA
Active
PIM1
Active
PGAG
Idle
PIM2
MDSDisabled Synchronizer
OPC
PGnB
Idle Data Connection
to Side A CallRouter. PGAG
sends and receives
heartbeats
and acknowledgments.
ACD2
Active Data connection to
Side B CallRouter. PGAG sends
and receives Data & Heartbeats.
Synchronized
Zone
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-99
AW Startup
• Real Time Client (rtc) connects to its distributor and sends a
registration request.
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-100
• Real Time Client (rtc) connects to its distributor and sends a
registration request.
• Real Time Distributor (rtd) receives connect request from
client and attempts to connect to preferred Real Time Server
(rts).
AW Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-101
• Real Time Client (rtc) connects to its distributor and sends a
registration request.
• Real Time Distributor (rtd) receives connect request from
client and attempts to connect to preferred Real Time Server
(rts).
• Real Time Server receives connect request from distributor
and forwards the initial state of all real time tables (base
records).
AW Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-102
• Real Time Client (rtc) connects to its distributor and sends a registration request.
• Real Time Distributor (rtd) receives connect request from client and attempts to connect to preferred Real Time Server (rts).
• Real Time Server receives connect request from distributor and forwards the initial state of all real time tables (base records).
• UpdateAW service waits for real time feed to become active and then brings local config DB up to date according to config sequence number.
AW Startup
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-103
RTDistributor
RTClient
Logger
Replication
UpdateAW
cust_awdb
cust_hds
Admin
Workstation
ProcessesReal-Time Data from
CallRouter’s RTS process
Historical Data from
Central Controller Logger
NMM
NM1
2
3
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-104
RTDistributor
RTClient
Logger
Replication
UpdateAW
cust_awdb
cust_hds
Admin
Workstation
ProcessesReal-Time Data from
CallRouter’s RTS process
Historical Data from
Central Controller Logger
4
5
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-105
Logger Call Router Dist AW
Just showing Processes involved in Configuration change
(Intra-process communication on the Router and Logger flow thru MDS)
Logger
CC DB
4
Router
RTServer
3
5
Configure ICM
(on an AW)
1
DBAgent
2 6
7
8
RTDist
RTClient
UpdateAW
Logger AWDB
9
10
11
13
14
15
AWRTClientupcc.dll
12
12
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-106
Central Controller Failure Scenarios
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-107
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-108
Quiz
a) Network Interface Card
b) Network Intermediary Connector
c) Network Interface Controller
d) Non-Interruptible Computer
1In the context of ICM,
what is a NIC?
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-109
a) To store Configuration Information and
Historical Data
b) To cut down trees in the forest
c) To connect Peripheral devices to the Call
Router
d) To respond to route requests from a carrier network
2
Quiz
What is the primary function
of the Logger?
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-110
a) Modem, Scanner, or Printer
b) Automatic Call Distributor or Voice
Response Unit
c) Admin Workstations
d) AT&T, MCI, or Sprint NICs
3What are examples of
Peripheral Devices?
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-111
a) Dialed Number, Calling Line ID, and Caller
Entered Digits
b) Dialed Number, Caller Entered Digits, and
Peripheral Gateway Number
c) Dialed Number, ACD, and Calling Line ID
d) Calling Line ID, ANI, and Dialed Number
4What three things comprise
a route request?
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-112
a) MIS Link
b) CTI Link
c) TCP/IP Link
d) A and B
5PGs connect to ACDs over
the following logical
connections?
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-113
a) Cross Links
b) A-Links
c) Missing Links
d) Cuff Links
6The AT&T NIC connects to
the AT&T Network via:
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-114
a) Motor Oil Weight
b) Wire Gauge
c) Administrative Workstation
d) Admin Widget
7AW is an acronym for:
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-115
a) Synchronization and State Transfer of
Central Controller data
b) Passing Private messages
c) Connecting to Peripherals
d) Connecting to Admin Workstations
8The Private Network is used
for:
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-116
a) Storage of Historical Data
b) Storage of Real-time data
c) Storage of Configuration data
d) A & B
e) B & C
9The AWDB is used for:
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-117
a) Synchronized Execution
b) Duplicate Data Paths
c) Hot Standby
d) Node Manager
e) All of the above
10The ICM uses what approach
to fault tolerance:
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-118
a) Monitor Distribution Service
b) Message Delivery Service
c) Magical Data Synchronizer
d) Mail Delivery System
11MDS is an acronym for:
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-119
a) Node Manager will attempt to restart it.
b) The process is restarted by the INIT
kernel
c) It remains stopped
d) The PC reboots
12What happens if an individual
process fails?
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-120
a) Duplicate active processes receive
identical input messages, and produce
identical output
b) There is one active process, and one or
more idle backups
c) Two systems each do half the work
13Which of the following best
describes "synchronized
execution?"
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-121
a) Duplicate active processes receive identical input messages, and produce
identical output
b) Two systems each do half the work
c) Two electric chairs
d) There is one active process, and one or more idle backups
14Which of the following best describes
the Hot Standby approach to fault
tolerance?
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-122
a) To eliminate 007 and take over the world
b) To maintain session layer connectivity
with PGs and NICs.
c) To store and forward real-time data to
AWs
d) To enforce all the laws that haven't been passed yet
15What is the responsibility of the Central
Controller Agent (CCAgent)?
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-123
a) Create, Modify, and Edit configuration
information
b) Create, Modify, Edit, Schedule, and
Monitor Routing Scripts
c) Create, Edit, and Monitor Reports
d) All of the above
16What are the functions of the
Admin Workstation?
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-124
a) Personal Information Manager
b) Peripheral Intermediary Module
c) Peripheral Interface Manager
d) PC Interface Monitor
17What is PIM an acronym for?
Quiz
© 2002, Cisco Systems, Inc. All rights reserved. ICMSA 5.0—Lesson 2-125
18
T.
F.
It is possible to run ICM on
Windows 95/98? T/F.
Quiz
© 2002, Cisco Systems, Inc. All rights reserved.