Cisco Cisco Unified Contact Center Enterprise 9.0(1)

Página de 254
Serviceability Best Practices Guide for Unified ICM/Unified CCE & Unified CCH 
©2012 Cisco Systems, Inc. 
 
207  
25: CICMRGRA: Feb 8 2007 05:36:09.890 +0000: %ICM_Router_unknown: [comp=Router-
A][pname=nm][iid=ipcc][sev=info][part=19.7/14]: Pings completed in zero time: 0 
26: CICMRGRA: Feb 8 2007 05:36:09.890 +0000: %ICM_Router_unknown: [comp=Router-
A][pname=nm][iid=ipcc][sev=info][part=19.8/14]: Pings completed in first third: 0 
27: CICMRGRA: Feb 8 2007 05:36:09.890 +0000: %ICM_Router_unknown: [comp=Router-
A][pname=nm][iid=ipcc][sev=info][part=19.9/14]: Total first third milliseconds: 0 
28: CICMRGRA: Feb 8 2007 05:36:09.890 +0000: %ICM_Router_unknown: [comp=Router-
A][pname=nm][iid=ipcc][sev=info][part=19.10/14]: Pings completed in second third: 0 
29: CICMRGRA: Feb 8 2007 05:36:09.890 +0000: %ICM_Router_unknown: [comp=Router-
A][pname=nm][iid=ipcc][sev=info][part=19.11/14]: Total second third milliseconds: 0 
30: CICMRGRA: Feb 8 2007 05:36:09.890 +0000: %ICM_Router_unknown: [comp=Router-
A][pname=nm][iid=ipcc][sev=info][part=19.12/14]: Pings completed in third third: 0 
31: CICMRGRA: Feb 8 2007 05:36:09.890 +0000: %ICM_Router_unknown: [comp=Router-
A][pname=nm][iid=ipcc][sev=info][part=19.13/14]: Total third third milliseconds: 0 
32: CICMRGRA: Feb 8 2007 05:36:09.890 +0000: %ICM_Router_unknown: [comp=Router-
A][pname=nm][iid=ipcc][sev=info][part=19.14/14]: Longest Ping Time: 0  
 
To differentiate each line in the entry, the part tag is added to each header where: 
[part=#1.#2/#3] 
#1
 = the sequence number of the first line (this is the same for all lines in the entry) 
#2
 = the part number of the specific line 
#3
 = the total number of parts in the entry 
Note the line beginning with sequence number 32, [part=19.14/14]: 
#1 = 19. #2 = 14 / #3 = 14 
 
10.6  EMSMON 
In Release 8.5(2), for Windows 2008, process windows for Unified CCE processes are no longer 
available. The title bar status information is available in the Diagnostic Portico; however, real time 
messages do not appear there. To address this, Cisco recommends that partners and TAC use 
EMSMON as a replacement. 
EMSMON displays process messages as they are logged. It displays the same content as the former 
process windows, except for the title bar and the stdout and stderr output. Logged events for the 
selected processs appear in the EMSMON window. However, rare error condition messages (for 
example, shelled processes) that go to stdout do not appear in an EMSMON window. 
To change the number of lines each EMSMON window retains, modify the command window 
parameters.
 
You can cut and paste in EMSMON (just as in the command windows). It is safer to cut and paste in 
EMSMON. 
For history (events before EMSMON starting), use DUMPLOG. 
10.6.1  How to Run EMSMON 
You can start EMSMON at anytime, even when the process is not running. (You can have a batch file 
on a machine to start sessions.) If the process is down, EMSMON displays messages from the process 
when the process starts. EMSMON does not end when the process ends. To end EMSMON, press 
Ctrl+C or close the window.