Cisco Cisco Unified Contact Center Enterprise 9.0(1)
Serviceability Best Practices Guide for Unified ICM/Unified CCE & Unified CCH
©2012 Cisco Systems, Inc.
208
EMSMON has the same parameters as ProcMon:
<instance> <node> <process> [<process>…] [<system>]
The system parameter is optional. Use the system parameter to remotely run EMSMON.
For example, if the instance node is “ucce,” to monitor the JTAPI gateway on PG1A, type the
following:
following:
EMSMON ucce PG1A jgw1
If you are remote (on another PG) and the system name is UCCEPG1A, type:
EMSMON ucce PG1A jgw1 UCCEPG1A
Note: A trust relationship must exist between the two machines. (Use the “NET USE” command or complete an operation
that sets up a trust [for example, map a drive].)
that sets up a trust [for example, map a drive].)
10.6.2 Monitoring Process
A single EMSMON can monitor multiple processes and merge their output (for example, [jgw1 and
pim1]).
pim1]).
Multiple EMSMONs can watch a single process. For example, you can have a local EMSMON and a
remote EMSMON. However, Cisco recommends that you use one EMSMON only for each process.
remote EMSMON. However, Cisco recommends that you use one EMSMON only for each process.
10.6.3 Running EMSMON Remotely
To reserve system resources for Unified CCE processes, Cisco recommends that you run the
EMSMON client on a remote machine that does not host Unified CCE processes. For example, Cisco
does not recommend that you run the EMSMON client on side A of a PG and connect it to a process
on side B of a PG.
EMSMON client on a remote machine that does not host Unified CCE processes. For example, Cisco
does not recommend that you run the EMSMON client on side A of a PG and connect it to a process
on side B of a PG.
To run EMSMON on a remote machine, copy emsmon.exe, emsmon.pdb, and icrmessages.dll from
c:\icm\bin and place them on a remote machine.
c:\icm\bin and place them on a remote machine.
10.6.4 EMSMON Connections
You can have one local connection and five remote connections per process. When the number of
connections is exceeded, the oldest session is disconnected with the following message “You are
being disconnected because another user has connected to this named pipe.”
connections is exceeded, the oldest session is disconnected with the following message “You are
being disconnected because another user has connected to this named pipe.”
If your system is running a heavy call load, your EMSMON connections may disconnect and the
following message appears: “You are being disconnected because the system is running a heavy call
load; this connection may impact the performance of the system. It is recommended that you do not
reconnect your EMSMON sessions until your system returns to a normal call load.”
following message appears: “You are being disconnected because the system is running a heavy call
load; this connection may impact the performance of the system. It is recommended that you do not
reconnect your EMSMON sessions until your system returns to a normal call load.”
Note: To prevent Unified CCE processes from exceeding the system memory, Unified CC processes may stop
sending queued event messages to slow or paused EMSMON clients. If this occurs, EMSMON clients display a
message indicating one of the clients fell behind and there is a gap. This message is also logged in the processes
event log. This can happen if a particular EMSMON client is too slow or paused by quick edit or Ctrl+S for
example. This does not affect the Unified CCE process, only the EMSMON client.
sending queued event messages to slow or paused EMSMON clients. If this occurs, EMSMON clients display a
message indicating one of the clients fell behind and there is a gap. This message is also logged in the processes
event log. This can happen if a particular EMSMON client is too slow or paused by quick edit or Ctrl+S for
example. This does not affect the Unified CCE process, only the EMSMON client.