Traffic Capture on Tier - O Getaway Uplink

Mar 01, 2023

This post will walk you through the steps needed to capture the incoming/outgoiing traffic on Tier0 gateway uplink level. The result will be a PCAP file that can be imported into a packet analyzer such as Wireshark for further troubleshooting and analysis.

Step 1: Collect ID of the Tier0 Uplink Interface

First you have to SSH to the NSX-T edge node running the active SR using admin credentials, then switch the context to the VRF corresponding to the Tier0 SR.

Now you are in the right context, you need to identify the ID of the Tier0 SR uplink interface.

The Tier0 SR uplink interface ID: 684b9ba1-c298-41cd-976f-8d5f91cabe4f

This is the interface where you will capture the incoming & outgoing traffic.

 

Step 2: Define and Start Capture Session

Next you need to define a new capture session, interface (the ID that we collected at step 1) and direction of traffic (dual means both incoming and outgoing traffic) that you want to trace. Note that before running the below command, you have to exit the VRF mode:

 

Let’s start the capture session now by capturing 50 packets and save them into a PCAP file:

The capture in done successfully. Let’s delete the capture session and make sure no capture sessions are running on the NSX-T edge node.

 

To check the current running capture sessions:

Let’s delete the capture session “1” that we created.

 

Step 3: Copy the PCAP file and analyze it

By default, the generated PCAP file will be stored in the following directory on the NSX-T edge node:

You can use WinSCP to connect to the edge node and copy the .pcap file to your machine.

Finally, you can open the pcap fil using WireShark and analyze it.  


12 Feb, 2024
Embracing Change with VMware vSphere Foundation
VMware by Broadcom Dramatically Simplifies Offer Lineup and Licensing Model
13 Dec, 2023
VMware by Broadcom Dramatically Simplifies Offer Lineup and Licensing Model
By Mohamad AlHussein 01 Mar, 2023
I came into a scenario recently where we need to decommission a cluster from a provider PVDC where that cluster also contains workloads already provisioned by the customer through the VCD tenant portal. In order to do so, we need to migrate a bunch of workloads for an organization from the orgVDC under workload cluster 1 knowing that both workload cluster 1 and cluster 2 are part of an elastic PVDC spanning both clusters. There may be other ways to do the migration but I want to share my simple procedure that I followed which may help others in case the hit the same use case. Always keep it simple!
More Posts
Share by: