Sun StorageTek VSM4 System
 
Sun StorageTek VSM System
 
Sun StorageTek V2X SVA Disk System
 
Sun StorageTek VSM5 System
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: TAPE-CAP VCAP
 

In this Document

Goal

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU CAP

Applies to:

Goal

How to Remove and Replace a VSM : Battery Replacement

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE ENGINEER NEED: Sun Storagetek VSM or V2X Training, including DOP

DELIVERY REQUIREMENT: Schedule with customer.

TASK COMPLEXITY: 4

FIELD ENGINEER INSTRUCTIONS

PROBLEM OVERVIEW:

VSM battery replacement can be done for a couple reasons:

 - The battery is fenced and needs to be replaced.
 - The battery has failed with FSC7464 or FSC7465.
 - The battery is due for replacement based on the age of the battery.
    VSM batteries should be replaced every 4 years as a part of preventative maintenance.

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? :

The subsystem may be in degraded mode, but operational state when a FRU is fenced.

WHAT ACTIONS DOES THE ENGINEER NEED TO TAKE:

     PLEASE NOTE:
     If you are here to replace a fenced battery you do not need to execute the following action plan in its entirety.
     You will only need to replace the fenced battery called out in the field task.

PLEASE ALSO NOTE:
There is a known microcode limitation that can prevent the successful GFR of either a cache battery or the BCU (Battery Charger Unit) if both are fenced.
There is no plan to address this microcode limitation.
The work-around for this issue is addressed in the following knowledge documents:
    - For machines with a floppy reader - MOS Knowledge Document ID 1350128.1.
    - For all SVA or VSM machines (with or without a floppy reader) - MOS Knowledge Document ID 1350205.1.

Parts required for preventative maintenance battery replacement:
     CU.1.PB0 & CU.1.PB1 card (Lithium battery) p/n 307134402 (2 per machine)
     CU.3.BAT0 & CU.3.BAT1 (Black Brick) p/n 307645801 (2 per machine)

Action Plan:

Day 1 of preventative maintenance battery replacements.

ISP battery replacements

1. Identify what ISP card is the slave ISP and this will tell you what PB card to replace first:
    - ISP0 Slave - CU.1.PB0
    - ISP1 Slave - CU.1.PB1

2. GFR no-replace the slave ISP PB card to allow you to replace the PB card.

First PB card:

Select GFR menu
Select List FRU Menu
Scroll to find the “Slave ISP PB card”
Select the slave ISP PB for GFR and when told the card can be replaced go round the back and physically replace this ISP's coin battery (located on the motherboard)
Press the validate button and the GFR will now complete.
Wait 2 minutes then go to the ‘Subsystem debug’ menu
Select ‘Switch ISP Master’
Your DOP will go away then come back – allow at least 10 minutes after the switch before continuing.
Check the Hic_Stat for any unusual messages or failures during switch - check what ISP is master and confirm you are now on the other ISP.
Check the FRU status menu to verify all FRU's are optimal.
If all ok and we are now on the other ISP, continue else stop and escalate.

Second PB card:

Select GFR menu
Select List FRU Menu
Scroll to find the “Slave ISP PB card”
Select the slave ISP PB for GFR and when told the card can be replaced go round the back and physically replace this ISP's coin battery (located on the motherboard)
Press the validate button and the GFR will now complete.

This ends the replacement instructions for the PB card (ISP batteries).
What follows are instructions for replacing the cache battery.

Cache battery

1. Physically replace the first battery CU.3.BAT0 without GFR.
    Now wait 3 - 24 hours.  (This allows batteries that are partially drained while in storage to charge so they can pass GFR requirements.)
2. GFR no-replace CU.3.BAT0 using FRU replacement procedures
    - Select GFR menu
    - Select List FRU Menu
    - Scroll to find "CU.3.BAT0" and select it for GFR and validate it when told it is ready for replacement - verify it completes successfully x0000.

    - If it fails with 7465 then you need to wait 24 hours

Day 2 of preventative maintenance battery replacements.

1. If the GFR of CU.3.BAT0 has not been performed or failed previously, perform it now but if it was successful skip to step 2
    - Select GFR menu
    - Select List FRU Menu
    - Scroll to find "CU.3.BAT0" and select it for GFR and validate it when told it is ready for replacement - verify it completes successfully x0000
2. Physically replace the battery CU.3.BAT1.
    Now wait 3 - 24 hours.  (This allows batteries that are partially drained while in storage to charge so they can pass GFR requirements.)
3. Select GFR menu
    - Select List FRU Menu
    - Scroll to find "CU.3.BAT1" and select it for GFR and validate it when told it is ready for replacement - verify it completes successfully x0000.

    - If it fails with 7465 then you need to wait or come back after 24 hours

Note: The service manual implies that both batteries must always be replaced at the same time.  It is not mandatory to replace both batteries in order to recover the one that failed, but replacing both is recommended as a proactive measure aimed at preserving data integrity.  PLEASE follow the maintenance action above as to how and when to replace the batteries.

CONFIRM THE FIX BY:

Check sub-system availability and that the subsystem is 100% with no fenced FRUs - specifically verify a battery or battery charger is not fenced.

WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE: None.

PARTS NOTE: N/A

TIME ESTIMATE: 60 minutes for a single battery GFR

REFERENCE INFORMATION:

VTSS for VSM4-VSM4e with DOP - Installation and Service Guide

VTSS for VSM4 FICON - Installation, Operation, and Maintenance Guide
VTSS for VSM4-VSM4e with Local Operator Panel - Installation and Service Guide

VTSS for VSM5 - Installation and Service Guide

This solution has no attachment