Enabling VPN-based deployments with Azure
Note
The functionality referenced in this topic applies to version 4.6.03 and later.
A remote access VPN client connection does not connect your entire enterprise network to Microsoft Azure. Instead, it enables remote access to virtual machines that are contained within Azure Virtual Networks so that you can manage them from BMC Cloud Lifecycle Management.
Note
Currently, BMC supports this functionality for a Windows BMC Cloud Lifecycle Management stack with point-to-site VPN connectivity.
High-level process to enable VPN-based deployments
The overall process for enabling VPN-based deployments with Azure includes the following steps:
- (Optional) Set up IP Address Management (IPAM). For details, see Enabling IP address management (and its subtopics).
Configure BMC Atrium Orchestrator for DNS registration by activating the DNS adapter on the grid and install Bind9 where your BMC Atrium Orchestrator server is installed. For details, see Configuring BMC Atrium Orchestrator for automatic DNS registration.
- Enable the integration between BMC Atrium Orchestrator and BMC Network Automation by setting the System Parameters in BMC Network Automation. Also, set performDnsOperation to true in the global.properties file in BMC Network Automation.
- Onboard the logical data center (LDC) and then edit the LDC to enable DNS registration.
- Create a service blueprint for the Azure service with DNS enabled. To know more about the additional items to consider when creating a service blueprint for Azure Provider, see Building service blueprints for Azure service.
- Create the service offering for Azure.
Configure DNS cache on the BMC Server Automation server.
Comments
Log in or register to comment.