No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

CNA node can't be added to the cluster on FusionCompute system

Publication Date:  2017-06-29  |   Views:  1294  |   Downloads:  0  |   Author:  c00507397  |   Document ID:  EKB1000712154


Issue Description

When the VRM is ready, and the new CNA is also installed successfully, the CNA node can't be added to the cluster on the FusionCompute portal.

The error message is "the system interface doesn't exist"

Alarm Information

There is no alarm, on the task list, there will be detailed error message as above

Handling Process

When chekcing the VRM Log, there was error as below:

Then, continue to check the log for the CNA node, there was also error about creating the interface

The error code 300 mean that the EVS service was abnormal,and we can double check the status of EVS with the command below

With the output above, we can see there is no EVS service running, then we have to confirm if there is iNIC on this CNA with the command below

Root Cause

For the FusionCompute system, if there is iNIC on the CNA node, the system service will not try to start EVS service.then, when the system try to add the CNA to the cluster, the error about the "system interface" will prompt out and the operation failed.


Because the iNIC was not used for that CNA node, we can remove that card, then run the command "service evsd restart" to start the service

Then, add the CNA to the cluster again on the portal


It's better to use the common NIC and iNIC on the same CNA node when installing the FusionCompute system