![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Technical Instruction Sure Solution 1429544.1 : Sun Storage 7000 Unified Storage System: How to install an IDR
Applies to:Sun Storage 7210 Unified Storage System - Version Not Applicable and laterSun 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 an IDR, what is an IDR and why is it needed ...
Engineering ZFSSA IDR information Sun ZFS Storage Appliances Troubleshooting Resource Center (Doc ID 1416406.1)
SolutionInstalling an IDRHow 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://dogoro.us.oracle.com/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) Example head2# /usr/lib/ak/update/up_stage0 /tmp/ak-nas-2011-04-24-4-0-1-2-21-10-2.pkg.gz pkgtrans: ERROR: unable to complete package transfer - no packages were selected from </var/tmp/aaau3aW2D>/usr/lib/ak/update/up_stage0: line 112: AKTXT_UP_STAGE0_ERROR: ak-nas-2011-04-24-4-0-1-2-21-10-2 Please address any requests to the IDR alias at oak_sw_idr_ww_grp ML <OAK_SW_IDR_WW_GRP@oracle.com All of the IB related fixes in the IDR will be fixed in 2011.1.4 Thanks, Christian
How to install the IDR prior to the 2011.1.x.x Release
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: $ ls /tmp/IDR
kernel/drv/zfs kernel/drv/amd64/zfs
Maintenance->WORKFLOWS
Escalation identifier
Service Request marked "relief-approved" Email address of service personnel New file Path to file on appliance
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" Your.Email@oracle.com
/kernel/drv/zfs
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
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@oracle.com successfully replaced file /usr/lib/amd64/zfs; original saved as /usr/lib/amd64/.zfs.0 (end payload) Attachments This solution has no attachment |
||||||||||||
|