Not Sure What This Error Means - No System Crash

Rich,

Thanks for your analysis and suggestion.  The odd thing is that this SAN has been in operation for approximately 4 years without any cabling changes.  Perhaps someone in the cabinet jarred a cable.  We'll check it out.  Thanks again.

It's specifically referring to the backend bus cabling between shelves..  Essentially saying that the cabling from the SPA to a disk shelf is different than the cabling from SPB to the disk shelf.

When correctly cables, both SPs will have backend bus cables that daisy chain between shelves in the exact same path as each other.  If, for example, SPA has a cable from itself to DAE 0_0, then another cable fro DAE 0_0 to 0_1 on the same side.  While SPB was accidentally cables from itself to DAE 0_1, then back from 0_1 to 0_0..  Then SPA and SPB has mismatched cabling and it is invalid.  Assuming at least one SP can communicate successfully with all DAEs, there would not be an outage, but it may no survive a component failure since redundancy may be impacted.

I would meticulously trace every cable on the backend of the array, from SP to DAE, to the next DAE, etc and ensure that the A and B sides are identical.

Do not just unplug the cables to resolve it without first knowing which side is properly working however as you could cause an outage if you unplug the wrong cable.

According to KB emc172277 "Why is a customer receiving emails for event number 0x2580 after upgrading to FLARE code 3.24.80.5.011?":

The event number 2580 should be unchecked in the monitor template. According to EMC Engineering, event 2580 event is always called during an SPS test even if the SPS has no problems. That is why this event is not monitored. If there is a problem with the SPS, a subsequent event will identify the problem and dial home.

Note: Navisphere may need to be in engineering mode in order to access the template properties.

So you can check the SPS status as well.