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 ShellAdmin console provides many options for managing and configuring Cisco ICFPP. You can access the ShellAdmin console by using SSH as described in this procedure.
The ShellAdmin console enables you to execute common administration tasks such as changing your password, stopping and starting services, generating log and report data, and performing other system-related tasks.
You can view the Cisco ICFPP product version by choosing the Show Version option. The product version number uses the format version-build-patch where:
version is the product release, such as 2.3.1.
build is the build number, such as 206.
patch is the patch applied to the build, such as p208.
This information is required for debugging purposes.
You can start all Cisco ICFPP services by choosing the Start Services option.
Note | Services started in the background are not displayed. |
You can stop all Cisco ICFPP services by choosing the Stop Services option.
The Display Services Status option enables you to view the following services and their status:
You can change the password for the Cisco ICFPP shelladmin account by choosing the Change ShellAdmin Password option.
You can synchronize the system time to the hardware time and a network time protocol (NTP) server by choosing the Time Sync option.
You can use the ShellAdmin console to test network connectivity by pinging a host by hostname or IP address.
You can use the ShellAdmin console to apply Cisco ICFPP patches that include infrastructure changes. For more information or to obtain a patch file, contact your Cisco representative.
Download the patch file from Cisco. If you need assistance, contact your Cisco representative.
Place the patch file on a web server or FTP server that is accessible from Cisco ICFPP.
Review the patch release notes and README file.
Take a snapshot of the Cisco ICFPP virtual appliance.
Back up the Cisco ICFPP virtual appliance database. Although the Apply Patch option enables you to back up the database as part of the procedure, we recommend that you create a backup immediately before choosing the Apply Patch option.
The topics in this section describe how to configure Cisco ICFPP for multiple-node clusters.
The following workflow describes the high-level tasks that are required to configure a multiple-node cluster.
Step |
Task |
Related Information |
||
---|---|---|---|---|
1. |
Install a minimum of four Cisco ICFPP virtual appliances. The role that is assigned to each appliance during installation depends on whether you are using VMware or OpenStack. |
Cisco Intercloud Fabric Provider Platform Installation Guide |
||
2. |
Configure two primary nodes. |
|||
3. |
Configure two or more service nodes. |
|||
4. |
Configure additional storage. |
|||
5. |
Configure the two primary nodes for HA. |
|||
6. |
(OpenStack only) Configure VIP access. |
|||
7. |
Configure a load balancer for the service nodes in the cluster.
|
Your load balancer documentation |
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 Mode 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.
The default disk size of 100 GB for Cisco ICFPP is not sufficient for configuring Cisco ICFPP in a multiple-node cluster. As a result, you must add additional disk space before configuring a multiple-node cluster. You can use either NFS or a Cinder volume as described in the following topics:
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.
Note | If NFS is not available, you can configure a Cinder volume as described in Configuring a Cinder Volume. |
The default disk size of 100 GB for the Cisco ICFPP virtual appliance is not sufficient for configuring Cisco ICFPP in a multiple-node cluster. If you do not have access to an NFS server, you can increase the disk size by creating additional Cinder volumes. Cinder volumes that you create are formatted as physical disks and then combined to form a logical volume that can be mounted on the VM in a specific location.
Configure a Cisco ICFPP virtual appliance as a service node by using the ShellAdmin console. For more information, see Configuring a Service Node.
If you have not already done so, configure the root user password for the Cisco ICFPP service node. For more information, see Configuring Root Access.
Collect the following information:
After you deploy Cisco ICFPP virtual appliances, you can configure them for high availability (HA) by using the ShellAdmin console.
When configuring HA:
To deploy a Cisco ICFPP virtual appliance with the Primary Mode role, see the Cisco Intercloud Fabric Provider Platform Installation Guide.
To configure an existing Cisco ICFPP virtual appliance as a primary node, see Configuring a Primary Node.
Identify a virtual IP (VIP) address for the HA pair.
Determine which node will be the active node and which node 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.
Step 1 | Using SSH, log in to the ShellAdmin console of the node that will be the active node for the HA pair. |
Step 2 | At the ShellAdmin prompt, choose the Setup HA option and press Enter. A warning is displayed stating that the contents of the database on the standby node will be deleted. |
Step 3 | When prompted, enter Y to configure the node for HA. |
Step 4 | Enter A to configure the node as the active node. |
Step 5 | When prompted, enter Y to configure the node as the active node. Cisco ICFPP detects and displays the IP address of the current node. |
Step 6 | Enter Y to confirm the node IP address. |
Step 7 | Enter the standby node IP address. |
Step 8 | Enter the VIP to
use for the IP pair.
Information similar to the
following is displayed:
-------------------------------------------- HA Configuration Information: -------------------------------------------- This node will be configured as active node Active Node IP address: 123.45.1.61 Standby Node IP address: 123.45.1.62 Virtual IP address: 123.45.1.60 -------------------------------------------- Proceed with setting up HA with above configuration [y/n]: |
Step 9 | Enter Y to confirm the configuration and proceed or N to change the values. If you choose to proceed, Cisco ICFPP displays progress messages while it configures the active node for HA. |
Step 10 | While Cisco ICFPP is configuring the active node for HA, log in to the ShellAdmin console of the node that will be the standby node for the HA pair. |
Step 11 | At the ShellAdmin prompt, choose the Setup HA option and press Enter. |
Step 12 | Enter Y to configure the node for HA. |
Step 13 | Enter B to configure the node as the standby node. |
Step 14 | When prompted, enter Y to configure the node as the standby node. Cisco ICFPP detects and displays the IP address of the current node. |
Step 15 | Enter Y to confirm the node IP address. |
Step 16 | Enter the active node IP address. |
Step 17 | Enter the VIP to
use for the HA pair.
Information similar to the
following is displayed:
-------------------------------------------- HA Configuration Information: -------------------------------------------- This node will be configured as standby node Active Node IP address: 123.45.1.61 Standby Node IP address: 123.45.1.62 Virtual IP address: 123.45.1.60 -------------------------------------------- Proceed with setting up HA with above configuration [y/n]: |
Step 18 | Enter Y to confirm the configuration. Cisco ICFPP displays progress messages while it configures the standby node for HA and synchronizes the database information on both nodes. |
Step 19 | When prompted, press Enter to return to the ShellAdmin menu. |
For OpenStack environments, continue with Configuring VIP Access for HA 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.
Step 1 | Obtain a list of
networks by entering the following command:
$ neutron net-listInformation similar to the following is displayed: +--------------------------------------+----------------------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+----------------------+-----------------------------------------------------+ | 2d84eaa4-8b81-4dc8-9897-dd8ef4719f8b | public-direct-600 | 3e0b77fe-fc66-4913-bc58-7f62d4ab247a 10.203.28.0/23 | | | | 5c2f73a9-4e2f-498c-8244-6aefe5129fdd 10.203.50.0/23 | | | | ba29165f-c88a-496a-9adc-99ee90407ebe 10.203.24.0/23 | | | | d5b69780-aefb-42a6-8ba5-aaf405fb36a0 10.203.30.0/24 | | b5d8d461-74d7-45a4-a1f0-f7ac96586bd5 | Net1 | c0921b42-2896-4b32-b33e-f54db9e5a3d6 192.168.0.0/24 | | ca80ff29-4f29-49a5-aa22-549f31b09268 | public-floating-601 | 0cfde3f1-e28b-4b87-8095-e0014b0ee573 | | | | 348a808d-ce64-43bc-a9d9-c20e52d2ac06 | | | | 3784170e-5d7f-48b4-b63d-aab4a0fef769 | | ff95095f-89f0-4005-b709-70a75212d73c | icfpp-ha-123-network | 1099b814-05d9-4da0-93d1-06167db4891f 192.168.1.0/24 | +--------------------------------------+----------------------+-----------------------------------------------------+ |
Step 2 | Obtain a list of
ports on the network on which the active and standby nodes in the HA pair are
deployed by entering the following command:
$ neutron port-list -- --network_id=net_id where net_id is the identifier for the required network. In this example, the network name is icfpp-ha-123-network. $ neutron port-list -- --network_id=ff95095f-89f0-4005-b709-70a75212d73cInformation similar to the following is displayed: +--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+ | 4a439cf1-b95e-49ba-a8d6-0b03a8142dd2 | | fa:16:3e:f6:f8:a9 | {"subnet_id": "1099b814-05d9-4da0-93d1-06167db4891f", "ip_address": "192.168.1.12"} | | 93d0a69a-7bb8-4719-9ed7-63c10accd78b | | fa:16:3e:1f:7f:d2 | {"subnet_id": "1099b814-05d9-4da0-93d1-06167db4891f", "ip_address": "192.168.1.11"} | | 9d626a64-ee7c-410b-ae00-661dd275de79 | | fa:16:3e:61:81:4b | {"subnet_id": "1099b814-05d9-4da0-93d1-06167db4891f", "ip_address": "192.168.1.14"} | | cf56fd7b-2896-4e06-b520-1d2258ad6158 | | fa:16:3e:ab:27:ca | {"subnet_id": "1099b814-05d9-4da0-93d1-06167db4891f", "ip_address": "192.168.1.13"} | | d7457d29-44ba-46ef-b47a-4b94c9199902 | | fa:16:3e:ad:d0:e9 | {"subnet_id": "1099b814-05d9-4da0-93d1-06167db4891f", "ip_address": "192.168.1.15"} | +--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+ |
Step 3 | In the output of the previous step, locate the port ID for the active node. |
Step 4 | Update the port
so that it accepts traffic from the VIP by entering the following command:
$ neutron port-update active-port-id --allowed_address_pairs list=true type=dict ip_address=vip where: For example, if the IP address of the active node is 192.168.1.11 and the VIP is 192.168.1.10, the command resembles the following: $ neutron port-update 93d0a69a-7bb8-4719-9ed7-63c10accd78b --allowed_address_pairs list=true type=dict ip_address=192.168.1.10 |
Step 5 | View the port
details and confirm that the allowed_address_pairs field lists the VIP by
entering the following command:
$ neutron port-show active-port-id where active-port-id is the identifier for the port configured in the previous step. Using the current example, the command and results resemble the following: $ neutron port-show 93d0a69a-7bb8-4719-9ed7-63c10accd78b +-----------------------+-------------------------------------------------------------------------------------+ | Field | Value | +-----------------------+-------------------------------------------------------------------------------------+ | admin_state_up | True | | allowed_address_pairs | {"ip_address": "192.168.1.10", "mac_address": "fa:16:3e:1f:7f:d2"} | | device_id | b7b8eeb5-70ad-49ac-a3b4-6d8a144293a2 | | device_owner | compute:alln01-1-csi | | extra_dhcp_opts | | | fixed_ips | {"subnet_id": "1099b814-05d9-4da0-93d1-06167db4891f","ip_address": "192.168.1.11"} | | id | 93d0a69a-7bb8-4719-9ed7-63c10accd78b | | mac_address | fa:16:3e:1f:7f:d2 | | name | | | network_id | ff95095f-89f0-4005-b709-70a75212d73c | | security_groups | f995d22f-edb8-47c0-9aff-6339a15fb5be | | status | ACTIVE | | tenant_id | b1436740f8db42e39904ee9779f67eb8 | +-----------------------+-------------------------------------------------------------------------------------+ |
Step 6 | Configure the
standby node to accept VIP traffic by entering the following command:
$ neutron port-update standby-port-id --allowed_address_pairs list=true type=dict ip_address=vip where: |
Step 7 | View the port
details for the standby node and confirm that the allowed_address_pairs field
lists the VIP:
$ neutron port-show standby-port-id |
Step 8 | (Optional)
Complete the following steps to configure the VIP so that it is accessible from
an external network and so that the VIP uses a floating IP address:
|
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.
Step 1 | Log in to the ShellAdmin console for one of the nodes in the HA pair. |
Step 2 | At the menu
prompt, choose
Display
HA Status.
Information similar to the following is displayed:
Configured HA role for this node is: Active Current HA role for this node is: Active HA Configuration properties for this node are: ACTIVE_IP_ADDRESS=123.16.1.30 STANDBY_IP_ADDRESS=123.16.1.3 VIRTUAL_IP_ADDRESS=123.16.1.25 IP address of this node is: 123.16.1.30 Checking if Virtual IP Address is reachable...OK Virtual IP Address service status on this node...OK Checking DB replication from 123.16.1.30 to 123.16.1.3...OK Checking DB replication from 123.16.1.3 to 123.16.1.30...OK Do you want to view detailed replication status ? [y/n] |
Step 3 | To view
detailed information, enter
Y and press
Enter.
Information similar to the following is displayed:
Slave_IO_State : Waiting for master to send event Master_Host : 123.16.1.3 Master_User : replicator Master_Port : 3306 Connect_Retry : 60 Master_Log_File : mysql-bin.000002 Read_Master_Log_Pos : 645644 Relay_Log_File : mysqld-relay-bin.000004 Relay_Log_Pos : 361 Relay_Master_Log_File : mysql-bin.000002 Slave_IO_Running : Yes Slave_SQL_Running : Yes Replicate_Do_DB : Replicate_Ignore_DB : … |
Step 4 | Use your arrow keys to scroll through the information, and enter Q to return to the menu. |
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. |
Step 1 | Stop the VIP service on the current standby node in the HA pair as follows: |
Step 2 | Stop the VIP service on the current active node in the HA pair as follows: Stopping the VIP service on the active node in an HA pair automatically stops the Infrastructure Manager services if they are running. |
Step 3 | On the active node in the HA pair, restore the database backup obtained from the standalone node as follows: |
Step 4 | Restart the VIP service on the active node as follows: Starting the VIP service on the active node in an HA pair automatically starts the Infrastructure Manager services on that node. |
Step 5 | Restart the VIP service on the standby node in the HA pair as follows: |
If you change a virtual IP address (VIP) for an HA pair or on a primary node that supports a service node, you must reconfigure VIP as follows:
On both nodes in the HA configuration
On any service nodes that communicate with the HA pair
On any service node that has been configured to communicate with the primary node
Reconfiguring a VIP involves the following high-level tasks:
Reconfigure the VIP service on the active node in the HA pair.
Reconfigure the VIP service on the standby node in the HA pair.
Reconfigure the VIP address on service nodes that used the old VIP to communicate with either the HA pair or the primary node.
The following procedure describes how to perform these tasks.
Step 1 | Stop the VIP service on the standby node as follows: |
Step 2 | Reconfigure VIP service on the active node in the HA pair as follows:
Proceed with setting up VIP as 123.45.1.25 ? [y/n]: y ******************************************************* Updating Virtual IP Address ******************************************************* Updating Keepalived configuration for Virtual IP... Setting up new keepalived configuration for active node... Setting up IP addresses in keepalived configuration for active node... Stopping Virtual IP service, Keepalived... Starting Keepalived... Successfully reconfigured Virtual IP |
Step 3 | Reconfigure the VIP service on the standby node as follows: |
Step 4 | Reconfigure any service nodes that used the previous VIP as follows:
|
If you change the IP address of a primary node or the VIP of an HA pair that a service node uses for database services, reconfigure the service node to use the updated IP address or VIP through the ShellAdmin console.
Step 1 | In the ShellAdmin console for the service node, choose the Reconfigure Node option. |
Step 2 | When asked if you want to change the node role to configure multi-node setup, enter Y. |
Step 3 | At the submenu prompt, enter A to reconfigure the node as a service node. |
Step 4 | When prompted, enter Y to continue. |
Step 5 | When prompted,
enter the IP address of the primary node or the VIP of the HA pair that the
service node uses for database access.
Information similar to the following is displayed:
Configuring as Service Node... Stopping services before changing node role Stopping the services... Setting up current node as ICFPP service node...with remote DB IP 123.45.1.30 Disabling Database service at startup SUCCESS: Successfully changed node role to Service Node Starting services that were previously stopped... Starting the services... In order for changes to take effect logout and login back Do you want to logout [y/n]? |
Step 6 | Enter Y to log out. You are logged out of the ShellAdmin console and the GUI, and the changes are applied. Logging in again can take a few minutes while Cisco ICFPP is reconfigured. |
You can reconfigure an HA setup by using the ShellAdmin console.
When reconfiguring HA:
You must reconfigure both the active and standby nodes for HA.
Reconfiguring HA restarts all services for the current HA setup, including VIP and the database, which disrupts services for any service nodes using the HA pair.
The database on the node that you specify as the standby node in this procedure is deleted and replicates the contents of the database on the node that you specify as the active node.
Step 1 | Log into the ShellAdmin console of the active or standby node in the HA pair. |
Step 2 | At the ShellAdmin prompt, choose the Setup HA option. Cisco ICFPP displays a message stating that HA is already configured on the node, provides additional information about the HA pair, and asks if you want to reconfigure HA on the node. |
Step 3 | Enter Y to reconfigure HA. The HA reconfiguration submenu is displayed. |
Step 4 | Enter B to reconfigure the HA setup. Cisco ICFPP displays informational messages and asks if you want to continue with the reconfiguration. |
Step 5 | Enter
Y to continue.
Information similar to the following is displayed:
NOTE: The DB contents of the node being configured as the Standby node will be deleted and the Standby node DB will replicate the contents of the node configured as Active. Do you want to change this node to configure HA [y/n]? |
Step 6 | Enter Y to configure HA on the current node. |
Step 7 | At the submenu prompt, enter A to configure the node as the active node or B to configure the node as the standby node. |
Step 8 | Enter Y to continue. Cisco ICFPP detects and displays the IP address of the current node. |
Step 9 | Enter Y to confirm the node IP address. |
Step 10 | Enter the IP address for the other node in the HA pair. |
Step 11 | Enter the VIP to
use for the IP pair.
Information similar to the following is displayed:
------------------------------------------------- HA Configuration information: ------------------------------------------------- This node will be configured as active node Active Node IP address: 123.45.1.30 Standby Node IP address: 123.45.1.32 Virtual IP address: 123.45.1.25 ------------------------------------------------- Proceed with setting up HA with above configuration [y/n]: |
Step 12 | Enter Y to continue. |
Step 13 | While Cisco ICFPP is configuring the current node for HA, configure the other node in the HA pair by choosing the Setup HA option in the ShellAdmin menu and repeating the steps in this procedure. Cisco ICFPP displays progress messages as it configures the nodes for HA and synchronizes the databases on both nodes. |
Step 14 | When prompted, press Enter to return to the ShellAdmin menu. |
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.
Step 1 | In the ShellAdmin console, choose the Log in as Root option. |
Step 2 | Enter Y to confirm the login request, and enter the root account password at the prompt. |
Step 3 | Enter the
following command to view the contents of the log file:
vi /directory-path/filename where directory-path is location of the log file and filename is the name of the log file. For example, you might enter the following: vi /var/log/messages |
Step 4 | To identify
messages that pertain to HA, look for entries that contain the string
ICFPP
HA as shown in the following example:
Mar 13 03:27:13 localhost logger: ICFPP HA: MySQL replication from 123.45.67.8 to 123.45.67.9 is in WARN state Mar 13 03:27:13 localhost logger: ICFPP HA: Please use shelladmin to check HA status details Mar 13 03:27:13 localhost logger: ICFPP HA: MySQL replication from 122.33.44.5 to 122.33.44.6 is in WARN state Mar 13 03:27:13 localhost logger: ICFPP HA: Please use shelladmin to check HA status details |
Step 5 | Address any HA-related messages as needed. |
Cisco ICFPP enables you to start, stop, back up, and restore a database.
Note | This option starts the appliance database only. |
Step 1 | In the
ShellAdmin console,
choose the
Start
Database option.
Starting database..... directory (/var/lib/mysql/data/confmgr_production) exists directory (/var/lib/mysql/data/db_private_admin) exists the file (/var/lib/mysql/data/ib_logfile1) exists the file (/var/lib/mysql/data/ib_logfile0) exists the file (/var/lib/mysql/data/ibdata1) exists Database started Press return to continue ...130917 10:10:54 mysqld_safe Logging to '/var/log/mysqld.log'. 130917 10:10:54 mysqld_safe Starting mysqld daemon with databaes from /var/lib/mysql/data |
Step 2 | Choose the Start Services option to start the Cisco services. |
Step 1 | From the
ShellAdmin menu, choose the
Stop
Database option.
Do you want to stop the database [y/n]? y Stopping database.... Database stopped.... Stopping broker [PID=21921]/[Child=21923] Stopping controller [PID=21959]/[Child=21961] Stopping eventmgr [PID=21993]/[Child=21995] Stopping client [PID=22052]/[Child=22054 22101 22160] Stopping idaccessmgr [PID=22099]/[Child=] Stopping inframgr [PID=22158]/[Child=] Tomcat is running with [PID=22213]. Stoping it and its child process Flashpolicyd is running with [PID=22237]. Stopping it Stopping websock[PID=22242] Press return to continue ... |
Step 2 | Follow the onscreen prompts to complete the process. |
Step 3 | To restart the database, choose the Start Database option. |
Cisco ICFPP enables you to back up the entire database of a Cisco ICFPP virtual appliance to an FTP server.
Collect the following information:
Step 1 | Log in to the ShellAdmin console for the node with the database that is to be backed up. |
Step 2 | Stop Cisco services by choosing Stop Services. |
Step 3 | After the
services have stopped, choose
Backup
Database.
Backing database...... Backup will Upload file to an FTP server. Provide the necessary access credentials FTP Server IP Address: |
Step 4 | When prompted, enter the FTP server IP address and login credentials. Cisco ICFPP displays progress messages while the database is being backed up. |
Step 5 | When the backup operation is complete, restart services by choosing Start Services. |
To restore the database, see Restoring the Database.
Cisco ICFPP enables you to restore a backed up database from an FTP server. After you provide the FTP IP address, login credentials, and file details, Cisco ICFPP restores the database on the current node.
Gather the following information:
Step 1 | In the ShellAdmin console, choose the Stop Services option. |
Step 2 | After the
services have stopped, choose the
Restore
Database option.
Restore database...... Restore will recover file from an FTP server. Provide the necessary access credentials FTP Server IP Address: |
Step 3 | At the prompts, enter the FTP server IP address, login credentials, and the absolute path and filename of the backed-up database file. |
Step 4 | After the database has been restored, choose the Start Services option to restart the Cisco services. |
Note | For security reasons, we recommend that you do not compile software as root. |
Step 1 | In the
ShellAdmin console,
choose the
Manage
Root Access option.
Enable/Disable/Configure (root privilege) [e/d/c]: |
Step 2 | Enter
E.
Information similar to the
following is displayed:
Do you want to Enable Root Access [y/n]? : |
Step 3 | Enter
Y.
Enabling root access... Unlocking password for user root. passwd: Success. Root access enabled successfully Press return to continue |
Step 4 | Press Enter to return to the ShellAdmin menu. |
Step 1 | In the
ShellAdmin console,
choose the
Manage
Root Access option.
Enable/Disable/Configure (root privilege) [e/d/c]: |
Step 2 | Enter
C to configure root access.
Do you want to Configure/Set Root Privilege/Password [y/n]? : |
Step 3 | Enter
Y set a new root password.
Changing root password... Changing password for user root. New UNIX password: |
Step 4 | Enter the new
root password and confirm it when prompted.
passswd: all authentication tokens updated successfully. Root passwd changed successfully Press return to continue... |
Step 5 | Press Enter to return to the ShellAdmin menu. |
Step 1 | In the
ShellAdmin console,
choose the
Manage
Root Access option.
Enable/Disable/Configure (root privilege) [e/d/c]: |
Step 2 | Enter
D.
Do you want to Disable Root Access [y/n]? : |
Step 3 | Enter
Y.
disabling root access... Locking password for user root. Passwd: Success Root access disabled sucessfully Press return to continue... |
Step 4 | Press Enter to return to the ShellAdmin menu. |
Step 1 | From the
ShellAdmin console,
choose the
Login As
Root option.
Do you want to Login As Root [y/n]? : |
Step 2 | Enter
Y.
Logging in as root password: |
Step 3 | Enter the root
password.
Logging as root Password: [root@localhost shelladmin]# |
Step 4 | To log out,
enter
exit.
[root@localhost shelladmin]# exit exit Successful logout Press return to continue ... |
Step 5 | Press Enter to return to the ShellAdmin menu. |