Installing Cisco Elastic Services Controller on VMware vCenter. Cisco Elastic Services Controller

P A R T

II

Installing Cisco Elastic Services Controller on

VMware vCenter

•

Prerequisites, on page 57

•

Installing Cisco Elastic Services Controller on VMware vCenter, on page 61

•

Installing High Availability, on page 69

C H A P T E R

11

Prerequisites

The following sections detail the prerequisites for installing Cisco Elastic Services Controller:

•

Virtual Resource and Hypervisor Requirements, on page 57

•

vCenter Resources, on page 57

•

Important Notes, on page 58

Virtual Resource and Hypervisor Requirements

The following table lists the prerequisites to install Cisco Elastic Services Controller on VMware vCenter or vSphere:

See the VMware Compatibility Guide to confirm that VMware supports your hardware platform.

Requirement Description

System Requirements

Virtual CPUs

Memory

Disk Space

Hypervisor Requirements

VMWare vCenter

4 VCPUs

8 GB RAM

30 GB

ESC supports VMware and vCenter versions 6.5.

vCenter Resources

Resources to be created/installed on vCenter:

• Datacenters : At least one datacenter. For more details, see the Important Notes below.

• Hosts : Host configuration based on your targeted performance objectives. Each Host under the single vDS must have at least two physical Network Interface Card (NIC) connected, (one for vCenter

Management Interface by default, and the other used to assign to VDS's uplink portgroup). This setup is required for data access across hosts.

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

57

Installing Cisco Elastic Services Controller on VMware vCenter

Important Notes

• Compute Clusters : Clusters can be created to group several hosts together.

• Datastores : Shared datastore is required if user wants to leverage DRS.

• Distributed Switches : At least one distributed switch that will contains all the VNF supporting networks.

Important Notes

Keep in mind the following important notes while installing ESC on a VMware:

• A single ESC instance will only support:

• Multiple Datacenter supported deployment, network, image, subnet creation

• One vSphere Distributed Switch (VDS)

• DPM, HA Active/Standby, and vMotion must be off.

• If DRS is enabled, it has to be in the "Manual Mode".

• Fault Tolerance is not supported.

• Datastore Cluster is not supported, only flat datastore(s) structure under the cluster or under the datacenter are supported.

• ESC only supports a default resource pool. Adding and creating resource pools are not supported.

• Image (Template) created through ESC are stored under /esc-ovas folder .

• Day-0, smart license, and other supported files are packed into a ISO file, and uploaded to the same folder where the VM rest, then mount it as a CD-ROM to the VM.

• ESC/VIM does not respond for the name and file content passed in for generating ISO file. They have to be provided according to each template's requirements. e.g. for ASAv, the day-0 config has to be named as "day0-config", and smart license token has to be named as "idtoken".

• When you see the error message "Networking Configuration Operation Is Rolled Back and a Host Is

Disconnected from vCenter Server", it is due to a vCenter's limitation. See the Troubleshooting guide , page 91 to increase the timeout for rollback.

• The following VM features and operations are not supported in all versions of the Cisco CSR 1000V. If still these operations are used or performed, there may be risk of encountering dropped packets, dropped connections, and other error statistics.

1.

DRS

2.

Suspend

3.

Snapshot

4.

Resume

• Although deployments can be processed without shared storage, ESC does not guarantee optimized computing resource. Shared storage(s) should associate with as many as possible hosts, which will give more opportunity to DRS to balance resources.

58

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

Installing Cisco Elastic Services Controller on VMware vCenter

Important Notes

• Every time a redeploy happens as part of recovery on VMware, VM's interface(s) will have different

MAC addresses.

• All the VM group defined in a datamodel must accompany with a "zone-host" placement policy, meaning the deployment has to be either host-targeted or cluster-targeted.

• Recovery may fail, if a VM has PCI/PCIe passthrough device(s) attached, when it's recovered to a computing-host (picked based on ESC placement algorithm) which does not have any PCI/PCIe passthrough enabled device available .

• For PCI/PCIe passthrough working, DRS has to be off .

• If you experience a PowerOn error on a VM that has PCI/PCIe passthrough device(s) attached to it, update the VM or the image (template) the VM is cloned from, using the solution described here .

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

59

Important Notes

Installing Cisco Elastic Services Controller on VMware vCenter

60

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

C H A P T E R

12

Installing Cisco Elastic Services Controller on

VMware vCenter

This chapter describes how to install Cisco Elastic Services Controller on VMware vCenter and includes the following sections:

•

Installing Cisco Elastic Services Controller on VMware vCenter, on page 61

•

Next Steps: Cisco Elastic Services Controller Virtual Machine, on page 67

Installing Cisco Elastic Services Controller on VMware vCenter

Cisco Elastic Services Controller can be installed in a VMware ESXi hypervisor and can be accessed or managed using vSphere client of VMware. You can install Cisco Elastic Services Controller in a VMware environment using an Open Virtual Appliance (OVA) package.

The VMware vSphere client can be connected directly to your ESXi installation, or it can be connected to a vCenter server which in turn is connected to your vSphere installation. Connecting through vCenter provides a number of capabilities that connecting directly to ESXi does not. If a vCenter server is available and associated with the ESXi installation, it should be used.

Preparing to Install Cisco Elastic Services Controller

In order to install Cisco Elastic Services Controller and configure its network connection, you have to answer several questions. Some of these questions concern the networking environment in which the virtual machine is being installed, and some of them concern values which are unique to the particular virtual machine being installed.

Before you perform the installation, ensure that you are prepared by reviewing this checklist:

Requirements Your Information/ Notes

OVA image location

OVA image

VSphere Web Client

Hostname

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

61

Installing Cisco Elastic Services Controller on VMware vCenter

Installing the Elastic Services Controller Using the OVA Image

Requirements

IP address

Subnet mask

Network vCenter IP vCenter Port vCenter credentials

Datacenter Name

Datastore Host

Computer Cluster Name

Your Information/ Notes

Installing the Elastic Services Controller Using the OVA Image

To install Cisco Elastic Services Controller, you must first download the correct installation file.

Using vSphere, connect directly to the ESXi installation or the vCenter server, and select the ESXi installation where the OVA is to be deployed.

This procedure describes how to deploy the Elastic Services Controller OVA image on VMware.

Before you begin

• Set your keyboard to United States English.

• Confirm that the Elastic Services Controller OVA image is available from the VMware vSphere Client.

• Make sure that all system requirements are met as specified in the Chapter 6: Prerequisites.

• Gather the information identified in Preparing to Install Cisco Elastic Services Controller.

Procedure

Step 1

Step 2

Step 3

Using the VMware vSphere Client, log in to the vCenter server.

Choose vCenterHome > Hosts and Clusters . Right click the host where you want to deploy ESC, and then choose Deploy OVF Template .

In the wizard, provide the information as described in the following table:

Screen

Select source

Action

Select the Elastic Services Controller OVA.

Review details

Select name and folder

Review OVF Template details.

Enter a name and select a folder for the VM.

62

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

Installing Cisco Elastic Services Controller on VMware vCenter

Screen

Select configuration

Select a resource

Select storage

Select networks

Customize template

Bootstrap Properties

Username

Password

Host name

Network IP

Network Gateway

Enable Https Rest

Enable Portal startup

VIM Settings of vCenter Server vCenter IP vCenter Port vCenter Username vCenter Password

Installing the Elastic Services Controller Using the OVA Image

Action

Select any one of the following deployment configurations:

• Large, 1 Network

• Large, 2 Networks

• Large, 3 Networks

Select the host or cluster to run the ESC template.

Select a location to store the files for the VM and a provisioning type. The storage can be local or shared remote, such as NFS or SAN.

You can choose either Thin provisioned format or

Thick provisioned format to store the VM virtual disks.

Based on the Network configuration for the deployment selected in the Select configuration option, you can allocate the pre-configured networks in vCenter to ESC network interfaces.

Administrator username for remote login.

Administrator password.

VM Hostname.

VM IP address.

Gateway IP address.

Enable external REST interface over HTTPS on port

8443.

Enable Portal startup at port 9001 (for https).

IP address of vCenter server for VNF deployment .

Port of the vCenter server.

Username to access vCenter server.

Password to access vCenter server.

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

63

Installing Cisco Elastic Services Controller on VMware vCenter

Installing Elastic Services Controller Using OVF Tool

Step 4

Step 5

Step 6

Step 7

Screen

Datacenter Name

Datastore Name

Datastore Host

Ready to Complete

Public Key

ConfD Username

ConfD Password

ConfD Public Key

Action

Name of the Datacenter in target vCenter for VNF deployment (Default VDC after Multi-VDC supported)

The destination datastore of all the image (template) create through ESC .

The destination computing-host of all the image

(template) create through ESC.

Review the deployment settings.

Caution Any discrepancies can cause VM booting issues. Carefully review the IP address, subnet mask, and gateway information for accuracy.

Administrator authorized public key for remote login.

Administrator username for netconf and ConfD CLI.

Administrator password for netconf and ConfD CLI.

Administrator authorized public key for netconf and

ConfD CLI.

Check the Power on after deployment check box to power on the VM after deployment.

Click Finish .

A progress indicator shows the task progress until Elastic Services Controller is deployed.

After Elastic Services Controller is successfully deployed, click Close .

Power on the Elastic Services Controller VM.

Installing Elastic Services Controller Using OVF Tool

In addition to installing the Elastic Services Controller using the OVA image, you can use the VMware OVF

Tool, a command-line client, to install Elastic Services Controller on VMware vCenter or vSphere.

To install Elastic Services Controller (ESC) from the command line, do the following:

Procedure

Step 1 Use the probe mode to learn the properties of the OVA package. The probe mode allows you to investigate the contents of a source.

To invoke the probe mode, use the ovftool command with only a source and no target.

>ovftool <source locator>

The following example shows the result of probing the ESC OVA.

64

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

Installing Cisco Elastic Services Controller on VMware vCenter

Installing Elastic Services Controller Using OVF Tool

Step 2

NETWORK_OVA= (Path to the OVA Package)

NETWORK_HOSTNAME="$ (User Name) "

NETWORK_GATEWAY="192.0.2.1"

NETWORK_NET1_IP="192.0.2.0.xx/24" #

NETWORK_NET2_IP="192.51.100.xx/24"

ADMIN_USERNAME=" (admin name) "

ADMIN_PASSWORD=" (password) "

HTTPS_REST="True"

VMWARE_VCENTER_PORT='80'

VMWARE_VCENTER_IP='192.0.2.0.xx'

VMWARE_DATASTORE_HOST='192.0.2.0.xx'

VMWARE_DATACENTER_NAME='DC-NETWORK-1'

VMWARE_DATASTORE_NAME='cluster-datastore1'

VMWARE_COMPUTE_CLUSTER_NAME='DC-CLUSTER-1'

VMWARE_VCENTER_USERNAME='root'

VMWARE_VCENTER_PASSWORD=' password '

VMWARE_VCENTER_FOLDER="$USER"

# All valid deployment options:

#

#

4CPU-8GB (default)

4CPU-8GB-2Net

# 4CPU-8GB-3Net

DEPLOYMENT_OPTION="4CPU-8GB-2Net"

Before you deploy the ESC OVA, configure the properties of the OVA packages. Ensure the following OVA package properties are updated for the ESC OVA: NETWORK_OVA, NETWORK_HOSTNAME,

VMWARE_VCENTER_FOLDER, NETWORK_NET1_IP, NETWORK_NET2_IP, and

VMWARE_VCENTER_FOLDER.

The OVA descriptors contain configuration properties for the OVA package. You can set only one property at a time, but you can have multiple instances of the option per command. For multiple property mappings, repeat the option, separating them with a blank, for example --prop:p1=v1 --prop:p2=v2 --prop:p3=v3.

>.ovftool/ovftool\

--powerOn \

--acceptAllEulas \

--noSSLVerify \

--datastore=$VMWARE_DATASTORE_NAME \

--diskMode=thin \

--name=$NETWORK_HOSTNAME \

--deploymentOption=$DEPLOYMENT_OPTION \

--vmFolder=$VMWARE_VCENTER_FOLDER \

--prop:admin_username=$ADMIN_USERNAME --prop:admin_password=$ADMIN_PASSWORD \

--prop:admin_username=admin \

--prop:admin_password='Strong4Security!' \

--prop:confd_admin_username=admin \

--prop:confd_admin_password='Strong4Security!' \

--prop:network_hostname=$NETWORK_HOSTNAME \

--prop:vmware_vcenter_port=$VMWARE_VCENTER_PORT \

--prop:vmware_vcenter_ip=$VMWARE_VCENTER_IP \

--prop:vmware_datastore_host=$VMWARE_DATASTORE_HOST \

--prop:vmware_datacenter_name=$VMWARE_DATACENTER_NAME \

--prop:vmware_vcenter_username=$VMWARE_VCENTER_USERNAME \

--prop:vmware_datastore_name=$VMWARE_DATASTORE_NAME \

--prop:vmware_compute_cluster_name=$VMWARE_COMPUTE_CLUSTER_NAME \

--prop:vmware_vcenter_password=$VMWARE_VCENTER_PASSWORD \

--prop:net1_ip=$NETWORK_NET1_IP \

--prop:net2_ip=$NETWORK_NET2_IP \

--prop:gateway=$NETWORK_GATEWAY \

--prop:https_rest=$HTTPS_REST \

--net:"Network1=VM Network" --net:"Network2=MgtNetwork" --net:"Network3=VNFNetwork" \

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

65

Installing Cisco Elastic Services Controller on VMware vCenter

Powering on Cisco Elastic Services Controller Virtual Machine

Step 3

$NETWORK_OVA vi://$VMWARE_VCENTER_USERNAME:$VMWARE_VCENTER_PASSWORD@$VMWARE_VCENTER_IP/$VMWARE_DATACENTER_NAME/ host/$VMWARE_COMPUTE_CLUSTER_NAME

Following are some advanced examples of passing user credentials through properties.

Advanced usage with password hash:

--prop:admin_username=admin \

--prop:admin_password='$6$wnOi$UDOQmkKm2tQtr2jDVNhoo4wS42ffYYmzxMXLDugfzTbTXmMQDw146VzpxQvMumeaa125.agYHZUqQ8L.sdM2v0'

\

--prop:confd_admin_username=admin \

--prop:confd_admin_password='$6$wnOi$UDOQmkKm2tQtr2jDVNhoo4wS42ffYYmzxMXLDugfzTbTXmMQDw146VzpxQvMumeaa125.agYHZUqQ8L.sdM2v0'

\

Advanced usage with password hash and authorized public key:

--prop:admin_username=admin \

--prop:admin_password='$6$wnOi$UDOQmkKm2tQtr2jDVNhoo4wS42ffYYmzxMXLDugfzTbTXmMQDw146VzpxQvMumeaa125.agYHZUqQ8L.sdM2v0'

\

--prop:admin_public_key='ssh-rsa

AAAAB3NzaC1yc2EAAAABIwAAAIEAu+nkTtu2pShVbTYL+mmKxtmzM5dNXFy8IeX/lH5fXsODH1EAySlzHGFXq36RT5vIG/

+c2uV8fRsWaY7xXDrdGICxfkPuEj2UQH2MQx2yFjMFcaSAT56hsqE= admin@net' \

--prop:confd_admin_username=admin \

--prop:confd_admin_password='$6$wnOi$UDOQmkKm2tQtr2jDVNhoo4wS42ffYYmzxMXLDugfzTbTXmMQDw146VzpxQvMumeaa125.agYHZUqQ8L.sdM2v0'

\

--prop:confd_admin_public_key='ssh-rsa

AAAAB3NzaC1yc2EAAAABIwAAAIEAu+nkTtu2pShVbTYL+mmKxtmzM5dNXFy8IeX+xXu6TT2sTsxkKtVy8uOAeBp1qKzkp+ c2uV8fRsWaY7xXDrdGICxfkPuEj2UQH2MQx2yFjMFcaSAT56hsqE= admin@net' \

Note You need to replace the variables (IP addresses, root password, VM names, and so on) in the examples above with values from your own system.

To deploy the OVA package with the VMware OVF Tool, use the following command syntax:

>ovftool <source locator> <target locator> where <source locator> is the path to the OVA package and <target locator> is the path target for the virtual machine, OVA package or VI. A VI location refers to any location on a VMware product, such as vSphere,

VMware Server or ESXi. For more information on the VMware OVF Tool, see the VMware OVF Tool user documentation.

The ESC VM is deployed on VMware and powered on automatically.

Powering on Cisco Elastic Services Controller Virtual Machine

To power on the Cisco Elastic Services Controller virtual machine (VM):

Note You must set the memory and CPUs based on the requirements prior to clicking the power on. Once you start the VM you cannot change the memory or CPU settings until you shut down.

66

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

Installing Cisco Elastic Services Controller on VMware vCenter

Next Steps: Cisco Elastic Services Controller Virtual Machine

Procedure

Step 1

Step 2

After deploying the VM, select the virtual machine name in vSphere, right-click on it and select Open Console .

Click the Power on button ( ). During the initial boot of the newly deployed machine, you will be prompted to enter a root (system) password, which is not the Cisco Elastic Services Controller portal password.

Initialization may vary depending on the setup.

Note This is the root password for the underlying Linux operating system on which the Cisco Elastic

Services Controller portal is installed. You will be asked to enter this password twice. You will need root access to the underlying Linux operating system at various times in the future, so make sure that you remember this password.

The End User License Agreement window appears on the first boot. Read the license agreement in its entirety, and only if you understand and accept the license terms, enter y (Yes).

Next Steps: Cisco Elastic Services Controller Virtual Machine

Logging in to Cisco Elastic Services Controller Portal

To log in to the ESC Portal, see the

Logging in to the ESC Portal, on page 126

Configuring the Virtual Machine to Automatically Power Up

You can configure the ESXi hypervisor to automatically power up the ESC VM when power is restored to the ESXi hypervisor layer.

Note You must manually power up the VM.

Procedure

Step 1

Step 2

Step 3

Step 4

Step 5

In the vSphere client, select the ESXi machine to which you are connected. It is not a specific VM that you have to select but the ESXi hypervisor on which they reside.

Select the Configuration tab.

Click the Virtual Machine Startup/Shutdown link under the Software area. You should see the VM in the list shown in window.

Click the Properties...

link present at the top right corner of the page. If you do not see that, resize the window until you do.

The Virtual Machine Startup and Shutdown page is displayed.

Check the Allow virtual machines to start and stop automatically with the system check box.

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

67

Installing Cisco Elastic Services Controller on VMware vCenter

Configuring the Virtual Machine to Automatically Power Up

Step 6

Step 7

Select the virtual machine running ESC and use the Move Up button on the right to move it up into the group labeled Automatic Startup

Click OK

This ensures that whenever power is restored to the ESXi hypervisor, the ESC VM powers up automatically.

68

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

C H A P T E R

13

Installing High Availability

This chapter contains the following sections:

•

High Availability Active/Standby Overview, on page 69

•

How High Availability Active/Standby Works, on page 70

•

Deploying ESC High Availability Active/Standby with User Data (HA Active/Standby Pair), on page

70

•

Deploying ESC High Availability Active/Standby (Standalone Instances), on page 74

•

Important Notes for ESC HA Active/Standby, on page 75

•

Troubleshooting High Availability Active/Standby, on page 75

High Availability Active/Standby Overview

ESC supports High Availability (HA) in the form of Active/Standby and Active/Active models. For

Active/Standby model, two ESC instances are deployed in the network to prevent ESC failure and provide

ESC service with minimum service interruption. If the primary ESC instance fails, the standby instance automatically takes over the ESC services. ESC HA Active/Standby resolves the following single point failures:

• Network failures

• Power failures

• Dead VM instance

• Scheduled downtime

• Hardware issues

• Internal application failures

Note From ESC 5.0, the name, Active/Passive model is changed to Active/Standby model.

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

69

Installing Cisco Elastic Services Controller on VMware vCenter

How High Availability Active/Standby Works

How High Availability Active/Standby Works

A High Availability Active/Standby deployment consists of two ESC instances: a primary and a standby.

Under normal circumstances, the primary ESC instance provides the services. The corresponding standby instance is passive. The standby instance is in constant communication with the primary instance and monitors the primary instances' status. If the primary ESC instance fails, the standby instance automatically takes over the ESC services to provide ESC service with minimum interruption.

The standby also has a complete copy of the database of the primary, but it does not actively manage the network until the primary instance fails. When the primary instance fails, the standby takes over automatically.

Standby instance takes over primary instance to manage the services while primary instance restoration taken place.

When the failed instance is restored, failback operations can be initiated to resume network management via the original primary instance.

ESC instances are managed by using KeepAliveD service. The VM handshake between ESC instances occurs through the KeepAliveD over the IPv4 network.

Deploying ESC High Availability Active/Standby with User Data

(HA Active/Standby Pair)

Before you begin:

• Cisco Elastic Services Controller (ESC) High Availability (HA) Active/Standby requires a network to keep alive and replicate database between primary and standby nodes. Both ESC VMs must have at least one network interface connecting to the same network and must be able to communicate to each other through the network.

• Ensure the two ESC VMs are located in different hosts and datastores so that single point failures can be prevented.

You can deploy ESC HA Active/Standby on VMware vCenter or vSphere in either of two ways:

• Deploying ESC HA Active/Standby with user data as a High Availability Active/Standby pair (Supported from ESC 4.2)

• Deploying ESC HA Active/Standby as two standalone instances and then using post configuration to set them as a High Availability pair. For more information,see the section on "Deploying ESC High

Availability Active/Standby (Standalone Instances)".

To deploy ESC HA Active/Standby on VMware vCenter or vSphere with user data as a High Availability

Active/Standby pair, define the user data file for each HA Active/Standby instance and then point the user data for each instance via ovftool. The encoding of user data is done via a set of commands in the ovftool script, and the result of this is set as a variable to the –prop:user-data= property in the ovftool.

Note The admin user/password and confd user/password properties are mandatory OVF properties. These properties cannot be defined in the user-data files.

70

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

Installing Cisco Elastic Services Controller on VMware vCenter

Deploying ESC High Availability Active/Standby with User Data (HA Active/Standby Pair)

• Define the two VMs for ESC HA Active/Standby.

User Data 1

#cloud-config ssh_pwauth: True write_files:

- path: /etc/cloud/cloud.cfg.d/sys-cfg.yaml

content: | network: version: 1 config:

- type: nameserver address:

- 161.44.124.122

- type: physical name: eth0 subnets:

- type: static address: 172.16.0.0

netmask: 255.255.255.0

routes:

- gateway: 172.16.0.0

network: 0.0.0.0

netmask: 0.0.0.0

- path: /opt/cisco/esc/esc-config/esc-config.yaml

content: | resources: confd: option: start-phase0 drbd: nodes:

- 172.16.0.0

- 172.16.1.0

run_forever: true esc_service: depend_on: filesystem type: group escmanager: depend_on:

- pgsql

- mona

- vimmanager etsi: depend_on: pgsql startup: false filesystem: depend_on: drbd:master keepalived: vip: 172.16.2.0

portal: depend_on: escmanager startup: false snmp: startup: false runcmd:

- [ cloud-init-per, once, escadm_ovf_merge, sh, -c, "/usr/bin/escadm ovf merge"]

- [ cloud-init-per, once, escservicestart, sh, -c, "chkconfig esc_service on && service esc_service start"]

User data 2

#cloud-config ssh_pwauth: True write_files:

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

71

Deploying ESC High Availability Active/Standby with User Data (HA Active/Standby Pair)

Installing Cisco Elastic Services Controller on VMware vCenter

- path: /etc/cloud/cloud.cfg.d/sys-cfg.yaml

content: | network: version: 1 config:

- type: nameserver address:

- 161.44.124.122

- type: physical name: eth0 subnets:

- type: static address: 172.16.1.0

netmask: 255.255.255.0

routes:

- gateway: 172.16.0.0

network: 0.0.0.0

netmask: 0.0.0.0

- path: /opt/cisco/esc/esc-config/esc-config.yaml

content: | resources: confd: option: start-phase0 drbd: nodes:

- 172.16.0.0

- 172.16.1.0

run_forever: true esc_service: depend_on: filesystem type: group escmanager: depend_on:

- pgsql

- mona

- vimmanager etsi: depend_on: pgsql startup: false filesystem: depend_on: drbd:master keepalived: vip: 172.16.2.0

portal: depend_on: escmanager startup: false snmp: startup: false runcmd:

- [ cloud-init-per, once, escadm_ovf_merge, sh, -c, "/usr/bin/escadm ovf merge"]

- [ cloud-init-per, once, escservicestart, sh, -c, "chkconfig esc_service on && service esc_service start"]

• OVFtool should be called twice - once for each VM instance. Each instance needs to provide a

"--prop:user-data" property to point to its hashed user-data.

• Here is an example to boot a pair of HA Active/Standby instances that use 172.16.0.0 and 172.16.1.0

(floating) IPs to its instances, and 172.16.2.0 as a KAD_VIP.

user_data_1=`cat ./user-data-1` user_data_2=`cat ./user-data-2` dec_user_data_1=`echo "$user_data_1" | base64 | tr -d '[:space:]'` dec_user_data_2=`echo "$user_data_2" | base64 | tr -d '[:space:]'`

# vcenter-16 is the developer lab for vmware5

72

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

Installing Cisco Elastic Services Controller on VMware vCenter

Deploying ESC High Availability Active/Standby with User Data (HA Active/Standby Pair)

#

#

ESC_OVA=/scratch/BUILD-${ESC_IMAGE}/BUILD-${ESC_IMAGE}/ESC-${ESC_IMAGE}.ova

# All valid deployment options:

2CPU-4GB

4CPU-8GB (default)

#

#

4CPU-8GB-2Net

4CPU-8GB-3Net

DEPLOYMENT_OPTION="4CPU-8GB-2Net" deploy_vmware_vm1() {

/usr/bin/ovftool \

--powerOn \

--acceptAllEulas \

--noSSLVerify \

--datastore=$VM_WARE_DATASTORE_NAME \

--diskMode=thin \

--name=$INSTANCE_NAME"-0" \

--deploymentOption=$DEPLOYMENT_OPTION \

--vmFolder=$FOLDER \

--prop:admin_username=$ESC_VM_USERNAME --prop:admin_password=$ESC_VM_PASSWORD \

--prop:esc_hostname=$INSTANCE_NAME"-0" \

--prop:rest_username=$REST_USERNAME \

--prop:rest_password=$REST_PASSWORD \

--prop:portal_username=$PORTAL_USERNAME \

--prop:portal_password=$PORTAL_PASSWORD \

--prop:confd_admin_username=$CONFD_USERNAME \

--prop:confd_admin_password=$CONFD_PASSWORD \

--prop:vmware_vcenter_port=$VMWARE_VCENTER_PORT \

--prop:vmware_vcenter_ip=$VM_WARE_VCENTER_IP \

--prop:vmware_datastore_host=$VM_WARE_DATASTORE_HOST \

--prop:vmware_datacenter_name=$VM_WARE_DATACENTER_NAME \

--prop:vmware_vcenter_username=$VM_WARE_VCENTER_USERNAME \

--prop:vmware_datastore_name=$VM_WARE_DATASTORE_NAME \

--prop:vmware_vcenter_password=$VM_WARE_VCENTER_PASSWORD \

--prop:net1_ip=$NET1_IP1 \

--prop:net2_ip=$NET2_IP1 \

--prop:gateway=$ESC_GATEWAY \

--prop:https_rest=$HTTPS_REST \

--prop:user-data=$dec_user_data_1 \

--net:"Network1=VM Network" --net:"Network2=MgtNetwork" --net:"Network3=VNFNetwork" \

$ESC_OVA vi://$VM_WARE_VCENTER_USERNAME:$VM_WARE_VCENTER_PASSWORD@$VM_WARE_VCENTER_IP/

$VM_WARE_DATACENTER_NAME/host/$VM_WARE_DATASTORE_CLUSTER

} deploy_vmware_vm2() {

/usr/bin/ovftool \

--powerOn \

--acceptAllEulas \

--noSSLVerify \

--datastore=$VM_WARE_DATASTORE_NAME \

--diskMode=thin \

--name=$INSTANCE_NAME"-1" \

--deploymentOption=$DEPLOYMENT_OPTION \

--vmFolder=$FOLDER \

--prop:admin_username=$ESC_VM_USERNAME --prop:admin_password=$ESC_VM_PASSWORD \

--prop:esc_hostname=$INSTANCE_NAME"-1" \

--prop:rest_username=$REST_USERNAME \

--prop:rest_password=$REST_PASSWORD \

--prop:portal_username=$PORTAL_USERNAME \

--prop:portal_password=$PORTAL_PASSWORD \

--prop:confd_admin_username=$CONFD_USERNAME \

--prop:confd_admin_password=$CONFD_PASSWORD \

--prop:vmware_vcenter_port=$VMWARE_VCENTER_PORT \

--prop:vmware_vcenter_ip=$VM_WARE_VCENTER_IP \

--prop:vmware_datastore_host=$VM_WARE_DATASTORE_HOST \

--prop:vmware_datacenter_name=$VM_WARE_DATACENTER_NAME \

--prop:vmware_vcenter_username=$VM_WARE_VCENTER_USERNAME \

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

73

Installing Cisco Elastic Services Controller on VMware vCenter

Deploying ESC High Availability Active/Standby (Standalone Instances)

--prop:vmware_datastore_name=$VM_WARE_DATASTORE_NAME \

--prop:vmware_vcenter_password=$VM_WARE_VCENTER_PASSWORD \

--prop:net1_ip=$NET1_IP2 \

--prop:net2_ip=$NET2_IP2 \

--prop:gateway=$ESC_GATEWAY \

--prop:https_rest=$HTTPS_REST \

--prop:user-data=$dec_user_data_2 \

--net:"Network1=VM Network" --net:"Network2=MgtNetwork" --net:"Network3=VNFNetwork" \

$ESC_OVA vi://$VM_WARE_VCENTER_USERNAME:$VM_WARE_VCENTER_PASSWORD@$VM_WARE_VCENTER_IP/

$VM_WARE_DATACENTER_NAME/host/$VM_WARE_DATASTORE_CLUSTER

} deploy_vmware_vm1 deploy_vmware_vm2

• Once the VMs are deployed successfully, you can check the status of ESC HA Active/Standby. You will find that one VM instance is booted as MASTER while the other VM instance is a BACKUP.

Deploying ESC High Availability Active/Standby (Standalone

Instances)

To deploy ESC HA Active/Standby on VMware vCenter or vSphere, two separate standalone nodes need to be installed first. After the standalone ESC instances are installed, reconfigure these nodes to turn them into

Primary and Standby using the following:

• kad_vip

• kad_vif

• ha_node_list

Note • On each ESC VM, we need to run escadm tool to configure ESC HA Active/Standby parameters and then reload and restart the escadm service.

• When you are deploying ESC HA Active/Standby, the kad_vip argument allows end users to access the

Primary ESC instance.

Procedure

Step 1

Step 2

Log in to the ESC Standalone instances.

As an admin user, run the escadm tool on both the Primary and Standby instances and provide the corresponding arguments.

• kad_vip — Specifies the IP address for Keepalived VIP (virtual IP) plus the interface of Keepalived VIP

[ESC-HA Active/Standby]

• kad_vif — Specifies the interface for Keepalived virtual IP and keepalived VRRP [ESC-HA

Active/Standby]. You can also use this argument to only specify the interface for keepalived VRRP, if the VIP interface is already specified using the kad_vip argument.

74

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

Installing Cisco Elastic Services Controller on VMware vCenter

Important Notes for ESC HA Active/Standby

• ha_node_list — Specifies list of IP addresses for HA Active/Standby nodes in the Primary/Standby cluster for DRDB synchronization. This argument is utilized for replication-based HA Active/Standby solution only. For ESC instances with multiple network interfaces, the IP addresses should be within the network that --kad_vif argument specifies .

Step 3

Step 4

Step 5

$ sudo escadm ha set --kad_vip= <ESC_HA_VIP> --kad_vif= <ESC_KEEPALIVE_IF> --ha_node_list=

<ESC_NODE_1_IP> <ESC_NODE_2_IP>

$ sudo escadm reload

$ sudo escadm restart

After the restart, one ESC VM should be in Primary state and the other one should be in Standby state.

Add the VIP to the allowed address pairs for both VMs so that the VIP is reachable from outside.

Verify the status of each ESC instance.

# sudo escadm status

The following table lists few other command to check the status:

Status

ESC HA Active/Standby Role

CLI Commands cat /opt/cisco/esc/keepalived_state

ESC Health

ESC Service Status sudo escadm health

If you want to see more details (such as status of the

VIM manager, SNMP, portal, ESC manager, keepalived status and so on), add '–v': sudo escadm status --v

To check the detailed status, check the

/var/log/esc/escadm.log

Important Notes for ESC HA Active/Standby

• The HA Active/Standby failover takes about 2 to 5 minutes based on the number of managed VNFs to be operational. ESC service will not be available during the switchover time.

• When the switchover is triggered during transactions, all incomplete transactions will be dropped. The requests should be re-sent by Northbound interface if it does not receive any response from ESC.

Troubleshooting High Availability Active/Standby

• Check for network failures. If a network problem occurs, you must check the following details:

• The IP address assigned is correct, and is based on the OpenStack configuration.

• The gateway for each network interface must be pinged.

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide

75

Installing Cisco Elastic Services Controller on VMware vCenter

Troubleshooting High Availability Active/Standby

• Check the logs for troubleshooting:

• The ESC manager log at /var/log/esc/escmanager.log

• The KeepAliveD log at /var/log/messages by grep keepalived

• The ESC service status log at /var/log/esc/escadm.log

76

Cisco Elastic Services Controller 5.2 Install and Upgrade Guide