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

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.

Authoritative DNS Servers Delegation and Internal DNS Explained

DNS (Domain Name System) plays a critical role in how users and systems find resources on the internet or within internal networks. Whether it's managing an internal domain in an enterprise or delegating parts of a domain for traffic distribution, DNS setups vary widely depending on needs. In this blog post, we’ll break down the different types of DNS setups, including authoritative DNS servers, DNS delegation, and how internal DNS functions within organizations. 1. Authoritative DNS Server An Authoritative DNS server is the final source of truth for a specific domain. When someone queries a domain (e.g., example.com ), the authoritative DNS server for that domain holds the DNS records (A records, CNAME, MX, etc.) and responds with the corresponding IP address. Key Points: Who can host it? Authoritative DNS servers are often hosted by domain registrars (e.g., GoDaddy, Namecheap) or cloud DNS providers (e.g., AWS Route 53, Cloudflare). However, organizations can also host their ...

BGP MED: Managing Inbound Traffic with Multi-Exit Discriminator

The Multi-Exit Discriminator (MED) is used in BGP to control inbound traffic into your AS. It tells a neighboring AS which entry point into your network it should prefer when there are multiple links between your AS and the neighboring AS. The lower the MED value , the more preferred the path. MED is only honored between the same neighboring AS . Example Scenario : You are connected to ISP1 via two routers, CE1 and CE2 , and want to control which router ISP1 uses to send traffic into your AS. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP1): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE1 (Lower MED, More Preferred) : Create a route map to set the MED to 50 for CE1: route-map SET_MED permit 10 set metric 50 Apply this route map to the neighbor in the BGP configuration for CE1: router bgp 65001 neighbor 10.0.1.1 remote-as 65000 neighbor 10.0.1.1 route-map SET_MED out Configuratio...