polyfuze0411
2 Bronze

CX3-20 uptime

Jump to solution
Hi Guys,

Any idea on how to check uptime for cx3-20f?

Thanks
Labels (1)
0 Kudos
1 Solution

Accepted Solutions
Bor4s
1 Nickel

Re: CX3-20 uptime

Jump to solution

Remember as was pointed before clariion has 2 SP's and each one can be rebooted separately

Follow these steps:

  1. In Navisphere right click on the SP on the specific array that you want to check At the “Confirm:Event Viewer” Pop up window hit “Yes” to continue.
  2. At the bottom of the SPx event window hit the “Filters” button.
  3. In the “Event Filters:” window uncheck all but the “Information” check box.
  4. In he View by event code selection box scroll down and select the event code group 0x79500000 – 0x7900ffff and hit “OK.”
  5. The occurrence of every event code “0x79500000:Dynamic Strings:Reboot:………….” will be displayed.
  6. Find the most recent occurrence of the reboot event.
  7. By comparing the current date and time with the date and time of the last reboot the uptime of the SP can be determined.
  8. To determine how long the array has been up check the last time both SPs rebooted at the same time. (SPs can reboot one at a time for various reasons but that does not indicate that the array was down)

The other way to determine the uptime of the array is to have SPCollects analyzed running Triiage - but this tool available only for EMC support peronal.

0 Kudos
4 Replies
ovivier
2 Iron

Re: CX3-20 uptime

Jump to solution
Hi,

I haven't seen anything in Navicli, I think the best way is to look at SP events. Anyway "uptime for a CX" has no sense, as it is composed of two SPs, so you will have to look at both uptimes. You may have an event like "SP initializing" for each SP, but it may depend on the FLARE you are running,

Unfortunately the total events size is limited so if you have too many events you will loose the olders.

Hope this helps
mumpster1
1 Copper

Re: CX3-20 uptime

Jump to solution

I found only one more or less reliable way if try to look for Microsoft (R) Windows pattern in log file.

For example:

path> grep 'Microsoft (R) Windows' cx40/SPA_navi_getlog.txt
04/26/2008 09:09:52                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.
04/26/2008 11:52:09                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.
04/27/2008 08:08:33                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.
04/27/2008 08:53:09                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.
10/24/2008 07:17:07                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.
10/24/2008 07:51:21                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.
10/24/2008 07:58:43                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.
10/24/2008 08:49:19                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.
10/24/2008 11:31:16                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.
path> grep 'Microsoft (R) Windows' cx10/SPA_navi_getlog.txt
12/06/2007 17:46:47                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.
02/19/2008 14:54:16                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.
02/20/2008 15:00:28                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.
04/20/2008 06:25:31                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.
07/29/2008 06:12:31                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.

But beware that Event Log may miss some old information like there:

path> grep 'Microsoft (R) Windows' SPA_navi_getlog.txt

08/25/2009 07:40:21                      (1779)Microsoft (R) Windows (R) 5.01. 2600 Service Pack 1 Multiprocessor Free.

I know for sure there are many halts and reboots in past but they all have gone.

So for a very long uptime you won't gain anything in this case.:(

Hope it would help for someone.

Bor4s
1 Nickel

Re: CX3-20 uptime

Jump to solution

Remember as was pointed before clariion has 2 SP's and each one can be rebooted separately

Follow these steps:

  1. In Navisphere right click on the SP on the specific array that you want to check At the “Confirm:Event Viewer” Pop up window hit “Yes” to continue.
  2. At the bottom of the SPx event window hit the “Filters” button.
  3. In the “Event Filters:” window uncheck all but the “Information” check box.
  4. In he View by event code selection box scroll down and select the event code group 0x79500000 – 0x7900ffff and hit “OK.”
  5. The occurrence of every event code “0x79500000:Dynamic Strings:Reboot:………….” will be displayed.
  6. Find the most recent occurrence of the reboot event.
  7. By comparing the current date and time with the date and time of the last reboot the uptime of the SP can be determined.
  8. To determine how long the array has been up check the last time both SPs rebooted at the same time. (SPs can reboot one at a time for various reasons but that does not indicate that the array was down)

The other way to determine the uptime of the array is to have SPCollects analyzed running Triiage - but this tool available only for EMC support peronal.

0 Kudos
Highlighted
RRR
5 Tungsten

Re: CX3-20 uptime

Jump to solution

I've seen events in the SP event logs mentioning the uptime. I'm not sure if this also works on older CX3's, but on CX4 it's definately present. Open the event log and set a filter on "uptime".