IBM Storwize V7000 Unified Problem Determination Manual page 45

Table of Contents

Advertisement

4. Expand any mgmt00xst001 subcomponent that shows a critical or warning event
Connectivity issues for the 2073-720
This topic provides information for troubleshooting connectivity issues. The major
focus is on connectivity between the file modules and the control enclosure. Good
connectivity is required to troubleshoot control enclosure problems.
Host to file modules connectivity
This procedure is used to troubleshoot Ethernet network connectivity between the
host and the file modules. These network paths are used for all system requests
and management operations. The paths are also needed for Ethernet network
connectivity between the file module and the Storwize V7000.
About this task
Within the file modules, two internal 1 GB network ports and two 10 GbE network
ports can be configured for system operations.
Figure 1 on page 26 identifies the various rear ports and hardware for the file
module.
subcomponent areas of the system in which the interface nodes reflect the file
module components, and the enclosure number represents the storage system.
a. Expand the interface nodes to display the two individual file modules that
are represented by the host names mgmt001st001 and mgmt002st001. Expand
each of these file modules to display further details.
For any critical or warning level events, the corresponding hardware reflects
the status with a small red circle or yellow triangle next to the
corresponding device.
b. Navigate to the status by expanding the mgmt00xst001 system that shows a
problem.
c. Select Status to produce a list of statuses.
indication and select Status.
a. Review the Sensor column and the Level column for Critical Error, Major
Warning, or Minor Warning items.
If the problem that caused the Level item is resolved, right-click the event
and select the Mark Event as Resolved action.
b. Follow the online instructions to complete the change.
c. Review the status list for the other events that might cause the Health
Status to be red or yellow.
d. Perform the same steps.
As long as there is a single sensor that is marked as Critical Error, Major
Warning, or Minor Warning, the Health Status is red or yellow. When you
use the Mark Event as Resolved action against the sensor, the sensor no
longer shows in the status view. If the problem is still not resolved, a new
sensor update occurs that reflects the problem. An example might be if a
software error event is marked as resolved but the system still detects the
problem; then the status is properly reflected in the Status display.
Chapter 3. Getting started troubleshooting
25

Advertisement

Table of Contents
loading

Table of Contents