1060036 EVS Fails to Connect to Cinder
Description
EVS fails to connect to Cinder.
Attribute
Alarm ID |
Alarm Severity |
Auto Clear |
---|---|---|
1060036 |
Major |
Yes |
Parameters
Parameter |
Description |
|
---|---|---|
Alarm ID |
Indicates the alarm ID. |
|
Notification Type |
Indicates an alarm. |
|
Alarm Severity |
Indicates the alarm severity. 1: Critical 2: Major 3: Minor 4: Warning |
|
Last Occurred At |
Indicates the time when the alarm was generated for the last time. |
|
Fault Location Info |
HostAddress |
IP address of the host for which the alarm is generated. |
Additional Info |
Service |
Indicates the service name. |
MicroService |
Indicates the microservice name. |
|
Cinder URL |
URL of the Cinder node that cannot be connected |
|
ErrorMessage |
Indicates the error message. |
Impact on the System
EVS and Cinder failed to be connected and the EVS service is not available.
Possible Causes
- A Cinder service fault occurred.
- A Cinder network failure occurred.
- The Cinder URL is incorrect.
Procedure
- Log in to ManageOne Maintenance Portal using a browser.
- The login address is https://Address for accessing ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943.
- Default username: admin; default password: Huawei12#$
- In the navigation tree, choose Filter to filter alarms by alarm name. . Click
- Query the following alarm information:
- IP Address
- Location information (host address)
- Last Occurred At
- Additional Info
- Query Additional Information. If ErrorMessage contains statusCode is Unauthorized (401) - The request requires user authentication, account op_svc_evs configured for the Combined API node does not exist in IAM or the account password is incorrect. Contact the IAM O&M personnel to check whether account op_svc_evs exists.
- If account op_svc_evs does not exist, contact the IAM O&M personnel to add the account and obtain its password. If the account exists, obtain the account password.
- After the account password is obtained, change the iam.evs.password value in the configuration file on the Combined API node. For details, see Changing the Account Passwords for Component or Service Interconnection.
- After the configuration is successful, wait for 6 minutes and check whether the alarm is cleared. If the alarm is cleared, the fault has been rectified. If the alarm persists, go to 5.
- Query Additional Info to check whether the Cinder URL is correct.
- If ErrorMessage contains information such as java.net.ConnectException: Connection refused, java.net.NoRouteToHostException: No route to host (Host unreachable), java.net.UnknownHostException:, and Name or service not known, indicating that the connection to the Cinder is broken, the Cinder URL is incorrect. Apply for a configuration change to change the Cinder URL of the node.
- If ErrorMessage contains information such as 503 Service Unavailable and No server is available to handle this request, indicating that services are unavailable, the services at the Cinder API layer is abnormal and cannot respond to the request. Contact FusionSphere OpenStack Cinder O&M personnel to locate and rectify the fault.
- If the Cinder URL is correct, locate the fault by performing operations provided in Troubleshooting Guide for Typical Cinder Problems. If the fault persists, provide Location Information for FusionSphere OpenStack Cinder O&M personnel for alarm locating and handling.
- After 6 minutes, check whether the alarm is automatically cleared.
Related Information
None