Adding New Enclosure Causes Fault ─ CX4

Added a new enclosure and Navisphere

indicates that the enclosure has a fault. (0)
NOTE: This tree is for CX4 series arrays
running Flare Release 28 or greater.

Run either Navisphere Manager or enter the

Navisphere CLI getcrus command.
Look for any enclosure faults. (1)

Does Navisphere
Indicate that the enclosure is in
a FAILED State? (2)
If the enclosure has faulted drives, refer to the appropriate troubleshooting
No
tree. For example, Multiple Drive Failures or New Drive is Offline. (3)

Yes

Does Navisphere
Indicate that there are duplicate
enclosure addresses? (4)
Make sure that the enclosure is on the correct loop.
Yes
If it is on the correct loop, fix the enclosure address. (5)

No

If the loop is running at 4G and the new enclosure is not capable of running at 4G
Does Navisphere (for example, a DAE-2P), you can either:
Indicate that the enclosure can • reset the Back End (BE) bus to run at 2G using either Navisphere Manager
Yes
not change speed to the loop or the Navisphere CLI backendbus -resetspeed command (reset operation is
Speed? (6) disruptive), or
• replace the 2G enclosure with a 4G enclosure (for example, a DAE-3P).
(7)

No

Does Navisphere Make sure that BOTH of the LCCs in the enclosure are inserted correctly.
Indicate that there are too many If one of the LCCs was reseated recently, then either wait 2 minutes and reseat
Yes
speed change retries? the Backend cables to this enclosure, or power cycle the enclosure.
(8) If Navisphere still displays the same error, replace the enclosure. (9)

No

Does Navisphere
A 4G LCC might be plugged into a 2G enclosure. Verify this. If a 4G LCC is
Indicate that there is a general
Yes plugged into a 2G enclosure, replace the LCC on the side that is reporting the
fault on this enclosure?
general fault. (11)
(10)

No NOTE: When closing a solved case, be sure to open CSI and

specify the action that solved the problem. If the case needs to be
escalated, make sure that you have the spcollect data.
A
 Adding New Enclosure Causes Fault ─ CX4 (continued)
Does Navisphere
indicate that there is a cabling
error? (12)
No
Does Navisphere
Display an error about enclosure type
and raid group type mismatch?
(14)
No
Does Navisphere
Indicate that there is a bad
component in the enclosure?
(16)
No
Make sure that:
- the cable from the previous enclosure or SP is connected to the
PRI port on the LCC.
Yes - LCC A and LCC B are on the same loop.
- LCC A is cabled either to LCC A of another enclosure, or to SPA.
- LCC B is cabled either to LCC B of another enclosure, or to SPB.
(13)
Make sure that the new enclosure is the same enclosure type as the
Yes
enclosure that was previously present at this address. (15)
- If both SPA and SPB are reporting the same problem, replace the enclosure.
- If only one side is reporting the problem, replace the cable.
Yes
- If that does not fix the problem, replace the LCC or the LCC in the previous
enclosure. (17)
NOTE: When closing a solved case, be sure to open CSI and
specify the action that solved the problem. If the case needs to be
escalated, make sure that you have the spcollect data.
 Adding New Enclosure Causes Fault – CX4 (continued)

Does Navisphere
It takes time for the enclosure to change speed. Wait about 2-5 minutes.
Indicate that the enclosure is
Yes If you still see this error on SPA, then SPA is waiting for SPB to change its speed.
changing speeds?
Make sure that the enclosure is cabled correctly. (23)
(22)

No

Power cycle the enclosure.

(26)

Does the error

Yes Escalate to Engineering (28)
still exist? (27)

No
NOTE: When closing a solved case, be sure to open CSI and
specify the action that solved the problem. If the case needs to be
Done (29) escalated, make sure that you have the spcollect data.