Block SP Boot Issue Checklist

In order to handle typical SP Boot issue, TSE should know the following basic skills beforehand.

Open RA via Management port Open RA via Service LAN port. Open EMC remote to SP.(For legacy CX box) Gather SPCollect via RA. Restart K10governor via RA. Enter FLARECONS and check status of any RAID Group. Capture boot log (see coach share 44) Setup PPP connection (see coach share 44) Know the meaning of the fault LED color and blinking rate. Reboot SP into utility partition

Can this SP handle I/O?

No >

Fault LED color Amber Blue

Fault LED blink rate Hz 1Hz 4Hz Solid

Boot Log available and reviewed

Peer SP Collect available and reviewed

unavailable

Peer SP Remotely Anywhere output review spstate

speclcli mpb

speclcli mps

Conclusion Hardware Fault

Rolling reboot

Degraded mode

Yes> FLARE is running fine. SP unmanaged, fill in the table

Port open Unisphere setup page & CLI via RA CLI from NAS ping RA CLI

Mgmt Port

Service LAN

Port

PPP connection

If the answer is No, go to the right. If the answer is Yes, stop.

Appendix: SPA rolling reboot troubleshooting steps:

1. Mini configure the backend (only connect DAE 0_0 on A side) 2. Reboot SP into utility partition 3. Choose force degraded mode to start the SP into degraded mode. 4. Remoteanywhere access the SPA. 5. CMD > HFOFF 6. Reboot SPA again. 7. Start KTRACE log capture

a. CMD > ktcons il b. !load fdb c. .logopen c:\spa_flarestart_ktracelog.txt d. .logto both e. !ktail T all

8. Manually start the flare by running FlareandLayeredStart.bat 9. If started successfully >>> add DAE one by one back. 10. If started failed >>> in ktrace log window, press Ctrl+C >>> .logclose >>>contact l2 the case with

ktrace log ,if required open an AR request