VMware NSX-T has a preconfigured password expiration policy of 90 days.
Attention you lower your security standards if you never change your password. Same procedure for nsx-t edge nodes the same.
clear user admin password-expiration
clear user root password-expiration
clear user audit password-expiration
I think it is better you change your password once a year
set user admin password-expiration 365
set user root password-expiration 365
set user audit password-expiration 365
A very long time I used ha-proxy for lb to publish Exchange OWA/Active-Sync in to the WWW. After the installation with NSX-T. I have the opportunity to replace my old ha-proxy configuration with the integrated LB from NSX-T. I would like to replace the ha-proxy for internal MAPI namespace. Normally that will be used often KEMP LB or ha-proxy. With NSX-T you can also replace this product. To Replace MAPI Namespace lb is very simple that will be used only TCP for lb.
I will not write how to deploy the LB that can you read here.
I will show you some configuration where not included in the knowledge base.
To protect your Administrator interface from external access. In my old ha-proxy configuration I had a ACL to protect ecp from external.
For the OWA rule you must add a forwarding rule with this options.
For your SSL configuration you need your domain certificate and intermediate certificates also.
You need Client SSL and Server SSL. You can use twice the same certificate,.
Before you can assign the certificates you have to import the certificates for your domain and the intermediate certificates under System = >Certificates
After importing the certificates you can assign this to your Virtual Servers HTTP 7 rule.
Trusted CA Certificates means your intermediate certificate.
VM wil not power-on and throws the following error:
Object type requires hosted I/O
SSH into the ESX-host that’s hosting the VM.
Browse to the VM-folder containing the disk files.
Run the following command in ESXI CLI:
vmkfstools -x check “disk.vmdk”
Disk needs repaired
vmkfstools -x repair “disk.vmdk”
Disk was successfully repaired.
Start VM from vCenter