In a configured NSX with network service insertion working environment.
If we power down the whole infrastructure then power up with an incorrect order.
The NSX network service insertion will not able to recover.
Reproduce Step:
1. In a configured and working network service insertion environment.
(ESXi 6.0 U3 / vCenter 6.0 U3 / NSX Manager 6.2.6)
2. Power down all VMs from vCenter. Then power down ESXi.
3. Power up all ESXi in cluster. Power up vCenter and wait until web client page able to login.
4. Power up NSX Manger.
Current Behavior:
In vCenter > vCNS > Installation > Host Preparation. The installation status (Network Fabric) will show "Not Ready".
Even though we can manually click on "Resolve" to make it green again. But in fact, it would not apply updates to ESXi and related components. So network service insertion would not work anymore.
Which means, if we missed the chance let NSX Manager and 3rd party service console ready before vCenter. Then network service insertion related functions would not work.
Expected Result:
Even in an incorrect boot up sequence. i.e when vCenter boot up first but NSX Manager not ready to serve. After manually click "Resolve" from vCenter > vCNS > Installation > Host Preparation.
After installation status green again, it should apply updates to ESXi or related components and bring up ESX Agents such as Guest Introspection VM or 3rd party services VMs.
Comparison Experiment:
If we power up NSX Manager and 3rd party service console before than vCenter. When vCenter ready, it would automatically bring up ESX Agents and network service insertion would work.
We can always reproduce this issue repeatedly with different stats: working > make it bad with incorrect boot up sequence > working with correct boot up sequence.
But its unacceptable that the recovery method is power down whole infrastructure and boot up with the correct one. In some cases, its not guaranteed that NSX Manager and 3rd party console always ready before vCenter.
Does anyone able to help? If you need further information, please feel free to reach me.