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 objects appear to be missing after proton or policy service restarts (76241)

Last Updated: 1/7/2022Categories: TroubleshootingTotal Views: 9556Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

NSX-T version is 2.4.x

NSX Manager logs (nsxapi.log, policy.log, syslog) display message(s) showing NSX Manager or Policy service restarted (either manually or automatically), similar to:

NSX Manager service automatic restart (nsxapi.log):
2019-11-06T09:34:44.749Z INFO CorfuDB-DCN-Publisher-0 ContainerConfigServiceImpl - - [nsx@6876 comp="nsx-manager" subcomp="manager"] Restart application now.

NSX Manager service manual restart (syslog):
<182>1 2020-01-06T10:09:11.599Z nsx-ctl-2-bb145 NSX 8973 - [nsx@6876 comp="nsx-cli" subcomp="node-mgmt" username="admin" level="INFO"] CMD: restart service manager

Policy service automatic restart (policy.log):
2019-12-02T09:42:05.777Z  INFO localhost-startStop-2 ContainerConfigServiceImpl - - [nsx@6876 comp="nsx-manager" subcomp="policy"] Out-of-bound lifecycle event received: Restart = true

Policy service manual restart (syslog):
<182>1 2020-01-07T10:38:03.664Z nsx-mngr-01 NSX 9481 - [nsx@6876 comp="nsx-cli" subcomp="node-mgmt" username="root" level="INFO"] CMD: restart service policy

NSX Manager logs (nsxapi.log or policy.log) display message(s) showing trimmed exception occurred while NSX Manager service is restarting, similar to:

2019-11-06T09:36:58.379Z  WARN pool-2-thread-1 FastObjectLoader - applyForEachAddress[171952709, start=171952684] address is trimmed
2019-11-06T09:36:58.387Z  WARN pool-2-thread-1 FastObjectLoader - applyForEachAddress[171952709, start=171957863] address is trimmed

NSX-T objects (NSGroup, Firewall sections and rules, Logical Switches, Logical Ports etc.) appear to be missing on the NSX Manager UI and API results:

GET /api/v1/ns-groups
GET /api/v1/firewall/sections/summary
GET /api/v1/logical-switches/status
GET /api/v1/logical-ports

NOTE: The objects missing dictate the impact this symptom carries.  Network traffic can be impacted if objects that traffic depends on are missing.

Cause

The issue is due to concurrent operations when the NSX Manager or Policy service restarts and while the restart is in progress Corfu performs routing trim and checkpoint operations.
When this happens, a Corfu trimmed exception occurs and the affected NSX Manager get presented with empty Corfu tables and the NSX-T objects appear missing.

Resolution

This issue is resolved in NSX-T 2.5.0.

Workaround

To workaround the issue, restart the NSX Manager or Policy service on the impacted NSX Manager(s).

1. Identify the impacted NSX Manager(s):
#grep "address is trimmed" /var/log/proton/nsxapi.log
#grep "address is trimmed" /var/log/policy/policy.log

Example of output:
2019-11-06T09:36:58.379Z  WARN pool-2-thread-1 FastObjectLoader - applyForEachAddress[171952709, start=171952684] address is trimmed
2019-11-06T09:36:58.387Z  WARN pool-2-thread-1 FastObjectLoader - applyForEachAddress[171952709, start=171957863] address is trimmed

2. Based on the result of step 1., restart the relevant NSX Manager service:
- If the "address is trimmed" error is found in nsxapi.log, restart the NSX Manager service:
#> restart service manager
- If the "address is trimmed" error is found in policy.log, restart the NSX Manager policy service:
#> restart service policy

3. Verify the object counts are as expected using REST API:
GET /api/v1/ns-groups
GET /api/v1/firewall/sections/summary
GET /api/v1/logical-switches/status
GET /api/v1/logical-ports

Note: the Corfu trimmed exception may occur after a manual restart of the NSX Manager or Policy services. Restart the service again if this happens.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

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

Take Our Survey

Support Assistant