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

Upgrading NSX-T manager from 2.1.0.0 to 2.2.0.0 reports "General Error has occurred" on Firewall's General UI section. (56611)

Last Updated: 7/12/2018Categories: How toTotal Views: 3389Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

It has been observed that after upgrading NSX manager (proton) from 2.1.0.0 (NSX-T DGo) to 2.2.0.0 (NSX-T Equinox), all firewall section (layer3 and layer 2) were not displayed on UI and in listSections API response.
Apparently, UI and API reports "General Error has occurred" on Firewall's General or Ethernet tabs and/or JSON response with a NullPointerException in NSX manager logs (nsxapi.log) in listSections API workflow.

Cause

The NSX-T DFW allows the consumption of group references (like NSGroups, Logical Switches, IP Sets, ect.) as sources, destinations, and the appliedTo field.
When a firewall rule is created using these group references, DFW validates the existence of these entities. However, the DFW does not manage any future changes or updates made to the referenced object. Thus, if a user deletes a referenced entity after rule creation, then the firewall rule will contain a stale reference.

During an upgrade of NSX, the DFW re-validates the existence of these group references. This attempt to revalidate the logical objects of the DFW results in the error: "General Error has occurred."

Resolution

There are couple ways customer can migrate firewall entities from 2.1 (DGo) to 2.2 (EQ) without experiencing above issue.
Please refer to workaround section.

Workaround

There are couple ways customer can migrate firewall entities from 2.1 (DGo) to 2.2 (EQ) without experiencing above issue:

In NSX-T  2.1:
User can invoke listSections API (sample below) before upgrading NSX Manager and look for firewall sections consuming invalid references ("is_valid" : false) in JSON API response. Then, perform one of the following operations best suited to keep his/her security posture unscathed:

Delete Firewall Section (along with rules) which has all references in appliedTos as invalid.

Or Update Firewall Section to sanitize appliedTo list to contain only valid references (Note: Emptying appliedTo essentially mean applied to ALL)

API Sample:
GET  /api/v1/firewall/sections?type=[LAYER3|LAYER2]

{

"cursor": "003616a93c39-5822-469e-b0be-70728153642eFirewallSection",
"sort_by": "position",
"result_count": 2,
"results": [
{
"resource_type": "FirewallSection",
"description": "protects app VMs",
"id": "65a60890-6f48-418d-a7d5-5aaf65fc4e5b",
"display_name": "app-firewall",
"section_type": "LAYER3",
"applied_tos": [
{
"target_display_name": "app-switch-port",
"is_valid": false,
"target_type": "LogicalPort",
"target_id": "1d9fb5cb-0344-4d7f-899a-afd93276899f"
}
],
"is_default": false,
"stateful": true,
"rule_count": 0,
"locked": true,
"comments": "Locked the section",
"lock_modified_by": "admin",
"lock_modified_time": "14458940331000",
"_last_modified_user": "admin",
"_system_owned": false,
"_last_modified_time": 1445894033107,
"_create_user": "admin",
"_create_time": 1445894033107,
"_revision": 0
}
]
}

In NSX-T 2.2:

If NSX is already upgraded to Equinox (2.2) and you have encountered this issue, then a jar file patch can be applied on NSX-T manager. Once the patch is applied, reboot the manager, and DFW objects and UI should come up properly.
Please open a case with VMware support to acquire the jar file patch.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

nsx-firewall-1.0.jar

Additional Resources

No results for undefined

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 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant