FusionSphere failed to add hosts during environment

Publication Date: 2014-01-01Views: 417Downloads: 0

Issue Description

failed to add hosts during environment

Alarm Information

no

Handling Process

Step 1 Check the connection between the VRM and Computing Node Agent (CNA) nodes.
1. Perform the required step based on the scenarios in which a host fails to be added.
− If you fail to add a host during VRM installation using a tool, go to step 2.
− If you fail to add a host on the FusionCompute portal, go to step 3.
2. Check whether the management IP address of the faulty CNA can be pinged from the local PC.
− If yes, go to step 7.
− If not, repair the network connection and ping the management IP address again.
3. Use PuTTY to log in to the active VRM node.
Ensure that the management floating IP address and username gandalf are used to establish the connection.
4. Run the following command and enter the password of user root to switch to user root:
su - root
5. Run the following command to disable logout on timeout:
TMOUT=0
6. Check whether the management IP address of the faulty CNA can be pinged from the active VRM.
− If yes, go to step 7.
− If not, check and rectify network faults and perform the ping operation again.
Step 2 Check whether the STP function is enabled for the physical switch.
7. Check whether the STP function is enabled for the physical switch. For details, see switch-related documents.
− If yes, disable the STP function. For details, see the switch guide.
− If not, go to step 8.

Step 3 Check whether the host has any residual network data.
8. Use PuTTY to log in to the CNA node.
Ensure that the management IP address and username gandalf are used to establish the connection.
9. Run the following command and enter the password of user root to switch to user root:
su -root
10. Run the following command to disable logout on timeout:
TMOUT=0
11. Run the following command to enter the system database:
sqlite3 /opt/galax/data/vsa/vsa.db
12. Run the following command to check whether the host has any residual network data:
select * from UPLINKPORTAGGR;
Network data remains on the host if information similar to the following is displayed:
1|10|1|1||0|0|0|0|0|0|0
13. Run the .q command to exit the system database and run the following command to switch to the hostinfo directory:
cd /opt/galax/data/hostinfo
14. Run the following command to delete the vrm-info file:
rm vrm-info
15. Run the following command to restart the NC process:
service vnad restart
16. Add the host again and check whether it can be successfully added.
− If yes, no further action is required.
− If not, contact technical support.

Root Cause

The STP function of the physical switch is enabled, which makes the time required for binding network ports during the host addition process longer than the waiting time of the Virtual Resource Management (VRM) node by 40 seconds. As a result, hosts fail to be added to the system. Moreover, because the network configuration information of the hosts remains in the system, these hosts fail to be added to the system once again. This problem has been solved in FusionCompute V1001R003C00SPC300.