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.
The topics in this section describe how to use the ShellAdmin console to configure Cisco ICFPP nodes for multiple-node clusters.
To configure a Cisco ICFPP virtual appliance that has been installed using the Standalone Mode role for a multiple-node cluster, you must first configure it as a primary node or service node by using the ShellAdmin console. This procedure describes how to configure a standalone node as a primary node. To configure a standalone node as a service node, see Configuring a Service Node.
Install a Cisco ICFPP virtual appliance using the Standalone Mode role.
To configure a Cisco ICFPP virtual appliance that has been installed using the Standalone Mode role for a multiple-node cluster, you must first configure it as a primary node or as a service node by using the ShellAdmin console. This procedure describes how to configure a standalone node as a service node. To configure a standalone node as a primary node, see Configuring a Primary Node.
Install a Cisco ICFPP virtual appliance using the Standalone role.
Obtain the IP address of a primary node in the cluster or the virtual IP address (VIP) of an HA pair in the cluster.
Back up any data in the virtual appliance database that you want to keep. When the virtual appliance is reconfigured as a service node, the existing data will be deleted.
If you did not configure an NFS server for a Cisco ICFPP virtual appliance when you installed it, you can configure the appliance for NFS by using the ShellAdmin console.
We recommend that you configure an NFS server for all Cisco ICFPP nodes. If NFS is not configured, all VM images that are uploaded from Cisco Intercloud Fabric Director are stored on the local disk. If NFS is not configured and a node fails, any images stored on that node will not be available and could cause template creation and VM migration to fail if the node is part of a cluster.After you deploy Cisco ICFPP virtual appliances, you can configure them for high availability (HA) by using the ShellAdmin console.
When configuring HA:
Deploy or configure two Cisco ICFPP virtual appliances as primary nodes.
Identify a virtual IP (VIP) address for the HA pair.
Determine which node will be the active node and which will be the standby node.
On the node that will be the standby node, move any existing data that you want to save to another location.
For OpenStack environments, continue with Configuring VIP Access for HA Nodes in OpenStack.
After Cisco ICFPP primary nodes are configured for HA, the virtual IP address (VIP) is used in the event of failover. However, OpenStack Neutron does not allow a host to accept packets with an IP address in the packet header that does not match the destination host IP address. As a result, packets sent to the VIP do not reach the node to which the VIP is assigned. To allow the packets to reach HA pair, the VIP must be added as an allowed address for both nodes (active and standby) in the HA pair.
This procedure describes how to configure VIP access on the nodes in the HA pair by using the OpenStack neutron port-update command. For more information, see the OpenStack documentation at docs.openstack.org.
Cisco ICFPP enables you to move from a standalone configuration to a cluster. Moving from a standalone configuration to a cluster involves moving the database contents from the existing standalone node to the active HA node in the cluster as described in this procedure.
After moving the database contents, you can configure and test the cluster setup without modifying or affecting the standalone setup. For more information about configuring a multiple-node cluster, see Deployment Workflows.
Step 1 | In the ShellAdmin console for the standalone node, back up the existing database as follows: | ||
Step 2 | Deploy or
configure two primary nodes by using any of the following methods:
| ||
Step 3 | Restore the backed-up database from Step 1 onto one of the primary nodes: | ||
Step 4 | In the
ShellAdmin console, configure the two primary nodes as an HA pair.
For more information, see Configuring HA. | ||
Step 5 | Configure service nodes for the cluster. For more information, see Configuring a Service Node. |
Cisco ICFPP enables you to configure an HA pair and then restore a database from an existing standalone node to the HA pair.
Note | You must stop and start services in the sequence described in this procedure to successfully restore the database on the HA pair. |
After configuring Cisco ICFPP for HA, you can view the configuration details, check the status of the active and standby nodes, and view detailed replication status.
After configuring Cisco ICFPP for HA, Cisco ICFPP checks HA status every five minutes. Any warning or failure messages that are issued are included in the log file for syslog messages. This log file commonly resides in /var/log/ with the name messages. To view these messages, log in as root and use a text editor as described in this procedure.