USER’S GUIDE Global Array Manager Transition Tool Server Software May 2003 First Edition ® DB15-000279-00
This document is preliminary. As such, it contains data derived from functional simulations and performance estimates. LSI Logic has not verified either the functional descriptions, or the electrical and mechanical specifications using production parts. This document contains proprietary information of LSI Logic Corporation. The information contained herein is not to be used by or disclosed to third parties without the express written permission of an officer of LSI Logic Corporation.
and memory included in the Product will (i) be free from defects in workmanship and materials, and (ii) substantially conform to the documentation or other specifications for the Product.
INCLUDING MAINTENANCE AND SUPPORT. LSI SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE WITH RESPECT TO THE PRODUCT AND ANY OTHER MATERIALS AND SERVICES, AND WITH RESPECT TO THE USE OF ANY OF THE FOREGOING. THE REMEDIES STATED IN THIS DOCUMENT CONSTITUTE CUSTOMER’S EXCLUSIVE REMEDIES AND LSI’S SOLE LIABILITY FOR BREACH OF THE LIMITED WARRANTIES SET FORTH HEREIN.
For a current list of our distributors, sales offices, and design resource centers, view our web page located at http://www.lsilogic.com/contacts/index.html v Copyright © 2001, 2003 by LSI Logic Corporation. All rights reserved.
Preface This installation guide explains how to install and use the Global Array Manager® Server Software. In addition, this document explains how to install and use SNMP, SANArray Manager (SAM), GAM TT Event Logging, creation of GAM TT Server diskettes, and GAM TT Server for Failover or Failback in MSCS.
Chapter 4, UnixWare, describes information about the following installation, verification, and startup of the GAM TT Server software for UnixWare 7.1. Chapter 5, Linux, describes installation, startup, and troubleshooting of the GAM TT Server software for the Linux operating system with the following distributions: Red Hat 7.2, 7.3, SuSE 7.3 Appendix A, SNMP Installation, Operation, and Definition, describes the installation of the SNMP agent including configuring traps, and device information.
Conventions Used in This Manual Throughout the manual, the following conventions are used to describe user interaction with the product: bold The user must enter the bold text exactly as shown. ↵ Press the Enter key. Enter Press the key labeled “Enter” (or “Delete”, etc.). File->Run Select the Run option from the pull-down menu activated when the File menu pad is selected. Note: viii Notes contain supplementary information that can have an effect on system performance.
Contents Chapter 1 Introduction 1.1 1.2 1.3 Overview 1-1 1.1.1 NetWare, Windows 2000, 2003, and XP 1-1 1.1.2 UnixWare 1-1 1.1.3 Linux 1-2 Global Array Manager Transition Tool Server Overview 1-2 1.2.1 GAM TT Server Components 1-2 1.2.2 Monitoring Functions 1-3 1.2.3 Management Functions 1-4 1.2.4 Configuration Functions 1-4 Requirements 1-4 1.3.1 Server Hardware and Software – NetWare 1-5 1.3.2 Server Hardware and Software – Windows 2000, 2003, or XP 1-5 1.3.
2.3.1 2.3.2 2.3.3 2.3.4 DMI Service Provider Mylex RAID Component Mylex DMI CI Management Information Optional DMI CI Parameters 2-4 2-5 2-5 2-6 Chapter 3 Windows 2000, 2003 and XP 3.1 Overview 3-1 3.2 Global Array Manager Transition Tool Server Software for Windows 2000, 2003, and XP 3-1 3.2.1 Installation Overview 3-1 3.2.2 Installing Global Array Manager Transition Tool Server Software 3-1 3.2.3 Running Global Array Manager Transition Tool Server 311 3.2.
Chapter 5 Linux 5.1 5.2 Overview 5-1 Global Array Manager Transition Tool Server Software for Linux 5-1 5.2.1 Installation Overview 5-1 5.2.2 Installing Global Array Manager Transition Tool Server Software 5-2 5.2.3 Editing GAMEVENT and GAMEVLOG 5-3 5.2.4 Running Global Array Manager Transition Tool Server 53 5.2.5 Troubleshooting Server Software Installation 5-4 5.2.6 Uninstalling the Server Software 5-5 Appendix A SNMP Installation, Operation, and Definition A.1 Introduction A-1 A.
A.7 A.8 A.6.5 Uninstalling gamagent Files A.6.6 Optional SNMP Parameters for Linux MIB Compilation and Definition File Creation MYLEXRAIDMIB Object Definitions A.8.1 Traps A.8.2 Controller Information Group A.8.3 Logical Drive Information Group A.8.4 Physical Device Information Group A.8.5 RAID Management Software Group A.8.6 Logical Drive Statistics Group A.8.7 Physical Drive Statistics Group A.8.8 Fault Management Cabinet Information Group A.8.9 RAID Event Information Group A.8.
Creating a GAM TT Server Installation Diskette C.1 Introduction C-1 C.1.1 When to Create a GAM TT Server Installation Diskette C-1 C.2 Creating a GAM TT Server Software Installation Diskette C-2 Appendix D Installation of GAM TT Server for Failover or Failback in MSCS D.1 Preparation D.2 Using Virtual Cluster IP Address D.3 Installing GAM TT Server for Failover or Failback in MSCS Contents Copyright © 2001, 2003 by LSI Logic Corporation. All rights reserved.
xiv Contents Copyright © 2001, 2003 by LSI Logic Corporation. All rights reserved.
Figures 1.1 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 C.1 D.1 GAM TT Server and GAM TT Client Interactions Loading the Installation Wizard Welcome Dialog Box Select Components to Install Sub-Components List Previous GAM TT Server Found Installation Summary Screen Error – PCI Driver Must Be Version 6.90-00 or Higher Installation Progress Display Modify Server Configuration File Dialog Box Enter Event Recipients Dialog Box Server Event Logging Dialog Box Directory Path Information for gamscm.
xvi Copyright © 2001, 2003 by LSI Logic Corporation. All rights reserved.
Tables A.1 A.2 A.3 A.4 A.5 A.6 A.7 A.8 A.9 A.10 A.11 A.12 C.
xviii Copyright © 2001, 2003 by LSI Logic Corporation. All rights reserved.
Chapter 1 Introduction 1.1 Overview This manual explains how to install the Global Array Manager Transition Tool (GAM TT)® Server software for several supported operating systems. This chapter describes: • GAM TT Server functions • GAM TT Server requirements under supported operating systems Global Array Manager Transition Tool Server software is delivered on the web (www.lsilogic.com), and is used to install GAM TT Server software on a server running a particular network operating system. Note: 1.
1.1.3 Linux Before installing the GAM TT Server for Linux on a MegaRAID or Mylex PCI controller, you must first download and install the MegaRAID or Mylex PCI operating system driver. You can get this from the appropriate web site (see Chapter 5, “Linux”). 1.2 Global Array Manager Transition Tool Server Overview Global Array Manager Transition Tool (GAM TT) Server Software is used to manage disk array subsystems attached to a MegaRAID or Mylex Disk Array Controller. 1.2.
Figure 1.1 GAM TT Server and GAM TT Client Interactions GAMTT/SAM Client mlxraid.mib SNMP Management Software Client DMI Management Software SNMP DMI MI Server GAMTTSERV GAMTTEVENT SNMP Main Agent Log File GAM TT Server API through TCP/IP DMI Service Provider SNMP GAMTTEVLOG GAMTTAGENT mdac.
1.2.3 Management Functions The GAM TT Server software executes the management instructions the GAM TT Client specifies. GAM TT Server software offers fault management, reliable messaging, and superior operating system support. GAM TT Client software manages or performs maintenance on individual disk arrays and drives (with the appropriate authentication), again through means of the graphical user interface. 1.2.
1.3.1 1.3.2 1.3.3 1.3.4 Server Hardware and Software – NetWare • A server running Novell® NetWare 5.1/6 • 10 Mbytes of free hard disk space on the SYS: volume • Properly installed and configured MegaRAID or Mylex Disk Array Controller with the appropriate NetWare drivers • (Optional) If SNMP participation is desired, SNMP support should be installed.
1-6 • Properly installed and configured MegaRAID or Mylex Disk Array Controller with the appropriate Linux drivers found on the web site to be used with the Software Kit (see Chapter 5, “Linux”). • TCP/IP must be installed • Inetd or Xinetd must be running • SNMP (Optional) Introduction Copyright © 2001, 2003 by LSI Logic Corporation. All rights reserved.
Chapter 2 NetWare 2.1 Overview This chapter describes installation, verification, and startup of the Global Array Manager Transition Tool Server software for Novell® NetWare. The software is provided on the web (www.lsilogic.com). Note: 2.2 2.2.1 This chapter assumes that the network administrator for this site will perform these installation procedures. Global Array Manager Transition Tool Server Software for NetWare 5.
Note: Do not type any extension. Type only ....\install. 2. The Global Array Manager Transition Tool Server software installation screen displays. – To install the GAM TT Server software, select Install. – To cancel the installation, select Exit. As the software is installed, the server’s AUTOEXEC.NCF file is updated to start the Global Array Manager Transition Tool Server application whenever the server runs this file. 3. Press the Enter key at the Update AUTOEXEC.NCF message. 4.
2.2.2.1 Loading Global Array Manager Transition Tool Server Manually The Global Array Manager Transition Tool Server can be loaded manually from the NetWare server console prompt by typing the following two commands: load gamserv ↵ load gamevent -h (repeat...) 2.2.2.
2.2.3 Troubleshooting Server Software Installation Problem: The message “Error in connecting selected server” is displayed or an error is encountered when trying to connect to a server. Check: Is the IP address correct? Check: Is the server software, GAMSERV.NLM, installed and loaded on the server(s)? Use the following NetWare console command to verify that the GAMSERV module is loaded: modules GAMSERV ↵ Check: Is the Ethernet connection good? Check: Is TCP/IP set up correctly? Try Ping to find the server.
Mylex DMI CI requires a compatible DMI Service Provider to the service provider of SmartDMI™ Service Provider SDK v1.20 for Netware from Smart Technology Enablers, Inc. You can use the SmartDMI™ SP from Smart Technology Enablers, Inc. From more information, visit the web site http://www.enablers.com. Note: 2.3.2 In order for SmartDMI™ SP to launch properly on Netware 6, choose to install the IPX protocol and to enable the Transaction Tracking System (TTS) when you install the operating system.
2.3.4 Optional DMI CI Parameters After the installation of the DMI CI subcomponent, you have the option to specify additional parameters, known as the GAM IPC Port and the Update Time Interval. The default IPC port number for the GAM TT Server driver and Mylex CI port is 43162; however, this number may be modified. The update time interval specifies the interval in seconds for the DMI CI to update the controller status, e.g. inserted or removed, to provide timely information.
Chapter 3 Windows 2000, 2003 and XP 3.1 Overview This chapter describes installation, verification, and startup of the Global Array Manager Transition Tool (GAM TT) Server software for Microsoft Windows 2000, 2003, and XP. The software is provided by downloading the files from http://www.lsilogic.com/GAMTT. Note: 3.2 3.2.1 This chapter assumes that the network administrator for this site will perform these installation procedures.
1. Make sure TCP/IP is installed and functioning properly. 2. Double-click Setup.exe. Global Array Manager Setup loads the installation wizard (Figure 3.1). Figure 3.1 Loading the Installation Wizard 3. After a few moments, the Welcome dialog box displays (Figure 3.2). After reading the Welcome information, click Next to proceed with the installation, or click Cancel to end the installation procedure and return to the menu. Figure 3.2 Welcome Dialog Box 4.
If you click No, you will not be allowed to continue GAM TT Server installation. The Select Components dialog box is displayed, as shown in Figure 3.3. At this point you select the component(s) you wish to install. Figure 3.3 Select Components to Install 5. To select Global Array Manager Transition Tool Server for installation, click the box to check the Global Array Manager Transition Tool Server option.
7. Click Change if you want to see the Select Sub-components screen (Figure 3.4). The Program Files are normally selected. DMI and/or SNMP may be selected or deselected as needed: – If you select DMI, Setup copies the DMI files to the server directory, but it does not configure the DMI files. Refer to Section 3.3, “DMI CI Manual Configuration for Windows,” and Section 3.3.6, “Optional DMI CI Parameters,” near the end of this section.
9. Click Next from the “Select Components” dialog box to continue with the installation. 10. Special Condition: GAM TT Server Installation If setup finds a previous installation of GAM TT Server software, the following message appears (Figure 3.5): Figure 3.5 Previous GAM TT Server Found Click OK to replace the existing GAM TT Server and GAM TT Driver with the new installation, OR Click Cancel to retain your existing GAM TT Server/GAM TT Driver installation.
Figure 3.6 Installation Summary Screen 12. Special Condition: Old PCI Controller Drivers If setup finds that an installed PCI driver for any of your Mylex PCI RAID Controllers is older than version 6.90-00, you will see a message of the following type1 (Figure 3.7): Figure 3.7 Error – PCI Driver Must Be Version 6.90-00 or Higher If you intend to use GAM TT Server only with Mylex External RAID Controllers, you should choose to continue installation by clicking OK. 1.
However, if you intend to use GAM TT Server with Mylex PCI RAID Controllers, your PCI Controller Drivers must be version 6.90-00 or higher in order to install and run GAM TT Server. Click Cancel, and setup will exit. After clicking Cancel, follow the instructions in the PCI Disk Array Controller Drivers Installation Guide and User Manual to update your PCI driver(s). Then rerun GAM TT Server installation as described herein. If the above Special Condition does not apply, installation continues.
Figure 3.9 Modify Server Configuration File Dialog Box If no existing configuration file is found, Setup creates one. Proceed to step 15. – If you select “Use the existing file without modification” and click Next, your existing configuration file will continue to be used. Skip ahead to step 16. – If you select “Modify the existing file” and click Next, your configuration file is changed to include features new to this version of GAM TT Server. Proceed to step 15.
Figure 3.10 Enter Event Recipients Dialog Box Note: Event notifications cannot be received by a client unless its IP address or node name is identified. You may include additional IP addresses or node names by editing the GAMSCM.INI (configuration file) later. See Appendix C, “Creating a GAM TT Server Installation Diskette.” Click Next. If you did not enter any IP addresses or node names in the Enter Event Recipients dialog box, a message appears asking if you want to continue.
Figure 3.11 Server Event Logging Dialog Box 16. The full path for the configuration file is identified for future reference (Figure 3.12). Figure 3.12 Directory Path Information for gamscm.ini File Click OK. 17. The Setup Complete dialog box displays (Figure 3.13). 3-10 Windows 2000, 2003 and XP Copyright © 2001, 2003 by LSI Logic Corporation. All rights reserved.
Figure 3.13 Setup Complete Setup has finished copying files to your computer. Click Finish. 18. Create a user account called gamroot. Setup of Global Array Manager Transition Tool Server is complete. 3.2.3 Running Global Array Manager Transition Tool Server The Global Array Manager Transition Tool Server runs on the server and delivers the following information to the Global Array Manager Transition Tool Client: • Monitors the controller(s) and disks in the server.
To verify that this service has started, go to Start->Settings->Control Panel->Administrative Tools->Services, then check under Name File, GAM TT Server, and Status to see if it has started. 3.2.4 Troubleshooting Server Software Installation Problem: The message “Error in connecting selected server” is displayed or an error is encountered when trying to connect to a server.
3.3.1 DMI Service Provider The DMI CI relies on the DMI Service Provider to report DMI information about Mylex RAID devices. Therefore, you must install and launch the appropriate DMI Service Provider before you use Mylex DMI CI. Mylex DMI CI requires a compatible DMI Service Provider to the service provider of SmartDMI™ Secure Service Provider SDK v1.0.30.2 for Win32 from Smart Technology Enablers, Inc. You can use the SmartDMI™ SP from Smart Technology Enablers, Inc.
3.3.3 DMI CI Manual Configuration DMI is selected in the sub-component dialog box during the Global Array Manager Transition Tool Server installation if the DMI application such as Intel LDCM was installed. The DMI subcomponent can also be installed by itself via the server installation utility. Note: When installation is complete, see Section 3.3.6, “Optional DMI CI Parameters,” page 3-15. Use the SRVCCFG.EXE utility to configure the DMI files. 1.
4. Reboot your system OR start the “MYLEXDMI” service through Windows Services Control to start the DMI CI. 3.3.4 Mylex RAID Component When the DMI CI starts, it checks to determine if the MIF database of the DMI SP contains the corresponding component. If the component is not there, MDACCI imports the component information from MDAC.MIF and create a component, called “Mylex RAID,” in the MIF database. Note: Be sure that mdacci.exe and the “Mylex RAID” component are consistent in the MIF database.
controller status, e.g. inserted or removed, to provide timely information. This is useful on a hot-plug or hot-swap enabled system. If not specified, the default value of 60 seconds is used. Note: The IPC Port number for the GAM TT Server driver and the Mylex CI port number must match for proper communication. Therefore, if either the GAM TT Server driver port number or the Mylex CI port number changes, be sure to change the other port number to match.
5. To specify update time interval parameter, add a DWORD value, “Update TimeInterval,” under “ExtraParameters”, then you can specify the value of the time interval, as done for the -t option in the NetWare DMI CI command line inSection 2.3.4, “Optional DMI CI Parameters,” page 2-6. DMI CI Manual Configuration for Windows Copyright © 2001, 2003 by LSI Logic Corporation. All rights reserved.
3-18 Windows 2000, 2003 and XP Copyright © 2001, 2003 by LSI Logic Corporation. All rights reserved.
Chapter 4 UnixWare 4.1 Overview This chapter describes information about the following installation, verification, and startup of the Global Array Manager Transition Tool (GAM TT) Server software for UnixWare 7.1. The software is provided by downloading the files from http://www.lsilogic.com/GAMTT. Note: 4.2 This chapter assumes that the network administrator for this site will perform these installation procedures. Global Array Manager Transition Tool Server Software for UnixWare 7.
2. Insert the GAM TT Server diskette for UnixWare in the file server’s diskette drive. 3. Type the following (match case exactly as shown): pkgadd -d diskette1 GAM ↵ 4. You are prompted to insert the diskette and confirm installation as shown: Insert diskette into Floppy Drive 1. Type [go] when ready. or [q] to quit: (default: go) To begin installation, type: go ↵ The files are copied and the Kernel is rebuilt. 5. Installation is complete. Modify the GAMEVENT and GAMEVLOG lines manually.
4.2.2 Running Global Array Manager Transition Tool Server The Global Array Manager Transition Tool Server runs on the server and delivers the following information to the Global Array Manager Transition Tool Client: • Monitors the controller(s) and disks in the server. • Manages the controller(s) and associated disk subsystems in the server. The installation of Global Array Manager Transition Tool Server for UnixWare causes the appropriate drivers to load automatically at system startup.
Problem: Global Array Manager Transition Tool Server does not load. Check: Do you have login rights to the root? Check: Did all of the server files load to the destination directory? Do you have sufficient disk space for the installation? If necessary, reinstall the software. 4.2.5 Uninstalling the Server Software To remove the Global Array Manager Transition Tool Server software, complete the following procedures: 1. Type the following command (match case exactly as shown): pkgrm GAM ↵ 2.
Chapter 5 Linux 5.1 Overview This chapter describes installation, startup, and troubleshooting of the Global Array Manager Transition Tool Server software for the Linux operating system with the following distributions: • Red Hat 7.2, 7.3 (external products support only 7.1) • SuSE 7.3 The software is provided by downloading the files from http://www.lsilogic.com/GAMTT. Note: This chapter assumes that the network administrator for this site will perform these installation procedures.
• Section 5.2.2, “Installing Global Array Manager Transition Tool Server Software” • Section 5.2.4, “Running Global Array Manager Transition Tool Server” • Section 5.2.5, “Troubleshooting Server Software Installation” • Section 5.2.6, “Uninstalling the Server Software” This process assumes that the network administrator for this site will perform this installation procedure. 5.2.
5.2.3 Editing GAMEVENT and GAMEVLOG The $EVENTLOGFILE and GAMEVENT files must be edited so that they will hold the correct host or IP address to direct the events to the desired client(s). 1. Access the GAM TT file for GAMEVENT, type: vi /etc/rc.d/init.d/gam 2. Edit gam (replace [-h host1] with an actual—your user—address) gamevent -h host1 & For example (remove the # symbol to enable the command line): gamevent -h 192.168.0.
3. Verify that all GAM TT Server components are gone: ps -A | grep gam 4. If you see several process IDs left behind, remove them by typing: kill -g gamdrvd If necessary, you can also remove process IDs individually by typing: kill -9 Note: It is not necessary to reboot in order to enable GAM TT when using Software Kit 5.x or higher. However, if you need to reboot for any other reason, go to step 5. 5. To restart the GAM TT Server, type: /etc/rc.d/init.d/gam start 5.2.
Problem: Global Array Manager Transition Tool Server does not load. Check: Do you have login rights to the root? Check: Did all of the server files load to the destination directory? Do you have sufficient disk space for the installation? If necessary, reinstall the software. 5.2.6 Uninstalling the Server Software 1. To query the rpm database for GAM TT, type: rpm -qa | grep gam 2. Locate the GAM TT file name within the list.
5-6 Linux Copyright © 2001, 2003 by LSI Logic Corporation. All rights reserved.
Appendix A SNMP Installation, Operation, and Definition A.1 Introduction The Global Array Manager Transition Tool Server includes a Simple Network Management Protocol (SNMP) subagent for the MegaRAID or Mylex RAID controller and connected storage devices. An SNMP-based management application (also known as an SNMP manager) can monitor and manage devices through SNMP subagents. An example of an SNMP management application is Hewlett-Packard’s Open View.
A.3 SNMP Installation for NetWare During installation of the Global Array Manager Transition Tool Server, the SNMP files were copied to their appropriate directory, as shown in Table A.1. The files can also be copied to the server directory from a workstation’s floppy disk drive (with the appropriate NetWare access rights to the server directory). Table A.1 NetWare SNMP File Operating system Agent filename Server directory NetWare GAMAGENT.NLM SYS:SYSTEM NetWare MLXRAID.
You must copy and edit TRAPTARG.CFG to direct the events to be logged into the etc/ directory. (See the traptarg.cfg file for more information.) Follow the steps below: 1. Copy TRAPTARG.CFG to this path: etc/traptarg.cfg 2. Edit the TRAPTARG.CFG file by adding either the logical (host) name, IP, or IPX address, which is directly below Protocol UDP or Protocol IPX. Note: Leave white space preceding the address name. Each address destination must be on a separate line.
A.3.2.1 About the NetWare SNMP Main Agent The GAMAGENT NLM assumes that SNMP main agent for NetWare servers (SNMP.NLM) is already installed on the server. The GAMAGENT NLM attempts to autoload the SNMP.NLM. If the SNMP.NLM file is not present, the agent does not load. The command to load the agent can be incorporated into the AUTOEXEC.NCF or other operating system startup files as well. A.3.
tus too frequently. If the time interval is too big, the CI may not be able to report controller changes in time. Therefore, be careful when changing this parameter. A.4 SNMP Installation for Windows 2000/2003, and XP The SNMP subagent is available on Windows 2000/2003/XP. The SNMP subagent files are: • GAMAGENT.DLL • MLXRAID.MIB During GAM TT Server installation, these files are copied to the same folder as the GAM TT Server. See Section 3.2.
A.4.2 Enable/Disable the SNMP Subagent for Windows After installing the SNMP subagent, you can enable it by enabling the SNMP service through Windows Service Control. When you install the SNMP Service, by default, it is enabled and it is auto-loaded after system boot. To disable the SNMP subagent, you can disable the Windows SNMP service through the Windows Service Control. However, in this way, you also disable other SNMP subagents.
“HKEY_LOCAL_MACHINE\SOFTWARE\Mylex\Global Array Manager\\Pathname” 3. To specify the AM IPC Port parameter, add a DWORD value, “GamIpcPort” under the key. Then, you can specify the GAM TT driver ipc port number. (See -p in the NetWare command line, as in Section A.3.3, “Optional SNMP Parameters for NetWare,” page A-4.) 4. To add the Update Time Interval parameter, add a DWORD value, “UpdateTimeInterval” under the key.
This ensures the proper communication between the SNMP subagent and the UnixWare SNMP peer agent. A.5.2 Enable/Disable SNMP Subagent To enable the SNMP subagent, you can uncomment the command line of “gamagent” in S99GAM in the folder of /etc/rc2.d/S99GAM. S99GAM is the script file, to auto-load GAM TT Server components during boot time, which is copied to your UnixWare system during GAM TT Server installation. By default, gamagent is disabled in S99GAM.
Note: The value of update time interval can affect the performance of the SNMP subagent. If the time interval is too small, the subagent uses much of the system’s resources by updating the status too frequently. If the time interval is too big, the subagent may not be able to report controller changes in time. Therefore, be careful when changing this parameter. A.6 SNMP Installation for Linux The SNMP Subagent for LINUX kernel 2.2 and 2.4 works with the UCDavis SNMP agent when compiled in the SMUX mode.
A.6.2 Example of /etc/rc.d/init.d/snmpd File The following is an example of the /etc/rc.d/init.d/snmpd file from Red Hat Linux which has been modified to use the above configuration: #!/bin/bash # ucd-snmp init file for snmpd # # chkconfig: - 50 50 # description: Simple Network Management Protocol (SNMP) Daemon # # processname: /usr/sbin/snmpd # config: /etc/snmp/snmpd.conf # config: /usr/share/snmp/snmpd.conf # pidfile: /var/run/snmpd # source function library #this is for the function of killproc etc. .
RETVAL=$? echo rm -f /var/lock/subsys/snmp return $RETVAL } reload () { start stop } restart () { start stop } condrestart () { [ -e /var/lock/subsys/snmpd ] && restart return 0 } case "$1" in start) start ;; stop) stop ;; restart) restart ;; reload) reload ;; condrestart) condrestart ;; status) status snmpd RETVAL=$? ;; *) echo $"Usage: $0 {start|stop|status|restart|condrestart|reload}" RETVAL=1 esac exit $RETVAL Use the following commands to create some symbolic links: ln -s /etc/rc.d/init.
ln -s /etc.rc.d/init.d/snmpd /etc/rc.d/rc5.d/S90snmpd S90snmpd must precede S99gamagent lexically in /etc/rc.d/rc3.d and /etc/rc.d/rc5.d so S90snmpd (UCD SNMP Agent) is run before S99gamagent (SNMP Subagent) at boot time. Note: A.6.3 This install procedure may change due to installing GAM TT driver/server in the same rpm package Installing the SNMP Subagent Files Before installing the SNMP Subagent (gamagent) files, install the GAM TT Server/Driver.
The S99gamagent files ensure that gamagent runs after snmpd and that gamdrvd starts at boot. The /usr/share/snmp/snmpd.conf configuration file must be edited for the local system environment. The file contains SNMP security options (man snmpd.conf) which are set to ‘public’ but may be changed. Change the sysLocation and sysContact parameters. Change the trapsink, trap2sink, and informsink IP addresses to the IP address of where SNMP traps are to be sent. Do NOT change the smuxpeer line.
Enter the command rpm –qa | grep gamagent to list gamagent’s full name for the next command. Enter the command rpm –e The main gamagent files are removed. If snmpd is still to be used, the /usr/share/snmp/snmpd.conf file must be recreated. The snmpd.conf is backed up in /usr/share/snmp before gamagent was removed for such an occasion. If it is necessary to modify snmpd.conf, see Section A.6.3, “Installing the SNMP Subagent Files,” page A-12. A.6.
Note: The value of update time interval can affect the performance of the SNMP subagent. If the time interval is too small, the subagent uses much of the system’s resources by updating the status too frequently. If the time interval is too big, the subagent may not be able to report controller changes in time. Therefore, be careful when changing this parameter. A.
A.8 A.8.1 MYLEXRAIDMIB Object Definitions Traps All traps are defined under this object according to Table A.3: Table A.
Table A.3 Traps and Trap Numbers (Cont.
Table A.3 Traps and Trap Numbers (Cont.
Table A.3 Traps and Trap Numbers (Cont.
Table A.3 Traps and Trap Numbers (Cont.
Table A.3 Traps and Trap Numbers (Cont.
Table A.3 Traps and Trap Numbers (Cont.
Table A.3 Traps and Trap Numbers (Cont.
Table A.3 Traps and Trap Numbers (Cont.
Table A.3 Traps and Trap Numbers (Cont.
Table A.3 Traps and Trap Numbers (Cont.
Table A.3 Traps and Trap Numbers (Cont.
A.8.2 Controller Information Group This object is used to find information about any or all of the controllers present in the system. Table A.4 Controller Information Group Table Object Data Type Description a2ControllerNumber 1.3.6.1.4.1.1608.1.1.1.2.1.1 Integer References a particular controller by its controller number a2OperationalState 1.3.6.1.4.1.1608.1.1.1.2.1.
Table A.4 Controller Information Group (Cont.) Table Object Data Type Description a2LogicalSectorSizeInBytes 1.3.6.1.4.1.1608.1.1.1.2.1.12 Integer The logical sector (block) size in bytes (Default: 512 bytes) (obsolete) a2PhysicalSectorSizeInBytes 1.3.6.1.4.1.1608.1.1.1.2.1.13 Integer The physical sector (block) size in bytes (Default: 512 bytes) (obsolete) a2CacheLineSizeInBytes 1.3.6.1.4.1.1608.1.1.1.2.1.14 Integer The cache line size in bytes a2CacheSizeInMb 1.3.6.1.4.1.1608.1.1.1.2.1.
Table A.4 Controller Information Group (Cont.) Table Object Data Type Description a2BusType 1.3.6.1.4.1.1608.1.1.1.2.1.18 Integer Numerical identification of controller’s bus type: Value 1 EISA 2 MCA 3 PCI 4 VESA 5 ISA 255 a2ControllerClass 1.3.6.1.4.1.1608.1.1.1.2.1.19 a2ControllerModel 1.3.6.1.4.1.1608.1.1.1.2.1.
Table A.4 Controller Information Group (Cont.
Table A.4 Controller Information Group (Cont.) Table Object Data Type Description (a2ControllerModel) (Integer) 105 DAC960MFL 106 DAC960MFF 107 DAC960FFX 108 DAC960FFX2 109 DACFFX2 255 Unknown a2SystemBusNumber 1.3.6.1.4.1.1608.1.1.1.2.1.21 Integer The system bus number for the controller. This value is supplied by the Operating System and may not be defined for all operating systems. a2SlotNumber 1.3.6.1.4.1.1608.1.1.1.2.1.
Table A.4 Controller Information Group (Cont.) Table Object Data Type Description a2FaultManagementType 1.3.6.1.4.1.1608.1.1.1.2.1.30 Integer The controller’s fault management type: Value Meaning 1 AEMI 2 OEM1 4 OEM2 8 OEM3 16 CONNER 32 SAFTE 64 SES 0 Not Present a2ArrayInformation 1.3.6.1.4.1.1608.1.1.1.2.1.31 Display String A displayable ASCII string containing the array information.
Table A.4 Controller Information Group (Cont.) Table Object Data Type Description a2DataWrittenToPhysicalDrivesInMb 1.3.6.1.4.1.1608.1.1.1.2.1.40 Integer The amount of data that was written to all physical drives in Mbytes a2StorageWorksCabinetStatusOn Channel0 1.3.6.1.4.1.1608.1.1.1.2.1.41 Integer StorageWorks cabinet status on channel 0 (obsolete) a2StorageWorksCabinetStatusOn Channel1 1.3.6.1.4.1.1608.1.1.1.2.1.42 a2StorageWorksCabinetStatusOn Channel2 1.3.6.1.4.1.1608.1.1.1.2.1.
Table A.4 Controller Information Group (Cont.) Table Object Data Type Description a2HostChannelNumber 1.3.6.1.4.1.1608.1.1.1.2.1.48 Integer Host Channel Number a2HostTargetId 1.3.6.1.4.1.1608.1.1.1.2.1.49 Integer Host Target ID (Sheet 8 of 8) Notes: • a2ControllerNumber is the index for any search operations against this object. • This is a READ-ONLY object. No SET operations are allowed. • A GET operation returns information about the object whose MIB ID is in the query.
A.8.3 Logical Drive Information Group This object is used to determine information about any or all the logical drives present in the system. Table A.5 Logical Drive Information Group Table Object Data Type Description a3ControllerNumber 1.3.6.1.4.1.1608.1.1.1.3.1.1 Integer References a particular controller by its controller number a3LogicalDriveNumber 1.3.6.1.4.1.1608.1.1.1.3.1.2 Integer The logical drive number a3OperationalState 1.3.6.1.4.1.1608.1.1.1.3.1.
Table A.5 Logical Drive Information Group (Cont.) Table Object Data Type Description a3SizeInMb 1.3.6.1.4.1.1608.1.1.1.3.1.6 Integer The logical drive capacity in Mbytes a3PhysicalSizeInMb 1.3.6.1.4.1.1608.1.1.1.3.1.7 Integer The total physical capacity used by this logical drive in Mbytes a3StripeSizeInBytes 1.3.6.1.4.1.1608.1.1.1.3.1.8 Integer The value of the stripe size in bytes, valid only for RAID levels 0, 5, and 6 a3PhysicalDriveMap 1.3.6.1.4.1.1608.1.1.1.3.1.
A.8.4 Physical Device Information Group This object is used to find information about any or all of the physical devices present in the system. Table A.6 Physical Device Information Group Table Object Data Type Description a4ControllerNumber 1.3.6.1.4.1.1608.1.1.1.4.1.1 Integer References a particular controller by its controller number a4ChannelNumber 1.3.6.1.4.1.1608.1.1.1.4.1.2 Integer SCSI channel number a4TargetId 1.3.6.1.4.1.1608.1.1.1.4.1.3 Integer SCSI target number a4Lun 1.3.6.1.4.
Table A.6 Physical Device Information Group (Cont.) Table Object Data Type Description a4ProductId 1.3.6.1.4.1.1608.1.1.1.4.1.7 Display String The SCSI device product ID. This is the product ID from the SCSI INQUIRY data. a4ProductRevisionLevel 1.3.6.1.4.1.1608.1.1.1.4.1.8 Display String The SCSI device product revision level. This is the revision level from the SCSI INQUIRY data. a4SizeInMb 1.3.6.1.4.1.1608.1.1.1.4.1.9 Integer The physical device capacity in Mbytes a4DeviceType Integer 1.3.6.
Table A.6 Physical Device Information Group (Cont.) Table Object Data Type Description a4ParityErrors Integer 1.3.6.1.4.1.1608.1.1.1.4.1.13 The number of parity errors that occurred a4MiscErrors Integer 1.3.6.1.4.1.1608.1.1.1.4.1.14 The number of miscellaneous errors that occurred a4ArrayList Display 1.3.6.1.4.1.1608.1.1.1.4.1.15 String The list of arrays to which this physical drive belongs. For example, A, B, etc. a4LogicalDriveList Integer 1.3.6.1.4.1.1608.1.1.1.4.1.
A.8.5 RAID Management Software Group This object contains the build date and version number for the Global Array Manager driver, Disk Array Controller device driver, and SNMP agent. Table A.7 RAID Management Software Group Table Object Data Type Description a5ManagementSoftwareRevision 1.3.6.1.4.1.1608.1.1.1.5.1.1 Display String A displayable string that shows the revision level of the SNMP agent a5ManagementSoftwareBuildDate 1.3.6.1.4.1.1608.1.1.1.5.1.
A.8.6 Logical Drive Statistics Group This object is used to determine statistics about all logical drives configured on a controller. Table A.8 Logical Drive Statistics Group Table Object Data Type Description a6ControllerNumber 1.3.6.1.4.1.1608.1.1.1.6.1.1 Integer References a particular controller by its controller number a6LogicalDriveNumber 1.3.6.1.4.1.1608.1.1.1.6.1.2 Integer The logical drive number a6ReadRequests 1.3.6.1.4.1.1608.1.1.1.6.1.
A.8.7 Physical Drive Statistics Group This object is used to determine statistics about all physical drives configured on a controller. Table A.9 Physical Drive Statistics Group Table Object Data Type Description a7ControllerNumber 1.3.6.1.4.1.1608.1.1.1.7.1.1 Integer References a particular controller by its controller number a7ChannelNumber 1.3.6.1.4.1.1608.1.1.1.7.1.2 Integer SCSI channel number a7TargetId 1.3.6.1.4.1.1608.1.1.1.7.1.3 Integer SCSI target number a7Lun 1.3.6.1.4.1.1608.1.1.
A.8.8 • The lowest address of a device (a7ControllerNumber/a7ScsiBusId/ a7ScsiTargetId) is defined as 0/0/0/0, followed by 0/0/0/1... 0/0/1/0, 0/0/1/1... 1/0/0/0, 1/0/0/1, and so on. • Controller numbers start at 0. Channel numbers start at 0. Target IDs start at 0. Fault Management Cabinet Information Group This object is used to obtain information about the fault management cabinet that is in use. Table A.
Table A.10 Fault Management Cabinet Information Group (Cont.) Table Object Data Type Description a8NumberOfHeatSensors 1.3.6.1.4.1.1608.1.1.1.8.1.9 Integer Number of heat sensors a8NumberOfDriveSlots 1.3.6.1.4.1.1608.1.1.1.8.1.10 Integer Number of drive slots a8NumberOfDoorLocks 1.3.6.1.4.1.1608.1.1.1.8.1.11 Integer Number of door locks a8NumberOfSpeakers 1.3.6.1.4.1.1608.1.1.1.8.1.12 Integer Number of speakers a8NumberOfFansCritical 1.3.6.1.4.1.1608.1.1.1.8.1.
• A.8.9 Controller numbers start at 0. Channel numbers start at 0. Target IDs start at 0. RAID Event Information Group This object is used to obtain information on events that occur for any or all of the controllers. This group’s information is used to send SNMP traps to the SNMP Manager workstation. Table A.11 RAID Event Information Group Table Object Data Type Description a9EventTableIndex 1.3.6.1.4.1.1608.1.1.1.9.1.1 Integer The index to the Event Table a9EventCode 1.3.6.1.4.1.1608.1.1.1.9.1.
• The value -1 in any of the object fields signifies that the field is not valid for the event being considered. • This is a READ-ONLY object. No SET operations are allowed. • A GET operation returns information about the object whose MIB ID is in the query. • A GETNEXT operation returns the object’s information which is next to the MIB ID given in the query. A.8.10 Battery Backup Unit Information Group This object is used to obtain information about the Battery Backup Unit (BBU). Table A.
Table A.12 Battery Backup Unit Information Group Table Object Data Type Description a10BatteryType 1.3.6.1.4.1.1608.1.1.1.10.1.3 Integer Battery type Value Meaning 0 Unknown 1 Nickel Cadmium 2 NiMh 3 Lithium Ion 254 No battery backup present a10CurrentPowerInHours 1.3.6.1.4.1.1608.1.1.1.10.1.4 Integer Current battery power in hours a10MaximumPowerInHours 1.3.6.1.4.1.1608.1.1.1.10.1.5 Integer Maximum battery power in hours a10ThresholdValueInHours 1.3.6.1.4.1.1608.1.1.1.10.1.
Appendix B GAMEVENT B.1 Introduction GAMEVENT refers to the concept of “Event Notification” in Global Array Manager. Event Notification involves the following: 1. The Global Array Manager Transition Tool Server (GAM TT Server) runs on the server computer to which the MegaRAID or Mylex controllers and third-party disk drives or enclosures are installed. When an informational event or error occurs, GAM TT Server generates an “event.
Note: The server and the client must have matching port numbers to generate inpro event logging activity. By default, the Linux client and server are configured to communicate correctly when using the root login. If you would like to use any login other than root for the GAM TT WINE Client, then you must modify the server and client event port numbers. This is due to a requirement by non-root users to use a port number above 1000.
each additional entry you need. Additional entries are read by the system as a continuous string of addresses. Correct spacing is important to avoid confusion of the server names. Note: The argument list is limited to 1028 bytes, allowing a practical maximum of about 50 event notification addresses and provides space for additional addresses. 5. Delete the comment marker “#” from the command line to enable event notification: LOAD GAMEVENT -h 10.97.49.189 -h fabd_test B.2.
B.3 B.3.1 Windows 2000, 2003, and XP Enabling Event Notification To modify or add event notification to GAM TT Clients, both local and remote, edit the GAMEVENT command line in the GAMSCM.INI file. 1. Open the GAMSCM.INI configuration file in a text editor. 2. Navigate to the section of the configuration file called GAMEVENT. gamevent.exe -h host1 -h host2 3. Replace host1 and host2 with a desired IP address or system name. For example: gamevent.exe -h 192.9.11.
B.3.2 Enabling a GAM TT Event Log File 1. Navigate to the section of the GAMSCM.INI file called GAMEVENT LOG. #gamevlog.exe -f .\gamserv\gamevlog.log -s 0 2. If necessary, delete the comment marker “#” from the command line to enable event logging to a file: gamevlog.exe -f .\gamserv\gamevlog.log -s 0 3. The file shown (gamevlog.log) is the default file name for the GAM TT event log. If you want to change this file name, replace “gamevlog” with your desired log file name. 4. The file path shown (.
B.3.4 GAMEVENT LOG Options The server sends event activity (EVENT LOG) to other hosts computers, which can be another server or a client system. Events can be written to a file and/or to your local terminal screen. There are two options associated with the GAMEVENT LOG, -f and -s. Usage: -f Note: File :: Sets the event log file name The event log file is created in the following directory: %SystemRoot%\system32\gamserv Note: -s Note: Option -s is valid for only Windows 2000.
3. Replace host1, host2, and host3 with a desired system name or IP address. For example: #gamevent -h 10.97.49.189 -h 10.97.49.190 -h fabd_test where: -h
sets address as a receiver of events. Address may be an IP address or a network system name. 4. Additional entries require that you extend the command line. Type -h then an IP address or system name, separated by one space, for each additional entry you need. The system reads additional entries as a continuous string of addresses.B.5 B.5.1 Linux Enabling Event Notification To enable event notification to GAM TT Clients, both local and remote, edit the GAMEVENT command line in the GAM TT file to remove the initial comment marker. To enable the Event Comment Line, follow these steps: 1. Log in as root. 2. Stop the GAM TT Server, type: /etc/rc.d/init.d/Gam stop 3. Using a text editor such as gnotebook+, open the GAM TT file located in the following path: /etc/rc.d/init.d/Gam 4. Navigate to the section of the file called GAMEVENT. 5.
8. Save the GAM TT file in your text editor. 9. Delete the comment marker “#” from the command line to enable event notification: gamevent -h 10.97.49.189 -h 10.97.49.190 -h fabd_test & B.5.2 Enable GAM TT Event Logging To enable event logging, follow these steps: 1. Navigate to the section of the file called GAMEVENT LOG. #gamevlog -f $EVENTLOGFILE & where: -f sets the event log file name 2.
B-10 GAMEVENT Copyright © 2001, 2003 by LSI Logic Corporation. All rights reserved.
Appendix C Creating a GAM TT Server Installation Diskette C.1 Introduction The Global Array Manager Transition Tool (GAM TT) Server Software package provides RAID Management functions for your MegaRAID or Mylex Disk Array Controller. You can create your own GAM TT Server installation diskette from the RAID Management Software Installation menu under Windows. See Table C.1 for information about GAM TT Server Installation Diskettes. C.1.1 When to Create a GAM TT Server Installation Diskette Table C.
C.2 Creating a GAM TT Server Software Installation Diskette Global Array Manager Transition Tool Server software can be downloaded from http://www.lsilogic.com/GAMTT. Once you download and unzip the GAM TT Server onto a Windows 2000/2003/XP operating system, use the following procedure to create a GAM TT Server installation diskette: 1. Double-click Gamsxx_xx-x. (where: x is the name and version number) 2. You are prompted with a DOS shell requesting that you insert a blank diskette. Figure C.
Appendix D Installation of GAM TT Server for Failover or Failback in MSCS D.1 Preparation When preparing to use Clustering on external products, you need to install GAM TT Server to utilize the failover or failback in Microsoft Clustering Service™ (MSCS). However, you must first complete the installation of Windows 2000 Advanced Server or Datacenter, Windows 2003 (32-bits), or Windows XP 32-bit on both servers. D.
– Group: Cluster Group – Possible Owners: “Both Nodes” – Resource Dependencies: Cluster IP Address – Service Name: gamscm – Startup Parameters: Leave blank 5. Bring the GAM Service resource online. 6. Go into GAM TT Client, and the following configuration appears on the virtual IP. Figure D.
