atusmenezes's Posts

Hello, As far as I know, this limitations are linked to NSX instance, so, considering that this new cluster going to be managed by a new NSX-T instance...
Hello, how are you? You can use vlan-backed segments as service interfaces (or centralized service ports). Unfortunately, it is possible to use NSX-T to work with vlans, but you cannot leveraging NS... See more...
Hello, how are you? You can use vlan-backed segments as service interfaces (or centralized service ports). Unfortunately, it is possible to use NSX-T to work with vlans, but you cannot leveraging NSX-T logical routing with then.
Hello, how are you? 1. When you have to restore NSX-T, be sure to deploy a new appliance with the same IP and Hostname (FQDN), as also in the same version as the old one. It not necessary to do anyt... See more...
Hello, how are you? 1. When you have to restore NSX-T, be sure to deploy a new appliance with the same IP and Hostname (FQDN), as also in the same version as the old one. It not necessary to do anything else. Just deploy and point to the SFTP server with the right configurations. 2. When you backup NSX, all configurations will be written in the backup file. What you do after the backup obviously doesn't count. That's why it's interesting to backup periodically. 3. You can delete the old files directly in the SFTP server, but, check this doc: https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/administration/GUID-ECFFBD6D-4D2F-4773-B552-B27D4ECE0AC4.html  
Hello, how are you? Did you reboot the host after NSX removal?
Hello, how are you? Try to restart vmware-vapi-endpoint service. Log in vCenter via ssh and execute this command: $service-control --stop vmware-vapi-endpoint $service-control --start vmware-vapi-... See more...
Hello, how are you? Try to restart vmware-vapi-endpoint service. Log in vCenter via ssh and execute this command: $service-control --stop vmware-vapi-endpoint $service-control --start vmware-vapi-endpoint
I believe you want to download it to do a restore, right? In this case, you can user the version 3.2.0.1. https://customerconnect.vmware.com/downloads/details?downloadGroup=NSX-T-3201&productId=982... See more...
I believe you want to download it to do a restore, right? In this case, you can user the version 3.2.0.1. https://customerconnect.vmware.com/downloads/details?downloadGroup=NSX-T-3201&productId=982  
Try this one, then: Execute a GET against this URL https://<manager-ip>/api/v1/transport-nodes/<tn-id>  and in tn-id, put the ID of the edge that is presenting problems. This will return a JSON wi... See more...
Try this one, then: Execute a GET against this URL https://<manager-ip>/api/v1/transport-nodes/<tn-id>  and in tn-id, put the ID of the edge that is presenting problems. This will return a JSON with all configuration of this node. Then, execute the POST below: url -k -v -u 'admin:PASSWORD' -X POST -H 'Content-Type: application/json' -d '{ "vm_id":"VM ID", "vm_deployment_config": { <You can get this info from the previous GET command> } }' https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=addOrUpdatePlacementReferences   You can get the VM_DEPLOYMENT_CONFIG info, from the previous GET command.
Hello, how are you? I believe you have to do something like that: curl -k -v -u 'admin:PASSWORD' -X POST -H 'Content-Type: application/json' -d '{ "vc_id": "VCENTE ID", "vm_id":"VM ID", ... See more...
Hello, how are you? I believe you have to do something like that: curl -k -v -u 'admin:PASSWORD' -X POST -H 'Content-Type: application/json' -d '{ "vc_id": "VCENTE ID", "vm_id":"VM ID", "node_user_settings": { "cli_username": "admin", "root_password":"PASSWORD", "cli_password":"PASSWORD" } }' https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=addOrUpdatePlacementReferences   But, I believe that recreate the edge node is easier.
No. You can reboot the standby vm.
Hello, No. You can do a reboot in the standby VM without problems. Just be sure there are no services running there. You also can run some commands to validate which process could be causing this hi... See more...
Hello, No. You can do a reboot in the standby VM without problems. Just be sure there are no services running there. You also can run some commands to validate which process could be causing this high CPU usage.