2017-10-19 03:45 AM
OCUM 7.2 P1 reports unused ATTO SAS Port as "Critical Incident".
We have a cDOT MetroCluster with ATTO7500 (4 Stacks/4 SAS-Ports).
Two are in use (1,2 or A,B), two are unused (3,4 or C,D).
Every couple of minutes, OCUM reports the unused SAS-Ports as "offline
Impact Level: Incident
Impact Area: Availability
Source Type: MetroCluster Bridge Stack Connection
Triggered Time: 3 Mins Ago
Trigger Condition: Link ATTO_x.x.x.x to storage stack 5 is down. The Ids of the affected shelves are 12,14,13.
Solved! SEE THE SOLUTION
2017-10-20 01:27 AM
this is works as designed and actually not an OCUM issue.
OCUM is just visualizing what the built-in health monitor of ONTAP is reporting.
You will see the same error on ONTAP CLI or System Manager as the system cannot distinguish between a port being unused intentially and a faulty port, e.g. due to a broken cable.
If those ports are indeed not used, they have to be explicitely disabled as described in the Fabric MetroCluster Installation and Configuration Guide - page 148:
Disable any unused SAS ports:
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO or both.
2017-10-20 04:22 AM - edited 2017-10-20 04:22 AM
I had the SAS ports disabled, but the errors kept popping up.
You have to disable the SAS Ports AND do a "SaveConfiguration Restart" on every ATTO to get rid of these errors.
2017-10-20 04:24 AM - edited 2017-10-20 04:25 AM
I had the ports disabled, but without the restart.
"SaveCondiguration Restart" did the job!
2017-10-20 06:38 AM
Hence I posted the link to the configuration guide and the relevant page.
The paragraph just below the one I quoted in my post reads:
Save the bridge's configuration.
If using the CLI, issue the following command:
You are prompted to restart the bridge.
Sorry for causing confusion by just posting the part to disable the ports.