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

NSX-T Data Center 2.x Error Codes (71077)

Last Updated: 1/6/2020Categories: InformationalTotal Views: 38618Language:
Chinese (Simplified)JapaneseEnglish

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Details

This article provides information on helping customers identify errors and provide recommended actions to correct the errors.

Solution

CCP Error Codes

CCP
Error Code

Code

Meaning

Recommended Action

CCP0110520

ALL_CONFIGURED_BROKERS_RETURNED_AUTHENTICATION_ERROR

The Controller could not connect to any broker.

Check CCP-MP connection status.

Verify the broker IPs and thumbprints in the broker file bootstrap.config.

CCP0110570

BOOTSRAP_FILE_DOES_NOT_CONTAIN_VALID_ACCOUNT_FIELD

No accounts present in the broker file.

Verify the contents of bootstrap.config for "account" field.

CCP0110590

BOOTSRAP_FILE_DOES_NOT_CONTAIN_VALID_BROKER_FIELD

Broker information not present in the broker file.

Verify the contents of bootstrap.config for "brokers" field.

CCP0110580

BOOTSRAP_FILE_DOES_NOT_CONTAIN_VALID_SECRET_FILED

Shared secret not present in the broker file.

Verify the contents of bootstrap.config for "secret" field.

CCP2010130

BROKER_CONFIG_FILE_IS_NOT_PROVIDED

Broker file is absent.

Check CCP-MP connection status.

Verify if bootstrap.config is present.

CCP0110610

BROKER_INDEXED_DOES_NOT_HAVE_A_VALID_HOST_FIELD

Broker file does not contain a valid IP address or FQDN for at least 1 broker.

Verify the contents of "brokers" field in bootstrap.config.

CCP0110620

BROKER_INDEXED_DOES_NOT_HAVE_A_VALID_PORT_FIELD

Broker file does not contain a valid port for at least 1 broker.

Verify the contents of "brokers" field in bootstrap.config.

CCP1910030

CANNOT_READ_CONTROLLER_VERSION_FROM_FILE

Failed to read/access the version file.

Verify that the version file /etc/nsx_issue exists.

CCP2010150

CONTROLLER_STARTUP_FAILED

The Controller Process Failed to Start.

Check the product logs.

CCP0110540

COULDNT_FIND_BOOTSTRAP_FILE

Broker file is absent.

Check CCP-MP connection status.

Verify if bootstrap.config is present.

CCP0110740

FAILED_TO_CONNECT_TO_BROKER

The controller could not connect to a broker.

Verify that bootstrap.config file is present.

Verify its contents.

CCP1910010

VERSION_FORMAT_IS_INVALID

Version file does not contain the version in the expected format.

Verify the controller version in /etc/nsx_issue. Expected format is
major.minor.maintenance.patch.suffix.build.

.

LCP Error Codes

LCP Error Code

Code

Meaning

Recommended Action

LCP00028

ERR_INVALID_NESTDB_MSG

Cfgagent receives invalid nestdb messages.

Need to check the nsx-nestdb daemon state.

LCP00001

ERR_INVALID_CONFIG

Cfgagent receives invalid configuration parameters.

Need to check what is the correct configuration and update in MP side.

LCP00021

ERR_MEMORY_ALLOC_FAILED

Cfgagent runs out of memory.

Need to check why the memory runs out.
Need to check whether it needs to enlarge the reserved memory size.

LCP00125

ERR_VMKLINK_SOCKET_RECV_FAILED

Failed to receive messages from vmklink socket.

Need to check whether the vmklink socket is closed. Try restarting cfgagent/rebooting host.

LCP00127

ERR_VMKLINK_SOCKET_DOWN

Vmklink socket is disconnected. The messages can’t be sent to vmklink socket.

Need to check whether the vmklink socket is closed. Try restaring cfgagent/rebooting host.

LCP00921

ERR_GET_MGMT_IP_FAIL

Failed to get management vmknic IP address.

Need to check whether management vmknic exists and has the correct IP setting.

LCP00703

ERR_CLI_BAD_PARAM_INPUT

Failed to execute the CLI command.

Need to check/validate CLI command parameter.

LCP00701

ERR_CLI_CREATE_SERVER_FAILED

Failed to create CLI socket server.

Need to check whether "/var/run/vmware/netcpa/cfgagent-cli" exists.

LCP00003

ERR_FILE_LOAD_FAILED

Cfgagent failed to load config file.

Need to check whether this file exists correctly. The file should be /etc/vmware/nsx/cfgAgent.xml.

MP Error Codes

MP Error Code

Code

Meaning

Recommended Action

[DHCP]MP22004

PROFILE_NOT_FOUND

DhcpProfile referenced by LogicalDhcpServer is not found.

Need to add existing DhcpProfile referenced by LogicalDhcpServer.

[DHCP]MP22009

IP_ASSIGNMENT_OVERLAPPS_INSIDE

IP overlapping within the ip-ranges of DhcpIpPool.

Reset IP that it doesn't be included in ip-ranges of DhcpIpPool.

[DHCP]MP22011

EDGE_CLUSTER_MEMBER_NOT_FOUND

EdgeCluster Member index is not found in EdgeCluster specified in DhcpProfile.

Check if the EdgeCluster member is existing in EdgeCluster.

[DHCP]MP22015

MIXED_IP_ADDRESS_TYPE_IN_SAME_POOL

Disallow to mix IPV4 address and IPV6 address in a same DhcpIpPool.

Only provide IPv4 address for DhcpIpPool.

[DHCP]MP22019

INVALID_ATTACHING_TO_LOGICAL_SWITCH_IN_DIFFERENT_TRANSPORT_ZONE

Invalid attaching. A LogicalDhcpServer needs to be attached to a LogicalSwitch in a same transport zone. The LogicalDhcpServer is in TransportZone(s), while the attach target LogicalSwitch is in a different TransportZone.

Attach the LogicalDhcpServer to a LogicalSwitch  in a same transport zone.

[DHCP]MP22027

DISALLOW_GATEWAY_OF_IP_ASSIGNMENT_BE_SAME_WITH_SERVER_IP

Disallow default gateway ip to be same with its dhcp server IP.

Provide the valid default gateway ip, and the ip cannot be dhcp server IP.

[DHCPRELAY]MP22301

DHCPRELAY_INVALID_SERVER_LIST

Invalid DHCP_RELAY profile. At least one server_address needs to be defined.

Provide the correct value for DHCP_RELAY profile that include server_address at least.

[DNSFORWARDER]MP23001

DISALLOW_GATEWAY_OF_IP_ASSIGNMENT_BE_SAME_WITH_SERVER_IP

The DnsForwarder's target logical router cannot be found.

Verify the logical router exists before creating the DnsForwarder.

[DNSFORWARDER]MP23002

LOGICAL_ROUTER_NOT_ACTIVE_STANDBY_HA

DnsForwarder cannot run on LogicalRouter which is in HA mode.

DnsForwarder can run only on Active/StandBy LogicalRouter.

[DNSFORWARDER]MP23005

LACK_OF_DOMAIN_NAME_IN_CONDITIONAL_FOWARDER_ZONE

Domain name is not provided in the ConditionalForwarderZone of DnsForwarder.

A domain name should be provided.

[DNSFORWARDER]MP23006

DISALLOW_MATCH_ALL_DOMAIN_NAME_IN_CONDITIONAL_FOWARDER_ZONE

Empty domain-name "" can appear in default forwarder.

A concrete domain name should be provided.

[DNSFORWARDER]MP23007

DUPLICATED_DOMAIN_NAME

Duplicated domain-name with the ConditionalForwarderZones of DnsForwarder.

Rename it to avoid duplication.

[DNSFORWARDER]MP23008

DUPLICATED_UPSTREAM_SERVER_IPS_AND_FORWARDER_SOURCE_IP

Duplicated ip address between the listener-ip and upstream DnsForwarder address.

Change the ip to another one without duplicated.

[DNSFORWARDER]MP23009

DNS_FORWARDER_COUNT_EXCEEDS_MAXIMUM

Count of DnsForwarder instances exceeds maximum number.

Need to delete some not used dns forwards.

[METADATAPROXY]MP22501

LACK_OF_SECRET

Secret of MetadataProxy is mandatory.

Provide the secret for the MetadatProxy.

[METADATAPROXY]MP22502

EDGE_CLUSTER_NOT_FOUND

EdgeCluster which is specified in MetadataProxy is not found.

Make sure the edge cluster existing.

[METADATAPROXY]MP22503

EDGE_CLUSTER_MEMBER_INDEX_NOT_FOUND

EdgeCluster member index is NOT found in EdgeCluster specified in MetadataProxy.

Check the member index of the edge cluster to make sure member existing.

[METADATAPROXY]MP22504

METADATA_PROXIES_EXCEEDS_MAXIMUM

MetadataProxies exceeds maximum number.

Delete the not used MetadataProxy.

[METADATAPROXY]MP22505

MALFORMED_SERVER_URL

Invalid server url.

Check the server url to make sure the url format is right.

[METADATAPROXY]MP22506

METADATA_SERVER_CA_ID_NOT_FOUND

CA with identifier is not found.

Check if the CA existing and change the CA id to the existed one.

[METADATAPROXY]MP22507

INVALID_ATTACHING_TO_LOGICAL_SWITCH_IN_DIFFERENT_TRANSPORT_ZONE

A MetadataProxy needs to be attached to a LogicalSwitch in a same transport zone.

Make sure the LogicalSwitch the MetadataProxy attachs to is in the same transport zone as the MetadataProxy.

[LOADBALANCER]MP23522

NO_CA_CERTS_IN_CLIENT_AUTH_REQUIRED_MODE

If client authentication is required, CA certificates to verify client certificate should be specified.

Make sure CA certificates are configured when LB needs to verify client certificate.

[LOADBALANCER]MP23523

NO_CA_CERTS_IN_SERVER_AUTH_REQUIRED_MODE

If server authentication is required, CA certificates to verify server certificate should be specified.

Make sure CA certificates are configured when LB needs to verify server certificate.

[LOADBALANCER]MP23607

INVALID_MEMBER_GROUP_PORT

Pool member group port should be null when virtual server is configured with multiple ports.

Make Sure pool member port is not configured for virtual server with multiple ports.

[LOADBALANCER]MP23722

SNAT_AND_POOL_MEMBER_IP_ADDRESSES_CONFLICTED

The same IP address can not be configured in both load balancer pool member and load balancer SNAT IP pool.

Make sure pool member and SNAT IP are the same.

[LOADBALANCER]MP23724

VIRTUAL_SERVERS_WITH_DIFF_PERSISTENCE_PROFILE_TYPES_SHARE_SAME_POOL

Load balancer virtual servers share the same pool but have different persistence settings.

When the pool is shared by multiple virtual servers, they should have the same persistence settings.

[LOADBALANCER]MP23908

COOKIE_PERSISTENCE_PROFILE_MODE_TYPE_AND_COOKIE_TIME_CONFLICT

If cookie persistence profile mode type is configured as prefix or rewrite, the cookie time should not be set.

Cookie expiry setting is only valid for cookie insert mode. Make sure the expiry time setting is removed for cookie prefix or rewrite modes.

[LOADBALANCER]MP23952

NO_CA_CERTS_IN_HTTPS_MONITOR_SERVER_AUTH_REQUIRED_MODE

If https monitor server authentication is required, CA certificates to verify server certificate should be specified.

Make sure CA certificates are configured when LB needs to verify server certificate.

[LOADBALANCER]MP24010

EMPTY_LB_RULE_ACTION_NOT_ALLOWED

At least 1 load balancer rule action should be specified.

For each LB rule, at least 1 rule action should be specified.

Edge Error Codes

Edge Error Code

Meaning

Recommended Action

EDG0400335 (NAT/FW)

Failed to realize edge FW/NAT config for logical router port.

Check the syslog on edge node to see what DP/CP error.

EDG0400448 (NAT/FW)

Mempool creation failed in DP.

DP runs out of memory, please check datapathd daemon memory.

EDG0400533 (NAT/FW)

Get VTI message for LR port which is not VTI type.

Check the configuration if LR port is configured as VTI type.

EDG0400537 (NAT/FW)

Failed to apply firewall .config to l2-bridge port

Check the syslog on edge node to see what DP/CP error.

EDG0200005 (Routing)

Connection with Edge-Agent went down.

Need to check the Edge-Agent status. Check the syslog to see the Edge-Agent (NSXA) errors.

EDG0200009 (Routing)

Failed to send FIB entries to Edge-Agent.

Check the syslog to look for either EDG020000011 or EDG02000008 error code.

EDG020000011, error sending message to local-controller (Edge-Agent). Restart the Routing Control Plane Manager (RCPM) service (service nsx-edge-rcpm restart)

EDG02000008, there is no connection between RCPM and local-controller (Edge-Agent). Verify the status of Edge-Agent.

EDG0200010 (Routing)

Mempool creation failed in Routing Control Plane Manager (RCPM).

Edge runs out of memory. Please check the edge node memory.

EDG0200028 (Routing)

Routing Control Plane Manager (RCPM) is not able to connect to the routing stack configurator.

Verify that the RCPM-PYTHON service is running. If not, start the service.

service nsx-edge-rcpm-python <status/start>

EDG0200030 (Routing)

Configuration are not applied to the routing stack (FRR).

Check the syslog to look for FRR errors. If daemon not found, try restarting the routing stack service.

nsd-cli service_frr restart

EDG0200032 (Routing)

No database exists for Routing Control Plane Manager (RCPM).

Check the nsx-nestdb in edge. If everything looks good, try restarting the RCPM service.

service nsx-edge-rcpm restart

EDG0200063 (Routing)

Failed to send message to DP.

Need to check the status of DataPath.

EDG0200064 (Routing)

No connection with DP.

Need to check the status of DataPath. Check the syslog to see the DP errors.

EDG0200067 (Routing)

Threads creation failed in Routing Control Plane Manager (RCPM).

Check the full message to find out which thread failed in the creation process. Try restarting the RCPM service.

service nsx-edge-rcpm restart

EDG0200093 (Routing)

Routing Control Plane Manager (RCPM) has lost connection with the routing stack (FRR).

Check the syslog to see the FRR errors.

CSM Error Codes

CSM Error Code

Meaning

Recommended Action

CSM60143

AWS allocate address api call failed, it might be due to limit exceeded on the number of EIPs that can be allocated.

Go to AWS portal and free up elastic IPs in that particular VPC.

CSM60254

Gateway role is incorrect.

Go to AWS portal , and change role of gateway instance to same as what is given while creating or updating AWS account in CSM.

CSM60197

Compute VPC is associated to hosted zone which does not have association with transit VPC.

Compute VPC is already associated to hosted zone which has association with some other transit VPC. Please delete this hosted zone entry and try compute VPC on-boarding again.

CSM60616

Resource group with name already exists, it needs to be cleaned up manually before starting gateway deployment or VNET on-boarding.

Go to Azure portal and manually delete resource group shown in error.

CSM60636

Failed to sync Azure Virtual Machines due to either read time out or internal error.

This error comes during account sync due to API throttling, wait for an hour. It will get resolve automatically.

CSM60665

Failed to sync Azure Network .Interfaces due to either read time out or internal error.

This error comes during account sync due to API throttling, wait for an hour. It will get resolve automatically.

CSM60666

Failed to sync Azure Networks due to either read time out or internal error.

This error comes during account sync due to API throttling, wait for an hour. It will get resolve automatically.

CSM60349

Gateway not reachable.

Check connectivity of Gateway from CSM If it is not reachable then please fix connectivity and re-deploy gateway.

CSM60641

VHD location is not valid.

Check VHD exists at given path, or simply copy VHD path from Azure portal and paste it in "VHD URL" field.

CSM60642

No gateway image URL found, which is compatible to current CSM version.

This error may come during copying gateway image, in that case please sync time on CSM with NTP.

CSM60336

Deleting cloud resources failed. Please manually delete them.

If CSM is not able to delete entities in cloud due to some reason, then please manually delete cloud entities created by CSM for that particular VNET.

PCG Error Codes

PCG
Error Code

Code

Meaning

Recommended Action

PCG51527

CLOUD_PLUGIN_GET_ACTIVITY_LOG_FAILED

Failed to get Azure activity log events.

Azure is throttling API requests from PCG

Check scale limits supported by NSX Cloud.

Verify the API usage of the other Azure api clients.

PCG51501

CLOUD_PLUGIN_INIT_FAILED

Failed to initialize cloud plugin.

Verify the gateway role has right permission.

Verify the role/region details for compute.

VPC/VNet boarding are correct.

PCG51446-51465

PROXY_*FAILED

Connection via Proxy has failed.

Verify that Proxy Profile configuration is correct on CSM UI.

PCG51426

PCM_AGENT_INSTALL_FAILED

Auto Install of NSX Tools on VM has failed.

Check VM agent logs and error codes for further details.

PCG50653

NAT_UNABLE_TO_RESERVE_IP

Unable to reserve Public IP tagged on VM.

Check the Public IP tagged on VM is not being used by any other VM/interfaces on Cloud UI.

PCG50536-50550

CLOUD_NW_RES*

Onboarding or Offboarding of compute has failed.

Check /var/log/pcm/pcm.log for actual error details.

To retry, manually cleanup of Policy as suggested in
documentation for failed onboarding/offboarding of PCGs.

PCG50501 - 50535

PCG50911

GW_ONBOARD_*

GW_OFFBOARD_*

Failed to onboard or offboard PCG.

Check /var/log/pcm/pcm.log for actual error details.

To redeploy PCG, manually cleanup of Policy as suggested in documentation for failed onboarding/offboarding of PCGs.

PCG50201 - 50300

PCG51300 - 51400

NSX_*_FAILED

API call to MP/Policy has failed.

Check the Policy cluster is functioning properly on Policy UI.

Verify that connectivity PCG and Policy (DNS name).

PCG50007

NSX_MANAGER_NOT_READY

NSX manager is not ready.

Check the Policy cluster is functioning properly on Policy UI.

Verify that connectivity between PCG and Policy(DNS name).

PCG50006

NESTDB_PLUGIN_FAILED

Failed to start NEST DB plugin.

Check scale limits supported by NSX Cloud.

Check cpu/memory usage on PCG.

Restarting PCM might help in reconnecting to Nestdb.

/etc/init.d/nsx-public-cloud-manager restart

PCG50002

GENERAL_ERROR

General Error has occurred.

Check /var/log/pcm/pcm.log|sys.log, for further details on unhandled AWS/Azure API failures.

PCG5052 - 50353

HA_STANDBY_TO_ACTIVE_FAILED

HA_ACTIVE_TO_STANDBY_FAILED

Failed to change gateway from standby to active.

Verify PublicIPs are properly assigned on the PCG on Cloud UI.

PCG (VM) Error Codes

VM Error Code(NA)

Code

Meaning

Recommended Action

Windows Installaltion Errors

Logs can be accessed C:\ProgramData\VMware\NSX\Logs\nsx-agent-bootstrap.log
C:\ProgramData\VMware\NSX\Logs\nsx_install.log

Failed to download http://<PCG IP>:8080/factory_default/windows/nsx-vm-agent-bundle.zip*
Could not resolve <PCG name> to its IP Address
Failed to install VMware-NSX-*_public-cloud_setup.exe

VM bundle could not downloaded from PCG
PCG name could not be resolved from VM
Agent installation failed.

Verify PCG name can be resolved. Verify if port 8080 is open.

Invalid operation
Unsupported OS version

An invalid operation specified while running VM installation script.

Please verify the installation commands from CSM agent install options. Check list of supported OS version.

Failed to set up nsx_bootstrap  task
Failed to set up nsx_watchdog task
Failed to find driver INF file:
Failed to install OVSIM driver

Template creation failed.
Agents crashed, would not be restarted.
Driver installation failed.
Driver installation failed.

Uninstall and Install agent with "noStart" option.
Uninstall and Install agent.

Linux Installation Errors

Logs can be accessed:
/var/log/vmware/nsx-agent/
/tmp/nsx-bundle-install.log

Failed to resolve: <PCG name>
Failed to download nsx files

PCG name could not be resolved from VM
VM bundle could not downloaded from PCG.

Verify PCG name can be resolved. Verify if port 8080 is open.

This script is not intended to run on your OS
NSX OVS package is not compatible with the linux kernel on this machine

Not supported OS version
NSX does not support this linux kernel.

Check list of supported platform, OS and linux kernel version.

SELinux is detected and enforcing. Please set it to Disabled or Permissive, aborting

Disabling SELinux

Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.

Failed to install
Installation failed!!!
Unable to get the interface id/mac from provider for <interface name>

Agent installation failed.
NSX packages could not be installed.
AWS metadata query failed, likely ec2service is not running.

Reboot, Uninstall and Install agent.

Install script failed to download linux-headers for OVS kernel module install

Failed to install linux headers.

Install missing header using the below command.
sudo apt-get install linux-headers-$(uname -r)

MP Error Codes

MP Error Code

Meaning

Recommended Action

MP7049

Cannot register compute manager, server thumbprint is blank or empty.

Note thumbprint from the error or the correct thumbprint and try to register the compute manager.

MP7061

Cannot register compute manager server , credentials are incorrect or invalid compute manager.

Verify Compute Manager ip/fqdn and credential and try to register with correct details.

MP7050

Cannot register compute manager. Server {0} already registered with NSX.

Remove the compute manager from the other NSX and attempt to register again.

MP26114

Auto install NSX not permitted.Hosts within cluster are scheduled/in-progress for NSX uninstall.

Wait for NSX uninstall on ESX hosts before Setting Auto Install.

MP26115

Auto uninstall NSX not permitted. Hosts within cluster have NSX install in-progress.

Wait for NSX install on ESX hosts before Setting Auto uninstall.

MP280

Application is not ready.

Wait for some time before attempting to make REST call so that all necessary services of nsx manager is up.

MP285

The object was modified by somebody else. Fetch the latest copy of the object and retry operation.

Make a Get call to get the latest copy of the object, and modify update payload to retry the update attempt.

MP401

User is not authorized to perform this operation on the application.

Check user's RBAC permission settting, modify it to assign correct permission before attempting the operation again.

MP402

This request is already in progress.

Current operation is already in progress. Let the current operation to be completed before retrying.

MP403

Invalid username/password combination.

Validate username and password before attempting again.

MP604

The object used in this operation has different version than the current system version. Fetch the latest copy of the object and retry operation.

Make a Get call to get the latest copy of the object, and modify update payload to retry the update attempt.

MP26119

Transport Node Profile is attached to any Compute Collection can not be deleted.

Detach the Transport node from the compute collection before attempting to delete.

MP26138

Invalid host state.

Reboot the host to reset invalid state.

MP3022

One or more relationships exist for object with id.

The object cannot be deleted as it is linked/used with different object.

MP4506

Invalid backup file format or wrong password.

Unable to restore the backup due to wrong password, provide the correct password and check if the backup file is not corrupted or invalid.

MP4505

ackup file version mismatch with system, cannot restore. System version: {0}, backup file version: {1}.

Need to restore on NSX manager which has same version has the backed up NSX.

MP4507

Need password to decrypt backup file.

Provice correct password while restoring the backup.

MP26140

Auto TN configuration failed for host {0}.

Check the configuration failure message for the particular host , and invoke Resolve to fix the issue.

MP9508

Physical NIC {0} was not found on the host.

Check if physical NIC added as uplink while adding a transport node exists.

MP9509

Physical NIC {0} is already in use on the host.

Check if physical NIC added as uplink while adding a transport node is already in use.

MP30023

Cannot modify upgrade plan, upgrade is in progress.

You can pause the upgrade or wait till upgrade is complete and then edit the upgrade plan.

MP30107

New NSX services did not come up on the host node.

Please check syslog and /var/log/upgrade.log logs on the host for troubleshooting.

MP30119

Host {0} needs to be put in maintenance mode before upgrade.

From vcenter webconsole put the esx in maintenance mode.

MP30166

In NSX 2.4, requirements for CPU and RAM have changed, Your NSX Manager is running with {0} CPUs and {1} GB of RAM.

Please increase the CPU & RAM count to mentioned baule in manual before upgrade.

MP3021

License key ending with {0} is expired ({1,date}).

Use a new unexpired license key.

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:

VMware NSX-T Data Center 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant