We've just moved offices and our 7 rack CX3-20 has been re-installed in the new building but the sequence of which cable goes in which fibre port for the 4Gb backplanes has been lost! Duh!
Currently the Windows 2008 server hosts can see the correct disk drives and read & write to them but whilst I can login to the SPs Navisphere just shows a 'fault' on each SP and does not show any LUNS, drives or disks.
So, silly question, but is there anyway to retroactively discover what fibre should plug into which disk array? The diagram we used for the removal obviously is wrong!
Solved! Go to Solution.
OK, we'll wrap this up now. Many thanks to all who helped out.
Key things we've learnt are that the cable sequence does not matter so long as basic rules about 'in' & 'out' are observed along with not crossing over from 'A' to 'B'.
In the end it seems one of the SPs - SPB - has died so we are currently running on one leg, but can at least now get Navisphere to work and manage the system. It is 'long in the teeth' (5 years old) and out of support so time to be replaced I think.
Do you have old SP Collects before you moved the Storage Unit? Then I reckon, you can get the old cabling information.
i am amazed that some raid groups apparently still working so not all DAEs got cabled incorrectly.
Thanks for all of those suggestions. I tried running up Navisphere (Java version) on a directly connected laptop and, after logging in with my creds, it 'sees' the SP (either A or B) but shows 'F' (fault) against both the 'domain' and the array. RBC should, as you say, bring up a menu which it does. Select 'Connectivity' and the browser just locks up with no result. I get similar results on both SPs.
WRT the backplane cables I'm told that it doesn't matter which 'sequence' the DAEs are in? [so long as SPA goes to 'A' side and v.v.?? I may have the DAEs in the wrong 'stack' order but that would not seem to matter??
Indeed, the Windows host 'sees' all the drives at a Windows level and they are all R/W OK.
So any ideas how to get the SPs (connected via a Brocade 200e) to 'see' the LUNS etc for management?
and no, I did have SP collects but from a couple of years ago so junked.. sigh.
Many many thanks
You are correct that on the CLARiiON there isn't any requirement that the DAE's be physically cabled to match the logical assignment. For instance, it is possible to have DAE 3 physically come before DAE 2 on the bus. Also, there isn't any technical reason they have to be contiguous. For example, you can have DAE 0, 1, 4, 5; where DAE 2 and 3 don't exist either because someone accidentally/intentionally manually skipped those numbers upon initialization or later they were removed from the middle of the loop (which, just to mention it, can be done entirely online).
You can obtain the Bus and DAE number for each enclosure via the LED's on the back which will (should) not change once initialized. You will find two colored LED's:
1) Green = Enclosure Address
2) Blue = Bus number
Also, if the Blue LED is blinking, it can denote invalid cabling in the following situations (however, you can not imply that if it is not blinking that cabling is valid - still verify manually) :
a) LCC A and LCC B are not cabled to the same bus
b) Or the maximum number of DAEs allowed on the bus is exceeded
For reference, here is a diagram of a DAE3P (unless you own an older model) :
Fantastic support & advice! Many thanks - I'll check out on Monday when I'm next in the comms room,.
So if the order is not an issue now ~all~ I have to do is figure out why the SPS are not 'seeing' the DAEs.....
David, did you ever have to upload SPcollects to a service request? You could look for those older SRs and download the SPcollects again to verify which DAE goes where.
Isn't is so that the CX3-20 only has 1 BE bus so mixing DAEs between 2 or more buses is impossible and since the DAE number is placed IN the DAE instead of in the SPs the sequence of the cables shouldn't matter.