Knowledge Base  /  Disaster Recovery  /  SafeHaven 5 CLC to Azure
Knowledge Base  /  Disaster Recovery  /  SafeHaven 5 CLC to Azure

Create CMS in Azure

Updated by Juan Aristizabal on Jun 13, 2018
Article Code: kb/1098

Article Overview

This article explains how to create a CMS (Central Management Server) in Azure DR Datacenter.

Requirements

  1. User must have an Azure account and permissions to deploy a server in the DR subnet.
  2. Internet access on CMS in Azure once it is deployed.

Assumptions

  1. It is assumed here that the user has an Azure account, a VNet created which has accessibility to CenturyLink Cloud Production Datacenter and a Resource Group that will contain all the resources related to SafeHaven.
  2. It is assumed the user has a storage account created.

Create an Azure instance

  1. Go to the Azure portal https://portal.azure.com
  2. Go to Virtual Machines service on the Favorites list or search for the service at top of the page next to the arrow glass.
  3. Click on the plus sign Add.
  4. Click on Ubuntu Server, and then click on Ubuntu Server 16.04 LTS. Finally click on the Create button.
  5. On the Basics blade provide the following information:
    • Enter a Name for the Virtual Machine
    • Select HDD for the VM disk type
    • Click on Password for Authentication type and provide both a Username and Password for it. The username cannot be root, the password for root is generated automatically by Azure.
    • Select a Subscription and a Resource Group.
    • Select the Location for the CMS. This location must match the location of the Vnet where the Instance will reside on.
    • Click on the OK button.
  6. On the Size blade search for B1ms and then select the B1ms Standard type instance. 1 vCPU, 2 GB of RAM and 2 data disks. Click on the Select button.
  7. On the Settings blade provide the following information:
    • Click on No for Use managed disks, select a Storage account for the destination of the CMS unmanaged disks. Azure will filter out automatically the storage accounts that do not match the location selected previously for the Virtual Machine on step 5.
    • Click on Virtual Network under Network and select the VNet. Azure will filter out automatically the virtual networks that do not match the location selected previously for the Virtual Machine on step 5.
    • Select a Subnet and a Public IP address for the CMS, by default Azure will create a new IP address. CMS requires access to the Internet therefore a public IP address is needed.
    • Click on Advanced under Network Security Group, this will open the option to select a Network Security Group, by default Azure will create one that has all traffic open to Instances deployed on the same VNet and any Point to Point VPNs on it. Use the automatically created Network security group.
    • Select a Diagnostics storage account, it can be the same storage account selected on step 7. By default Azure enables the Boot diagnostics on the Virtual Machine.
  8. Leave all the other values to default and click on the OK button.
  9. On the Summary blade review the settings and click on the OK button.
  10. Once the Virtual Machine is created go to Virtual Machines service and find the Instance, select it and then click on Networking, write down either the Public IP or Private IP information depending if you will be accessing the server through the Internet or via VPN from CenturyLink.
  11. SSH to the CMS Instance using the credentials created on step 5.
    • Once logged in elevate to root access and modify the password
      sudo -s
      passwd root
      
    • Enable SSH root login vi editing /etc/ssh/sshd_config with this line
      PermitRootLogin yes
      
    • Restart the SSH service
      systemctl restart sshd