Goal

Solution

Troubleshooting True Copy, Shadow Image, Universal Replicator

1. Verify which applications and components are involved in the issue.
   There would be at least one of the products below:
   • Shadow Image
   • True Copy
   • True Copy Async
   • Command Control Interface (CCI, Raid Manager)
   • Universal Replicator (HUR); only SE9985 and SE9990
   • Open LDEV Guard
2. Verify whether the problem is related to a New Installation and Configuration Changed or it was Working Before.
3. Verify that the subsystem configuration meets the prerequisites and requirements including proper licences.
4. Verify the operation of the products by performing them through Remote Console (SE9910, SE9960) or Storage Navigator (SE9970, SE9980, SE9985, SE9990, SE9985V, SE9990V).
5. In case the operation was working proceed with Troubleshooting Command Control Interface .
   Otherwise please record the operation request and the related message. It is very likely that the message refers to either an illegal operation request or a configuration issue. Consulting the product guides or someone experienced would be required.

Troubleshooting Command Control Interface

1. In case of a New Installation and Configuration Changed consult the Command Control Interface (CCI) User and Reference Guide for prerequisites and requirements.
   • Microcode level of the subsystem.
   • Subsystem proper licences installed.
   • Subsystem has at least one CMD device enabled and mapped.
   • Revision of RAID Manager or Command Control Interface (CCI).
   • Edit according HORCM.conf and services files.
   • Startup of CCI (horcmstart) has been performed.
2. In case it was Working Before or after you have verified all items above do a Command Control Interface (CCI) data collection as next.

Command Control Interface (CCI) data collection

1. For every server involved, we need the actual CCI configuration definition files and environmental variables used to when starting the HORCM manager. Refer to Section 2.8 and 3.6 and Table 4.1 of Command Control Interface (CCI) User and Reference Guide.
   • Running one instance of HORCM manager on a server: horcm(x).conf.
     Where (x) could be not set or any number. By default horcm.conf.
   • Running two or more instances of HORCM manager on a server: horcm(x).conf and horcm(y).conf. For example horcm0.conf and horcm1.conf.
     Where (x) or (y) could be any number.
   • HORCMINST environmental variable;
     Only useful if two or more instances of HORCM manager running on a server.
   • HORCM_MRCF environmental variable;
     Only set to one if Shadow Image is used. For example HORCM_MRCF=1.
2. For every server involved, we need the log files.
   • For a UNIX system the following logs are needed:
     $HORCM_LOG/horcm_HOST.log
     $HORCC_LOG/horcc_HOST.log
     $HORCM_LOG/horcmlog_HOST/horcm.log
     $HORCM_LOG/horcmlog_HOST/horcm_PID.trc
     $HORCM_LOG/horcmlog_HOST/horcc_PID.trc
     $HORCM_LOG/core_HOST_PID/core
   • For a Windows based system:
     $HORCM_LOG\horcm_HOST_log.txt
     $HORCC_LOG\horcc_HOST_log.txt
     $HORCM_LOG\horcmlog_HOST\horcm_log.txt
     $HORCM_LOG\horcmlog_HOST\horcm_PID_trc.txt
     $HORCM_LOG\horcmlog_HOST\horcc_PID_trc.txt
     $HORCM_LOG\core_HOST_PID\core
   • Either syslog files for UNIX systems or event log files for Windows based systems.
3. Description of the sequence of commands producing the error including date and time of the error incidents.
4. Capture the terminal command(s) and messages from sequence of commands producing the error incident.
5. Provide configuration diagram or information regarding SAN/WAN.
   • Fabric topology.
   • FC Switch model, firmware level, port configuration, logs.
   • SAN router or channel extender model, firmware level, port configuration, logs.
6. Capture the terminal command(s) and messages from commands below. For proper arguments consult the Command Control Interface (CCI) User and Reference Guide or type -h to display help and usage information after each command.
   • raidscan
   • raidscan -x findcmddev; Windows based systems only
   • raidscan -x drivescan; Windows based systems only
   • raidscan -x portscan; Windows based systems only
   • raidar
   • raidqry
   • inqraid
   • pairdisplay; pairdisplay commands should be part of the sequence of commands at key times especially before and after the error.
   • pairvolchk
   • paircurchk; TrueCopy only
   • raidvchkdsp: Open LDEV Guard only
   • raidchkvscan: Open LDEV Guard only

This solution has no attachment