Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
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"
There is no alarm, on the task list, there will be detailed error message as above
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
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