Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Problem Resolution Sure Solution 1004090.1 : DKU Microcode exchange is stopped with SVP messages SMT3167E
PreviouslyPublishedAs 205694 Symptoms When upgrade Sun StorEdge[TM] 9980V Microcode to current RGA (21-14-30-00/00) using online exchange procedure, while the upgrade process were at the stage of DKU micro-program upgrade, the following error messages SMT3167E where received at the SVP (Service Console) "Driver information acquisition failed for the following HDD: HDDR16-1A" Click "OK", and system came back with: "SMT2435E" An exchange of a microprogram finished abnormally. Please check subsystem status and microprogram version with MAINTENANCE, and also, check information from log -> Information for details: Upon reviewing the Running/FW (firmware) informations from maintenance, and compared them with ECN (21-14-30-00/00) Micro-program version list, all micro-programs such as SVP,SSVP,DKCMAIN,LCP,CUDG,RAM Boot.etc were all upgraded as listed in the ECN (Engineering Change Number) bulletin. Retry the process by just upgrading DKU micro-program, error persisted with error messages with "SMT3167E" on HDDR16-1A. Micro-program - DKU upgrade still failed which prevent the completion of the Microcode update leaving version up procedures, such as: config version up, config backup, etc. unable to proceed. Resolution (1) Check the faulty HDDR16-1A with MAINTENANCE tool, it was in normal status but not failed. (2) Replace HDD (Hard Disk) - HDDR16-1A. For detailed, follow the disk replacement procedure of the maintenance manual for HDD normal status (Not failed) replacement and remember to do correction copy. (3) When the correction copy end and completed successfully, complete the related SIM (System Information Messages). (4) Re-run DKU Micro-program upgrade. This time, the upgrade process completed successfully and reported: "The DKU microprogram is not updated because of the same revision." (If there is actual needs for DKU FW upgrade, of course, system will automatically start the microcode upgrade) "An exchange of a microprogram finished normally. Please check subsystem status and microprogram version with MAINTENANCE" What the above meant was that Microcode upgrade were successfully ended now. (5) Remember to follow-up on all the remaining procedure according to microcode ECN version up procedures. Product Sun StorageTek 9980 System Internal Comments "Driver information aquisition failed for the following HDD: HDDR16-1A" means that system could not read HDDR16-1A's Disk Firmware informations during DKU - micro-program upgrade stage, so, system could not determin whether it need to upgrade the faulty HDD's disk firmware. DKU, micro-program, microcode, Driver information aquisition failed Previously Published As 88450 Change History Date: 2007-04-05 User Name: 95826 Action: Approved Comment: - verified metadata - changed review date to 2008-04-05 - checked for TM - 1 added + full product name - checked audience : contract Publishing Version: 3 Date: 2007-04-05 User Name: 95826 Action: Accept Comment: Version: 0 Date: 2007-04-05 User Name: 128938 Action: Approved Comment: I had review the document and make some cosmetic changes without changing the content of the document. Passing on for Final Review. Version: 0 Date: 2007-04-04 User Name: 128938 Action: Accept Comment: Version: 0 Date: 2007-04-04 User Name: 97961 Action: Reassign Comment: Moved to correct Tech Group as per request from author. Version: 0 Date: 2007-04-04 User Name: 100761 Action: Add Comment Comment: This document should be reviewed by "Storage" Tech team. The submitter should re-submit this document to Storage team for tech review. - Srinivas. Version: 0 Date: 2007-02-06 User Name: 125432 Action: Approved Comment: Expert, Please kindly help to review this doc, any error need to be corrected, please let me know. Thanks, Willis Version: 0 Date: 2007-02-06 User Name: 125432 Action: Created Comment: Version: 0 Product_uuid c2428fbe-8ab7-41d0-8b6e-ab489823c9d4|Sun StorageTek 9980 System Attachments This solution has no attachment |
||||||||||||
|