Downloads |
Document ID: 20545
Contents
Introduction
Before You Begin
Conventions
Prerequisites
Components Used
Opening a NICROI Session
Turning on Tracing within NICROI
Turning Tracing On
Turning Tracing Off
Log Files
Niclog.xxx File
Roilog.txt File
Copying the Files
Using Roilog.txt
Using Niclog.xxx
Setting Download Directory
Transferring File
Examples
Related Information
Introduction
This document introduces you to possible trace settings available within a Network Interface Controller (NIC) Remote Operator Interface (NICROI) session, and provides step-by-step instructions for turning the trace level on and off. With this information you see route request data from the inter-exchange carrier (IXC), and label response information from the Cisco Intelligent Contact Management (ICM) Call Routers.
Before You Begin
Conventions
For more information on document conventions, see the Cisco Technical Tips Conventions.
Prerequisites
Readers of this document should be knowledgeable of the following:
-
Cisco ICM
-
AT&T NIC
Components Used
The information in this document is based on the software and hardware versions below.
-
Cisco ICM versions 4.6.2 and earlier
The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.
Opening a NICROI Session
NICROI is a session of a customer's AT&T NIC that allows the user to view a status of the NIC and the SS7 links that AT&T and the Cisco ICM Call Routers use to communicate. AT&T NIC sends Route Requests to the ICM using these links, and the ICM returns Labels used for making call routing decisions over these links. The following steps should be done on an ICM Logger.
-
Open a command prompt and change directory to the temp directory,
c:\>cd temp
-
There are two methods of accessing a NICROI session:
2A - Enter the following command from the command prompt:
nicroi geocustnic1a 5300 support custxyzzy
where:
-
nicroi is the executable command,
-
geocustnic1a is the name of the NIC,
-
5300 is the TCP/IP port on the NIC that connecting to,
-
support is the user name, and
-
custxyzzy is the password, configured in the nic.prm file.
2B - Enter the provided batch command from the command prompt:
nic cust 1[a/b]
where:
-
nic is the provided batch command,
-
cust is the customer instance, and
-
1a/1b represents LoggerA or LoggerB.
-
Once the above command is executed you see the NICROI console appears with a scrolling window behind it containing the activity seen by the NIC. The NICROI session is now open to the AT&T NIC.
Turning on Tracing within NICROI
There is only one level of tracing available within NICROI, it allows you to view Route Requests from the carrier. These route requests include the caller's Calling Line ID, any Caller Entered Digits, and the Dialed Digits (same as Dialed Number).
Turning Tracing On
Type nic sfk 4 in the NICROI CONSOLE window. (There is not be a prompt in this window, just an empty command line where you may enter commands.) This is the only trace element available within NICROI. You should now be able to click on the activity window behind your NICROI session and see the results of this trace setting scrolling.
Turning Tracing Off
In order to turn this tracing off, repeat the same entry nic sfk 4.
This added information is then inserted into a log file, either the niclog.xxx or the roilog.txt log file that you open/create. (explained below).
Log Files
There are two different places that you can capture this data, within the niclog.xxx or within a log file that you must open in order to have data written to it called roilog.txt.
Niclog.xxx File
The niclog.xxx is a file that the NIC writes data to automatically and labels each log file with a date/time stamp, along the same functionality as an EMS log file used for other ICM processes. Use the following steps to view a list of niclog.xxx files:
-
Type mgmt help within the NICROI window to see the options available.
-
Type mgmt file list to view all the niclog.xxx files available.
Note: The time shown is the time that the log is closed, meaning the time that information stopped being written to that particular log and another log is created. You can see in this list also the size of the file.
-
If you do not see the date and time you are looking for, you can view more log files by typing mgmt file list more until you see the log file that you want to capture. This log file format is useful if you have several specific time periods that you want to capture.
Roilog.txt File
The roilog.txt file is a file that is invoked by opening and closing it, this file is NOT automatically generated like the niclog.xxx. This log file is useful if you have one general, extended period of time that you want to capture. Use the following steps to create a roilog.txt file:
-
To "Open" a roilog.txt file:
From within NICROI issue the log open [<filename>] command. This command causes all status displayed in the NICROI logging window to be stored in a log file on the NICROI host system. The name of the log file can be specified. If omitted, the default name is roilog.txt which is placed in the current directory of the process from which NICROI starts.
Note: If you use this type of log file, you must close the log to stop the writing of information (once you have captured the time frame in question) before you copy the log file out to analyze it.
-
To "Close" an roilog.txt file:
From within NICROI type the .log command to close the NICROI log file. No further file logging is performed.
Copying the Files
You can copy these log files to your local drive. There are basically two ways you can gather this data, based on which file format you choose to use above.
Using Roilog.txt
If you have opened and created a log file using the method for roilog.txt, upon closing the log file, you have a copy of the log on your local drive. The file is located in the directory from which you began your NICROI session. Unless you have specified a download directory using the .xdir c:\<path name> command, then the file is created and written onto your local drive at the location from which you started your NICROI session.
Using Niclog.xxx
If you choose to use the niclog.xxx files you need to download or transfer the files to your local drive using the nmg roi transfer command as outlined below. Remember, if you do not specify a transfer directory with the .xdir c:\<path Name> command then the file is transferred to the directory from which you started your NICROI session. The following two sections are examples of these download commands.
Setting Download Directory
The .xdir d:\support command allows you to set your download directory so all roilog.txt files created are automatically transferred to that directory as well as any niclog.xxx files downloaded using the nmg roi transfer command (syntax below). If you do not use this command you may still gather these log files. They are then automatically downloaded into the directory from which you started your NICROI session.
Transferring File
The nmg roi transfer <file name> command allows you to transfer niclog.xxx files from NICROI to your local drive. Once you execute this command you can see the following lines from within your NICROI session as confirmation that the file transferred correctly.
nmg roi transfer <file name> ->BEGIN FILE TRANSFER of <file name> ->TRANSFER: d:\support\<file name> <file size> <date / time / year> ->FILE TRANSFER COMPLETE, seqnum = 3
Examples
Examples of the ROILOG with and without SFK 4 tracing are as follows:
Without SFK 4 Tracing:
1056901832 14:53:11 CCComm: (A)DMPRecvMsg: len=56, class=131, type=9, msg_buf=9CA9:0672 1056901833 14:53:11 ICRGate: RecvCRSMail: class = 131, len = 56, buf = 9CA9:0672 1056901973 14:53:11 CCComm: DMPReturnMsg: len=72, class=131, type=8, msg_buf=8CA8:3B2E 1056902004 14:53:11 CCComm: (A)DMPRecvMsg: len=56, class=131, type=9, msg_buf=9CA9:0672 1056902005 14:53:11 ICRGate: RecvCRSMail: class = 131, len = 56, buf = 9CA9:0672 1056902062 14:53:11 EMT: (0) Hearbeat sent. Countdown=4 1056902093 14:53:11 CCComm: DMPReturnMsg: len=72, class=131, type=8, msg_buf=8CA8:3DCE 1056902124 14:53:11 CCComm: (A)DMPRecvMsg: len=56, class=131, type=9, msg_buf=9CA9:0672 1056902124 14:53:11 CCComm: DMPSendAck: hi-seq=2244083712, lo-seq=2151022592 1056902125 14:53:11 ICRGate: RecvCRSMail: class = 131, len = 56, buf = 9CA9:0672 1056902163 14:53:11 EMT: (0) Hearbeat received.
With SFK 4 Tracing:
1057065593 14:54:45 MTP3: DIAG SLTC[0]: (<- HMDT (SLTM)) -> HMRT (SLTA) 1057065681 14:54:45 ICRGate: (5071) XId=0x10010(396), Q=1, DD=8002220300 1057065681 14:54:45 ICRGate: (5071) ANI=5089557093, CED= 1057065682 14:54:45 CCComm: DMPReturnMsg: len=72, class=131, type=8, msg_buf=8CA8:430E 1057065697 14:54:45 CCComm: (A)DMPRecvMsg: len=56, class=131, type=9, msg_buf=9CA9:068E 1057065697 14:54:45 CCComm: DMPSendAck: hi-seq=2991849473, lo-seq=2952986624 1057065698 14:54:45 ICRGate: RecvCRSMail: class = 131, len = 56, buf = 9CA9:068E 1057065698 14:54:45 ICRGate: (5071) (396) Label=7846402130, Type=0, CDPD= 1057065738 14:54:45 EMT: (0) Hearbeat received. 1057065819 14:54:45 ICRGate: (5071) XId=0x10001(397), Q=1, DD=8002220300 1057065819 14:54:45 ICRGate: (5071) ANI=2127410484, CED=3 1057065820 14:54:45 CCComm: DMPReturnMsg: len=72, class=131, type=8, msg_buf=8CA8:45AE 1057065831 14:54:45 CCComm: (A)DMPRecvMsg: len=56, class=131, type=9, msg_buf=9CA9:06AA 1057065832 14:54:45 ICRGate: RecvCRSMail: class = 131, len = 56, buf = 9CA9:06AA 1057065832 14:54:45 ICRGate: (5071) (397) Label=7846402076, Type=0, CDPD= 1057065966 14:54:45 EMT: (0) Hearbeat sent. Countdown=4 1057066098 14:54:45 EMT: (0) Hearbeat received.
Related Information
| Updated: Apr 28, 2005 | Document ID: 20545 |