Hitachi HiCommand Tuning Manager
 
Sun Storage 9990 System
 
Sun Storage 9960 System
 

GCS>Sun Microsystems>Storage - Disk>Datacenter Disk
 

This document details two examples(with solutions), of how to troubleshoot the
following generic symptoms:

• The Sun StorEdge[TM] 9900, HiCommand Software, HiCommand Tuning Manager(HTnM) GUI,
  showed a RAID storage agent not collecting any data.
• Performance resource output shows data as n/a(not available)
• the HTnM logfile shows a KAVF18501-E message error:

      /opt/jp1pc/log/Jpclog 

      KAVF18501-E, a command device can not be connected

These errors can happen during RAID agent configuration, or when there is an
error accessing a Sun StorEdge 99x0 command device.

This behaviour may be seen on an HTnM RAID agent, installed on a host running
Solaris[TM] Operating System(OS).

Error Message

The following log error(/opt/jp1pc/log/Jpclog), generally happens during RAID
agent agtd startup:

2005/10/06 15:02:00 jpcagtd 00006746 00000001 RecordBuilder.c 0941 KAVF18501-E
A command device cannot be connected. (device=/dev/rdsk/c5t50060E800327B700d0s2)

Troubleshooting Examples

Following, are two examples of how to find the possible underlying
cause of the above symptom:

1. Check that the RAID host agent has access to a command device

  # /opt/jp1pc/tools/jpctdchkinst -inst 9980v

  KAVF18800-I The verification of the agent instance settings will now start.
(instance name=9980v)
[Instance parameters]
Storage Model : Lightning
***Command Device File Name : /dev/rdsk/c7t50060E800327B700d7s2  <------COMMAND DEVICE
[Check result]
KAVF18851-E Attempt to access the device set by the agent instance parameter <---ERROR
is failed. (parameter name=Command Device File Name, parameter           <---ERROR
value=/dev/rdsk/c7t50060E800327B700d7s2)
KAVF18801-I The verification of the agent instance settings will now end.

Solution:

 Check if the command device listed above is accessible by using:

• The Solaris OS "format" command shows the device name with -CM-
• The HTnM command /opt/jp1pc/tools/jpctdlistraid.

If the incorrect command device is configured, use the HTnM command
/opt/jp1pc/tools/jpcinstsetup to reconfigure.

2. Check if the RAID manager library is installed.

     Note: The library is available from HTnM installation CDs. 

  # /opt/jp1pc/tools/jpctdchkinst -inst 9980v

  KAVF18800-I The verification of the agent instance settings will now start.
(instance name=9980v)
[Instance parameters]
Storage Model : Lightning
Command Device File Name : /dev/rdsk/c5t50060E800327B700d0s2
[Check result]
KAVF18865-E An error occurred during access to the storage subsystem.
(name=attachcmddev, rc=2)
KAVF18801-I The verification of the agent instance settings will now end.

  Below is an extract from the output of a Solaris OS "truss" command, while
opening/creating /usr/lib/RMLIB/RLSYSLK

    Note: The "ENOENT" error 

    7252:   ioctl(4, TCGETA, 0xFFBF3984)                    Err#25 ENOTTY
7252:   read(4, " H I T A C H I ; D F 3 5".., 8192)     = 1025
7252:   llseek(4, 0xFFFFFFFFFFFFFEA8, SEEK_CUR)         = 681
7252:   close(4)                                        = 0
7252:   open("/usr/lib/RMLIB/RLSYSLK", O_RDWR|O_CREAT, 0666) Err#2 ENOENT

Solution:

  Ensure that the RAID Manager library is installed.
Reinstall if necessary and make sure the directory /usr/lib/RMLIB exists.
If the directory is still not present, then create it manually.
This directory is required to create RLSYSLK as locking mechanism.

  # ls -al /usr/lib/RMLIB/RLSYSLK
-rw-rw-rw-   1 root     other          0 Oct  5 16:42 RLSYSLK

References:

- HiCommand Tuning Manager Installation Guide
- Hitachi HiCommand Tuning Manager User's Guide
- HiCommand Tuning Manager Agent for Raid Reference Guide

Service Request ID: 10730491

Escalation ID: 1-10941173

Solution ID: 1-12354859

Owner GEO: APAC

Customer GEO: APAC

- The reference documents listed above can be downloaded from Sun Internal site

available at http://tsc-storage.us.oracle.com/products/T99x0/documentation.html

- HDS knowledge document HDS18595 shows RMLIB 01-06-03/03 or later uses

"/usr/lib/RMLIB" directory.

This solution has no attachment