VSM4 VSM5 - How to IML a VTSS from the LOP or DOP

Asset ID:	1-71-2353767.1
Update Date:	2018-02-02
Keywords:

Solution Type Technical Instruction Sure

Solution 2353767.1 : VSM4 VSM5 - How to IML a VTSS from the LOP or DOP

Applies to:

Sun StorageTek VSM4 System - Version All Versions to All Versions [Release All Releases]
Sun StorageTek VSM5 System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

IML the VTSS

IML the VSM4 or VSM5

Solution

Step by step procedure to IML the VSM4 or VSM5

Customer engagement
1) Have the customer vary the VTSS offline
2. Vary the paths and chpids offline to the VTSS
3) Vary the RTDs and VTDs offline

Field Engineer Engagement
VSM4/5 Cold Box IML
1. Connect to the LOP or DOP with the CSE login. Using the LOP, some items may be slightly different.
2. At the CSE Main Menu, click on Configuration/Status Menu>Subsystem Availability and verify the VSM is 100%.
3. Go back to the CSE Main Menu by clicking on Main at the bottom left of the screen.
4. Click on Configuration/Status Menu>FRU Status and verify nothing is fenced. If there is anything fenced, make note of the items and continue.
5. Go back to the CSE Main Menu by clicking on Main at the bottom left of the screen.
6. Click on the Software Release Level.
7. Verify the current code that is running on the VSM is checked.
8. Click on Disruptive Code Load
9. Click on Continue and the Cold Box IML will proceed.
10. Go to the hic_stat display to monitor the progress.
11. Wait 5 minutes and you should see the VSM IML. Total time of the IML should take approximately 30-40 minutes.
12. Wait until the subsystem is back up and IML complete, then log back into the DOP.
13. Repeat steps 2-4 to verify the VSM operation.
14. If there were any items fenced and they are still fenced, make note and get the VSM base files and statesaves (using vshell, allstate $). Upload these files zipped to the service request or SPLAT.

Customer engagement
Have the customer vary the paths, chipids, RTDs, VTSS online.

The below information can be found in the D02.21.00.00 Release notes.

Notes

Ensure no FRUs are fenced before proceeding.
Assure that the operator has varied off all interfaces to the VTSS.

LOP:
1) Navigate to the CSE main menu (PS02).
2) At the CSE main menu (PS02), depress F10 - FILE UTIL.
3) At the file utility menu (FU01), depress F5 - SLCT SSYS.
4) At the select software release level screen (FU11), using the F7 - CURS DOWN or the F6
- CURS UP highlight the current software release level (SRL) that is to be IML'ed.
5) With the required SRL highlighted, depress F10 - IML SRL.
6) At the IML Software Revision Level Menu (FU28), depress F8 DISR LOAD
7) Confirm the selection; depress F9 -YES
8) Upon completion of the IML,
9) IMPORTANT!!!!
• After a Cold IML or NDCL with arrays formed, wait until this
message is observed in hic_stat.dia before performing ANY DOP/LOP
maintenance actions.
"IT IS SAFE TO PERFORM MAINTENANCE ACTIONS"
• Failure to do so could result in maintenance ACTION failures or loss
of configuration data.
10)NOTE: if no arrays are yet formed, wait for message
"CMS: Remaining Freezer Complete' before maintenance actions.
11) Confirm no diagnostic failures before returning the subsystem to the customer

DOP:
1) From 'Software Release Level' screen, select the current software release level (SRL) to be IML'ed.
2) Select IML
3) Upon completion of the IML,
4) IMPORTANT!!!!
• After a Cold IML or NDCL with arrays formed, wait until this message is
observed in hic_stat.dia before performing ANY DOP/LOP maintenance actions.
"IT IS SAFE TO PERFORM MAINTENANCE ACTIONS"
• Failure to do so could result in maintenance ACTION failures or loss of
configuration data.
• note: if no arrays are yet formed, wait for message
"CMS: Remaining Freezer Complete' before maintenance actions.”
5) Confirm no diagnostic failures before returning the subsystem to the customer.

Attachments

This solution has no attachment