Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Commandline migration of vmk0 from NVDS to vSS in an NSX-T environment (71080)

Last Updated: 8/18/2022Categories: InformationalTotal Views: 23812Language:
Chinese (Simplified)JapaneseEnglish

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Details

This article provides step to migrate the VMkernel interface that is used for management traffic from NVDS to vSS in an NSX-T environment.
This procedure is intended for a scenario where the ESXi host has lost management network connectivity and commandline recovery to vSS is required.

Note: In VSAN environments extra care should be taken to ensure that there is no additional disruption to the VSAN vmkernel network. If in doubt please open a Support Request with VMware GSS to get assistance with this activity.

Solution

NSX-T Data Center environments earlier than 2.4.2

Sample output has been edited to show only output of relevance to the procedure

Gather information on the NICs attached to the NVDS

# nsxdp-cli vswitch instance list
Client                         PortID          DVPortID                             MAC                  Uplink
vmnic0                         67108866        uplink-1                             00:00:00:00:00:00
vmnic1                         67108872        uplink-2                             00:00:00:00:00:00

# net-stats -l
PortNum          Type SubType SwitchName       MACAddress         ClientName
67108866            4       0 DvsPortset-0     b4:96:91:43:f5:d0  vmnic0
67108873            4       0 DvsPortset-0     a4:bf:01:58:61:af  vmnic1

Remove NIC(s) from NVDS
# esxcfg-vswitch -Q vmnic0 -V uplink-1 DvsPortset-0
# esxcfg-vswitch -Q vmnic1 -V uplink-2 DvsPortset-0

Create a vSS
# esxcfg-vswitch -a vSwitch0

Add the NIC(s)
# esxcfg-vswitch -L vmnic0 vSwitch0
# esxcfg-vswitch -L vmnic1 vSwitch0

Create a portgroup
# esxcfg-vswitch -A mgmt vSwitch0

Delete vmk0 from the NVDS
# esxcli network ip interface remove –-interface-name=vmk0

Add vmk0 to vSS
# esxcfg-vmknic -a -i <IP address> -n <netmask> -p mgmt
# esxcfg-vswitch -v <mgmt VLAN ID> -p mgmt vSwitch0

Add the default GW
# esxcfg-route -a default <GW IP address>

At this point the ESXi host should have management connectivity restored and should reconnect back to vCenter.
Further configuration changes can then be made via the vSphere Client.

NSX-T Datacenter environments 2.4.2/2.5.0 and above

NSX-T Data Center 2.4.2 and 2.5.0 introduced a script to simplify the recovery procedure

Create a vSS
# esxcfg-vswitch -a vSwitch0

Create a Management portgroup
# esxcfg-vswitch -A "Management Network" vSwitch0

Migrate vmkernel and vmnic from NVDS to vSS
#/usr/lib64/vmware/nsx-opsagent/bin/nsxcfg-vswitch -m -p "Management Network" -I vmk0 -P vmnic0

At this point the ESXi host should have management connectivity restored and should reconnect back to vCenter.
Further configuration changes can then be made via the vSphere Client.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
将 CA 签名的 SSL 证书应用于嵌入式 Orchestrator 端口 8283 (71060)

KB
•
移除智能卡时在 Ubuntu 18.4、16.4、SLED12SP3、SLES12SP3 和 SLED11SP4 上自动锁定屏幕 (71068)

KB
•
在启用了 UAC 的 Windows 上无法安装 vRealize Operations Manager 7.5 Telegraf 代理 (70780)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant