SANworks by Compaq Storage Resource Manager Enterprise Edition Installation Guide Part Number: AA-RLFDD-TE Fourth Edition (June 2002) Product Version: 4.0B This guide enables system administrators of Windows NT/Windows 2000 domains and workgroups to install, configure, and manage SANworks™ Storage Resource Manager Servers and Agents on various platforms.
© 2002 Compaq Information Technologies Group, L.P. Compaq, the Compaq logo, SANworks, StorageWorks, Tru64, and OpenVMS are trademarks of Compaq Information Technologies Group, L.P. in the U.S. and/or other countries. Microsoft, MS-DOS, Windows, and Windows NT are trademarks of Microsoft Corporation in the U.S. and/or other countries. Intel and Pentium are trademarks of Intel Corporation in the U.S. and/or other countries. UNIX is a trademark of The Open Group in the U.S. and/or other countries.
Contents About this Guide Text Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Symbols in Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Compaq Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 3 Installation Prerequisites SRM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Account Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 5 Modifying Installation Settings Database Transaction Logs and SRM Upgrading/Reinstalling . . . . . . . . . . . . . . . . . . . 5–1 Modifying an SRM for Windows NT/Windows 2000 Installation . . . . . . . . . . . . . . . . 5–2 Modifying Installed Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3 Reinstalling or Upgrading Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4 Uninstalling Components . . . . . . . . . . . . . . . . .
Contents NetWare Plug-In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Plug-In Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before you Register this Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–3 Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–4 Database Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–6 B Post-Installation Reference Uninstalling SRM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Running SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–6 Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–7 Error When Trying to Submit Scans or Remote Install Jobs . . . . . . . . . . . . . . . . . C–7 Reports do not show recently updated data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–7 Cache Contains Old Data . . . . . . . . . . . . .
Contents SRM for UNIX FAQ (Frequently Asked Questions) . . . . . . . . . . . . . . . . . . . . . . . . . C–21 After an Agent is installed, Why don’t We See All the Information About it in SRM?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–22 How Can I Tell if a Scan is Running? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–22 What Happens if the UNIX Agent Crashes? . . . . . . . . . . . . . . . . . . . . . . . . .
Contents OEMScanio Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Messages Always Logged (Do not Require Registry Key Settings). . . . . . . Messages Requiring Registry Key HKEY_LOCALMACHINE\Software\ Storeway\OEMScan\Log>0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Messages Requiring Registry Key HKEY_LOCALMACHINE\Software\ Storeway\OEMScan\Log>1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4–21 4–22 4–23 4–24 4–25 4–26 4–27 4–28 4–29 4–30 4–31 4–32 4–33 4–34 5–1 6–1 6–2 6–3 6–4 6–5 7–1 7–2 7–3 C–1 C–2 Advanced Agent Security Setting dialog box . . . . . . . . . . . . . . . . . . . . . . . . . 4–22 Choose Destination Location dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–23 Start Installation dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24 Installing dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this Guide The following sections are covered: • Text Conventions • Symbols in Text • Getting Help • Compaq Authorized Reseller Text Conventions This document uses the conventions in Table 1 to distinguish elements of text.
About this Guide Table 1: Text Conventions (Continued) Element • User Input and System Responses (Output and Error Messages) • COMMAND NAMES • Drive Names Convention Initial Caps and monospace font. Examples User Input and System Responses: • To exit from the program, type Exit.
About this Guide Symbols in Text These symbols may be found in the text of this guide. They have the following meanings. WARNING: Text set off in this manner indicates that failure to follow directions in the warning could result in bodily harm or loss of life or damage to equipment. CAUTION: Text set off in this manner indicates that failure to follow directions could result in damage to equipment or loss of information.
About this Guide • Detailed, specific questions Compaq Website The Compaq Website has the latest information on this product as well as the latest drivers. Access the Compaq Website at: http://www.compaq.com/storage. From this Website, select SANworks. Compaq Authorized Reseller For the name of your nearest Compaq Authorized Reseller: xvi • In the United States, call 1-800-345-1518. • In Canada, call 1-800-263-5868. • Elsewhere, see the Compaq Website for locations and telephone numbers.
1 Introduction SRM enables administrators of Windows NT/Windows 2000 domains and workgroups to manage distributed storage resources across the enterprise both effectively and efficiently. SRM automatically creates configuration and usage reports organized by domain and workgroup, computer, disk, file system, group, and user. SRM Servers and Agents An SRM Server can manage several kinds of Agents: Windows NT/Windows 2000, StorageWorks™ NAS, UNIX, OpenVMS, and Linux.
Introduction • An average of the number of managed file systems where each user has space. Typically, a user has space on a few file systems, but not on all managed file systems. • Fifteen hundred users. • The total number of users known to the SRM Server. To SRM, a user is one who owns at least one file on a managed file system. • One hundred managed directories. • The number of directories that you designate as managed.
Introduction domain, and the SRM Service Login Account and the SRM Server in different domains. Both worksheets assume the default name of SRMSvcUser for the Service Login Account and that the SRM Server installation includes an SRM Agent. If you use these worksheets to define your environment’s configuration before installation, make note of the SRM Server’s Service Login Account password and keep it in a secure place. You will need it during the SRM installation.
Introduction SRM Server and Service Login Account in Different Domains This worksheet shows how the trusts are configured when the Server’s Service Login Account and its password are maintained in one domain, and the SQL Server, SRM Server, and SRM Agents are installed in other domains, as shown in Figure 1–2. If your Server’s Service Login Account uses a non-default name, make a note of it. Record the password for your SRM Server’s Service Login Account.
Introduction Since the SRM Server is an SQL Server client, you can install the SQL Server Client Utilities on the SRM Server computer if you want to configure the SQL client. This is completely optional. SRM does not require that the client utilities be installed on the SRM Server computer for installation or operation. There is a one-to-one relationship between SRM and its database. If upgrading an existing multiple SRM database installation, each SRM Server must be upgraded individually.
Introduction As with all SRM installations, remember to install the SRM Server first. The service user account set up on the SRM Server (by default SRMSvcUser) must be in place before you install any SRM Agents. You must provide the service user account’s password during Agent installation. Additionally, be sure that the login account you plan to use for installation is a member of the Local Administrator group on each computer in each workgroup.
2 Installation Preparation This chapter includes procedures that will simplify installation of Storage Resource Manager (SRM) Enterprise Edition.
Installation Preparation 4. Click Next on the Welcome to the Prerequisite Check Program dialog box. You can also click View Readme on this dialog box to review the SRM Release Notes in the computer’s default browser. 5. Select the check box of the components you want to verify on the Select Components dialog box. Clear the check boxes of the components you do not need to verify. 6. Click Next. 7. If the prerequisite check passes, the Prerequisite Check OK dialog box displays. 8.
Installation Preparation Figure 2–1: Distributed COM Configuration Properties dialog box 4. Select the Default Properties tab. The properties page displays, as shown in Figure 2–2.
Installation Preparation Figure 2–2: Distributed COM Configuration Properties, Default Properties tab 5. Verify that the check box for Enable Distributed COM on this computer is selected. If it is unchecked, select it.
Installation Preparation 6. Click OK on this dialog box and again on the Distributed COM Configuration Properties dialog box. Distributed COM is now enabled on this computer. Prepare SQL Server for SRM This section addresses two types of SRM SQL Server information, Confirm SRM SQL Server Settings and SRM SQL Server Database Configuration. The Confirm SRM SQL Server Settings section explains how to prepare an SQL Server for an SRM installation.
Installation Preparation • Make sure that you have adequate CALs for SRM database access if you are using an SQL Server licensing model that requires CALs. SRM requires a minimum of two CALs, one for the SRM Server and one for access to the database through the SRM Web. SRM SQL Server Database Configuration This optional procedure contains SRM SQL Server database configuration requirements and guidelines for SRM SQL Server 7.0 databases. It does not explain how to create the database.
Installation Preparation c. Verify that the SQL Server name in the Server field of the first dialog box is correct. d. Make sure the Change the default database to field in the third dialog points to the new database. e. Setup configures all other SRMDB data source settings during installation. IMPORTANT: Modifying any data source settings after installation will result in unpredictable behavior. 6. Optional configuration steps include: a. Define the database maintenance configuration. b.
Installation Preparation Create the SRM Service Login Account SRM runs as a Windows NT/Windows 2000 service, which needs an authorized account to run. By default, this account is SRMSvcUser on each computer where an SRM Server, an Agent, or both are installed. Use the default account; however, you can use an account specific to your environment. The SRM Server uses the SRM Service Login Account to authenticate communication with SRM Agents.
Installation Preparation • Domain Admins (This is the global Domain Admins group in the Service Login Account’s domain. This applies only if you are installing the SRM Server in a domain). 4. After the user account is created, go to Policies/User Rights. Choose the Show Advanced User Rights check box. Grant the Logon as a Service right to the SRMSvcUser account. 5. Make a note of the account’s password; you will need it during SRM installation. 6. Apply the settings and install SRM.
Installation Preparation 7. Click OK to apply the configuration. To create the SRMAdmin group on Windows 2000: 1. On the computer where you will install the SRM Server software, log in to an account with Administrator privileges. 2. Go to Start > Programs > Administrative Tools > Computer Management. 3. In the console tree, expand Local Users and Groups. 4. Right-click the Groups folder, and then create a new group named SRMAdmin. 5. Assign group membership as desired.
Installation Preparation 6. Assign group membership as desired. NOTE: You can add Everyone to allow any user from other trusted domains access to SRM information. 7. Click OK to apply your configuration. To create the SRMUser group on Windows 2000: 1. On the computer where you will install the SRM Server software, log in to an account with Administrator privileges. 2. Go to Start > Programs > Administrative Tools > Computer Management. 3. In the console tree, expand Local Users and Groups. 4.
3 Installation Prerequisites Setup verifies all installation prerequisites and provides a report of any missing or outdated prerequisites. Although you can complete the installation program with missing or outdated prerequisites, you should restart the system after rectifying any prerequisite discrepancy to ensure that SRM runs smoothly. For more SRM information, including downloading prerequisite software, access the Compaq Website at: www.compaq.com/products/sanworks/srmindex.html.
Installation Prerequisites • Internet Explorer 5.01 (or 5.0 with SP1) or later. • Microsoft Data Access Components (MDAC) 2.1 or later. • TCP/IP. • SQL Server 7.0 with SP1 or later. Required Account Information Setup prompts for the required account information. Have it ready before beginning the installation process to save time during installation. • Obtain the login ID and password for the account to use for database creation or access.
Installation Prerequisites Required Software • Microsoft Windows NT Server or Workstation 4.0 with SP5 or later. or Microsoft Windows 2000, Server or Advanced Server edition. • TCP/IP. Required Account Information Setup prompts you for the required account information. Have it ready before beginning the installation process to save time during installation. • Obtain the name and password of the Service Login Account that this Agent will run under.
Installation Prerequisites — Tru64 UNIX 4.0f, 4.0g, 5.0, 5.0A, 5.1, or 5.1A — Red Hat Linux 6.2, 7.1, or 7.2 (Intel 32 only) NOTE: Using any other Linux product or version may yield unpredictable results. • SRM Server 4.0 or later must be installed on the network and able to manage this agent. Required Account Information Setup prompts you for the required account information. Have it ready before beginning the installation process to save time during installation.
Installation Prerequisites SRM Web Browser Shortcut The Web Browser shortcut starts the default Web browser and displays SRM’s Web-based user interface. Use the browser to access the information stored in an SRM database. Obtain the name of the target SRM Server computer before performing this installation. Setup prompts you to input this name during installation. The Web Browser shortcut can be installed on any Intel-compatible PC where you want quick access to your SRM data.
4 Installation This chapter describes how to install the following SRM components: • Installing the SRM Server • Installing and Registering SRM for Windows NT/ Windows 2000, Datacenter, and StorageWorks NAS Agent • Installing and Registering SRM for UNIX or Linux Agents • Installing and Registering SRM for OpenVMS Agent • Installing the SRM Web Browser Shortcut Before installing any of these components, the SRM prerequisite check must be run on the target computer to ensure that the computer meets
Installation SRM for Windows NT/Windows 2000 Components Common Installation Steps When you install the SRM for Windows NT/Windows 2000 components, follow the initial steps listed here. The specific component installation procedures begin with the next dialog box in the sequence. To install SRM for Windows NT/Windows 2000 components: 1. Exit all Windows programs and insert the SRM CD into the CD-ROM drive. 2. If Auto Start is enabled, the SRM Installation Menu launches automatically, as shown in Figure 4–1.
Installation NOTE: If you are installing from an SRM Upgrade CD, you must have SRM Version 1.0, 4.0, or 4.0A currently installed on your system. If you are installing from an SRM Web Update kit, you must have SRM Version 4.0 or 4.0A currently installed on your system. 4. To read the Release Notes, click Readme First. 5. Click Install. The Welcome dialog box displays, as shown in Figure 4–2. Figure 4– 2: Welcome dialog box 6. Review the information, then click Next.
Installation Figure 4– 3: Get Registration Information dialog box 8. Enter your name and the name of your company in the respective fields and click Next. The Select Components dialog box displays, as shown in Figure 4–4. 9. Go to the specific installation procedure for the component you are installing. Installing the SRM Server In addition to local administrator privilege on the computer, Setup prompts you for database creation privileges on the target SQL Server computer.
Installation Follow this procedure to install an SRM Server on a local Intel-compatible computer. SRM Server can only be installed locally. To install SRM Server: 1. Make sure that you are logged in to an account with local administrator privileges on the computer and have any additional privileged account information you may need. 2. Insert the SRM CD into the CD-ROM drive. Click the Next button to advance through the dialog boxes to the Select Components dialog box, as shown in Figure 4–4.
Installation 3. Choose the SRM Server check box. Click Next. The Get SQL Server Name dialog box displays, as shown in Figure 4–5. Figure 4– 5: Get SQL Server Name dialog box 4. Enter the name of the computer where SQL Server is installed in the SQL Server Name field. Click Next. 5. If you are logged in to an account with administrator privilege on this SQL Server, the Get Database Size dialog box displays, as shown in Figure 4–7. Go to step 7.
Installation Figure 4– 6: Privileged Account Required dialog box 6. Specify an account type and fill in the appropriate information. Click Next. The Get Database Size dialog box displays, as shown in Figure 4–7.
Installation Figure 4– 7: Get Database Size dialog box 7. Click Next to accept the initial default settings. The Get Service Login Information dialog box displays, as shown in Figure 4–9. or To change the initial default settings, click Advanced to go to the Get Database Size Estimation dialog box and edit the default initial database size, as shown in Figure 4–8.
Installation Figure 4– 8: Get Database Size Estimation dialog box 8. Review the settings. Make any desired changes, and click Next. The Get Service Login Information dialog box displays, as shown in Figure 4–9.
Installation Figure 4– 9: Get Service Login Information dialog box IMPORTANT: This is the Service Login Account that this SRM Server will use to run on this computer. 9. If you created the Service Login Account before running Setup, the dialog box has the Use an Existing Account option selected, with the account name that you created in the LoginID field. Enter the Domain and Password for this account, and click Next. The Get Web Shortcut Destination dialog box appears, as shown in Figure 4–11.
Installation or If you choose to create a new account and Setup determines that you do not have account creation privileges, the Privileged Account Required dialog box displays, as shown in Figure 4–10. Go to step 10. Figure 4– 10: Privileged Account Required dialog box 10. Provide information for an account that Setup can use to create the new Service Login Account. Typically, this is an account with domain administrator privileges in the target domain. Click Next.
Installation Figure 4– 11: Get Web Shortcut Destination dialog box 11. During installation of the SRM Server, the server name appears by default in the SRM Server Name field. This name is used to create a Web shortcut on the Start menu of the server. Click Next. The Choose Destination Location dialog box displays, as shown in Figure 4–12.
Installation Figure 4– 12: Choose Destination Location dialog box 12. Click Next to accept the default location. or Click Browse to navigate to another installation location for the Server and click Next. The Choose Web Destination Location dialog box displays, as shown in Figure 4–13.
Installation Figure 4– 13: Choose Web Dest ination Location dialog box 13. Click Next to accept the default Web location. or Click Browse to navigate to another Web location for the Server and click Next. The Start Installation dialog box displays, as shown in Figure 4–14.
Installation Figure 4– 14: Start Installation dialog box 14. Click Next to begin installing files on your computer. The Installing dialog box displays the progress of the installation, as shown in Figure 4–15.
Installation Figure 4– 15: Installing dialog box example 15. This dialog box lists all installed components, any services that must be restarted, and instructions on resolving any installation errors. Review the information and click Back to fix any installation errors. Click Next after all errors have been fixed. 16. After the software is installed, the Installation Complete dialog box displays, as shown in Figure 4–16.
Installation Figure 4– 16: Installation Complete dialog box 17. Click Finish to allow Setup to complete the installation. Installing and Registering SRM for Windows NT/ Windows 2000, Datacenter, and StorageWorks NAS Agent Other than local administrator privilege on the computer, Setup prompts you for no additional privileged account information unless you choose to create a new Service Login Account for this Agent.
Installation Follow this procedure to install an SRM for Windows NT/Windows 2000 Agent on a local Intel-compatible computer. For Microsoft Datacenter or StorageWorks NAS systems, use the same Agent installation procedure. Remote installation of an SRM for Windows NT/Windows 2000 Agent is performed from the SRM user interface. To install an SRM for Windows NT/Windows 2000 Agent: 1.
Installation 3. Select SRM Agent then click Next. The Get Service Login Information dialog box displays, as shown in Figure 4–18. Figure 4– 18: Get Service Login Information dialog box IMPORTANT: This is the Service Login Account for this SRM Agent to run as on this computer. 4. The default selection is Use System Account, which requires no account information.
Installation Figure 4– 19: Privileged Account Required dialog box 5. Provide information for an account Setup can use to create the new Service Login Account. Typically, this is an account with domain administrator privileges in the target domain. NOTE: You must use the same Service Login Account for the SRM Agent as the one used for the SRM Server. 6. Click Next. The Get Server Registration Information dialog box displays, as shown in Figure 4–20.
Installation Figure 4– 20: Get Server Registration Information dialog box NOTE: Enter the name of an SRM Server only if you want this Agent registered during installation. If you will manually register this Agent from a Server after installation, leave this dialog box blank and click Next. The Choose Destination Location dialog box appears, as shown in Figure 4–22. Go to step 10. 7. Type the name of the SRM Server that will monitor this Agent in the SRM Server Name field, and click Next.
Installation Figure 4– 21: Advanced Agent Security Setting dialog box 8. Specify if the SRM Server you listed in the Get Server Registration Information dialog box has access to the computer where you are installing this agent. If you need to specify an account or group, you must provide the login and domain information. 9. Click Next. The Choose Destination Location dialog box displays, as shown in Figure 4–22.
Installation Figure 4– 22: Choose Destination Location dialog box 10. Click Next to accept the default location. or Click Browse to navigate to another installation location for the Server and click Next. The Start Installation dialog box displays, as shown in Figure 4–23.
Installation Figure 4– 23: Start Installation dialog box 11. Click Next to begin installing files on your computer. The Installing dialog box displays the progress of the installation, as shown in Figure 4–24.
Installation Figure 4– 24: Installing dialog box 12. This dialog box lists all installed components, any services that must be restarted, and instructions on resolving any installation errors. Review the information and click Back to fix any installation errors. Click Next after all errors have been fixed. 13. If you are registering this Agent with an SRM Server during installation, the Agent Registration dialog box displays, as shown in Figure 4–25.
Installation Figure 4– 25: Agent Registration dialog box 14. Click Next. Setup launches the default browser on this computer and registers the Agent with the SRM Server you specified. When the registration is finished, the browser is minimized and a Success message displays, as shown in Figure 4–26.
Installation Figure 4– 26: Success message 15. Close the browser window. The Installation Complete dialog box displays, as shown in Figure 4–27.
Installation Figure 4– 27: Installation Complete dialog box 16. Click Finish to allow Setup to complete the installation. Installing and Registering SRM for UNIX or Linux Agents SRM for UNIX or Linux Agents must be installed using superuser privileges. No additional privileged account information is required. Tru64 Cluster Support When installing the SRM Agent on a Tru64 UNIX Cluster, the Agent’s installation script automatically registers with the SRM Server using the cluster alias.
Installation the computer name. Registration using the cluster alias provides high availability and eliminates the duplicate reporting of storage data. In the event of a node failure on the cluster, the SRM Agent will automatically failover and execute on another node. NOTE: SRM provides UNIX Agents for IBM AIX, Sun Solaris, Hewlett-Packard HP-UX, Compaq Tru64 UNIX, and a Linux Agent for Red Hat Linux. To install the SRM for UNIX or Linux Agent: 1.
Installation 6. Enter y or n. If you enter y, go to step 9. or If you enter n, the following message displays: Please enter port to use: 7. Enter the port you want to use. 8. If the proposed port is not available, the following message displays: Port port number is already in use. Please select another. 9. After the port is specified, the installation script proceeds and the following messages appear. Respond to each prompt appropriately.
Installation Installing and Registering SRM for OpenVMS Agent The SRM for OpenVMS Agent can be installed with system privileges. No additional privileged account information is required. To install the SRM for OpenVMS Agent: NOTE: The OpenVMS directories in these procedures are examples and might differ from the ones on your OpenVMS system. 1. Insert the SRM CD into the CD-ROM drive. 2. Mount the CD device on your target OpenVMS system, for example: MOUNT /MEDIA=CD /OVERRIDE=ID DKD100 3.
Installation CPQ AXPVMS SRM_AXP V4.2-3: Compaq Storage Resource Manager Agent for OpenVMS. © Compaq Computer Corporation 2000. All Rights Reserved. Compaq Computer Corporation *This product does not have any configuration options. Execution phase starting... The following product will be installed to destination: CPQ AXPVMS SRM_AXP V4.2-3 DISK$ALPHASYS:[VMS$COMMON.] or CPQ AXPVMS SRM_AXP V4.2-3 DISK$VAXSYS:[VMS$COMMON.] Portion done: 0%...20%...50%...80%...
Installation 7. Enable the service by entering configuration option 1. Enter configuration option: 1 You see the following message: SRM$AGENT Service requires a TCP Port to listen for SRM Server requests. It is recommended that a port in the range 11125-11127 be selected. The selection must not conflict with another service already installed on this system. 8. Enter a TCP port number, or press Enter to accept the default.
Installation The use of this Agent is according to the terms of the particular SRM license that you have (e.g. commercial, evaluation). You may register this OpenVMS Agent only with Compaq SANworks Storage Resource Manager Enterprise Edition servers. 1 - Accept the above NOTICE and Continue with Registration 2 - Not Accept the above NOTICE and Exit Registration Enter selection: 10. Enter 1 and press Enter to accept the above notice.
Installation behalf of the cluster, then specify the cluster alias name (or IP address). 13. Enter the Agent's Contact Name (or IP address). For example: Enter Agent's Contact Name (or IP address): [local hostname] 16.20.8.116 14. Enter the Agent's Assigned Port Number, or press Enter to accept the default. For example: Enter Agent's Assigned Port Number: [11125] 15. Enter the SRM Server's name (or IP address). For example: Enter SRM Server's name (or IP address): 16.20.204.212 16.
Installation NOTE: If you are not successful, you will return to the Agent Configuration Options menu. You will need to register the Agent again. SRM$AGENT Configuration Service is defined in the SYSUAF. Service directory exists. Service is defined in the TCP/IP SERVICE database. Service is enabled on specific node. Agent is registered as: engineering_private SRM$AGENT configuration options: 1 - Register Agent with an SRM Server 2 - Unregister Agent with an SRM Server E - Exit SRM$AGENT configuration 18.
Installation Figure 4– 28: Example OpenVMS configuration Refer to Figure 4–28 as you read the sections that follow. Registering with a Cluster Alias If you have a cluster alias, for example X, register the SRM OpenVMS Agents in the following way: 1. Register Nodes A, B, and C in “p” (private) configuration mode. 2. Do not register D or E, since they have no private storage devices. 3. Register the cluster alias X in “c” (cluster) configuration mode from any one of the nodes.
Installation Registering without a Cluster Alias If you do not have a cluster alias, register the SRM OpenVMS Agents according to one of the following examples: Example 1 1. Register Nodes A, B, and C in “p” (private) configuration mode. 2. Register either Node D or Node E in “c” (cluster) configuration mode, leaving the other node unregistered. • In this configuration, the nodes will report on the following disks: — Node A will report on Disks 1 and 2. — Node B will report on Disk 3.
Installation 2. At the prompt, enter the following command: @srm$agent_config.com You see the following: SRM$AGENT Configuration Procedure This procedure helps you define the parameters required to run Compaq Storage Resource Manager Agent for OpenVMS on this system. Please select the TCP/IP stack running on this system: 1 - UCX or Digital TCP/IP Services 2 - TCPware E - Exit SRM$AGENT configuration 3. Select the appropriate TCP/IP stack.
Installation The use of this Agent is according to the terms of the particular SRM license that you have (e.g. commercial, evaluation). You may register this OpenVMS Agent only with Compaq SANworks Storage Resource Manager Enterprise Edition servers. 1 - Accept the above NOTICE and Continue with Registration 2 - Not Accept the above NOTICE and Exit Registration Enter selection: 5. Enter 1 and press Enter to accept the above notice.
Installation behalf of the cluster, then specify the cluster alias name (or IP address). 8. Enter the Agent's Contact Name (or IP address). For example: Enter Agent's Contact Name (or IP address): [local hostname] 16.20.8.13 9. Enter the Agent's Assigned Port Number, or press Enter to accept the default. For example: Enter Agent's Assigned Port Number: [11125] 10. Enter the SRM Server's name (or IP address). For example: Enter SRM Server's name (or IP address): 16.20.204.167 11.
Installation NOTE: If you are not successful, you will return to the Agent configuration options menu. You will need to register the Agent again. SRM$AGENT Configuration Service is defined in the SYSUAF. Service directory exists. Service is defined in the TCP/IP SERVICE database. Service is enabled on specific node.
Installation Figure 4– 29: Select Components dialog box 2. Select SRM Web Shortcut and click Next. The Get Web Shortcut dialog box displays, as shown in Figure 4–30.
Installation Figure 4– 30: Get Web Shortcut dialog box 3. Provide the name of the SRM server for which you want to have a Web shortcut. Click Next. The Choose Destination Location dialog box displays, as shown in Figure 4–31.
Installation Figure 4– 31: Choose Destination Location dialog box 4. Click Next to accept the default Web location. or Click Browse to navigate to another Web location for the Server and click Next. The Start Installation dialog box displays, as shown in Figure 4–32.
Installation Figure 4– 32: Start Installation dialog box 5. Click Next to begin installing files on your computer. The Installing dialog box displays the progress of the installation, as shown in Figure 4–33.
Installation Figure 4– 33: Installing dialog box 6. This dialog box lists all installed components, any services that must be restarted, and instructions on resolving any installation errors. Review the information and click Back to fix any installation errors. Click Next after all errors have been fixed. 7. After the software is installed, the Installation Complete dialog box displays, as shown in Figure 4–34.
Installation Figure 4– 34: Installation Complete dialog box 8. Click Finish to allow Setup to complete the installation.
5 Modifying Installation Settings This chapter describes how to • Modify installed SRM components • Add or remove components • Reinstall or upgrade SRM Server and Agents • Uninstall the SRM Server and Agents All modifications of SRM installations are performed from the Change Installation Settings dialog box, as shown in Figure 5–1. All modifications to UNIX, Linux, or OpenVMS installations are performed from the command prompt.
Modifying Installation Settings 6. Highlight the appropriate database name in the list. By default, this is SRMDB_COMPUTERNAME. Right-click and select Properties from the context menu. 7. Make sure there is adequate disk space available for the log file to grow. The log file might grow up to 70% of your database size. a. Select the General tab and note the amount of space allocated for the database. Calculate 70% of this number; this is the amount of disk space you need to hold the log file. b.
Modifying Installation Settings Figure 5–1: Change Installation Settings dialog box 5. From this dialog box, you can modify your installation, reinstall or upgrade your software, or uninstall your SRM software. See the following sections in this chapter for more information on these features. Modifying Installed Components Use the Modify option on the Change Installation Settings dialog box to add or remove selected SRM components from the local computer.
Modifying Installation Settings To modify installed components: 1. Click the Modify button on the Change Installation Settings dialog box. The Select Components dialog box displays. NOTE: Components currently installed on the computer are selected, and those not installed are not selected. 2. Choose the check boxes of all components you want installed on this computer and clear the check boxes of all components you do not want on the computer. Click Next. 3.
Modifying Installation Settings To uninstall components: 1. Click Remove All on the Change Install Settings dialog box. The Perform Uninstall dialog box displays. 2. Click Next on the Perform Uninstall dialog box. Setup then removes all SRM software from the computer. 3. Click Finish in the Uninstallation Complete dialog box. Modifying SRM for UNIX or Linux Installations One SRM Server can monitor multiple SRM agents, including SRM for Windows NT/Windows 2000, and UNIX Agents.
Modifying Installation Settings When the registersrm script detects a previous installation, it uses the previous configuration information, attempting to repair any deficiencies in the set of configuration files /etc/services, /etc/inetd.conf, and /etc/srmagent/agentconfig.
Modifying Installation Settings To unregister SRM for UNIX or Linux Agent, type the following at the command line on the UNIX or Linux system: /installdirectory/srmagent/registersrm -r Follow any prompts as they are displayed. Reverting to a Previous Version of SRM for UNIX or Linux Agent Software Use the revertsrm script to revert to an earlier version of SRM for UNIX or Linux. To revert to a previous version of SRM for UNIX or Linux Agent: 1.
Modifying Installation Settings Modifying SRM for OpenVMS Installations The following sections describe how to unregister, disable, and uninstall the OpenVMS Agent, as well as how to register the Agent with additional SRM Servers. Unregistering the SRM for OpenVMS Agent The directories in this procedure are examples and might differ from your OpenVMS systems. To unregister the OpenVMS Agent: 1.
Modifying Installation Settings Service is enabled on specific node. Agent is registered as: engineering_private. SRM$AGENT configuration options: 1 - Register Agent with an SRM Server 2 - Unregister Agent with an SRM Server E - Exit SRM$AGENT configuration 4. Enter configuration option number 2. The Agent is currently registered as follows: Agent engineering_private registered with SRM Server 16.20.204.167:80 Proxy 16.20.212.174:11125:2:Auth_By_Addr:20000814.
Modifying Installation Settings NOTE: If you are not successful, you will return to the Agent configuration options menu. You will need to unregister the Agent again. SRM$AGENT Configuration Service is defined in the SYSUAF. Service directory exists. Service is defined in the TCP/IP SERVICE database. Service is enabled on specific node. Agent is not registered. SRM$AGENT configuration options: 1 - Register Agent with an SRM Server 2 - Disable service on this node E - Exit SRM$AGENT configuration 7.
Modifying Installation Settings The following message appears: TCP/IP stack is UCX. Press Return to continue. SRM$AGENT Configuration Service is defined in the SYSUAF. Service directory exists. Service is defined in the TCP/IP SERVICE database. Service is enabled on specific node. Agent is registered as: engineering_private. SRM$AGENT configuration options: Service is defined in the SYSUAF. Service directory exists. Service is defined in the TCP/IP SERVICE database. Service is enabled on specific node.
Modifying Installation Settings NOTE: The directories in this procedure are examples and might differ from your OpenVMS systems. 1. Depending on your OpenVMS system, enter one of the following commands at the OpenVMS system prompt in the directory where you downloaded the SRM OpenVMS Agent: product remove srm_axp (for an Alpha system) or product remove srm_vax (for a VAX system) The following message appears: The following product has been selected: CPQ AXPVMS SRM_AXP V4.
Modifying Installation Settings SRM$AGENT Configuration Service is not defined in the SYSUAF. Service directory exists. Service is not defined in the TCP/IP SERVICE database. Service is not enabled on specific node. SRM$AGENT configuration options: 1 - Enable service on this node E - Exit SRM$AGENT configuration 4. Enter option E to exit the installation program. The following message appears: ...80%...90%...100% The following product has been removed: CPQ AXPVMS SRM_AXP V4.
6 Installing and Registering Plug-ins This chapter describes installation and registration procedures for the plug-ins provided with SRM. For information about a particular plug-in, refer to the separate sections at the end of this chapter or to the Readme file included in the same directory as the plug-in you want to install. What are Plug-Ins? A plug-in is software that allows SRM to scan, collect, and report information from various types of objects, such as SAN switches.
Installing and Registering Plug-ins Reports available in the graphical user interface display the information reported by the plug-ins. NetWare systems are listed in the Managed Computers report. All other plug-in types have sections devoted to them. Plug-In Kits Provided with SRM Plug-in kits are on your SRM CD-ROM in a directory named Plug-ins. This directory contains a subdirectory for each type of plug-in.
Installing and Registering Plug-ins • For more information about requirements for a particular plug-in, refer to sections at the end of this chapter or to the Readme file that comes with each plug-in. Installing a Plug-In To install the plug-in on the selected SRM Agent computer: 1. Insert your SRM CD-ROM into your SRM Agent computer and locate the appropriate plug-in installation kit in the Plug-ins directory. 2. In Windows Explorer, click the executable file to start the installation process.
Installing and Registering Plug-ins 4. Click Next, and then click Finish. The plug-in files are removed from the computer. NOTE: If you uninstall the SRM Agent from a computer, it automatically removes all plug-ins installed on that computer. Registering a Plug-In Once you have installed a plug-in, you are ready to register it with the SRM Server so that it can be scanned and reported on. Each plug-in provided with SRM includes a registration utility called the Plug-In Registration Wizard.
Installing and Registering Plug-ins Figure 6– 1: Plug-In Registration Introduction dialog box 2. Click Next. The Registration Function dialog box displays, as shown in Figure 6–2.
Installing and Registering Plug-ins Figure 6– 2: Registration Function dialog box 3. Select the registration task you want to perform. The following list describes each registration task: • Register an unmanaged object — This option registers the device as a managed object with the SRM Server. Upon the successful completion of this task, the SRM Server knows about and manages scans for the object you specified.
Installing and Registering Plug-ins 5. Click Next. The Required Registration Information dialog box displays, as shown in Figure 6–3. Figure 6– 3: Required Registration Information dialog box 6. You must fill in all of the fields in this dialog box before you can continue to the next step. 7. The following list describes each field: • Host Name — The name of this field may be different depending upon the type of object you are registering.
Installing and Registering Plug-ins • Proxy Agent Name — This is the name of the SRM Agent computer where you installed the plug-in. NOTE: The SRM Agent computer named in this field must be a managed computer on the SRM Server with which you want to register the object. • SRM Display Name — This is the name by which the SRM Server knows the managed object, and it displays in all SRM reports. This box is automatically filled in with the name you entered in the Host Name box.
Installing and Registering Plug-ins Figure 6– 4: Optional Registration Information dialog box 10. The following list describes each field: • Contact information — Enter the contact information for the unmanaged object being registered (for example, System Administrator, x555). • Location information — Enter the geographical location of the unmanaged object being registered (for example, Data Center, Building 5).
Installing and Registering Plug-ins • Manufacturer URL — Enter the URL of the corporate Website for the vendor that produced the unmanaged object being registered. • Display Text for Manufacturer URL — Enter the text to be displayed in SRM reports as the link to the manufacturer’s Website. 11. When the wizard is done registering the unmanaged object, the Registration Command Output dialog box displays, as shown in Figure 6–5. Figure 6– 5: Registration Command Output dialog box 12.
Installing and Registering Plug-ins Saving your Registration Settings to a File You can save your registration settings to a file if you want. You may want to do this if you are registering many unmanaged objects of the same type. To save your registration settings: 1. In the Required Registration Information dialog box, click Save As. The Save As dialog box displays. 2. Enter a name for the file and give it an .SVR file extension (for example, MySANSwitchSettings.svr).
Installing and Registering Plug-ins • The SRM Agent computer should have a static or long-lease DHCP TCP/IP address. • rsh must be enabled on each Network Appliance Filer that you want to scan. • SNMP must be enabled on each Network Appliance Filer that you want to scan. Before You Register this Plug-In The Plug-In Registration Wizard prompts for the following information; organize it beforehand to save time: • The network name that the SRM Agent and plug-in uses to contact the Filer via TCP/IP.
Installing and Registering Plug-ins • This plug-in requires rsh access to the NAS system. Select Allow rsh Permissions Setup if you want the registration wizard to automatically update the hosts.equiv file, which must be modified to enable rsh access. If you do not want to continue with the automatic update, clear the check box and click Next to proceed with the registration. • Computer Name — Select the computer name or TCP/IP address to use for rsh access to this Filer.
Installing and Registering Plug-ins Editing Scan Proxy Information Using SRM, you can edit the proxy system settings for a registered Filer. For example, you can change the SRM Agent computer you want to use for computer scans, or you can set up a computer to use for CIFS-based file system scanning. To edit scan proxy information: 1. Launch Storage Resource Manager. 2. Click the Options tab, and then click the Scans notebook. 3. In the navigation pane, click select proxy. The Select Proxy page displays. 4.
Installing and Registering Plug-ins 3. In the Computer Name column, select the NAS system for which you want to enable scanning. The Single Computer Report displays. 4. Scroll down to the File Systems Report, and click Modify to change the scanning enabled status of the file systems displayed in the table. The File System Scan Settings page displays. 5. In the Scanning Enabled column, select the check boxes beside the file systems that you want to scan, and click Submit.
Installing and Registering Plug-ins Many NetWare administrative utilities report file ownership based on the user who created the file. SRM file ownership helps you find the NetWare users modifying files. Using the Plug-In Registration Wizard When registering a NetWare server with the SRM Server, provide the following information in the first Required Registration Information dialog box: • NetWare Server Name — Enter the simple (not distinguished) name of the NetWare server as it is known on the network.
Installing and Registering Plug-ins Editing Scan Proxy Information You must use the following steps to change the proxy agent used for volume scans, the NetWare user name, password, and context information used when performing file system scans of NetWare volumes. Using SRM, you can edit the proxy system settings for a registered NetWare server.
Installing and Registering Plug-ins • Password — Enter the password for that user — it is kept encrypted in the SRM database. • Context — Enter the NDS context for that user. The context must be in the same NDS tree as the NetWare server being scanned.
Installing and Registering Plug-ins • The SRM Agent computer must contain a Fibre Channel controller that is connected to the same Fibre Channel network as the Compaq HSG80-based RAID subsystem with which you want to communicate. • The SRM Agent computer must have a connection enabled to one or more LUNs on the HSG80-based RAID subsystem. NOTE: The command console LUN can be the LUN to which the SRM Agent computer connection is enabled.
Installing and Registering Plug-ins 4. Next to the RAID option, click Modify. The Modify Scan Settings for RAID dialog box displays. 5. In the Select a managed object list box, choose the RAID subsystem you want to modify, and make the necessary changes. You can change the following setting: • Computer Scan Agent — Enter the name of a managed SRM Agent computer that has the correct plug-in installed on it. If you select an SRM 4.
Installing and Registering Plug-ins Using the Plug-In Registration Wizard When registering a SmartArray controller with the SRM Server, provide the following information in the Required Registration Information dialog box: • Host Name — Enter the network name of the system in which the SmartArray controller to be scanned is installed. • SRM Display Name — Enter the name of the SmartArray that you want displayed in SRM reports. This name is arbitrary.
Installing and Registering Plug-ins Plug-In Prerequisites The SRM 4.0B Windows NT/Windows 2000 Agent must be installed on the computer that you want to act as the SRM proxy agent. Before you Register this Plug-In The Plug-In Registration Wizard prompts you for the following information; organize it beforehand to save time: • The TCP/IP address of the SAN switch in dotted notation (for example, 255.255.255.255).
Installing and Registering Plug-ins You can change the following setting: • Computer Scan Agent — Enter the name of a managed SRM Agent computer that has the correct plug-in installed on it. If you select an SRM 4.0B Agent computer that does not have the correct plug-in installed, all computer scans for the selected SAN switch fail.
7 Security SRM security is designed to manage user access to SRM. The default settings established during installation provide a basic configuration that you can modify to meet the specific needs of your environment. How SRM Determines User Access There are two kinds of SRM user access: • Privileged access — provides the user access to the SRM Options pages for SRM administration.
Security Default SRM Directory Settings During installation, Setup sets permissions on the SRM program files directory and the Web directory. All directories and files within these directories inherit the permissions. By default, the SRM program files directory is installed in %System Drive%\Program Files\StorageResourceManager and the SRM Web directory is installed in %System Drive%\InetPub\wwwroot\StorageResourceManager. Setup applies the following access rights to the SRM program and Web directories.
Security Grants read access to local users. In a domain, this group includes Domain Users. Extra Security Settings To add an extra level of security to your SRM environment, make the following changes to the default setup: • System — Required as is for proper operation; do not change. • Administrators — Required as is for proper operation; do not change. • SRMAdmin — Required for proper operation. Members of the SRMAdmin local group on the SRM Server can modify SRM settings.
Security SRM Security in Multiple Domains SRM depends on standard Windows NT security mechanisms for its operation. The SRM Server and Agent authenticate each other to prevent potentially sensitive information from being revealed to unauthorized programs. Using the SRM Service Login account (SRMSvcUser, by default), the SRM Server logs in and runs as the Windows NT Service, SRPROCMGR.EXE, while SRM Agents log in and run as the Windows NT Service, SRMAGENT.EXE.
Security Figure 7–1: Trust Relationships dialog box 4. Click Add in the Trusting Domains section. The Add Trusting Domain dialog box displays, as shown in Figure 7–2.
Security 5. Enter the domain where the SQL Server, SRM Agents, and SRM Server will be installed (ENGTEST2 in this example) in the Trusting Domain field. 6. Enter the password in the Initial Password field. 7. Re-enter the password in the Confirm Password field. Save this password because you will need it during the next procedure. 8. Click OK. The Domain is now a trusting domain. On the Trusting Domain (the domain of the SQL Server, SRM Agent and SRM Server. In this example, ENGTEST2): 1.
A Database Concepts SRM creates one database where all of your SRM data is maintained. When you install the SRM server, you have the ability to specify the database space allocation for your SRM data. SRM, SQL Server, and IIS You can configure SRM with SQL Server and IIS in one of the following ways: Configuration 1 • Computer 1: SQL Server • Computer 2: SRM Server, IIS Server • The Web browser can be installed on any computer. In this configuration, computers 1 and 2 can be in different domains.
Database Concepts You can access the sizing tool before installing SRM on any Windows NT/Windows 2000 computer that does not have any SRM components installed. You can also use it during your SRM installation if SRM 1.0 Server is not installed and the SRMDB data source does not point to a valid SRM SQL Server database. Otherwise, the database dialog boxes are bypassed.
Database Concepts • Managed Directories: The number of directories that you designate as managed. The history for these directories is kept in addition to what is kept for the user and domain history settings. The default is 100. • Days of User History: The maximum number of daily records of user group history you want to store in the database. The default is 180.
Database Concepts Setup configures the SRM SQL Server database maintenance task as follows: • Backup — Daily full backup of the SRM database to the default MSSQL backup directory (for example, Mssql\Backup). — No transaction log backups — Truncate log on checkpoint option set — Backups are retained for one week • Statistics Update — Daily statistics update. • Database Consistency Checking — Daily database consistency checking.
Database Concepts If you want to let the installation program create and configure your SRM SQL Server database, see section “Prepare SQL Server for SRM” in Chapter 2 for the pre-installation requirements. When SRM creates and configures an SQL Server database, separate devices are created for the data and transaction log. These devices are created in the same location as the master device.
Database Concepts id – selected. Use ANSI quoted identifiers - not selected. Use ANSI nulls, padding, and warnings - not selected. NOTE: Modifying any data source settings after the SRM installation finishes will result in unpredictable behavior. Optional configurations you may want to define include: • Define the database maintenance configuration. SRM’s maintenance task is called SRM Maint SRMDB_SRM server computer name and by default runs daily at 1:15 a.m.
Database Concepts • Access is granted using sp_grantlogin with SQL Server 7.0. When the access is granted, an SQL Server login is created for the SRM Service User Account. The name of this login depends on the SQL Server’s default domain, and the domain of the Service User Account. (You can install across domains, provided there is a one-way trust).
B Post-Installation Reference Uninstalling SRM To uninstall SRM, run Setup from the SRM CD. When you uninstall an SRM Server, you are asked if you want to keep the database. Keeping the current database allows you to add the SRM Server back onto the computer and use the data stored in this database. NOTE: Before uninstalling an SRM Server, be sure to register any Agents it is monitoring with another SRM Server to ensure continued data collection. To uninstall SRM: 1. Insert the SRM CD into the CD-ROM.
Post-Installation Reference 5. Click the HELP button at the bottom of any remote installation dialog box for more information. Starting SRM Use one of these methods to start SRM: 1. If you have installed the Web Browser shortcut, go to Start > Programs > Storage Resource Manager. 2.
Post-Installation Reference Starting the SRM Process Manager Service If an invalid password was entered or if there was an incomplete domain synchronization, you might have to start the Process Manager manually. To start the SRM Process Manager service: 1. For Windows NT, go to Start > Settings > Control Panel and choose Services. or For Windows 2000, go to Start > Settings > Control Panel > Administrative Tools. 2. Search for Storage Resource Manager Service. 3.
Post-Installation Reference Verifying SRM’s Application Configuration Settings When SRM is installed, the application configuration settings are inherited from the default Website configuration. To verify that these are properly set for SRM, check that: • The server-side script debugging is not enabled. • The default ASP script language is VBScript. You can perform this procedure on any computer on your network that has access to the SRM Server computer.
Post-Installation Reference 8. In the Debugging Flags area, ensure that both Enable ASP server-side script debugging and Enable ASP client-side script debugging check boxes are not selected. If they are selected, clear their check boxes. 9. Choose the App Options tab. Ensure that VBScript is entered in the Default ASP language field. If not, enter it. 10. Click OK in the Application Configuration dialog box and the StorageResourceManager Properties dialog box.
C SRM Troubleshooting Guide Introduction This appendix is designed to help anyone who will be installing and/or supporting SRM to determine and debug any encountered problems. SRM Server Installation SRM Server consists of the following actions: • Checking for prerequisite products and settings. • Creating the SRM Database. • Configuring SQL Server Security to allow SRM Service account access to the SRM Database. • Creating the SRM Service Login Account (default SRMSvcUser) on the SRM Server.
SRM Troubleshooting Guide SRM Directories and Log Files The Installation process creates “SRM”, “StorageResourceManager”, and “SRMScanWeb” virtual directories in IIS if these options are selected. Log files are located in the “\Program files\Storage Resource Manager” directory and are useful for determining why an install has failed: • SRMAgentInstall.log • Install.log • SRMServerInstall.log • SRMCoreinstall.log • SRMProcMgrInstall.log • SRMShortcutInstall.log • Srm_PostMortem.
SRM Troubleshooting Guide SQL Server Name Error Sometimes when you are running the prerequisite check or the installation, when you specify the SQL Server name, an error message displays stating that you have specified an incorrect account name. It also tells you to go back and correct the account name or reenter it. This is an incorrect error, because you have not yet been prompted for a SQL Server account name. The problem is actually that the computer cannot resolve the SQL Server name you have entered.
SRM Troubleshooting Guide This message displays if the account you are logged into does not have access to the \Program Files\Storage Resource Manager\Kits\Config\ directory on the SRM Server where the install scripts are kept. By default, this directory is shared as SRMInstallConfigs and is configured to allow only Local Administrators access. If your login account is not a member of the Local Admin group on the SRM Server, you will not be able to create or modify install scripts.
SRM Troubleshooting Guide Install Fails Immediately With Permission Error The account you specified when running the install script in the GUI does not have Local Administrator rights on the agent. Rerun the job and be sure to specify an account with these rights. Install Fails When You Select Submit After Inputting All Install Information The SRM Server Service Account is not a member of the Local Administrators group on the SRM Server machine.
SRM Troubleshooting Guide Registration Failed The registration failed due to an invalid domain was entered for the SRM Service Account. NOTE: When prompted for the SRM Service account domain during the UNIX Agent install, or when registering the UNIX Agent with a different SRM Server. You have the option to press Enter without entering anything, taking the “default” domain. If the registration fails, retry the registration and enter the service account domain. Do NOT take the default this second time.
SRM Troubleshooting Guide If the service is running, open Task Manager and sort on Image Name. Look for SRProcmgr.exe. Below it should be SRMServer.exe. If SRMServer.exe is not there, or if it is there briefly then disappears, and continues to do this, check the following registry key using REGEDT32: HKL-Software-HighGround-SRManager--Server-Options Once you’ve highlighted this OPTIONS key, from the menu bar at the top of the window, select Security then select Permissions.
SRM Troubleshooting Guide Cruft Data Data that no longer exists and is showing in grayed out boxes in the UI, does not get removed automatically as it should. There is a setting under Options-Report Sizes where you can specify how long “old” resources should be kept. There is a Maintenance job that continuously runs within the SRM Server that monitors this and removes data from the database. If this time has passed and the data is still in the database, check the SRMSCHED.
SRM Troubleshooting Guide The SRM Service Account MUST be a member of the Domain Users group in the domain in which it exists. It cannot be a local account on the SRM Server machine. For example, if the SRM Server machine name is PIPER and it is a member of the domain ENGINEERING, the service account CANNOT be created as PIPER\SRMSVCUSER. The service account must be in the ENGINEERING domain, or some other master domain.
SRM Troubleshooting Guide Figure C–1: StorageResourceManger Properties window 3. Under the Application settings field, there MUST be an entry next to “Name:” and the option “Run in separate memory space” must be checked. This will cause the Web page to run using MTX. To check the settings in MTX: 1. Select Microsoft Transaction Server from the MMC and drill down into Packages Installed. 2. Right click on the appropriate package and select Properties.
SRM Troubleshooting Guide Figure C–2: IIS Properties window 3. Click the Identity tab. NOTE: This is the account that will be used to access the SRM database via the Web UI. By default this is configured as the SRM Service account. If it is changed, the new account MUST be granted SQL Server access as noted above. If the Service account password were changed, it would have to be changed here or the UI will fail.
SRM Troubleshooting Guide The user account that is being used to access the SRM UI via a Web browser must have access to the SRM Web directory: \Inetpub\wwwroot\StorageResourceManager\ and all of its subdirectories. By default EVERYONE has Full Access to this directory. If this is removed, individual access will need to be granted. An Access Denied browser error is returned to you if you do not have access. The Options tab on the SRM UI is controlled by the login account of the user accessing the SRM Web.
SRM Troubleshooting Guide SRM Debugging Tools SRM automatically installs debugging tools into the \Program Files\Storage Resource Manger\Internal\ directory. Not all of the files in this directory are for debugging purposes. The following is a description of the ones that are. tst_agentscan.exe - NT Agents Only This program will simulate an SRM scan of the type specified, without updating the database. It can be run both locally (from the agent itself) and remotely (from the SRM Server). 1.
SRM Troubleshooting Guide • The security key in the Agent registry is not configured correctly. • The agent machine is down. • There are name resolution issues. • The SRM service on the Agent is not started. • There are connectivity issues. If you get a DWORD error, this usually means there was a security failure on the agent when trying to authenticate the requesting user.
SRM Troubleshooting Guide tst_srmcmd.exe This program will perform a number of functions on the SRM Server machine, including enabling/disabling tracing and checking the scheduler and listener. 1. Copy the program to the Program Files\Storage Resource Manager\ directory. It uses DLLs that are located here. 2. Enter the following at the command prompt to list all options: tst_srmcmd /? The four different formats for this program are: • -cT+ — Enables server-side tracing.
SRM Troubleshooting Guide SRM Traces, Logs, and Dumps The following procedures are used to configure traces, logs, and dumps on the SRM Server: SRM Server Trace 1. To enable the SRM Server trace and put its output into a file (continuously updated), open a Command Prompt (DOS window) on the NT server, and type the following: cd /d drive letter:\Program Files\Storage Resource Manager 2. Import the following registry keys from the \internal\ directory SRMServerTraceRegistry.txt.
SRM Troubleshooting Guide SRM NT Agent Trace The SRM Agent has tracing, as well as the SRM Server. All that gets logged to the trace file is the share information. Perform the following step to enable tracing. 1. Import the following files from \Program Files\Storage Resource Manger\Internal\ into the registry via REGEDIT: • SRMAgentTrace.txt • SRMAgentTraceEnable.
SRM Troubleshooting Guide Tracing can be controlled with a number of options and directives, as shown in Table C–1: Table C–1: UNIX Tracing Options and Directives Option Default How to change Trace file directory .
SRM Troubleshooting Guide • NICE • TRACEDIR • TRACESEV • DUMP_REPORTS
SRM Troubleshooting Guide If SRM does not open the pipe in this amount of time, OEMSCANIO will read the agent’s data, and write it to a new temporary file (by default with the FILE_FLAG_DELETE_ON_CLOSE attribute set). It will then create a new OEMSCANIO process which is set to read this file, and will continue to wait for SRM to pick up the scan posting. Once the data is written to the file and the new process is started, the CGI process will terminate.
SRM Troubleshooting Guide IIS Log Since the SRM product uses IIS extensively, it is also useful to consult the IIS log, especially if: • UNIX agent registration fails • A user encounters a problem when accessing an SRM GUI page IIS creates its log at: %WINNT%\system32\LogFiles\W3SVC1\exYYMMDD.LOG Log entries contain the following information: • Time • Calling IP address • HTTP method (GET, PUT) • URL invoked • Status of operation Dr.
SRM Troubleshooting Guide How Can I Tell if a Scan is Running? SRM scanning is a complex process. Note that for UNIX agents, there are two types of scans, “Computer” and “Partition” (sometimes called “file”) scans. These are run from a schedule, based on groups of Computers and Partitions. When a group is scanned, SRM can scan up to ten (10) group members at one time. To determine which SRM Groups are currently scanning, you can look at the Web page SRMServerName/StorageResourceManager/Scans/Srmsched.
SRM Troubleshooting Guide Then it is supposed to report the scan failure to SRM, which in turn should write it to the NT Event log. NOTE: When a program terminates abnormally, it is not always possible to cleanly catch the exception and clean everything up. In any case, SRM will eventually be given a “timeout” status to declare that the scan failed.
SRM Troubleshooting Guide “Partition Could not be Scanned,” “Insufficient Virtual Memory” or “Paging Space Exhausted (SIGDANGER)” The Unix agent requires sufficient virtual memory to complete its scans, notably Partition (file) scans. Virtual memory consists of RAM and Swap (also known as Paging) space. The amount of virtual memory necessary is dependent on many factors, including the number of directory levels and the number of managed points.
SRM Troubleshooting Guide “Partition Could not be Scanned,” “Tree Scan Failed” The Partition File scan on UNIX could not complete for some reason. Often this is due to problems in the UNIX file system, and indicates a fsck should be run on the file system to repair damage. Consult the trace file created by the scan under /usr/srmagent/trace for this scan for more details on why the scan failed.
SRM Troubleshooting Guide The number of concurrent scans can be adjusted in the agentconfig file with directive “MAX_CONC_FILE_SCANS.” Why aren’t CD-ROMs or Mounted NFS Partitions Scanned? The SRM Unix agent only scans local, “standard” file systems. In both these cases, it might be useful to display that the partitions are available, but it does not make sense to scan their files (especially on NFS, it could cause network performance problems).
SRM Troubleshooting Guide “Computer Could not be Scanned,” “Scan Time Exhausted.” The UNIX agent expects to be able to complete a computer scan in less than 10 minutes. For very large or old and slow systems, this may not be adequate, especially on AIX. The maximum value can be overridden via agentconfig file configuration directive COMPUTERSCAN_TIMER, with the value specified in seconds.
SRM Troubleshooting Guide If gdb (the gnu debugger) is present on the agent system, it is also possible to attach to the “hung” process. If the stack shows the following profile, the above described situation is occurring: #0 0xff1955fc in _read () #1 0x50028 in URLReadResult (sid=4, buf=0xffbef640 “”, len=1024) at urlio.c:425 #2 0x48fb4 in SendOutput (s=0xd2698) at srmagent.cpp:806 #3 0x47284 in main (argc=1, argv=0xffbefe04) at srmagent.
SRM Troubleshooting Guide SRM was unable to retrieve host information for hostname . Unable to locate host name or interpret the name as an IP address. • MessageId=18 SymbolicName=OEMSCAN_CONNECT_ERR SRM was unable to establish a connection to the UNIX agent listening on socket . The connect request failed with the following error . Unable to connect to the remote system.
SRM Troubleshooting Guide Called from get_InputReady method. The named pipe is created and available for use. • MessageId=4 SymbolicName=OEMSCAN_FROMPIPE_SET SRM UNIX output pipe is available. Called from get_OutputReady method. The named pipe is created and available for use. • MessageId=5 SymbolicName=OEMSCAN_TOPIPE_NRDY SRM UNIX input pipe is unavailable. Called from get_InputReady method. The pipe has not been created and is not ready. The WaitNamedPipe(pipe,1000) call failed.
SRM Troubleshooting Guide Output pipe has been requested for scan on . The get_OutputPathname method was called and was given this pipe name. • MessageId=15 SymbolicName=OEMSCAN_SUPPORTED scan on support input pipe and output pipe
SRM Troubleshooting Guide • MessageId=210 Main buffered - no connection to pipe , giving up. SRM never came back to pick up scan results, because SRM service was stopped. • MessageId=260 Scan to pipe - could not create buffer file for pipe - error Unable to create the temporary file to buffer data in. The value should provide a reason for lack of creation. This would probably be a disk space or permissions error.
SRM Troubleshooting Guide Table C–2: Error Messages (Continued) Message Text 100 Filters from pipe - WideCharToMultiByte returned error . 110 Filters from pipe - could not write to stdout - error . 120 Filters from pipe - too many “no data” errors from pipe , giving up. 130 Filters from pipe - could not read pipe - error . 140 Process parameters - parameter type is not known.
SRM Troubleshooting Guide Table C–2: Error Messages (Continued) Message Text 340 Main buffered - Could not read pipe - error . 350 Main buffered - Invalid parameters from pipe : . Messages Requiring Registry Key HKEY_LOCALMACHINE\Software\ Storeway\OEMScan\Log>0 • MessageId=360 Main buffered - buffered scan in file delivered to pipe . SRM is now reading the scan results that were put into .
SRM Troubleshooting Guide Messages Requiring Registry Key HKEY_LOCALMACHINE\Software\ Storeway\OEMScan\Log>2 • MessageId=500 Scan to pipe - Total read - left to read: . Traces the amount of data left to read from the pipe. • MessageId=510 Filters from pipe - No data seen on pipe . Didn’t receive any scan input from SRM yet • MessageId=250 Main buffered - to few arguments passed to start buffered process.
Index A access rights 7–2 accounts login 1–3, 1–4 SRMSvcUser 1–6, 2–8, 3–2, 7–4, A–1, A–6, A–7 authorized reseller, Compaq xvi B Brocade plug-in 6–2, 6–21 button names, convention defined xiii C Caution, symbol and definition xv command names, convention defined xiv Compaq authorized reseller xvi technical support xv website xvi Compaq HSG80 plug-in 6–2, 6–18 Compaq SmartArray plug-in 6–2, 6–20 configuring A–1 conventions button names, defined xiii command names, defined xiv dialog box names, defined xiii
Index SRMUser 2–10, 7–1 guidelines for a typical installation 2–6, A–5 unregister 5–7 upgrade 5–5 login accounts 1–3, 1–4 H M Help, obtaining xv MDAC 3–1 menu command sequences, convention defined xiv menu items, convention defined xiii Microsoft Data Access Components 3–1 Microsoft Internet Explorer_ 3–5 Microsoft Internet Information Server 3–1 modify installation settings 5–2 installed components 5–3 OpenVMS Agent 5–8 SQL Server 7.
Index P permissions 7–2 Plug-In Registration Wizard 6–4 plug-ins Brocade 6–2, 6–21 Compaq HSG80 6–2, 6–18 Compaq SmartArray 6–2, 6–20 defined 6–1 directories 6–2 Fibre Channel Switch 6–2 installation 6–3 NetWare 6–1, 6–2, 6–15 prerequisites 6–3 RAID 6–1, 6–2 registration 6–4 SAN Switch 6–1, 6–2 uninstall 6–4 prerequisite check program 2–1 R RAID plug-in 6–1, 6–2 register Linux Agent 4–28 OpenVMS Agent 4–31, 4–36, 4–38 plug-ins 6–4 saving settings 6–11 UNIX Agent 4–28 unmanaged objects 6–5 unregistering ma
Index managed partitions per computer A–2 managed partitions per user A–2 partition report size A–3 SRM size A–3 users A–2 SRM for OpenVMS Agent cluster configuration 4–36, 4–37 configuration 4–36 private configuration 4–36, 4–38 registration 4–36, 4–38 SRM for Windows NT installation components 4–2 SRM Maint SRM Server computer name_SRMDB task 2–7, A–3, A–4, A–6 SRM Process Manager Service monitoring B–3 starting B–3 stopping B–3 SRM Server hardware requirements 3–2 installation 4–4 required account infor
Index SRM Server 5–1 UNIX Agent 5–5 upgrading from SRM upgrade CD 4–3 from SRM web update kit 4–3 URLs, convention defined xiv user access determining 7–1 user input, convention defined xiv V verify DCOM enabled 2–2 prerequisites 2–1 W Warning symbol and definition xv websites Storage Resource Manager Enterprise Edition Compaq storage xvi Compaq technical support xv Windows 2000 workgroups 1–6 Windows 2000 Agent 3–2 hardware requirements 3–3 required account information 3–3 software requirements 3–2 Wi
