Solaris

PROBLEM OVERVIEW
Defective Battery
WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?
Write cache should be disabled prior to replacing battery to prevent data loss if power event occurs before replacement battery is charged

WHAT ACTION DOES THE CUSTOMER NEED TO TAKE
Check for amber LED on battery, check CLI battery status and location (upper or lower slot). From SC CLI: sccli> show battery
Prepare array for battery replacement
1. To determine status of write cache on array, access array Main Menu from telnet.

2. Select appropriate mode and press

3. Clear any pop-up messages with + < C> Select Disable pop-ups On upper right of Main Menu, Cache Status is displayed. Value to right indicates percentage of controller cache that differs from what is saved to disk. “Clean” means all cache has been saved to disk.

4. From telnet Main Menu, Disable cache: a. Select View and edit Configuration parameters b. Select Caching Parameters . Note cache state (enabled or disabled). c. Select Write-Back Cache Enable ? > No d. Disable Write-back cache? >YesFrom sccli, Disable Cache: e. sccli -o (out-of-band) or sccli /dev/dsk/c#t#d#s2(in-band) f. Check cache parameters. From sccli> show cache-parameters g. Disable cache. sccli> set cache-parameters write-through

5. Verify write-through cache status. sccli> show cache-parameters
Note: Verify "cache" status led on Raid controller is off

6. Remove ethernet and serial cable from battery module

7. Unscrew and disengage thumbscrews and cables on battery module and use thumbscrews to pull out the battery module

8. Insert new battery module and tighten thumbscrews until finger tightWARNING: Do not force or apply excessive pressure when inserting battery module

9. Re-attach cables

10. Using CLI (sccli), check battery status and set in service datesccli> show battery-statussccli> show battery-status -usccli> show battery-status
If second battery needs to be replaced, repeat steps 6-10

11. Confirm controller redundancy. sccli >show redundancy

12. Restore write cache to original settings. To Enable Write-Back Cache a. Select View and edit Configuration parameters b. Select Caching Parameters c. Select Write-Back Cache Disabled d. Enable Write-Back Cache?--> YESsccli> set cache-parameters write-back
Note:Write cache will enable once battery can protect on-board cache. Verify battery is charging by blinking green light on battery. Battery status LED may remain amber for up to 30 minutes.

13. Verify host access

14. Restart Configuration Services agent to prevent expired battery related messages from recurring. From host, type/etc/init.d/ssagent stop/etc/init.d/ssagent start

Steps for Installing EMC Solutions Enabler version 6.2.1

server:/tmp/symcli/6.2.1# ./emc_install.csh

#----------------------------------------------------------------------------
# EMC Installation Manager
#----------------------------------------------------------------------------
Copyright 2003, EMC Corporation
All rights reserved.

The terms of your use of this software are governed by the
applicable contract.

1. Kit Location [/tmp/symcli/6.2.1/osl_cd] :
Provide the location of the software

2. Install root directory [/opt/emc] :
Enter the path where the symcli needs to be installed

#-----------------------------------------------------------------------------
# The following is AVAILABLE TO BE INSTALLED from the selected Kit Location:
#-----------------------------------------------------------------------------
# ITEM PRODUCT VERSION
#-----------------------------------------------------------------------------
01 EMC Solutions Enabler V6.2.1

What would you like to do? Install (i) Uninstall (u) Register (r) Exit (x):
Enter i to proceed installation

3. At the following prompt, specify whether to install all of the
Solutions Enabler libraries:
Install All Solutions Enabler Shared Libraries and Run
Time Environment? [Y]:
• A [Y]es response installs all the libraries.
• A [N]o response produces the following series of prompts,
which allow you to select the libraries to install. If you only
want to install Solutions Enabler’s core functionality, specify
[N]o for each of the prompts. Solutions Enabler’s core
functionality includes symapi[mt], symlvm[mt],
storapi[mt], storsrvd[mt], symapisrv[mt],
storapid[mt], storcore[mt], stordaemon[mt], and
storpds[mt].
– BaseStor Library Component ? [Y]:
A [Y]es response installs StorSil and Storbase. This
option provides base storage and host specific
functionality, and an interface to storage arrays for features
like I/O scan, device listings, statistics, and showings.
– CtrlStor Library Component ? [Y]:
A [Y]es response installs StorSil, Storbase, and
Storctrl. This option provides the same functionality as
the BaseStor option (explained earlier), but includes
storage control functionality for features like Snap, device
masking, and device mirroring.
– BaseMapping Library Component ? [Y]:
A [Y]es response installs stormap, which provides Storage
Resource Management (SRM) functionality.

4. Solutions Enabler is available in both 32 and 64 bit support on
some operating systems. The following prompt only displays if
Solutions Enabler can support both 32 and 64 bit versions of the
libraries and executables on the host:
Install Solutions Enabler 64-bit Shared libraries ?
[N]:
A [Y]es response installs the 32 and 64 bit libraries. A [N]o
response only installs the 32 bit libraries.
9
Installation
5. At the following prompt, specify whether to install the collection
of binaries known as SYMCLI. A [Y]es response installs the
SYMCLI binaries:
Install Symmetrix Command Line Interface (SYMCLI) ?
[Y]:

6. If you are installing Solutions Enabler on a host with a Linux,
HP-UX, SunOS, or AIX operating system, the following prompt
displays, asking whether to install one or more optional database
components:
Install Solutions Enabler SRM Database Run Time
Components ? [N]:
A [Y]es response displays the following prompts, depending on
your operating system:
• SRM Oracle Database Component ? [N]:
This prompt only displays on operating systems where
Solutions Enabler supports Oracle. A [Y]es response installs
the optional Oracle daemon.
• SRM Informix Database Component ? [N]:
This prompt only displays on operating systems where
Solutions Enabler supports Informix. A [Y]es response
installs the optional Informix daemon.
• SRM Sybase Database Component ? [N]:
This prompt only displays on operating systems where
Solutions Enabler supports Sybase. A [Y]es response installs
the optional Sybase daemon.
• IBM UDB Database Component ? [N]:
This prompt only displays on operating systems where
Solutions Enabler supports UDB. A [Y]es response installs
the optional UDB daemon.

7. At the following prompt, specify whether to install the Solutions
Enabler Java interface component. You should install this
component if your Solutions Enabler application uses a Java
interface. A [Y]es response installs the JNI component:
Install Option to Enable JNI Interface for EMC
Solutions Enabler APIs ? [N]:
40
Installation
8. At the following prompt, specify whether to install the Solutions
Enabler Star component. A [Y]es response installs the Star
component:
Install option to Enable EMC Solutions Enabler Star
component ? [N]:


9. If you are upgrading, the following prompt displays, asking
whether to move the previous installation’s data files to the
symapi_old directory. A [Y]es response moves the files:
Do you want to move this data to
/usr/emc/API/symapi_old ? [N]:

In server server the below issue is faced

server:/opt/emc/SYMCLI/V6.2.1/bin# ./syminq
A requested network service was not found in the service file
server:/opt/emc/SYMCLI/V6.2.1/bin#

Found the environmental variables are not set properly
>>>
server:/tmp/symcli/6.2.1# symcli -def
Symmetrix Command Line Interface (SYMCLI) Version V6.2.1.0 (Edit Level: 733)
built with SYMAPI Version V6.2.1.0 (Edit Level: 733)

Current settings of the SYMCLI environmental variables:

SYMCLI_CONNECT : SYMAPI_SERVER
>>>

To correct this I done the unset command
Unset SYMCLI_CONNECT and removed the SYMCLI_CONNECT from root user .profile file as below

# SYMCLI_CONNECT=SYMAPI_SERVER
# export SYMCLI_CONNECT