Note: it may be necessary to exclude a particular host, in this case use a '!' in front of the IP. In troubleshooting an issue with CUCM and a particular host, it may be necessary to use the 'host' option to filter for traffic to and from a particular host. Note: For more information about which services require communications on each port, refer to the TCP and UDP Port Usage Guide for the applicable version of CUCM. Troubleshooting a communications issue with Cluster Manager, it might be desireable to capture based on a specific port (8500) using the port option. To do this simply execute on the admin CLI 'utils network capture eth0 file packets count 100000 size all' Note: If 'host' is provided, do not provide 'src' or 'dest'įor a typical capture, one might wish to collect ALL packets of ALL sizes from and to ALL address into a capture file called 'packets.cap'. This option will display all packets to and fro that address. The host address of the packet as a host name or IPV4Īddress. Protocol addr - the protocol should be one of the following: Num - the port number of the packet (either src or dest) The number of bytes of the packet to captureĭestination address of the packet as a host name or IPV4 address

Note: The file will be saved in platform/cli/fname.capįname should not contain the '.' characterĬount of the number of packets to captureįor the screen is 1000, for a file is 100000 Page,numeric,file fname,count num,size bytes,src addr,dest addr,portįile fname - output the information to a file The command is 'utils network capture' and the syntax is as follows: To start the capture, establish a secure shell (SSH) session to the CUCM server authenticating with the Platform Administrator account: This document describes the process in four steps. When troubleshooting in Cisco Unified Communications Manager, it is sometimes necessary to collect packets which are being sent to and from the network interface on a CUCM server.

Packet capture tool from intune