Skip to main content

Capture Cisco CSR packets and Examine with Wireshark


As you know the Cisco’s Cloud Services Router is a virtual router either installed and configured in public Clouds like Amazon Web Services, AWS, or in your private cloud hosted locally. I needed to capture and monitor the traffic on its interfaces with Wireshark. One way I could found is to capture your desired traffic on any interface of CSR, export it to your local disk and open it with Wireshark.
The following procedure can also be used to capture packets on other physical Cisco Routers running following IOS versions.
Cisco IOS Release 12.4(20)T or later
Cisco IOS-XE Release 15.2(4)S – 3.7.0 or later
Lets start capturing traffic here on Cisco CSR.
First we specify the interface to capture the packets on;
csr#monitor capture GIG2 interface GigabitEthernet 2 both
Here GIG2 is any name to create a file and store packets in it, both means to capture both inbound and outbound packets on interface gigabitethernet 2
You can specify ipv4 or ipv6 traffic, select protocol or even sepcify ACL to capture only selected traffic with following command;
csr#monitor capture GIG2 match ipv4 protocol tcp any any
Now we Start the capturing packets on our selected criteria as configured above
csr#monitor capture GIG2 start
The capture is now active. Allow it to collect the necessary data.
After capturing sufficient packets, Stop the capture:
csr#monitor capture CAP stop
Now either you can examine the capture in a summary or detailed view on CSR router itself or export it to your local computer disk and examine with Wireshark.
To examine the capture in a summary view:
csr#show monitor capture CAP buffer brief
Examine the capture in a detailed view:
csr#show monitor capture CAP buffer detailed
Export the capture in PCAP format for further analysis:
csr#monitor capture GIG2 export tftp://10.0.1.11/GIG2.pcap
Once the necessary data has been collected, and exported to tftp server, remove the capture:
csr#no monitor capture GIG2


Comments

Popular posts from this blog

Basic MPLS BGP and L3VPN Lab Setup

In this lab, we’ve set up a basic MPLS, BGP, and L3VPN environment, which is a great foundation for understanding how service providers build scalable networks. The lab uses the EVE-NG simulator along with Router IOS C7200-ADVENTERPRISEK9-M, Version 15.2(4)M8 to emulate a realistic MPLS environment. Below is a summary of the key components and roles of each router in the lab. MPLS Core Routers : The MPLS core consists of the routers responsible for label switching and forwarding customer traffic through the network: PE1 (Provider Edge 1) : Connects customer networks to the MPLS core and handles both MPLS and BGP routing. It also hosts VRF (Virtual Routing and Forwarding) instances for customers. PE2 (Provider Edge 2) : Functions similarly to PE1, connecting another customer network to the MPLS core. P1 (Core Router 1) and P2 (Core Router 2) : These routers serve as MPLS core routers and handle label switching but do not store or process customer routes directly. They simply f

OSPF Adjacency Stuck in EXSTART on Cisco IOS XR – Issue and Solution

In a recent lab setup using Cisco IOS XR on EVE-NG, I faced a common but frustrating issue with OSPF adjacencies getting stuck in the EXSTART state. After spending considerable time troubleshooting interface MTUs and configurations, I discovered that the root cause was related to the virtual network interface type being used. This post outlines the issue, troubleshooting steps, and the eventual solution that got everything working. Issue: While configuring OSPF between two routers running Cisco IOS XR in my lab, OSPF adjacencies were getting stuck in the EXSTART state. I verified that interface configurations, MTU settings, and OSPF parameters were correct, but the problem persisted. I tried adjusting the MTU size, using the mtu-ignore command, and even checked for ACLs, but nothing seemed to resolve the issue. Troubleshooting Steps: MTU Settings: I started by verifying that both sides of the OSPF adjacency had matching MTUs. I used the default MTU and even tried different values wit

How to Properly Clone an EVE-NG Lab with Configurations

Cloning labs in EVE-NG is a great way to duplicate setups and expand or experiment on a new copy without affecting the original lab. However, if not done correctly, the cloned lab may only copy the topology without configurations. In this guide, I’ll show you how to properly clone a lab in EVE-NG with all configurations using the EVE-NG GUI . Follow these steps to ensure that both the topology and router configurations are retained when cloning your lab. Steps to Clone an EVE-NG Lab with Configurations Save Running Configuration on All Devices In your original lab, make sure all devices have their configurations saved to NVRAM. Go into the CLI of each router and run the command: copy running-config startup-config Export All Configurations (CFGs) On the left sidebar in the EVE-NG Web UI , click on the "More Actions" option. Then select "Export all CFGs" . This step exports the configurations of all devices in the lab. Shutdown All Devices After exporting the confi