NSX-T

AUST IT Information Technology for everyone

NSX-T randomly stopped services

Then start the SSH service manually:

start service ssh
NSX-T Password expired issue

Just recently connected to my test NSX-T environment and found that my password is espired.

Actually it is admin credentials. See picture below:

Fix is eazy, just SSH to the host and update the admin passwrd.

You are required to change your password immediately (password aged)
WARNING: Your password has expired.
You must change your password now and login again!
Changing password for admin.
(current) UNIX password:

New password:
Retype new password:

After updating the password over CLI, you can successfuly login over UI.

Password expiration is 90 days by default.

To avoind this issue in the future we can extend expiration dates using next command:

set user admin password-expiration 9999

To check the expiration date:
get user admin password-expiration

Thu Nov 09 2021 UTC 00:36:18.240
Password expires 9970 days after last change. Current password will expire in 9970 days.
NSX-V to NSX-T Migration: universal objects

We are planning to process with NSX to vSphere to NSX-T migration.

This article will be focused on multisite implementation.

If you have Standalone NSX-V implemetation, this article is not for you.

We have two site NSX-V (Cross-vCenters). Unfortunately, when we try to test the migtarion using the migration coordinator, we stuck solution it fails as it is not a supported connection.

It is related to universal objects that not able to be migrated due to miltisite implementation.

Migration of a true Cross-vCenter NSX for vSphere deployment with a primary NSX Manager and multiple secondary NSX Managers is not supported yet. However, if either the primary or secondary NSX Manager is set to a standalone or transit mode, the migration is supported.

We had further issue once we set the site as standalone, and had some issues with universal objects.

Fortunately for us, starting in NSX-T 3.1.1, migration of a single universal objects on the primary site, is supported.

Hope it helps.
NSX-T issue: Some appliance components are not functioning properly

One of the NSX-T nodes reporting "Some appliance components are not functioning properly" and web page is down.

Also could be some errors on the screen like:

Component health: SEARCH:UP, POLICY:UP, MANAGER:UNKNOWN, UI:UP, NODE_MGMT:UP.
Error code: 101

First, CLI to the applience and check if next services status:

get service

If manager services for example is down tray to start it manually and if it fails check errors for manager.log using this command:
get log-file manager.log

Assuming reboot alredy was in place.

If you need to detuch manangement plane:

For NSX-T 2.3 the command it:

detach management-plane

For NSX-T 3.0 it involes:

del nsx
NSX-T node deployment stuck in "Waiting To Register Host"

During the auto deployment installation of additional NSX node using User Interface (UI), the NSX Node displays a status of "Waiting to Register VM" indefinitely.

Issues could be differet and must be checked case by case.

Workaround is do delete the node with issues over API.

First check all your deployments and grab vm_id.

Delete the node using next command:

https://10.3.60.179/api/v1/cluster/nodes/deployments/86f643e9-e722-451b-be68-9a9f08d0b5b7?action=delete

Bonus:

Issue with the deloyment in my case was laydown in NFS storage. Simly moving the delpoyment VM target to anither type of storage, solved issue.

Google AdSence

AUST IT - Computer help out of hours, when you need it most.

Find out why we do it for less.

About

AUST IT will help you resolve any technical support issues you are facing onsite or remotely via remote desktop 24/7. More...

Contacts

Reservoir, Melbourne,
3073, VIC, Australia

Phone: 0422 348 882

This email address is being protected from spambots. You need JavaScript enabled to view it.

Sydney: 0481 837 077

Connect

Join us in social networks to be in touch.

Newsletter