This multi-part blog focuses on deploying vRA 8.1 HA, vIDM 3.3.2 HA using an F5 BIG-IP LTM load balancer. The context for the material is to call out pitfalls, direction and resolution to issues with an HA vRA 8.1 deployment. Specifically, these blogs call out additional configuration for vIDM HA scale out with vRA 8.1 HA. This content is broken into four parts:
- Part 1: Pre-work with F5 BIG-IP LTM
- Part 2: vRA HA install
- Part 3: Post vRA and vIDM HA install configurations
- Part 4: vIDM HA scale out
vIDM HA Scale Out
In the previous posts, we configured F5 BIG-IP, deployed vRSLCM, vRA HA, x 1 vIDM node and configured post install configurations to support vIDM Scale out. In this post, we will use vRSLCM to deploy x 2 additional vIDM nodes so as to configure an HA vIDM deployment.
There are five manual checks to validate before scaling out vIDM. These are
- Load Balancer Check – For Cluster: vRSLCM references vIDM documentation for Load-Balancer configuration and making sure to establish trust between the F5 and vIDM Nodes. The primary intent with this four-part blog posts is to save you time in gathering the details necessary to scale out vIDM.
- Time Server Configuration – For Cluster: double check time sync is correct on all nodes and configurations.
- Delegate IP Check – For Cluster: this Delegate IP is used with vIDM cluster configuration. It must be a free available IP that is used internally as a database Load-Balancer IP for Proxying to the vIDM Postgress master. IMPORTANT This is not the same as the one used to load-balance the application.
- Ping Check – For Cluster: Make sure all the vRA and vIDM nodes are resolvable from vRSLCM.
- Re-Register Check – For Cluster: After vIDM is scaled out, make sure to re-register all the products/applications already configured with vIDM. In this case, vRA can be re-registered with vIDM as shown in previous posts.
vRSCLM Scale Out vIDM x 2 Nodes
This section outlines steps in vRSLCM to scale out vIDM. Navigate to vRSLCM > Lifecycle Operations > Environments > globalenvironment > View Details > + Add Components
Selecting + Add Components, you are reminded to have snapshot of vIDM and Trigger Inventory Sync before proceeding.
- Validate snapshot for vIDM node # 1
- Click to Trigger Inventory Sync
- Click Proceed
- Complete the infrastructure details that apply to scaling out vIDM nodes # 2 and 3.
- Complete the network details that apply to scaling out vIDM nodes # 2 and 3.
- Complete adding Components + and selecting Secondary.
- Add secondary nodes, ie vIDM node # 2 and 3. VM Name, FQDN and IP Adddress
The precheck needs to return green on all items. Correct items that fail and re-run the precheck until achieving green on all items. For convenience, see the below download for an example Precheck_Report pdf.
The precheck validation is important to resolve any flagged items prior to vIDM scale out. Once validation is complete, click Next.
It is recommended to export configuration, which downloads a json file that can be used to redeploy or edit and deploy new. When ready, Click Submit
With all the prework on place and double checking configurations. The scale out of vIDM begins as shown above. It takes a while to run through the scale out process and consider taking the time reviewing its progress and the different stages. Remember when complete to re-register with vIDM as called out earlier in this post.
Once vIDM HA with vRA HA is stood up, validate the installation using the vIDM and vRA F5 VIP FQDN.
In this post, we reviewed the vRSLCM scale out of vIDM node 2 and 3.