Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

NSX-T NCP troubleshooting and debug logging (67651)

Last Updated: 9/3/2019Categories: TroubleshootingTotal Views: 10566Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

NCP troubleshooting steps and enable debug logging

Purpose

This KB article describes NCP troubleshooting steps and how to enable debug logging

Resolution

For PKS setup , NCP runs as a service, hence login PKS master node
steps can be found in https://kb.vmware.com/s/article/67648

If NCP runs as a POD such as openshift setup, SSH into the NCP pod

#oc project nsx-system

# oc get pods

NAME                   READY     STATUS    RESTARTS   AGE

nsx-ncp-snn56          1/1       Running   1          3d

nsx-node-agent-fk9xl   2/2       Running   331        3d

nsx-node-agent-lzxmn   2/2       Running   8          3d

nsx-node-agent-smjlw   2/2       Running   8          3d

nsx-node-agent-tgj8m   2/2       Running   18         3d

nsx-node-agent-w9dsr   2/2       Running   1444       3d

nsx-node-agent-zb4h6   2/2       Running   20         3d

#kubectl exec -it nsx-ncp-snn56 -- /bin/bash

Collect NCP logs from Bosh / OC / Kubectl

#bosh logs -d [service-instance_uuid]

#oc logs [ncp-pod-name]

#kubectl logs [ncp-pod-name]

NCP configuration file (ncp.ini) in PKS

ncp.ini located under /var/vcap/jobs/ncp/config
settings can be adjusted .

content looks like this:

[DEFAULT]
use_stderr = False

[coe]
enable_snat = true
cluster = pks-60c7bef1-a796-4276-8001-cfa0aca85707

[ha]
enable = True
[k8s]

apiserver_host_ip = master.cfcr.internal
apiserver_host_port = 8443
ca_file = /etc/nsx-ujo/certs/k8s/ca.crt
client_cert_file = /etc/nsx-ujo/certs/k8s/client.crt
client_private_key_file = /etc/nsx-ujo/certs/k8s/client.key
ingress_mode = nat
...

In PKS master node root mode or NCP pod , execute nsxcli
nsxcli command path may different in various setup

I.E. in PKS
# /var/vcap/data/jobs/ncp/45626f1c68983490975053434143ed2eff8b138b/bin/nsxcli

81b91b91-3001-45cb-8ec3-c035e70b118f> get version
2.3.1

81b91b91-3001-45cb-8ec3-c035e70b118f> get ncp-nsx status
NSX Manager status: Healthy

81b91b91-3001-45cb-8ec3-c035e70b118f> get ncp-master status
This instance is the NCP master
Current NCP Master id is c9a754fc-c3f4-4957-b140-3ad238b7160b
Current NCP Instance id is c9a754fc-c3f4-4957-b140-3ad238b7160b
Last master update at Mon Apr  1 20:11:46 2019

81b91b91-3001-45cb-8ec3-c035e70b118f> get ncp-k8s-api-server status
Kubernetes ApiServer status: Healthy

To Debug NCP , change logging level from Info to Debug

81b91b91-3001-45cb-8ec3-c035e70b118f> set ncp-log-level DEBUG
NCP log level is changed to DEBUG

To Stop /Start / restart NCP in PKS master node

# monit restart ncp
# monit stop ncp
# monit start ncp

To disable NCP HA
change ncp.ini and restart ncp
[ha]
enable = True to  False

To change NCP HA HB and timeout timer
By default below values are hardcoded with default values, If we need change these timers then add below parameters and restart ncp.

ncp.ha.master_timeout = 9
ncp.ha.heartbeat_period = 3

[ha]
master_timeout = 18
heartbeat_period = 6
update_timeout = 6

verify if the ncp is running on the master node
#monit summary | grep ncp

Also check Hyperbus status on ESXi host

vESXi-1.nsx-lab.local> get hyperbus connection info
VIFID                            Connection                         Status
acbffb45-c762-4dd6-8c6e-6fa8584f74af         169.254.1.10:2345                     HEALTHY

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
古いメタデータ ソリューションから新しい Edge クラスタ ソリューションへの移行 (67554)

KB
•
裸机服务器支持对 NSX-T 中的传输节点配置使用 OVS 绑定 (67835)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center

Take Our Survey

Support Assistant