Pillar Axiom 500 Storage System
 
Pillar Axiom 300 Storage System
 
Pillar Axiom 600 Storage System
 

PLA-Support>Sun Systems>DISK>Pillar Axiom>SN-DK: Ax600
 

In this Document

Purpose

Troubleshooting Steps

--- Symptoms ---

--- Changes ---

--- Cause ---

--- Solution ---

Applies to:

Purpose

Any FICM ports can be disabled by the Axiom port monitoring tool when it has excessive errors. This will generate a event/callhome Storage Fabric Port Disabled By Monitor. As the Axiom has multiple paths, this is not a critical issue. The steps in this document will provide the information on what data will need to be collected for Pillar support to find the root cause and corrective actions.

Troubleshooting Steps

--- Symptoms ---

Any FICM ports can be disabled by the Axiom port monitoring tool when it has excessive errors. This will generate a event/callhome Storage Fabric Port Disabled By Monitor. As the Axiom has multiple paths, this is not a critical issue. The steps in this document will provide the information on what data will need to be collected for Pillar support to find the root cause and corrective actions.

--- Changes ---

--- Cause ---

Any components in the loop could be the cause of the errors. FCIM, cables, or RC.

Verification

The callhome will have the information of what port on what CU was disabled. This can be verified by reviewing the information in the GUI. Health->Hardware->Slammers->Slammer->I/O Port Details. Reference to the cabling guide available in any axiom GUI under the documentation links to see what port should be connected.

--- Solution ---

Once the data in this document is collected,sent to support and analyzed. The causing hardware component(s) will need to be replaced to completely resolve this problem.

Following are the steps to collect the needed information to determine the defective part.

1) Enable Slammer ports with supporttool commands:

supporttool sub -H 10.64.100.46 EnableSlammerPort Slammer=[/Slammer1 Port=FS8 ControlUnit=0](substitute your disabled port)

2) Disable Port Monitor with supporttool

supporttool sub -H 172.20.188.80 DisablePortMonitor

DisablePortMonitor (no need to re-enable, system will automatically re-enable this)

3) Verify all ports are solid green on the rear of the PIM and on the bricks.

4) Verify ports show connected in the GUI Slammer I/O Details and Brick I/O Port Details screens.

5) Execute GetPIStats to capture 3 output files

6) Email captured output files for analysis

7) Get new Axiom logs.

The PIStats and Axiom log file will be use to determine the part that is generating the error. Part(s) will then be dispatched.

This solution has no attachment