How to Determine Uptime of Sun Storage[TM] 2500, 2500-M2 and 6000 Disk Arrays

Asset ID:	1-71-1455525.1
Update Date:	2017-05-12
Keywords:

Solution Type Technical Instruction Sure

Solution 1455525.1 : How to Determine Uptime of Sun Storage[TM] 2500, 2500-M2 and 6000 Disk Arrays

Applies to:

Sun Storage 6140 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 6180 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2540 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2510 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2530 Array - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Goal

How to determine uptime of Sun Storage[TM] 2500, 2500-M2 and 6000 Disk Array

Solution

1. Collect the stateCaptureData.dmp file:

The stateCaptureData.dmp file can be collected by any one of two methods below:

Method1:
Collect supportdata of the array. Reference Document 1002514.1 Collecting Sun Storage Common Array Manager Array Support Data.
This supportdata contains the stateCaptureData.dmp file.
Method2:
Create a stateCaptureData file manually using the 'service' command:

service -d <device> -c save -t state -p <dir> -o <filename>

where <device>   = The name of the array, or IP address of any of the controllers.
         <dir>         = The directory to store the result file.
         <filename> = The filename for the result file.

Note: The location of the 'service' command in CAM management host:
Solaris: /opt/SUNWsefms/bin/
Windows: C:\Program Files\Sun\Common Array Manager\Component\fms\bin
Linux: /opt/sun/cam/private/fms/bin

2. Locate the 'getObjectGraph_MT(1,0...)' output and 'bootTime' value in the stateCaptureData.dmp file:

Locate the 'getObjectGraph_MT(1,0...)' output by opening the stateCaptureData.dmp file, and search for the keyword "getObjectGraph_MT". The 'bootTime' value is reported under 'getObjectGraph_MT(1,0...)'.

For Example:

Executing getObjectGraph_MT(1,0,0,0,0,0,0,0,0,0) on controller A:
CONTROLLER - 0x12345678
. . .
bootTime : 0x4f0b7397
. . .

Note: In a Dual Controller Array, there will be two 'getObjectGraph_MT(1,0...)' outputs, one for each controller. The example above shows Controller A output.

If 'bootTime' value is found, it's the time the controller completed its last boot cycle. It is HEX value in unix time format (also known as Epoch time).
Convert this time format to standard date format, you may use pearl script ($ perl -e 'print scalar(localtime(<time_value_in_decimal>)), "\n"') to do the conversion.
For example:

0x4f0b7397 equals to 1326150551
. . . .
. . . .
$ perl -e 'print scalar(localtime(1326150551)), "\n"'
Tue Jan 10 07:09:11 2012
Find the controller uptime, by calculating the difference between the current time and the boot time value found above.
The 'bootTime' value is not collected for certain firmware versions. If the value is not found, proceed to Step 3.

Note: bootTime is value is found only for 06.70, 07.77 and 07.8x firmware versions stateCaptureData.dmp, and it's not found for 06.19, 06.60, 07.35, 07.50 and 07.60 series.

3. Locate 'chall' (or) 'fcAll' output and 'Tick' value in the stateCaptureData.dmp file:

Locate 'chall' or 'fcAll' output by opening the stateCaptureData.dmp file, and searching for the keyword 'chAll' (or) 'fcAll'. These outputs are associated with a 'Tick' value.

Example 'chall' output:

Executing xxxx(x,x,x,x) on controller A:

-> chall 0

chAll (Tick 0029858754) ==> 05/02/12-23:59:58 (GMT)

Example 'fcAll' output:

Executing fcAll(0,0,0,0,0,0,0,0,0,0):

fcAll (Tick 0029858754) ==> 05/02/12-23:59:58 (GMT)

Note: In a Dual Controller Array, there will be two 'chall' (or) 'fcAll' outputs, one for each controller. From the example above, the output represents for Controller A.

"Tick" value is the controller's uptime: 60 Ticks equal One Second. Note that the tick value can either be Positive or Negative, it is positive up to 2147483648 (or 0x80000000) at which point it becomes a negative value and reduces back down to zero to reach the max 0xFFFFFFFF (or 4294967296).

If the Tick value is Negative, proceed to Step 4.
If the Tick value is Positive, proceed to Step 5.

4. Convert the tick value from Negative to Positive:

To get actual Tick value, Deduct the Negative Tick value from 4,294,967,296.

For example:

Executing xxxx(x,x,x,x) on controller A:

-> chall 0

chAll (Tick -1874383274) ==> 05/04/12-06:53:36 (GMT)

Negative Tick value = -1874383274
Actual Tick Value = 4294967296 - 1874383274 = 2420584022

Calculate the Actual Tick value using the example above, and then proceed to Step 5.

5. Determine Controller Uptime:

60 Ticks equals One Second. Divide the Tick value by 5184000 (60ticks * 60seconds * 60minutes * 24hours) to get Controller uptime in Days.

For example:

Actual Tick Value = 2420584022

2420584022 / 5184000 = 466.93 days

Note: In a Dual Controller Array, there will be two Tick values as noted in Step 2. Thus the calculation should be done for Both controllers.

Do you still have questions? You can use My Oracle Support Communities. Communities put you in touch with industry professionals like yourself. They are monitored by Oracle support engineers, so you can expect reliable and correct answers. Ask questions and see what others are asking about in the Disk Storage 2000, 3000, 6000 RAID Arrays & JBODs Community.

Internal Notes for Oracle TSE:

We can get the Tick value by executing "vxAbsTicks" command from Controller shell.

Note: ***This command should only be executed by Oracle Engineer. Serial shell passwd should not be shared with Customer ***

For example:

-> vxAbsTicks
vxAbsTicks = 0x22d360: value = 15971913 = 0xf3b649

Here 15971913 - Tick value in Decimal
0xf3b649 - Tick value in Hex

Note: If the Decimal Tick value is Negative, use either the Hex value directly, or Step(4) above to convert from negative to positive.

Attachments

This solution has no attachment