Installation Guide July 2009

Transcription

1 July 2009

2 About this guide Edition notice This edition applies to Version 4.0 of the Pivot3 RAIGE Operating System and to any subsequent releases until otherwise indicated in new editions. Notification of Use Intent This document contains information confidential and proprietary to Pivot3, Inc. and shall not be reproduced or transferred to other documents or disclosed to others or used for any purpose other than that for which it was obtained without the expressed written consent by Pivot3, Inc. Pivot3 EULA and Open Source Notices During the installation of all Pivot3 software components, a copy of the Pivot3 End User License Agreement will be placed in a subdirectory called Documentation located under the primary installation directory. If applicable, the Pivot3 Open Source Notices document will also be found in the Documentation subdirectory. Copyright Pivot3, Inc. July

3 Table of Contents About this guide... 2 Preface... 4 Who should read this guide...4 Related publications...4 Support information...4 Introduction to Pivot Components in a Pivot3 Array installation...6 Section 1: Connecting Pivot3 Appliances to the network... 9 Best practices: Hardware and network connections...9 Installing Pivot3 Appliances...10 Section 2: Installing application server support software Section 3: Setting up the RAIGE Director PC Configuring non DHCP storage networks...14 Installing RAIGE Director Software...16 Section 4: Creating a Pivot3 Array Best practices: Using RAIGE Director Software...17 Setting up an Array Administrator...17 Assigning Pivot3 Appliances and naming the Pivot3 Array...18 Assigning static IP addresses to Pivot3 Appliances...21 Method 1: Automatically generating IP addresses...23 Method 2: Manually entering IP addresses...25 Section 5: Re configuring the RAIGE Director PC Section 6: Creating Logical Volumes Section 7: Connecting standalone and hosted virtual servers to Logical Volumes Best practices: Optimizing Logical Volume size...43 Configuring a Logical Volume...43 Section 8: Managing hosted virtual servers Appendix A: Standalone server network configuration settings Appendix B: Switch and network configuration recommendations Appendix C: Management through SNMP Agents...56 Network Management System (NMS)...56 Community Strings...57 Pivot3 MIB...57 Appendix D: Using the RAIGE Director command line interface Appendix E: RAIGE Array state legend July

4 Preface Thank you for selecting Pivot3. This guide describes how to install Pivot3 RAIGE and Serverless Computing Arrays and deploy server applications on your array. It guides you through connecting a Pivot3 hardware appliance to the network, creating a Pivot3 Array, allocating storage for Logical Volumes, connecting standalone servers and hosted virtual servers to Logical Volumes, and creating virtual machines to run your applications. Who should read this guide The target audience for this publication is a system administrator installing a Pivot3 Array. In this guide, it is assumed that you have an understanding of the following: The operating system on which the standalone or hosted virtual servers connected to the Pivot3 Array will be installed Devices and user applications that a Pivot3 Array can use Communication protocols installed on your client and server machines Related publications Additional Pivot3 product documentation is available on the CD that came with your Pivot3 Appliance. Also, the following publications are available online at Pivot3 Serverless Computing Technology Overview Technical specifications Architectural and engineering specifications Support information Complete support information is available at July

5 Introduction to Pivot3 Pivot3 RAIGE (RAID across Gigabit Ethernet) technology is the first parallel RAID storage architecture delivering distributed RAID protection across, rather than within, individual devices. The RAIGE architecture brings powerful x86 appliances together into a single managed logical platform as an iscsi storage area network (SAN) and provides linear performance gains across all applications. Pivot3 offers the choice of RAIGE storage only networks or Serverless Computing server/storage networks to address diverse infrastructure needs. The Pivot3 Serverless Computing Architecture is the first and only iscsi SAN that simultaneously runs server applications on shared x86 hardware. The combined server/storage platform has no single point of failure and provides uninterrupted storage access and application recovery in the case of physical appliance failures. The RAIGE operating system (RAIGE OS) provides an intuitive appliance approach as it manages data distribution across Pivot3 Appliances to provide scalable availability, performance and capacity. The RAIGE OS runs on each appliance to aggregate the physical resources of the appliances, automatically load balance across the appliances and protect against component failures. Table 1: Pivot3 product specifications RAIGE Array Linear storage scaling Scales to 24 gigabits per second Scales to 12 parallel x86 RAID controllers Scales to 48 GB ECC DIMM RAM Linear scaling for up to 12 appliances Each Array scales up to 144TB Logical volumes scale to 144TB Supports up to 128 logical volumes and 128 initiators Serverless Computing Array Linear storage scaling Scales to 24 gigabits per second Scales to 24 parallel x86 RAID controllers Scales to 96 GB ECC DIMM RAM Linear server scaling Scales to 12 Quad core Xeon CPUs 4 dedicated LAN GigE ports per server 4 GB ECC DIMM RAM per server Linear scaling for up to 12 appliances Each RAIGE Array scales to 144TB Logical volumes scale to 144TB Supports up to 128 logical volumes and 4 initiators Both Pivot3 products provide advanced disk protection with RAID 5e and RAID 6e: With RAID 6e, up to 3 simultaneous disk failures will not affect data With RAID 5e, one disk failure will not affect data Both RAID 5e and 6e protect data in the case of an appliance failure July

6 As with any centralized resource it is important that the data stored be available and accessible. The Pivot3 storage centric approach for application environments characterized by high capacity needs and I/O intensive workloads offers higher performance, lower cost and higher availability than traditional alternatives. Components in a Pivot3 Array installation Pivot3 Appliances The term Pivot3 Appliances generically refers to both Databank and Cloudbank Appliances. Pivot3 Appliances are the hardware platform for the Pivot3 RAIGE Array and contain fully populated drive bays of 12 enterprise SATA disk drives. Databank Appliances are used in storage only environments. They are connected with standard Gigabit Ethernet networks, discovered automatically and assigned to a RAIGE Array. Each appliance contributes storage capacity, a CPU, RAM and shared bandwidth to the expandable array. Cloudbank Appliances are used in combined storage and server environments, known as Pivot3 Serverless Computing environments. In addition to features of the Databank Appliance, Cloudbank Appliances: Contain a second CPU, and additional RAM and NIC ports Include one optional embedded Windows Storage Server operating system. Users can use part or all of a Serverless Computing Array as a NAS share by running the Windows Storage Server on one or more Cloudbank Appliance in the array. All Windows Storage Server features are supported. Run a virtualization software layer that allows storage and server operating systems to run simultaneously on the same appliance. Have access to the entire shared capacity and bandwidth of the Serverless Computing Array through the hosted virtual server. Server instances can be started, stopped and managed as would any remote server. Pivot3 Software CD RAIGE Director Software is the configuration and management software for the Pivot3 Array. RAIGE Director has both a Java based GUI and a command line interface (CLI; see Appendix D). The software can run on any Windows desktop or server connected to the Pivot3 Array. RAIGE Connection Manager Software automates the process of creating network connections between the Pivot3 Array and a standalone or hosted virtual server. The software runs on each application server connected to the RAIGE Array and each hosted virtual server in Serverless Computing Array. RAIGE Multi Path I/O Software (not required for Serverless Computing) provides network fault tolerance and clustered network performance for the network connections between the application servers and the RAIGE Array. The software runs on each application server that acts as an iscsi initiator to the RAIGE Array. July

7 Network infrastructure Gigabit Ethernet Switches. Pivot3 Arrays provide a SAN using Gigabit Ethernet. It is required that two switches be used for SAN switch redundancy and that the SAN switches be segmented, either logically or physically from the local area network (LAN). Gigabit Ethernet NICs (not required for Serverless Computing). Application servers connected to the RAIGE Array require two Gigabit NIC ports for array connectivity. In addition, one or two more NIC ports are needed to connect the server to the LAN (for example, to access cameras or other devices on the network.) Virtualization software The virtualization software in the Serverless Computing Array runs the RAIGE OS in the first guest operating system. You can create a hosted virtual server (virtual machine) to add another server operating system as a guest. Hosted virtual servers running on a Cloudbank Appliance have access to the entire shared capacity and bandwidth of the underlying iscsi storage array. Server instances can be started, stopped and managed as would any remote server. Application server Application server refers to standalone servers attached to the RAIGE Array running applications that access the storage provided by the RAIGE Array. An example of such an application is a Network Video Recorder (NVR) capturing a video stream and recording it to the RAIGE Array. For a Serverless Computing Array utilizing Cloudbank Appliances, applications run on a hosted virtual server in the Cloudbank Appliance and do not require external application servers. This saves the costs that would be incurred for extra servers, racks, space and cooling. Virtual Machine recovery Pivot3 provides added server application reliability with a feature called Virtual Machine (VM) recovery that protects applications against server hardware failures. The VM recovery feature is enabled for each hosted virtual server using the RAIGE Director Software. In the case of a Cloudbank hardware failure, the hosted virtual server is automatically rebooted on a Cloudbank Appliance specified as a Recovery Cloudbank. The network, peripheral hardware, and storage connections are then dynamically re established. This recovery capability speeds the restoration of the application and access to the storage volumes, which are protected against appliance failures by the RAIGE OS. July

8 Unlike hardware based failover techniques, Pivot3 application recovery does not require dedicated physical server, storage or network hardware and is a standard feature included with Pivot3 Serverless Computing Arrays. July

9 Section 1: Connecting Pivot3 Appliances to the network This section describes how to connect your new Pivot3 Databank and Cloudbank hardware appliances to the network. In this section you will: Connect Pivot3 Appliances and Gigabit Ethernet switches to create a Pivot3 Array. Equipment you need for this section: Pivot3 Appliances An industry standard 19 data center rack Two Gigabit Ethernet switches Application servers each with two dedicated Gigabit Ethernet NICs to attach to the RAIGE Array (this equipment is not needed when setting up a Serverless Computing Array) IMPORTANT! Note the following installation requirements Pivot3 Appliances have two storage Network Interface Cards (NICs). Each storage NIC must be on a different subnet (no routers). Storage NIC 0 on all appliances in a Pivot3 Array must be on the same subnet, and Storage NIC 1 on all appliances must be on the same subnet. Each application server connected to a Pivot3 Array must have 2 one Gigabit Ethernet network interfaces dedicated to the storage networks (IP subnets) used by the Array. Use additional network interfaces for LAN access by each application server. Connecting the servers in this way provides maximum protection from network failures and optimal performance when using Pivot3 RAIGE Multi Path IO software. See Appendix A for recommended standalone application server network configuration settings. Gigabit Ethernet is required for switch connections. Refer to Appendix B for recommended switch configurations Best practices: Hardware and network connections Recommended best practices: Provide adequate cooling for optimal system resiliency. Appliances self detect 120VAC or 240VAC but 240 VAC is recommended for power efficiency. Use an uninterruptible power supply (UPS) to guard against brown outs and unanticipated power interruptions. Pivot3 Appliances contain two redundant power supplies that should be connected to separate AC power sources. Using two physically separate switches that each have a dedicated local subnet protects the Pivot3 Array from a single switch failure and provides the most predictable performance. If you experience multiple drive failures, replace one drive at a time, allowing the drive to rebuild completely before repairing the second drive. Continue replacing/rebuilding drives, one at a time, until they are all rebuilt. July

10 Installing Pivot3 Appliances 1. Follow the instructions in the Pivot3 Appliance Hardware Installation Guide to install the Pivot3 Appliances in a rack. 2. Follow your switch vendor s instructions to install the Gigabit Ethernet switches in the rack. 3. Connect the Appliances to the storage networks: a. Connect NIC 0 of all Appliances to the Gigabit Ethernet switch for Storage Network 0. b. Connect NIC 1 of all Appliances to the Gigabit Ethernet switch for Storage Network 1. NOTE: For simplicity, we refer to Storage Network 0 and Storage Network 1 throughout this guide. Your network naming conventions may vary. 4. If you are using Databank Appliances, connect the application servers to the storage networks: a. For each application server, connect one dedicated NIC to the Storage Network 0 switch. b. For each application server, connect the other dedicated NIC to the Storage Network 1 switch. c. Connect the application servers to the LAN. 5. Power up the appliances, switches, and application servers. Figure 1 1: Connecting Appliances to the iscsi SAN July

11 Section 2: Installing application server support software In this section, you will install the software needed on standalone application servers connected to Databank Appliances. This software is preinstalled on the hosted virtual servers in Cloudbank Appliances. In this section you will: Install Microsoft iscsi Initiator software Install Pivot3 RAIGE Multi path IO software Install Pivot3 RAIGE Connection Manager (supported Microsoft Windows versions only) To complete this section, you need the following: Name to be assigned to the iscsi initiator Administrator privileges on each standalone application server The Pivot3 RAIGE Software & Documentation CD contains software enhancements for the Microsoft Windows operating system. This software allows application servers to fully utilize the high availability and scalability features of Pivot3 Arrays. The following sections detail how to install this software and begin accessing Pivot3 Logical Volumes. You will need to complete this procedure for every standalone server you wish to connect to Pivot3 RAIGE Arrays. 1. If your standalone server is running Microsoft Windows Server 2008, skip this step and go to step 2. If your standalone server is running Microsoft Windows Server 2003, download and install the latest Microsoft iscsi Software Initiator package from Microsoft. When prompted for installation options, check all of the boxes, including Microsoft MPIO Multipathing Support for iscsi. July

12 Once the iscsi Initiator software is installed, you can change the default iscsi Initiator name by double clicking the Microsoft iscsi Initiator desktop icon or selecting Microsoft iscsi Initiator from the Windows Start menu. Click Change to enter a new iscsi Initiator name. 2. Install RAIGE Multi Path I/O. Copy the file DSM_SETUP_<release number>.exe from your Pivot3 software CD to the local drive of your standalone server and double click on the file or launch it directly from the CD. 3. Follow the step by step installation instructions. This installation may require a reboot. July

13 4. Install RAIGE Connection Manager. a. Copy the file RCM_SETUP.exe from the Pivot3 Software & Documentation CD to the local drive of your standalone server and double click on the file or launch it directly from the CD. b. Follow the step by step installation instructions. July

14 Section 3: Setting up the RAIGE Director PC This section explains how to configure the PC that will run the RAIGE Director Software to manage your storage network. In this section you will: Configure non DHCP storage networks, if necessary Install RAIGE Director Software on a PC connected to the Pivot3 Array To complete this section you need: A non dedicated PC running Microsoft Windows with IP connectivity to the Pivot3 Array Ethernet network (this should not be a hosted virtual server in a Cloudbank Appliance) The Pivot3 Software CD Configuring non DHCP storage networks If there are no DHCP servers on your storage networks, follow the steps in this section to configure the storage network interfaces on the PC running the RAIGE Director Software. Once completed, this procedure will enable the PC to discover Pivot3 Appliances on non DHCP storage networks. If one or more of the storage networks utilize a DHCP server, skip this step and proceed to the next section, Installing RAIGE Director Software. 1. Select Network Connections from the Windows Control Panel. 2. If there are two network interface connections (NIC) on the RAIGE Director PC, right click the Storage Network 1 icon and select Disable. You will re enable this NIC after the RAIGE Array is created. If your RAIGE Director PC has only one network interface connection, go to step 3. July

15 NOTE: For simplicity, we refer to Storage Network 0 and Storage Network 1 throughout this guide. Your network naming conventions may vary. 3. Right click the Storage Network 0 icon and select Properties. 4. On the General tab of the Storage Network 0 Properties dialog, scroll through the list under This connection uses the following items: and select Internet Protocol (TCP/IP). Then click Properties. July

16 5. On the General tab of the Internet Protocol (TCP/IP) Properties dialog, click the Obtain an IP address automatically radio button. On the Alternate Configuration tab, click the Automatic private IP address radio button. 6. Click OK to close the Internet Protocol (TCP/IP) Properties dialog. Click Close on the Storage Network 0 Properties dialog for the changes to take effect. Making the above changes instructs Windows to assign an APIPA (Automatic Private IP Address) to the interface for Storage Network 0. This change is required to enable the discovery of Pivot3 Appliances when creating a Pivot3 Array in the absence of a DHCP server on the storage networks. Installing RAIGE Director Software To install RAIGE Director: launch RD_SETUP_<software version>.exe, located in the RAIGE Director folder of your Pivot3 software CD, or copy RD_SETUP_<software version>.exe to the hard drive of the PC you will use to manage your Pivot3 Array and launch it. Follow the step by step instructions to complete the installation. July

17 Section 4: Creating a Pivot3 Array This section explains how to assign Pivot3 Appliances to a new Pivot3 Array, name the array and set IP addresses for appliances in the array. In this section you will: Perform operations in the Physical View of the RAIGE Director Software Discover the Pivot3 Appliances in the Pivot3 Array Create the Pivot3 Array Reconfigure the RAIGE Director PC (if needed) To complete this section, you need to know: The user name and password to be used for the Array Administrator, if applicable The names to be assigned to each Pivot3 Array The IP addressing information (IP addresses, subnet masks, and any default gateways) for the storage networks Best practices: Using RAIGE Director Software Recommended best practices: If using Administrator login credentials, configure a second Array Administrator as a backup. After an Array is created, use RAIGE Director Software to set up an additional Array Administrator. Select Manage Administrators from the Configuration menu to add a new administrator. When using any RAIGE Director Wizard, if you want to understand why the Next or Finish button is not enabled, mouse over the button to see a pop up explanation. Setting up an Array Administrator Use the following steps to create a RAIGE Array using RAIGE Director Software. 1. Launch RAIGE Director. You are prompted to enter a user name and password or disable login requirements. a. If you want to require Array Administrator login credentials, enter the user name and password and click Log In. b. If you do not want to require login credentials, click Disable Login Requirement and then click Log In. July

18 You can use the RAIGE Director Configuration menu to enable or disable Administrator login requirements at any time. When credentials are specified, only Arrays with the specified credentials are displayed in RAIGE Director. If login is disabled, only Arrays that do not have an Administrator are displayed in RAIGE Director. IMPORTANT! Retain administrator user names and passwords in a secure location. Should the user name and password get lost, contact Pivot3 to have your password reset. Management of the array will be delayed until this process is carried out. Assigning Pivot3 Appliances and naming the Pivot3 Array When RAIGE Director launches, it performs RAIGE discovery on the connected networks. This process gathers information about Pivot3 Appliances that are not currently part of a Pivot3 Array (unassigned) and Pivot3 Arrays authorized by the input Administrator user name and password. The first time RAIGE Director is launched, no appliances or arrays have been assigned, so you will see Discover RAIGE Products in the Quick Links of the Physical View as shown in the following figure: 1. Select any Cloudbank or Databank Appliance that is to be a member of the new array. This selection determines whether the Array will be made up of Databank Appliances or Cloudbank Appliances. July

19 2. Select Create Array from the File menu or Quick Links. This action starts the Array Wizard. 3. Select appliances that will become members of the Pivot3 Array from the Available Cloudbanks/Databanks table and click the up arrow to move them to the Selected Cloudbanks/Databanks table. Member appliances are combined into a virtual array, allowing them to be viewed and managed as a single, unified storage system. An appliance can be a member of only one Pivot3 Array. July

20 The following example shows that all of the available appliances were selected to become members of the array. 4. After all member appliances have been selected, click the Next button to continue. 5. Enter the name of the Pivot3 Array to be created. The array name can be up to 15 alphanumeric characters. 6. After entering the Array name, click Next to continue. July

21 Assigning static IP addresses to Pivot3 Appliances In the next step of the Array Wizard, static IP addresses are assigned to the Pivot3 Appliances. These IP addresses are used by the iscsi initiator on a standalone or hosted virtual server to connect to Pivot3 Logical Volumes and send I/O. Every NIC on all appliances must be assigned a unique static IP address. There are two methods for completing this step: Allow RAIGE Director to automatically generate and assign IP addresses for the member appliances. Manually enter the IP addresses to be assigned to each NIC in every appliance. Regardless of the method chosen, you must enter values in the Subnet Information table for each storage network: Subnet Mask by default is assigned the common Class C value of for each subnet. This value may be changed based on the IP address requirements of your storage networks. Network enter a unique value for each subnet. This is the value of the Network Portion of a full IP address after applying the Subnet Mask value. Default Gateway set only if a storage network is bridged to another IP subnet. In most configurations, this field will be left blank. NOTES: The IP Addresses for NIC 0 must all be on the Subnet defined by Subnet 0. The IP Addresses for NIC 1 must all be on the Subnet defined by Subnet 1. If you enter a Default Gateway, it is not necessary to specify the network. If you enter both Network and Default Gateway values, they must define the same Subnet. In the following example, Subnet 0 corresponds to Storage Network 0 and Subnet 1 corresponds to Storage Network 1. Both networks use the default Subnet Mask value. IP addresses that will be used on Storage Network 0 will be of the form x and therefore, the Network value assigned to Subnet 0 in the table is Likewise, the IP addresses for Storage Network 1 will be x and the Network value assigned to Subnet 1 is Because these storage networks are not bridged to any other networks, the Default Gateway is left blank for both. July

22 When the Subnet Information table is complete, the Auto Generate IP Addresses link becomes enabled. You can now choose the method for assigning IP addresses to the appliances. NOTE: A field with a yellow background indicates that input is required or the current value is incorrect. You can mouse over the field to display a message explaining why the value is incorrect. When all IP addresses have been entered, press the Enter key to close the cell editor and enable the Finish button. The Finish button remains disabled whenever an IP Address is being edited. July

23 Method 1: Automatically generating IP addresses This is the simplest method for generating IP addresses. 1. Choose the Auto Generate IP Addresses link. The following dialog is displayed: 2. Enter a value for the Start Address for each subnet. These values will be assigned to the associated NIC s in the first Pivot3 Appliance. RAIGE Director then increments the Host Portion of the Start Address for each subnet and sequentially assigns IP addresses to the remaining appliances. NOTE: Make sure you enter an IP Address that is unused on the Subnet. Check with your network administrator if your need assistance. 3. Click Apply. July

24 The results from auto generating IP addresses are shown in the Array Wizard Step 3 Set Static IP Address Paths display. 4. Once all IP addresses have been entered one of two things happens: a. If you have Administrator credentials configured and this is the first Pivot3 Array configured in RAIGE Director, the Next button is enabled. Click Next to continue to step 5, which is Administrator verification. b. If you do not have Administrator credentials configured or this is not the first Pivot3 Array configured in RAIGE Director, the Finish button is enabled. Click Finish to exit the Array Wizard and create the Pivot3 Array. This completes the Array Wizard for automatically generating IP addresses for Pivot3 Appliances. 5. Re enter the Array Administrator user name and password specified during RAIGE Director login. This final verification step of the Array Wizard is required only when adding the first Pivot3 Array. 6. After entering the administrator name and password, click Finish to create the Pivot3 Array. 7. Once the Pivot3 Array has been created, close RAIGE Director by selecting Exit from the File menu. July

25 Method 2: Manually entering IP addresses This method requires you to manually enter an IP address for every NIC for each Appliance. 1. Click in the IP address entry field for NIC 0 for the first Appliance and enter its IP address. Repeat this step for each NIC for every appliance until all IP addresses have been entered. 2. Press Enter after entering all IP addresses. NOTE: The IP Addresses for NIC 0 must all be on the Subnet defined by Subnet 0. The IP Addresses for NIC 1 must all be on the Subnet defined by Subnet Once all IP addresses have been entered one of two things happens: a. If you have Administrator credentials configured and this is the first Pivot3 Array configured in RAIGE Director, the Next button is enabled. Click Next to continue to step 4, which is Administrator verification. b. If you do not have Administrator credentials configured or this is not the first Pivot3 Array configured in RAIGE Director, the Finish button is enabled. Click Finish to exit the Array Wizard and create the Pivot3 Array. This completes the Array Wizard for manually entering IP addresses for Pivot3 Appliances. 4. Re enter the Array Administrator user name and password specified during RAIGE Director login. This final verification step of the Array Wizard is required only when adding the first Pivot3 Array. July

26 5. After entering the administrator name and password, click Finish to create the Pivot3 Array. 6. Once the Pivot3 Array has been created, close RAIGE Director by selecting Exit from the File menu. The Pivot3 Array creation process may take several minutes to complete. The amount of time varies depending on the number of Pivot3 Appliances. Once complete, RAIGE Director displays the Array. IMPORTANT! Use RAIGE Director to properly shut down a Pivot3 Array or any Pivot3 Appliance assigned to a Pivot3 Array before physically powering down the hardware. Failure to do so risks Array failure and data loss. July

27 Section 5: Re configuring the RAIGE Director PC Now that the Pivot3 Array has been created and the appliances in the array have been assigned static IP addresses, the RAIGE Director PC network interfaces that connect to the storage networks need to be configured to also use static IP addresses. RAIGE Director will communicate with the array using these new IP addresses. These will also later be used by the iscsi Initiator software to communicate with Pivot3 Logical Volumes. This procedure also establishes a standalone server connected to a Databank Appliance as both an application server and a RAIGE Director PC, if desired. In this section you will: Set a static IP address for the RAIGE Director PC Re enable Storage Network 1, if necessary To complete this section, you need to know: The values entered when the static IP addresses were assigned to the Pivot3 Appliance (that is, the Subnet mask and Default gateway, if applicable) 1. Select Network Connections from the Windows Control Panel. July

28 2. Right click the Storage Network 0 icon and select Properties. 3. On the General tab of the Storage Network 0 Properties dialog, scroll through the list under This connection uses the following items: and select Internet Protocol (TCP/IP). Then click Properties. July

29 4. On the General tab of the Internet Protocol (TCP/IP) Properties dialog, click the Use the following IP address radio button. Enter a unique IP address along with the Subnet 0 (Storage Network 0) values entered when the static IP addresses were assigned to the Appliance (that is, the Subnet mask and Default gateway (if needed)). 5. Click OK to close the Internet Protocol (TCP/IP) Properties dialog. Click Close on the Storage Network 0 Properties dialog for the changes to take effect. If the RAIGE Director PC has two network interface connections, continue with steps 6 through 10. Otherwise, this completes the re configuration of the RAIGE Director PC to enable it to communicate with the Pivot3 Array and, if desired, act as a standalone application server. July

30 6. Right click the Storage Network 1 icon and select Properties. 7. On the General tab of the Storage Network 1 Properties dialog, scroll through the list under This connection uses the following items: and select Internet Protocol (TCP/IP). Then click Properties. 8. On the General tab of the Internet Protocol (TCP/IP) Properties dialog, select the Use the following IP address radio button. Enter a unique IP address along with the Subnet 1 (Storage Network 1) values entered when the static IP addresses were assigned to the Appliance (that is, the Subnet mask and Default gateway (if needed)). July

31 9. Click OK to close the Internet Protocol (TCP/IP) Properties dialog. Click Close on the Storage Network 1 Properties dialog for the changes to take effect. 10. Right click the Storage Network 1 icon and select Enable. This completes the re configuration of the RAIGE Director PC to enable it to communicate with the Pivot3 Array and, if desired, act as a standalone application server. July

32 Section 6: Creating Logical Volumes This section explains how to use RAIGE Director Software to create a Logical Volume. It describes the available RAID protection levels and setting rebuild priority, capacity, and iscsi Initiator access to the volume. In this step you will: Perform operations in the Logical View of the RAIGE Director Software Create Logical Volumes Configure standalone and hosted virtual server access to the created Logical Volumes To complete this step, you will need to know the following information for each Logical Volume to be created: Name to be assigned RAID protection desired Usable capacity in gigabytes iscsi Initiator name that will be granted access CHAP Secret requirements Use the following procedure to create a new Logical Volume on a Pivot3 Array. 1. Launch RAIGE Director Software. If you configured Array Administrator credentials, respond to the prompt to enter the user name and password. These are the credentials assigned to the Array Administrator during the array creation process (see Section 4: Creating a Pivot3 Array ). After receiving the login information or upon launch if no login credentials were used, RAIGE Director performs RAIGE discovery on the networks to which the RAIGE Director is connected. If applicable, the user name and password are validated by the RAIGE Array and, if correct, RAIGE Director displays the Array in the Logical View as shown in the following example: July

33 2. To start the Create Logical Volume Wizard: a. Select the Array on which the Logical Volume is to be created. b. Select Create Logical Volume from the File menu or Quick Links. July

34 3. Assign a name and settings to the Logical Volume. Name the name of the Logical Volume. The name must be unique within the array. QoS (Quality of Service) this setting determines the rebuild priority of the Logical Volume versus other volumes. This setting only affects volumes that are fault tolerant (RAID levels 1e, 5, 5e, or 6e). RAID protection six RAID protection levels are provided to meet the data protection goals of each application: RAID 0 Striping with no parity. Data is not protected against failures. There is no protection capacity required for RAID 0. RAID 0 is a valid choice for single appliance arrays. RAID 1 Disk mirroring within the appliance. RAID 1 is a valid choice for single appliance arrays. RAID 1e Enhanced network mirroring. The protection capacity required for RAID 1e is 100% of the primary data. RAID 1e protects against the failure of any drive in the array. The e indicates enhanced RAID 1 since data is also protected if an entire appliance with all twelve drives fails. RAID 5 Striping with parity. RAID 5 is a valid choice for single appliance arrays. RAID 5e Enhanced striping with parity. This is a valid choice for arrays with 3 or more appliances. RAID 5e protects against one failure which can be either a drive failure or an appliance failure. The e indicates the enhanced RAID 5 protection for all twelve drives in the appliance July

35 RAID 6e Enhanced striping with disk parity. This is a valid choice for arrays with 3 or more appliances. RAID 6e protects against three simultaneous disk failures. The e indicates enhanced RAID 6 since data is also protected against a simultaneous failure of one drive and an entire appliance with all twelve drives. NOTE: For applications that require the highest availability, use RAID 1e, RAID 5e or RAID 6e. Capacity the amount of usable storage for the Logical Volume. The minimum capacity for a Logical Volume is 1GB and must be specified in 1GB increments. Clicking the Autogenerate link automatically populates the Capacity field with the maximum usable capacity (in gigabytes) for a Logical Volume based on the specified RAID level. Changing the RAID Level invalidates the current setting because the RAID overhead required changes. If you change the RAID Level, simply click Auto generate again to determine the new maximum capacity. NOTE: The usable capacity of a Logical Volume can be dynamically expanded after it has been created by selecting the Logical Volume in the RAIGE Director Logical View and then selecting Dynamic Capacity Expansion from the Edit menu. Enable CHAP CHAP is an optional security mechanism that allows network entities to perform additional authentication. If this box is checked, iscsi initiators must provide the CHAP secret when accessing the Logical Volume. If not checked no Initiator is allowed to specify a CHAP Secret. The following example shows the settings for the first Logical Volume, which is named DataVolume 2, has a high priority for rebuild operations, 5000GB capacity, RAID 6e fault tolerance and no CHAP authentication required. July

36 After entering the name and settings, click Next to continue. RAIGE Director validates that the Logical Volume can be created with the specified RAID Level and capacity. If there is insufficient capacity on the Array to create the Logical Volume, an error message is displayed. Dismiss the error message and make the changes necessary to create the Logical Volume. 4. The Logical Volume Wizard Step 2 allows you to specify an iscsi initiator. You can configure the iscsi initiator now or after the Logical Volume is created. Pivot3 Logical Volumes are accessed by standalone and hosted virtual servers using the iscsi protocol. These servers must have an iscsi initiator installed in order to perform I/O to the Logical Volumes (see Section 2: Installing application server support software ). An iscsi initiator has an associated initiator name, which must be unique for the initiator on each server. The iscsi initiator name is the key that grants access to the Logical Volumes. NOTE: RAIGE Director allows you to enter the initiator name using uppercase and lowercase letters. Some host software iscsi utilities used to configure the iscsi initiator display only lowercase letters and also automatically convert any input uppercase letters to lowercase. All iscsi names are converted to lowercase internally. Therefore APPSERVER, appserver, and ApPsErVeR are all considered to be the same name. The Specify Initiator dialog allows you to add the initiator name and set its access rights. Initiator access can be one of the following: None Specifies that the Initiator is a member of the associated Volume's Access Control List, but is not currently allowed access to the Logical Volume. Read Only Specifies that the Initiator can only read from the Logical Volume. Read/Write Specifies that the Initiator can both read from and write to the Logical Volume. Enter an iscsi initiator name and click Finish to continue, or click Next to configure the initiator later. July

37 In this example, the iscsi initiator named Initiator1 is granted read and write access to the volume. The CHAP Secret value was generated automatically through the Auto generate option. NOTES: The CHAP Secret value is displayed only when first generated, so you should save the value for future reference. You can change or delete the CHAP Secret later if desired. Only one Initiator can be assigned to each Logical Volume.\ July

38 5. The final step in creating a Logical Volume is to confirm its settings. As shown in this example, the Logical Volume s capacity is 4.882TB (5000GB); additional storage will be allocated from the array for RAID protection parity (fault tolerance) and sparing. Click Finish to create the Logical Volume. The storage capacity of the RAIGE Array has been allocated to Logical Volumes and is now ready for use by application servers. July

39 You can close RAIGE Director by selecting Exit from the File menu See Section 7: Connecting standalone and hosted virtual servers to Logical Volumes for instructions on connecting application servers to the Pivot3 Logical Volumes. July

40 Section 7: Connecting standalone and hosted virtual servers to Logical Volumes After running RAIGE Director, creating an array and configuring Logical Volumes, use the Pivot3 RAIGE Quick Connect Wizard to connect the standalone or hosted virtual servers to the Logical Volumes. 1. Start the RAIGE Quick Connect Wizard by selecting All Programs>Pivot3>RAIGE Connection Manager>RAIGE Quick Connect Wizard from the Start menu or launching the RAIGE Quick Connect Wizard shortcut from the desktop (if this option was selected during installation). The Quick Connect Wizard displays the currently configured iscsi initiator name. July

41 2. Select Logical Volumes to connect. The RAIGE Connection Manager discovers and displays the Logical Volumes that the initiator can access. By default, all Logical Volumes are selected to be connected. 3. Confirm the Logical Volumes to be connected and then select Next to continue. July

42 The RAIGE Connection Manager connects to the selected Logical Volumes. When complete, the wizard displays the Windows device names associated with the connected Logical Volumes. 4. Launch the Microsoft Disk Management tool (optional). The connected volumes appear as physical disks to Windows and can now be initialized and partitioned using the Disk Management utility. Click the Launch Disk Management checkbox to run the Disk Management tool after the Finish button is clicked. Click Finish to complete Logical Volume creation or click Cancel to cancel the operation. July

43 Best practices: Optimizing Logical Volume size Pivot3 solutions are designed for high capacity storage and I/O intensive applications, so it is important that Pivot3 Logical Volume sizes are optimized to meet the needs of those applications. Convert Logical Volumes to GPT disks before creating a partition. While this conversion is not necessary for volumes smaller than 2TB, it is still advisable to allow for future expansion. Once the volume has been partitioned, you cannot convert it to a GPT disk. Set the cluster (allocation unit) size to 64KB before formatting the NTFS file system. This size supports Logical Volumes up to 256TB, providing room for expansion and avoiding potential errors during volume expansion in the future. If a volume is extended past the maximum volume size for the associated cluster size, the partition is extended; however, the file system silently fails to expand. The net effect is unusable space allocated to a Logical Volume that cannot be recovered without an interruption of service or loss of data. Once a volume is formatted, it is not possible to adjust the cluster size without taking the volume offline and migrating the data, or utilizing third party tools such as Partition Magic to modify the cluster size. In other words, the initial format of the volume determines the maximum nondisruptive capacity expansion that is possible for that volume due a limit of clusters for NTFS. Because of this, it is important that you consider if the volume may need to be expanded in the future before formatting it and another reason to set all volume cluster sizes to 64KB. Configuring a Logical Volume These steps show how to convert a Pivot3 Logical Volume to a GPT disk and change the cluster size to 64KB as recommended. 1. Start the Microsoft Disk Management tool, if it is not running. Click the Windows Start menu and select Administrative Tools > Computer Management. In the console tree, click Disk Management. The Disk Management window displays your disks and volumes. 2. Right click the first disk volume and select Convert to GPT Disk. July

44 3. To create a new partition, right click the unallocated space on the disk where you want to create the partition, and then click New Partition. 4. Follow the prompts to set the partition type, size, and drive letter or path, clicking Next after each entry. July

45 5. On the Format Partition page, specify the formatting options that you want, and then click Next. Recommended values are: File system: NTFS Allocation unit size: 64KB Perform a quick format selected 6. On the Completing the New Partition Wizard page, verify the options that you selected are correct, and then click Finish. Disk Management creates the new partition and displays it in the appropriate Disk Management window. If you chose to format the partition in step 5, the format process now starts. July

46 Section 8: Managing hosted virtual servers Cloudbank Appliances include the software that allows you to run applications directly on the Appliance in a virtual environment. When you initialize this virtualization software, a guest or hosted virtual server operating system is created on the Cloudbank Appliance. Hosted virtual servers have access to the entire shared capacity and bandwidth of the underlying Pivot3 Array. These server instances can be started, stopped and managed as would any remote server. You can run one hosted virtual server on each Cloudbank Appliance. This eliminates the need for standalone physical servers. NOTE: RAIGE Director Software refers to a hosted virtual server as a virtual machine or VM and provides the management capabilities described in Table 8 1. Table 8 1: Hosted virtual server management features Boot VM Image Delete VM Reboot VM Image Shutdown VM Image Rename VM Manage Primary Cloudbank Manage Recovery Cloudbank Boots the operating system associated with the hosted virtual server or VM. When the VM operating system is not booted its state is Offline. Deletes the VM Image, the VM Volume and configuration information associated with the VM. The VM operating system must be shut down before the VM can be deleted. Reboots the operating system associated with the VM. The VM operating system attempts to shut down any executing applications before rebooting. Stops the operating system associated with the VM. The VM operating system attempts to shut down any executing applications before shutting down. Changes the name of the VM. Specifies the Cloudbank Appliance responsible for running the VM operating system and maintaining the VM environment. Specifies the Cloudbank Appliance responsible for VM recovery if the Primary Cloudbank fails. VM recovery dynamically re establishes network, peripheral hardware, and storage connections In the section you will: Select the Cloudbank Appliances for Virtual Machine (VM) operations Give the hosted virtual server a VM name To complete this section you will need to know: Which Cloudbank Appliance will run the hosted virtual server (or VM) operating system Which Cloudbank Appliance to use for VM recovery July

47 1. Launch RAIGE Director Software. In the RAIGE Director Logical View. Select a Serverless Computing Array (an array comprised of Cloudbank Appliances). 2. Select Create Virtual Machine from the Configuration menu Item or Quick Links to start the Create Virtual Machine Wizard. July

48 3. In the first window of the Create Virtual Machine Wizard, select the Virtual Machine Image containing the operating system to be executed in the hosted virtual server and click Next. From here, the Create Virtual Machine Wizard will display windows that allow you to configure the Primary Cloudbank, Recovery Cloudbank, Virtual Machine name and Virtual Machine Volume, as described in the following steps. 4. Select the Primary Cloudbank and click Next. This Cloudbank Appliance will run the hosted virtual server operating system and maintain the virtual machine environment. NOTE: VM recovery requires at least one available Cloudbank Appliance that is not designated as the Primary Cloudbank for a hosted virtual server. July

49 5. Select the Recovery Cloudbank and click Next. This Cloudbank Appliance will run the hosted virtual server if the Primary Cloudbank fails. This option will be displayed only if at least one Cloudbank Appliance that is not assigned as Primary for any hosted virtual server is available to be assigned as the Recovery Cloudbank. A Cloudbank can be designated as Recovery for any number of hosted virtual servers but is capable of executing only one hosted virtual server operating system. A Cloudbank cannot be designated both as a Primary and a Recovery Cloudbank. If no Cloudbank is designated as Recovery, the hosted virtual server will be unprotected if the Primary Cloudbank fails. 6. Enter a name for the Virtual Machine (hosted virtual server). The name must be unique within the scope of the Serverless Computing Array and is not case sensitive. The Virtual Machine name must be between 1 and 15 alphanumeric characters. July

50 7. Enter a name for the Virtual Machine Volume. This volume provides the storage required to host the hosted virtual server operating system and is automatically created as part of Virtual Machine creation. (See Section 6: Creating Logical Volumes for information on setting the values for the Virtual Machine Volume; the procedure is the same.) 8. If you want the operating system to boot after the hosted virtual server is successfully created, click the Boot after creation checkbox. If not selected, the hosted virtual server will be in the offline state after it is created. 9. A confirmation message now displays the Virtual Machine (hosted virtual server) settings. If all of the settings are acceptable, click Finish. July

51 10. RAIGE Director displays a window showing the progress of the Virtual Machine (hosted virtual server) creation process. Click Start to initiate the Virtual Machine creation or Close to return to the Create Virtual Machine Wizard. The hosted virtual server is now ready to execute your applications in the Serverless Computing Array. July

52 Appendix A: Standalone server network configuration settings This appendix provides network setting recommendations for optimal performance when using standalone servers with Databank Appliances in a RAIGE Array. Table A 1: Standalone server networking recommendations Recommendation Use multiple network interfaces and connect directly to Appliance switches Enable Flow Control on iscsi Initiator network interfaces Do not utilize jumbo frames Description Two dedicated network interfaces in each standalone server are required for RAIGE Array performance and availability. The network interfaces should be connected to the same redundant storage network switches as the Appliances. It is recommended that you enable symmetrical Ethernet Flow Control (generate and accept PAUSE frames) on each network interface used by the standalone server s iscsi Initiator that will communicate with the RAIGE Array. Do not configure jumbo frames on standalone server network interfaces that are attached to the same switches as Appliances, since Appliances do not support jumbo frames. July

53 Appendix B: Switch and network configuration recommendations This appendix provides switch selection and setting recommendations for optimal performance in Pivot3 Arrays. What type of network switch should I use with my iscsi SAN? You can use any standard Gigabit Ethernet switch. Your actual performance will be vendor and product implementation specific. It is a good idea to check with the switch manufacturer or your systems integrator regarding specific support capabilities. You should ask the following questions: Which switches do they support for your application and why do they recommend any particular switch over another? What are their requirements and recommendations for isolating SAN traffic from LAN traffic? Should you use a switch with cut through routing or store and forward? When comparing network switches, look at the latency numbers and the performance criteria for your application. For storage switching, low latency and data integrity are very important. Unlike other iscsi implementations, Pivot3 Arrays do not use or require jumbo frames, which eliminates the need to check that your Ethernet adapter or storage NIC, associated driver software, and storage subsystem can utilize jumbo frames. However, it is highly recommended that you verify that your Ethernet NIC or storage adapter, storage system, software drivers, and switches are compatible with each other and with the switch you are considering or already using. NOTE: While any Gigabit Ethernet switch is supported, higher performance switches will provide better throughput results. Table B 1: Recommended network switch specifications Specification Forwarding modes Latency Jumbo frame Network standards Notes Store and Forward Non blocking < 6us for 64 byte frames Not supported IEEE 802.3u 100BASE TX IEEE 802.3ab 1000BASE T IEEE 802.3z 1000BASE X IEEE 802.3x Flow Control IEEE 802.3ae 10000BASE X July

54 Table B 2: Networking Requirements Requirement Use the appropriate network cabling Use a switched, Gigabit Ethernet network Configure both network interfaces on each Appliance All devices within a subnet must be in the same broadcast domain/logical switch Appliance connectivity to the Internet is not required Disable jumbo frames support Untagged VLAN ports for Appliances Description Use Category 6 or Category 5e cables. Category 5 cables can be used if they adhere to the TIA/EIA TSB95 standard. Pivot3 Appliances only support UTP Gigabit Ethernet (1000BASE T) connections, and will require media converters for use with optical 1000BASE LX / 1000BASE SX switch ports. You must connect Appliances to a switched network and make sure that all network connections to the Appliances are set to Gigabit Ethernet speed (1000 Megabits per second). Appliances will not operate at link rates lower than Gigabit Ethernet speed. It is recommended that ports connecting Appliances be manually set to 1000/full duplex to avoid potential auto negotiation conflicts between switches and Appliances. Appliances require two Gigabit Ethernet connections to differing subnets/switches. Be sure to connect the same physical ports (top/bottom or left/right) to the same switch across all your Appliances (for instance, all left most ports should connect to switch 1 and all right most ports should connect to switch 2). Pivot3 Appliances are not link aggregation aware, and will not participate with 802.3ad link aggregation switch configurations. Each of the two network interfaces in an Appliance will be in a separate subnet (shared with corresponding network interfaces in other Appliances and standalone servers) and should be connected to different physical switches for high availability and the best performance. For Pivot3 Array creation, two active network connections to differing subnets/switches must be available on each Appliance. After the Array creation, the Appliances can operate suboptimally on a single switch or a single network interface if a switch or network interface failure occurs. If multiple switches are required to support a single subnet/broadcast domain of Array Appliances and standalone servers, ensure that the additional switches are in the same broadcast domain by utilizing trunking or backplane connections. Appliances do not require network connectivity to the Internet. It may be helpful for the RAIGE Director PC to have Internet access. Pivot3 Appliances do not support jumbo frames. If your switches are configurable, ensure that other devices on the switches cannot transmit jumbo frames by disabling jumbo frames support in the switches. Pivot3 Appliances do not participate with 802.1Q VLANs and will discard any VLAN tagged traffic. July

55 For optimal performance and availability, follow the recommendations in Table B 3, which also provides background information on some of the recommendations. Table B 3: Networking Recommendations Recommendation Disable Spanning Tree Protocol on iscsi ports Enable Flow Control on iscsi ports Disable unicast storm control on iscsi ports Segment non iscsi devices via VLANs Increase switch port buffers Description Pivot3 recommends disabling Spanning Tree Protocol (STP) on switch ports that connect end nodes (standalone server iscsi network interfaces or Appliance network interfaces), but Pivot3 Arrays will function with or without STP enabled. Enabling STP can introduce delays with NIC link establishments. If STP is required, it is recommended that an enhanced STP implementation that allows fast port state transitions (like Fast Start or Cisco PortFast) be used to reduce STP forwarding state transition delays. Enable symmetrical Ethernet Flow Control (generate and accept PAUSE frames) on each switch port that handles iscsi traffic. Appliances have Ethernet Flow Control enabled and perform best if switches are manually configured to utilize Flow Control. Standalone server network interfaces used by the iscsi Initiator should be configured to generate and accept Flow Control PAUSE frames. Some commodity switches do not allow for Flow Control configuration, but most will still honor and generate Flow Control PAUSE frames generated by iscsi devices. Disable unicast and broadcast/multicast storm controls on switches that handle iscsi traffic. Not all switches provide storm control functionality. If switches will be shared with non iscsi network devices, utilize VLANS to isolate iscsi traffic from other traffic. Appliances are not 802.1Q VLAN tag aware, so any VLANs created must be untagged to/from Appliances. Pivot3 does not recommend using a single VLAN ed switch for both Appliance interfaces since it degrades performance and introduces single points of failure. For optimal performance, utilize switches that allow the configuration of transmit buffer sizes. Transmit buffers of 256KB and larger for Appliance ports will provide the best results. July

56 Appendix C: Management through SNMP The RAIGE OS supports SNMP v2c. An SNMP managed network consists of three key components: Managed devices Agents Network management systems (NMS) In Pivot3 architecture, the managed devices are Appliances, the agents are inside each Appliance, and the NMS is third party software. Figure C 1: Serverless Computing Array in an SNMP managed network Agents SNMP is configured at the array level via RAIGE Director. All agents are affected by the array settings so there is no need to do anything independently to each agent. Since Appliances (managed devices) cooperate within an array the agents are capable of providing information and traps for events on the other Appliances within an array. Array wide events like Appliance failures can be reported from the agent in any available Appliance. Network Management System (NMS) Third party management software using SNMP can be found from many sources. Some are simple trap catchers that route traps to . Others involve more sophisticated polling mechanisms. A RAIGE Director PC running such software must have access to both of the storage networks of the Pivot3 Array and the application network. In many cases the storage network will be an isolated network so the RAIGE Director PC will have to be physically connected to both networks. Another option would be to have an NMS running on the standalone application server that is utilizing the RAIGE Array. This server is in essence a gateway between the storage network and the public network. When the network management application uses SNMP for polling, be sure to set up polls for both of the static IP addresses of each Appliance. Otherwise a failed switch may not be reported. July

57 The Appliance agents use default SNMP ports. The RAIGE Director PC must allow access to UDP port 162 to receive traps and UDP port 161 to poll for information. Each of these ports may have to be opened on the RAIGE Director PC if the PC has a firewall enabled. Many network management applications use SMTP to forward traps as . The networkmanagement application will push an SMTP message to the corporate server, which will forward the message as an to a specified address. The default port for SMTP is TCP port 25. This port must be exempted from a firewall at the corporate server. Table C 1: Ports for SNMP network management Port Transport Used For Must be open at 25 TCP SMTP server receiving SMTP messages 161 UDP SNMP requests RAIGE Director PC 162 UDP SNMP traps RAIGE Director PC Community Strings Community Strings are configured through RAIGE Director for a Pivot3 Array. There are separate Community Strings for SNMP Clients and Trap Targets. Common defaults for both are public. The Community String for SNMP Clients is used to allow the agents to be in a group polled by an NMS. Specifically, this is the Community String for SNMP GETs. SNMP SETs are not supported. The agents will only answer an NMS retrieval request if the NMS knows the Community String. The Community String for Trap Targets allows an NMS functioning as a trap receiver to filter for desired traps. Trap receivers receive all traps sent and it is up to this NMS to filter on the Community String. A trap receiver may choose to ignore the Community String. Pivot3 MIB SNMP uses management information bases (MIBs) to define the variables an SNMP managed system offers. A Pivot3 MIB has been defined to describe each object identifier used for alerts and status for Pivot3 storage. The Pivot3 MIB is contained within the file PIVOT3SYS MIB.txt which may be found on the RAIGE Software Support CD in the SNMP Support folder. The SNMP MIB hierarchy is a tree with levels defined by different organizations. When importing a MIB file into a management software application, the MIB details will exist within that hierarchy. The Pivot3 MIB will be imported into the enterprises class of the MIB tree. MIB II is also supported. July

58 Figure C 2: Pivot3 MIB in MIB Tree July

59 Appendix D: Using the RAIGE Director command line interface To use the RAIGE Director command line interface (CLI): 1. From the Windows Start menu, select Programs > Pivot3 > RAIGE Director > RAIGE Director CLI. 2. Log in to RAIGE Director, if you have specified Administrator credentials. Table D 1 shows the CLI help available from the RAIGE # prompt. Table D 1: RAIGE Director command line interface help This command: help help <command> help config help show 'help all' v outputpath Examples: help all help all v help all v "c:\cli Commands\syntax.txt" Displays: All available help syntax Help for the specific command The commands that configure RAIGE entities The commands to display information on RAIGE entities. The command name and a short description for CLI commands. [OPTIONAL] Change the output to verbose mode: Command Name, Syntax Detailed Description. [OPTIONAL] Save the output to a user specified file. Paths with embedded spaces MUST be contained in quotes. Display all CLI commands to the console. Display all CLI commands in verbose format to the console. Save all CLI commands in verbose format to the file c:\cli Commands\syntax.txt July

60 Appendix E: RAIGE Array state legend July

61 July