This post is more than 5 years old
2 Intern
•
388 Posts
0
5041
January 3rd, 2008 14:00
Error message when rebooting SP in CX3-20 Storage Array ?
In order to test the Storage Array, we have attempted to reboot SPA and SPB. We reboot SPA first. We reboot SPB later when everything is stable.
We are surprised as we only get the following error message from SPA reboot but not from SPB reboot. Is there any clue for those messages ?
Severity Warning Host CX320-SPA
Storage Array CK200085300402 SPA Device SP A
Description Flare's ATM detects one CMI connection is down.
Severity Critical Error Host CX320-SPA
Storage Array CK200085300402 SPA Device SP B
Description Peer SP Down.
Severity Error Host CX320-SPA
Storage Array CK200085300402 SPA Device SP A
Description Hard Peer Bus Error
Severity Warning Host CX320-SPA
Storage Array CK200085300402 SP N/A Device N/A
Description #THREADO: Peer died in Run: 1073774611
40 00 40 01
Thansk
We are surprised as we only get the following error message from SPA reboot but not from SPB reboot. Is there any clue for those messages ?
Severity Warning Host CX320-SPA
Storage Array CK200085300402 SPA Device SP A
Description Flare's ATM detects one CMI connection is down.
Severity Critical Error Host CX320-SPA
Storage Array CK200085300402 SPA Device SP B
Description Peer SP Down.
Severity Error Host CX320-SPA
Storage Array CK200085300402 SPA Device SP A
Description Hard Peer Bus Error
Severity Warning Host CX320-SPA
Storage Array CK200085300402 SP N/A Device N/A
Description #THREADO: Peer died in Run: 1073774611
40 00 40 01
Thansk
No Events found!
mohas
1 Rookie
•
44 Posts
0
February 4th, 2008 05:00
Adding to Amrith`s.
It should report for the Both the SP`s when you reboot. If you check the SP Events, you can find the same or Analyse the SP Collects, you can find it.
In your case, during the ConnectEMC Setup, they might have setup the Interval time between refreshing and that delay might ignores the alert from the other SP.
To confirm the same, during your next test, you can change the order of Rebooting and confirm the same...
amrith
1 Rookie
•
76 Posts
1
January 11th, 2008 00:00
Description Peer SP Down.
Description Hard Peer Bus Error
Description #THREADO: Peer died in Run:
The above messages are reported by the peer SP and NOT the SP which is rebooting...
During a reboot, say if SP A is rebooting, SP A goes offline.and SP B attempts to communicate with SP A but in vain ,hence reporting the above errors.
Once the SP starts rebooting , SP A starts logging "reboot" in the events.
TonyJK2
2 Intern
•
388 Posts
0
January 13th, 2008 01:00
Thank you for your advice.
I would like to ask 2 additional questions
1) We just wonder why we don't get the same warning message when we reboot SPB ?
2) Does it mean that it is OK to ignore those warning messages ?
Thanks
AranH1
2.2K Posts
0
January 14th, 2008 08:00
It looks like these are benign error reporting messages during an SP reboot, but I would double check with EMC support to confirm this.
Aran
TonyJK2
2 Intern
•
388 Posts
0
January 14th, 2008 14:00
Thanking you in anticipation.
Regards,
Tony
amrith
1 Rookie
•
76 Posts
0
January 29th, 2008 22:00
Thank you for your advice.
I would like to ask 2 additional questions
1) We just wonder why we don't get the same warning
message when we reboot SPB ?
2) Does it mean that it is OK to ignore those warning
messages ?
Thanks
You Should get the same warnings in SP A when you reboot SP B.
Rebooting an SP is a critical operation - you can ignore if you are doing this manually.
Well, I was with clariion support