"Fail to communicate with nsx-ccp service" error observed when running "get logical-switches"

Products

• VMware NSX

Issue/Introduction

• You are running VMware NSX 4.1.2.5 or earlier.
• When executing the get logical-switches command on any of the NSX-T controller nodes, the following error is observed:

nsxt-03> get logical-switches

Fri Apr 18 2025 UTC 11:50:39.645

% Fail to communicate with nsx-ccp service.

nsxt-03>

• This occurs despite all controller nodes being reported as healthy and no active alarms in the system.
• This issue does not impact production environments or network functionality. The issue is isolated to the manager CLI's ability to display the output correctly.
• Additionally, the NSX Manager /var/log/syslog logs the following error:

NSX 4932 - [nsx@6876 comp="nsx-manager" subcomp="cli" username="admin" level="ERROR" errorCode="NOD101"] exception: 'utf-8' codec can't decode byte 0xf3 in position 70689: invalid continuation byte#012Traceback (most recent call last):#012  File "/opt/vmware/nsx-node-api/bin/python/management_api/napi/root/administration/support_bundles/controller_util.py", line 165, in get_table_from_jmx_json_output_with_header#012 "false", parameters)#012  File "/opt/vmware/ccp/bin/python/nsx_cli/cli_utils.py", line 82, in get_json_jmx_response#012    result = simplejson.loads(response)#012  File "/usr/lib/python3/dist-packages/simplejson/__init__.py", line 518, in loads#012    return _default_decoder.decode(s)#012  File "/usr/lib/python3/dist-packages/simplejson/decoder.py", line 369, in decode#012    s = s.decode(self.encoding)#012UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf3 in position 70689: invalid continuation byte

NSX 4932 - [nsx@6876 comp="nsx-manager" subcomp="cli" username="admin" level="WARNING"] Fail to communicate with nsx-ccp service.

NSX 4932 - [nsx@6876 comp="nsx-manager" subcomp="cli" username="admin" level="INFO" audit="true"] CMD: get logical-switches (duration: 1.545s), Operation status: CMD_EXECUTED_WITH_ERROR_RESULT

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware NSX

VMware NSX-T Data Center

Cause

This issue occurs due to the presence of a special character in the name of one or more Logical Switches (Segments). The NSX Manager is unable to decode the character when processing the logical switch data, resulting in a failure of the nsx-ccp service interaction.

Special Character Examples: À, á, â, ç, ê, É, È, Ì, î, í, Ò, ô, ó, Ù, ú

Resolution

This issue has been fixed in NSX Manager version 4.2.1.0. To avoid encountering this problem in the future, upgrade to NSX 4.2.1.0 or a later version.

To workaround this issue:

1. Identify the Logical Switch/Segment that contains a special character in its name.
2. Rename the Logical Switch/Segment, removing or replacing any special characters with standard alphanumeric characters or supported symbols.
3. Re-run the get logical-switches command to confirm the issue is resolved.