IBM Storwize V7000 Unified Problem Determination Manual page 75

inaccessible to the hosts. The fix procedures automatically perform configuration
changes that are required to return the system to its optimum state.
Accessing the Storwize V7000 Unified management GUI
This procedure describes how to access the Storwize V7000 Unified management
GUI.
About this task
You must use a supported web browser. Verify that you are using a supported web
browser. Checking your web browser settings for the management GUI from the
Storwize V7000 Information Center.
www.ibm.com/storage/support/storwize/v7000/unified
You can use the management GUI to manage your system as soon as you have
completed the USB flash drive initialization.
Procedure
1. Start a supported web browser and point the browser to the management IP
address of the file module.
The management IP address is set during the USB flash drive initialization.
2. When the connection is successful, you see a login panel.
3. Log on by using your user name and password. The default user name is
admin.
4. When you have logged on, select Monitoring > Events.
5. Ensure that the events log is filtered by using Recommended actions.
6. Select the recommended action and run the fix procedure.
7. Continue to work through the alerts in the order suggested, if possible.
Results
After all the alerts are fixed, check the status of your system to ensure that it is
operating as intended.
If you encounter problems logging on the management GUI or connecting to the
management GUI, see "Problem: Unable to log on to the management GUI" on
page 191 or "Problem: Unable to connect to the management GUI" on page 190.
Using fix procedures
You can use fix procedures to diagnose and resolve problems with the Storwize
V7000 Unified.
About this task
For example, to repair a Storwize V7000 Unified system, you might perform the
following tasks:
v Analyze the event log
v Replace failed components
v Verify the status of a repaired device
v Restore a device to an operational state in the system
v Mark the error as fixed in the event log
Chapter 3. Getting started troubleshooting
55