OnStor NAS Gateway Installation and Cluster Configuartion

ONStor Bobcat NAS Gateway Installation and Cluster Configuration
Customer Order Number: ONS-DOC-CCG-2200, Rev B1 Text Part Number: 690-0018-0001, B1 Cover Number: 695-0018-0001, B1
ONStor, Inc. 254 East Hacienda Ave. Campbell, CA 95008 (408) 963-2400
Copyright 2005-2007 ONStor, Incorporated. All rights reserved. This document exists for use with the products of ONStor, Inc. and is intended for use by employees, representatives, assigns, and clientele of ONStor, Inc. This document cannot be copied, reproduced, transmitted, or stored electronically, in part or in whole, without first obtaining the express consent and agreement of ONStor, Inc. This document can contain the names of products and services of other companies. Such products and services are the property of their owners, and ONStor, Inc. makes no implications or claims, express or implicit, to the ownership of such products and services. ONStor, Inc. has, in good faith, made efforts to represent trademarked and copyrighted products and services as the property of their respective owners .
Contents
Foreword ........................................................................................................ 5
Audience................................................................................................................................ ii-6 Scope ..................................................................................................................................... ii-7 Related Documentation ......................................................................................................... ii-8 Revision Trail........................................................................................................................ ii-9 Syntax Usage....................................................................................................................... ii-10
Chapter 1: Setup the ONStor NAS Gateway Hardware..................................... 1-1

NAS Gateway Hardware Installation.................................................................................... 1-2
Chapter 2: Preinstallation Tasks........................................................................... 2-1

Preinstallation Planning and Tasks ....................................................................................... 2-2 Basic Installation Process...................................................................................................... 2-5 System Configuration ..................................................................................................... 2-5 System Support, Validation, and Documentation........................................................... 2-6 Customer Orientation...................................................................................................... 2-7 Extended Installation Process................................................................................................ 2-8
Chapter 3: Firmware Installation and Configuration......................................... 3-1

Preconfiguration Considerations ........................................................................................... 3-2 Connect to the ONStor NAS Gateway.................................................................................. 3-3 NAS Gateway Startup ........................................................................................................... 3-4 The ONStor Configuration Tool (OCT)................................................................................ 3-5 Completing the OCT....................................................................................................... 3-6 Configure Administrative Settings ................................................................................. 3-8 Configure Network Settings ......................................................................................... 3-11
Displaying Current Settings in the OCT ............................................................................. 3-15 Committing Parameters ................................................................................................ 3-15 Exiting the OCT............................................................................................................ 3-16 Cluster Cables ..................................................................................................................... 3-19 Management Port Pinouts............................................................................................. 3-19 Cabling the Cluster.............................................................................................................. 3-20 Cabling Redundant SSC Paths...................................................................................... 3-21 Cable Dressing Guidelines ........................................................................................... 3-21
Chapter 4: Software Configuration ...................................................................... 4-1

Connect to the NAS Gateway ............................................................................................... 4-2 Verify NAS Gateway Firmware Installation......................................................................... 4-3 Set System Time and Join Cluster......................................................................................... 4-5 Add the NAS Gateway to a Domain ..................................................................................... 4-6 Configuration Tasks in the Management Virtual Server Domain Context........................... 4-8 Create Volumes on the Management Virtual Server...................................................... 4-8 Create Interface and Route to the Management Virtual Server.................................... 4-11 Configuration Tasks for Virtual Servers ............................................................................. 4-14 Create and Configure a Virtual Server for Data Storage.............................................. 4-14 Add Virtual Server to Network Domain....................................................................... 4-16 Create Share Point for the Virtual Server ..................................................................... 4-17 Configuration Tasks in the Management Virtual Server Domain Context......................... 4-20 Create Volumes on the Management Virtual Server.................................................... 4-20 Configuration of Additional Utilities .................................................................................. 4-24 Event Monitoring and Report Service .......................................................................... 4-24 Autogrow ...................................................................................................................... 4-25 Snapshots ...................................................................................................................... 4-25 Logging for Installation and Upgrades................................................................................ 4-27 Comparing Contents of the Current Software .............................................................. 4-28 Sample Procedure for Install or Upgrade Logging....................................................... 4-28
Chapter 5: Installing Storage Arrays on a NAS Gateway .................................. 5-1

Connecting the Storage Array to the Gateway...................................................................... 5-2 Direct Connect Cabling Requirements ........................................................................... 5-2 Fabric Connect Cabling Requirements........................................................................... 5-3 Configuring the Storage Array.............................................................................................. 5-4
Setting Port Topology..................................................................................................... 5-4 Setting Port Interconnect Settings............................................................................ 5-6 Adding Disk Shelves in an Optimal Manner ........................................................................ 5-9 Creating and Configuring a VDisk...................................................................................... 5-11 Installing and Initializing a VDisk................................................................................ 5-11 Selecting Drives for the VDisk..................................................................................... 5-13 Configuring Volumes on the VDisk ............................................................................. 5-15 Manually Assigning VDisk Ownership........................................................................ 5-17 Managing LUN Ownership................................................................................................. 5-18 Moving VDisks and LUNs ........................................................................................... 5-18 Changing LUN Identifiers ............................................................................................ 5-20
Chapter 6: Overview of Cluster Configuration ................................................... 6-1

Cluster Configuration Concepts ............................................................................................ 6-2 Cluster Configurations Overview.......................................................................................... 6-3 The Primary Cluster Controller (PCC).................................................................................. 6-6 Primary Cluster Controller Election ............................................................................... 6-6 Primary Cluster Controller in Runtime........................................................................... 6-7 The Cluster Database ............................................................................................................ 6-8 Clusters and Time Sources.................................................................................................... 6-9
Chapter 7: Cluster Management Commands ...................................................... 7-1

Cluster Configuration Commands......................................................................................... 7-2 Adding NAS Gateways to a Cluster ............................................................................... 7-2 Deleting NAS Gateways from a Cluster......................................................................... 7-3 Committing Changes to a Cluster................................................................................... 7-4 Uncommitting Changes from the Cluster Database ....................................................... 7-5 Displaying the Cluster Configuration............................................................................. 7-5 Adding a NAS Gateway Group to a Cluster................................................................... 7-6 Moving a NAS Gateway Into or Out of a Group............................................................ 7-7 Deleting a NAS Gateway Group from a Cluster ............................................................ 7-8 Displaying a NAS Gateway Group Configuration ......................................................... 7-8 Deleting a Cluster ........................................................................................................... 7-9
Chapter 8: Configuring Clusters........................................................................... 8-1
Serial Port Settings for Initial Configuration ........................................................................ 8-2 Prerequisites of Configuration .............................................................................................. 8-3 Cluster Creation Procedure ................................................................................................... 8-5 Connecting Multiple Nodes............................................................................................ 8-8
Appendix A:Console Cable Pinouts ..................................................................... A-1

What are the Pinouts?............................................................................................................A-2 Where Should the Cable Be Connected? ..............................................................................A-3
Appendix B:Safety Information ............................................................................B-1

Safety Considerations............................................................................................................B-2 Heat Considerations........................................................................................................B-2 Electrostatic Discharge Considerations ..........................................................................B-2 Equipment Weight Considerations .................................................................................B-2 Electrical Considerations ................................................................................................B-3 Power Supplies.........................................................................................................B-3 Power Cords .............................................................................................................B-3 Grounding ................................................................................................................B-3 Lithium Battery ........................................................................................................B-4 Optical Considerations....................................................................................................B-4 Eye Safety.......................................................................................................................B-4
Appendix C:Approvals and Certifications .......................................................... C-1

Compliances ..........................................................................................................................C-2 European Union Evaluation............................................................................................C-2 ETL/cETL Listing for North America............................................................................C-3 FCC Declaration of Conformity, United States..............................................................C-4 Voluntary Control Council for Interference (VCCI), Japan...........................................C-6 Australian Communications Authority (ACA) Compliance ..........................................C-6 CB Scheme Certificate ..........................................................................................................C-8
ii-5
Preface
This preface contains the front matter for the Installation and Configuration Guide for the ONStor Bobcat 2200 Series NAS Gateway family of products. This foreword contains the following sections: Audience. Scope. Related Documentation. Revision Trail. Syntax Usage
690-0018-0001B1
ii-6
Audience
This guide is for IT professionals and storage administrators of varying levels who administer the ONStor family of 2200 NAS Gateway products and their companys storage area network (SAN).
690-0018-0001B1
ii-7
Scope
The High Availability Deployment Guide is helps to you install and configure the ONStor Bobcat 2200 Series NAS Gateway hardware, firmware, and software, and to set up the NAS Gateway in a cluster configuration.
690-0018-0001B1
ii-8
Related Documentation
This document is part of a set of product documentation for the NAS Gateway. Table F-ii-1 shows the related documentation.
Table ii-1 : ONStor Product Documentation Document Name
ONStor Bobcat 2200 Series NAS Gateway Command Reference ONStor Bobcat 2200 Series NAS Gateway Manager Administrators and Users Guide ONStor Bobcat 2200 Series NAS Cluster Manager Administrators and Users Guide ONStor Bobcat NAS Gateway System Administrators Guide
Part Number
ONS-DOC-CR-2200 ONS-DOC-GMGR D1 E1
Revision Level
ONS-DOC-CMA
B1
ONS-DOC-SAG-2200
E1
If you are managing the NAS Gateway through the ONStor NAS Gateway Manager GUI product, you can also the HTML version of the ONStor NAS Gateway Manager Administrators and Users Guide, which is built into the NAS Gateway Manager GUI. Release notes are available with every release of software. The release notes contain additional information about bugs and fixes in the product, documentation errata or omissions, and new features or enhancements.
690-0018-0001B1
ii-9
Revision Trail
This document is regularly reviewed and revised. Table F-3 shows the history of revision for this document. We recommend obtaining the latest information whenever possible.
Table F-3 : Product Documentation Revision History Document Name
ONStor Bobcat 2200 Series System Administrators Guide ONStor Bobcat 2200 Series System Administrators Guide ONStor Bobcat 2200 Series System Administrators Guide ONStor Bobcat 2200 Series NAS Gateway High Availability Deployment Guide ONStor Bobcat 2200 Series NAS Gateway High Availability Deployment Guide ONStor Bobcat 2200 Series NAS Gateway Cluster Configuration Guide ONStor Bobcat NAS Gateway Installation and Cluster Configuration
Part Number
ONS-DOC-SAG2200 ONS-DOC-SAG2200 ONS-DOC-SAG2200 ONS-DOC-HAD2200 ONS-DOC-HAD2200 ONS-DOC-HAD2200 ONS-DOC-CCG2200
Revision Level
A1 B1 C1 A1
Revision Date
01/18/05 03/16/06 05/08/06 01/18/05
B1
03/15/06
C1
08/17/06
B1
01/23/07
690-0018-0001B1
ii-10
Syntax Usage
The NAS Gateways command-line interpreter uses different syntax markers to indicate specific conditions of usage in the command line. Table F-4 shows the different syntax markers used in the command-line interpreter, and explains what each marker means.
Table F-4 : Syntax Markers Syntax Marker - (dash) blank space bold text bold italic text [ ] (squared brackets) Means... You are specifying an option You are delimiting words, arguments, or options in a command Command syntax A mandatory variable. You need to enter some input for italicized arguments. Input is optional. The command will complete with or without the optional argument. A logical or operation. Select one of the choices for the command to complete A choice is contained within the braces. The open brace ({) indicates the beginning of the choice list, and the closed brace (}) indicates the end of the choice list. Choice lists use pipes (described above) to delimit each element in the choice list. Enter one of the elements in the choice list exactly as it occurs in the list.
-a arp show
Example
list ipaddr
[-c CONTROLLER]
| (pipe) { } (braces)
disk|tape|all
{enable|disable}
690-0018-0001B1
Chapter 1: Setup the ONStor NAS Gateway Hardware

This chapter describes how to install the ONStor NAS Gateway hardware.
690-0018-0001B1
1-2
NAS Gateway Hardware Installation

To install the ONStor NAS Gateway, do the following steps: Step 1: While positioning the ONStor NAS Gateway, ensure that the two socket outlets required to power the NAS Gateway are near the equipment and are easily accessible. Install the NAS Gateway on a rack as shown in Figure 1-1.
Note! The NAS Gateway should not be installed in a WAN-type environment where voltage surges can enter the unit through CAT 5 cables.
Figure 1-1
Step 2: Attach the two IEC 320 power cables to the NAS Gateway. Plug each cable into the IEC 320 plugs, which are located on the rear
690-0018-0001B1
1-3
of the NAS Gateway, one plug on the left side and the other plug on the right side as shown in Figure 1-2.
Figure 1-2
Note! A redundant network configuration is the preferred setup. It is recommended that you always have redundant network connections so that a single failure does not shut down the management network, which makes recovery difficult. For a two-node cluster, you should have one connection to the main network and another connection with a crossover cable. For a cluster larger than two nodes, you should have one connection to the main network and another connection with a second switch (a setup described as a hybrid network).
Step 3: After plugging the two IEC 3320 power cables into the NAS Gateway, plug each power cord cable into a separate power outlet. The NAS Gateway contains load-sharing power supplies and for this reason requires two power outlets. To ensure failover, you must plug the power supplies into outlets that are on different AC circuits as shown in Figure 1-3.
690-0018-0001B1
1-4
Figure 1-3
Step 4: After verifying that both connections to the power facilities are correct, switch on the power supplies. The power supply activation switches, located on the rear of the NAS Gateway, are marked with an I (In) for on and O (Out) for off as shown in Figure 1-4. Press the I marker to turn on the power supply (the switch should rock upwards). Conversely, press the O marker to turn off the power supply (the switch should rock downwards). You should hear the power supplies activate when you turn them on. Also, the built-in fans start to operate at maximum speed, then slow to an operational speed. This behavior is normal.
Step 5: Check the LED lights on the front of the NAS Gateway after it completes its boot up phase. After power-up, the FLT LED will be red and then will turn off when the system is fully booted. At this point, the OK LED will then become green. The PS and FAN LEDs should also be green. The LEDs for GigE and FC ports behave as follows:
690-0018-0001B1
1-5
Green: port enabled, valid link Amber: port enabled, no link Off: port disabled
Note! If a cable is not plugged into a port, the corresponding LED will be amber assuming the ports have been enabled (which they are, by default, at the first installation). Once a cable is plugged in and a link is established, the LED will turn green.
Figure 1-4
This concludes the physical hardware installation of the NAS Gateway.

Note! Contact the ONStor Customer Support department if your ONStor NAS Gateway is not operating properly.
690-0018-0001B1
1-6
690-0018-0001B1
Chapter 2: Preinstallation Tasks

This chapter describes the preinstallation planning and tasks that you need to perform before the actual installation takes place. In addition, the chapter outlines the process that comprises a basic installation. It includes the following sections: Preinstallation Planning and Tasks on page 2-2 Basic Installation Process on page 2-5 Extended Installation Process on page 2-8
690-0018-0001B1
2-2
Preinstallation Planning and Tasks

Before installing and configuring the firmware and software components of the ONStor NAS Gateway device, the preinstallation tasks listed here should be completed. Typically, the customer performs these preinstallation tasks.
Note! The ONStor Site Survey, which provides a checklist of these preinstallation tasks, should be completed and available during this installation. The survey is available as a separate document. The customer should also have read and signed the ONStor Statement of Work.
Preinstallation covers planning and preparing the SAN network, storage subsystem, IP network, client environment, and backup/tape information. It consists of the following tasks: Physical site preparation: Site preparation includes ensuring: System environment has adequate rack space Redundant power available HVAC requirements are met Fiber raceway is in place for the new equipment Cable lengths are appropriate for the host locations Provide SAN configuration documentation, including: Switch port connections Host/LUN table Any switch zoning requirements if tape is required
Installation planning:
Provide a network diagram that includes details of the LAN/SAN switch and IP configuration pertaining to the environment Schedule a downtime window to configure and install ONStors configuration.
Fibre Channel and SAN tasks:
690-0018-0001B1
2-3
LUN allocation: All LUNs must be pre-allocated/zeroed available in a common zone Performance: To deliver the requested performance, adequate resources (such as spindle count), and appropriate policies, (such as read ahead), need to be used to create LUNs. Oversubscription: If the array is a shared resource, take steps to ensure that the array will not be oversubscribed by other applications. (ONStor access to the SAN administrator is highly recommended.) SAN: Two FC cables per node from the SAN in the same zone. (WWN can be provided by ONStor as needed.) For each node, up to four network ports are needed on the switch that connects the ONStor NAS Gateway. For each switch, provide the appropriate VLANs and configure its ether channel. Ensure that all Layer 3 network addresses, netmasks, and default routes are identified and allocated to the NAS Gateway. Provide the IP addresses for network servers (e.g. DNS, AD, NIS, and so forth). Set up access to the following servers as required: FTP server, NTP server, NIS server, SMTP server, and domain controllers. Have available at least one Windows client to run ONStor management software. Provide two high-performance clients to test the performance for each protocol. Provide the names of the users or groups who will have cluster administrative privileges.
Network setup: -
Server access setup: -
Security setup: -
690-0018-0001B1
2-4
Provide access to a domain administrator who has the capability to add a machine account to the domain.
690-0018-0001B1
2-5
Basic Installation Process

This section gives you an overview of a complete, basic installation and the sequence of operations. You can find details for many of these operations in subsequent chapters.
System Configuration
System configuration consists of the following tasks and operations: Node installation: Physically installing one or more systems on the rack. Performing operating system (OS) upgrades, if needed. Laying out LUNs in a best practices manner. Checking supported array settings. Checking for pre-allocated LUNs. Creating or integrating the ONStor NAS Gateway into the current network. Use NTP for this operation. Connecting into the LAN switch. Setting up ether channel, if required. Connecting into the SAN switch, if required. Setting up IP addresses, default routes, and joining the ONStor NAS Gateway to the NIS/AD domain. Creating up to five virtual servers. For each virtual server volume, set up the snapshot utility as per each customers policy. Creating up to five file systems/shares and export each share according to each customers policy.
LUN integration:
Network integration:
Virtual servers configuration: -
690-0018-0001B1
2-6
Additional licensed products: Enabling all purchased software products. Clients: Validating that client operating system versions are supports. Installing NGM management software on any Windows systems.
Administration: Adding at least one user with cluster administration privileges
System Support, Validation, and Documentation

The maintenance, protective features for the system, and plus test that clients can perform for basic operations. Setting up maintenance features: Setting up console, core volume, management volume, and autosupport features. Setting up remote error logs (elogs), if customer desires this feature.
Testing redundancy and high-availability features: Includes testing dual power, vserver failover, ether channel, and FC multi-pathing features. Testing client access: Checking that a file can be create from a client for each protocol, and the permissions should be appropriately set. For a multi-protocol environment, checking that the same file operations (create, read, and change permissions) can be performed via both protocols on the same file by users allowed file access by the default mapping. Recovering a file from the snapshot utility.
Establishing a performance baseline: Documenting the streaming performance of read and write operations for one to two clients per protocol. Documenting install: Collect support.sh.
690-0018-0001B1
2-7
Customer Orientation
Customer orientation involves transferring information to the customer, or customer education. It includes the following: Providing a system architecture overview Reviewing the basic system configuration, operation, and monitoring commands, including: Tour of the graphical user interface Instructions to create virtual servers, file systems, and shares Management of snapshots and file recovery from snapshots Explanation of how to create mirrors for a volume Product road map
Providing an overview of the customer support services: Includes creating an ASSIST account, opening a case, and downloading software.
690-0018-0001B1
2-8
Extended Installation Process

In addition to the basic installation, an extended installation includes the following: Creating additional virtual servers, file systems, shares. This includes creating up to 20 virtual servers and file systems, and up to 40 shares. Performing site integration for no more than two sites. Site integration includes: Filer NDMP integration into an existing backup architecture Filer anti-virus integration into an existing set of virus scanner servers Filer SNMP integration into an existing MRTG server
690-0018-0001B1
Chapter 3: Firmware Installation and Configuration

Installation of the ONStor NAS Gateway device is a two-part process. Begin by installing and configuring the firmware component. When completed successfully, proceed to the software configuration. This chapter covers the following topics: Preconfiguration Considerations on page 3-2 The ONStor Configuration Tool (OCT) on page 3-5 Configure Administrative Settings on page 3-8 Configure Network Settings on page 3-11
690-0018-0001B1
3-2
Preconfiguration Considerations
Before configuring a cluster, you need to determine the following: The network on which you will support the cluster. All NAS Gateways in the cluster need to be configured on the same subnet. However, since SC1 and SC2 have to be on two different subnets, the SSC ports, FibreChannel ports and Gigabit Ethernet interfaces could be on different subnets. The number of NAS Gateway groups that each cluster will support. The number of NAS Gateways that each NAS Gateway group will support. The virtual servers you want to create in protected mode and the ones you want unprotected. The number of virtual servers that will be configured on each NAS Gateway. ONStor recommends that you balance the system usage between the NAS Gateways in the cluster.
690-0018-0001B1
3-3
Connect to the ONStor NAS Gateway

Use a console (or serial) cable to connect your computer to the ONStor NAS Gateway device. (A console cable has a DB9 end and an adapter end and it is supplied with every new NAS Gateway.) The cable goes into the socket to the far right of the front of the NAS Gateway device. Plug the other end of the cable into a USB port on your computer. Use a terminal emulation application such as hyper terminal to open a TTY terminal window to connect to the NAS Gateway console through its serial port. Then, set the baud rate and serial port settings for the connection, as follows: Baud Rate: 57600 (56 K) Data Bits: 8 Parity: None Stop Bits: 1 Flow Control: None
From the terminal window, connect to the NAS Gateway. You are now ready to use the ONStor Configuration Tool (OCT), which is the firmware configuration tool. If you are just now booting (powering on) the NAS Gateway, the OCT runs automatically. If the NAS Gateway was booted prior to connecting to the device, then you need to start the tool: Enter OCT in the terminal window to start the tool.
690-0018-0001B1
3-4
NAS Gateway Startup

When you first start up the NAS Gateway, the ONStor Configuration Tool (OCT) runs automatically. The OCT is a menu-driven tool that facilitates the initial configuration of the NAS Gateway.
Note! You can access the OCT only through the SSC console port.
For a comprehensive list of information elements required to configure the NAS Gateway, please see the ONStor Pre Configuration Checklist.
690-0018-0001B1
3-5
The ONStor Configuration Tool (OCT)

The OCT guides you through the initial configuration of the NAS Gateway and enables you to connect it to the network. The NAS Gateway is not configured on the network until all tasks of the OCT are completed, and the parameters are committed. The NAS Gateway supports a command-line interface, and a GUI that enables you to use the NAS Gateway features. When you use the OCT, you are prompted to enter the following information: The current date, time, and time zone A unique node name for each NAS Gateway in the cluster IP addresses and netmasks for the NAS Gateways management IP ports A default route
Select the Display Current Settings on the main menu to check your progress. Table 3-1 displays each task and explains its part in the configuration.
Note! The cluster network is configured on the management IP port on the SSC. Therefore, the management IPs are set using the OCT prior to the NAS Gateway joining the cluster. The management ports are labeled SC1 and SC2 for the left and right ports, respectively.
690-0018-0001B1
3-6
Table 3-1 : Contents of the ONStor Configuration Tool Task

Administrative settings
Controls
Setting parameters that you use to facilitate managing the NAS Gateway. For example, the system date and time are configured through this menu. Setting network parameters that enable the NAS Gateway to connect to IP clients. For example, default and specific routes are configured through this menu. Displaying sections of the OCT to determine which are configured. Applying parameters to the NAS Gateway as a batch. Before committing changes, it is a good practice to review parameters. Exiting the OCT. If you exit before committing changes, the NAS Gateway is not configured with any of the information that you entered, and the OCT will run the next time you log in.
See...
Completing the OCT on page 3-6
Network settings
Completing the OCT on page 3-6
Display current settings Commit changes
Exiting the OCT on page 3-16 Committing Pending Parameters on page 3-15.
Exit
Exiting the OCT on page 3-16.
Completing the OCT

When you start the OCT, the Welcome screen is displayed as shown in Figure 3-1. This screen introduces the product and references the documentation that is provided with your product
690-0018-0001B1
3-7
Welcome to the ONStor NAS Gateway Initial Configuration Tool The ONStor Configuration Tool (OCT) guides you through the initial setup of the ONStor NAS Gateway. Please refer to the Hardware Installation Guide and complete the hardware installation prior to configuring the NAS Gateway. To configure the NAS Gateway, you need to give the machine a unique name and provide IP addresses for the management network ports. Collect this information prior to continuing with the installation. The initial user name for this machine is 'admin'. The initial password is 'password'. Press 'Enter' to proceed to the main menu... Gathering system info, please wait...
Figure 3-1 OCT Welcome Screen
690-0018-0001B1
3-8
To configure the cluster using the OCT, perform the following procedures: Step 1: Press Enter to begin the OCT and display the main menu. Information about each task is listed on the main menu, as displayed in Figure 3-2.
ONStor NAS Gateway Initial Configuration Tool 1. Configure Administrative Settings 2. Configure Network Settings 3. Display Current Settings 4. Commit Changes 5. Help 6. Exit Enter Selection:
Figure 3-2 Main Menu
Configure Administrative Settings

Use the Administrative Settings submenu to set the time zone and current date and time for the system. These settings should reflect the time zone, date, and time where the NAS Gateway is installed. Enter 1, Configure Administrative Settings, from the OCT main menu to open the Administrative submenu. This submenu has options to set the time zone and the current date and time. (See Figure 3-3.)
690-0018-0001B1
3-9
Current time and date: Wed Jan 1. Set Time Zone 2. Set Time & Date 3. Help 4. Return to previous menu Enter Selection:
5 11:37:16 PST 2006
Figure 3-3 Administrative Settings Submenu
The following steps pertain to the functions available from the Administrative Settings submenu. Step 1: Enter 1, Set Time Zone, to set the time zone. If the Administrative Settings submenu displays the correct time zone, then skip this step. Step 2: Enter the number corresponding to the appropriate time zone from the list of time zones. It is important to set the time zone correctly since you later (during the software configuration phase) synchronize the management virtual server to the NAS Gateway. Press Enter to see additional time zones. (See Figure 34.)
690-0018-0001B1
3-10
Step 3: Press 1 to configure the time zone where the NAS Gateway is installed. When you press 1, a list of time zones is displayed, as shown in Figure 3-4.
Select a time zone from the list 1 US/Eastern 2 US/Central 3 US/Mountain 4 US/Pacific 5 Japan 6 Hongkong 7 Europe/London 8 Europe/Paris 9 Africa/Abidjan 10 Africa/Accra 11 Africa/Addis_Ababa 12 Africa/Algiers 13 Africa/Asmera 14 Africa/Bamako 15 Africa/Bangui Enter selection or press Enter to continue list (q to quit):
Figure 3-4 Time Zone List
You can page through the list of time zones by pressing Enter, or you can quit the time zone list by pressing Q. Enter the number associated with the time zone you require, and the time zone is automatically programmed into the NAS Gateway. After the time zone is programmed, the OCT returns to the Date and Time menu.
690-0018-0001B1
3-11
Step 4: Enter 2 from the Administrative Settings submenu to set the current date and time. (See Figure 3-5.) Skip this step if the current time and date display is correct..
Current time and date: Sun Jan 9 11:20:25 PST 2006 Enter day, month, year (format: DD/MM/YY) Press 'Enter' to retain current date: Current time and date: Sun Jan 9 11:27:48 PST 2006 Enter time (format HH:MM:SS) Press 'Enter' to retain current time settings):
Figure 3-5 System Time and Date Prompts
Enter the date in the following format: DD/MM/YY for the day, month, and year. For example, 03/07/06 is July 3, 2006. DD is a two-digit indicator from 01 to 31 that determines the day of the month. An invalid date can negatively affect the date stamp that the NAS Gateway uses. MM is a two-digit indicator from 01 to 12 that determines the current month. YY is a two-digit indicator from 00 to 99 where 00 is the first year of the century, and 99 is the last year of the century.
Note! If the currently programmed date is correct, press Enter to accept it.
Step 5: Similarly, set the time .Enter the current time in the following format: HH:MM:SS for hours, minutes, and seconds values. Use 24-hour time. For example, 20:30:13 is 8:30:13 PM whereas 08:30:13 is 8:30:13 AM. It is critical when later doing the software configuration that the time be set correctly This completes the administrative settings configuration. Enter 4 in the Administrative Settings submenu to return to the OCT main menu.
Configure Network Settings

The Configure Network Configuration submenu assists you to configure the network, including:
690-0018-0001B1 ONStor Bobcat NAS Gateway Installation and Cluster Configuration
3-12
Set a node name for the NAS Gateway Configure the management network ports (referred to as the SC ports) Set a default route
Enter 2, Configure Network Settings, from the OCT main menu to open the Network Configuration submenu as shown in Figure 3-6.
Network Configuration 1. Set Node Name [ NOT_CONFIGURED ] 2. Configure Management Network Ports [ NOT_CONFIGURED ] 3. Set Default Route [ NOT_SET ] 4. Help 5. Return to Previous Menu Enter Selection:
Figure 3-6 Network Configuration Submenu
The following steps pertain to the functions available from the Network Configuration submenu. Step 1: Set a node name that uniquely identifies this NAS Gateway within a cluster. Enter 1 at the Network Configuration submenu to bring up the prompt for setting the user-determined node name for the NAS Gateway. Step 2: The OCT prompts for a node name, as shown in Figure 3-7. Enter an identifying name, such as onstor1_lab. The name should be an alphanumeric string of up to 16 characters.
Note! Do not use the special characters *~? in a node name.
690-0018-0001B1
3-13
Node name must be unique to the cluster this node will join Enter Node Name:
Figure 3-7 Node Name Prompt
Press Enter to return to the Network Configuration submenu. Step 3: Enter 2 to configure the management network ports. The Configure Management Network Ports screen displays. (See Figure 3-8.)
Configure Management Network Ports 1. Configure Port 1 [ IP: NOT_CONFIGURED netmask: NOT_CONFIGURED ] 2. Configure Port 2 [ IP: NOT_CONFIGURED netmask: NOT_CONFIGURED ] 3. Help 4. Return to Previous Menu Enter Selection:
Figure 3-8 Configure Management Network Ports Screen
You configure two management network ports, SC1 and SC2. Port 1 is the ethernet port for client access. Port 2 is used for clustering. Configure each port by entering its respective Internet Protocol (IP) address and subnet mask. This information is supplied by the customer. Step 4: Enter 1 to configure port 1. Enter the port IP address and subnet mask to the following prompts (see Figure 3-9):
690-0018-0001B1
3-14
Configure Management Network Ports Enter port 1's IP address: Enter port 1's address mask: Enter Selection:
Figure 3-9 Configure Management Network Port 1
Step 5: Enter 2 to configure port 2. The same prompts appear for port 2, to which you enter its IP address and subnet mask. Press Enter to return to the Network Configuration submenu. Step 6: Enter 3 at the Network Configuration submenu to set a default route. The following prompt appears (see Figure 3-10), to which you enter the IP address of the default route. The IP address for the default route is supplied by the customer.
Enter Default Route (n.n.n.n):
Figure 3-10 Set Default Route
After you set the default route, the tool returns you to the Network Configuration submenu. Enter 4 to return to the OCT main menu.
Note! The default route must be on the same subnet as an SSC IP port to be displayed in the route table. After the NAS Gateway comes online, you can modify the default route by deleting and re-adding the default route by using the route delete default -g and the route add default -g commands, respectively.
Step 7: Verify that the current configuration settings are correct. From the OCT main menu, enter 3, Display Current Settings, to view the current configuration settings. The tool displays the Current Settings Report. Figure 3-11 shows an example of this report.
690-0018-0001B1
3-15
Displaying Current Settings in the OCT

After completing the information elements in the OCT, you can display the parameters on screen to verify that the information is correct. The current settings are displayed using the main menu. The display shows the committed parameters in the Current Settings section and the pending parameters in the Pending Parameters section. To display the current OCT settings, follow this procedure: Step 1: From the main menu, press 3 to display the Current Settings Report as shown in Figure 3-11.
Current Settings: Node Name: nas-gw1 Date & Time: Wed Jan 5 11:37:16 PST 2006 Network Settings: Mgmt port 1 IP: 192.168.128.1 NETMASK: 0xffff0000 Mgmt port 2 IP: NETMASK: 0xffff0000 Current default route: 192.119.0.1 Pending changes: New Node Name: pubstest Network Settings: New default route: 192.168.0.1 Press Enter to continue...
Figure 3-11 OCT Current Settings Report
Step 2: After reviewing the Current Settings report, press Enter to close the report and return to the main menu. Step 3: Use the appropriate option on the main menu to make changes.
Note! If you need help to configure the OCT, use the Task Help, which is in the menu of each OCT task. To learn more about the concepts and operation of OCT, read the General Help text on the main menu.
Committing Parameters
After reviewing parameters, return to the main menu and press 4. The parameters are written to the NAS Gateways configuration file. When you commit parameters to the
690-0018-0001B1
3-16
NAS Gateway, they are written as a batch file. The NAS Gateway goes only online after you commit parameters. Before committing the configuration, verify all settings and correct any errors using the appropriate OCT function. Step 4: Commit the configuration. Enter 4, Commit Changes, on the OCT main menu to commit the configuration and build the configuration table. You configure each NAS Gateway device only once. Also, be sure to commit the configuration before exiting, since the configuration setup is lost if you exit without performing the commit. Step 5: Exit the OCT configuration tool. Enter 6, Exit, on the OCT main menu. You are asked to confirm that you are exiting the tool. (See Figure 3-12.)
Please answer 'yes' or 'no' Are you sure you wish to exit setup now? (Yes or No) Enter Selection:
Figure 3-12 Exit the OCT
Since all configuration data is discarded if you exit the OCT before committing the configuration, the tool warns you if you attempt to exit without committing the configuration setup. (See Figure 3-13.)
Changes have not been committed. Are you sure you wish to exit setup now? (Yes or No) Enter Selection:
Figure 3-13 Exit the OCT Confirmation
Exiting the OCT

You need to press 6 to exit the OCT. Depending on whether you have made changes, and whether the changes have been committed, you can have three different outputs. If
ONStor Bobcat NAS Gateway Installation and Cluster Configuration 690-0018-0001B1
3-17
changes have been made, or if they have been made but not yet committed, the OCT will inform you and ask you for confirmation. When changes have been made, and committed, the OCT exits without confirmation. When no changes have been made, follow the procedure as displayed in Figure 3-14.
The following must be configured prior to exiting the setup tool: The NAS Gateway name has not been set. It is recommended you configure the following prior to exiting the setup tool: Management Port 1 has not been configured Management Port 2 has not been configured You must configure mandatory settings prior to exiting. Press 'Enter' to continue...
Figure 3-14 Exit OCT Confirmation Prompt: No Changes Made
690-0018-0001B1
3-18
When changes have been made, but not committed, follow the procedure as displayed in Figure 3-15.
Changes have not been committed. Are you sure you wish to exit setup now? (Yes or No) If answer is Yes, the bootup process continues but all changes are discarded If answer is No, returns to main menu
Figure 3-15 Exit OCT Confirmation Prompt: Changes Made but Not Committed
When changes have been made and they have been committed, no confirmation is required before exit. Follow the procedure as displayed in Figure 3-16.
Enter Selection: 6 Value Entered is 6 Starting network Add net default: gateway 10.2.0.1
Figure 3-16 Exiting OCT: Changes Made and Committed

Note! While you run the OCT, all the messages and input from the installation are stored in a log file /var/log/rc.initial.log on compact flash. After completing the OCT, you can copy the rc.initial.log file from the default location (/var/log) to a target specified volume and virtual server, where the log file can be viewed or sent to ONStor support if needed.
690-0018-0001B1
3-19
Cluster Cables
The NAS Gateway contains a cluster accessory kit that contains crossover cluster cables to connect the NAS Gateways in a direct configuration that only works for twonode clusters. When you add multiple nodes in direct or hybrid configuration, use CAT-5 Ethernet cables. The following cables are used: Management cable for the CONSOLE port. This cable is provided with the SF4400 NAS Gateway. Pinouts are included in case you need to use additional cables. Management port cables for the NAS Gateways 10/100 RJ-45 ports.
Management Port Pinouts

To create a management cable for the NAS Gateway, connect a male RJ45 connector to a standard CAT5 10/100BaseTX cable. This cable connects to the 10/100 RJ45 port on the NAS Gateways faceplate. The pinouts are industry standards.
690-0018-0001B1
3-20
Cabling the Cluster

While configuring the cluster, you need to ensure that the physical layer is correctly cabled to support synchronization of the cluster database and proper failover of virtual servers. A correctly cabled cluster provides high availability of file services. A cluster can be cabled through the 10/100 ports on the SSC to provide either of the following: Network configuration cluster with the two SSC paths to two different management networks. Direct configuration cluster with two SSC path with a direct connection between two NAS Gateways. Hybrid configuration with one SSC path to the management network, and one SSC path for a direct connection between two NAS Gateways.
Figure 3-17 shows the location of the two SSC management ports.
SSC Management port 1 and 2
Figure 3-17 SSC Management port locations

Note! ONStor recommends installing the NAS Gateways vertically in the same rack. This reduces the footprint required for the cluster. For a vertical installation, you should allocate at least 6 rack units of vertical space to accommodate the clustering pair.
Caution! ESD Sensitive Components! This product contains electronic components that are sensitive to electrostatic discharge (ESD). To avoid damage to the product or its components, ensure that you are wearing an ESD wrist strap, or are using an appropriate method of ESD protection prior to handling the product or any of its components.
690-0018-0001B1
3-21
Cabling Redundant SSC Paths

Although the cable connection depends on the configuration you choose, the basics remain consistent. For illustrative purposes, we are using two NAS Gateways to show the different configurations. For any configuration, you also need to perform the following two steps: Step 1: Connect both NAS Gateways into the Gigabit Ethernet network using Gigabit Ethernet switches that are in the same network. Step 2: Connect the NAS Gateways into the storage area network (SAN) using the FibreChannel ports.
Cable Dressing Guidelines

A proper cable dressing facilitates checking the NAS Gateways visual indicators, creates a safer physical environment, and protects the NAS Gateways cables against undue wear. The NAS Gateway has a cable hook on the right side of the front of the chassis, through which you can hook all the cables together.
Note! Before connecting cables, label the cables near both plugs to make them easier to identify.
Arrange cables through the cable hook and attach to the rack, as shown in Figure 3-18. Ensure that the screw that holds the unit in the rack is not obstructed. .
Figure 3-18 Cable arrangement for cables

Note! Leave some slack in the cables between the management ports on the SSC and the corresponding cable hook to relieve stress on the cable, and provide easy access to the NAS Gateways compact flash drives.
690-0018-0001B1
3-22
690-0018-0001B1
Chapter 4: Software Configuration

The software configuration of the ONStor NAS Gateway device can be done remotely from a computer. This chapter covers the steps for performing a basic software configuration of the NAS Gateway. This process can be done remotely from your computer. The chapter covers the following configuration topics: Connect to the NAS Gateway on page 4-2 Verify NAS Gateway Firmware Installation on page 4-3 Set System Time and Join Cluster on page 4-5 Add the NAS Gateway to a Domain on page 4-6 Configuration Tasks in the Management Virtual Server Domain Context on page 4-8 Create Volumes on the Management Virtual Server on page 4-8 Create Interface and Route to the Management Virtual Server on page 4-12 Create and Configure a Virtual Server for Data Storage on page 4-14 Add Virtual Server to Network Domain on page 4-16 Create Share Point for the Virtual Server on page 4-17 Event Monitoring and Report Service on page 4-24 Autogrow on page 4-25 Snapshots on page 4-25
Configuration Tasks for Virtual Servers on page 4-14 -
Configuration of Additional Utilities on page 4-24 -
690-0018-0001B1
4-2
Connect to the NAS Gateway

To configure the software, you need to connect to the NAS Gateway. From your computer, use the NAS Gateway Graphical User Interface (GUI) or a Secure Shell (SSH) client, such as PuTTy Client, to establish a remote connection to the NAS Gateway. Through the client window, login to the NAS Gateway with the user name admin and password password. After logging in, the user is in the NAS Gateway context by default. This is considered the global context, and the user needs to do some configuration steps, such as set system time, join the cluster, and add the NAS Gateway to the domain.
Note! Much of the work you do here entails using NAS Gateway system commands. You should refer to the ONStor 2200 Bobcat Command Reference for a complete listing and explanation of the available system commands. You can also enter a question mark (?) at the terminal prompt to see a list of all system commands.
690-0018-0001B1
4-3
Verify NAS Gateway Firmware Installation

Before configuring the software, you should verify that the firmware component is correctly installed on the NAS Gateway. Use the system commands to check the NAS Gateway status. Verify that the CPU state is UP for the NAS Gateway you are installing. This command displays the current state for all CPUs on each NAS Gateway device on the network:
system show chassis
Verify the virtual servers configured on the NAS Gateway. You should check that the device has a management virtual server, which should have been created automatically and physically linked to the NAS Gateway, and which exists solely for management purposes. You will also be creating at least one virtual server, which enables client access to the file storage. This command shows all virtual servers configured on the NAS Gateway:
vsvr show
Verify the IP interfaces that exist and are up. The IP interface provides the means to connect the NAS Gateway to the clients IP network and every NAS Gateway must have at least one such I interface.
interface show interface
Verify the system version. This command shows the full configuration of the NAS Gateway, including all CPUs, PROMs, compact flash cards, and SC ports.
system show version
Verify all configured ports and check that their statuses are UP. This command displays the ports as SC1, SC2, and so forth.
port show all
Verify the virtual storage LUNs. LUNs, which represent virtual chunks of storage on the physical hard disks of the Storage Area Network (SAN), are configured and added to the storage pool by the customer. The NAS Gateway addresses a LUN via an IP address through a fiber channel switch, which converts the IP address to the addressing scheme used in the SAN network. This command displays a table of all LUNs, state, and the name of the NAS Gateway to which the LUN belongs:
690-0018-0001B1
4-4 lun show all
For example, this command may produce a report similar to the following
All devices known to PCC. ========================= Device Name NEXSAN_5000402001 ec0590_6DCABA41 NEXSAN_5000402001 ec0590_6DCABAA6 NEXSAN_5000402001 ec0590_6D7791C0 NEXSAN_5000402001 ec0590_6D49C4D7 vol_mgt_495 NEXSAN_5000402001 ec0590_6D49C46B Model Disk Disk Disk Disk Raid Raid-5 Raid-5 Raid-5 Raid-5 Size(MB) State 9536.62 9536.62 9536.62 9536.62 free free Cluster onstor1_lab onstor1_lab diff Volume
outCluster onstor2 outCluster onstor2
Disk
Raid-5
9536.62
outCluster onstor2
core2
The PCC is the Primary Cluster Controller. The Device Name column identifies each LUN. The Cluster column indicates that NAS Gateway to which the LUN belongs, such as onstor1_lab or onstor2. A LUN can be in one of four states: - Out of clusterThis LUN is currently not in the cluster and not available to the cluster. It needs to be added to the cluster before it can be used. UsedThis LUN is assigned to a NAS Gateway and is unavailable to other devices. ForeignThe LUN has just been discovered and nothing is known about it. FreeThe LUN is available and free to use with a NAS Gateway.
690-0018-0001B1
4-5
Set System Time and Join Cluster

First, synchronize the system time between the NAS Gateway management virtual server and the network. You supply the IP address for the NAS Gateway using this command:
system time ntp -a IP address
You can verify that the time is properly synchronized using this command:
system time show -v
Next, add the NAS Gateway to a cluster. The following steps show how to join the NAS Gateway to cluster. Step 1: Add the NAS Gateway to the cluster. Specify the name of the NAS Gateway and its IP address.
cluster add nasgateway NASGATEWAYNAME -a IP address
Step 2: Commit the operation, using this command:

cluster commit
Step 3: The NAS Gateway that you just added will reboot and join the cluster.
690-0018-0001B1
4-6
Add the NAS Gateway to a Domain

For a client to be able to access the NAS Gateway, the NAS Gateway must be part of a domain. There are two steps to add the NAS Gateway to a domain: actually adding it to the domain and then configuring the Domain Name Server (DNS) resolver. Step 1: You add the NAS Gateway to a domain using one of the following commands, depending on the platform. To properly complete the command, you need to know the name of the domain, the IP address for the domain controller, and the administrator login name. On a Windows platform:
domain add windows domain name admin-name IP address
For example, to add the NAS Gateway to a Windows domain named effigy whose domain controller is at the IP address 10.2.128.141, and use the admin login name onstor, enter the command as follow
domain add windows effigy onstor 10.2.128.141
On a UNIX platform, the command is as follows:
domain add nis domain name IP address
Step 2: Add the IP address for the NAS Gateway to the DNS server. This enables a client to access the NAS Gateway by name rather than having to use the IP address. Step 3: You add the IP address for the NAS Gateway to the DNS server by editing the DNS resolver configuration file. (The DNS resolver configuration file contains keyword/value pairs, and you need to add the DNS servers IP address value for the nameserver keyword. In addition, you can add domain and search information.) Use the following command to edit the configuration file:
system dnsconfigure resolver
Enter the nameserver keyword and the IP address value into the file that opens, along with domain and search information.
690-0018-0001B1
4-7
nameserver IP address Domain domain name Search list_of_domains
For example, if the IP address of the NAS Gateway is 10.3.35.1, you add the following to the file:
nameserver 10.3.35.1
The NAS Gateway is now added to the domain and can be located by the DNS name server. This also completes the configuration of the global domain context. The next set of configuration tasks apply to the management virtual server domain context.
690-0018-0001B1
4-8
Configuration Tasks in the Management Virtual Server Domain Context

You perform the configuration tasks in this section from within the management virtual server domain context rather than the global domain context. Once you change to this domain context, the commands you enter act only on the management virtual server itself. In the management virtual server domain, you create two volumes (also referred to as file systems) and add references to these volumes in the DNS resolver configuration file. You also create interfaces to allow access to the server and add a route to the interfaces. The following steps take you through this process. Step 1: Set the domain context to the management virtual server domain. This command changes the domain context from the global context to the management virtual server context.
vsvr set management virtual server
You reference the management virtual server by name, which always begins with the name string VS_MGMT followed by a numerical ID. For example, if the management virtual server on the NAS Gateway is named VS_MGMT_512, the command looks as follows:
vsvr set VS_MGMT_512
After you change to the management virtual server domain, the terminal prompt, assuming the NAS Gateway is called onstor1_lab, is as follows:
onstor1_lab VS_MGMT_512 diag>
Create Volumes on the Management Virtual Server

You need to create two volumes on the management virtual servera management volume and a core volumeand each volume must be connected to an available LUN. Both volumes have specific management uses. As a result, customers should not use either of these volumes for client data storage:
690-0018-0001B1
4-9
Since you are working in the context of the management virtual server, you create the volumes specifying the available LUNs to which they should be connected. If need be, before creating these volumes use the command lun show all to see the available (free) LUNs. Keep in mind the following information before creating these two volumes: Management volumeA management volume is used for Network Data Management Protocol (NDMP) buffering and for backup purposes. This volume is mounted by default. The management volume also holds all system logs, including output from the system get all script, which tracks configuration and troubleshooting information. The management volume size should be at least ten (10) gigabytes and preferably should be twenty (20) gigabytes. While the management volume must use at least one LUN, the number of LUNs it uses does not matter. Management volume use is not performance critical. Thus, if your storage configuration includes multiple types of storage, consider using your slowest storage for the management volume. Management volume availability is important. The management volume, although accessible through NFS and CIFS, should never be used to store your own data files. Because it uses the management volume for administrative purposes, the NAS Gateway may fill, delete, and overwrite files on the volume without notice.
Core volumeThe core volumes sole purpose is as a repository for the system to dump its raw memory in the event of a panic, thus preserving the raw memory for later analysis. Such core dumps are automatically generated if the NAS Gateway fails for some reason. The core volume does not contain a readable file system and does not appear as mounted. The amount of memory in the core volumes NAS Gateway owner dictates the volumes minimum size. If you attempt to create a core
690-0018-0001B1
4-10
volume too small for the NAS Gateway, the system prints an error and does not create the core volume. Step 1: Create the management volume. The command to create the management volume is:
system create mgmtVolume LUN
For example, if you are working in the management virtual server domain context and there is a free LUN device called NEXSAN_5000402001ec0590_6DCABA41, you create the management volume as follows:
system create mgmtVolume NEXSAN_5000402001ec0590_6DCABA41
Step 2: Create the core volume. The command to create the core volume is as follows:
system create corevolume core volume name LUN
For example, to create a core volume called core1 connected to the free LUN called NEXSAN_5000402001ec0590_6DCABAA6, you use this command:
system create corevolume core1 NEXSAN_5000402001ec0590_6DCABAA6
Step 3: You may want to verify that the two volumes were created correctly. Use the following command to see the volumes created on the management virtual server:
volume show
This command displays the following report for the VS_MGMT_512 management virtual server:
Name
Status
Type
Curre nt (MiB)
Hard Quot a
Use d
Avail
Usag e
VirtualServer
690-0018-0001B1
4-11
vol_m gmt_5 12 core1
Mounte d Not Mounte d
Standar d Core
9408. 62 0.00
No Limit No Limit
34.6 2 0.00
9374.0 1 0.00
0.37 % 0.00 %
VS_MGMT_51 2 VS_MGMT_51 2
You may also want to verify that the two volumes are associated to the LUNs you designated. Use the command lun show all. For example, the lun show all command displays the following information for the NAS Gateway onstor1_lab:
All devices known to PCC. ========================= Device Name NEXSAN_5000402001 ec0590_6DCABAB2 NEXSAN_5000402001 ec0590_6DCABA41 NEXSAN_5000402001 ec0590_6DCABAA6 Model Disk Disk Disk Raid Raid-5 Raid-5 Raid-5 Size(MB) State 9536.62 9536.62 9536.62 free used used Cluster onstor1_lab onstor1_lab onstor1_lab vol_mgmt_512 core1 Volume
Create Interface and Route to the Management Virtual Server

Next, you need to create an interface to the management virtual server. An interface is required for client access to this server, and to any other server. The interface becomes part of the network stack for access between the client and the server. You should create the interface to the management virtual server while you are still within the management virtual server domain context. Step 1: To create an interface, you need to specify a port. Use the lport show command to see the available ports. In particular, you need to find a port whose operation status is UP. The lport show command produces a report similar to the following:
Table 4-1 : Logical Port Table
Name fp1.0 Admin UP Operation UP Mode single IPCnt 0 PrefPort N/A ActPort fp1.0 Ports fp1.0
690-0018-0001B1
4-12
Name fp1.1 fp1.2 fp1.3
Admin UP UP UP
Operation DOWN DOWN DOWN
Mode single single single
IPCnt 0 0 0
PrefPort N/A N/A N/A
ActPort fp1.1 fp1.2 fp1.3
Ports fp1.1 fp1.2 fp1.3
Step 2: Create an interface to the management virtual server. When you create the interface, you provide a name for the interface, associate it to a logical port, and assign the interface an IP address. Use the following command (the -l option lets you specify the logical port for the interface, the -s option lets you indicate whether the interface is enabled or disabled, and the -a option lets you specify the IP address):
interface create interface name -l logical port -s enable|disable -a IP address
For example, the following command creates an interface called mgmt using the logical port fp1.0 and assigns it the IP address 10.3.35.52/16. The interface is enabled.
int create mgmt -l fp1.0 -s enable -a 10.3.35.52/16
Step 3: Add a route. A route is associated to an interface and is the means to access the interface. Use the following command to add a route:
route add default -g IP address
For example, the following command adds a route for an interface whose IP address is 10.3.30.1:
route add default -g 10.3.30.1
Step 4: Exit the management virtual server domain context. This completes the installation steps that involve the management virtual server. Use the following command to exit the management virtual server domain and return to the global domain context:
vsvr clear
690-0018-0001B1
4-13
To indicate that you are in the global domain, the terminal prompt displays only the NAS Gateway and no longer displays the management virtual server name. Step 5: Edit the DNS resolver configuration file using the command system dnsconfigure resolver. Enter the nameserver keyword and the IP address value into the file that opens, along with domain and search information.
After you complete the management virtual server installation and return to the global domain context, you can create the data storage servers.
690-0018-0001B1
4-14
Configuration Tasks for Virtual Servers

This section covers the installation and configuration tasks for logical virtual servers, the servers that handle client data storage. These servers are referred to as virtual servers, but you might think of them as virtual file servers.
Create and Configure a Virtual Server for Data Storage

After completing the configuration of the management virtual server, you create and configure the virtual servers on the NAS Gateway that will be used for client data storage. You create the virtual server by creating an interface for the serverassigning it an interface name, logical port, and IP address. Then, you add a route to the virtual server interface. Step 1: Start by checking the logical virtual servers already created for the NAS Gateway. Use this command to see all virtual servers on the NAS Gateway:
vsvr show
This command produces a report such as the following::

Virtual servers on nas gateway onstor1_lab ID State Name
================================================== == 1 Enabled VS_MGMT_512
Note that only the management virtual server, VM_MGMT_512, is defined for the NAS Gateway onstor1_lab. Step 2: Create a logical virtual server within the NAS Gateway and change to that servers domain context. Use the following command:
vsvr create virtual server name
For example, this command creates a logical virtual server called training on the NAS Gateway onstor1_lab and sets the context to that server:
690-0018-0001B1
4-15
vsvr create training
The steps that follow pertain to this particular virtual server and commands are given from within its domain context. Step 3: Create an interface for a virtual server. Use the following command (the -l option lets you specify the logical port for the interface, the -s option lets you indicate the interface status either enabled or disabledand the -a option lets you specify the IP address):
interface create virtual server name -l logical port -s enable|disable -a IP address
For example, this command creates an interface to the logical virtual server training. In addition, it assigns the server the logical port fp1.0, enables the server, and gives it the IP address 10.4.43.35.53/16.
int create training -l fp1.0 -s enable -a 10.4.4 3.35.53/16 Note! You can use the same logical port for more than one server.
Step 4: Add a route to the virtual server interface to give clients access to the interface. Use this command:
route add default -g IP address
For example, the following command adds a route to the training virtual server interface at the IP address 10.3.35.1:
route add default -g 10.3.35.1
Step 5: Edit the DNS resolver configuration file using the command system dnsconfigure resolver. Enter the nameserver keyword and the IP address value into the file that opens, along with domain and search information.
690-0018-0001B1
4-16
For example, if the IP address is 10.3.35.1, you add the following to the file:
nameserver 10.3.35.1
Add Virtual Server to Network Domain

Once a virtual server is configured, you can add it to the network domain. You may add a virtual server to a Windows Common Internet File System (CIFS) domain and/ or a UNIX Network File System (NFS) domain. Step 1: Set a domain for the virtual server. The domain may be either a Windows domaina Domain Name Server (DNS) domainor a UNIX Network Information Service (NIS) domain. As part of the command, you specify the domaineither windows or nisalong with the domain name and, if you are specifying a Windows domain, the administrator user name. The following command sets the domain:
vsvr set domain windows|nis domainname adminuser
For example, this command sets a Windows domain called cslab whose administrator user name is administrator. (You are prompted for the administrator password after entering this command.)
vsvr set domain windows cslab administrator Note! For this command to work, you must previously have defined a Windows and/ or a NIS domain using the command domain add windows|nis.
After the command completes, you can view the results using the command vsvr show all, which produces a report of the virtual servers on the NAS Gateway. Notice
690-0018-0001B1
4-17
that, in addition to the management virtual server VS_MGMT_512 on the onstor1_lab NAS Gateway, there is now a TRAINING virtual server.:
================================================== 1 2 Enabled Disabled VS_MGMT_512 TRAINING
Step 2: Enable the virtual server within the domain. When you configure a virtual server, you do so while it is disabled. By default, when a virtual server is added to a domain, it is disabled. At this point, you need to enable the virtual server. Use this command:
vsvr enable
Step 3: Create a storage areaa data storage volumefor the virtual server. Use the following command, specifying a name for the data storage volume and a LUN for the volume. (Use the lun show all command to see the list of free LUNs.)
volume create volumename LUN
For example, this command creates a volume called training connected to the LUN NEXSAN_5000402001ec0590_6DCABAB2:
volume create training NEXSAN_5000402001ec0590_6DCABAB2
Create Share Point for the Virtual Server

You need to create a share point for the virtual server volume or data storage file. A share point essentially pus the servers volume on the network and makes it accessible to clients. This action is comparable to mounting a file system (in UNIX terms) or sharing computer files or directories across a network. After creating a share point, you must also set up the correct security permissions and privileges. Step 1: Add the virtual server data storage volume to the CIFS network.
690-0018-0001B1 ONStor Bobcat NAS Gateway Installation and Cluster Configuration
4-18
You need to specify the volume name, a sharename for the volume, and the path to the volume. The sharename is the name that is visible to clients. Use the following CIFS command:
cifs share add volumename sharename pathname
For example, this command creates a share point for the training storage volume, gives it the name techpub, and specifies that the path to techpub is the root directory, represented by the back slash (\):
cifs share add training techpub \
Step 2: Set the security permissions for the share point. Add the necessary access privileges and security permissions to the share point so that clients can access it. ONStor follows the Windows security model for the NAS Gateway: it grants a user deemed to be an administrator all privileges (admin privileges) and all other users read only privileges (exec privileges). Use this command to grant security privileges, designating either a user or a group and setting the scope of the granted privileges to the entire cluster or the virtual server: (On a UNIX system, the default security permissions for a file system are encoded as 755. That is, a root user has read, write, and edit permissions and all other users have read only permissions.)
privilege add allow user|group cluster|vsvr privilege
For example, the following command grants administrator security privileges to the user cslab. Furthermore, the users privileges span the entire cluster:
privilege add allow user cslab\administrator CLUSTER cluster
Step 3: At this point, the NAS Gateway is operational and can be accessed by Windows clients. You can verify this using the following command:
cifs show
This command displays the storage volumes available on CIFS. For example, you might see the following output:
ONStor Bobcat NAS Gateway Installation and Cluster Configuration 690-0018-0001B1
4-19
VSCAN$ IPC$ techpub
You can more information on a specific volume using the command:

cifs show volumename
For example, use the following command to see more information on the techpub volume, which produces a report showing the volumes share name, the volume name, and the path to the volume:
cifs show techpub Share name: techpub Volume: training Path: \
If your setup includes providing client access to the NAS Gateway from a UNIX system, you must also create a Network File System (NFS) share point for the data storage volume. Follow these steps on a UNIX system: Step 1: Create and add the share point for the volume. Use the NFS command:
nfs share add directory path
For example, to create a NFS share point for the training volume and set up some access privileges, you might use the following command:
nfs share add /training -o rw=*;no_root_squash=*
The data storage volume should now be accessible to UNIX clients.
690-0018-0001B1
4-20
Configuration Tasks in the Management Virtual Server Domain Context

You perform the configuration tasks in this section from within the management virtual server domain context rather than the global domain context. Once you change to this domain context, the commands you enter act only on the management virtual server itself. In the management virtual server domain, you create two volumes (also referred to as file systems) and add references to these volumes in the DNS resolver configuration file. You also create interfaces to allow access to the server and add a route to the interfaces. The following steps take you through this process. Step 1: Set the domain context to the management virtual server domain. This command changes the domain context from the global context to the management virtual server context.
vsvr set management virtual server
You reference the management virtual server by name, which always begins with the name string VS_MGMT followed by a numerical ID. For example, if the management virtual server on the NAS Gateway is named VS_MGMT_512, the command looks as follows:
vsvr set VS_MGMT_512
After you change to the management virtual server domain, the terminal prompt, assuming the NAS Gateway is called onstor1_lab, is as follows:
onstor1_lab VS_MGMT_512 diag>
Create Volumes on the Management Virtual Server

You need to create two volumes on the management virtual servera management volume and a core volumeand each volume must be connected to an available LUN. Both volumes have specific management uses. As a result, customers should not use either of these volumes for client data storage:
690-0018-0001B1
4-21
Since you are working in the context of the management virtual server, you create the volumes specifying the available LUNs to which they should be connected. If need be, before creating these volumes use the command lun show all to see the available (free) LUNs. Keep in mind the following information before creating these two volumes: Management volumeA management volume is used for Network Data Management Protocol (NDMP) buffering and for backup purposes. This volume is mounted by default. The management volume also holds all system logs, including output from the system get all script, which tracks configuration and troubleshooting information. The management volume size should be at least ten (10) gigabytes and preferably should be twenty (20) gigabytes. While the management volume must use at least one LUN, the number of LUNs it uses does not matter. Management volume use is not performance critical. Thus, if your storage configuration includes multiple types of storage, consider using your slowest storage for the management volume. Management volume availability is important. The management volume, although accessible through NFS and CIFS, should never be used to store your own data files. Because it uses the management volume for administrative purposes, the NAS Gateway may fill, delete, and overwrite files on the volume without notice.
Core volumeThe core volumes sole purpose is as a repository for the system to dump its raw memory in the event of a panic, thus preserving the raw memory for later analysis. Such core dumps are automatically generated if the NAS Gateway fails for some reason. The core volume does not contain a readable file system and does not appear as mounted. The amount of memory in the core volumes NAS Gateway owner dictates the volumes minimum size. If you attempt to create a core
690-0018-0001B1
4-22
volume too small for the NAS Gateway, the system prints an error and does not create the core volume. Step 1: Create the management volume. The command to create the management volume is:
system create mgmtVolume LUN
For example, if you are working in the management virtual server domain context and there is a free LUN device called NEXSAN_5000402001ec0590_6DCABA41, you create the management volume as follows:
system create mgmtVolume NEXSAN_5000402001ec0590_6DCABA41
Step 2: Create the core volume. The command to create the core volume is as follows:
system create corevolume core volume name LUN
For example, to create a core volume called core1 connected to the free LUN called NEXSAN_5000402001ec0590_6DCABAA6, you use this command:
system create corevolume core1 NEXSAN_5000402001ec0590_6DCABAA6
Step 3: You may want to verify that the two volumes were created correctly. Use the following command to see the volumes created on the management virtual server:
volume show
This command displays the following report for the VS_MGMT_512 management virtual server:
Name vol_mg mt_512 core1 Status Mounted Not Mounted Type Standard Core Current (MiB) 9408.6 2 0.00 Hard Quota No Limit No Limit Used 34.62 0.00 Avail 9374.01 0.00 Usage 0.37 % 0.00 % VirtualServer VS_MGMT_512 VS_MGMT_512
690-0018-0001B1
4-23
You may also want to verify that the two volumes are associated to the LUNs you designated. Use the command lun show all. For example, the lun show all command displays the following information for the NAS Gateway onstor1_lab::
All devices known to PCC. ========================= Device Name NEXSAN_5000402001 ec0590_6DCABAB2 NEXSAN_5000402001 ec0590_6DCABA41 NEXSAN_5000402001 ec0590_6DCABAA6 Model Disk Disk Disk Raid Raid-5 Raid-5 Raid-5 Size(MB) State 9536.62 9536.62 9536.62 free used used Cluster onstor1_lab onstor1_lab onstor1_lab vol_mgmt_512 core1 Volume
690-0018-0001B1
4-24
Configuration of Additional Utilities

You may also install additional utilities that help with troubleshooting and supporting any problems that may occur on the NAS Gateway. These additional utilities include: Event Monitoring Reporting Service (EMRS)Monitors the NAS Gateway, collects information for troubleshooting, and sends email when a change event occurs to support at ONStor. AutogrowPermits a data storage volume to automatically grow in size, based on specified parameters. SnapshotRecords changes made to an entire data storage volume at predefined intervals, and can be used to recover data.
Event Monitoring and Report Service

The Event Monitoring and Reporting Service (EMRS) provides extensive support capabilities. Not only does it collect information useful for troubleshooting NAS Gateway problems, it also automatically sends email notification messages to support at ONStor. The EMRS reporting can occur without the clients knowledge or even when the client is not aware of a problem. Use the autosupport command to setup EMRS and email notification. This command has the following options:
clear email emrs generate schedule show state clear autosupport related info autosupport email option EMRS commands generate instant autosupport report schedule for auto support report generation show autosupport related info modify autosupport state
When using the autosupport command to setup EMRS, you can enable or disable EMRS, configure EMRS for a proxy server, and enable or disable the automatic
690-0018-0001B1
4-25
sending of EMRS data. Use the command autosupport emrs show to see the current EMRS configuration on a NAS Gateway. It produces a report such as the following::
================================================== 1 2 Enabled Enabled VS_MGMT_512 TRAINING
Autogrow
The autogrow utility, which is an optional utility, allows you to specify parameters to automatically grow a volumes storage. You typically specify a volume to grow by some number of gigabytes. You set up this utility using the autogrow command followed by one or more options and parameters. Some of the options you can specify with autogrow are:
hardquotaSets a softquotaSends
hard maximum size limit for the volume. a message when the volume grows to this size. the minimum size amount to autogrow the volume.
min autogrowIndicates
highwatermarkIndicates the size of the volume at which autogrow should grow
the volume.
min/max lunsizeSpecifies
a minimum and/or maximum LUN size, usually between 400 and 600 gigabytes.
Note! There is no support for shrinking a volume.
Snapshots
Snapshots is a utility that is useful for recovering data that is mistakenly deleted. The utility takes an initial picture of the entire data storage volume. Then, every so many hours according to a schedule you define, the utility takes another picture of the entire data storage volume and saves the delta between the two pictures. Thus, it keeps a
690-0018-0001B1
4-26
running track of data storage changes to file systems made between successive snapshots of the volume. By default, snapshots are enabled on a new volume, but can be disabled. The snapshots schedule is approximately every four hours, but this, too, can be modified. Use the snapshot command to setup this utility. To see how the utility is currently defined for a volume, use this command:
snapshot show volumename
For example, the command snapshot show vol_mgmt_512 schedule displays the following report:
** snapshot scheduling currently disabled for this volume ** schedule ======== 0 2 8 @8 12 16 20
690-0018-0001B1
4-27
Logging for Installation and Upgrades

The NAS Gateway can track status messages during installation and upgrades. These messages are written to logs where they can be viewed or copied to another location. Two different logs exist, one for installation and one for upgrades: For installation, the log file is called rc.initial.log. The first time you install a NAS Gateway, a bootup script called the ONStor Configuration Tool (OCT) activates to help guide you through configuring the NAS Gateway on the network. While you run the OCT, all the messages and input from the OCT are stored in a log file /var/log/rc.initial.log on compact flash. When you have completed the OCT, you can copy the rc.initial.log file from the default location (/var/log) to a target specified volume and virtual server, where the log file can be viewed or sent to ONStor support if needed.
Note! You can exit the OCT at any time during initial configuration of the NAS Gateway. If you exit the OCT before completing it, the rc.initial.log retains all the configuration messages that have been completed. The log does not delete the partial configurations messages.
For upgrade, the log file is called sys_upgrade.log. Whenever you upgrade the EverON software on a NAS Gateway, you issue the system upgrade command. This command triggers the logging so that upgrade messages are logged during the entire upgrade process. During the upgrade, console messages are stored in file / var/log/sys_upgrade.log on the compact flash. When you have completed the upgrade, you can copy the sys_upgrade.log file from the default location (/var/ log) to a target volume and virtual server, where the log file can be viewed or sent to ONStor support if needed.
Note! As part of supporting logging of upgrades, a new command called system compare has been added to help validate the distribution software that you are upgrading to. For more information about system compare, see Comparing Contents of the Current Software on page 4-28.
690-0018-0001B1
4-28
Comparing Contents of the Current Software

You can use a the system compare command, to compare the contents of the current system software on the NAS Gateways active flash module to the system software that resides on another location, for example an NFS or FTP download server. To compare the contents of the current software to the contents of new software run this command from the NAS Gateway context:
system compare LOCATION [-s]
LOCATION is where the distribution software is. For upgrading from an NFS or FTP server, enter the IP address of the server and the download directory location separated by a colon (:). For example, to specify the new distribution software in the directory /home/upgrade/R1.3.0-022806.tar.gz on an FTP server with IP address 168.192.3.4, you would issue the command as follows
system compare ftp://user:password@168.192.3.4/home/ upgrade/R1.3.0-022806.tar.gz
-s is an optional argument that specifies the standby flash module that contains the system software that you want to compare to the software on the NFS or FTP server.
Sample Procedure for Install or Upgrade Logging

These steps show the sequence for using the new install or upgrade logging feature: Step 1: Select the appropriate task: If you are performing a first time install, complete the ONStor Configuration Tool (OCT) script as documented in the ONStor High Availability Deployment Guide. Proceed to Step 3. If you are upgrading existing software, issue the system compare command to check the distribution software against the software currently on your compact flash. For information about this command, see Comparing Contents of the Current Software on page 4-28. Proceed to Step 2.
Step 2: Issue the system upgrade command.
690-0018-0001B1
4-29
Step 3: When the NAS Gateway is up and running, copy the log files to a target volume by issuing the system get logs command and specifying the virtual server and the volume where you want the log file to be copied. For example, to copy the log files to the virtual server eng and the volume temp, you would issue the command as follows:
system get logs -V eng -v temp
Step 4: When the log files are on the target volume, they can be viewed or sent to ONStor Technical Support engineers.
690-0018-0001B1
4-30
The following is an example of the upgrade log:

Performing system upgrade from location ftp://upgrade:password@168.192.0.2/home/upgrade/R1.2.3.0BC062205.tar.gz Downloading external system software distribution. Done. Mounted the upgrade directory Current system version: 1.2.3.0 upgrade version: 1.2.6.0 Reading the system descriptor...done Reading the upgrade directory...done Making upgrade files list checking /bin/cat...up-to-date checking /bin/chmod...up-to-date checking /bin/chio...up-to-date checking /bin/cp...up-to-date checking /bin/csh...up-to-date checking /bin/date...up-to-date ../ checking /version...version file The following files will be upgraded: /mnt/etc/rc.initial/mnt/usr/local/agile/bin/nfxsh/mnt/usr/local/ agile/lib/libnfxsh.so/mnt/versionSystem will reboot due to system upgrade. Shutting down the MCP...done Shutting down the system software...done Shutting down the inetd...done Remounting the local filesystem read-write...done Updating directories...done Installing /etc/rc.initial...done Installing /usr/local/agile/bin/nfxsh...done Installing /usr/local/agile/lib/libnfxsh.so...done Installing /version...done Rebooting the system...
This example output from sys_upgrade.log shows: the beginning of the system upgrade procedure. some standard status messages as the upgrade continues. the end of the system upgrade when the NAS Gateway is rebooted.
For a sample procedure for using the upgrade and install logging, see Sample Procedure for Install or Upgrade Logging on page 4-28.
690-0018-0001B1
4-31
690-0018-0001B1
4-32
690-0018-0001B1
Chapter 5: Installing Storage Arrays on a NAS Gateway

This chapter describes how to install and configure the RAID (Redundant Array of Independent Disks) storage on a clustered set of NAS Gateway systems. Specifically, this chapter addresses how to connect the storage to the NAS Gateway systems for proper failover, so that an abnormal failure of one part of the system results in an automatic switchover to a standby machine. It also describes how to configure the storage array through the user interface. Before continuing, decide if your NAS Gateway RAID storage will be directly connected or fabric connected through a switch. You install and configure the storage arrays differently depending on the connection mode you choose. This chapter covers the following: Connecting the Storage Array to the Gateway on page 5-2 Configuring the Storage Array on page 5-4 Adding Disk Shelves in an Optimal Manner on page 5-9 Creating and Configuring a VDisk on page 5-11 Managing LUN Ownership on page 5-18
690-0018-0001B1
5-2
Connecting the Storage Array to the Gateway

This section describes how to connect a RAID storage array to the NAS Gateway. It includes specific hardware instructions for cabling the array controller to the NAS Gateway.
Direct Connect Cabling Requirements

Direct connect cabling requirements are necessary for multipathing to work. Multipathing is the ability to seamlessly send data down a different path, either cable or port, in case of a failure in one path. In direct connect cabling, you cable the storage array controller to the NAS Gateway in a manner that multipathing occurs in case of a controller failure. Step 1: Connect port SP0 of the NAS Gateway to Port 0 of the storage array controller A. (See Figure 5-1.) Step 2: Connect port SP1 of the NAS Gateway to Port 0 of the storage array controller B. (See Figure 5-1.) You need to connect one NAS Gateway port to controller A and the other Gateway port to controller B to support multipathing. Connecting in this manner leaves two ports available if you choose to use a high availability solution.
Note! Do not connect both cables to the same controller, since this creates a single point of failure. Note! Do not connect the cables from the Gateway to Port 0 and Port 1 of different controllers. If the ports are connected in this manner, the NAS Gateway perceives twice the number of paths then actually exist. (Because the ports are in fact linked, the paths are not duplicated.) However, because a NAS Gateway is limited in the number of paths that it recognizes, this connection pattern is not recommended.
690-0018-0001B1
5-3
Figure 5-1 Direct Connect Cabling Between NAS Gateway and Array Controllers
Fabric Connect Cabling Requirements

Unlike the direct connect mode, fabric connect mode has no cabling requirements.
690-0018-0001B1
5-4
Configuring the Storage Array

This section provides instructions for using the user interface to configure the storage array. Configuring the storage array requires setting the port topology and then interconnecting the ports. Before continuing with the configuration, you should refer to the NAS Gateway Getting Started Guide and the Storage Array Getting Started Guide so that both the Gateway and the storage array are properly unpacked and set up. Access the user interface from a browser window. The default IP address for the user interface is 10.0.0.1, but you can change it during the installation using the command line interface (CLI). To set a new default IP address, use the following command:
CLI$: set network-parameters ip <IP address> netmask <netmask IP address> gateway <gateway IP address> controller <controller ID>
For more information on setting the default IP address, see the Getting Started Guide for the storage array.
Note! You can find the user interface selection options, shown as a series of options separated by arrows (->) such as Manage -> General Conf -> host port configuration, on the left-hand frame in the browser window.
Setting Port Topology

Setting port topology is identical for both direct and fabric connect modes. Step 1: From the storage array user interface, select the Manage -> General Conf -> host port configuration function. For both direct and fabric connect modes, verify that the link speed is set to 2 Gbit/sec; this link speed setting is required so that the LUNS can be discovered. See Figure 5-2. Warning! Do not select 4 Gbit/sec.
690-0018-0001B1
5-5
Figure 5-2 Verifying Port Speed and Setting Port Topology
Step 2: Select Change Host Port Topology (under Advanced Options, for Fibre Channel Topology), as shown in Figure 5-2. Step 3: Set Topology to Loop mode for all ports for both direct and fabric connect modes. Click Save and Continue. (See Figure 5-3.) Fabric connect requires that the array be run in Loop mode so that multipathing for failover works.
690-0018-0001B1
5-6
Figure 5-3 Setting Port Topology to Loop Mode
Setting Port Interconnect Settings Ports must be interconnected after the storage array is directly connected to the NAS Gateway to allow for failover due to link failures. Interconnect mode links Port 0 of the storage array controller A to Port 1 of controller B. By interconnecting these two ports on the two different controllers, all LUNs on controller B are available on controller A, and vice versa. Interconnect the ports through the user interface as follows: Step 1: Select Manage -> General Config -> host port configuration. Step 2: Select Change FC Port Interconnect Settings as shown in See Figure 5-4.
690-0018-0001B1
5-7
Figure 5-4 Change Interconnect Settings
Step 3: If you are using direct connect mode, select Interconnected. Then click Save and Continue as shown in Figure 5-5. If you are using fabric connect mode, select Straight-through.
690-0018-0001B1
5-8
Figure 5-5 Set Port Interconnect for Direct Connect Mode
690-0018-0001B1
5-9
Adding Disk Shelves in an Optimal Manner

You can add additional disk shelves to the Gateway configuration. For optimal performance, these additional disk shelves should be connected controller to controller. While in theory, cross-connecting the Serial Attached SCSI (SAS) cables from the storage array controllers to the disk shelves has no impact on performance, it is possible that performance may be impacted (up to 40%) when the SAS cables are cross connected. Figure 5-6 illustrates currently how best to connect extra disk shelves. The SAS cabling directly connects the RAID controller to the JBOD (Just Bunch of Disks) controller.
RAID Controller
JBOD Controller
Figure 5-6 Cabling Extra Disk Shelves

Note! It is expected that reverse cabling will be supported in the near future. With reverse cabling, you connect three or more disk shelves following a set pattern. This cabling configuration pattern allows you to remove, power off, or service
690-0018-0001B1
5-10 a middle controller unit without affecting IO to the other units. The cabling configuration pattern is as follows: Connect RAID controller A to the first JBOD controller A. Connect RAID controller B to the last JBOD controller B. Connect the first JBOD controller A to the second JBOD controller A until you reach the last JBOD controller. Connect the last JBOD controller B to the next to last JBOD controller B until you reach the first JBOD controller.
690-0018-0001B1
5-11
Creating and Configuring a VDisk

The storage array uses virtual disks (VDisks). A VDisk contains volumes and a volume appears to the NAS Gateway as a LUN. See Configuration Tasks for Virtual Servers on page 4-14 for information on creating volumes and LUNs. This section describes how to create and configure a VDisk, which you do from within the user interface application.
Installing and Initializing a VDisk

Begin by installing and initializing a VDisk. Figure 5-7 illustrates the steps in this process. Above Step 1: Select Manage > VIRTUAL DISK CONFIG > create a vdisk. Step 2: For the Virtual Disk Creation Method, select Manual Virtual Disk Creation.
Note! Generally, manual virtual disk creation is recommended because you can choose the number of drives to use for the disk. Keep in mind that the best throughput performance was measured using twelve disks per virtual disk. But you must also balance throughput performance with availability requirements (that is, hot or dedicated spares).
Step 3: Enter the virtual disk name and select the virtual disk RAID level. Step 4: Select whether you want the installation initialization to be online or offline. Click Advanced Options, then select either Offline or Online for Initialization Type. When deciding between offline and online initialization, you should keep the following points in mind: The larger the virtual disk (whether SAS or SATA), the longer the initialization process takes. SAS disks initialize in less time than SATA disks. For example, a sizeable SATA disk may initialize overnight with offline initialization, but online
690-0018-0001B1
5-12
initialization of the same disk may take several days. Offline initialization is always faster than online initialization. Although offline initialization always completes in less time than online initialization, your LUNs are not available during offline initialization until the entire initialization completes. With online initialization, although it takes considerably longer than offline initialization, your LUNs are available during the initialization process. If you want to have immediate access to the LUNs on the virtual disk and you are not concerned about performance, then you should consider choosing the online installation initialization type. When performance is an issue, use offline initialization. Performance is degraded during online initialization, but you can access and use the LUNs. Storage should stay online during the initialization process.
Note!
When you use automatic VDisk creation, the system alternates the assignment of VDisks to controllers. That is, it assigns the first VDisk to controller A, then it assigns the second VDisk to controller B, then the third VDisk to controller A, and so on. If you prefer, you can manually assign VDisk ownership to specific controllers when you do the initial VDisk configuration. See Manually Assigning VDisk Ownership on page 5-17 for more information. Step 5: Click Create New Virtual Disk when you have completed the above steps.
690-0018-0001B1
5-13
1 2
4 5
Figure 5-7 Creating a VDisk
Selecting Drives for the VDisk

Select the drives that you want to add to the VDisk. The user interface displays the different enclosures and the drives within each enclosure. Hover the mouse over a drive to see information about that drive. (See Figure 5-8.) Generally, you should consider leaving some drives unchecked so that they are available as spares, although it is not required that drives be designated as spares. Designating one or more drives as spares is a trade off between data protection and performance. Step 1: Select the drives to add to the VDisk. Check the box next to each drive that you want to add. (See Figure 5-8.) Click Calculate Virtual Disk Size to see the size of the disk.
690-0018-0001B1
5-14
690-0018-0001B1
5-15
Figure 5-8 Select Drives for a VDisk
Step 2: Click Continue after selecting the drives for this virtual disk. The user interface displays the screen for configuring the volumes of the virtual disk. See Figure 5-9 in Configuring Volumes on the VDisk on page 5-15. If you want to dedicate spare drives, use the Manage -> Virtual Disk Config -> add vdisk spares function after you configure the disk volumes.
Configuring Volumes on the VDisk

After you specify the VDisk drives, the user interface displays the VDisk summary screen. (See Figure 5-9.) The top half of the screen displays the drives that you have chosen with their serial numbers and size. You use the options available on the bottom half of this screen to configure the volumes or LUNs on the VDisk. You can specify the following: The number of volumes (LUNs) to create Whether the volumes should be of equal size or not Whether the volumes should be exposed to all hosts If you want LUN IDs automatically assigned or not If you want to name the volumes
Step 1: Enter the number of volumes you want to create on the disk. The example in Figure 5-9 creates one volume. Creating one volume defaults to the assumption of volumes of equal sizes. This example also has the LUN IDs automatically assigned. For failover to properly work, it is also recommended that you expose the volume to all hosts.
690-0018-0001B1
5-16
Figure 5-9 Configure VDisk Volumes
Step 2: Click Advanced Options, and in the pop-up screen that displays, you can override the automatic settings. (See Figure 5-10 in Manually Assigning VDisk Ownership on page 5-17.) Step 3: Click Create Virtual Disk to complete the virtual disk creation process.
Note! The VDisk must be initialized before disk performance can be demonstrated.
690-0018-0001B1
5-17
Manually Assigning VDisk Ownership

At the time you create a virtual disk you manually can assign ownership of that disk. To do so, follow the VDisk create steps outlined above. Be sure to select Manual Virtual Disk Creation (see Figure 5-7) in the Create Virtual Disk screen (shown in the section Installing and Initializing a VDisk on page 5-11). Step 1: Follow the virtual disk creation steps outlined above until you reach the screen Configure Volumes for Virtual Disk (see Figure 5-9). Here you want to select Advanced Options, as described in Step 2 for Configuring Volumes on the VDisk on page 5-15. A pop-up screen opens through which you can manually override the automatic settings for the virtual disk.
Figure 5-10 Advanced Virtual Disk Creation Options Pop-Up Screen
Step 2: If you wish, you can select a virtual disk block size other than the default block size of 64K. However, note that our testing shows that 64K has the best performance. Step 3: Select the preferred owner for the virtual disk.
690-0018-0001B1
5-18
Managing LUN Ownership

This section describes how to assign VDisk ownership and move LUNs to different controllers. Keep in mind that it is a disruptive process to change the controller associated with a LUN. When you move a LUN to a different controller, the volumes are offline until you assign new LUN identifiers to the volumes in a VDisk. This section covers: Moving VDisks and LUNs on page 5-18 Changing LUN Identifiers on page 5-20
Moving VDisks and LUNs

Recall that virtual disks (VDisks) in the storage array contain volumes and that volumes are synonymous to LUNs. When you move a virtual disk from one controller to another, all the LUNs on that virtual disk are affected. Step 1: In the user interface, select Manage -> Virtual Disk Config -> change vdisk owner. Step 2: Select the virtual disk and then click Change Virtual Disk Owner with the alternate controller name. (See Figure 5-11.)
690-0018-0001B1
5-19
Figure 5-11 Changing VDisk Owner
Step 3: The user interface displays a warning message alerting you to reassign the LUN IDs and to issue a rescan operation from the host. See Figure 5-12.
Note! Keep in mind that the LUN IDs you assign must be unique across the controller.
690-0018-0001B1
5-20
Figure 5-12 Warning When Changing Virtual Disk Owner
Step 4: Click OK to proceed.
Changing LUN Identifiers

Changing the LUN identifiers is a complicated process since it requires that you manually record LUN identifiers. Step 1: After you move the VDisk to the alternate controller, select Monitor -> Status -> vdisk status and select the VDisk you moved. The screen displays the status of the virtual disk. If you look closely at this screen, notice that the virtual disk Volume Information panel indicates that no LUN identifiers exist on the volumes for the moved virtual disk. (See Figure 5-13.)
690-0018-0001B1
5-21
Figure 5-13 VDisk Status and LUN Identifiers
Step 2: Select the VDisks on the target controller and record all the LUN identifiers in use. For example, if you moved the VDisk to
690-0018-0001B1
5-22
controller B, then you must record all LUN identifiers used for all VDisks on controller B. Step 3: Select Manage -> Volume Management -> volume mapping -> map hosts to volume. Repeat the following steps for each volume in the virtual disk (see Figure 5-14): Step 1: Select a volume. Step 2: Set the Host WWN to default. Step 3: Leave Host Name blank. Step 4: Add an unused LUN ID. Step 5: Select Map Host.
690-0018-0001B1
5-23
2 5
Figure 5-14 Assigning New LUN Identifiers
690-0018-0001B1
5-24
690-0018-0001B1
Chapter 6: Overview of Cluster Configuration

This chapter details the following topics: Cluster Configuration Concepts on page 6-2 Cluster Configurations Overview on page 6-3 The Primary Cluster Controller (PCC) on page 6-6 The Cluster Database on page 6-8 Clusters and Time Sources on page 6-9
690-0018-0001B1
6-2
Cluster Configuration Concepts

ONStor cluster configuration enables a networked cluster of NAS Gateways to form one large logical entity. Cluster configuration enables restoration of file services in minimal downtime if a failure occurs on one of the NAS Gateways in the cluster. Clustering supports the following: High availability: Failover allows transfer of virtual servers in the cluster to another NAS Gateway if an event takes a NAS Gateway offline. Although virtual servers are configured on a specific NAS Gateway, any NAS Gateway in the cluster can assume ownership of a virtual server if an error occurs on the NAS Gateway, leading to high availability of the virtual servers. Load balancing: Load balancing is done through the manual transfer of virtual servers. When a NAS Gateway has a high load, you can transfer virtual servers manually to another NAS Gateways.
690-0018-0001B1
6-3
Cluster Configurations Overview

Clusters are created by plugging the NAS Gateways 10/100 Ethernet RJ-45 management ports into the cluster network, connecting the Gigabit Ethernet ports into an IP data network, and connecting the FibreChannel ports into a storage area network (SAN). The cluster database is a binary file that resides on each NAS Gateway and maintains the configuration information for all nodes in the cluster, and is updated when changes occur. Each node has the same database, so propagation of changes are controlled by the NAS Gateway, which assumes the role of the Primary Cluster Controller (PCC).
Note! The NAS Gateway is always considered to be in a cluster. Even in a configuration that has only one NAS Gateway, the NAS Gateway regards itself as a cluster of one.
Clusters are configured in any of the following ways: Network configuration: In this configuration, the SC1 ports of each NAS Gateway are connected to one management network, and the SC2 ports to a different management network. Both networks use different subnets. This configuration can be used for either a two-node cluster or a multiple-node cluster. Direct configuration: In this configuration, two nodes are directly connected to each other through crossover cables that are provided in ONStor accessory kit. The cables allow the NAS Gateways to support synchronization and heartbeat in the cluster. This configuration is used only for a two-node cluster. Hybrid configuration: In this configuration, nodes are connected to each other through a combination of methods on the SSCs management ports. One SSC port on each NAS Gateway connects into a management network, and the other SSC port on each NAS Gateway connects the nodes directly using crossover cables. Both connections support synchronization and heartbeat in the cluster. This configuration is used only for a two-node cluster.
Note! Regardless of which configuration you use, to ensure full redundancy both NAS Gateways in the cluster must have the same connectivity to the IP data network and SAN resources.
690-0018-0001B1
6-4
Figure 6-1 shows the cluster topology of a two-node cluster. The NAS Gateways connect into the SAN through FibreChannel ports. Each NAS Gateway has two connections to a FibreChannel switch. The cluster of NAS Gateways is indicated by the dark grey rounded rectangle. This cluster contains the NAS Gateways Gateway 1 and Gateway2 that are connected to the management network through their 10/ 100 management ports. The management network supports the synchronization and heartbeat signal between all NAS Gateways in the cluster.
Windows Client
IBM Compatible
Linux Client
W orkstation
UNIX Client
W orkstation
Gigabit Ethernet Data Network
Management Network NAS Gateway Gateway 2
NAS Gateway Gateway 1
Storage Area Network
Disk a rr ay
Disk a rr ay
Disk a rr ay
Disk a rr ay
Consolidated NAS and SAN Storage
Figure 6-1 Cluster Configuration Supported through Cluster Network
690-0018-0001B1
6-5
The clients on the Gigabit Ethernet data network are connected to Gigabit Ethernet switches. These switches are connected to both NAS Gateways to enable redundancy. In the example, the management port connections enable cluster configuration for: Heartbeat signal between the two NAS Gateways. Arbitration between the NAS Gateways for the role of a new PCC if an event takes the previous PCC offline. State change notification. Convergence on an Network Time Protocol (NTP) server and synchronization of the NTP time signal between the NAS Gateways. An external NTP server is supported if your cluster is in a hybrid or management network.
690-0018-0001B1
6-6
The Primary Cluster Controller (PCC)

The Primary Cluster Controller is the NAS Gateway on which you configure the cluster. It is a role that can be assumed by any NAS Gateway in the cluster. The Primary Cluster Controller owns the master cluster database and is responsible for propagating the cluster-wide configuration and topology to the rest of the NAS Gateways in the cluster. When an event requires an update of the master cluster database, the Primary Cluster Controller serializes those changes and updates the cluster database on all the nodes in the cluster.
Note! All nodes have the same instance of the cluster database
Only one Primary Cluster Controller exists at a time in each cluster. When the NAS Gateway reboots, or goes offline, an election process starts to find the NAS Gateway that will assume the Primary Cluster Controller role. If a new Primary Cluster Controller is established, the second Primary Cluster Controller does not relinquish its responsibilities when the previous Primary Cluster Controller comes back online. When a Primary Cluster Controller drops offline, it reboots as a cluster node and can be elected as the Primary Cluster Controller again if an event causes a failure of the current Primary Cluster Controller.
Primary Cluster Controller Election

The Primary Cluster Controller is elected. When more than one node exists in the cluster, each NAS Gateway is a candidate for the role of Primary Cluster Controller. To determine which NAS Gateway should be the Primary Cluster Controller, an election process occurs in which each NAS Gateway arbitrates for the role of Primary Cluster Controller. The NAS Gateway performs some calculations and elects the Primary Cluster Controller. Node availability has a direct effect on the election process for the Primary Cluster Controller: In a cluster of one there is no election process because the NAS Gateway is its own Primary Cluster Controller. In a cluster of two nodes, if one node is down, the second node in the cluster assumes the role of PCC.
690-0018-0001B1
6-7
In a multinode cluster, nodes negotiate for the role of the PCC when the PCC becomes unavailable.
When the PCC is elected, the other NAS Gateways synchronize their cluster database with the PCC so that each node in the cluster contains an identical cluster configuration. After this synchronization is complete, the cluster is online and available to provide high availability of file services.
Primary Cluster Controller in Runtime

When the NAS Gateways are in runtime, the PCC governs few aspects of configuration and management in the cluster. During runtime, the PCC accepts configuration and management commands that are issued on it or on other cluster nodes. The PCC is also a cluster node that serves file system I/O to and from clients. Runtime configuration changes to the cluster, such as the addition or deletion of a node, can trigger another update or synchronization of the cluster database. When a new node is added to the cluster it performs a serial synchronization with the PCC, so that each node has an identical view of the configuration, same instances of the cluster database, and same members list.
Note! You cannot merge different cluster databases. Therefore, when a new node is added to the cluster, its current database is removed and replaced by the cluster it joins. All previous configuration is lost (a few exceptions are SSC interfaces, default SSC route, NAS Gateway name, and NTP server configurations.
690-0018-0001B1
6-8
The Cluster Database

The cluster database is the repository of all configuration information for all NAS Gateways in the cluster and is owned by the PCC. However, it propagates the cluster database to other nodes in the cluster, so they all contain the same information. If a node resets, the node announces its presence and re-synchronizes with the PCC. However, if the node leaves the current cluster, it resets as a cluster of one and it uses an unconfigured version of the cluster database. After the cluster is configured, the master cluster database is kept coherent with other NAS Gateways in the cluster and the PCC synchronizes the cluster databases on all NAS Gateways if anything changes. However, a node failure can change the state of cluster entities. When a node fails, the node and virtual servers can be temporarily offline. If virtual servers are protected, they will failover to the other NAS Gateway. If virtual servers are not protected, they remain offline until the NAS Gateway reboots and comes online in the cluster.
690-0018-0001B1
6-9
Clusters and Time Sources

When you configure a cluster, its NAS Gateways require a consistent time signal so that there is no variance on the time stamps between NAS Gateways. In a cluster of multiple NAS Gateways, the NAS Gateways need to synchronize with a valid and reliable NTP time server. The NAS Gateway uses NTP v4 as the time synchronization protocol between the NAS Gateways. The optimal time source for the cluster is external NTP server. In all cluster types, an external time source should be referenced from the SSC interface.
690-0018-0001B1
6-10
690-0018-0001B1
Chapter 7: Cluster Management Commands

This chapter details the following topics: Cluster Configuration Commands on page 7-2 Adding NAS Gateways to a Cluster on page 7-2 Deleting NAS Gateways from a Cluster on page 7-3 Committing Changes to a Cluster on page 7-4 Uncommitting Changes from the Cluster Database on page 7-5 Displaying the Cluster Configuration on page 7-5 Adding a NAS Gateway Group to a Cluster on page 7-6 Moving a NAS Gateway Into or Out of a Group on page 7-7 Moving a NAS Gateway Into or Out of a Group on page 7-7 Deleting a NAS Gateway Group from a Cluster on page 7-8 Deleting a Cluster on page 7-9
690-0018-0001B1
ONStor 2200 NAS Gateway Cluster Configuration GuideONStor Bobcat
7-2
Cluster Configuration Commands

Clusters require you to issue specific commands for negotiation of the cluster controllers and admission of nodes to the cluster. Commands are issued from any node to configure and manage the cluster. The cluster add and cluster delete commands are issued from any node of the same NAS Gateway that gives its name to the cluster. The node for whom the cluster is named cannot be deleted from the cluster.
Adding NAS Gateways to a Cluster

By default, each NAS Gateway boots up as a cluster of one. To add other NAS Gateways to the cluster, you need to issue commands from the command line of the first NAS Gateway that boots. You can manually add a NAS Gateway to a cluster and post its name in the cluster member list by issuing the cluster add nasgateway command. In the multiple NAS Gateway cluster configuration the following occurs: The cluster adopts the node name of the NAS Gateway from which the cluster add command is issued. The cluster controller is elected after the cluster commit command is issued. The NAS Gateway becomes active after you issue the cluster commit command. Each NAS Gateway you add to the cluster synchronizes with the cluster controller and updates its cluster database.
To add individual NAS Gateways to a cluster, follow this procedure: Step 1: Issue this command:
cluster add nasgateway NASGATEWAY1 -a IPADDAR
where:
NASGATEWAY1 is the unique node name of the NAS Gateway that you are adding to the cluster. -a IPADDR is an argument that specifies the IP address of the
NAS Gateway. This is usually the interface associated to the interface SC1.
ONStor 2200 NAS Gateway Cluster Configuration GuideONStor Bobcat NAS Gateway
7-3
Note! The cluster add nasgateway command needs to be run on a node in the cluster to which other NAS Gateways are being added. Suppose you are adding Gateway2 to the cluster in which Gateway1 is. You need to run the cluster add nasgateway command on Gateway1, and name Gateway2 in the arguments to the command. Issue the cluster add nasgateway and cluster delete nasgateway commands from the same NAS Gateway.
Step 2: After adding all NAS Gateways to the cluster, run the commit command.
Deleting NAS Gateways from a Cluster

When you delete a NAS Gateway from a cluster, it is removed from the cluster database. The NAS Gateways node name is also removed from the cluster members list. To delete a NAS Gateway issue the cluster delete nasgateway command. Removing a NAS Gateway from a cluster with the cluster delete nasgateway command causes the NAS Gateway to reboot. When the NAS Gateway reboots, the NAS Gateway deletes all the configuration information from its cluster database. Therefore, before you delete a NAS Gateway, move the configuration information to another node by moving the virtual servers currently hosted by the NAS Gateway.
690-0018-0001B1
7-4
After you have moved the virtual server, issue the following command to delete the NAS Gateway from the cluster:
cluster delete nasgateway NASGATEWAY1 -a IPADDR
where:
NASGATEWAY1
is the name of the NAS Gateway
-a IPADDR is an argument that specifies the IP address of the NAS Gateway that you are deleting
Committing Changes to a Cluster

The cluster commit command is required after a cluster add or cluster delete command, but not at any other time. Cluster changes can be configured without being active, but they do need a commit action to be processed. Table 7-1 displays each cluster command and whether it requires the cluster commit command.
Table 7-1 : Commands Requiring Cluster Commit Command Name
cluster add NAS Gateway cluster delete NAS Gateway cluster add group cluster delete group cluster move cluster show cluster cluster show group Yes Yes No No No No No
Commit Requirement
To commit cluster changes to the cluster database, issue the following command:
cluster commit
7-5
Uncommitting Changes from the Cluster Database

When cluster changes have been made but not committed to the cluster database, you can undo those changes by issuing the cluster uncommit command. Some cluster commands require the cluster uncommit command to invalidate their settings if they have not been committed to the cluster database. Table 7-2 displays each cluster command and whether it requires the cluster uncommit command to be changed.
Table 7-2 : Commands Requiring Cluster Uncommit Command Name cluster add NAS Gateway cluster delete NAS Gateway cluster add group cluster delete group cluster move cluster show cluster cluster show group
Yes Yes No No No No No
Requires Uncommit?
To remove parameters that have not been committed to the cluster database, issue the following command:
cluster uncommit Note! The cluster uncommit command does not remove changes that have already been committed to the cluster database.
Displaying the Cluster Configuration

You can display the cluster configuration by issuing the cluster show cluster command. The cluster configuration shows the following information: Name of the cluster. The cluster inherits the name of the node name on which you built the cluster. State of cluster. Valid values are ON or OFF.
690-0018-0001B1
7-6
Node name of each NAS Gateway in the cluster. IP address of the NAS Gateways that form the cluster. The IP addresses listed are the same as the SSC management IP network of each NAS Gateway. The operational state of each NAS Gateway in the cluster. Valid values are UP or DOWN. The role that each NAS Gateway has as cluster controller. Valid values are YES if the NAS Gateway listed is the cluster controller, or NO if the NAS Gateway listed is just a node in the cluster.
cluster show cluster
To display the cluster configuration, issue the following command:
Adding a NAS Gateway Group to a Cluster

NAS Gateway groups are smaller logical areas in the cluster in which virtual servers can failover and move. By default, virtual servers can failover only within their NAS Gateway group. Group boundaries are enforced for automatic failover events. You can override the boundaries by explicitly specifying a target for move or load balancing events. This is manual failover using the vsvr move command.
NAS Gateway group boundaries do not apply to control messages, cluster heartbeat signals, and NTP time signals. Each NAS Gateway group can contain one or more NAS Gateways. When the NAS Gateway starts up, it is configured as part of the default NAS Gateway group, but you can create a different NAS Gateway group. For a two-node cluster, both NAS Gateways must be in the same NAS Gateway group otherwise redundancy and failover are not supported.
Note! Each cluster can support a maximum of four Gateway groups, excluding the default NAS Gateway group, regardless of how many NAS Gateways are in the cluster.
To add or create NAS Gateway groups in a cluster, follow this procedure: Step 1: Issue this command:
cluster add group GROUP1
7-7
Step 2: Repeat Step 1 for more filer groups that you want to create.
Moving a NAS Gateway Into or Out of a Group

When you first create a NAS Gateway group, the group is empty. To populate a newly created NAS Gateway group with NAS Gateways, you must explicitly move individual NAS Gateways into the new NAS Gateway group. By default, NAS Gateways virtual servers do not move where the NAS Gateway is moved. However, you can specify that the virtual servers move with it by specifying the -a option. If there are other NAS Gateways online in the group, the virtual servers will failover to those NAS Gateways if the -a option is not used. Otherwise, these virtual servers are taken offline and become owned by the virtual NAS Gateway. When NAS Gateways are added to a NAS Gateway group, they support failover of virtual servers within the group. NAS Gateway group boundaries are enforced so that virtual servers do not failover from one NAS Gateway group to another. However, you can explicitly move a virtual server to a different NAS Gateway group using the vsvr move command.
Note! NAS Gateways can be added to a group regardless of whether they are UP or DOWN. The act of moving a NAS Gateway to a new group does not trigger a DOWN NAS Gateway to reboot and transition to the UP state. If you add a DOWN NAS Gateway to a group, that NAS Gateway remains DOWN till the NAS Gateway reboots.
You can move a NAS Gateway in and out of a group by issuing the cluster move nasgateway command. You can move one NAS Gateway at a time out of a NAS Gateway group. The NAS Gateway group itself remains configured even if no NAS Gateways remain in the NAS Gateway group. To manually move a NAS Gateway from a NAS Gateway group, run the following command:
cluster move nasgateway NASGATEWAY1 -g GROUP1 [-a]
is the name of the target NAS Gateway group to which you are moving the NAS Gateway NASGATEWAY1.
-g GROUP1
You use the-a argument to move all virtual servers with the NAS Gateway. If you do not specify -a, the NAS Gateway is
690-0018-0001B1
7-8
moved to a new NAS Gateway group, but the virtual servers that are assigned to the NAS Gateway are not moved to the new NAS Gateway group.
Deleting a NAS Gateway Group from a Cluster

You can delete a NAS Gateway group from a cluster by issuing the cluster delete group command. You cannot delete a NAS Gateway group if it still contains NAS Gateways. If you attempt to delete a NAS Gateway group that is not empty, the NAS Gateway will post an error message stating that the requested operation failed because the NAS Gateway group is not empty. To delete a NAS Gateway group from the cluster, follow this procedure: Step 1: Issue this command to move the NAS Gateways to a different NAS Gateway group:
cluster move nasgateway NASGATEWAY1 -g GROUP1 -a
Step 2: Repeat Step 1 for all the NAS Gateways in the NAS Gateway group that you want to delete. Step 3: After all NAS Gateways have been moved out of the NAS Gateway group you are deleting, issue this command to delete the empty NAS Gateway group:
cluster delete group GROUP1
Displaying a NAS Gateway Group Configuration

You can display the configuration of a NAS Gateway group by running the cluster show group command. This command displays the following information: Name of each group that is configured in the cluster. Name of the default group, called default in the cluster. Node names of the NAS Gateways that are part of each NAS Gateway group. Virtual servers that are currently hosted by NAS Gateway groups in the cluster.
7-9
Note! Management virtual servers always stay with theirs NAS Gateway. Therefore, a management virtual server will appear in the same NAS Gateway group that holds its NAS Gateway.
To display the NAS Gateway group configuration, issue the following command:
cluster show group
Deleting a Cluster
Deleting a cluster consists of moving all virtual servers to the NAS Gateway that gave its name to the cluster, then removing all the other NAS Gateways one by one from the cluster. All cluster commands should be run from the original NAS Gateway.
Note! To find which NAS Gateway is the original gateway, issue the cluster show cluster command and check the cluster name.
To delete a cluster, follow this procedure: Step 1: From the NAS Gateway you want to delete, move all virtual servers, to the original NAS Gateway. You can move virtual servers by issuing the vsvr move command. For information about this command, see the Virtual Servers chapter in the ONStor 2200 NAS Gateway System Administrators Guide. Step 2: On the NAS Gateway you want to delete, issue the system time ntp server -d ip command to remove the NTP servers address. To find out about the IP address of the NTP server, run the system time show -v command. Ignore the default entry 127.127.1.0.
Note! To find which is the original NAS Gateway, run the cluster show cluster command.
Step 3: When all virtual servers have been moved, issue the cluster delete nasgateway command from the original NAS Gateway to remove the NAS Gateway you want to delete. For example, to delete Gateway3 from the cluster:
cluster delete nasgateway Gateway3 -a sscip
690-0018-0001B1
7-10
sscip is the IP that associated with the NAS Gateway that is displayed as the result of cluster show cluster command.
Step 4: To commit this change, run the following command from the original NAS Gateway:
cluster commit
When the command completes, the deleted NAS Gateway will no longer be in the cluster. When a NAS Gateway is deleted from a cluster, it will reboot and come back online in standalone mode with its own cluster database. When the deleted NAS Gateway reboots, its cluster database will contain the following information: Node name. SSCs management port IP address. Management virtual server. NTP configuration if not removed as described in Step 2. Default management route.
Note! If you are uninstalling the NAS Gateway, at this point it is safe to power off the deleted NAS Gateway and remove its cabling.
Step 5: Repeat Steps 1-4 if other NAS Gateways need to be deleted from the cluster. Step 6: On the NAS Gateway that will remain configured, you can delete empty groups by issuing the cluster delete group command. For example, to delete the NAS Gateway group GROUP1 issue the command as shown:
cluster delete group GROUP1
Chapter 8: Configuring Clusters

This chapter details the procedure for configuring clusters on a separate network configuration, direct configuration, and the hybrid configuration. Serial Port Settings for Initial Configuration on page 8-2 Prerequisites of Configuration on page 8-3 Cluster Creation Procedure on page 8-5 Connecting Multiple Nodes on page 8-8
690-0018-0001B1
8-2
Serial Port Settings for Initial Configuration

NAS Gateways do not have preconfigured IP addresses nor do they use DHCP. Therefore, you need to connect to a serial port to do the initial NAS Gateway configuration at installation time, which includes setting up the name and IP address for the NAS Gateway. However, if the NAS Gateway is already on the network, you can follow the upgrade process by initiating a secure shell (SSH) session to the management IP Address of either SC1 or SC2. A serial cable is supplied with every new NAS Gateway, and you can use a terminal emulation application, such as a hyper terminal, to connect to the console of the NAS Gateway through its serial port. The settings of the serial port with an RS232 cable are as follows: Baud Rate: 57600 (56 K) Data Bits: 8 Parity: None Stop Bits: 1 Flow Control: None
8-3
Prerequisites of Configuration
Before you start with the cluster configuration, ensure that the following conditions are met: The cluster configuration commands are run from the same node. Each node is running the same version of software. Each NAS Gateway has redundant paths to the same IP clients and storage area network (SAN) resources. The NAS Gateways Gigabit Ethernet interfaces are on the same subnet to support client connectivity. The NAS Gateways management IP interfaces are on the same subnet (SC1s on one subnet and SC2s on another subnet) to support NAS Gateway-to-NAS Gateway connectivity and synchronization. The subnet can be the same as, or different than, the Gigabit Ethernet interfaces. All LUNs in the cluster are labeled by the NAS Gateway on which you are creating the cluster. Network configuration: In a network configuration, all NAS Gateways in the cluster are configured on the same subnet. The cluster network is configured on the management IP ports on the SSC. You can configure two external NTP servers. Direct configuration: Since external NTP server cannot be reached from the network configuration, one NAS Gateway can serve as the NTP server. Configure the NTP server on the NAS Gateways that will join the cluster, providing one of the management IP addresses (associated with interfaces SC1 or SC2) of the NAS Gateway that is designated as that internal NTP server. You can also set up a secondary NTP server using the IP address associated with the second interface. Hybrid configuration: In a hybrid configuration, you can configure an external NTP server that can be reached through the management port connected to the network, and an internal NTP server (IP address of the NAS Gateway designated to serve as the server) that can be reached through the management port that is directly connected to the other Gateway.
Based on the configuration you have, ensure that the following exist:
690-0018-0001B1
8-4
For illustrative purposes, we will use the following details in our example: The NAS Gateways are named Gateway1 and Gateway2. Gateway1 has 192.168.172.1 and 192.168.173.1 as its SC1 and SC2 management port IP addresses. Similarly, Gateway2 has 192.168.172.2 and 192.168.173.2 as its SC1 and SC2 management port IP addresses. The cluster will be configured on Gateway1. The NTP server addresses for the cluster are 192.168.172.3 and 192.168.173.3.
Note! Once the NAS Gateway is running in cluster mode, the management IP addresses on the SC1 and SC2 interface cannot be changed. Management IP address on the SC1 or SC2 interface can be changed only when the NAS Gateway is in standalone mode.
8-5
Cluster Creation Procedure

Use the following steps to create clusters. You can add as many NAS Gateways as you require. We are using a two-node cluster in our example and using the assumptions given earlier: Step 1: On both Gateway1 and Gateway2, set the correct time by issuing the system time set command. For example, to set the time in the cluster to October 31, 2003 at 11:59:30 p.m., issue the command as follows:
system time set 200310312359.30 Note! After this step both the Gateways show the same time.
Step 2: On Gateway1, use one of the following methods, depending on the configuration you are in: If you are in a network or hybrid configuration, add the external NTP server using the system time ntp server command for all NAS Gateways. For example, to configure the NAS Gateways NTP client to use the time signal from the time source at 192.168.172.3 (SC1 subnet), and 192.168.173.3 (SC2 subnet) issue the following commands on both:
system time ntp server -a 192.168.172.3 system time ntp server -a 192.168.173.3
If you are in a direct configuration, issue the system time ntp disable command to disable the NTP client and use the system's hardware clock.
Step 3: On Gateway2, add Gateway1 as the NTP server using the system time ntp server command. For example, issue the following command from Gateway1.
system time ntp server -a 192.168.173.1
Step 4: Verify the configuration on all NAS Gateways using the system time show -v command.
690-0018-0001B1
8-6
127.127.1.0 is the hardware clock, and it is normal for it to appear there. After a few minutes, an asterisk will appear by the IP address of the external NTP server (Gateway1) or Gateway1's IP address (Gateway 2, etc.), and the system clocks will begin drifting to an accurate setting.
Note! The system times will not immediately correct themselves; NTP will adjust the hardware clocks over a short period of time (typically fifteen minutes) until they are all synchronized.
Step 5: After synchronizing the time, from Gateway1, add Gateway2 to the cluster by running the cluster add nasgateway command. For example, issue the following command from Gateway1:
cluster add nasgateway Gateway2 -a 192.168.172.2
Step 6: From Gateway1, run the cluster commit command to activate the cluster configuration. The cluster then elects a Primary Cluster Controller between Gateway1 and Gateway2.
Note! At this point, Gateway2 reboots. When it comes back online, it will be in the cluster.
Step 7: To verify that NAS Gateways have been added to the cluster, issue the cluster show cluster command to view the cluster configuration. Step 8: To conclude the cluster configuration process, ensure the following: One NAS Gateway is labeled as the PCC to indicate that it is assuming the Cluster Controller role. All NAS Gateways in the cluster are listed by node name and IP address. All NAS Gateways should be in the UP state.
This concludes the cluster configuration process.
8-7
Note! At this point the cluster has been created with all NAS Gateways in the same cluster and in the default NAS Gateway group. However, file services have not been configured within the cluster.
Figure 8-1 illustrates clustering through a hybrid configuration.
Windows Client
IBM Compatible
Linux Client
W orkstation
UNIX Client
W orkstation
Gigabit Ethernet Data Network Time Server

W orkstati o n
Gigabit Ethernet switch
Gigabit Ethernet switch
Management IP Networks
Hub NAS Gateway Gateway 2 NAS Gateway Gateway 1
Fibre Channel switch
Fibre Channel switch
Storage Area Network
Disk a rr ay
Dis k ar ray
Disk a rr ay
Disk a rr ay
Consolidated NAS and SAN Storage
Figure 8-1 Clustering through a hybrid configuration
690-0018-0001B1
8-8
Connecting Multiple Nodes

Typically, if you use the network configuration, you can connect multiple nodes, but in a direct or hybrid configuration you can connect only two nodes. However, even if you currently have direct or hybrid connection, you can add multiple nodes, such as Gateway3, and Gateway4 by using CAT-5 Fast Ethernet cables, and hub. To do this, instead of using the crossover cable to connect the ports of SC1 of Gateway1 to SC1 of Gateway2, connect the SC1 ports of each NAS Gateway with the CAT-5 Fast Ethernet cables to a hub.
A-1
Appendix A: Console Cable Pinouts

This appendix documents the pinouts for the ONStor NAS Gateways console cable. If cables are lost, damaged, or destroyed, these pinouts should help you create replacement cables. This appendix contains the following sections: What are the Pinouts? on page 2 Where Should the Cable Be Connected? on page 3
690-0018-0001B1
A-2
What are the Pinouts?

The console cable includes certain wires that carry specific signals. When creating a connector for the cable, it is important that pins in the connector align with the correct wires so that the correct signals are carried between the management console and the NAS Gateway. To create a direct connect management cable for the CONSOLE port on the rear of the chassis, you need to connect a male DB9 connector to a female null modem cable. Table A-A-1 shows the pinouts for the console cable. The listed pinouts are industry standards.
Table A-1 : Pinouts for DB-9 to Null Modem Cable for CONSOLE Port Pin
1 2 3 4 5 6 7 8 9 NC RX TX NC GND (on-board) NC RTS CTS NC
Signal
690-0018-0001B1
A-3
Where Should the Cable Be Connected?

Attach one end of the management cable to the management console. Attach the male DB connector to the CONSOLE port on the NAS Gateway to connect the management console to the NAS Gateway. See Figure A-1.
Console Access Port
Figure A-1 Console Access Port
690-0018-0001B1
A-4
690-0018-0001B1
B-1
Appendix B: Safety Information

This appendix details the safety considerations when installing, operating, and performing maintenance on the ONStor 2200 family of NAS Gateway products. This appendix contains the following topics: Heat Considerations on page 2. Electrostatic Discharge Considerations on page 2. Equipment Weight Considerations on page 2. Electrical Considerations on page 3. Optical Considerations on page 4. Eye Safety on page 4.
For more information, see the listed sections.
690-0018-0001B1
B-2
Safety Considerations
We recommend that you read and follow the safety considerations listed in these sections while working with the ONStor 2200 NAS Gateway (NAS Gateway). Warning! Failure to follow the information in the following sections can result in damage to the product, personal injury, or loss of life.
Heat Considerations
To reduce the risk of personal injury from hot surfaces, whenever you are working inside the chassis or with components that have removed from the chassis, allow sufficient time for the components to cool before touching them.
Electrostatic Discharge Considerations

Caution! ESD Sensitive Components! This product contains electronic components that are sensitive to electrostatic discharge (ESD). To avoid damage to the product or its components, ensure that you are wearing an ESD wrist strap, or using an appropriate method of ESD protection prior to handling the product, its modules, or any of its components. Also, when removing modules or NAS Gateway components, ensure that you set them on a grounded rubberized mat or other ESD safe work surface.
Equipment Weight Considerations

To reduce the risk of personal injury or damage to the product, ensure that the equipment is properly supported or braced when installing or removing the chassis, or when working with the NAS Gateway or any of its modules or components.
690-0018-0001B1
B-3
Electrical Considerations
To reduce the risk of loss of life, personal injury, or damage to the product, follow these considerations when working with the NAS Gateways electrical components. Power Supplies This product contains multiple power supplies. The product can operate effectively on one power supply. When operating in a non-error condition, the units Fault LED (FLT) LED has a continuous a green light. Error conditions are indicated by a continuous red FLT LED. Caution! This product contains multiple power supplies. If you fail to activate all power supplies, the product will operate correctly, but you will lose redundancy in the unlikely event that a power supply fails. Whenever you are powering on the NAS Gateway, we recommend that you activate all power supplies to keep redundancy. Power Cords Warning! This product might have multiple power supply cords. To reduce the risk of electrical shock, disconnect all power supply cords before servicing the unit. Grounding This equipment is designed for connection to a grounded outlet. The power cords are terminated with an IEC 320 plug for insertion into the wall socket (facility power). The grounding type plug is an important safety feature. To avoid the risk of electrical shock or damage to the product, do not disable or alter the power cord or plug.
690-0018-0001B1
B-4
Lithium Battery Warning! This product contains one or more lithium batteries. If the battery is misused damaged, or incorrectly installed or replaced, the danger of explosion exists. To avoid personal injury or damage to the product, do not attempt to recharge the battery, disassemble it, or dispose of it in a fire. Ensure that you dispose of the battery properly.
Optical Considerations
This product has four fiber optic connections on the Gigabit Ethernet File Processing module and four fiber optic connections on the FibreChannel Storage Processing module. The optical transceivers support a Class 1 laser to drive signals on the links. The laser operates at the following specifications: output power: < 1.0 mW wavelength: 830 nm (minimum), 850 nm (nominal), 860 nm (maximum) pulse duration: 800 pS (minimum), 4nS (maximum) frequency: 125 MHz (minimum), 625 MHz (maximum)
Class 1 laser devices are supported for connection to other Class 1 Laser devices only.
Eye Safety
To reduce the risk of personal injury, always try to avoid pointing the NAS Gateways laser signal directly into your eye. However, casual laser contact with the human eye poses no threat. Warning! Laser Radiation To reduce the risk of personal injury, avoid pointing the NAS Gateways laser directly into your eye. The laser signal supported on the NAS Gateways optical transceivers have been categorized as a Class 1 laser. Per the IEC 825-1: 1993 and CDRH, 21 CFR Laser Safety Requirements the NAS Gateways laser is considered safe for casual contact with the human eye.
690-0018-0001B1
B-5
Always operate the laser components in a manner compliant with the IEC 825-1: 1993 and CDRH, 21 CFR Laser Safety Requirements. Misuse of the laser or prolonged exposure to the human has the possibility of causing personal injury.
690-0018-0001B1
B-6
690-0018-0001B1
C-1
Appendix C: Approvals and Certifications

This appendix details the regulatory notices, agency approvals, and certifications for the ONStor 2200 family of NAS Gateway products. ONStor declares that its models of ONStor 2000 NAS Gateway comply with the following: European Union Evaluation on page 2. ETL/cETL Listing for North America on page 3. FCC Declaration of Conformity, United States on page 4. Voluntary Control Council for Interference (VCCI), Japan on page 6. Australian Communications Authority (ACA) Compliance on page 6.
For more details, see the listed sections.
690-0018-0001B1
ONStor 2200 NAS Gateway Cluster Configuration GuideONStor
C-2
Compliances
ONStor 2200 NAS Gateway products comply with the standards of: European Union Evaluation ETL/cETL Listing for North America FCC Declaration of Conformity, United States Voluntary Control Council for Interference (VCCI), Japan Australian Communications Authority (ACA) Compliance
European Union Evaluation

The ONStor family of NAS Gateway products complies with the European Union standards shown in Table C-1.
Table C-1 : European Union Standards Designation

CENELEC EN 55022:1998 CENELEC EN 55024:1998
Standard
Limits and Methods of Measurement of Radio Interference Characteristics of Information Technology Equipment. Information Technology Equipment - Immunity Characteristics Limits and Methods of Measurement CISPR 24:1997, Modified. Safety of Information Technology Equipment, Including Electrical Business Equipment. Electromagnetic compatibility (EMC). Limits for harmonic current emissions (equipment input current up to and including 16 A per phase) Electromagnetic compatibility (EMC). Limits for harmonic current emissions (equipment input current up to and including 16 A per phase)
CENELEC EN 60950-1 EN 61000-3-2:2001 (IEC 1000-3-2) EN 61000-3-3:2000 (IEC 1000-3-3)
690-0018-0001B1
C-3
The Commonwealth of Europe (CE) mark affixed to each model of ONStor 2200 NAS Gateway indicates its compliance with the listed standards and the EMC Directive and the Low Voltage Directive of the European Union. Figure C-1 shows the CE mark.
Figure C-1 CE mark
Caution! The ONStor 2200 NAS Gateway is a Class A product and might cause radio interference in a domestic environment. If such interference occurs, the user may be required to take adequate measures.
ETL/cETL Listing for North America

The ONStor 2200 family of NAS Gateway products complies with the Canadian standards shown in Table C-2.
Table C-2 : United States and Canadian Safety Standards Designation
ANSI/UL 6950-1 CAN/CSA C22.2 No. 6950-1
Standard
UL Standard for Safety for Information Technology Equipment, Part 1 Safety of Information Technology Equipment, Including: Electrical Business Equipment First Edition.
The Edison Test Laboratories (ETL/cETL) mark affixed to each ONStor 2200 NAS Gateway unit indicates its compliance with the listed standards. Figure C-2 shows the ETL/cETL mark.
690-0018-0001B1
C-4
Figure C-2 ETL Mark
FCC Declaration of Conformity, United States

The ONStor 2200 family of NAS Gateway products complies with the United States of Americas Federal Communications Commissions (FCC) Part 15 standards shown in Table C-3.
Table C-3 : FCC Conformity Standards Designation
FCC Part 15, Class A
Standard
Radio Frequency Devices: 15.107 Conducted Limits 15.109 Radiated Emissions Limits
690-0018-0001B1
C-5
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: This device may not cause harmful interference, and This device must accept any interference received, including interference that may cause undesired operation. Warning! Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the users authority to operate the equipment. This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy, and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense. The Federal Communications Commissions (FCC) mark affixed to each ONStor 2200 NAS Gateway unit indicates its compliance with the listed standards. Figure C-3 shows the FCC mark.
Figure C-3 FCC mark
690-0018-0001B1
C-6
Voluntary Control Council for Interference (VCCI), Japan

The ONStor 2200 family of NAS Gateway products complies with the VCCI emission certification in Japan shown in Table C-4.The Voluntary Control Council for Interference (VCCI) mark affixed to each ONStor 2200 NAS Gateway unit indicates its compliance with the listed standards. Figure C-4 shows the VCCI mark.
Table C-4 : VCCI Standard for Japan Designation

VCCI V-2/97.04 A
Standard
Emission limits and methods for ITE-Class A.
Figure C-4 VCCI mark
Australian Communications Authority (ACA) Compliance

The ONStor 2200 family of NAS Gateway products complies with the Australian Communications Authoritys (ACA) EMI requirements shown in Table C-5.
Table C-5 : Australian Communications Authority EMI Requirements Designation

AS/NZS 3548:1995
Standard
Limits and Methods of Radio Disturbance Characteristics of Information Technology Equipment.
690-0018-0001B1
C-7
Table C-5 : Australian Communications Authority EMI Requirements Designation

AS/NZS 3260:1993
Standard
Approval and Test Specification - Safety of Information Technology Equipment, including: Electrical business equipment, incorporating
Amendment 1 Amendment 2 Amendment 3
The C-tick or RCM Mark affixed to each ONStor 2200 NAS Gateway unit indicates its compliance with the listed standards. Figure C-5 shows the C-tick mark.
Figure C-5 ACA C-tick mark
690-0018-0001B1
C-8
CB Scheme Certificate
The ONStor 2200 family of NAS Gateway products complies with the applicable requirements of the International Standards shown in Table C-6.
Table C-6 : CB Scheme Certificate Designation

IEC 6950-1
Standard
Information Technology Equipment, Part 1
690-0018-0001B1

OnStor NAS Gateway Installation and Cluster Configuartion

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

OnStor NAS Gateway Installation and Cluster Configuartion

Transféré par

Droits d'auteur :

Formats disponibles

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

Chapter 1: Setup the ONStor NAS Gateway Hardware..................................... 1-1

Chapter 2: Preinstallation Tasks........................................................................... 2-1

Chapter 3: Firmware Installation and Configuration......................................... 3-1

Chapter 4: Software Configuration ...................................................................... 4-1

Chapter 5: Installing Storage Arrays on a NAS Gateway .................................. 5-1

Chapter 6: Overview of Cluster Configuration ................................................... 6-1

Chapter 7: Cluster Management Commands ...................................................... 7-1

Chapter 8: Configuring Clusters........................................................................... 8-1

Appendix A:Console Cable Pinouts ..................................................................... A-1

Appendix B:Safety Information ............................................................................B-1

Appendix C:Approvals and Certifications .......................................................... C-1

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

Chapter 1: Setup the ONStor NAS Gateway Hardware

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

NAS Gateway Hardware Installation

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

This concludes the physical hardware installation of the NAS Gateway.

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

Chapter 2: Preinstallation Tasks

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

Preinstallation Planning and Tasks

Fibre Channel and SAN tasks:

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

Server access setup: -

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

Basic Installation Process

Virtual servers configuration: -

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

Administration: Adding at least one user with cluster administration privileges

System Support, Validation, and Documentation

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

Extended Installation Process

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

Chapter 3: Firmware Installation and Configuration

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

Connect to the ONStor NAS Gateway

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

NAS Gateway Startup

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

The ONStor Configuration Tool (OCT)

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

Table 3-1 : Contents of the ONStor Configuration Tool Task

Completing the OCT on page 3-6

Display current settings Commit changes

Exiting the OCT on page 3-16.

Completing the OCT

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

Figure 3-1 OCT Welcome Screen

ONStor Bobcat NAS Gateway Installation and Cluster Configuration

Figure 3-2 Main Menu

Configure Administrative Settings