CX3-20 backplane cables out of sequence - office move jumbled them up!

ASR is correct. If plugged into the SPA Service Port you are talking to SPB and visa versa. Have you tried logging into the peer SP? One thing you could do is bring up one SP at a time and see if there is a difference in Navisphere. It sounds like the Embedded WinXP OS may have been corrupted hence Navisphere not behaving correctly.

15-20 min could be normal for the LUNs to become visible on the SAN to the hosts.

The "Pri" and "Exp" DAE3 ports are intended to be dedicated to input and output respectivley.

If LUNs have R/W access then there is something wrong within the Embedded OS/Navisphere.

You could try an Off Array Navisphere app to see if a difference there.

Oh and yes if old SP Collects are required there is probably a set on each SP under "File Transfer Manager", they could have assisted of there was more than one back end bus for the jumbled DAE's but in your case does not apply due to the one BE bus on CX3-20.

I would have enclosure 0 first on the bus if possible, if it is not could explain the slow boot up.

Network pings respond long before the array can service I/O.

Good luck! and keep trying.

Was your question answered correctly? If so, please remember to mark your question Answered when you get the correct answer and award points to the person providing the answer. This helps others searching for a similar issue.

glen