 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
From: BoxMonitor
Subject: Celerra Notification - CS0, CRITICAL, BoxMonitor
Event Time: Nov 23 14:33:04 2009
Brief Description: Slot 3 has panicked.
Full Description:
The operating system running on the slot has panicked. The Data Mover
slot will be failed over, if possible, and rebooted.
From: BoxMonitor
Subject: Celerra Notification - CS0, CRITICAL, BoxMonitor
Event Time: Nov 23 14:36:51 2009
Brief Description: Slot 3 Both internal interfaces are down.
Full Description:
The Control Station is not able to communicate with either of the
(local) network interfaces of the identified Data Mover (slot). The
operating system running on the identified Data Mover may be
unresponsive. The specified Data Mover will be failed over, if possible,
and rebooted.
I have no idea what system this is nor why I'm receiving these alerts,
but I find something deeply amusing about the concept of "slot 3" having
"panicked". :-D
What a great start to my day...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
> From: BoxMonitor
> Subject: Celerra Notification - CS0, CRITICAL, BoxMonitor
>
> Event Time: Nov 23 14:33:04 2009
>
> Brief Description: Slot 3 has panicked.
>
> Full Description:
> The operating system running on the slot has panicked. The Data Mover
> slot will be failed over, if possible, and rebooted.
>
>
>
>
> From: BoxMonitor
> Subject: Celerra Notification - CS0, CRITICAL, BoxMonitor
>
> Event Time: Nov 23 14:36:51 2009
>
> Brief Description: Slot 3 Both internal interfaces are down.
>
> Full Description:
> The Control Station is not able to communicate with either of the
> (local) network interfaces of the identified Data Mover (slot). The
> operating system running on the identified Data Mover may be
> unresponsive. The specified Data Mover will be failed over, if possible,
> and rebooted.
>
>
>
>
Event Time: Nov 23 15:27:26 2009
Brief Description: Slot 3 reason code of 3 is stale.
Full Description:
The Data Mover identified by the slot location is reporting an
unexpected status code indicating it may not have booted and initialized
correctly. The specified Data Mover will be failed over, if possible,
and rebooted.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> From: BoxMonitor
>> Subject: Celerra Notification - CS0, CRITICAL, BoxMonitor
>>
>> Event Time: Nov 23 14:33:04 2009
>>
>> Brief Description: Slot 3 has panicked.
>>
>> Full Description:
>> The operating system running on the slot has panicked. The Data Mover
>> slot will be failed over, if possible, and rebooted.
>>
>>
>> From: BoxMonitor
>> Subject: Celerra Notification - CS0, CRITICAL, BoxMonitor
>>
>> Event Time: Nov 23 14:36:51 2009
>>
>> Brief Description: Slot 3 Both internal interfaces are down.
>>
>> Full Description:
>> The Control Station is not able to communicate with either of the
>> (local) network interfaces of the identified Data Mover (slot). The
>> operating system running on the identified Data Mover may be
>> unresponsive. The specified Data Mover will be failed over, if
>> possible, and rebooted.
>>
>>
>
> Event Time: Nov 23 15:27:26 2009
>
> Brief Description: Slot 3 reason code of 3 is stale.
>
> Full Description:
> The Data Mover identified by the slot location is reporting an
> unexpected status code indicating it may not have booted and initialized
> correctly. The specified Data Mover will be failed over, if possible,
> and rebooted.
Event Time: Nov 23 15:38:03 2009
Brief Description: Enclosure 0 CPU module B fault.
Full Description:
The specified Data Mover CPU blade is faulted.
I'd say somebody somewhere is going to have a really great morning when
they arrive at the office. ;-)
Also... They really have *blade servers* over there??
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
> Event Time: Nov 23 15:38:03 2009
>
> Brief Description: Enclosure 0 CPU module B fault.
>
> Full Description:
> The specified Data Mover CPU blade is faulted.
6 duplicates and counting... :-D
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> Event Time: Nov 23 15:38:03 2009
>>
>> Brief Description: Enclosure 0 CPU module B fault.
>>
>> Full Description:
>> The specified Data Mover CPU blade is faulted.
>
> 6 duplicates and counting... :-D
Now 9 duplicates, plus this:
Event Time: Nov 23 16:19:22 2009
Brief Description: Enclosure 0 CPU module B NAS Personality Module fault.
Full Description:
A CPU NAS personality module fault has occurred. The NAS personality
module is a daughterboard attached to the blade. The logic for the four
external gigabit Ethernet ports is contained on the NAS personality
module daughterboard. This event indicates a fault occurred on the NAS
personality module and the daughterboard probably needs to be replaced.
...so it's personality has failed? LOL!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> Event Time: Nov 23 15:38:03 2009
>>
>> Brief Description: Enclosure 0 CPU module B fault.
>>
>> Full Description:
>> The specified Data Mover CPU blade is faulted.
>
> 6 duplicates and counting... :-D
Currently at about 35 duplicates and still climbing.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/23/2009 5:21 AM, Invisible wrote:
> ...so it's personality has failed? LOL!
Mine fails all the time ;)
Nothing new ...
Is this coming from the U.S. servers? Somebody is going to have a rough
day for sure...
--
~Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> ...so it's personality has failed? LOL!
>
> Mine fails all the time ;)
>
> Nothing new ...
Heh. One time I took one of those stupid online "personality tests".
I failed the test.
*rimshot*
> Is this coming from the U.S. servers?
Yup. Certainly *I* don't have any blade servers or anything nearly so
sophisticated. ;-)
> Somebody is going to have a rough day for sure...
Apparently not. I just got an email to say "ignore this; the technition
is working on it". Couldn't have told me that on Friday, no?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible <voi### [at] dev null> wrote:
> >> Event Time: Nov 23 15:38:03 2009
> >>
> >> Brief Description: Enclosure 0 CPU module B fault.
> >>
> >> Full Description:
> >> The specified Data Mover CPU blade is faulted.
> >
> > 6 duplicates and counting... :-D
>
> Now 9 duplicates, plus this:
>
>
>
> Event Time: Nov 23 16:19:22 2009
>
> Brief Description: Enclosure 0 CPU module B NAS Personality Module fault.
>
> Full Description:
> A CPU NAS personality module fault has occurred. The NAS personality
> module is a daughterboard attached to the blade. The logic for the four
> external gigabit Ethernet ports is contained on the NAS personality
> module daughterboard. This event indicates a fault occurred on the NAS
> personality module and the daughterboard probably needs to be replaced.
>
>
>
> ...so it's personality has failed? LOL!
LOL
hope the machine doesn't get paranoid... :P
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible <voi### [at] devnull> wrote:
> >> Event Time: Nov 23 15:38:03 2009
> >>
> >> Brief Description: Enclosure 0 CPU module B fault.
> >>
> >> Full Description:
> >> The specified Data Mover CPU blade is faulted.
> >
> > 6 duplicates and counting... :-D
>
> Currently at about 35 duplicates and still climbing.
Better push some button somewhere...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
