Guest

Cisco TelePresence Server

TelePresence Server, MCU, IP VCR, and Gateway Network Packet Capture

Document ID: 118353

Updated: Sep 08, 2014

Contributed by Cisco TAC Engineers.

   Print

Introduction

This document describes how to capture packets from the Cisco TelePresence Server, multipoint control unit (MCU), IP videoconferencing recording (VCR), and Gateways.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

  • Cisco TelePresence Server
  • Cisco TelePresence MCU Series
  • Cisco TelePresence Advanced Media (AM) Gateway 3600
  • Cisco TelePresence Integrated Services Digital Network (ISDN) Gateway Series
  • Cisco TelePresence IP Gateway Series
  • Cisco TelePresence Serial Gateway Series
  • Cisco TelePresence IP VCR Series

Components Used

The information in this document is based on these software and hardware versions:

  • Cisco TelePresence Server
  • Cisco TelePresence MCU Series
  • Cisco TelePresence Advanced Media Gateway 3600
  • Cisco TelePresence ISDN Gateway Series
  • Cisco TelePresence IP Gateway Series
  • Cisco TelePresence Serial Gateway Series
  • Cisco TelePresence IP VCR Series

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Capture Network Packets from Cisco TelePresence Server, MCU, IP VCR, and Gateways

The method to capture network packets varies slightly based on which product is used. The <interface> parameter differs based on the list given at the end of this document.

Note: For all products except MCU Mobility Service Engine (MSE) 8510, TelePresence Server, AM Gateway, and Cisco TelePresence MCU 5300 Series, a compact flash card must be inserted in the product's external slot.

The general syntax is shown here:

  1. Connect a serial terminal to the device's console port.

  2. Check that there are no active calls on the device.

  3. At the command prompt, enter:
    nettap <options> <interface>


  4. Go to the web interface and launch a call to a problem endpoint so that the problem is reproduced.

  5. Wait a few seconds and press Ctrl+C at the console in order to stop the packet-capturing process.

    The network capture file can be accessed in two ways:
    • Via the web interface if you click the Download network capture file on the Status page in order to download the file.
    • Via the built in FTP server (if available) if you use an FTP client in order to connect to the device's IP address and download the network_trace.cap file.

Nettap options

The nettap command has a few options that might be useful when you capture network traffic.

Tip: Use these options under the guidance of Cisco Technical Support.

These options are:

  • -a captures all packets that are sent/received on the port. By default, the device uses a capture filter in order to limit which packets are collected. The default capture filter reduces the load on the system while the capture runs and also reduces the file size of the capture.

  • -l removes the limit on the number of packets that are collected in a capture (by default, this is 160,000 packets). The limit reduces the file size of the capture; therefore this option must be used with care because it increases the CPU load on the device and fills the limited storage space.

  • -s removes the limit on the amount of data that is captured in each packet (normally 128 bytes). This option might be useful where the entire packet needs to be captured rather than just the headers. If you use this option, it increases the size of the capture file.

  • -h <host> limits the capture for packets to or from a specific IP address. This might be useful if there is a lot of network traffic on the interface and only one host is of interest, such as an endpoint.

Interfaces

The name of the interface depends on both the product in use and the software version it runs:

  • bge0 (port A) or bge1 (port B):

    • MCU 4200/ MSE 8420 or MCU 4500 that runs Version 3.1 or earlier
    • ISDN Gateway Series that runs Version 2.0 or earlier
    • IP Gateway Series that runs Version 2.0(1.11) or earlier
    • Serial Gateway Series
    • IP VCR Series


  • vfx0 (port A) or vfx1 (port B):

    • MSE 8510 that runs Version 3.1 or earlier
    • TelePresence Server that runs Version 2.2 or earlier
    • AM Gateway that runs Version 1.0(1.13)


  • A (port A) or B (port B): MCU 4200/ MSE 8420 or MCU 4500 that runs Version 4.0 or later:

    • MSE 8510 that runs Version 4.0 or later
    • MCU 5300 Series
    • TelePresence Server that runs Version 2.3 or later
    • ISDN Gateway Series that runs Version 2.1 or later
    • IP Gateway Series that runs Version 2.0(3.32)
    • AM Gateway that runs Version 1.1(1.33) or later
Updated: Sep 08, 2014
Document ID: 118353