The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in
the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an
additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Warranty
WARRANTY STATEMENT: See the warranty information sheet provided in the product box and available online.
Table of Contents
About This Guide...................................................................................................................................... 6
Running and Configuring VRS .................................................................................................................. 59
Specifying the Active and Standby HP VSCs.......................................................................................... 59
7 Support and Other Resources...................................................................... 61
Gather information before contacting an authorized support..........................................................................61
How to contact HP ...................................................................................................................................61
Software technical support and software updates.........................................................................................61
Care Packs ....................................................................................................................................... 62
Related information................................................................................................................................. 62
9 Appendix: Emulated Ethernet NIC Notes ...................................................... 66
Table of Contents5
About This Guide
The scope of this manual is to describe the installation process for HP Distributed Cloud
Networking (DCN).
Audience
This manual is intended for system administrators who are responsible for installing and
configuring the HP DCN software.
6
1 HP DCN: Overview and Infrastructure
This chapter provides an overview of HP Distributed Cloud Networking (DCN) 3.0.R2 and of
the infrastructure required to implement the DCN solution. It also gives a brief overview of the
installation process itself.
Topics in this chapter include:
• HP DCN Overview
• HP DCN Infrastructure Requirements and Recommendations
• Data Center IP Network
• NTP Infrastructure
• Domain Name System
• Certificate Authority
• HP DCN Installation Overview
HP DCN Overview
HP DCN is a Software-Defined Networking (SDN) solution that enhances data center (DC)
network virtualization by automatically establishing connectivity between compute resources
upon their creation. Leveraging programmable business logic and a powerful policy engine,
HP DCN provides an open and highly responsive solution that scales to meet the stringent
needs of massive multi-tenant DCs. HP DCN is a software solution that can be deployed over
an existing DC IP network fabric. Figure 1 illustrates the logical architecture of the HP DCN
solution.
Figure1:HPDCNArchitectureandComponents
HP DCN Overview7
There are three main components in the HP DCN solution: HP Virtualized Services Directory
(HP VSD), HP Virtualized Services Controller (HP VSC) and HP Virtual Routing and Switching
(HP VRS).
HP Virtualized Services Directory
HP VSD is a programmable policy and analytics engine that provides a flexible and
hierarchical network policy framework that enables IT administrators to define and enforce
resource policies.
HP VSD contains a multi-tenant service directory which supports role-based administration of
users, computers, and network resources. It also manages network resource assignments such
as IP and MAC addresses.
HP VSD enables the definition of sophisticated statistics rules such as:
• collection frequencies
• rolling averages and samples
• threshold crossing alerts (TCAs).
When a TCA occurs it will trigger an event that can be exported to external systems
through a generic messaging bus.
Statistics are aggregated over hours, days and months and stored in a Hadoop® analytics
cluster to facilitate data mining and performance reporting.
HP VSD is composed of many components and modules, but all required components can run
on a single Linux server or in a single Linux virtual machine. Redundancy requires multiple
servers or VMs.
To get a license key to activate your HP VSD, contact your HP Sales Representative.
HP Virtualized Services Controller
HP VSC functions as the robust network control plane for DCs, maintaining a full view of pertenant network and service topologies. Through the HP VSC, virtual routing and switching
constructs are established to program the network forwarding plane, HP VRS, using the
OpenFlow™ protocol.
The HP VSC communicates with the VSD policy engine using Extensible Messaging and
Presence Protocol (XMPP). An ejabberd XMPP server/cluster is used to distribute messages
between the HP VSD and HP VSC entities.
Multiple HP VSC instances can be federated within and across DCs by leveraging MP-BGP.
The HP VSC is based on HP DCN Operating System (DCNOS) and runs in a virtual machine
environment.
HP Virtual Routing and Switching
HP VRS is an enhanced Open vSwitch (OVS) implementation that constitutes the network
forwarding plane. It encapsulates and de-encapsulates user traffic, enforcing L2-L4 traffic
policies as defined by the HP VSD. The HP VRS tracks VM creation, migration and deletion
events in order to dynamically adjust network connectivity.
8HP DCN: Overview and Infrastructure
HP VRS-G
For low volume deployments the software based HP VRS Gateway (VRS-G) module
incorporates bare metal as virtualized extensions to the datacenter.
HP DCN Infrastructure Requirements and
Recommendations
In order to make use of the HP DCN, the data center environment must meet some key
requirements as described in the following sections.
Data Center IP Network
HP VSP can be used in any data center with an IP network. HP VSC actively participates in the
IP routing infrastructure. HP VSCs can run OSPF or IS-IS for the IGP in addition to BGP, but
integration with the IGP is not mandatory.
BGP is used to form a federation of HP VSCs and synchronize the HP VSP network information.
In addition, BGP is also used to exchange routing information with the data center provider
edge router.
NTP Infrastructure
Because HP VSP is a distributed system, it is important that the different elements have a
reliable reference clock to ensure the messages exchanged between the elements have
meaningful timestamps. HP VSP relies on each of the elements having clocks synchronized with
NTP.
The HP VSD and HP VRS applications rely on the NTP facilities provided by the host operating
system. The HP VSC, which is based on HP DCN OS, has an NTP client.
HP recommends having at least three NTP reference clocks configured for each system.
Domain Name System
In scaled HP VSP deployments, the HP VSD functional elements can be distributed across
machines into clusters of machines where the failover and load sharing mechanisms for the
clusters rely on being referenced as a single DNS entity.
Certificate Authority
The northbound ReST API on HP VSD is accessed within an SSL session. The HP VSD is able to
use a self-signed certificate, but having a certificate from a certificate authority will enable
client applications to avoid processing security warnings about unrecognized certificate
authorities.
HP DCN Installation Overview
Installing HP DCN consists of installing the three software components (HP VSD, HP VSC, and
HP VRS) and configuring their interfaces to establish connectivity between them.
HP DCN Infrastructure Requirements and Recommendations9
Figure2:InstallationSetup
Figure 2 diagrams the installation of the HP VSP components and shows how they
communicate with each other. The labeled interfaces are referenced in the installation
instructions. The diagram could be used to map out the topology you plan to use for your own
installation.
The recommended order for installing the software is the order presented in this guide because
each newly installed software item component provides the infrastructure to communicate with
the next component on the list.
After installing HP DCN, configure policies in the HP VSD to derive full benefit from the system.
10HP DCN: Overview and Infrastructure
2 HP DCN Software Installation
Topics in this chapter include:
• HP VSD Hardware and Software Requirements
• HP VSD Installation Overview
• HP VSD Installation Using QCow2 Image
• HP VSD Installation Using ISO Disc Image
• Import Certificates on the Servers
• Example of Load Balancer Configuration
HP VSD Hardware and Software Requirements
Installing HP VSD software requires:
• A hypervisor of the specifications set out in the Release Notes
• A mechanism to access the graphical console of the HP VSD appliance (e.g. VNC)
• IP address for the HP VSD appliance(s) and host name(s) defined in DNS and accessible to
all VSP components.
For a license key to activate HP VSD once installed, contact your HP Sales Representative.
HP VSD Installation Overview
The procedures set out here assume installation on a hypervisor running KVM.
Installation Types
There are two types of installation, standalone and high availability.
High Availability
HP VSD High Availability is intended to guard against single-failure scenarios. High
availability for HP VSD is implemented as a 3 + 1 node cluster as shown in Figure 3.
For high availability of the HP VSD nodes, it is necessary to ensure each VSD node has
redundant network and power, so that no single failure can cause loss of connectivity to more
than one HP VSD node. Therefore, each HP VSD node should be installed on a different
hypervisor.
The cluster consists of three HP VSD nodes and one statistics master node (Name node). In
addition, a Load Balancer (not supplied) is optional to load balance across the HP VSD nodes
for the REST API.
Installation Methods
The standard method of installation of HP VSD uses the pre-installed appliance. This appliance
is distributed in four formats.
• a ready-to-use QCow2 VM image for KVM hypervisor deployment (see HP VSD Installation
Using QCow2 Image
)
• a ready-to-use image for VMWare hypervisor deployment
• a ready-to-use image for OVA hypervisor deployment
• an ISO disc image (see HP VSD Installation Using ISO Disc Image)
Table 1 provides an overview of the installation tasks with links to each.
Notes on Reinstallation: MySQL Root Password
The password for the MySQL root user is not set after installation, because the HP VSD
installation scripts require that the root user not have a MySQL password.
Reinstalling HP VSD
To reinstall HP VSD, before uninstalling:
1. Set the root password to ‘no password.’ On each node, run:
mysql -uroot -p<current password> -e “update mysql.user set
password=PASSWORD(‘’) where user=’root’; flush privileges;”
2. Uninstall all HP VSD nodes.
3. Install all HP VSD nodes following the procedure specified for your HP VSD version and
installation type.
4. Verify that installation was successful.
5. Set the root password:
To set the root password for the first time, on each node, run:
12HP DCN Software Installation
mysql -e “update mysql.user set password=PASSWORD <NEW PASSWORD>
WHERE USER=’ROOT’; FLUSH PRIVILEGES;”
To change the root password, on each node, run:
mysql -uroot -p<current password> -e “update mysql.user set
password=PASSWORD <new password> where user =’root’; flush privileges;”
Table1:HPVSDInstallationOverview
qcow2ISO
Set Up Appliance VMsSet Up VM for ISO
Extract and Mount ISO Image
Connect to Appliance VMs
Configure Networking
Configure DNS Server
Configure NTP Server
Install HP VSD using qcow2Install HP VSD Using ISO
HP VSD Installation Using QCow2 Image
The following instructions are for a High Availability installation. For a standalone installation,
use the same instructions to install one HP VSD on a single node.
1.
Set Up Appliance VMs
2. Connect to Appliance VMs
3. Configure Networking
4. Configure DNS Server
5. Configure NTP Server
Install HP VSD using qcow2
6.
Set Up Appliance VMs
1. Unzip all the HP VSD tar files to a temporary location.
2. If you do not already have virt-install on your hypervisor(s), run this command to put it in:
yum install virt-install
3. Copy the HP VSD qcow2 image to the KVM hypervisor image location <TTY>/var/lib/
libvirt/images/on each hypervisor.
4. Create appliance VMs.
In the example below, a VM is created for each of four HP VSD nodes. If you are doing a
standalone installation, create only
myh1.
Note: “listen=0.0.0.0” results in KVM responding to VNC connection requests on all IP
interfaces. Depending on your network configuration, this may be a security issue.
HP VSD Installation Using QCow2 Image13
Consider removing “listen=0.0.0.0” and using an alternative method (for
example,
The HP VSD appliance VM requires console access for initial configuration. Either:
14HP DCN Software Installation
• Connect Via VNC)
• Connect Via virsh Console).
Connect Via VNC
Using a VNC client (e.g. RealVNC, TightVNC) or other console access mechanism, connect to
the HP VSD appliance consoles and log in using the default username and password:
login: root
password: default password
Connect Via virsh Console
Using a virsh console domain command, connect to the HP VSD appliance consoles and
log in using the default username and password.
3. Ping the gateway (in this example, 192.168.100.1).
/etc/init.d/network restart
4. Ping the gateway (in this example, 192.168.100.1).
ping 192.168.100.1
Configure DNS Server
dhcp” with “static”.
Set up the fully qualified names for all the nodes in the cluster (unless you are doing a
standalone installation, in which case one FQDN is obviously sufficient). Reverse DNS lookup
for the HP VSD nodes should also be set up.
Note: If the Service Records (SRV) for the XMPP cluster are not in the Domain Name
Server (DNS), the script will generate them. An administrator must then load them
into the DNS server. The XMPP cluster name is typically xmpp host in the domain,
HP VSD Installation Using QCow2 Image15
for example, xmpp.example.com. To use a different host name run the install.sh
with the -x option.
TheDNSserverinthisexampleis10.10.10.100.
Test DNSandreverseDNSfromeachVSDnode(VM).
1. Set up the fully qualified names for the nodes in the DNS server forward named file as per
the following example:
myh1.myd.example.com. 604800 IN A 192.168.10.101
myh2.myd.example.com. 604800 IN A 192.168.10.102
myh3.myd.example.com. 604800 IN A 192.168.10.103
myname.myd.example.com. 604800 IN A 192.168.10.104
The installation script verifies the DNS forward named file records.
2. From the HP VSD node, verify the SRV record as follows:
; hosts
myh1 A 192.168.10.101
myh2 A 192.168.10.102
myh3 A 192.168.10.103
myname A 192.168.10.104
; xmpp nodes
xmpp A 192.168.10.101
xmpp A 192.168.10.102
xmpp A 192.168.10.103
; SRV records for xmpp.example.com
_xmpp-client._tcp.xmpp.example.com. IN SRV 10 0 5222 myh1.myd.example.com.
_xmpp-client._tcp.xmpp.example.com. IN SRV 10 0 5222 myh2.myd.example.com.
_xmpp-client._tcp.xmpp.example.com. IN SRV 10 0 5222 myh3.myd.example.com.
16HP DCN Software Installation
Configure NTP Server
Include one or more NTP servers in the /etc/ntp.conf file. For example, edit the NTP file and
add servers as follows, restarting the NTPD service to put these parameters into effect:
server 10.10.0.10
server 192.16.10.10
server 192.16.20.10
Install HP VSD using qcow2
The install script is interactive. Node 1 is the master node, and it serves as a template for the
other nodes.
Note: HP VSD consists of several components and providing high availability for each of
these components can be quite complex. It is imperative that the installation and
powering-on of each node be done in the order specified here.
1. Install HP VSD on Node 1.
The install script checks for the XMPP proxy entry in your DNS. Run
----------------------------------------------------| V I R T U A L S E R V I C E S D I R E C T O R Y |
| (c) 2014 HP Networks |
----------------------------------------------------VSD supports two configurations:
1) HA, consisting of 2 redundant installs of VSD with an optional statistics
server.
2) Standalone, where all services are installed on a single machine.
Is this a redundant (r) or standalone (s) installation [r|s]? (default=s):
Is this install the first (1), second (2), third (3) or cluster name node (t)
[1|2|3|t]: 1
Please enter the fully qualified domain name (fqdn) for this node:
, substituting your own XMPP server name.
<TTY>/opt/vsd/
r
myh1.myd.example.com
Install VSD on the 1st HA node myh1.myd.example.com ...
What is the fully qualified domain name for the 2nd node of VSD:
myh2.myd.example.com
What is the fully qualified domain name for the 3rd node of VSD:
myh3.myd.example.com
What is the fully qualified domain name for the cluster name node of VSD:
myname.myd.example.com
What is the fully qualified domain name for the load balancer (if any)
(default=none):
Node 1: myh1.myd.example.com
Node 2: myh2.myd.example.com
Node 3: myh3.myd.example.com
Name Node: myname.myd.example.com
XMPP: xmpp.myd.example.com
Continue [y|n]? (default=y):
Starting VSD installation. This may take as long as 20 minutes in some
situations ...
A self-signed certificate has been generated to get you started using VSD.
You may import one from a certificate authority later.
VSD installed on this host and the services have started.
Please install VSD on myh2.myd.example.com to complete the installation.
y
HP VSD Installation Using QCow2 Image17
2. Install VSD on Node 2:
[root@myh2 ~]# <TTY>/opt/vsd/install.sh
----------------------------------------------------| V I R T U A L S E R V I C E S D I R E C T O R Y |
| (c) 2014 HP Networks |
----------------------------------------------------VSD supports two configurations:
1) HA, consisting of 3 redundant installs of VSD with a cluster name node
server.
2) Standalone, where all services are installed on a single machine.
Is this a redundant (r) or standalone (s) installation [r|s]? (default=s):
Is this install the first (1), second (2), third (3) or cluster name node (t)
[1|2|3|t]:
Please enter the fully qualified domain name for the 1st node of VSD:
myh1.myd.example.com
Install VSD on the 2nd HA node myh2.myd.example.com ...
Node 2: myh2.myd.example.com
Continue [y|n]? (default=y):
Starting VSD installation. This may take as long as 20 minutes in some
situations ...
A self-signed certificate has been generated to get you started using VSD.
You may import one from a certificate authority later.
VSD installed on this host and the services have started.
2
r
3. Follow the interactive script to install HP VSD on Node 3.
4. Follow the interactive script to install HP VSD on the Name Node.
5. Verify that your HP VSD(s) are up and running by using the following command:
service vsd status
6. See Import Certificates on the Servers.
HP VSD Installation Using ISO Disc Image
Note: Consult the Release Notes for the ISO installation requirements.
The following instructions are for a High Availability installation. For a standalone installation,
use the same instructions to install one HP VSD on a single node.
1.
Set Up VM for ISO
2. Extract and Mount ISO Image
3. Configure Networking
4. Configure DNS Server
5. Configure NTP Server
6. Install HP VSD Using ISO
Set Up VM for ISO
Note: “listen=0.0.0.0” results in KVM responding to VNC connection requests on
all IP interfaces. Depending on your network configuration, this may be a security
issue. Consider removing “listen=0.0.0.0” and using an alternative method
(for example,
18HP DCN Software Installation
virt-manager or SSH tunnel) to obtain console access.
1. Bring up a VM named myh1 using 24 GB RAM and 6 logical cores with the following
commands:
----------------------------------------------------| V I R T U A L S E R V I C E S D I R E C T O R Y |
| (c) 2014 HP Networks |
----------------------------------------------------VSD supports two configurations:
1) HA, consisting of 2 redundant installs of VSD with an optional statistics
server.
2) Standalone, where all services are installed on a single machine.
Is this a redundant (r) or standalone (s) installation [r|s]? (default=s):
Is this install the first (1), second (2), third (3) or cluster name node (t)
[1|2|3|t]:
Please enter the fully qualified domain name (fqdn) for this node:
myh1.myd.example.com
Install VSD on the 1st HA node myh1.myd.example.com ...
What is the fully qualified domain name for the 2nd node of VSD:
myh2.myd.example.com
What is the fully qualified domain name for the 3rd node of VSD:
myh3.myd.example.com
What is the fully qualified domain name for the cluster name node of VSD:
myname.myd.example.com
What is the fully qualified domain name for the load balancer (if any)
1
, substituting your own XMPP server name.
r
HP VSD Installation Using QCow2 Image19
(default=none):
Node 1: myh1.myd.example.com
Node 2: myh2.myd.example.com
Node 3: myh3.myd.example.com
Name Node: myname.myd.example.com
XMPP: xmpp.myd.example.com
Continue [y|n]? (default=y):
Starting VSD installation. This may take as long as 20 minutes in some
situations ...
A self-signed certificate has been generated to get you started using VSD.
You may import one from a certificate authority later.
VSD installed on this host and the services have started.
Please install VSD on myh2.myd.example.com to complete the installation.
y
2. Install HP VSD on Node 2:
[root@myh2 ~]# /media/CDROM/install.sh
----------------------------------------------------| V I R T U A L S E R V I C E S D I R E C T O R Y |
| (c) 2014 HP Networks |
----------------------------------------------------VSD supports two configurations:
1) HA, consisting of 3 redundant installs of VSD with a cluster name node
server.
2) Standalone, where all services are installed on a single machine.
Is this a redundant (r) or standalone (s) installation [r|s]? (default=s):
Is this install the first (1), second (2), third (3) or cluster name node (t)
[1|2|3|t]:
Please enter the fully qualified domain name for the 1st node of VSD:
2
r
myh1.myd.example.com
Install VSD on the 2nd HA node myh2.myd.example.com ...
Node 2: myh2.myd.example.com
Continue [y|n]? (default=y):
Starting VSD installation. This may take as long as 20 minutes in some
situations ...
A self-signed certificate has been generated to get you started using VSD.
You may import one from a certificate authority later.
VSD installed on this host and the services have started.
3. Follow the interactive script to install VSD on Node 3.
4. Follow the interactive script to install VSD on the Name Node.
5. Verify that your VSD(s) are up and running by using the following command:
service vsd status
Import Certificates on the Servers
On each HP VSD host, installation generates a self-signed certificate. If you want to import an
official certificate signed by a certificate authority, use the
• Import a certificate generated by a Certificate Authority:
# ./set-cert.sh -r -i certificateFilename
• Generate and use a self-signed certificate if you do not run a proxy:
# ./set-cert.sh -r
20HP DCN Software Installation
set-cert.sh script:
• Generate and use a self-signed certificate if you run a proxy:
# ./set-cert.sh -r -p proxyHostname
Select an option and generate or import the certificate to Node 1. If you are running HA VSD,
import it to Nodes 2 and 3 as well.
LDAP Store
If you are using an LDAP store, see Using an LDAP Store.
Example of Load Balancer Configuration
frontend vsdha *:443
default_backend vsdhaapp
backend vsdhaapp
mode tcp
balance source
server c1 myh1.myd.example.com:8443 check
server c2 myh2.myd.example.com:8443 check
server c3 myh3.myd.example.com:8443 check