Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

3458

September 10th, 2013 01:00

SP A Failure on EMC CX3-20F

Hi,

Recently we have moved our EMC CX3-20F from one site to another. After powering up again in new site SP A doesn't comes up.

When I check the faults SPS B seems to be down (not sure if SPE fault is related with SP A or SPS B);

Faulted Subsystem:  VS03Storage

Enclosure SPE : Faulted

Enclosure SPE SPS B : Faulted

We are checking the HW installation for SPS B fault. Besides I wonder if SP A failure is related with it or not. What would we do for further troubleshooting.

Any suggestions on this regard will be appreciated.

Here are the related event logs on the system;

08/21/2013 16:36:45                      (7127ca2c)SPA is faulted. The fault cannot be isolated. Fault Code: 39, 'Illegal Config(i.e.SAN in NAS enclosure)'.

Please call your service provider.

08/21/2013 16:38:09 Enclosure 0 SPS B    (637) SPS Recharging                          [0x00]   0        0                                       

08/21/2013 16:38:09 Enclosure 0 SPS B    (912) SPS Power cable 2 is configured improperly.[0x00]   0        80                                      

08/21/2013 16:38:10 SP B                 (7f4) AC Power to power supply B1 has been restored. This condition can also be seen when the SPS has completed testing.[0x00]   0        0  

Details: Peer->SetTime failed.  This is normal if only one SP is in service

08/21/2013 16:42:34                      (743a)Navisphere can no longer manage (SP A). This does not impact server I/O to the storage system. See Navisphere Manager Alerts for details. 

08/21/2013 16:47:50 Enclosure 0 SPS B    (62f) 1.  The SPS is ready, but the SPS configuration is invalid.  2.  Look at SPS status to get more specific information about how the SPS is incorrectly configured and then correct the configuration.[0x00]   0        0  

08/25/2013 05:30:10 Enclosure 0 SPS B    (62a) 1.  Periodic SPS test time.  2.  No action needed unless this message is seen more frequently than the periodic SPS Test is setup to run.[0x00]   0        2                                       

08/25/2013 05:30:10 Enclosure 0 SPS B    (663) SPS Test Initiating                     [0x00]   0        2                                       

08/25/2013 05:30:10 Enclosure 0 SPS B    (663) SPS Test Initiating                     [0x00]   0        2                                       

08/25/2013 05:30:13 Enclosure 0 SPS B    (698) Battery Testing In Progress             [0x00]   0        80                                      

08/25/2013 05:30:14 SP B                 (7f8) AC Power to power supply B1 has been interrupted and SPS testing is in progress.[0x00]   0        0                                       

08/25/2013 05:31:41 Enclosure 0 SPS B    (637) SPS Recharging                          [0x00]   0        0                                       

08/25/2013 05:31:41 Enclosure 0 SPS B    (912) SPS Power cable 2 is configured improperly.[0x00]   0        80                                      

08/25/2013 05:31:42 SP B                 (7f4) AC Power to power supply B1 has been restored. This condition can also be seen when the SPS has completed testing.[0x00]   0        0                                       

08/25/2013 05:39:14 Enclosure 0 SPS B    (62f) 1.  The SPS is ready, but the SPS configuration is invalid.  2.  Look at SPS status to get more specific information about how the SPS is incorrectly configured and then correct the configuration.[0x00]   0        0 

Thanks,

//Sinan

2 Attachments

4 Operator

 • 

4K Posts

September 10th, 2013 01:00

Please refer to the KB emc211293  "Illegal Config' is reported in another SP's events and SP is faulted.": https://support.emc.com/kb/55997

It might be caused by "LCC 0-0 cable was inserted incorrectly into Exp port instead of Pri port. The results was that the SP could not find the boot disk". You can "Connect the LCC cable from SP to LCC 0-0 Pri port and reseat SP. The SP should come up".

251 Posts

September 10th, 2013 01:00

This is the key message

08/21/2013 16:36:45                      (7127ca2c)SPA is faulted. The fault cannot be isolated. Fault Code: 39, 'Illegal Config(i.e.SAN in NAS enclosure)'.

Please call your service provider.

Normally this means that the when the boot process goes to check its a valid SP for that enclosure that its picking it up as an incorrect type

Normally this requires a service engagement from EMC to resolve

Gearoid

14 Posts

September 12th, 2013 07:00

Hi Roger,

Thanks for your support. The problem is fixed. We still have SPS redundancy problem according to monitoring logs. I guess cabling is not well with that and gonna check it out.

Regards,

//Sinan

No Events found!

Top