Edge node vmid not found on NSX manager

-


 

Hello There,

Recently , we faced an issue in our NSX-T envrironment running with 3.2.x version.

We saw below error message while running the pre-check for NSX upgrade to 4.x version. 

"Edge node 31c2a0ba-e10a-48eb-940d-85f1e48c811f vmId is not found on NSX manager"




So to fix this vmId issue for Edge Nodes, we need to edit the DeploymentUnitInstance and EdgeNodeExternalConfig in NSX Corfu DB tables.

Steps to be done:

1) Login to NSX Manager UI . Start a backup by going to the NSX Manager UI System > Lifecycle Management > Backup and Restore and click on the START BACKUP button.


2) Log into any of NSX Manager node's CLI using the admin and switch to root account and stop the corfu service using the following command:

   /etc/init.d/corfu-server stop

3) Stop the proton service

   /etc/init.d/proton stop

4) Start the corfu service

   /etc/init.d/corfu-server start

5) Execute the following DB commands to make the changes in DeploymentUnitInstance and EdgeNodeExternalConfig tables on the Corfu DB one by one.  


First run the below command to udpate the DeploymentUnitInstance table in corfu DB.

corfu_tool_runner.py -t DeploymentUnitInstance -n nsx -o editTable --keyToEdit '{"uuid": { "left": "12448448404996573115", "right": "10430903042528069173" } }' --newRecord '{"managedResource":{"displayName":"acc1c5de-a099-47bb-90c2-030d486d4635"},"deploymentUnitId":{"uuid":{"left":"4178938188179001301","right":"9995961568062954963"} },"deploymentProgressState":"DEPLOYMENT_PROGRESS_STATE_DEPLOYMENT_SUCCESSFUL","deploymentGoalState":"DEPLOYMENT_GOAL_STATE_ENABLED","runningVersion":"2.5.1.0.0.15314297","errorMessage":"","entityId":vm-654, "uniqueVmExternalId":5015a23f-8cf3-e793-f662-ccb098105a98, "vcDeploymentConfig":{"baseDeploymentConfiguration":{"name":"nsxedg001","computeManagerId":"3070d243-6fae-4487-8e38-4262b9c11785"},"dataStore":"datastore-76","cluster":"domain-c47","memoryReservation":-1,"cpuReservation":-1,"cpuShares":-1,"hostId":"host-106"} }'


Now, run the below command to udpate the EdgeNodeExternalConfig table in corfu DB.


/opt/vmware/bin/corfu_tool_runner.py -t EdgeNodeExternalConfig -n nsx -o editTable --keyToEdit '{"stringId": "/infra/sites/default/enforcement-points/default/edge-transport-node/db86d51c-1a54-408c-9ad0-415613bfd2b1"}' --newRecord '{"managementIp":[{"ipAddress":[{"ipv4":169673490}],"prefixLength":24}],"vmId":{"stringId":"5015a23f-8cf3-e793-f662-ccb098105a98"},"deploymentType":"VIRTUAL_MACHINE","cpu":4,"memory":7962812,"hypervisor":"VMware","managementInterface":"eth0","maintenanceMode":"MAINTENANCE_MODE_DISABLED","searchString":"biosUuid:42153f0f-4783-cc05-1161-f2da9c30c578;macAddress:00:50:56:95:bd:59","pnic":[{"name":"fp-eth2","mac":"00:50:56:95:1d:6f"},{"name":"fp-eth1","mac":"00:50:56:95:5f:ee"},{"name":"fp-eth0","mac":"00:50:56:95:2a:ff"}],"prevPnic":[{"name":"fp-eth2","mac":"00:50:56:95:1d:6f"},{"name":"fp-eth1","mac":"00:50:56:95:5f:ee"},{"name":"fp-eth0","mac":"00:50:56:95:2a:ff"}],"enableSsh":true,"hostname":"nsxedg001.abc.com","ntpServer":["10.89.50.151","10.89.50.102"],"dnsServer":["10.90.22.151","10.90.22.102"],"qatConfig":{"isVm":true,"fipsCompliant":true},"syslogServer":[{"server":"10.35.1.110","port":514,"protocol":"SYSLOG_PROTOCOL_ENUM_UDP","logLevel":"SYSLOG_LEVEL_ENUM_INFO"}]}'


Please note: Please change the details in above commands as per your environment and Node details.


Once the abpve stpes competed successfully, please re-run the pre-checks and vmId warning should be fix. If not then, reboot the NSX managers one by one and then re-run the pre-checks and see.


Note:- the above procedure is critical as we are making the changes in corfu DB. Please take help from VMware support if you are not 100% confident and sure to do this.












Comments

Post a Comment

Popular posts from this blog

How to migrate the N-VDS as the host switch to VDS 7.0 in NSX-T 3.x

-
Image
  Hello There, In this article, i am covering how to migrate the ESXi host switch from N-VDS to VDS 7.0 switch in NSX-T 3.2.x version. When using N-VDS as the host switch,  NSX-T  is represented as an opaque network in  vCenter Server . N-VDS owns one or more of the physical interfaces (pNICs) on the transport node, and port configuration is performed from  NSX-T Data Center . You can migrate your host switch to  vSphere  Distributed Switch (VDS) 7.0 for optimal pNIC usage and manage the networking for  NSX-T  hosts from  vCenter Server . When running  NSX-T  on a VDS switch, a segment is represented as an  NSX-T  Distributed Virtual Port Groups. Any changes to the segments on the  NSX-T  network are synchronized in  vCenter Server. We have an NSX-T environment running with NSX-T 3.2.2.1 version. this environment was designed and implemented with NSX-T 2.x version and that time we used the N-VDS as host switch configuration on the transport nodes bcuz VDS was not supported that time. 
Read more

vROPS appliances password remediation tasks failed from SDDC manager

-
Image
Issue details:-   Password remediation tasks on SDDC manager getting failed with below error. However, we are able to connect SSH with root password on the vROPS appliances, no issues with credentials. I checked Operations logs on SDDC manager and found below logs, indicating the SSH connectivity issues from SDDC to vROPS appliances. Tried to do SSH vROPS appliance from SDDC manager, getting below error... Seems some issue with ECDSA key.. Resolution:- SSH to vROPS appliance and retrieve the ECDSA ssh keys as below. Now, we have 2 options to update the correct SSH keys for vROPS appliance on SDDC manager known_Hosts files located at below location.   /root/.ssh/known_hosts   /etc/vmware/vcf/commonsvcs/known_hosts   /home/vcf/.ssh/known_hosts   /opt/vmware/vcf/commonsvcs/defaults/hosts/known_hosts First option is manually copy and paste the SSH key on all the known_hosts files and restart the SDDC manager services and then try to remediate the password again. it will be successful this
Read more

How to Import/Register a VM into vRA portal

-
Image
You can import an unmanaged virtual machine to a vRealize Automation environment. An unmanaged virtual machine exists in a vCenter but is not managed in a vRealize Automation environment and cannot be viewed in the vRA portal . Once you import an unmanaged virtual machine, the virtual machine is managed by using the vRealize Automation management interface. you can see the virtual machine on the Managed Machines tab or the Items tab. Please follow below steps to Import/Register VM into a vRA portal. Log in to vRealize Automation as a fabric administrator and as a business group manager. If you are importing virtual machines that use static IP addresses, prepare a properly configured address pool.  If you use bulk import to import a virtual machine with a static IP address that is allocated to another virtual machine, the import fails. Create a Blueprint and should not have even network attached as well. See below snapin. Create Network profile that shoul
Read more