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

Asset ID: 1-72-1017973.1
Update Date:2009-09-17
Keywords:

Solution Type  Problem Resolution Sure

Solution  1017973.1 :   patched Sun StorEdge[TM] 6920 components still show up under "Revision Maintenance - Upgrade"  


Related Items
  • Sun Storage 6920 System
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
  •  

PreviouslyPublishedAs
229249


Symptoms
After performing a firmware upgrade, on a Sun StorEdge[TM]6920, there are components that can still be selected for patching. If you connect to the component and check the version you will see that the upgrade was successful. Attempting to upgrade again doesn't change this status.

Resolution
This problem is caused by the /var/opt/SUNWstade/DATA/Inventory.golden file not being updated with the current information. Here is an example of an incorrect entry in the Inventory.golden file:
'sysRevision' => 'D02.02.01.0138',
'name' => 'dsp00',
'ip' => '192.168.0.10',
This DSP was upgraded to 02.02.01.189 (URB22) but the Inventory.golden file is still listing 02.02.01.0138. Since the information in the Inventory.golden is incorrect, when you generate a patch report in Storade you will see the DSP listed as a component that can be patched.
There are 2 possible resolutions:
1 - Generate a new inventory to update the Inventory.golden file
- From the "Storage Automated Diagnostic Environment" select the Inventory tab. Under the Actions pull down select "Generate New Inventory". In the new window select the "Generate" button. Once the screen refreshes, select the save button.
Once we have the new inventory saved, select the "Rack Inventory" link on the top right side of the window. Under the "Actions" pull down select "upgrade". In the new window select the "Clear Upgrade Report" button and then select the "Generate Upgrade Report" button. The upgrade report should be correct.
2 - If the first option doesn't help, rename the Inventory.golden file and run through the procedure in step 1 again.


Product
Sun StorageTek 6920 System

Internal Comments
This issue may also occur with 6320's. I didn't have examples and couldn't find documented cases so I didn't include the 6320 in this SRDB.

6920, patch, revision, maintenance
Previously Published As
88028

Change History
Date: 2006-12-14
User Name: 95826
Action: Approved
Comment: - verified metadata
- review date ok : 2007-12-12
- checked for TM - 2 added + full product name
- checked audience : contract
Publishing
Version: 3
Date: 2006-12-14
User Name: 95826
Action: Accept
Comment:
Version: 0
Date: 2006-12-14
User Name: 38107
Action: Approved
Comment: Doc will be useful
Version: 0
Date: 2006-12-12
User Name: 39181
Action: Approved
Comment: I've had this question asked quite a few times so thought it would be a good doc. We are pushing customers to upgrade and may run into this issue often.
Version: 0
Date: 2006-12-12
User Name: 39181
Action: Created
Comment:
Version: 0
Product_uuid
67794720-356d-11d7-8ef2-ce2ac2bc9136|Sun StorageTek 6920 System

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