1 person found this helpful
There's a known issue that is in the release notes that might explain your problem:
Issue 2410224 - After completing NSX Intelligence appliance registration, refreshing view may return a 403 Forbidden error.
Does anybody configured the NSX Intelligence with an NSX-T which is integrated with VMware Enterprise PKS ?
Because of this product would have the big value in the nearly real time traffic monitoring and firewall rule recommendations, but as i can see it is not working with changed certificate.
But the first step says when you configure the Bosh directory with NSX-T to give an NSX CA Certificate, I made exactly the same as the KB says, but it is still not working.
NSX-T 2.5.1 was released last week and includes a workaround for the certificate change issue. Haven't tested it yet, but it should work.
Look at issue 2436302 in the release notes: VMware NSX-T Data Center 2.5.1 Release Notes