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


Labels:

Comments

Post a Comment

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.
1 comment
Read more

BGP Soft Reconfiguration vs. Route Refresh: Key Differences and Best Practices

In BGP (Border Gateway Protocol), managing route updates and reapplying new policies can sometimes be challenging, especially if you want to avoid resetting the BGP session. Two methods allow you to update routing policies without tearing down the session: BGP Soft Reconfiguration and BGP Route Refresh . While both methods serve the same purpose, they work differently and have distinct impacts on your router's resources. This post explains the key differences between Soft Reconfiguration and Route Refresh , when to use each, and why Route Refresh is preferred in most modern networks. 1. What is BGP Soft Reconfiguration? BGP Soft Reconfiguration is an older method of applying new policies (like route maps, filters, or prefix lists) without resetting the BGP session. It works by storing a local copy of all the routes received from a BGP neighbor before applying inbound policies. This local route copy allows the router to reprocess the routes when a policy change occurs. How So...
Post a Comment
Read more

BGP Local Preference Controlling Outbound Traffic in BGP

In BGP, Local Preference is used to control the outbound traffic path. It helps you decide which egress point (exit point) should be used when you have multiple connections to external networks, such as ISPs. Local Preference is an attribute that is local to your AS and is shared with all iBGP peers but not with eBGP neighbors. Higher Local Preference = More preferred outbound path. Example Scenario : You have two external links: ISP1 (via CE1) and ISP2 (via CE2). You want traffic to prefer ISP1 for all outbound traffic. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP2): 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 (Higher Local Preference) : Create a route map to set the local preference to 200 for routes learned from CE1: route-map SET_LOCAL_PREF permit 10 set local-preference 200 In the BGP configuration for CE1, apply this route map to the neighbor: router bgp 65001 ne...
Post a Comment
Read more