Troubleshoot active NSX Controller connections
The first place to check when troubleshooting NSX Controller connections, is the vSphere Web Client. Log in and navigate to Networking & Security -> Installation -> Management and check the status of each of your controllers.
If everything looks good, log into one of your controllers via SSH, and run the following commands. Control cluster status will give you a cluster status, whether or not the node is joined, as well as the role and active status.
nvp-controller # show control-cluster status Type Status Since -------------------------------------------------------------------------------- Join status: Join complete 05/09 21:54:51 Majority status: Connected to cluster majority 05/16 21:34:49 Restart status: This controller can be safely restarted 05/16 21:34:38 Cluster ID: 3b488082-126c-470f-8d01-6069e308fb64 Node UUID: 3b488082-126c-470f-8d01-6069e308fb64 Role Configured status Active status -------------------------------------------------------------------------------- api_provider enabled activated persistence_server enabled activated switch_manager enabled activated logical_manager enabled activated directory_server enabled activated
To get a list of active connections, run the following command. From here you will be able to see the ports, as well as listening and open connections.
nvp-controller # show control-cluster connections
role port listening open conns
--------------------------------------------------------
api_provider api/443 Y 5
--------------------------------------------------------
persistence_server server/2878 Y 2
client/2888 Y 3
election/3888 Y 0
--------------------------------------------------------
switch_manager ovsmgmt/6632 Y 0
openflow/6633 Y 0
--------------------------------------------------------
system cluster/7777 Y 1
You can also check the statistics in regards to how many messages are received, dropped, or transmitted, as well as what connections are up, down, active, etc.
nvp-controller # show control-cluster core stats messages.received 793586 messages.received.dropped 0 messages.transmitted 794465 messages.transmit.dropped 0 messages.processing.dropped 0 connections.up 12 connections.down 6 connections.timeout 1 connections.active 6 connections.sharding.subscribed 3
Finally, you can get a list of the active connections by running the following command.
nvp-controller # show network connections of-type tcp Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:9998 0.0.0.0:* LISTEN 3420/domain tcp 0 0 0.0.0.0:36878 0.0.0.0:* LISTEN 3399/java tcp 0 0 0.0.0.0:9999 0.0.0.0:* LISTEN 3399/java tcp 0 0 0.0.0.0:3888 0.0.0.0:* LISTEN 3385/java tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN 3851/python tcp 0 0 0.0.0.0:30865 0.0.0.0:* LISTEN 2916/csync2 tcp 0 0 127.0.0.1:8081 0.0.0.0:* LISTEN 1066/python tcp 0 0 0.0.0.0:1234 0.0.0.0:* LISTEN 3399/java tcp 0 0 127.0.0.1:2003 0.0.0.0:* LISTEN 1128/python tcp 0 0 127.0.0.1:2004 0.0.0.0:* LISTEN 1128/python tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 3228/sshd tcp 0 0 127.0.0.1:9080 0.0.0.0:* LISTEN 3420/domain tcp 0 0 127.0.0.1:7002 0.0.0.0:* LISTEN 1128/python tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 3851/python tcp 0 0 0.0.0.0:43995 0.0.0.0:* LISTEN 3399/java tcp 0 0 127.0.0.1:2812 0.0.0.0:* LISTEN 932/monit tcp 0 0 0.0.0.0:2878 0.0.0.0:* LISTEN 3385/java tcp 0 0 192.168.110.201:7777 0.0.0.0:* LISTEN 3353/domain tcp 0 0 192.168.110.201:2888 0.0.0.0:* LISTEN 3385/java tcp 0 0 192.168.110.201:6632 0.0.0.0:* LISTEN 3353/domain tcp 0 0 192.168.110.201:6633 0.0.0.0:* LISTEN 3353/domain tcp 0 0 192.168.110.201:443 192.168.110.42:57431 ESTABLISHED 3851/python tcp 0 0 127.0.0.1:40515 127.0.0.1:9080 TIME_WAIT - tcp 0 0 192.168.110.201:2888 192.168.110.203:50384 ESTABLISHED 3385/java tcp 0 0 192.168.110.201:1234 192.168.210.51:51180 ESTABLISHED 3399/java tcp 1 0 127.0.0.1:56553 127.0.0.1:9080 CLOSE_WAIT 3851/python tcp 0 3700 192.168.110.201:22 192.168.110.10:61759 ESTABLISHED 6581/sshd: admin [p tcp 0 0 192.168.110.201:1234 192.168.210.52:44734 ESTABLISHED 3399/java tcp 0 0 127.0.0.1:39457 127.0.0.1:9080 ESTABLISHED 3851/python tcp 0 0 192.168.110.201:443 192.168.110.42:42169 ESTABLISHED 3851/python tcp 0 0 127.0.0.1:40516 127.0.0.1:9080 TIME_WAIT - tcp 0 0 192.168.110.201:2888 192.168.110.202:58145 ESTABLISHED 3385/java tcp 0 0 192.168.110.201:39300 192.168.110.201:2888 ESTABLISHED 3353/domain tcp 0 0 192.168.110.201:443 192.168.110.42:48901 ESTABLISHED 3851/python tcp 0 0 127.0.0.1:9080 127.0.0.1:39457 ESTABLISHED 3420/domain tcp 0 0 192.168.110.201:1234 192.168.110.52:52475 ESTABLISHED 3399/java tcp 0 0 192.168.110.201:443 192.168.110.42:51008 ESTABLISHED 3851/python tcp 0 0 192.168.110.201:2878 192.168.110.203:45382 ESTABLISHED 3385/java tcp 1 0 127.0.0.1:37464 127.0.0.1:9080 CLOSE_WAIT 3851/python tcp 0 0 192.168.110.201:1234 192.168.110.51:14606 ESTABLISHED 3399/java tcp 0 0 127.0.0.1:40517 127.0.0.1:9080 TIME_WAIT - tcp 0 0 192.168.110.201:32913 192.168.110.203:3888 ESTABLISHED 3385/java tcp 0 0 192.168.110.201:54429 192.168.110.202:7777 ESTABLISHED 3353/domain tcp 0 0 192.168.110.201:7777 192.168.110.203:46751 ESTABLISHED 3353/domain tcp 0 0 192.168.110.201:2888 192.168.110.201:39300 ESTABLISHED 3385/java tcp 0 0 192.168.110.201:1234 192.168.210.57:61458 ESTABLISHED 3399/java tcp 0 0 127.0.0.1:40518 127.0.0.1:9080 TIME_WAIT - tcp 0 0 127.0.0.1:40514 127.0.0.1:9080 TIME_WAIT - tcp 0 0 192.168.110.201:1234 192.168.210.56:59173 ESTABLISHED 3399/java tcp 0 0 192.168.110.201:37645 192.168.110.202:3888 ESTABLISHED 3385/java tcp 1 0 127.0.0.1:56548 127.0.0.1:9080 CLOSE_WAIT 3851/python tcp 0 0 192.168.110.201:2878 192.168.110.202:49314 ESTABLISHED 3385/java tcp 0 0 192.168.110.201:443 192.168.110.42:60123 ESTABLISHED 3851/python tcp 1 0 127.0.0.1:44379 127.0.0.1:9080 CLOSE_WAIT 3851/python tcp6 0 0 :::22 :::* LISTEN 3228/sshd
Leave A Comment