C H A P T E R  4

Battery FRUs

This chapter provides instructions for removing and installing batteries and battery modules. The FC arrays have an independent battery module located above each I/O module. The SCSI arrays contain a battery on each controller module.

The battery dating information is the same for all batteries.

Topics covered in this chapter are:


4.1 Battery Operation

Your lithium ion battery should be changed every two years if the unit is continuously operated at 77°F (25°C). If the unit is continuously operated at 95°F (35°C) or higher, it should be changed every year. The shelf life of the battery is three years.

In the event of a power failure, the battery maintains power to the cache for 72 hours. When power is restored, the data in cache is dumped to disk.



Note - The RAID controller has a temperature sensor which shuts off battery charging above 129°F (54°C). When this happens, the battery status might be reported as BAD, but no alarm is written to the event log since no actual battery failure has occurred. This behavior is normal. As soon as the temperature returns to the normal range, battery charging resumes and the battery status is reported correctly. It is not necessary to replace or otherwise interfere with the battery in this situation.



The battery LED (on the far right side of the controller module) is amber if the battery is bad or missing. The LED blinks green if the battery is charging, and is solid green when the battery is fully charged.



Note - The batteries in controller FRUs experience discharge during shipment and might require an extended charging cycle upon initial power-up. Nominal battery operation is achieved when the battery status LED changes from amber to flashing green within 25 minutes after the initial power cycle. If the battery status LED remains amber for more than 25 minutes after the initial power-up, then the unit must be power cycled to initiate the extended charging cycle. If the battery status LED remains amber for more than 30 minutes after initiating the extended charging cycle, contact Sun service personnel for additional instructions.




4.2 Battery Status on the Initial Firmware Screen

The initial firmware screen displays the battery status at the top where BAT: status displays somewhere in the range from BAD to ----- (charging) or +++++ (fully charged).

For maximum life, lithium ion batteries are not recharged until the charge level is very low, indicated by a status of -----. Automatic recharging at this point takes very little time.

A battery module whose status shows one or more + signs can support cache memory for 72 hours. As long as one or more + signs are displayed, your battery is performing correctly.

TABLE 4-1 Battery Status Indicators

Battery Display

Description

-----

Discharged; the battery is automatically recharged when it reaches this state.

+----

Adequately charged to maintain cache memory for 72 hours or more in case of power loss. Automatic recharging occurs when the battery status drops below this level.

++---

Over 90% charged; adequate to maintain cache memory for 72 hours or more in case of power loss.

+++--

Over 92% charged; adequate to maintain cache memory for 72 hours or more in case of power loss.

++++-

Over 95% charged; adequate to maintain cache memory for 72 hours or more in case of power loss.

+++++

Over 97% charged; adequate to maintain cache memory for 72 hours or more in case of power loss.



4.3 Battery Dating on the Battery Labels

The battery modules display a serial number/part number label, whose placement on the battery is shown in FIGURE 4-1 and FIGURE 4-2.

The serial number bar code is a seven-digit code that indicates the place of manufacture, followed by a dash (-), followed by a four-digit code that indicates the date of manufacture, followed by a supplier-assigned serial number.

In FIGURE 4-1, the example date of battery manufacture is indicated by "0240," where "02" is the year of manufacture and "40" is the week of manufacture. If a battery does not have a serial number/part number label, the manufacture date for the battery is August 2002. The number below the bottom bar code is the part number (for example, 3705555-04).

  FIGURE 4-1 Battery Label Example for the Sun StorEdge 3310 SCSI Array

Figure showing battery label with serial number and with date code included in part number.

  FIGURE 4-2 Battery Label Example for the Sun StorEdge 3510 FC Array

Figure showing battery label with serial number and with date code included in part number.


4.4 Replacing a Battery or Battery Module

This section explains how to remove an existing battery or battery module and install a new one. The following procedures are guidelines for replacing battery FRUs in SCSI and FC arrays.



Note - The batteries in controller FRUs experience discharge during shipment and might require an extended charging cycle upon initial power-up. Nominal battery operation is achieved when the battery status LED changes from amber to flashing green within 25 minutes after the initial power cycle. If the battery status LED remains amber for more than 25 minutes after the initial power-up, then the unit must be power cycled to initiate the extended charging cycle. If the battery status LED remains amber for more than 30 minutes after initiating the extended charging cycle, contact Sun service personnel for additional instructions.



4.4.1 Replacing a SCSI Battery



caution icon

Caution - In a single controller array, you must power off the array before replacing the battery. For instructions on powering off the array, see Section 1.4, Powering Off the Array.





caution icon

Caution - In a dual controller array, if you plan to replace the batteries in both controllers, you must complete all the following steps for the first controller and battery before performing the steps for the second controller; otherwise, the array disconnects and goes offline.



When replacing the battery in a dual controller array, you should first force-fail the controller.

To force-fail a primary controller:

single-step bulletFrom the RAID firmware Main Menu, choose "view and edit Peripheral devices right arrow Set Peripheral Device Entry right arrow Redundant Controller right arrow force Primary controller failure," and then choose Yes to confirm your choice.

The primary controller is disabled and the array fails over to the secondary controller.

To force-fail a secondary controller:

1. From the RAID firmware Main Menu, choose "view and edit Peripheral devices right arrow Set Peripheral Device Entry right arrow Redundant Controller right arrow force Secondary controller failure," and then choose Yes to confirm your choice.

A message confirms that the controller has been failed.

2. Press Escape to clear the message.



caution icon

Caution - Use extreme care while removing the controller module. The controller module has many electrostatic discharge (ESD) sensitive components and should be handled using ESD protection. Follow Section 1.2, Static Electricity Precautions for all procedures.



To replace a SCSI array battery, perform the following steps (see FIGURE 4-3 through FIGURE 4-7).

1. Locate the controller module with the defective or expired battery.

2. Turn the thumbscrews on the left and right sides of the controller module that contains the defective or expired battery counterclockwise until the thumbscrews are disengaged from the chassis.

3. Use the thumbscrews to pull the controller module completely out of the chassis.

4. Disconnect the battery connector from the controller module.

5. With a Phillips screwdriver, remove the four battery screws on the underside of the controller module to release the battery from the module.

6. Lift out the battery.

7. Insert the new battery and attach the battery connector to the controller module.

8. With a Phillips screwdriver, attach the battery to the controller with the four screws that you removed in Step 5.

9. Reinsert the controller module into the array and turn the thumbscrews on the controller module clockwise until they are finger-tight.



Note - To ensure that a thumbscrew is finger-tight, tighten it with a screwdriver and then loosen the thumbscrew counterclockwise a quarter turn.



10. If you force-failed the controller, restore it.

a. From the RAID firmware Main Menu, choose "view and edit Peripheral devices right arrow Set Peripheral Device Entry right arrow Redundant Controller - Primary" to display the following message.

Deassert Reset on Failed Controller ?

b. Choose Yes to restore the controller that you previously force-failed.

c. Allow several minutes for the failed controller to come back online.

The following message notifies you when the controller is back online:

Controller Default Write Policy Restored

  FIGURE 4-3 The Battery and Connector in a SCSI Array

Figure showing the battery and connector.

  FIGURE 4-4 The Battery Connector Unplugged in a SCSI Array

Figure showing the connector unplugged.

  FIGURE 4-5 The Underside of the Battery Module With Screws Being Removed

Figure showing the underside of the controller module with screws being removed.

  FIGURE 4-6 The Top Side of the Controller Module With the Battery Being Lifted Out and the Connector Unplugged

Figure showing the top side of the controller module with the battery being lifted out and connector unplugged.

  FIGURE 4-7 The Top and Side View of the Controller Module With the Battery Being Inserted

Figure shows the connector attached to the battery module, how the battery is placed in the module, and the correct position of the mounting screws.

4.4.2 Replacing an FC Battery Module

FC array battery modules are hot-swappable.



Note - Be sure to follow Section 1.2, Static Electricity Precautions for all procedures.



To replace an FC array battery module, perform the following steps.

1. Locate the battery module with the defective or expired battery.

2. Turn the thumbscrews on the left and right sides of the battery module that contains the defective or expired battery counterclockwise until the thumbscrews are disengaged from the chassis.

3. Use the thumbscrews to pull the battery module completely out of the chassis.

  FIGURE 4-8 Battery Module Removed From the Chassis

Figure showing the battery module removed from the chassis.

4. Insert the new battery module into the array and turn the thumbscrews on the battery module clockwise until they are finger-tight.



Note - To ensure that a thumbscrew is finger-tight, tighten it with a screwdriver and then loosen the thumbscrew counterclockwise a quarter turn.



5. Set the in-service dates for the new FC battery replacement with the Sun StorEdge CLI or Sun StorEdge Configuration Service program procedures described under Section 4.5, FC Battery Status and In-Service Date Procedures.



Note - To successfully execute scripts using the Sun StorEdge CLI, the battery in-service date must be set. For details, see Section 4.5, FC Battery Status and In-Service Date Procedures.




4.5 FC Battery Status and In-Service Date Procedures

The Sun StorEdge CLI and Sun StorEdge Configuration Service programs offer the following features for FC battery modules:



Note - If you do not reset and verify the in-service date, Sun StorEdge Configuration Service and the Sun StorEdge CLI cannot accurately calculate the battery expiration date.



4.5.1 Viewing Status and Setting the In-Service Date With Sun StorEdge CLI

The show battery-status command displays the status of the battery modules, which preserve the contents of the write cache in each RAID controller. For redundant controllers, status for both batteries is shown. Status values include: Warning, Not present, Bad, N/A, Expired, and OK. A status of Warning indicates that the battery will expire within 21 days.

If you run the show battery-status command and the battery in-service date is not set, run the show battery-status -u command. Early model battery boards were not programmed with an in-service date. The show battery-status -u command sets the in-service date to the battery board manufacturing date and prompts the user to verify the date.



Note - If the battery type is an early board module (FRU ID 370-5545 REVB), then battery expiration monitoring is not supported. In this case, a message displays, "battery board type is not supported." If your configuration requires the battery expiration feature, consult your sales representative to obtain a new battery.



The following example shows one good battery and one expired battery.

sccli> show battery-status
 Upper Battery Type: 1
 Upper Battery Manufacturing Date: Fri Oct 17 15:59:08 2003
 Upper Battery Placed In Service:  Fri Oct 17 15:59:08 2003
 Upper Battery Expiration Date:    Sun Oct 16 15:59:08 2005
 Upper Battery Status: OK
 
 Lower Battery Type: 1
 Lower Battery Manufacturing Date: Fri Oct 17 19:29:20 2003
 Lower Battery Placed In Service:  Fri Oct 17 19:29:20 2003
 Lower Battery Expiration Date:    Sun Oct 6 19:29:20 2004
 Lower Battery Status: Expired

The following example uses the -u option, which prompts the user to verify the battery date if the battery in-service date has not been set previously.

sccli> show battery-status -u
 Upper Battery Type: 1
 Upper Battery Manufacturing Date: Mon Feb  2 08:00:00 2004
 Upper Battery Placed In Service:  Wed Aug 11 20:18:02 2004
 Upper Battery Expiration Date:    Fri Aug 11 20:18:02 2006
 Upper Battery Status: good
 
The date 2004/ 9/29 will be stored as the In-Service Date of Lower Battery. 
 Are you sure that this date is correct? y
 
 Lower Battery Type: 1
 Lower Battery Manufacturing Date: Tue Mar 30 14:32:26 2004
 Lower Battery Placed In Service:  Wed Sep 29 21:04:39 2004
 Lower Battery Expiration Date:    Fri Sep 29 21:04:39 2006
 Lower Battery Status: good



Note - To successfully execute scripts using the Sun StorEdge CLI, the battery in-service date must be set. Newer battery boards are programmed with the in-service date. If you are not sure that the in-service date is correct, consult your sales representative.



4.5.2 Viewing Status and Setting the In-Service Date With Sun StorEdge Configuration Service

Sun StorEdge Configuration Service monitors the usable life of the FC battery and displays its status in the Battery Information window. The program calculates the battery expiration date using the battery type, manufacture date, and in-service date, which have been programmed at the factory.



Note - For an FC battery FRU, you must verify the in-service date so that Sun StorEdge Configuration Service can set it as explained in Section 4.5.3, Verifying the In-Service Date When Replacing a Battery in Sun StorEdge Configuration Service.



The enclosure icon on the main window displays a degraded (yellow) status 21 days before the battery is going to expire. The enclosure icon also displays a warning (yellow) status if the in-service date has not been set for a battery FRU. A critical (red) status is displayed when a battery has expired.

To view the battery status, choose View right arrow View Enclosure or double-click the enclosure. The View Enclosure window is displayed, showing the battery status in the Summary box.

 Screen capture of the View Enclosure window showing a battery status of good.

To view battery information, including type, status, manufacture date, in-service date, and expiration date, click Battery. The Battery Information window is displayed.

 Screen capture of Battery Information showing battery status.


Note - If a battery FRU is replaced and Sun StorEdge Configuration Service does not show the updated battery information, perform a rescan. For details, see Section 4.5.4, Refreshing the Battery Status With Sun StorEdge Configuration Service.



4.5.3 Verifying the In-Service Date When Replacing a Battery in Sun StorEdge Configuration Service

When Sun StorEdge Configuration Service detects a battery FRU, the enclosure icon displays a degraded (yellow) status symbol as shown in the following example.



Note - If you do not reset and verify the in-service date, Sun StorEdge Configuration Service cannot accurately calculate the battery expiration date.



 Screen capture of Sun StorEdge Configuration Service main window showing a degraded device symbol.

To verify the in-service date, perform the following steps.

1. Double-click the enclosure icon.

Sun StorEdge Configuration Service calculates the battery expiration date using the in-service date (date that the battery is put into service), which is based on the host clock. The program prompts you to verify the date by displaying the following message:

 Screen capture showing the warning message if Sun StorEdge Configuration Service detects a new battery.

2. If the host clock is correct, click Yes.

The following confirmation message is displayed. Click OK.

 Screen capture verifying the in-service date.

Sun StorEdge Configuration Service sets the in-service date and displays the date in the In-Service Date field in the Battery Information window.

3. If the host clock is incorrect, click No and reset the clock so that Sun StorEdge Configuration Service can prompt you to verify it again and set the in-service date.

4.5.4 Refreshing the Battery Status With Sun StorEdge Configuration Service

Sun StorEdge Configuration Service does not automatically detect the status of a battery when it is replaced. To force Sun StorEdge Configuration Service to show the new battery status, you must perform a manual rescan.

To manually scan the battery FRU and view the updated status, perform the following steps.

1. Double-click the server icon or select the server icon and choose View right arrow View Server.

2. Click Rescan.

3. Click OK.

The server scans the existing server inventory and refreshes the console.

4. To view the new battery information, double-click the enclosure or select the enclosure and choose View right arrow View Enclosure.

5. Click Battery.

The Battery Information window displays the updated battery status.