- Managing Cisco NFVI
- Cisco VIM REST API
- Monitoring Cisco NFVI Performance
- Managing Cisco NFVI Security
- Managing Cisco NFVI Storage
- Overview to Cisco VIM Insight
- Managing Cisco VIM through Insight (Tech Preview)
- Managing Blueprints
- Managing Pod Through Cisco VIM Insight
- Shutting Down and Restarting Cisco VIM Insight
- Overview to the Cisco Virtual Topology System
- Managing Backup and Restore Operations
- Troubleshooting
Cisco Virtual Infrastructure Manager Administrator Guide, Release 2.0
- Updated:
- July 20, 2017
Chapter: Managing Pod Through Cisco VIM Insight
Managing Pod
Through Cisco VIM Insight
The following topics tell you how to install and replace Cisco Virtual Infrastructure Manager (VIM) nodes using Cisco VIM Insight.
Managing Hardware
Management of your Cisco VIM pods includes adding, removing, or replacing the nodes.
In a pod, multiple nodes cannot be changed at the same time. For example, if you want to replace two control nodes, you must successfully complete the replacement of the first node before you start to replace the second node. Same restriction applies for addition and removal of storage nodes. Only, in case of Compute Nodes you can add/remove multiple nodes together; however, there must always be one active compute node in the pod at any given point. VNF manager stays active and monitors the compute nodes thereby moving the VNFs accordingly as compute node management happens.
 Note | When you change a control, storage, or compute node in a Cisco VIM pod using Insight, it will automatically update the server and role in the active blueprint, as a result, your OpenStack deployment will change. When a node is removed from Cisco VIM, sensitive data may remain on the drives of the server. Administrator is advices to use Linux tools to wipe the storage server before using the same server for another purpose. The drives used by other application server should also be wiped out before being added to Cisco VIM. |
Managing Storage Nodes
Before you add or remove a storage node, review the following guidelines for Managing Storage Nodes.
-
Required Number of Storage Nodes: A Cisco VIM pod must have a minimum of three and a maximum of 20 storage nodes. If your pod has only two storage nodes, you cannot delete another storage node until you add another storage node. If you have fewer than three storage nodes, you can add one node at a time until you get to 20 storage nodes.
-
Validation of Nodes: When you add a storage node to a pod, Cisco VIM Insight validates that all the nodes in the pod meet the minimum requirements and are in active state. If you have a control or compute node in a faulty state, you must either correct, delete or replace that node before you can add a storage node.
-
Update Blueprint: When you add or delete a storage node, Insight will update the blueprint for the Cisco VIM pod.
-
Storage Node Logs: You can access the logs for each storage node from the link in the Log column on the Storage Nodes tab.
Failed Addition or Deletion of Storage Node: If your attempt to add or delete a storage node fails, complete the following instructions:
Adding Storage Node
You cannot add more than one storage node at a time. Complete the following instructions to add a storage node:
Deleting Storage Node
You cannot delete more than one storage node at a time.
Managing Compute Nodes
Before you add or remove a compute node, review the following guidelines:
-
Required Number of Compute Nodes: A Cisco VIM pod must have a minimum of one compute node and a maximum of 96 compute nodes. If your pod has only one compute node, you cannot delete that node until you add another compute node.
-
Update Blueprint: When you add or remove a compute node, Insight will update the blueprint for the Cisco VIM pod.
-
Compute Node Logs: You can access the logs for each compute node from the link in the Log column on the Compute Nodes table.
Adding Compute Node
Complete the instructions, to add a compute node:
Ensure that the server for the new compute node is in powered state in OpenStack. You can add more than one compute node at a time.
Deleting Compute Node
A compute node is deleted due to a hardware failure. You can delete one compute node at a time. If your pod has only one compute node, you cannot delete that node until you add another compute node.
Managing Control Nodes
Before you replace a control node, review the following guidelines:
-
Required Number of Control Nodes: A Cisco VIM pod must have three control nodes and you can only replace one node at a time.
-
Validation of Nodes: When you replace a control node, Cisco VIM Insight validates if all the other nodes in the pod meet the minimum requirements and are in active state. If you have a storage or compute node in a faulty state, you must correct the faulty state or delete or replace that node before you can replace the control node.
-
Update Blueprint: When you replace a control node, Insight will update the Active blueprint for the Cisco VIM pod.
-
Control Node Logs: You can access the logs for each control node from the link in the Logs column of Control Nodes table.
Replacing Control Node
You can replace only one control node at a time.
What to Do Next
If the replacement of the control node fails, do the following:
Managing Software
Software management of your Cisco VIM pods includes software update, reconfigure of openstack services and password, etc.
VIM Software Update
As part of the lifecycle management of the cloud, VIM has the ability to bring in patches (bug fixes related to code, security, etc.), thereby providing cloud management facility from software point of view. Software update of the cloud is achieved by uploading a valid tar file, following initiation of a System Update form the Insight as follows:
What to Do Next
System Update has been initiated message will be displayed. Logs front-ended by hyperlink will be in the section below in-front of Update Logs which shows the progress of the update. During the software update, all other pod management activities will be disabled. Post-update, normal cloud management will commence. Once update has completed you will see the status of update in the box below.
If log update fails, Auto-RollBack will be initiated automatically.
If Auto-rollback fails during software update fails through Insight UI, it is advised that the administrator contact Cisco TAC for help. Do not re-try the update or delete the new or the old installer workspace.
Reconfigure Password
-
Regenerate all passwords: Click Regenerate all passwords checkbox and click Set Password. This will automatically regenerate all passwords in alphanumeric format.
-
Regenerate single or more password: This will set a specific password by doing an inline edit for any service like Horizon's ADMIN_USER_PASSWORD. Double click on the filed under Password and enter the password to enable Set Password button.
During the reconfiguration of password, all other pod management activities will be disabled. Post-update, normal cloud management will commence. If the reconfigure of the password fails, all subsequent pod management operations will be blocked. It is advised to contact Cisco TAC to resolve the situation through CLI.
Reconfigure OpenStack Services, TLS Certificates and ELK Configurations
Cisco VIM supports the reconfiguration of OpenStack log level services, TLS certificates, and ELK configuration. Listed below are the steps to reconfigure the OpenStack and other services:
What to Do Next
During the reconfiguration process, all other pod management activities will be disabled. Post-update, normal cloud management will commence. If reconfigure of OpenStack Services fail, all subsequent pod management operations will be blocked. It is advised to contact Cisco TAC to resolve the situation through CLI.
Reconfigure Optional Services
Cisco VIM offers optional services such as heat, migration to Keystone v3, NFVBench, NFVIMON, etc, that can be enabled post-pod deployment. These services can be enabled in one-shot or selectively. Listed below are the steps to enable optional services:
Note | Un-configuration of the optional services post-deployment will be covered post 2.0. |
Feedback