HP StorageWorks Command View XP Advanced Edition Device Manager Agent Installation and Configuration Guide Part number: T1780-96010 Second edition: October, 2005
Legal and notice information © Copyright 2005 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents Revision history Revision tables ....................................................................................................................................................... 9 1 Overview of the Device Manager Agent 1-1 Device Manager Agent Overview..............................................................................................................
Troubleshooting Solaris™, AIX®, HP-UX, and Linux® Systems ................................................................ 68 4-2-1 Errors in a Cluster Environment (in AIX®)....................................................................................... 71 4-3 Troubleshooting Windows® 2000 and Windows Server™ 2003 Systems................................................. 71 4-3-1 If the Device Manager Agent has not Started the Process Automatically ......................................
Figures Figure 2-1 Agent Introduction Panel ......................................................................................................................... 16 Figure 2-2 License Agreement.................................................................................................................................. 16 Figure 2-3 Choose Destination Location...................................................................................................................
Tables Table 1 Document Conventions.................................................................................................................................. 7 Table 2 Revisions ........................................................................................................................................................ 9 Table 2-1 Supported Operating Systems and Required Programs for the Device Manager ....................................
About this guide This guide provides information about: • Installing HP StorageWorks Command View XP Advanced Edition Device Manager Agent software. • Installing Java™2 Java™ Runtime Environment (JRE). Intended audience This guide is intended for customers and HP authorized service providers who are experienced with the following: • Data processing and direct-access storage device subsystems. • HP StorageWorks XP Series disk array(s).
HP technical support Telephone numbers for worldwide technical support are listed on the HP web site: http://www.hp.com/support/ Collect the following information before calling: • Technical support registration number (if applicable) • Product serial numbers • Product model names and numbers • Applicable error messages • Operating system type and revision level • Detailed, specific questions For continuous quality improvement, calls may be recorded or monitored.
Revision history Revision tables Table 2 Revisions Date Edition Revision July, 2005 First Initial release October, 2005 Second • • • • Red Hat Enterprise Linux AS 4.0 and Red Hat Enterprise Linux ES 4.0 are now supported. Addition to the Windows Firewall exceptions list can now be performed during installation. Java Runtime Environment (JRE) for Windows, Solaris, and HP-UX is now supplied on CD-ROM. The Windows default installation folder has been changed.
1 Overview of the Device Manager Agent This chapter covers the following topic: • Overview of the Device Manager Agent (see section 1-1 ) 1-1 Device Manager Agent Overview The Device Manager agent collects information about storage devices (logical units on a disk array) that are connected to the host server as well as information about the host server itself. It then transmits this information to the Device Manager server using TCP/IP.
2 Installation Requirements and Procedures This chapter covers the following topics: • Supported operating systems and required programs for the Device Manager Agent (see section 2-1 ) • Supported disk arrays (see section 2-2 ) • Requirements for WWN acquisition without host recognition of logical units (see section Figure 2-3) • Requirements for using FC-HUB (FC-SWITCH) (see section 2-4 ) • Installing the Device Manager Agent (see section 2-5 ) • Setting Up the Device Manager Agent (see section
NOTE 1: The Enterprise and Datacenter Edition of Windows Server™ 2003 support the 64-bit processor version (running on WOW64). NOTE 2: If Windows Firewall is active, you must add the Device Manager agent as an exception to the Windows Firewall exceptions list. For details on how to do this after installing the agent, see section 3-2-6 . NOTE 3: Applicable only to EM64T (Intel ® Extended Memory 64 Technology). NOTE 4: The Device Manager agent runs in the usual global environment (global zone) only.
2-3 Acquiring WWN Information without Host Recognizing Logical Units To acquire WWN information for an HBA, in the situation when the host running the Device Manager agent recognizes no logical unit of the storage subsystem, you must have the HBA models and the HBA API library provided by the HBA vendors shown in Table 2-2.
2-5 Installing the Device Manager Agent This section describes how to install the Device Manager agent for each supported program (Windows®, Solaris™, AIX®, HP-UX, and Linux®). If the Device Manager agent has already been installed, you can obtain the version of the installed the Device Manager agent by executing the following command: • ® In Windows : • • • • \bin\hdvm_info.
• If you log in to Windows® from a remote console and install a Device Manager agent after logging in, you must use Terminal Service Client. New Installation in a Windows® System To install a Device Manager agent, the JRE version 1.4.2 (Build 06 or later) must be installed in advance. To perform a new installation of a Device Manager agent, use the installation support tool to first install the JRE required for the Device Manager agent and then the Device Manager agent.
CAUTION: If VxVM has been installed, specify the version of the installed VxVM in the programproductInfo.properties file. For details about the setting, see section 3-11-3 .
Figure 2-3 Choose Destination Location Figure 2-4 Adding to the Windows Firewall Exceptions List - Confirmation Installation Requirements and Procedures 17
Figure 2-5 Start Copying Files Figure 2-6 Setup Status Installation Requirements and Procedures 18
Figure 2-7 Installing Add-on Modules Figure 2-8 New Installation Complete Installation Requirements and Procedures 19
Re-installation in Windows ® NOTE: When performing a re-installation of the Device Manager agent, do not execute the following commands during installation: HiScan, hdvmagt_account, hdvmagt_schedule, hdvmagt, stop_hdvmagt, and TIC. Should you execute any of these commands, the re-installation might not complete properly. In such a case, retry execution of the re-installation. To perform re-installation: 1. Log on to Windows® using a user ID in the Administrators group. 2.
Figure 2-9 Welcome Dialog Box Figure 2-10 Re-installation Confirmation Figure 2-11 Upgrade Installation for Restoration Complete 2-5-2 Installing the Device Manager Agent on a Solaris™ System Before installing the Device Manager agent on a Solaris™ system: The installation procedure differs depending on whether the Device Manager agent is to be newly installed, or an overwrite installation of Device Manager agent version 1.0 or later is to be performed.
• You must be a super user. • At least 64 MB of free space is required on the hard disk. An additional 96 MB of free space is required on the system drive to create temporary files during installation. • Stop all Agents currently running. When installing the Device Manager agent, the JRE (version 1.4.2 (Build 06 or later)) must be installed in advance.
• Installation of Device Manager-Agent has been completed successfully. For details about how to set it up, see section 2-6 . For upgrade (overwrite) installations, predefined settings for Device Manager server information and the execution period of the HiScan command will be inherited. To modify information about the Device Manager server, see section 3-4 . To change the execution period, see section 3-5 .
The following shows an example of the window displayed during installation of Device Manager in a Solaris™ environment: –# ./agent_jre_setup.sh – Sun Microsystems, Inc. – Binary Code License Agreement – for the –JAVATM 2 RUNTIME ENVIRONMENT (J2RE), STANDARD EDITION, – VERSION 1.4.2_X –... – –Setup of JRE for Device Manager - Agent has completed successfully. – –Installing Device Manager - Agent... – –...
If you want to newly install the Device Manager agent, use the installation support tool to first install the JRE required for the Device Manager agent, and then install the Device Manager agent. To install the JRE and the Device Manager agent: 1. Store the JRE installer in any directory. The JRE is stored on a CD-ROM of the OS. If the correct version of JRE is not bundled, download the correct version from the AIX Web site. Use the 32-bit JRE. 2. Insert the Device Manager Agent CD-ROM and mount it. 3.
3. 4. At this point, software licensing agreement information displays. If you do not accept the licensing agreement, uninstall the Device Manager agent after installation finishes. The following message displays when installation finishes: • Installation of Device Manager-Agent has been completed successfully. For details about how to set it up, see section 2-6 .
Figure 2-13 illustrates an example of the screen displayed during installation of the Device Manager agent in AIX®. –# ./agent_jre_setup.sh –x COPYRIGHT, 1431 bytes, 3 tape blocks –x license – –... – –====================================================================================== –CONTAINS IBM(R) 64-bit Runtime Environment for AIX(TM), Java(TM) 2 Technology Edition, –Version 1.
• Refer to Table 2-1 for supported operating systems and a listing of required programs for your operating system. • Make sure beforehand that there is enough space in the default directory for installing the Device Manager agent. • You must be a super user. • Stop all Agents currently running. When installing the Device Manager agent, the RTE (version 1.4.2 (Build 06 or later)) must be installed in advance.
3. At this point, software licensing agreement information displays. If you do not accept the licensing agreement, uninstall the Device Manager agent after installation finishes. 4. The following message displays when installation finishes: • Installation of Device Manager-Agent has been completed successfully. For details about how to set it up, see section 2-6 .
Figure 2-14 illustrates an example of the screen displayed during installation of the Device Manager agent in an HP-UX environment: –# ./agent_jre_setup.sh – –======= 08/25/05 15:39:22 MDT BEGIN swinstall SESSION – (non-interactive) (jobid=koiwa-0016) – –... – –======= 08/25/05 15:39:45 MDT END swinstall SESSION (non-interactive) – (jobid=koiwa-0016) – – –Setup of JRE for Device Manager - Agent has completed successfully. – –Installing Device Manager - Agent...
When installing the Device Manager agent, the JRE (version 1.4.2 (Build 06 or later)) must be installed in advance. Use the following procedure to install the JRE. For the 32-bit processor version, install the 32-bit JRE. For the 64-bit processor version, install the 64-bit Java 2 SDK: If you want to newly install the Device Manager agent, use the installation support tool to first install the JRE required for the Device Manager agent, and then install the Device Manager agent.
NOTE: If the JRE (version 1.4.2 (Build 06 or later)) has not been installed in the /opt/HDVM/agent/JRE1.4 directory, the error message KAIC25165-E displays, and the installation is canceled. 3. At this point, software licensing agreement information displays. If you do not accept the licensing agreement, uninstall the Device Manager agent after installation finishes. 4. The following message displays when installation finishes: • Installation of Device Manager-Agent has been completed successfully.
– –Now executing hdvmagt_account command... –IPAddress : 255.255.255.255 –port : 2001 –userID : – –Would you like to change the Device Manager Server information? (Y)es or (N)o.(default:N) –... Figure 2-15 Installing the Device Manager Agent in a Linux® Environment 2-6 Setting Up the Device Manager Agent After installation of the Device Manager agent finishes, set the following information for Device Manager agent operation: • Information for the Device Manager server.
You can use the following characters for a user ID: • a-z A-Z 0-9 # + . - _ @ If you enter an invalid character or do not enter anything, you will be prompted to re-enter the user ID. 5. The following message displays, prompting you to enter the password for logging on to the Device Manager server. Enter the password: • Enter the Device Manager Server password. You can use the following characters for a password: • a-z A-Z 0-9 ! # $ % & ( ) * + - .
CAUTION: When the Device Manager agent is installed on multiple hosts, set the HiScan command to execute at different start times for each host so that the command will not be executed simultaneously from multiple hosts. When changing a start time, make sure that you set a time that does not overlap the HiScan command execution period (command start time to end time) set for any other hosts. You can check the HiScan command execution period by referencing the following messages output to the HiScan.
To uninstall the Device Manager agent in Windows®: 1. Select Start, Settings, Control Panel, and Add/Remove Programs. 2. Click the Change/Remove button for the Device Manager agent. 3. In the displayed the Device Manager agent maintenance menu, choose Remove. NOTE: In the maintenance menu, although Repair and Remove are selectable, do not select Repair.
2. Type Y. When the following message displays, uninstallation finishes: • Uninstallation of Device Manager-Agent was successful. ® 2-7-5 Uninstalling the Device Manager Agent on Linux Systems hdvmagt stops when you uninstall the Device Manager agent. The execution cycle schedule, and all the directories and files registered during installation are deleted, and the system is returned to its preinstallation state. NOTE: This operation does not uninstall JRE1.4.2_06 because it was installed separately. 1.
3 Device Manager Agent Operations This chapter describes how to specify commands used for Device Manager agent operations, and gives details on Device Manager agent properties.
For details on how to set up the execution period, see section 2-6-2 . For details on changing the specified execution period, see section 3-5 . • Under manual execution, the user runs programs as necessary. With the Device Manager agent, the user runs the HiScan command, and starts and stops the resident program (hdvmagt).
3-2-5 When Adding or Changing an HBA on the Host When you add or change an HBA on a host that runs the Device Manager agent, or when an HBA driver is installed after installing the Device Manager agent, perform the following: • Execute the installation-folder-for-Device-Manager-agent\bin\ hdvm_refresh.exe file.
3-2-7 When Changing the hdvmagt Service Execution User For Windows, the LocalSystem privilege is set up for the user that executes the hdvmagt service of the Device Manager agent. Follow the steps below to change the hdvmagt Service execution user to a user with Administrator privilege. To change the hdvmagt Service execution user: 1. Open the Services window by choosing Management Tools and then Services. 2. Choose the hdvmagt service and stop it. 3. Select Operations, and then Properties.
• # mv /opt/HDVM/agent/JRE1.4 /opt/HDVM/agent/JRE1.4_org In AIX® systems: • 4. # mv /usr/HDVM/agent/JRE1.4 /usr/HDVM/agent/JRE1.4_org Install JRE in the following directory. In Solaris™, HP-UX®, and Linux® systems: • # /opt/HDVM/agent In AIX® systems: • # /usr/HDVM/agent A subdirectory is created and JRE is installed in it. 5. 6. Change the name of the subdirectory created in Step 4 to JRE1.4. Restart the hdvmagt daemon process. Run the following command.
3-3-1 Starting, Stopping, and Checking the hdvmagt Service or the hdvmagt Daemon Process The following describes how to start and stop the service or the daemon process for the Device Manager agent, and how to confirm the operating status of each. Note that you must be a super user or a member of the Administrators group to perform the operations described below.
3-3-3 Difficulties Stopping the hdvmagt or Add-On Modules Before uninstalling and updating an Agent and any add-on modules, you must stop the Device Manager agent and add-on modules currently running.
For example: • 4. at 1 /delete (the ID is 1). Confirm that the schedule specified with the ID was deleted. Figure 3-1 shows an example of schedule confirmation and a delete operation. 5. Using Notepad, open the atdaily.bat file located in the following folder: • 6. installation-folder-for-Device-Manager-agent\bin\atdaily.bat Specify the day by rewriting the argument Days of the set command coded in the atdaily.bat file.
Figure 3-2 Using the atdaily.bat File to Modify a Schedule 3-5-1-1 Modification Using Task Scheduler You can use the task scheduler to change the execution period of the HiScan command. 3-5-2 Changing the Execution Period in Solaris™, AIX®, HP-UX, or Linux® Systems The following procedures show how to confirm and change the run cycle of the HiScan command by ® ® entering the crontab command from the command line in Solaris™, AIX , HP-UX, or Linux .
2. Rewrite the numbers indicating the run time (hours and minutes) coded in the file, and then save and close the file. An example of modifying a schedule is shown below. Specifying the * symbol in place of the number indicating hours (2 in the example) means "every hour": # crontab –e 47 2 * * * cd/opt/HDVM/bin/ ; (./HiScan -s 172.16.27.201 :2001 -t /opt/HDVM/bin logs/HiScan.msg >> /opt/HDVM/bin/logs/HiScan.log) 2> /opt/HDVM/bin/logs/HiScan.
Table 3-1 HiScan Command Syntax Syntax Component Description Description The HiScan command reports information about attached StorageWorks XP disk arrays. HiScan scans system information and constructs associations between file systems, volumes, partitions and disk drives. From these results it creates a HTTP/XML message.
Table 3-2 hldutil Command Syntax Syntax Component Description Synopsis For the device information display function: hldutil [-d [device-file]|[-g [disk-group]|-l ldev#.ser#][-p] [-q] [-nolog] [-s sort-key...] [-k|-hf [log-file]|-h [log-number]] For the execution-result log file management function: hldutil -h [log-number] -hb [log-file]| -hrm [log-number|all]| -history number Description Hldutil provides device information display and execution results log file management functions.
Table 3-2 hldutil Command Syntax Syntax Component Description Options -k: Specify this option when outputting the latest execution-result log file to the standard output. This processing involves no hardware access. Since the command skips processing for obtaining logical device information, its execution does not affect device input or output.
Table 3-3 lists and describes the sort keys. Table 3-3 Sort Key Descriptions Sort Key Descriptions dg Disk group name. fs File system name. ldev Logical device number. lun Logical unit number. port Port number. prod Product name. rg RAID Group number. rid Character string representing a disk array device model. ser Disk array device serial number. tid Target ID. vend Vendor name. wwnn Node WWN name. wwnp Port WWN name.
Table 3-5 describes the correspondence between the character string for RaidID and the models. Table 3-5 Correspondence between RaidID and Models RaidID Model R401 StorageWorks XP48 Disk Array. R400 StorageWorks XP512 Disk Array. R451 StorageWorks XP128 Disk Array. R450 StorageWorks XP1024 Disk Array. R500 StorageWorks XP 12000 Disk Array. R501 StorageWorks XP10000 Disk Array.
Table 3-6 hdvmagt_schedule Command Syntax Syntax Component Description Synopsis hdvmagt_schedule Description The hdvmagt_schedule command provides an interactive interface to setup the autoexecution period of the HiScan command. The hdvmagt_schedule command asks about the execution period of HiScan daily or hourly, and configures the /etc/crontab table (or task scheduler). You must possess super user/Administrator authority to execute the hdvmagt_schedule command.
Table 3-7 hdvmagt_account Command Syntax Syntax Component Description Synopsis hdvmagt_account Description The hdvmagt_account command allows you to change the information about the Device Manager server that communicates with the Device Manager agent. This command provides an interactive interface to set server.server.serverIPAddress, server.server.serverPort, and server.server.authorization in the server.properties file.
• • In a Solaris™, HP-UX, or Linux® system: • /opt/HDVM/agent/config/server.properties • /opt/HDVM/agent/config/logger.properties In an AIX® system: • /usr/HDVM/agent/config/server.properties • /usr/HDVM/agent/config/logger.properties 3-11-1 server.properties File The server.properties file contains network configuration properties. Table 3-8 lists and describes the HTTP communication function properties for the Device Manager agent.
Table 3-8 server.properties File Property Description server.server.serverIPAddress Specify the IPAddress of Device Manager server in dotted-decimal IPAddress form. You may specify this property using the text editor, or by executing the hdvmagt_account command (see section 3-10 ). Default: None (usually specified at installation). server.server.serverPort Specify the port number of the Device Manager server to which the Device Manager agent is going to connect.
Table 3-8 server.properties File Property Description server.agent.cashTimeOut (see Note) Specify a timeout value (in milliseconds) from the time a thread that executes a remotely requested function is started to the time the Device Manager agent determines that an error has occurred in the thread, in milliseconds. A value less than or equal to zero causes this property to have no effect.
Table 3-8 server.properties File Property Description server.http.socket.agentAddress (see Note) Specify the IP address at which the Device Manager agent transmits notifications to a Device Manager server. To limit the IP address at which a Device Manager agent transmits notifications to the Device Manager server, specify the desired IP address as a dotted decimal number. The default is the IP address acquired by the Device Manager agent.
Table 3-8 server.properties File Property Description server.http.request.timeout (see Note) Specify the read-blocking timeout value (in milliseconds) for the HTTP socket connection. This property allows you to switch enabling and disabling of the client-connection socket’s SO_TIMEOUT setting. When data is to be read from a socket-related input stream, the request from the remote site is waited for the length of time specified in this property before the socket times out. The default is 5000 (5 seconds).
Table 3-8 server.properties File Property Description server.http.socket.backlog (see Note) This property allows you to specify the maximum number (maximum queue size) of remote sites waiting for connection with respect to connection requests to the Device Manager agent. In other words, this property allows you to set the SO_MAX_CONN attribute for the server socket. When a connection request arrives from a remote site when the queue is full, the Device Manager agent declines the new request.
Table 3-8 server.properties File Property Description server.http.headers.maxNumber (see Note) This property allows you to specify the maximum number of HTTP headers that are permitted by the Web server function of the Device Manager agent. By limiting the impact of malicious requests that have a large number of headers, this setting can be useful in repelling attacks that are intended to impair services or cause a buffer overflow. Normally, the default value of this property need not be changed.
Table 3-8 server.properties File Property Description server.http.log.reverseDNS (see Note) Specify whether the Device Manager agent uses reverseDNS. If you specify this property "true", the Device Manager agent tries to find the hostname in the IP address. When the reverse DNS find the host according to the IP address, the host name is recorded into the access.log file (see section 4-4-1 ).
Table 3-8 server.properties File Property Description server.http.security.clientIP (see Note) Specify that the remote host or subnet can send a request to the Device Manager agent. This setting limits the IP addresses permitted for connection, thus preventing denial-of-service attacks or other attacks that intend to overflow buffers. In the following example, the specification permits 191.0.0.2 and 192.168.0.0 to 192.168.255.255 to connect to the Device Manager agent: server.http.security.clinentIP=191.
Table 3-8 server.properties File Property Description server.http.server.timeOut (see Note) Specify a timeout value (in seconds) for receiving a response from the Device Manager server when registering host information using the HiScan command. If no response is received from the Device Manager server by the time specified in this property, the Device Manager agent concludes that an error has occurred and the HiScan command terminates abnormally.
Table 3-9 logger.properties File Property Description logger.loglevel You can specify the level of log that the Device Manager agent outputs to the files error.log and trace.log (see section 4-4-1 ). Log levels: DEBUG, INFO, WARN, ERROR, and FATAL. Default: INFO. logger. MaxBackupIndex You can specify the maximum number of log file backups. If more log files are generated than specified, the Device Manager agent writes over the oldest one.
4 Troubleshooting Device Manager Agent Operations This chapter covers the following topics: • Acquiring Error Information Collectively (see section 4-1 ) • Troubleshooting Solaris™, AIX®, HP-UX, and Linux® Systems (see section 4-2 ) • Troubleshooting Windows® 2000 and Windows Server™ 2003 Systems (see section 4-3 ) • Device Manager Agent Log Files (see section 4-4 ) 4-1 Acquiring Error Information Collectively If an error occurs in the Device Manager agent, you can use Trouble Information Collector
• In Solaris™, AIX®, HP-UX, or Linux®: • TIC.sh [-outdir location-of-resultDir-directory [-f]] Arguments • -outdir location-of-resultDir-directory Specifies the location of the resultDir directory for storing the acquired error information. Specify the relative path from the execution directory or the absolute path. If another resultDir directory already exists in the specified location, a confirmation message displays, asking whether to delete that directory.
Figure 4-1 Executing TIC Command 4-2 Troubleshooting Solaris™, AIX®, HP-UX, and Linux® Systems For information on platform-specific logs that will be needed for troubleshooting these systems, please see Table 4-5 through Table 4-8. 1. 2. First, to determine the status of the Device Manager agent package on a specific host, execute the following applicable command for your OS: • # pkginfo -l HDVMAgent ( Solaris™ Systems). • # lslpp –l HDVMAgent.rte (AIX® Systems).
This produces output showing the Device Manager agent entry in the root crontab (see Figure 4-2). In this case, the last two lines of output from the crontab command show the entry governing scheduled execution of the HiScan command. Use the man crontab command to see an explanation of the format of this entry. The following explains the log file for the HiScan command. The HiScan command log files HiScan.msg, HiScan.log, and HiScan.
Table 4-2 Location of HiScan.log and HiScan.err System Type Location Solaris™ /opt/HDVM/bin/logs/HiScan.log HP-UX /opt/HDVM/bin/logs/HiScan.log AIX ® /usr/HDVM/bin/logs/HiScan.log ® Linux Windows /opt/HDVM/bin/logs/HiScan.log ® \ProgramFiles\HDVM\agent\bin\logs\Hi Scan.log, HiScan.
Table 4-3 Location of server.properties System Type Location Solaris™ /opt/HDVM/agent/config/server.properties HP-UX /opt/HDVM/agent/config/server.properties AIX ® /usr/HDVM/agent/config/server.properties ® Linux Windows /opt/HDVM/agent/config/server.properties ® \ProgramFiles\HDVM\agent\config\server.
2. Check whether the job entry schedule for each Device Manager agent is correct by viewing the Day and Time columns. If they are incorrect, delete each incorrect entry and re-enter it. 3. Check whether the job entry schedule for each Device Manager agent is correct by viewing the Command Line column. You can verify the jobs registered in the Command Line column from the command prompt. If executed successfully, no additional messages are displayed. A timestamp is recorded in the HiScan.
4-4 Device Manager Agent Log Files If an error occurs in the Device Manager agent, an error message is output to a log file, for use in determining the cause of the error. For details about the error messages for the Device Manager agent, contact your HP support representative for assistance. 4-4-1 Error Log Files If any problem occurs in the execution of the daemon/service or WebServer processes of the Device Manager agent, it records information about that problem to the proper log files.
File to Collect File Location Explanation access.log Installation-folder-for-DeviceManager-agent\agent\logs\ Access log for the communication control function. error.log Installation-folder-for-DeviceManager-agent\agent\logs\ Communication control function error log. service.log Installation-folder-for-DeviceManager-agent\agent\logs\ Servlet function operation log. trace.
Table 4-6 Required Logs for Troubleshooting Solaris™ Hosts File to Collect File Location Explanation access.log /opt/HDVM/agent/logs/ Access log for the communication control function. error.log /opt/HDVM/agent/logs/ Communication control function error log. service.log /opt/HDVM/agent/logs/ Servlet function operation log. trace.log /opt/HDVM/agent/logs/ Warnings of communication control function, internal trace data log. HiScan.
Table 4-8 Required Logs for Troubleshooting AIX Hosts File to Collect File Location Explanation access.log /usr/HDVM/agent/logs/ Access log for the communication control function. error.log /usr/HDVM/agent/logs/ Communication control function error log. service.log /usr/HDVM/agent/logs/ Servlet function operation log. trace.log /usr/HDVM/agent/logs/ Warnings of communication control function, internal trace data log. HiScan.
Acronyms and Abbreviations API ASCII application programming interface American Standard Code for Information Interchange CIM Common Information Model DNS Domain Name Server HBA HTML HTTP host bus adapter hypertext markup language hypertext transfer protocol JRE Java Runtime Environment or Java 2 Runtime Environment LU LUN logical unit logical unit number, logical unit NIC network interface card OS operating system RTE run time environment SCSI SDK SNIA SP small computer systems interface
Index C R calling the Support Center, 73 changing execution period at command, 44 atdaily.bat file, 44 Commands hldutil, 10 customer support, 73 Red Hat Linux® troubleshooting Agent operations, 68 D Device Manager Agent supported storage subsystem, 12 H hdvmagt confirming operating status, 43 restarting, 43 starting, 43 stopping, 43 hdvmagt daemon process, 42 hdvmagt_account command, 53 HiScan hldutil command syntax, 48 HiScan command HiScan.err, 69 HiScan.log, 69 HiScan.
