The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
This procedure describes how to install Open SDN Controller on VMware ESXi hypervisors.
Hostname resolution is recommended, but not required, for the installation. If you decide to make use of it, specify a fully qualified domain name either in the Deploy OVF Template wizard’s Properties page or the /etc/hosts file.
The config field in the Deploy OVF Template wizard’s Properties page can safely be left blank.
If you are setting up a 3-node cluster, you also need to complete Step 3 for the other 2 nodes in the cluster.
When configuring Open SDN controller from the browser, use only its IP address in the address bar and configuration fields. Do not use its FQDN name.
If you are using a multiple Network Interface Card (NIC) setup, have the IP addresses for the second and third NICs ready.
Have values for the following controller settings ready:
IP address
Hostname
Netmask
Gateway address
DNS server addresses (recommended, but not mandatory)
NTP server address (recommended, but not mandatory)
You will need these for Step 3i.
Complete the following procedure to install Open SDN Controller on a virtual machine using Oracle VM VirtualBox. When configuring Open SDN Controller from the browser, use only its IP address in the address bar and configuration fields. Do not use its FQDN name.
During the installation process, you can choose one of the following cluster configuration modes:
When Simple mode is selected, a cluster operates just as it did in previous Open SDN Controller releases. If you want to take things a step further, you can also specify a virtual IP address for use with that cluster. Doing so accomplishes two things: First, it enables either a user accessing the Open SDN Controller GUI or an application communicating with Open SDN Controller via REST APIs to access the system using a single IP address. And second, it provides built-in high availability (HA) by automatically associating the virtual IP address with an another active cluster node if the node that is currently associated with the virtual IP address goes down. In this mode, Open SDN Controller automatically assigns the same priority to each cluster node and chooses the best available node to associate the virtual IP address with.
When Enhanced mode is selected, you are required to specify a virtual IP address for cluster use. Doing so provides the same benefits described for Simple mode: system access with a single IP address and HA. However, there are a few key differences between the two modes:
In Enhanced mode, the cluster can continue to operate even if only one node is active. In Simple mode, at least 2 nodes need to be active at any given time.
Unlike Simple mode, Enhanced mode allows you to assign priority settings to cluster nodes as you see fit.
For more information on virtual IP address configuration, see Virtual IP Address Configuration Settings.
The following table describes the settings you need to specify when configuring a virtual IP address for use with an Open SDN Controller cluster in the setup wizard's Virtual IP Configuration page. Note than you can enter the settings for multiple BGP routers (if necessary).