Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1429544.1
Update Date:2012-07-09
Keywords:

Solution Type  Technical Instruction Sure

Solution  1429544.1 :   Sun Storage 7000 Unified Storage System: How to installing an IDR  


Related Items
  • Sun Storage 7410 Unified Storage System
  •  
  • Sun ZFS Storage 7320
  •  
  • Sun Storage 7210 Unified Storage System
  •  
  • Sun Storage 7310 Unified Storage System
  •  
  • Sun ZFS Storage 7120
  •  
  • Sun ZFS Storage 7420
  •  
  • Sun Storage 7110 Unified Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>NAS>SN-DK: 7xxx NAS
  •  
  • .Old GCS Categories>Sun Microsystems>Storage - Disk>Unified Storage
  •  




Applies to:

Sun Storage 7210 Unified Storage System - Version Not Applicable and later
Sun Storage 7310 Unified Storage System - Version Not Applicable and later
Sun ZFS Storage 7120 - Version Not Applicable and later
Sun ZFS Storage 7320 - Version Not Applicable and later
Sun Storage 7410 Unified Storage System - Version Not Applicable and later
7000 Appliance OS (Fishworks)

Goal

How to install IDR and what is an IDR and why is it needed


IDR a Interim Diagnostic Relief


Interim: Until official version with fix is released.
Diagnostic: Option of providing additional bits for debugging.
Relief: Implies customer is in need for a solution

Why is it needed


Urgent need to provide relief to customer. (hours not days or weeks)

  1. Issue happens frequently and is more than just a nuisance.
  2. Situation impacts production
  3. Customer can't wait for minor or micro release.



What has been changed

  1. Till 3.4.2 an IDR was provided as binary fix / T-Patch
  2. Starting with 2011.1 a full new binary release build is compiled for each new IDR
  3. Installed IDRs are listed as IDR in BUI/CLI in section Maintenance -> System -> "Available Updates"
  4. In the BUI the IDR rev/branch is now clearly displayed with a different color
  5. At the CLI you see an asterisk in front of the release number as here:                                     
    *[email protected],1-2.11.3.1 ( [*] : Interim Diagnostics and Relief (IDR) )

Engineering ZFSSA IDR information

Sun ZFS Storage Appliances Troubleshooting Resource Center (Doc ID 1416406.1)

 

Fix

Installing an IDR


How to install the IDR since 2011.1.x

If the IDR is of the form *.pkg.gz, it is a complete installation and should be installed using the process in

https://<system IP or name>:215/wiki/index.php/Maintenance:System:Updates

 

 



 http://rpe.us.oracle.com/bin/view/Tech/AK_IDR_Information

There are some presentations and information floating around which recommends IDR #1.6.
However customer should go with the latest, which includes everything in #1.6. Please go with the latest IDR available.

Also note that IDRs with double digit numbers. E.g. #10.x and higher will require that you install IDR #1.1 first.
This is due to a limit in the SVR4 packaging name length. (A fix is underway)

Please address any requests to the IDR alias at oak_sw_idr_ww_grp ML <[email protected]

All of the IB related fixes in the IDR will be fixed in 2011.1.4 Thanks, Christian

 

How to install the IDR till 3.4.2

To install a binary fix a so called hidden workflow is used to replace file by file, which means that the relief is installed file by file. If the IDR consists of 6 files you need to run the workflow 6 times, for each file once. The hidden workflows are displayed by navigating to Maintenance -> Workflow, hold shift-key and click on the "+" sign next to Workflows on the headline.

The workflow to install a binary relief is called "Temporary patch" and might be listed on the second page of the available workflows.

Example:

In this example the following files will be replaced by files provided through an IDR.

$ ls /tmp/IDR
kernel/drv/zfs
kernel/drv/amd64/zfs


To apply files binary fix ( procedure till 3.4.2) , navigate in the BUI to

Maintenance->WORKFLOWS


click "+" while holding down the SHIFT key. This will reveal a number of hidden workflows. The workflow to install an IDR is listed on the second page of
the workflow list which is available by clicking on the ">>" symbol just below the WORKFLOWS tab.

Look for a workflow called "Temporary patch" and a click on it will bring up a form requesting

Escalation identifier
Service Request marked "relief-approved"
Email address of service personnel
New file
Path to file on appliance


Start by pressing the "BROWSE" button for the "New file" property, then navigate throug the local filesystem and select the "kernel/drv/zfs" file. At this
point an "UPLOAD" button will appear, click this and wait for the file to be uploaded. Then complete the rest of the form with:

Esc ID: xyz
Tick "relief approved"
[email protected]


In the "Path..." box enter the path- and filename of the binary to be replaced:

/kernel/drv/zfs


then press "apply". The workflow will now perform the necessary steps to replace the original binary with the one containing the fix and will backup the original file. The "zfs" module requires these steps to be repeated for the 64bit version of the driver. Upload the file "kernel/drv/amd64/zfs" and provide the correct path to the original binary in the "Path..." box:

/kernel/drv/amd64/zfs


The example shows that for 2 files you need to repeat the necessary steps two times. The workflow can only replace file by file and and needs to be executed for every file provided in an IDR.

Now reboot the system as last step of the IDR installation.



Once booted, confirm the module is active by logging in to the ZFSSA and run "confirm shell"

S7000:> confirm shell

# cd /var/ak/logs
# aklog ./audit.ak|less
.....
Sat Mar 10 00:16:31 2012
nvlist version: 0
address = xx.xx.x.xxx
host = xx.xx.x.xxx
annotation =
user = root

class = audit.ak.xmlrpc.workflow.audit

payload = (embedded nvlist)

nvlist version: 0

name = Temporary patch

payload = Escalation 3-xxxxxxxxxx: [email protected]
successfully replaced file /usr/lib/amd64/zfs;
original saved as /usr/lib/amd64/.zfs.0

(end payload)





Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback