It is helpful in cases where communication between a WLC and a Remote Authentication Dial-In User Service (RADIUS) server, an Access Point (AP) or other controllers needs to be verified in a quick way with a packet capture at the WLC level but a port-span is hard to perform. This method displays the packets sent and/or received at CPU level of the WLC in hex format, which then be translated to a. Leaving a large trace on the box will also severely limit the space left for Audit and CDR logs.This document describes how to run a packet dump on a AireOS Wireless LAN Controller(WLC). Space is also limited on Codian products, so capturing media for an extended period of time is not an option. Using nettap on a busy MCU is a lot of work (the MCU will be dealing with a LOT of traffic), and this could cause performance issues and potentially even stability problems. Processing power is limited on Codian products, especially for 4200/8420, IP VCR and ISDN GW. Warnings Using on a busy MCU will cause problems It's a good idea to delete it after downloading if CDR logging or Audit logging is enabled. The capture can be retrieved from the MCU/TS using the Web interface: Status > General > Download network trace. In almost all cases you will want port A.įor example, if you want to capture media coming from a particular endpoint at 192.168.0.5, you would use:ĭon't forget the -s, or you will only capture the first 128 bytes of each packet - no good for media (and not much good for protocol signalling either). s : disable 128 byte limit on packet length l : disable limit on number of packets captured (160000) stop with Ctrl-C In order to start the capture, you will need access to the console port of the MCU/TS. True for MCU 4.2 or newer, and Telepresence Server Just found out today through a TAC case, that you can do packet captures directly from the MCU, there are two warning though, and are noted near the bottom.

Wireshark pcap captures