StorageTek Virtual Storage Manager System 6 (VSM6)
 

PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VSM6
 

In this Document

Symptoms

Cause

Solution

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: changed to partner distribution

Applies to:

Symptoms

Support file bundles (SFB) and/or Statesave files are created with a file name that has a Serial Number value that does not match the VSM6 System Serial number

Cause

ILOM FW update caused tools to access the incorrect VSM6 system serial number

Solution

Exposure:

--6.0.6 and 6.0.5 VSM6 systems are exposed to an issue where support file bundles were created with the value AK00000000-*.bz2

--6.0.7.00 and higher systems are exposed to an issue where support file bundles and statesave file names contain the chassis serial number instead of the vsm6 system serial number

Prerequisite:

--VSM6 must be at code level 6.1.0.07.000 or higher

--CAM version 6.9.1.7 released with 6.1.0.07.000 must be installed.

Action:

--Verify condition exists

--Execute an existing script on each VSM6 node to update system serial number file stored on the system.

--Validate correct file names

Please perform the below steps to update the SysSerNum file on both nodes.

This procedure is non-disruptive and does not affect customer operations.

Perform the following actions from BOTH nodes.

 
1) Determine correct product serial number using ipmitool command:

     Verify the “Product Serial” value is the same on both nodes

     vsmadm@vsmpriv1:~$ /usr/sbin/ipmitool fru print 3

Output Example:
FRU Device Description : /SYS (LUN 0, ID 3)
 Chassis Type          : Rack Mount Chassis
 Product Manufacturer  : Oracle Corporation
 Product Name          : SPARC T4-2
 Product Part Number   : 7066956
 Product Serial        : AK00249072

2) Show current value of product serial number in SysSerNum file:

    vsmadm@vsmpriv1:~$ /usr/bin/cat /var/opt/StatusService/output/SysSerNum | /usr/bin/awk '{print $1}'

Output Example:
AK00249072

3) Force an update of the file:

    vsmadm@vsmpriv1:~$ cd /opt/vsm/bin

    vsmadm@vsmpriv1:/opt/vsm/bin$ sudo ./createSysSerNumFile.pl -f

Output Example:
option: -f
Removing previous file, creating new file
Using ipmitool to get Serial Number, please wait ...
/var/vsm/SysSerNum created successfully (ipmitool) - system serial number: <AK00249072>

4) Restart StatusService:

    vsmadm@vsmpriv1:/opt/vsm/bin$ sudo /opt/VSM6cam/ss_cam/restart_service StatusService

5) Run ManualNoASR to trigger a manual SFB

    vsmadm@vsmpriv1:/opt/vsm/bin$ sudo /var/opt/StatusService/scripts/ManualNoASR

6) Wait 20 minutes and go to the following directory to display the stored SFBs and verify that the created SFB *.bz2 file contains the correct serial number in the file name.  The name will have a date code corresponding to the date/time it was created.

     ls /var/opt/StatusService/output/archive

Example:
AK00249072-vsmpriv1-2014.11.19_17.11.25.tar.bz2

7) If a problem already exists trying to connect to VLE, it may be necessary to shut down and reboot the VSM after correcting the serial numbers.

This step is disruptive and the VSM needs to be taken offline to all customer activity.

See chapter 8 in the microcode release notes for instructions to terminate the VSM resources, and reboot each node.

This solution has no attachment