Hello, community members.
Today I’m going to introduce you how to deal with failed to access the eSight and ManageOne.
I believe that you have used eSight, ManageOne, or ServiceOM to manage devices, and login failures often occur.
Today, I'd like to share with you the cause of failure to log in the eSight and ManageOne and how to handle the failure.
I hope this is helpful to you.
Problem Description
The user failed to log in to ManageOne, ServiceOM, and eSight
Problem Analysis
The solution is FusionCloud6.3.1TYPE3,
The management storage is FCSAN,
The management storage model is OceanStor5500V5, and the version is V500R007C10.
If you cannot log in to all management pages, please try to log in to the controller server using SSH and check whether the management storage status is abnormal.
Contact the user to learn about the latest operations performed by the user and restore the storage link.
Collected SNS2248 logs of Fibre Channel switches and management storage logs. And finally found that a user incorrectly configured zones on two Fibre Channel switches. As a result, all management storage links were interrupted. After the zone configuration was deleted, the fault was rectified.
Root Cause
No zone is configured on the two SNS2248s. The zone configured does not contain the original storage and host ports. As a result, the management host is disconnected from the storage device.
Solution Description
1. The user deletes the incorrect zone configuration.
2. Log in to the Controller background using SSH.
3. Stop all management VMs, and then start all management VMs, restore the management VMs, finally.
Suggestion
The SNS2248 still needs to be configured with zones to prevent service expansion risks.
Before configuring zones, submit the RFC seven days in advance.
That's all for today. I hope it will be helpful to all of you!
If you have any other comments or want to know more, please leave a message below to let me know.
