| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||
Solution Type Problem Resolution Sure Solution 1002254.1 : How to Upgrade Single Sun StorEdge[TM] T3+ Firmware in a Non-Disruptive Way
PreviouslyPublishedAs 203177 Symptoms Customer data is mirrored by DiskSuite[TM] on a pair of workgroup Sun StorEdge[TM] T3+ running firmware 2.00.01. Customers wanted no downtime on Sun Fire[TM] 480R production mail server during the T3+ firmware v3.1.5 upgrade period. Resolution To have full T3+ data access during the firmware upgrade process, the pre-requirement is to have T3+ data mirrored externally. The best case is if there is one more T3+ brick to be used as a mirror. However, the T3+ data can also be mirrored through different disk arrays like A5200 or SAN disk arrays as long as the same storage driver stack is used. In this customer case, Online:DiskSuite[TM] is used to mirror the data on two workgroup T3+. The logical steps to have T3+ firmware upgraded in a non-disruptive way are as follows: . Detach submirror from mirror set. . Remove metadb entry for the detached submirror. . Offline the T3+ from the server. . Perform the T3+ firmware upgrade. . Online the T3+ for the server. . Recreate the metadb entry for the detached submirror. . Reattach the submirror to the original mirror set. . Verify the success firmware upgrade and online of T3+. Below is a step by step example procedure to accomplish the T3 firmware upgrade from v2.00.01 to v3.1.5 in a non-disruptive way. The production environment on the server with data on the single T3+ brick is maintained during the T3+ firmware upgrade period. No server downtime is involved. The Disksuite mirror set d50 contains two submirrors d101 and d102. The metadb copies are on c0t0d0s7 and c1t1d0s7 and c2t1d0s7. Controller c0 is for boot disk. Controllers c1 and c2 are for the two mirrored T3+ through two different Sun hubs. The mirror set name, submirror names, controller numbers, and the slice numbers for the metadb may be different for different customers. 1. Backup T3+ data for data restore if needed. 2. On server: . Detach the submirror d102 from mirror set d50. # metadetach d50 d102 . Remove the metadb entry for d102. # metadb -d c1t1d0s7 . Offline the T3+ which firmware upgrade will be performed. Server format command output will not show c1t1d0 after below luxadm command. # luxadm -e offline /dev/rdsk/c1t1d0s2 3. Follow the firmware upgrade procedure described by the Patch ID 115180-07. 4. Recreate metadb and reattach detached mirror member d102 to d50 mirror set on server: . Log into server as root. . Verify the output from format command shows c1t1d0 entry if not, issue command # luxadm -e online /dev/rdsk/c1t1d0s2 . # metadb -a -c 3 c1t1d0s7 . # metattach d50 d102 . # luxadm probe . # luxadm display 5. Repeat steps 2 through 4 for the second submirror d101 with different metadb device c2t1d0s7 and proper disk firmware types from the second T3+. Product Sun StorageTek T3+/6X20 Controller Firmware 3.1 Sun StorageTek T3+ Array T3+, T3B, Firmware 3.1.5, nondisruptive, Patch 115180, luxadm, DiskSuite Previously Published As 79684 Change History Date: 2005-01-13 User Name: 7058 Action: Approved Comment: Trademarks in place where needed. Rephrased a few sentences for easier reading. Spell ck OK. Couldn't find dups anywhere Review date OK. OK to publish. Version: 5 Attachments This solution has no attachment |
||||||||||||
|
||||||||||||