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

Upgrade NSX-T from the 2.1.0.0 to 2.2.0.0 failed,all the services are stopped (56837)

Last Updated: 10/6/2018Categories: Best PracticesTotal Views: 3485Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After upgrade NSX-T from the 2.1.0.0 to 2.2.0.0 unable to access NSX manager UI to manage the environment as all the services are stopped.
Issue can occurs if prior to upgrade:

IPFIX enabled with Switch IPFIX Profiles applied to SwitchPorts

One or more ports configured in the IPFIX profile got deleted prior to upgrade.

Cause

NSX manager upgrade process goes through 10 different steps and on each step a particular script to executed to perform certain tasks
Following are the steps:

- name: pre_upgrade_validation
- name: shutdown_manager
- name: install_os
- name: migrate_manager_config
- name: switch_os
- name: reboot
- name: run_migration_tool
- name: start_manager
- name: update_upgrade_status
- name: finish_upgrade

In the following example the "run_migration_tool" script failed with error and failure status can be seen in the syslog.
We can see following entry through syslog logs:

<182>1 2018-07-10T23:13:26.287757Z nsx-mgr-1 NSX 1725 - [nsx@6876 comp="nsx-manager" subcomp="nsx-opsagent" tid="1725" level="INFO" s2comp="framework"] [SupportBundle] ScheduleTimer after 5000000 microseconds
<182>1 2018-07-10T23:13:29.188772+00:00 nsx-mgr-1 NSX - - [nsx@6876 comp="nsx-manager" subcomp="upgrade-bundle"] upgrade_bundle_helper: Received command ['/opt/vmware/nsx-upgrade-agent/upgrade_bundle_helper.py', 'execute', '/var/vmware/nsx/file-store/VMware-NSX-unified-appliance-2.2.0.0.0.8680778.nub', 'upgrade_task_status', 'target_task_id=8c0323df-659a-499c-bdc5-6d1c4c62f500']
<5>1 2018-07-10T23:13:29.383865+00:00 nsx-mgr-1 kernel - - - [ 710.197597] grsec: From 10.60.12.159: denied RWX mmap of <anonymous mapping> by /usr/bin/python2.7[python:7704] uid/euid:0/0 gid/egid:0/0, parent /bin/bash[bash:7702] uid/euid:0/0 gid/egid:0/0
<182>1 2018-07-10T23:13:29.429492+00:00 nsx-mgr-1 NSX 7704 SYSTEM [nsx@6876 comp="nsx-manager" subcomp="upgrade-bundle" level="INFO"] Received command upgrade_task_status with args {'target_task_id': '8c0323df-659a-499c-bdc5-6d1c4c62f500'}

**************************************
<179>1 2018-07-10T23:13:29.485439+00:00 nsx-mgr-1 NSX 4601 - [nsx@6876 comp="nsx-cli" subcomp="node-mgmt" username="admin" level="ERROR" errorCode="('CLI10',)"] Upgrade step run_migration_tool completed with errors Script exited with non-zero return code 255.
****************************************

We can see following entry through data-migration logs:
var/log/data-migration-10-07-2018-23-08-19.log

2018-07-10 23:13:15.729 UTC INFO main IdentifierCleaningMigration:22 - - [nsx@6876 comp="nsx-manager" subcomp="manager"] Identifiers clean up is done
2018-07-10 23:13:15.729 UTC INFO main ProtonMigration:45 - - [nsx@6876 comp="nsx-manager" subcomp="manager"] Migration task: IdentifierCleaningMigration finished.
2018-07-10 23:13:15.732 UTC INFO main ProtonMigration:51 - - [nsx@6876 comp="nsx-manager" subcomp="manager"] Migration task: IpfixSwitchProfileModification begins.
2018-07-10 23:13:15.737 UTC INFO main IpfixSwitchProfileModification:60 - UPM [nsx@6876 comp="nsx-manager" subcomp="manager"] Found IpfixSwitchGlobalConfigModel :Ipfix configuration[id=IpfixSwitchGlobalConfigModel/4e5d3a8c-5be8-4df6-9a0f-b0458715b036, enabled=false, collectors=[Ipfix collector [collector_ip_address=10.60.254.187, collector_port=9996]], active_timeout=300, packet_sample_probability=0.1, max_flows=16384, observation_domain_id=0, idle_timeout=300]
2018-07-10 23:13:15.747 UTC INFO main IpfixSwitchProfileModification:184 - UPM [nsx@6876 comp="nsx-manager" subcomp="manager"] Created IPFIX Collector Profile :IpfixCollectorProfile{id=UpmProfile/8e01408a-6ab2-4e2d-83f8-102ae8211aa3, displayName=Switch IPFIX Collector Profile [Default], collectors=[IpfixCollector{ipAddress=10.60.254.187, port=9996}]}
2018-07-10 23:13:15.748 UTC INFO main IpfixSwitchProfileModification:77 - UPM [nsx@6876 comp="nsx-manager" subcomp="manager"] Got all identifiers:[IpfixConfigModel/09d79263-51c3-47c2-876c-31499dbde542]
Exception in thread "main" java.lang.NullPointerException
at com.vmware.nsx.management.container.aspects.TransactionAspect.completeTransactionAfterThrowing(TransactionAspect.java:106)
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:298)
at org.springframework.transaction.aspectj.AbstractTransactionAspect.ajc$around$org_springframework_transaction_aspectj_AbstractTransactionAspect$1$2a73e96c(AbstractTransactionAspect.aj:70)

In the above logs the null pointer exception happened while migrating the IPFIX profile.

Resolution

System can be recovered by rolling back to original version, once the roll back is complete remove IPFIX configuration, then start the upgrade from NSX manager CLI.

Rollback steps:

1. Roll back to the D-GO Build 2.1.0.0 using the following steps:

Step 1: start the Rollback
> set debug-mode
> rollback upgrade-bundle <bundle-name>
Step 2: Run finish_upgrade step to delete the extracted bundle
> set debug-mode
> start upgrade-bundle <bundle-name> step finish_upgrade

In case the services don't start after the rollback, there is possibility the partition switch didn't happen , this can happen if we try to manually upgrade again using the playbook after the first upgrade failure or any other manual steps has been executed.

Step 1: Check the following log for the last upgrade task execution:

var/log/upgrade/history_xx
{
"stdout": null,
"start_time": "2018-07-11 16:15:15.621023",
"args": {},
"pid": 14891,
"return_code": null,
"status_file": null,
"path": null,
"name": "rollback",
"task_id": "76f3cde7-83ae-42a8-a81c-56c7e313d1e8",
"failure_reason": null,
"state": "TASK_SUCCESS",
"end_time": "2018-07-11 16:16:09.711613",
"stderr": null
},

Step 2: Run systemctl get-default
The result would look like this:

multi-user.target ---->> is not set to "nsx-customer.target " execute the following 2 commands:

systemctl set-default nsx-custom.target

systemctl isolate nsx-custom.target &

2. Once the roll-back is complete, login to NSX manager and delete all the relevant IPFIX Switch Profile configuration.

Upgrade Steps:

Step 3: Extract bundle again
copy bundle to filestore again –
> copy url http://<mp-ip>:8080/repository/<to-version>/Manager/nub/<bundle-name>.nub
> verify upgrade-bundle <bundle-name>
> start upgrade-bundle <bundle-name> playbook VMware-NSX-Manager-<version>-playbook

*** Root-cause:-
If the Customer has IPFIX enabled with Switch IP FIX Profiles applied to SwitchPorts and prior to the upgrade, one or more ports got deleted, then during data migration task, you may see the
NullPointerException message due to the inconsistency.

Workaround

To avoid upgrade failure beforehand, verify the IPFIX configuration and ensure that there are no deleted switch-ports still configured in the "Switch IP FIX Profiles".
As an alternative, delete the "Switch IP FIX Profile " prior to upgrade.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

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

VMware NSX-T 1.0.x

VMware NSX-T

Take Our Survey

Support Assistant