Sign up for the quarterly Flings Newsletter here!

Log In

Extensible Debugging Tool for EPSec and NetX

Communities:

Summary

Requirements

Instructions

Comments 0

Bugs 0

One of the features in NSX manager is the Service-Insertion platform, where partners can integrate their services with NSX manager. The two main programs that support service-insertion are - EPSec and NetX. In addition to vCenter and NSX Manager, EPSec has the MUX component (running as a userworld process on ESXi host) and thin-agents (running on the guest VMs – Linux and Windows). The main components of the NetX service include vsip (kernel module in ESXi hosts), vsfwd and netcpa (user-world processes on ESXi hosts). This Fling will help VMware partners, customers and developers to troubleshoot EPSec/NetX programs which integrate multiple components and subcomponents, where each of these components serves specific functionalities. This tool will help debugging issues by extracting only the relevant information from the product on a per-component level. This tool fetches required debugging information across modules, then validates the extracted information, and finally helps to correct invalid configurations. This would minimize the effort and time cost required from the partner in gathering the required information from the product and its components. The following scripts are part of this tool:
  • To extract version/build number of MUX, NSX vibs
  • To extract vCenter virtual appliance version info
  • To extract NSX Manager version info
  • To extract protected VM version info like thin agent, vsepd status
  • To extract EPSec library version
  • To extract Windows thin agent build/version info from Windows(PVM)
  • To extract Linux thin agent logs for troubleshooting
  • To extract logs from ESXi host for troubleshooting
  • Automatically discover vCenter, NSX Manager, PVM (Windows, Linux), SVM IPs
  • To check if vCenter, vSM, PVM (Windows) and PVM (Linux) are in the same network
screenshot_NSXDebug
  • VCVA 5.5 or later
  • NSX Manager 5.5 or later
  • ESXi host 5.5 or later
  • Linux thin agent (SLES11, SLES12, RHEL7)
  • Windows thin agent
    (Windows Vista (32 bit),Windows 7 (32/64 bit),Windows XP SP3 or higher (32 bit),Windows 2003 SP2 or higher (32/64 bit), Windows 2003 R2 (32/64 bit), Windows 2008 (32/64 bit), Windows 2008 R2 (64 bit),Windows 2012 (64 bit) ‐ only with vSphere 5.5; ReFS is not supported, Windows 2012 R2 ‐ only with vSphere 5.5; ReFS is not supported, Windows 8, and 8.1)

The Fling code is located here: https://git.eng.vmware.com/gitweb/repos/private/rbiswal/NSXDebug/
-Copy the files into a Linux machine such as PMC (Partner Management Console) or any Linux VM on the same network as the partner’s SVM or PMC
- Run the NSX_Debug.sh script with required options as below:
# ./NSX_Debug.sh -h
-H {To print MUX build, NSX vibs, checking status on vsip,vsfwd,netcpa, etc.}
-v { To print vCenter version info }
-V { To print NSX manager version info }
-G {Extract Protected VM version infos like thinAgent, OS, vsepd status, etc.}
-l {To print EPSec library version}
-w {Extract Windows thin agent build/version info from Windows (PVM)}
-t {To extract logs from ESxi host for troubleshooting}
-S <PVM(Linux) IP> {To extract Linux thin agent logs for troubleshooting}
-s -A {Automatically discover vCenter, NSX Manager, PVM (Windows,Linux), SVM IPs}
-N {Check to make sure that all the components such as vCenter, vSM, PVM (Windows), PVM(Linux) are in the same network}
-M {Prints the network info of the Linux VM where NSX_Debug.h script is running}

Report a Bug