Capturing Network Traces from the CLI on CUCM and other Cisco UC Appliances

William Bell
Vice President, Solutions and Products

Let’s assume that we have an issue where one has setup LDAP synchronization and authentication on a Cisco Unified Communications Manager (CUCM) cluster but is having an issue with authenticating against LDAP over SSL.

For our example, the LDAP server in question is ad1.mycompany.priv (  The server is a Microsoft AD server and we are using the default TCP port allocation for LDAP over SSL (which is 636 for Microsoft).

We have decided that we would like to see a sniffer trace (sorry, protocol trace) of the conversation between the CUCM publisher and the LDAP server.

Step 1: Connect to the CUCM Host

Using an SSH client like putty/secureCRT/copSSH connect to the  CUCM publisher.


wjbell@tuffgong /
$ ssh admin@
admin@’s password:
Last login: Sat Mar 21 12:51:00 2009 from
Welcome to the Platform Command Line Interface



Simple enough.

Step 2: Prepare a Capture Trace File

From the admin: prompt, you will use the capture network utility to setup a protocol trace.  You can do this live and watch it on the screen if you are simply trying to determine that a conversation is happening or you can capture the output to a file.  We are going to do the latter.


admin: utils network capture file mycap count 100000 size all host all

Executing command with options:
size=all count=100000 interface=eth0
src= dest= port=


The trace continues until you press Ctrl-C.

Step 3: Download the Trace File

OK, so now you have a file somewhere on the system with the data that you would really like to view.  You have to download it to your machine.  You will need a running SFTP server on the target machine.  You can use openSSH on linux/unix, freeFTPd, copSSH, or something similar.


admin:file get activelog platform/cli/mycap.cap

The size of the file and other information is sent to the output screen.  You are prompted for the host name: use DNS or IP address of SFTP server
You are prompted for the port: Defaults to 22 (SSH)
The CUCM checks its local keys and then asks for your user ID and password on the SFTP server.

Step 4: View Trace

After the file has been downloaded, you can view it in whatever protocol analyzer you prefer as long as it support the  tcpdump/libpcap format (.cap usual file extension).  A good tool is WireShark.

As previously noted you can look at packets live on the CUCM console screen. You can also specify port, source address, destination address, and protocol filters.  Enter the command “utils network capture ?” for a list of all options.

7 responses to “Capturing Network Traces from the CLI on CUCM and other Cisco UC Appliances

  1. It was very usefull. Before read it I used to use the remote port mirror feature. That CM feature is more easy to use. I used the freeFTPd as SFTP Server. Works Fine !

  2. Asif,

    I do not think that is possible but I would have to go double check that assertion. My lab is offline at the moment. I’ll have to look into that later. For now, I am assuming that this is not possible. When I have used RTMT to retrieve files it has always been application trace files (or things like app log or syslog).

    I guess I think that if you are going to be at the CLI to create the protocol trace/capture then you might as well stay there to download the file.


    (twitter: @ucguerrilla)

  3. Yes you can
    Trace and log central> collect files>next to second page> Packet Capture Logs

Leave a Reply