Software Configuration Guide

Transcription

1 IBM Scale Out Network Attached Storage Version Software Configuration Guide GA

2 Note Before using this information and the product it supports, read the general information in the Notices section, the Warranty and Support Information document for your system and the IBM Environmental Notices and User Guide on the documentation CD. Edition Notice This edition applies to the IBM Scale Out Network Attached Storage, Version 1.5.2, and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2009, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents Figures v Tables vii Safety and environmental notices... ix Safety information ix Safety information statements x Safety notices and labels xvii Danger notices for IBM SONAS xviii Caution notices for IBM SONAS xx Environmental notices xxii How to send your comments.... xxv Chapter 1. Before installing Machines/Models Affected Prerequisite, concurrent, and companion requirements Chapter 2. Preinstallation planning sheet 3 Customer required information SSR required information Chapter 3. Prerequisites Chapter 4. Software configuration procedures Logging on to the management node Verifying that Nodes are ready Creating a CTDB Cluster List available disks Listing available disks by physical location Creating a second failure group Creating the GPFS File System Configure the DNS Server IP Addresses and Domains Configure Data Path IP Addresses Configure Data Path IP Address Group Attach the Data Path IP Address Group Configure the NAT gateway Removing a NAT gateway Configure the authentication method Configure for authentication using Active Directory 45 Configure for authentication using Lightweight Directory Access Protocol (LDAP) Configure for authentication using Samba PDC.. 51 Configure for NIS Configure local authentication Export the File Access Protocols Modify the Access Control List for the Shared folder 60 Schedule a periodic backup of the TDB IBM Tivoli Assist On-site (AOS) Enable IBM Tivoli Assist On-site (AOS) Setting up AOS service Chapter 5. Test Procedures Test the IBM SONAS Chapter 6. Connect the customer Ethernet network cables to the 2851-SIx interface nodes Chapter 7. Completing installation and configuration Appendix A. Time zone list Appendix B. Remote Connection to the Active management node Appendix C. Remote Access to the InfoCenter Appendix D. Local Access to the Information Center Appendix E. Glossary Appendix F. Accessibility features for IBM SONAS Notices Trademarks Homologation statement Electronic emission notices Federal Communications Commission (FCC) statement Industry Canada compliance statement Australia and New Zealand Class A Statement 125 European Union Electromagnetic Compatibility Directive Germany Electromagnetic Compatibility Directive People's Republic of China Class A Statement 127 Taiwan Class A Statement Taiwan Contact Information Japan Voluntary Control Council for Interference Class A Statement Japan Electronics and Information Technology Industries Association Statement Korean Communications Commission Class A Statement Russia Electromagnetic Interference Class A Statement Copyright IBM Corp. 2009, 2015 iii

4 Index iv IBM SONAS 1.5.2: Software Configuration Guide

5 Figures 1. Customer Ethernet connections to the 2851-SIx interface nodes PuTTY Security Alert InfoCenter Security Alert Copyright IBM Corp. 2009, 2015 v

6 vi IBM SONAS 1.5.2: Software Configuration Guide

7 Tables 1. Caution notice symbols xviii 2. Number of customer Ethernet connections and IP addresses that are required Rack locations SI2 management node 1 configuration information Remote support information Command-line interface (CLI) user information 7 7. DNS configuration information NAT configuration information CIDR Subnet Mask Information Authentication Method Information Active Directory Configuration Information LDAP Configuration Information Samba Primary Domain Controller (PDC) Configuration Information NIS Configuration Information File Access Protocol Information interface node Subnet Configuration Information interface node Network Configuration Information Quorum Nodes management node Location Information InfiniBand switch Serial Numbers interface node Location Information storage node Location Information IBM SONAS netgroup support SIx interface node Ethernet cable connections Copyright IBM Corp. 2009, 2015 vii

8 viii IBM SONAS 1.5.2: Software Configuration Guide

9 Safety and environmental notices Safety information Review the safety notices, environmental notices, and electronic emission notices for the IBM SONAS product before you install and use the product. The Safety Information publication contains all the safety information statements for IBM System x servers in English and other languages. You can find the publication on the publications CD or on the Support Portal. Before installing this product, read the Safety Information. Antes de instalar este produto, leia as Informações de Segurança. Pred instalací tohoto produktu si prectete prírucku bezpecnostních instrukcí. Læs sikkerhedsforskrifterne, før du installerer dette produkt. Lees voordat u dit product installeert eerst de veiligheidsvoorschriften. Ennen kuin asennat tämän tuotteen, lue turvaohjeet kohdasta Safety Information. Avant d'installer ce produit, lisez les consignes de sécurité. Vor der Installation dieses Produkts die Sicherheitshinweise lesen. Prima di installare questo prodotto, leggere le Informazioni sulla Sicurezza. Copyright IBM Corp. 2009, 2015 ix

10 Les sikkerhetsinformasjonen (Safety Information) før du installerer dette produktet. Antes de instalar este produto, leia as Informações sobre Segurança. Antes de instalar este producto, lea la información de seguridad. Läs säkerhetsinformationen innan du installerar den här produkten. Bu ürünü kurmadan önce güvenlik bilgilerini okuyun. Safety information statements Important: Each caution and danger statement in this document is labeled with a number. This number is used to cross reference an English-language caution or danger statement with translated versions of the caution or danger statement in the Safety Information document. x IBM SONAS 1.5.2: Software Configuration Guide

11 For example, if a caution statement is labeled Statement 1, translations for that caution statement are in the Safety Information document under Statement 1. Be sure to read all caution and danger statements in this document before you perform the procedures. Read any additional safety information that comes with the server or optional device before you install the device. Statement 1 DANGER Electrical current from power, telephone, and communication cables is hazardous. To avoid a shock hazard: v Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. v Connect all power cords to a properly wired and grounded electrical outlet. v Connect to properly wired outlets any equipment that will be attached to this product. v When possible, use one hand only to connect or disconnect signal cables. v Never turn on any equipment when there is evidence of fire, water, or structural damage. v Disconnect the attached power cords, telecommunications systems, networks, and modems before you open the device covers, unless instructed otherwise in the installation and configuration procedures. v Connect and disconnect cables as described in the following table when installing, moving, or opening covers on this product or attached devices. To Connect: 1. Turn everything OFF. 2. First, attach all cables to devices. 3. Attach signal cables to connectors. 4. Attach power cords to outlet. 5. Turn device ON. To Disconnect: 1. Turn everything OFF. 2. First, remove power cords from outlet. 3. Remove signal cables from connectors. 4. Remove all cables from devices. Statement 2 Safety and environmental notices xi

12 CAUTION: When replacing the lithium battery, use only Part Number 33F8354 or an equivalent type battery recommended by the manufacturer. If your system has a module containing a lithium battery, replace it only with the same module type made by the same manufacturer. The battery contains lithium and can explode if not properly used, handled, or disposed of. Do not: v Throw or immerse into water v Heat to more than 100 C (212 F) v Repair or disassemble Dispose of the battery as required by local ordinances or regulations. Statement 3 CAUTION: When laser products (such as CD-ROMs, DVD drives, fiber optic devices, or transmitters) are installed, note the following: v v Do not remove the covers. Removing the covers of the laser product could result in exposure to hazardous laser radiation. There are no serviceable parts inside the device. Use of controls or adjustments or performance of procedures other than those specified herein might result in hazardous radiation exposure. DANGER Some laser products contain an embedded Class 3A or Class 3B laser diode. Note the following. Laser radiation when open. Do not stare into the beam, do not view directly with optical instruments, and avoid direct exposure to the beam. Statement 4 xii IBM SONAS 1.5.2: Software Configuration Guide

13 18 kg (39.7 lb) 32 kg (70.5 lb) 55 kg (121.2 lb) CAUTION: Use safe practices when lifting. Statement 5 CAUTION: The power control button on the device and the power switch on the power supply do not turn off the electrical current supplied to the device. The device also might have more than one power cord. To remove all electrical current from the device, ensure that all power cords are disconnected from the power source. Statement 6 CAUTION: If you install a strain-relief bracket option over the end of the power cord that is connected to the device, you must connect the other end of the power cord to an easily accessible power source. Statement 8 Safety and environmental notices xiii

14 CAUTION: Never remove the cover on a power supply or any part that has the following label attached. Hazardous voltage, current, and energy levels are present inside any component that has this label attached. There are no serviceable parts inside these components. If you suspect a problem with one of these parts, contact a service technician. Statement 12 CAUTION: The following label indicates a hot surface nearby. Statement 26 CAUTION: Do not place any object on top of rack-mounted devices. Statement 27 xiv IBM SONAS 1.5.2: Software Configuration Guide

15 CAUTION: Hazardous moving parts are nearby. Statement 29 CAUTION: This equipment is designed to permit the connection of the earthed conductor of the dc supply circuit to the earthing conductor at the equipment. If this connection is made, all of the following conditions must be met: v v v v This equipment shall be connected directly to the dc supply system earthing electrode conductor or to a bonding jumper from an earthing terminal bar or bus to which the dc supply system earthing electrode conductor is connected. This equipment shall be located in the same immediate area (such as, adjacent cabinets) as any other equipment that has a connection between the earthed conductor of the same dc supply circuit and the earthing conductor, and also the point of earthing of the dc system. The dc system shall not be earthed elsewhere. The dc supply source shall be located within the same premises as this equipment. Switching or disconnecting devices shall not be in the earthed circuit conductor between the dc source and the point of connection of the earthing electrode conductor. Statement 31 Safety and environmental notices xv

16 DANGER Electrical current from power, telephone, and communication cables is hazardous. To avoid a shock hazard: v Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. v Connect all power cords to a properly wired and grounded power source. v Connect to properly wired power sources any equipment that will be attached to this product. v When possible, use one hand only to connect or disconnect signal cables. v Never turn on any equipment when there is evidence of fire, water, or structural damage. v Disconnect the attached ac power cords, dc power sources, network connections, telecommunications systems, and serial cables before you open the device covers, unless you are instructed otherwise in the installation and configuration procedures. v Connect and disconnect cables as described in the following table when you install, move, or open covers on this product or attached devices. To Connect: 1. Turn OFF all power sources and equipment that is to be attached to this product. 2. Attach signal cables to the product. 3. Attach power cords to the product. v For ac systems, use appliance inlets. v For dc systems, ensure correct polarity of -48 V dc connections: RTN is + and -48 V dc is -. Earth ground should use a two-hole lug for safety. 4. Attach signal cables to other devices. 5. Connect power cords to their sources. 6. Turn ON all the power sources. To Disconnect: 1. Turn OFF all power sources and equipment that is to be attached to this product. v For ac systems, remove all power cords from the chassis power receptacles or interrupt power at the ac power distribution unit. v For dc systems, disconnect dc power sources at the breaker panel or by turning off the power source. Then, remove the dc cables. 2. Remove the signal cables from the connectors. 3. Remove all cables from the devices. Statement 33 CAUTION: This product does not provide a power-control button. Turning off blades or removing power modules and I/O modules does not turn off electrical current to the product. The product also might have more than one power cord. To remove all electrical current from the product, make sure that all power cords are disconnected from the power source. xvi IBM SONAS 1.5.2: Software Configuration Guide

17 Statement 34 CAUTION: To reduce the risk of electric shock or energy hazards: v v v v v v This equipment must be installed by trained service personnel in a restricted-access location, as defined by the NEC and IEC , First Edition, The Standard for Safety of Information Technology Equipment. Connect the equipment to a properly grounded safety extra low voltage (SELV) source. A SELV source is a secondary circuit that is designed so that normal and single fault conditions do not cause the voltages to exceed a safe level (60 V direct current). Incorporate a readily available approved and rated disconnect device in the field wiring. See the specifications in the product documentation for the required circuit-breaker rating for branch circuit overcurrent protection. Use copper wire conductors only. See the specifications in the product documentation for the required wire size. See the specifications in the product documentation for the required torque values for the wiring-terminal screws. Statement 37 DANGER When you populate a rack cabinet, adhere to the following guidelines: v Always lower the leveling pads on the rack cabinet. v Always install the stabilizer brackets on the rack cabinet. v Always install the heaviest devices in the bottom of the rack cabinet. v Always install devices starting from the bottom of the rack cabinet. v Do not extend multiple devices from the rack cabinet simultaneously, unless the rack-mounting instructions direction you to do so. Multiple devices extended into the service position can cause your rack cabinet to tip. v If you are not using the IBM 9308 rack cabinet, securely anchor the rack cabinet to ensure its stability. Safety notices and labels When using this product, observe the danger, caution, and attention notices contained in this guide. The notices are accompanied by symbols that represent the severity of the safety condition. Safety and environmental notices xvii

18 About this task Be sure to read all caution and danger statements in this documentation before performing the instructions. Read any additional safety information that comes with the equipment or other devices before installing or repairing the device. The following notices and statements are used in IBM documents. These notices provide important tips, guidance, or advice They are listed in order of decreasing severity of potential hazards. DANGER These statements indicate situations that are potentially lethal or extremely hazardous to people. A lightning bolt symbol accompanies a danger notice to represent a dangerous electrical condition. Safety labels are attached directly to products to warn of these situations. CAUTION: These statements indicate situations that are potentially hazardous to people because of some existing condition or where a potentially dangerous situation might develop because of some unsafe practice. A caution notice might be accompanied by the symbols shown in Table 1. Table 1. Caution notice symbols Symbol Description A risk of electrical shock or an energy hazard. A generally hazardous condition not represented by other safety symbols. A hazardous condition due to the use of a laser in the product. Laser symbols are always accompanied by the classification of the laser as defined by the U. S. Department of Health and Human Services (for example, Class I, Class II, and so forth). Attention: These notices indicate potential damage to programs, devices, or data. An exclamation point symbol might accompany an attention notice, but is not required. All caution and danger statements in this document are referenced with a letter and digit identifier. This identifier is used to cross reference an English caution (C) or danger (D) statement with translated versions of the caution or danger statement in IBM Systems Safety Notices. For example, if a danger statement contains the identifier D004, translations for that danger statement appear in IBM Systems Safety Notices under statement D004. In addition to these notices, labels might be attached to the product to warn of potential hazards. Danger notices for IBM SONAS Ensure that you understand the danger notices for IBM SONAS. xviii IBM SONAS 1.5.2: Software Configuration Guide

19 Danger notices Use the reference numbers in parentheses at the end of each notice, such as (D003) for example, to find the matching translated notice in IBM Systems Safety Notices. DANGER: To prevent a possible shock from touching two surfaces with different protective ground (earth), use one hand, when possible, to connect or disconnect signal cables. (D001) DANGER: Overloading a branch circuit is potentially a fire hazard and a shock hazard under certain conditions. To avoid these hazards, ensure that your system electrical requirements do not exceed branch circuit protection requirements. Refer to the information that is provided with your device or the power rating label for electrical specifications. (D002) DANGER: If the receptacle has a metal shell, do not touch the shell until you have completed the voltage and grounding checks. Improper wiring or grounding could place dangerous voltage on the metal shell. If any of the conditions are not as described, STOP. Ensure the improper voltage or impedance conditions are corrected before proceeding. (D003) DANGER: An electrical outlet that is not correctly wired could place hazardous voltage on the metal parts of the system or the devices that attach to the system. It is the responsibility of the customer to ensure that the outlet is correctly wired and grounded to prevent an electrical shock. (D004) Safety and environmental notices xix

20 DANGER: When working on or around the system, observe the following precautions: Electrical voltage and current from power, telephone, and communication cables are hazardous. To avoid a shock hazard: Connect power to this unit only with the IBM provided power cord. Do not use the IBM provided power cord for any other product. Do not open or service any power supply assembly. Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. The product might be equipped with multiple power cords. To remove all hazardous voltages, disconnect all power cords. Connect all power cords to a properly wired and grounded electrical outlet. Ensure that the outlet supplies proper voltage and phase rotation according to the system rating plate. Connect any equipment that will be attached to this product to properly wired outlets. When possible, use one hand only to connect or disconnect signal cables. Never turn on any equipment when there is evidence of fire, water, or structural damage. Disconnect the attached power cords, telecommunications systems, networks, and modems before you open the device covers, unless instructed otherwise in the installation and configuration procedures. Connect and disconnect cables as described in the following procedures when installing, moving, or opening covers on this product or attached devices. To disconnect: 1. Turn off everything (unless instructed otherwise). 2. Remove the power cords from the outlets. 3. Remove the signal cables from the connectors. 4. Remove all cables from the devices. To connect: 1. Turn off everything (unless instructed otherwise). 2. Attach all cables to the devices. 3. Attach the signal cables to the connectors. 4. Attach the power cords to the outlets. 5. Turn on the devices. Sharp edges, corners and joints may be present in and around the system. Use care when handling equipment to avoid cuts, scrapes and pinching. (D005) DANGER: Heavy equipment personal injury or equipment damage might result if mishandled. (D006) Caution notices for IBM SONAS Ensure that you understand the caution notices for IBM SONAS. Caution notices Use the reference numbers in parentheses at the end of each notice, such as (C003) for example, to find the matching translated notice in IBM Systems Safety Notices. CAUTION: Energy hazard present. Shorting might result in system outage and possible physical injury. Remove all metallic jewelry before servicing. (C001) xx IBM SONAS 1.5.2: Software Configuration Guide

21 CAUTION: Only trained service personnel may replace this battery. The battery contains lithium. To avoid possible explosion, do not burn or charge the battery. Do not: Throw or immerse into water, heat to more than 100 C (212 F), repair or disassemble. (C002) CAUTION: The battery is a nickel metal hydride battery. To avoid possible explosion, do not burn. (C006) CAUTION: The battery is a lithium ion battery. To avoid possible explosion, do not burn. (C007) CAUTION: To avoid personal injury, before lifting this unit, remove all appropriate subassemblies per instructions to reduce the system weight. (C012) CAUTION: The doors and covers to the product are to be closed at all times except for service by trained service personnel. All covers must be replaced and doors locked at the conclusion of the service operation. (C013) CAUTION: The system contains circuit cards, assemblies, or both that contain lead solder. To avoid the release of lead (Pb) into the environment, do not burn. Discard the circuit card as instructed by local regulations. (C014) CAUTION: Do not remove or install this unit without using the provided lift tool. (C017) CAUTION: This product is equipped with a 3-wire (two conductors and ground) power cable and plug. Use this power cable with a properly grounded electrical outlet to avoid electrical shock. (C018) CAUTION: The power distribution outlets provide 200 to 240 V ac. Use these outlets only for devices that operate within this voltage range. (C021) CAUTION: Ensure the building power circuit breakers are turned off BEFORE you connect the power cord or cords to the building power. (C023) CAUTION: This product might contain one or more of the following devices: CD-ROM drive, DVD-ROM drive, DVD-RAM drive or laser module, which are Class 1 laser products. Note the following information: Do not remove the covers. Removing the covers of the laser product could result in exposure to hazardous laser radiation. There are no serviceable parts inside the device. Use of the controls or adjustments or performance of the procedures other than those specified herein might result in hazardous radiation exposure. (C026) CAUTION: Some laser products contain an embedded Class3A or Class3B laser diode. Note the following information: Laser radiation when open. Do not stare into the beam, do not view directly with optical instruments, and avoid direct exposure to the beam. (C030) CAUTION: The power-control button on the device does not turn off the electrical current supplied to the device. The device might also have more than one connection to dc power. To remove all electrical current from the device, ensure that all connections to dc power are disconnected at the dc power input terminals. (C031) CAUTION: Servicing of this product or unit is to be performed by trained service personnel only. (C032) CAUTION: To reduce the risk of fire, use No. 26 AWG or larger (for example, 24 AWG) UL-listed or CSA certified telecommunication line cord. (C035) Safety and environmental notices xxi

22 Use the following general safety information for all rack mounted devices: DANGER: Observe the following precautions when working on or around your IT rack system: Heavy equipment personal injury or equipment damage might result if mishandled. Always lower the leveling pads on the rack cabinet. Always install stabilizer brackets on the rack cabinet. To avoid hazardous conditions due to uneven mechanical loading, always install the heaviest devices in the bottom of the rack cabinet. Always install servers and optional devices starting from the bottom of the rack cabinet. Rack-mounted devices are not to be used as shelves or work spaces. Do not place objects on top of rack-mounted devices. Each rack cabinet might have more than one power cord. Be sure to disconnect all power cords in the rack cabinet when directed to disconnect power during servicing. Connect all devices installed in a rack cabinet to power devices installed in the same rack cabinet. Do not plug a power cord from a device installed in one rack cabinet into a power device installed in a different rack cabinet. An electrical outlet that is not correctly wired could place hazardous voltage on the metal parts of the system or the devices that attach to the system. It is the responsibility of the customer to ensure that the outlet is correctly wired and grounded to prevent an electrical shock. (R001 part 1 of 2) CAUTION: Do not install a unit in a rack where the internal rack ambient temperatures will exceed the manufacturer s recommended ambient temperature for all your rack-mounted devices. Do not install a unit in a rack where the air flow is compromised. Ensure that air flow is not blocked or reduced on any side, front or back of a unit used for air flow through the unit. Consideration should be given to the connection of the equipment to the supply circuit so that overloading of the circuits does not compromise the supply wiring or overcurrent protection. To provide the correct power connection to a rack, refer to the rating labels located on the equipment in the rack to determine the total power requirement of the supply circuit. (For sliding drawers): Do not pull out or install any drawer or feature if the rack stabilizer brackets are not attached to the rack. Do not pull out more than one drawer at a time. The rack might become unstable if you pull out more than one drawer at a time. (For fixed drawers): This drawer is a fixed drawer and must not be moved for servicing unless specified by the manufacturer. Attempting to move the drawer partially or completely out of the rack might cause the rack to become unstable or cause the drawer to fall out of the rack. (R001 part 2 of 2) Environmental notices This publication contains all the required environmental notices for IBM Systems products in English and other languages. The environmental notices include statements on limitations, product recycling and disposal, product information, the battery return program, flat panel display, monitors and workstations, refrigeration, and water cooling systems. IBM Systems Environmental Notices and User Guide, Z xxii IBM SONAS 1.5.2: Software Configuration Guide

23 To view a PDF file, you need the Adobe Acrobat Reader. You can download it at no charge from the Adobe web site. Safety and environmental notices xxiii

24 xxiv IBM SONAS 1.5.2: Software Configuration Guide

25 How to send your comments Your feedback is important in helping to provide the most accurate and highest quality information. To submit any comments about this book or any other IBM Scale Out Network Attached Storage documentation: Send your comments by to Include the following information for this publication or use suitable replacements for the publication title and form number for the publication on which you are commenting: v Publication title v Page, table, or illustration numbers that you are commenting on v A detailed description of any information that should be changed Copyright IBM Corp. 2009, 2015 xxv

26 xxvi IBM SONAS 1.5.2: Software Configuration Guide

27 Chapter 1. Before installing Machines/Models Affected This content affects IBM Scale Out Network Attached Storage (IBM SONAS) system version x-xx. Prerequisite, concurrent, and companion requirements This topic lists the prerequisites for installing IBM SONAS system. Note: If IBM SONAS connects to a Gateway, ensure that the external storage of the Gateway is operational before proceeding with the installation. v IBM Scale Out Network Attached Storage Software Version x and later. v v v The hardware levels supported by IBM Scale Out Network Attached Storage Software Version x and later are: 2851-SI2, and 2851-SS2. IBM Scale Out Network Attached Storage Software Version x and later requires both active and passive management nodes. Before installing IBM Scale Out Network Attached Storage Software Version x and later, ensure that the network for the Management nodes is configured, active, and you have an accessible NTP server. Table 2. Number of customer Ethernet connections and IP addresses that are required IBM SONAS node management node 1 management node 2 Machine type and model Data path connections Data path IP addresses Management connections 2851-SI SI interface node 2851-SI2 Up to six 1Gb and up to four 10Gb storage node 2851-SS Management IP addresses Note: v The specifications in the table are for a single node. v The interface node has two 1 Gb data path connections on the system board, an optional 4-port 1 Gb card and up to two optional 2-port 10 Gb cards. If a single interface node has a maximum of eight data path connections, then a system with three interface nodes has a maximum of 24 data path connections (3 nodes x 8 connections per node = 24 connections). v The 1 Gb data path connections consist of copper wires. Use of Cat-6 cables because Cat-5 or Cat-5e cables are likely to reduce performance. The 10 Gb data path connections are shortwave fiber. Copyright IBM Corp. 2009,

28 2 IBM SONAS 1.5.2: Software Configuration Guide

29 Chapter 2. Preinstallation planning sheet Plan well in advance to successfully complete an IBM SONAS system installation. Use these planning guidelines to gather required information for specific components. Customer required information Table 3. Rack locations. Ask the customer for the Preinstallation Planning Sheets that were provided to them during the Solutions Assurance process. The information that is contained in those sheets is required during installation. After you complete installation, store the Preinstallation Planning Sheets in the 2851-RXA base rack so that they are available when needed for future installations, upgrades, or services. Provide the model and serial number (if available) for each rack, and a description of the location where each rack is to be installed. The information in Table 3 helps the installer know where to install each rack. Note: Complete the Description of location column with geographical information that is unique to each cluster. Complete as much information as possible, such as the x, y coordinates within a data center, room number, floor number, building number, city, and so on. Rack locations Rack number Rack model Rack serial number Description of location 1 RXA Copyright IBM Corp. 2009,

30 Table 3. Rack locations (continued). Rack locations Rack number Rack model Rack serial number Description of location Table SI2 management node 1 configuration information SI2 management node 1 configuration information Field Value Notes Cluster name Name of the IBM SONAS cluster. Example: cluster1 4 IBM SONAS 1.5.2: Software Configuration Guide

31 Table SI2 management node 1 configuration information (continued) SI2 management node 1 configuration information Field Value Notes Domain name Customer network domain name. Internal IP address range Management console IP address Management console service port 1 Management console service port 2 Management console gateway Management console subnet mask Root Password Note: Specify 1, 2, or 3 as described in the Notes column Example: customer.com Note: The cluster name and domain name are typically used in combination. Example: cluster1.customer.com Select from one of the following IP address ranges. The range that you select must not conflict with the IP addresses used for the customer Ethernet connections to the management nodes or interface nodes. The available IP address ranges: *.* *.* *.* Note: v If the customer network does not use IP addresses in the *.* range, select range 1. v If the customer network uses IP addresses in the *.* range, but does not use IP addresses in the *.* range, then select range 2. v If the customer network uses IP addresses in the *.* range and the *.* range, but does not use IP addresses in the *.* range, select range 3. The numeric IP address of 2851-SM2 management node 1 on the customer network. The customer storage administrator will connect to this IP address to manage the cluster. The physical connection is from the customer network to Ethernet port 3 on the 2851-SM2 management node. The numeric IP address of the management node service port 1, used for support access. The numeric IP address of the management node service port 2, used for support access. The numeric gateway of the management connection to the customer network. The numeric subnet mask of the management connection to the customer network. The password for root access to the management node. Note: The default root password is Passw0rd (where P is capitalized and 0 is zero). A good password must be at least eight characters in length, and contain a mix of uppercase and lowercase letters, and numbers. Chapter 2. Preinstallation planning sheet 5

32 Table SI2 management node 1 configuration information (continued) SI2 management node 1 configuration information Field Value Notes NTP server IP address At least one Network Time Protocol (NTP) server must be used to ensure time synchronization between the IBM SONAS cluster and the customer's authentication service (such as LDAP). You can use a second NTP server for redundancy. Note: The (NTP) servers can be local or remote (on the Internet). When you use remote servers, configure the network firewall to allow access on the NTP services port. Note: Only the management node will connect to the customer-specified NTP server. The management node will provide NTP services for all other nodes within the system. Time zone Refer to Appendix A, Time zone list, on page 71. Specify the number corresponding to a location in the time zone where the system is being installed. Example: If the machine is being installed in Tucson, Arizona, US, the best match for the time zone is America/Phoenix, and the corresponding number is 155. Number of frames being installed Specify the total quantity of rack frames in this cluster. Table 5. Remote support information. Remote support information Field Value Notes Company name Address The address where the machines are located. Example: Bldg 123, Room 456, 789 N DataCenter Rd, City, State Customer contact telephone number Off-shift customer contact telephone number IP address of proxy server (for Call Home and AOS) Port of proxy server (for Call Home and AOS) User ID for proxy server (for Call Home and AOS)... The primary telephone number that IBM Service calls if the system calls home to report a problem. The alternative telephone number that IBM Service calls if the system calls home to report a problem. Optional. If a proxy server is needed to access the Internet for Call Home, this is the IP address of that server. If no proxy server is used, leave this field blank. Optional. If a proxy server is needed, this is the port corresponding to the IP address listed in the earlier field. If no proxy server is used, leave this field blank. Optional. If a proxy server is needed, and the proxy server requires a user ID and password, record the user ID here. If no proxy server is used, or no user ID and password are used, leave this field blank. 6 IBM SONAS 1.5.2: Software Configuration Guide

33 Table 5. Remote support information (continued). Remote support information Field Value Notes Password for proxy server (for Call Home and AOS) Customer Optional. If a proxy server is needed, and the proxy server requires a user ID and password, record the password here. If no proxy server is used, or no user ID and password are used, leave this field blank. The address at which the customer would like to receive Call Home notifications. Table 6. Command-line interface (CLI) user information. Command-line interface (CLI) user information Field Value Notes CLI user ID admin The default user ID that the customer's administrator can use to log in to the management node to use the CLI commands or the GUI. CLI password admin The password corresponding to the default user ID given in the previous field. Table 7. DNS configuration information. DNS configuration information Field Value Note IP address of Domain Name Services (DNS) servers The public IP addresses require a single domain name (such as server1.company.com). All public IP addresses in the presence of a single public network must be registered with this name to enable DNS- round robin. The management access requires a second domain name (such as server3mgmt.company.com). This domain name is used when making a connection to IBM SONAS CLI or GUI. Domain... The domain name of the cluster (such as company.com). Note: This field is not required and can be left blank. If it is left blank, then no domain name is set for the cluster. Chapter 2. Preinstallation planning sheet 7

34 Table 7. DNS configuration information (continued). DNS configuration information Field Value Note Search strings A list of one or more domain names to be used when trying to resolve a shortname (example: company.com, storage.company.com, servers.company.com). Note: This field is not required and can be left blank. If it is left blank then no search string will be set for the cluster. Table 8. NAT configuration information. NAT configuration information Field Value Notes IP address A unique and unused numeric IP address on the customer network. It will be used by the management node and interface nodes to access the customer network through internal private network connections using NAT overloading, meaning that a combination of this IP address and a unique port number will correspond to each node (management node and interface nodes only). This IP address must be unused and must not be the same as the management node IP addresses specified in Table 4 on page 4 or the interface node IP addresses specified in Table 17 on page 20.Reserve an IP address on the customer network for this purpose.... This IP address must be in the same subnet as the one of the data path networks specified in Table 4 on page 4. Note: The NAT gateway service is provided by SONAS functionality on the IBM SONAS nodes - not by an external router or server on the customer's network. 8 IBM SONAS 1.5.2: Software Configuration Guide

35 Table 9. CIDR Subnet Mask Information. CIDR Subnet Mask information Subnet Mask CIDR Equivalent Note /32 Host (single address) /31 Unusable /30 2 usable /29 6 usable /28 14 usable /27 30 usable /26 62 usable / usable /24 "Class C" 254 usable /23 2 Class C's /22 4 Class C's /21 8 Class C's /20 16 Class C's /19 32 Class C's /18 64 Class C's / Class C's /16 "Class B" /15 2 Class B's /14 4 Class B's /13 8 Class B's /12 16 Class B's /11 32 Class B's /10 64 Class B's /9 128 Class B's /8 "Class A" /7 2 Class A's /6 4 Class A's /5 2 Class A's /4 8 Class A's /3 16 Class A's /2 32 Class A's /1 64 Class A's /0 IP space Chapter 2. Preinstallation planning sheet 9

36 Table 10. Authentication Method Information. Authentication Method information Field Value Note Authentication Method ID mapping options [ ] Microsoft Active Directory (AD) [ ] Lightweight Directory Access Protocol (LDAP) [ ] Samba Primary Domain Controller (PDC) [] NIS (NFS clients only) [ ] Local authentication [ ] Microsoft Windows Services for UNIX (SFU) server. This is used if AD is used as the authentication server. [ ] Network Information Service (NIS) server. This is used if the authentication method used is either AD or Samba PDC. [ ] Internal ID mapping server. The internal authentication sever and internal ID mapping servers are managed within the system. [ ] LDAP server. This option is uses if the LDAP server is used as the authentication server. Check one of the options. You can select NIS as the authentication method to enable NFS client access. The NFS users are authenticated based on the NFS server and client settings that are configured on the IBM SONAS system. You can use the NIS based authentication to specify the domains that can configure the netgroups, which will have access to the IBM SONAS system. One of these optional capabilities can be used to extend the capabilities of the authentication method that is selected in the previous field. If you checked Microsoft Active Directory in the Authentication Method field of Table 10, then you must complete this table. Table 11. Active Directory Configuration Information. Active Directory Configuration Information Field Value Note Active Directory Server IP Address... The numeric IP address of the remote Active Directory server on the customer's network. Active Directory UserID Active Directory Password... The user ID that must be provided when communicating with the remote Active Directory server. This user ID and the Password given in the next field will be used to authenticate to the Active Directory server. The password that must be provided when communicating with the remote Active Directory server. 10 IBM SONAS 1.5.2: Software Configuration Guide

37 Table 11. Active Directory Configuration Information (continued). Active Directory Configuration Information Field Value Note Kerberos KeyTab File If you need to use Kerberos with the AD based authentication, then you must fill in this field. Kerberos can be enabled for AD based authentication only if the NFS stack version is NFSv4.0. If AD based authentication is used, Kerberos is enabled by default for CIFS servers. SFU Domain Name If you have selected Microsoft Windows Services for UNIX (SFU) as the ID mapping mehtod, then you must fill in this field. If you did not check SFU, leave this field blank. SFU Range This field is used to specify the Trusted Domain Name for the Active Directory server. If you have selected Services For Unix (SFU) as the ID mapping method, then you must fill in this field, else you leave this field blank. SFU Schema Mode Automatic ID mapping range [ ] SFU [ ] rfc2307 This field is used to specify the Lower and Upper bounds of the User Identifier (UID) and Group Identifier (GID) ranges for the storage system. Use the format Lower-Upper (for example, 25-37). The SFU Range must contain the Unix UID/GID numbers corresponding to users/groups who need to access the system with SFU. The UNIX UID/GID that are assigned to such users/groups must lie in the ID range that is provided with --idmapconfig of the cfgad command. The default range minimum value is , the default range maximum value is , and the default range size is This corresponds to specifying --idmapconfig : , and allows for a maximum of 290 unique Active Directory domains. If you have selected Services For Unix (SFU) as the ID mapping method, then you must fill in this field, else you leave this field blank. This field is used to specify the Schema Mode. The schema Mode can be either "sfu" or "rfc2307" depending on the operating system of the Active Directory domain server. Specify 'rfc2307' for Microsoft Windows 2008 or Windows 2003 with R2 and 'sfu' for Windows 2000 and Windows 2003 releases prior to R2. If you have selected internal ID mapping server as the ID mapping method, you must fill in this field. The default range minimum value is , the default range maximum value is , and the default range size is This allows for a maximum of 290 unique Active Directory domains. Chapter 2. Preinstallation planning sheet 11

38 Table 11. Active Directory Configuration Information (continued). Active Directory Configuration Information Field Value Note Network Information Service details ID map role If NIS is used as the ID mapping method enter the details of the parameters that are listed in the NIS Configuration Information table. Select either Master or Subordinate as the ID map role. Master: Select this to mark the ID map rol of the system as Master. You need to export the ID maps from this system and import into the system whose ID map role is subordinate. The ID map role of a stand-alone system must be defined as Master as it does not have an asynchronous replication or remote caching relationship with another system. Subordinate: You need to import the ID maps from the master system. Table 12. LDAP Configuration Information. If you checked LDAP in the Authentication Method field of Table 10 on page 10, then you must complete this table. LDAP Configuration information Field Value Note LDAP Server IP Address... The numeric IP address of the remote LDAP server on the customer's network. SSL method suffix rootdn... []Off [ ] SSL (Secure Sockets Layer) [ ] TLS (Transport Layer Security) The communications link between the IBM SONAS and the customer's LDAP server may be open (not encrypted), or secured (encrypted). If secured, one of two methods is used: SSL or TLS. Note: When SSL or TLS is used, a security certificate file must be copied from the customer's LDAP server to the IBM SONAS management node. The suffix from the /etc/openldap/slapd.conf file on the customer's LDAP server. In the example following note 1 below, the suffix is "dc=sonasldap,dc=com" The rootdn from the /etc/openldap/slapd.conf file on the customer's LDAP server. In the example following note 1 below, the rootdn is "cn=manager,dc=sonasldap,dc=com" 12 IBM SONAS 1.5.2: Software Configuration Guide

39 Table 12. LDAP Configuration Information (continued). LDAP Configuration information Field Value Note rootpw The rootpw from the /etc/openldap/slapd.conf file on the customer's LDAP server. In the example following note 1 below, the rootdn is secret. Certificate Path If the SSL method is Off, leave this field blank. If the SSL method is SSL or TLS, record the path on the IBM SONAS management node where you will copy the Certificate file. As an example, if the Certificate File is cacert.pem and you will store it in a directory called /certificates, then record /certificates/cacert.pem. Kerberos Server Name If you need to use Kerberos with the LDAP based authentication, then you must fill in this field. This field is the name of the Kerberos server used with your LDAP environment. Kerberos Realm If you need to use Kerberos with the LDAP based authentication, then you must fill in this field. This field is the Realm for the Kerberos server used with your LDAP environment. Kerberos KeyTab File If you need to use Kerberos with the LDAP based authentication, then you must fill in this field. This field is the file name for the Kerberos KeyTab file. Note: The administrator of the customer's LDAP server is the source for this information. Most of the information can be found in the /etc/openldap/slapd.conf file on the customer's LDAP server. Here is an example of a portion of the file: suffix "dc=sonasldap,dc=com" rootdn "cn=manager,dc=sonasldap,dc=com" rootpw secret TLSCACertificateFile /usr/var/openldap-data/cacert.pem If you checked Samba Primary Domain Controller (PDC) in the Authentication Method field of Table 10 on page 10, then you must fill in this table. Table 13. Samba Primary Domain Controller (PDC) Configuration Information. Samba Primary Domain Controller (PDC) Configuration information Field Value Note Server IP Address... The numeric IP address of the remote server on the customer's network. Administrative user ID... The administrator's user ID for the customer's server. Chapter 2. Preinstallation planning sheet 13

40 Table 13. Samba Primary Domain Controller (PDC) Configuration Information (continued). Samba Primary Domain Controller (PDC) Configuration information Field Value Note Administrative user's password Domain name NetBIOS Name ID mapping method The password on the customer's server. The Domain Name for the customer's server. The NetBIOS Name for the customer's server. Fill the ID mapping method to be used with the Samba PDC based authentication. If automatic ID mapping is selected, enter the NIS domain and NIS server name. If NIS is used as the ID mapping method enter the details of the parameters that are listed in the NIS Configuration Information table. Table 14. NIS Configuration Information. If NIS is used as the ID mapping method enter the details of the parameters that are listed in the following table. NIS Configuration information Field Value Note Domain Map This field can be used to specify the mapping of NIS domains in the remote authentication server. When specifying a domain map, use a colon between the AD domain and the NIS domain(s). Example: ad_domain:nis_domain1 If more than one NIS domain is specified, use a comma separated list. Example: ad_domain:nis_domain1,nis_domain2 To specify more than one AD domain, use a semicolon. Example: ad_domain1:nis_domain1,nis_domain2; ad_domain2:nis_domain3,nis_domain4 14 IBM SONAS 1.5.2: Software Configuration Guide

41 Table 14. NIS Configuration Information (continued). NIS Configuration information Field Value Note Server Map This field must be used to specify the mapping between NIS servers and NIS domains. When specifying a server map, use a colon between the NIS server and the NIS domain(s). Example: nis_server:nis_domain1 If more than one NIS domain is specified, use a comma separated list. Example: nis_server:nis_domain1,nis_domain2 User Map To specify more than one NIS server, use a semicolon. Example: nis_server1:nis_domain1,nis_domain2; nis_server2:nis_domain3,nis_domain4 This optional field can be used to specify the handling for a user who is not known to the NIS server. Only one rule can be specified for each AD or Samba PDC domain. The handling is specified using one of the following keywords: v v v DENY_ACCESS Denies any user from the specified domain access if they do not have a mapping entry in the NIS. Example: ad_domain1:deny_access AUTO A new ID for the user is generated from the specific domain which does not have an entry in the NIS. This ID is generated from a pre-specified ID range and is auto-incremented. The administrator must make sure that existing NIS IDs do not fall in this provided ID range. This mapping is kept in SONAS and NIS is not aware of this ID mapping. The ID range can be specified using the ID Map User Range and ID Map Group Range options. Example: ad_domain1:auto DEFAULT Any user from the specified domain who does not have a mapping entry in the NIS server is mapped to a specified user (typically a guest user). Example: ad_domain1:default:ad_domain\guest NIS Domain To specify rules for multiple AD or Samba PDC domains, separate the rules with a semicolon. Example: ad_domain1:deny_access; ad_domain2:auto; ad_domain3:default:ad_domain3\guest This field must be used to specify the NIS Domain that will be stored in the registry. Chapter 2. Preinstallation planning sheet 15

42 Table 14. NIS Configuration Information (continued). NIS Configuration information Field Value Note User ID Map This is used to map Unix IDs to Windows IDs for an environment where AD or Samba PDC is used for authentication. User ID map range If the Use ID Map field is checked AND at least one User Map rule is AUTO then you must specify a User Range and/or a Group Range. Example: Note: The User Range values must be a minimum of ID Map Group Range If the Use ID Map field is blank, leave this field blank. If the Use ID Map field is checked AND at least one User Map rule is AUTO then you must specify a User Range and/or a Group Range. Example: Note: The Group Range values must be a minimum of Local authentication information You can plan to use IBM SONAS local authentication server to configure IBM SONAS system authentication when you do not have an external server for authentication and ID mapping and have a requirement of a limited number of data access users and groups. A CLI/GUI user with only SecurityAdmin role can create, modify, and delete users and groups stored on the internal authentication server used for authentication and ID mapping for NFS, CIFS, HTTPS, SCP, and FTP NAS protocols. Netgroups are not supported, nor is Kerberos for NFS or CIFS. The IBM SONAS local internal authentication server cannot be used as an external authentication server for other systems, including any other IBM SONAS system. Use the cfglocalauth command to configure local authentication. Use this table to specify the information about file access protocols to use for system configuration. Check the protocol, owner, CIFS options, and NFS options. Table 15. File Access Protocol Information Field Value Note Protocols [ ] CIFS (Common Internet File System) A list of file access protocols that the customer will use to access the system. [ ] HTTP (Hypertext Transfer Protocol) Check one or more options. [ ] FTP (File Transfer Protocol) [ ] SCP (Secure Copy Protocol) [ ] NFS (Network File System) 16 IBM SONAS 1.5.2: Software Configuration Guide

43 Table 15. File Access Protocol Information (continued) Field Value Note Owner The owner of the shared disk space. It can be a username, or a combination of Domain\username. Example: admin1 Example: Domain1\admin1 CIFS options If the Protocols row does not have CIFS checked, leave this field blank. If CIFS is checked, you may specify CIFS options. NFS options IP Address:... Subnet Mask:... CIDR Equivalent of the Subnet Mask: / Access Options: []roor[]rw [ ] root_squash or [ ]no_root_squash [ ] async or [ ]sync no_acl The options are a comma-separated key-value pair list. Valid CIFS options are: browseable=yes comment="place comment here" Example: -cifs browseable=yes,comment="ibm SONAS" If the Protocols row does not have NFS checked, leave this field blank. If NFS is checked, you must specify NFS options. If NFS options are not specified, the NFS shared disk will not be accessible by clients. The NFS options must be provided by the customer's NFS administrator. NFS options include a list of client machines allowed to access the NFS shared drive, and the type of access to be granted each client machine.see Note 1 for more information about specifying a list of client machines allowed to access the NFS shared drive. See Note 2 for more information about Access Options. Example: -nfs " / 16(rw,no_root_squash,sync)" If you are using NIS for NetGroup support, see Note 3 for more information. Hides the ACLs from the clients, so that they see only a subset of actual permissions on the given file system. Using this option is safe for file systems that are used by NFSv3 clients that perform access decisions locally. Current NFSv3 clients use the ACCESS RPC to perform all access decisions on the server. By default the no_acl option is off and the export is created with the ACL support. Use the acl option to configure ACL support for the export explicitly. 1. Client machines are specified by a combination of IP address and subnet mask (in CIDR /XX format). For example, if you want to access the NFS shared drive from any client with IP address of 10.0.*.* (from through ) then specify an IP Address as and a subnet mask as Look up the CIDR equivalent in Table 9 on page 9. Specify the IP Address, Subnet Mask, and the CIDR Equivalent of the Subnet Mask. 2. The access options you specify will be granted to all clients specified using the IP address/subnet Mask. Use one of the following valid options: Chapter 2. Preinstallation planning sheet 17

44 ro - NFS mount to be read-only. This flag is enabled by default. rw - NFS mount to be read-write. root_squash - Denies superusers on the clients any special access rights. It is used to provide improved security against an unauthorized user with root access. This flag is enabled by default. no_root_squash - Allows superusers on the clients to have superuser access to the exported directories. async - Provides completion status to a client as soon as all data to be written is in system memory, but before it has been written to disk. This enhances performance, but can result in undetectable data loss if the system crashes before all data has been written to disk. sync - Does not to provide completion status to a client until all data has been written to disk. This can reduce performance, but improves protection against undetected data loss. This flag is enabled by default. 3. If you are using NIS for NetGroup support, the NetGroups are defined in the /etc/netgroup file on the NIS server. They define network-wide groups used for permission checking when processing requests for remote mounts and remote logins. NIS NetGroups are supported for NFS clients. When creating an NFS export intended for use by NIS NetGroups, the NFS options should be in the format: "@<netgroup_name>(rw,root_squash)". Table 16. interface node Subnet Configuration Information. Subnet Configuration information Field Value Note Subnet Subnet Mask CIDR Equivalent of the Subnet Mask / The network defined for the data path communications links between all of the IBM SONAS interface nodes and the customer's application servers. As an example, if the customer has their interface nodes on a single network, and the interface node IP addresses are through then the subnet could be , with a subnet mask of (/24 in CIDR format). The subnet mask that is associated with the Subnet listed in the earlier field. In the example above, this would be The subnet mask that is listed in the earlier field, converted to CIDR format (refer to Table 9 on page 9). In the example above this would be IBM SONAS 1.5.2: Software Configuration Guide

45 Table 16. interface node Subnet Configuration Information (continued). Subnet Configuration information Field Value Note VLAN ID Optional. A list of one or more Virtual LAN Identifiers. A VLAN ID must be in the range If you do not use VLANs, then leave this field blank. Restriction: VLAN 1 is not supported for SONAS client traffic. This restriction is intended to prevent security exposure and reduce the probability of network configuration errors. VLAN 1 has been used within the industry as the default or native VLAN. Many vendors use VLAN ID value 1 for management traffic by default. Configuring VLAN 1 as available within the network can be a security exposure because VLAN 1 might span large parts of the switched network by default. Setting VLAN 1 for user client traffic can require explicit steps that differ by vendor and can be prone to configuration error. Chapter 2. Preinstallation planning sheet 19

46 Table 16. interface node Subnet Configuration Information (continued). Subnet Configuration information Field Value Note Group Name Optional. A name that is assigned to a network group. Use this to refer a set of interface nodes using a meaningful name instead of a list of IP addresses or host names. If you do not use network groups, then leave this field blank. Public interfaces are bonded redundantly into network groups. Bonds for each node within a network group must have identical interface names. This is required for proper node failover, where network IP addresses and supporting interfaces are moved from node to node within the network group due to a failover event. For example, if a network group is attached to ethx0, all nodes within that network group must support the ethx0 bond interface. When creating network groups, configuring uniform node characteristics for all nodes within a network group maximizes node behavior consistency on node failover. If node interfaces are not configured consistently within a network group such that there is an intermix of 1 GbE and 10 GbE speeds on an identical interface for different nodes within a network group, if a node with only 1 GbE network bandwidth capability for an interface assumes responsibility during fail over from a node that had a 10 GbE network speed for the identical interface, reduced client performance, and undesired behavior can occur. Other node characteristic consistencies that maximize node failover behavior include bonding mode, MTU size, and VLAN assignment. For more information, see "Managing the interface network" topic in the Information Center. Table 17. interface node Network Configuration Information. Network Configuration information Number (see Note 5) 2851-SIx interface node IP Address (see Note 1) 1 Subnet and Subnet Mask (see Note 2) Gateway (see Note 3) Host Name (see Note 4) int001st /... int002st / IBM SONAS 1.5.2: Software Configuration Guide

47 Table 17. interface node Network Configuration Information (continued). Network Configuration information Number (see Note 5) 2851-SIx interface node IP Address (see Note 1) 3 Subnet and Subnet Mask (see Note 2) Gateway (see Note 3) Host Name (see Note 4) int003st /... int004st /... int005st /... int006st /... int007st /... int008st /... int009st /... int010st /... int011st /... int012st /... int013st /... int014st /... Chapter 2. Preinstallation planning sheet 21

48 Table 17. interface node Network Configuration Information (continued). Network Configuration information Number (see Note 5) 2851-SIx interface node IP Address (see Note 1) 15 Subnet and Subnet Mask (see Note 2) Gateway (see Note 3) Host Name (see Note 4) int015st /... int016st /... int017st /... int018st /... int019st /... int020st /... int021st /... int022st /... int023st /... int024st /... int025st /... int026st / IBM SONAS 1.5.2: Software Configuration Guide

49 Table 17. interface node Network Configuration Information (continued). Network Configuration information Number (see Note 5) 2851-SIx interface node IP Address (see Note 1) 27 Subnet and Subnet Mask (see Note 2) Gateway (see Note 3) Host Name (see Note 4) int027st / int028st / int029st / int030st / int031st / int032st / This is the numeric IP address of the Data Path connection to the customer network. It is used for all of the Ethernet Data Path connections on a single 2851-SIx interface node. The Data Path connections use Ethernet Bonding, so a single IP address (along with a Subnet Mask and Gateway) is used for all available Ethernet ports on a single interface node. The system will automatically load balance between the physical ports on a single interface node. 2. This is the numeric Subnet and Subnet Mask (in CIDR format) of the Data Path connection to the customer network. It is used for all of the Ethernet Data Path connections on a single 2851-SIx interface node. In most cases, you can use the zero Subnet ( ) and the zero Subnet Mask (/0). Example: /0If you typically express Subnet Masks as 4 octets, refer to Table 9 on page 9 to convert from 4 octets to the two-digit CIDR format. 3. This is the numeric Gateway of the Data Path connection to the customer network. It is used for all of the Ethernet Data Path connections on a single 2851-SIx interface node. 4. This is the pre-assigned host name for the 2851-SIx interface node (if installed). 5. During the initial installation of the system, the interface nodes are numbered sequentially based on their position within the system. If you need to correlate an interface node Number to its physical position in the system, refer to the table of values for the Interface Node in SSR required information on page 24. Chapter 2. Preinstallation planning sheet 23

50 Table 18. Quorum Nodes. Quorum Nodes interface nodes storage nodes SSR required information 1. Select an odd number of Quorum Nodes, choosing from interface nodes and storage nodes. 2. The minimum number of Quorum Nodes is 3, the maximum number of Quorum Nodes is 7. Typical choices are 3, 5, or 7 Quorum Nodes. 3. If there is more than one frame in the cluster, you must select Quorum Nodes in more than one frame. 4. Write the interface node and storage node numbers in the previous table. 5. Refer to the following examples for more guidance. Examples: v For a small system with 3 interface nodes and 2 storage nodes: select interface node 1, storage node 1, and storage node 2. v For a medium system with 10 interface nodes and 6 storage nodes: select 2 interface nodes (preferably in more than one frame), and 3 storage nodes (preferably in more than one frame). v For a large system with 10 interface nodes and 10 storage nodes: select 3 interface nodes (preferably in more than one frame), and 4 storage nodes (preferably in more than one frame). Table 19. management node Location Information 2851-SM2 management node Number Rack Number (see Note 1) Rack Position (see Note 2) SM2 management node Serial Number (see Note 3) Table 20. InfiniBand switch Serial Numbers Note: 1. This is the number of the rack containing this node, as specified in Table 3 on page This number indicates the U position where this node is installed in the rack. Also known as the slot number. A 2851-SM2 management node fills 2U of rack space (such as 1U - 2U) and by convention we use the lower number (such as 1). 3. This is the serial number of this node. If the optional second management node is not installed, leave its serial number blank I36 or 2851-I96 InfiniBand switchnumber Rack Number (see Note 1) Rack Position (see Note 2) 1 (lower) I36 = 35 InfiniBand switch Serial Number (see Note 3) 2851-I96 = IBM SONAS 1.5.2: Software Configuration Guide

51 Table 20. InfiniBand switch Serial Numbers (continued) 2851-I36 or 2851-I96 InfiniBand switchnumber Rack Number (see Note 1) Rack Position (see Note 2) 2 (upper) I36 = 36 InfiniBand switch Serial Number (see Note 3) 2851-I96 = 30 Table 21. interface node Location Information Note: 1. This is the number of the rack containing the InfiniBand switch (always Rack Number 1). 2. This number indicates the U position where this InfiniBand switch is installed in the rack. Also known as the slot number. A 2851-I36 InfiniBand switch fills 1U of rack space. A 2851-I96 InfiniBand switch fills 7U of rack space. When a device in a rack takes more than 1U of rack space, by convention we use the lowest number. So a device that fills rack positions is referenced as position This is the serial number of this InfiniBand switch. Refer to a label on the InfiniBand switch that contains the machine type (2851), model (I36 or I96) and the 7-character serial number. On the 2851-I36, the serial number label is at the right rear of the switch. On the 2851-I96, the serial number label is at the center rear of the switch, located near the Ethernet connections SIx interface node Number (see Note 5) Rack Number (see Note 1) Rack Position (see Note 2) 2851-SIx interface node Serial Number (see Note 3) InfiniBand switch Port Number (see Note 4) Fill out this column during installation Chapter 2. Preinstallation planning sheet 25

52 Table 21. interface node Location Information (continued) 2851-SIx interface node Number (see Note 5) (see Note 1) 32(see Note 1) Rack Number (see Note 1) Rack Position (see Note 2) 2851-SIx interface node Serial Number (see Note 3) InfiniBand switch Port Number (see Note 4) Fill out this column during installation Note: 1. This is the number of the rack containing this node, as specified in Table 3 on page This number indicates the U position where this node is installed in the rack. Also known as the slot number. A 2851-SIx interface node fills 2U of rack space (such as 1U - 2U) and by convention we use the lower number (such as 1). Valid values are By convention, we start at the bottom of rack 1 and go up to the top, then go to the bottom of rack 2, and so on. 3. This is the serial number of this node. 4. This field is the InfiniBand switch port number for this node. InfiniBand port 1 (on the adapter in PCIe slot 1 of the server) will connect to an open port on InfiniBand switch 1 (the lower switch), and InfiniBand port 2 (on the adapter in PCIe slot 3 of the server) will connect to the same numbered port on InfiniBand switch 2 (the upper switch). Leave this field blank for nodes that were pre-installed in the base rack. 5. interface node Numbers must be assigned based on Rack Number and Rack Position. Start in Rack 1 and find the interface node in the lowest U position. This is interface node Number 1. Move upward in the rack assigning consecutive interface node Numbers to each interface node in the rack. When you have assigned interface node Numbers to all interface nodes in Rack 1, continue at the lowest U position in Rack 2, and assign consecutive interface node Numbers until all the interface nodes have been assigned a number. 6. For the 2851-RXA racks, you can install two additional 2851-SIx interface nodes in a rack, which means you can install a 31st and 32nd interface node, but only if you have code level x-xx or higher code installed. Applicable only to RXA3 configurations. 7. For the 2851-RXA racks, you can install two additional 2851-SIx interface nodes in a rack, which means you can install an interface node in EIA rack location IBM SONAS 1.5.2: Software Configuration Guide

53 -38 and 39-40, but only if you have code level xx or higher code installed and the 2851-RXA rack does not contain a 2851-SM1. Table 22. storage node Location Information 2851-SSx storage node Number (see Note 5) Rack Number (see Note 1) Rack Position (see Note 2) 2851-SSx storage node Serial Number (see Note 3) InfiniBand switch Port Number (see Note 4) Fill out this column during installation Chapter 2. Preinstallation planning sheet 27

54 Table 22. storage node Location Information (continued) 2851-SSx storage node Number (see Note 5) Rack Number (see Note 1) Rack Position (see Note 2) 2851-SSx storage node Serial Number (see Note 3) InfiniBand switch Port Number (see Note 4) Fill out this column during installation Note: 1. This is the number of the rack containing this node, as specified in Table 3 on page This number indicates the U position where this node is installed in the rack. Also known as the slot number. A 2851-SSx storage node fills 2U of rack space (such as 1U - 2U) and by convention we use the lower number (such as 1). Valid values are By convention, we start at the bottom of rack 1 and go up to the top, then go to the bottom of rack 2, and so on. 3. This is the serial number of the 2851-SSx storage node. 4. This field is the InfiniBand switch port number for this node. InfiniBand port 1 (on the adapter in PCIe slot 1 of the server) will connect to an open port on InfiniBand switch 1 (the lower switch), and InfiniBand port 2 (on the adapter in 28 IBM SONAS 1.5.2: Software Configuration Guide

55 PCIe slot 3 of the server) will connect to the same numbered port on InfiniBand switch 2 (the upper switch). Leave this field blank for nodes that were pre-installed in the base rack. 5. storage node Numbers must be assigned based on Rack Number and Rack Position. Start in Rack 1 and find the storage node in the lowest U position. This is storage node Number 1. Move upward in the rack assigning consecutive storage node Numbers to each storage node in the rack. When you have assigned storage node Numbers to all storage nodes in Rack 1, continue at the lowest U position in Rack 2, and assign consecutive storage node Numbers until all the storage nodes have been assigned a number. Chapter 2. Preinstallation planning sheet 29

56 30 IBM SONAS 1.5.2: Software Configuration Guide

57 Chapter 3. Prerequisites This topic lists the prerequisites for configuring IBM SONAS Software. 1. Before you can configure the IBM SONAS Software, the IBM SONAS hardware installation must have been completed (refer to the IBM Scale Out Network Attached Storage Installation Guide). This includes hardware installation and initial hardware configuration using the first_time_install script. The hardware should be installed by an IBM SSR. 2. As part of additional services offering, an IBM personnel configures the software. It is not part of hardware installation. and the IBM SSR does not configure the software. 3. A subset of the information in the Preinstallation Planning Sheet should be provided to the IBM SSR before the hardware installation. The hardware installation cannot start until the Preinstallation Planning Sheet is completed. The remainder of the information is used during the software configuration. 4. Information from the customer's network administrator, storage administrator, and Microsoft Active Directory or LDAP Administrator should be included in the Pre-installation Planning Sheet. Ensure that the sheet is completely filled out before starting software configuration. If you have questions that are not answered by the notes in each table, discuss these with IBM during the pre-installation planning meeting. Copyright IBM Corp. 2009,

58 32 IBM SONAS 1.5.2: Software Configuration Guide

59 Chapter 4. Software configuration procedures Follow the software configuration procedures after completing a hardware installation. The software configuration procedures consist of a series of CLI commands. If you encounter a problem with any of the CLI commands, refer to the IBM SONAS Information Center for troubleshooting information. Logging on to the management node Follow this procedure to log in to the management node. 1. To log in to the management node, you require a Service password. The default password is ibm2serv. If it has been changed, use the Service Password in Table 4 on page Log in to the management node using the Keyboard Video Mouse (KVM) in the 2851-RXA base rack, and continue with the following steps: 3. Perform the following sub-steps to ensure that the KVM switch is set to management node 1: a. Press the PrtSc button. The KVM selection screen is displayed. b. Click on Port 1 MGMT-1. c. Press Enter. For more information about logging in to the active management node using the Service user ID, refer to Logging in to the active management node locally. A Command Prompt session (known as a Terminal session) will open. Verifying that Nodes are ready Complete the following steps to verify that all Nodes are in the Ready state. 1. Type cd /opt/ibm/sofs/cli and press Enter. 2. Type lsnode -c <clustername> and press Enter. Here -c <clustername> is optional. v <clustername> is the Cluster Name specified in Table 4 on page 4. The name used to identify the cluster in the Windows network neighborhood. The name is limited to 15 ASCII characters and must not contain any white space or one of the following characters: /:*?"; Note: Include the domain name when specifying the clustername. For example, lsnode -c fstsonas01.domainz.com. A status report for the nodes in the system is displayed, similar to the following example: Hostname IP Description Role Product version Connection status GPFS status CTDB status Last updated int001st interface OK active active 11/1/14 7:09 PM mgmt001st active management node management,interface OK active active 11/1/14 7:09 PM mgmt002st passive management node management,interface OK active active 11/1/14 7:09 PM strg001st storage OK active 11/1/14 7:07 PM strg002st storage OK active 11/1/14 7:07 PM EFSSG1000I The command completed successfully. 3. Verify that the GPFS and CTDB status are active. If one or more nodes are not ready, refer to the Problem Determination guide in the SONAS Information Center. Copyright IBM Corp. 2009,

60 Creating a CTDB Cluster Use this procedure to prepare for the initial configuration of the cluster manager. The IBM Scale Out Network Attached Storage Software must be configured with a cluster name (host name) for the cluster. Important: The cluster name/netbios names specified with the cfgcluster command should be chosen carefully if one plans for an Active Directory (AD) authentication configuration. If the same names are used across multiple IBM SONAS/V7000 clusters, or between the Active Directory Domain and the netbios name, the configuration will not work properly. Please note the following observations regarding the name collisions when planning a naming strategy: v v v There should not be netbios name conflict between two IBM SONAS/V7000 clusters that are to be configured against the same Active Directory server. The domain join of the latter machines revokes the join of the former one. The netbios name and the domain name should not be same. The netbios name and the short name of the Domain Controllers hosting the domain should not be same. 1. If licences are not accepted for the system, accept them from the management GUI. Licence agreements must be accepted before creating CTDB cluster. 2. Type cfgcluster <clustername> where v <clustername> is the cluster name specified in Table 4 on page 4. The name used to identify the cluster in the Windows network neighborhood. The name is limited to 15 ASCII characters and must not contain any white space or one of the following characters: /:*?"; Note: This is only the name of the cluster. Do not enter domain information. Example: cfgcluster cluster1 Tip: If the cfgcluster command fails because it requires the -c option (full cluster name including domain name information), log out of the CLI, and then log back in. Return to cd/opt/ibm/sofs/cli and use the cfgcluster command again. 3. Press Enter. 4. At the Do you really want to perform the operation? prompt, type yes and press Enter. 5. Complete the following sub-steps to verify that the cluster has been configured: a. Type lscluster and press Enter. ClusterId Name PrimaryServer SecondaryServer cluster1.company.com strg001st001 strg002st001 List available disks b. Verify that the cluster name and domain are as shown as in the example above. Follow this procedure to view the list of available disks. 34 IBM SONAS 1.5.2: Software Configuration Guide

61 Follow the instructions to view a list of available disks (which are actually the LUNs that are provided by the 2851-IBM SONAS storage controller 2 Storage Controllers). This list of disks (LUNs) will be used in the following sections to create the file system. Complete the following steps to view the list of available disks: Note: The IBM 2851-DR1/DE1 information applies to hardware configurations purchased before release As of release 1.4.1, for any new configurations that are shipped from manufacturing, DR1/DE1s have been withdrawn. 1. Type lsdisk and press Enter. Note: The -c option is not necessary if the Tip listed in Step 1 of Create the CTDB Cluster is followed. A list of available disks is displayed as in the following example: Name File system Failure group Type Pool Status Availability Timestamp array0_sas_60001ff b89de003c 1 system ready up 2/25/14 3:03 AM array0_sas_60001ff d89e0003e 1 system ready up 2/25/14 3:03 AM array0_sas_60001ff f89e system ready up 2/25/14 3:03 AM array0_sas_60001ff e system ready up 2/25/14 3:03 AM array0_sas_60001ff e system ready up 2/25/14 3:03 AM array0_sas_60001ff e system ready up 2/25/14 3:03 AM array1_sas_60001ff c89df003d 1 system ready up 2/25/14 3:03 AM array1_sas_60001ff e89e1003f 1 system ready up 2/25/14 3:03 AM array1_sas_60001ff e system ready up 2/25/14 3:03 AM array1_sas_60001ff e system ready up 2/25/14 3:03 AM array1_sas_60001ff e system ready up 2/25/14 3:03 AM array1_sas_60001ff e system ready up 2/25/14 3:03 AM v For an IBM SONAS gateway configuration with IBM XIV Storage System external storage, a list of available disks will be displayed as in the following example: Name File system Failure group Type Pool Status Availability Timestamp XIV _S_GW_Vol_01 1 system ready 9/24/14 2:56 PM XIV _S_GW_Vol_02 1 system ready 9/24/14 2:56 PM XIV _S_GW_Vol_03 1 system ready 9/24/14 2:56 PM XIV _S_GW_Vol_04 1 system ready 9/24/14 2:56 PM XIV _S_GW_Vol_05 1 system ready 9/24/14 2:56 PM XIV _S_GW_Vol_06 1 system ready 9/24/14 2:56 PM XIV _S_GW_Vol_07 1 system ready 9/24/14 2:56 PM XIV _S_GW_Vol_08 1 system ready 9/24/14 2:56 PM XIV _S_GW_Vol_09 1 system ready 9/24/14 2:56 PM XIV _S_GW_Vol_10 1 system ready 9/24/14 2:56 PM Note: If the IBM SONAS was ordered with Gateway to IBM XIV Storage System (Feature Code 9006, previously irpq 8S1101) or Gateway to Storwize V7000 (Feature Code 9007), or IBM DCS3700 or IBM SONAS Storage 2 with FC9008 option, then a different naming convention may be used for the disks. This comment applies to the following sections: v List available disks on page 34 v Listing available disks by physical location v Creating a second failure group on page 36 v Creating the GPFS File System on page 38 Listing available disks by physical location Follow this procedure to view the list of available disks, along with the information about physical location of the disk. Chapter 4. Software configuration procedures 35

62 This topic lists the available disks (which are actually the LUNs that are provided by the 2851IBM SONAS storage controller 2 storage controllers). The output of the command in this topic is similar to the lsdisk output, except that it provides information about physical location. In a larger system this information might be useful when you select disks for a second failure group using the procedure in the next section. Complete the following steps to view the list of available disks and information about the physical location of the disk. 1. Type lsdisk -v 2. Press Enter. A list of available disks is displayed as in the following example: Disk name File System Failure Group Type Pool Status Availability TimeStamp ID Quorum Comment Size Available Blocks Available Fragments Storage Node(s) array0_sas_60001ff0732a gpfs0 1 dataandmetadata system ready up 8/17/12 3:03 AM AC1F86024FEDB87B no desc 3.12 TB 3.07 TB MB strg001st001,strg002st001 array0_sas_60001ff0732a gpfs0 1 dataandmetadata system ready up 8/17/12 3:03 AM AC1F86024FEDB881 no desc 3.12 TB 3.07 TB MB strg001st001,strg002st001 array1_sas_60001ff0732a f0002 gpfs1 1 dataandmetadata system ready up 8/17/12 3:03 AM AC1F86014FEDB875 no desc 3.12 TB 3.10 TB 696 kb strg002st001,strg001st001 array1_sas_60001ff0732a gpfs1 2 dataandmetadata system ready up 8/17/12 3:03 AM AC1F86014FEDB88D no desc 3.12 TB 3.10 TB 1.05 MB strg002st001,strg001st001 Note: The example is for a system with one 2851-IBM SONAS storage controller 2 storage controller and one -IBM SONAS storage expansion 2 storage expansion. Each Storage Drawer contains six arrays. a. For an IBM SONAS gateway configuration with IBM XIV Storage System external storage, a list of available disks will be displayed as in the following example: Disk name Storage Node(s) XIV Serial XIV _S_GW_Vol_01 strg001st001,strg002st XIV _S_GW_Vol_02 strg001st001,strg002st XIV _S_GW_Vol_03 strg001st001,strg002st XIV _S_GW_Vol_04 strg001st001,strg002st XIV _S_GW_Vol_05 strg001st001,strg002st XIV _S_GW_Vol_06 strg001st001,strg002st XIV _S_GW_Vol_07 strg001st001,strg002st XIV _S_GW_Vol_08 strg001st001,strg002st XIV _S_GW_Vol_09 strg001st001,strg002st XIV _S_GW_Vol_10 strg001st001,strg002st Creating a second failure group You can use this procedure to create a second failure group and move disks to the group. In the screen shown in section List available disks on page 34, all the available disks are stored in a single File System Failure Group (failure group 1). Follow the instructions in this section to move some of those disks into a second failure group. By creating a second failure group, the file system can replicate critical data (metadata) in both failure groups to minimize the risk of data loss if a single array or storage controller fails. Note: Do not use this procedure to configure an IBM SONAS gateway with IBM XIV Storage System external storage. For additional information about configuring IBM XIV Storage System, see sonas1ic/topic/com.ibm.sonas.doc/xiv_configxivstorage.html. 36 IBM SONAS 1.5.2: Software Configuration Guide

63 Use the following command to create a second failure group: 1. Type chdisk <list of disks> --failuregroup 2 where <list of disks> is up to half of the disk names displayed by using the lsdisk command in the previous section, separated by commas with no spaces. Note: a. If your system has only one IBM SONAS Storage Controller 2, select half of the disk names. One easy way to do this is to select all the names that start with array1. You can use copy and paste to insert disk names. b. If your system has more than one IBM SONAS Storage Controller 2, consider configuring the disks attached to one Storage Controller into a different failure group than the disks attached to another Storage Controller. This helps ensure that a failure of a single IBM SONAS Storage Controller 2 will not affect both failure groups. c. To determine which disks are attached to a single IBM SONAS Storage Controller 2, look at the first ten hex digits of the long number in the disk name. All disks attached to a IBM SONAS Storage Controller 2 will have the same first ten hex digits. d. In a large system, you may find it easier to use the storage nodes from section Listing available disks by physical location on page 35 to split disks between the failure groups. As an example, if you have four storage nodes, leave drives attached to storage nodes 1 and 2 in Failure group 1, and put drives attached to storage nodes 3 and 4 in Failure group 2. Example: cli chdisk array1_sas_60001ff c89df003d,array1_sas_60001ff e89e1003f, array1_sas_60001ff e30041,array1_sas_60001ff e50043, array1_sas_60001ff e70045,array1_sas_60001ff e failuregroup 2 Note: The command is a single line, containing a list of disk names from the 'lsdisk' or 'cnquerydisks' command, separated by commas with no spaces. 2. Press Enter. 3. To verify that the second failure group has been created, perform the following sub-steps: a. Type lsdisk and press Enter. Name File system Failure group Type Pool Status Availability Timestamp array0_sas_60001ff b89de003c 1 system ready 2/25/10 3:03 AM array0_sas_60001ff d89e0003e 1 system ready 2/25/10 3:03 AM array0_sas_60001ff f89e system ready 2/25/10 3:03 AM array0_sas_60001ff e system ready 2/25/10 3:03 AM array0_sas_60001ff e system ready 2/25/10 3:03 AM array0_sas_60001ff e system ready 2/25/10 3:03 AM array1_sas_60001ff c89df003d 2 system ready 2/25/10 3:03 AM array1_sas_60001ff e89e1003f 2 system ready 2/25/10 3:03 AM array1_sas_60001ff e system ready 2/25/10 3:03 AM array1_sas_60001ff e system ready 2/25/10 3:03 AM array1_sas_60001ff e system ready 2/25/10 3:03 AM array1_sas_60001ff e system ready 2/25/10 3:03 AM 4. Verify that the disks are now split into two failure groups as shown in the preceding example. Chapter 4. Software configuration procedures 37

64 Creating the GPFS File System Follow this procedure to create a file system and assign disks to it. With these instructions, you can create a file system before the external network and the authentication services are set up. 1. Type mkfs gpfs0 /ibm/gpfs0 -F <list of disks> -R meta [--dmapi --nodmapi] where v <list of disks> is a set of the disk names displayed by the lsdisk command in the previous section, separated by commas. v --dmapi and --nodmapi are keywords used to designate that support for external Storage Pool Management software (example: Tivoli Storage Manager) is enabled (--dmapi) or disabled (--nodmapi). Specify either --dmapi or --nodmapi. If you don't specify either, the default is --dmapi. Note: dmapi is required for HSM and Antivirus support. a. Type mkfs gpfs0 /ibm/gpfs0 -F <list of disks> [--dmapi --nodmapi] for an IBM SONAS gateway system using IBM XIV Storage System external storage. Note: a. The command is a single line, containing a set of disks from the 'lsdisk' command separated by commas with no spaces. b. If you are creating multiple file systems, issue this command once for each file system, assigning a different set of disks to each file system. Be sure to include disks from both failure groups in each file system to allow replication of critical data (metadata). c. If you are planning to use external Storage Pool Management software, you must specify the --dmapi keyword. d. The double '--' before the 'nodmapi' or 'dmapi' keyword is required. IBM SONAS system: v Example: mkfs gpfs0 /ibm/gpfs0 -F array0_sas_60001ff b89de003c,array0_sas_60001ff d89e0003e, array0_sas_60001ff f89e20040,array0_sas_60001ff e40042, array0_sas_60001ff e60044,array0_sas_60001ff e80046, array1_sas_60001ff c89df003d,array1_sas_60001ff e89e1003f, array1_sas_60001ff e30041,array1_sas_60001ff e50043, array1_sas_60001ff e70045,array1_sas_60001ff e R meta --dmapi IBM SONAS gateway system using IBM XIV Storage System external storage: v Example: mkfs gpfs0 /ibm/gpfs0 -F XIV _S_GW_Vol_23,XIV _S_GW_Vol_24 --dmapi Note: The example above assumes you are creating a file system with the default block size (256KB). If you use the -b parameter to specify a different block size, be aware that NDMP backup prefetch is designed to work on files that are less than or equal to 1MB in size. NDMP backup prefetch will not work for a file system that has block size greater than 1MB. 2. Press Enter. 3. To verify that the File System has been created, perform the following sub-steps: a. Type lsfs and press Enter. Output similar to the following is shown: 38 IBM SONAS 1.5.2: Software Configuration Guide

65 Cluster Devicename Quota Blocksize Inodes Replication Dmapi Block allocation type cluster1.company.com gpfs0 user;group;fileset 256kB 4213 meta no scatter b. Verify that the file system is shown, and that it is configured with Metadata replication, as in the preceding example. 4. To verify that the disks are properly assigned to the file system, perform the following sub-steps: a. Type lsdisk and press Enter The output for an IBM SONAS system will appear in the following format: Name File system Failure group Type Pool Status Availability Timestamp array0_sas_60001ff07db580d89e30001 gpfs0 1 dataandmetadata system ready up 8/11/11 1:05 PM array0_sas_60001ff07db580f89e50003 gpfs0 1 dataandmetadata system ready up 8/11/11 1:05 PM array0_sas_60001ff07db581189e70005 gpfs0 1 dataandmetadata system ready up 8/11/11 1:05 PM array0_sas_60001ff07db581389e90007 gpfs0 1 dataandmetadata system ready up 8/11/11 1:05 PM array0_sas_60001ff07db581589eb0009 gpfs0 1 dataandmetadata system ready up 8/11/11 1:05 PM array0_sas_60001ff07db581789ed000b gpfs0 1 dataandmetadata system ready up 8/11/11 1:05 PM array0_sas_60001ff07db600c8a5a0000 gpfs0 2 dataandmetadata system ready up 8/11/11 1:05 PM array0_sas_60001ff07db600e8a5c0002 gpfs0 2 dataandmetadata system ready up 8/11/11 1:05 PM array0_sas_60001ff07db60108a5e0004 gpfs0 2 dataandmetadata system ready up 8/11/11 1:05 PM array0_sas_60001ff07db60128a gpfs0 2 dataandmetadata system ready up 8/11/11 1:05 PM array0_sas_60001ff07db60148a gpfs0 2 dataandmetadata system ready up 8/11/11 1:05 PM array0_sas_60001ff07db60168a64000a gpfs0 2 dataandmetadata system ready up 8/11/11 1:05 PM The output for an IBM SONAS Gateway system using IBM XIV Storage System external storage will appear as follows: Name File system Failure group Type Pool Status Availability Timestamp XIV _S_GW_Vol_01 gpfs0 1 dataandmetadata system ready up 9/24/12 4:54 PM XIV _S_GW_Vol_02 gpfs0 1 dataandmetadata system ready up 9/24/12 4:54 PM XIV _S_GW_Vol_03 gpfs0 1 dataandmetadata system ready up 9/24/12 4:54 PM XIV _S_GW_Vol_04 gpfs0 1 dataandmetadata system ready up 9/24/12 4:54 PM XIV _S_GW_Vol_05 gpfs0 1 dataandmetadata system ready up 9/24/12 4:54 PM XIV _S_GW_Vol_06 gpfs0 1 dataandmetadata system ready up 9/24/12 4:54 PM XIV _S_GW_Vol_07 gpfs0 1 dataandmetadata system ready up 9/24/12 4:54 PM XIV _S_GW_Vol_08 gpfs0 1 dataandmetadata system ready up 9/24/12 4:54 PM XIV _S_GW_Vol_09 gpfs0 1 dataandmetadata system ready up 9/24/12 4:54 PM XIV _S_GW_Vol_10 gpfs0 1 dataandmetadata system ready up 9/24/12 4:54 PM b. Verify that the disks are now part of the specified file system (gpfs0 in the example), and that the file system includes disks from both failure groups, as in the preceding example. Configure the DNS Server IP Addresses and Domains Follow this procedure to configure the Domain Name Services (DNS) servers and domains for the IBM Scale Out Network Attached Storage Software system. CAUTION: The onnode command require root access and you must not use the command unless directed to do so by the next level of IBM support. The IBM Scale Out Network Attached Storage Software must be configured with the IP Address of the Domain Name Services (DNS) servers and the domains. 1. Refer to Table 7 on page 7 for the Domain Name Services (DNS) server IP address and search string. 2. Use the setnwdns command to configure the system to use one, two, or a maximum of three external DNS servers. Type setnwdns <ipaddresslist> [--domain <domainname>] [--search <searchstringlist>] where v <ipaddresslist> is the DNS server IP address. This can be a comma-separated list of DNS server IP addresses. Chapter 4. Software configuration procedures 39

66 v <domain> is the domain suffix of the cluster. If the --domain keyword is specified then it must be followed by the domain name. v <searchstringlist> is the domain. If the --search keyword is specified then it must be followed by one search name or a comma-separated list of search names. Example for a single DNS server with no domain or search strings: setnwdns Example for a single DNS server with a domain name and a single search string: setnwdns domain company.com --search company.com Example for two DNS servers with a domain name and two search strings: setnwdns , domain company.com --search servers.company.com,storage.company.com Note: a. The double '--' before the 'domain' and 'search' keywords is required. b. The command is a single line. 3. Press Enter. 4. To verify that the DNS server IP address and domain have been configured, perform the following sub-steps: a. Type onnode all cat /etc/resolv.conf and press Enter. >>NODE: << search servers.company.com domain company.com nameserver >>NODE: << search servers.company.com domain company.com nameserver >>NODE: << search servers.company.com domain company.com nameserver >>NODE: << search servers.company.com domain company.com nameserver b. Verify that the IP addresses and search strings you specified are shown as in the example above. Note: 1) The IP addresses shown are for the interface nodes and management nodes. The storage nodes are not included because they are not accessible on the customer network. 2) The example shown above is for a single DNS server IP address ( ) with a single search string (servers.company.com) and a single domain (company.com). GUI Navigation You can create a DNS server using Sonas GUI. To create a new DNS server: 1. Log on to the GUI and select Settings > Directory Services > DNS. The Directory Services page appears. 40 IBM SONAS 1.5.2: Software Configuration Guide

67 2. Click Edit. 3. Click + to add a new server. 4. Enter the DNS domain name. It is the domain suffix name placed after the host or computer name. For example, mydomain.com. 5. Enter the IP addresses of the DNS servers. You can add up to three IP addresses. 6. Enter the DNS search domains. It: specifies the default domain suffix names. 7. Click OK to save the changes. Configure Data Path IP Addresses Follow this procedure to configure data path IP addresses. 1. Type mknw <subnet>/<subnetmask> <subnet:gateway list> [--vlanid <vlanid>] [--add <ip list>] where v <subnet> is the subnet specified in Table 16 on page 18. Example: v <subnetmask> is the CIDR equivalent of the subnet mask specified in Table 16 on page 18. Example: 24 v <subnet:gateway list> is a comma-separated list of subnet:gateway combinations as specified in Table 17 on page 20. Example: /0: where is the zero subnet, /0 is the subnet mask (in CIDR format), and is the gateway. v <vlanid> is the VLAN ID as specified in Table 16 on page 18. If the VLAN ID is blank, do not specify the --vlanid parameter. v <ip list> is a comma-separated list of IP addresses as specified in Table 17 on page 20. Example: , , Example (one physical network with no VLAN): cli mknw / /0: add , , Example (one physical network with a VLAN): cli mknw / /0: vlanid add , , Note: The command is a single line. 2. Press Enter. 3. If more than one network is needed, repeat the preceding steps until all networks have been configured. 4. To verify that the IP addresses have been configured, perform the following sub-steps: a. Type lsnw. b. Press Enter. c. Verify that the IP addresses are all listed and correct. Configure Data Path IP Address Group Follow this procedure to configure data path IP address group using network group. 1. Refer to Group Name as specified in Table 16 on page 18. Public interfaces are bonded redundantly into network groups. Bonds for each node within a network group must have identical interface names. This is required for proper node fail over, where network IP addresses and supporting interfaces are moved from node to node within the network group due to a fail Chapter 4. Software configuration procedures 41

68 over event. For example, if a network group is attached to ethx0, all nodes within that network group must support the ethx0 bond interface. When creating network groups, configuring uniform node characteristics for all nodes within a network group maximizes node behavior consistency on node fail over. If node interfaces are not configured consistently within a network group such that there is an intermix of 1 GbE and 10 GbE speeds on an identical interface for different nodes within a network group, if a node with only 1 GbE network bandwidth capability for an interface assumes responsibility during fail over from a node that had a 10 GbE network speed for the identical interface, reduced client performance and undesired behavior can occur. Other node characteristic consistencies that maximize node fail over behavior include bonding mode, MTU size, and VLAN assignment. See Managing the interface network for details. v If the Group Name has been provided, go to step 2. v If the Group Name is blank, notify the customer that a Group Name must be created. Note: In the current version of IBM SONAS Software, a network group must be created to avoid a potential problem with NDMP. If the customer selects a Group Name, record it in the Group Name field in Table 16 on page 18. If the customer does not select a Group Name, record "interfacegroup" in the Group Name field in Table 16 on page 18. Continue with the following steps. 2. Type mknwgroup <groupname> <nodelist> where v <groupname> is the Group Name specified in Table 16 on page 18. Example: interfacegroup v <nodelist> is a comma-separated list of interface node host names specified in Table 17 on page 20. Example: int001st001,int002st001,int003st001 Example: mknwgroup interfacegroup mgmt001st001,mgmt002st001,int001st001,int002st001,int003st001 Note: The command is a single line. The mknwgroup command creates a group of nodes with the name groupname. An existing network configuration can be attached to this group of nodes. Note that the use of custom groups is mutually exclusive with the use of the default group. Therefore, this command fails if this cluster's default group has at least one network attached. A group of nodes consists of at least one node. For redundancy a network group should contain at least two nodes. 3. Press Enter. 4. To verify that the IP Addresses have been configured, perform the following sub-steps: a. Type lsnwgroup -r b. Press Enter. c. Verify that the group is listed and correct. Attach the Data Path IP Address Group Follow this procedure to attach data path IP address group using subnet and network group. Note: 42 IBM SONAS 1.5.2: Software Configuration Guide

69 Please note the following recommendations when configuring nodes with both 1Gb Ethernet and 10Gb Ethernet Network Interface Connectivity: v For Management Nodes that utilize both 1 and 10 Gb Ethernet network interfaces, apply the Management network IP to the 1 Gb Ethernet network interface (normally ethx0) and configure the data traffic IPs to use the 10 Gb Ethernet network interface (normally ethx1). v For Interface Nodes with 1 and 10 Gb Ethernet network interfaces, configure two networks, one for each network interface speed. The use of independent subnets for each network interface bond is strongly recommended. Failure to do this can result in routing ambiguity issues. 1. Type attachnw <subnet>/<subnetmask> ethx0 -g <groupname> where v <subnet> is the subnetwork specified in Table 16 on page 18. Example: v <subnetmask> is the subnet mask (in CIDR format) specified in Table 16 on page 18. Example: 24 v <groupname> is the Group Name specified in Table 16 on page 18. Example: interfacegroup Example: attachnw /24 ethx0 -g interfacegroup Note: The command is a single line. 2. To verify that the IP Address group has been configured, perform the following sub-steps: a. Type lsnw. b. Press Enter. c. Verify that the group is listed and correct. If the Subnet settings allows for network overlap or conflict between the data path addresses and the management path addresses, either network could become unavailable. Important: It is highly recommended, that for a given VLAN subnet definition, you must also consistently provide the same VLAN ID (tag) for that subnet on any network definition that you create within a common interface bond on the clustered system. If you define a VLAN on your management network, and you have the same VLAN subnet on the same interface bond for data connectivity, ensure that you provide the exact same VLAN ID. Additionally, the switch configurations supporting this VLAN should be same for all connections that the VLAN uses. Ensure that you use trunk, access link, or native VLAN consistently on the switch ports that are connected to all ports on the clustered system. The clustered system shares the same VLAN subnet. Avoid defining the same VLAN with a tag ID either different or missing, when providing the VLAN ID to a management network bond, as well as to a shared data network bond. Unless you have intentionally configured your switching network to support this unique case, where the VLAN ID for the management network and data network are not the same and you are confident on how this will be routed from the clustered system to your switch, you might incur unpredictable routing path behavior and even network connectivity loss. 3. To verify that CTDB and GPFS are healthy on all nodes and also that network interfaces are up, perform the following sub-steps: Chapter 4. Software configuration procedures 43

70 Configure the NAT gateway a. Type lsnode. b. Press Enter. c. Verify that CTDB and GPFS show an active status. d. Type lsnwinterface. e. Press Enter. f. Verify that network interfaces show an UP status. You can use this procedure to configure an IBM SONAS system to use the NAT gateway function. Typically, network address translation (NAT) is a technique that is used with network routers. The benefit of the NAT gateway within IBM SONAS is that it provides a network failover path by which local IBM SONAS functions on a given management node or interface node can still access public services such as DNS and LDAP. The path taken is private network to NAT gateway node, and then to public network. The response from the remote public services takes the inverse path when returning communication. This function prevents a node which loses public network connectivity from becoming more unhealthy due to internal functions being unable to reach out to those critical services. The NAT gateway is not a Data Path; it is not used to write files to or read files from the interface nodes) failover function. It is used only by internal functions on a public network outage. The NAT gateway function has two types of node functionality: v Master - Functions that can host and use the NAT Gateway. v Slave - Functions that can use only the NAT gateway via private network access. When the NAT gateway is created using the CLI mknwnatgateway command, management nodes or interface nodes that host the same network as the NAT gateway IP are available to be a NAT gateway master. Management nodes or interface nodes that do not host the network of the NAT gateway are configured as slaves. There is only one active node that hosts the NAT gateway from the pool of possible hosts (Masters). To configure the NAT gateway function on IBM SONAS, the customer must supply an unused IP address (cannot be overlapping with Management or Data Path IP addresses). This IP address should come from a network that is hosted by the Data Path public networks (not the Management network). Note: The external network must also have a default route defined. If no default route is defined, the command fails. 1. Type mknwnatgateway <external ip> where <external ip> is the IP address as specified in Table 8 on page 8. Example: mknwnatgateway Note: The command is a single line. 2. Press Enter. 3. To verify that the NAT gateway has been configured, perform the following sub-steps: a. Type lsnwnatgateway and press Enter. 44 IBM SONAS 1.5.2: Software Configuration Guide

71 Public IP Public interface Default gateway Private network Nodes /24 ethx / , , , Removing a NAT gateway b. Verify that the Public IP address that is shown on the screen is the same as the IP address that you specified previously using the mknwnatgateway command. You can use the command-line interface (CLI) or the graphical user interface (GUI) to remove the configuration of a clustered trivial database (CTDB) network address translation (NAT) gateway. GUI navigation To with this function in the management GUI, log on to the GUI and select Settings > Network. CLI usage Using the CLI, issue the rmnwnatgateway command. Configure the authentication method These topics provide information about configuring your authentication method. The customer has a choice of the following methods for user Authentication. 1. Refer to Authentication Method in Table 10 on page 10. v If the Authentication Method is Microsoft Active Directory (AD), goto Configure for authentication using Active Directory. v If the Authentication Method is Lightweight Directory Access Protocol (LDAP), go to Configure for authentication using Lightweight Directory Access Protocol (LDAP) on page 49. v If the Authentication Method is Samba Primary Domain Controller (PDC), go to Configure for authentication using Samba PDC on page 51. v If the Authentication Method is NIS, go to Configure for NIS on page 53. v If the Authentication Method is Local authentication, go to Configure local authentication on page 56. Configure for authentication using Active Directory Follow this procedure to configure the IBM SONAS system for authenticating users using Active Directory. The remote server that runs the Active Directory software provides authentication services. Authentication is the process of verifying the identify of a user. This is typically accomplished by verifying a user id and password. When a user attempts to access the IBM SONAS system, they need to enter a user ID and password. The user ID and password are sent across the customer's network to the remote authentication server, which compares the user ID and password to valid user ID and password combinations that are stored in its database. If they match, the remote server sends a response back to the system, confirming that the user has been authenticated. Chapter 4. Software configuration procedures 45

72 Note: Configuration of authentication for Active Directory with SFU and NIS is only available using the command line interface (CLI). The following procedure configures the IBM SONAS system to communicate with the remote authentication server. 1. Type the following command all on one line and then press Enter: # cfgad [-c {clusterid clustername}] -s adservername -u username [-p password]\ --idmaprole {master subordinate} [--preferreddc preferreddomaincontroller]\ [--idmapconfig idmapconfig] [--krbkeytabfile krbkeytabfile] Example: # cfgad -s u user1 -p test01 --idmaprole master --idmapconfig : For more information on each parameter used in the command, refer to the manpage for cfgad in the Information Center. 2. Press Enter. 3. Select the any of the following ID mapping method: v v v If you have selected automatic ID mapping as the ID mapping method, go to Configuring ID mapping using automatic ID mapping. If you have selected SFU as the ID mapping method, go to Configuring ID mapping using SFU on page 47. If you have selected NIS as the ID mapping method, go to Configure for NIS on page 53. Configuring ID mapping using automatic ID mapping Automatic ID mapping method can be used to create UID or GID of a user or group. The ID maps are stored in the internal repositories. When external ID mapping server is not present in the environment or cannot be used, then this ID mapping method can be used. The following example configures an IBM SONAS system with Active Directory. 1. Submit the lsauth command to verify that no authentication method is configured, as in the following example: # lsauth EFSSG0571I Cluster st001.virtual1.com is not configured with any type of authentication server. 2. Submit the cfgad command to configure the IBM SONAS system with Active Directory, as in the following example: # cfgad -s u user1 -p test01 --idmaprole master --idmapconfig : (1/9) Fetching the list of cluster Nodes. (2/9) Check if cfgcluster has done the basic configuration successfully. (3/9) Check whether Interface nodes are reachable from management node. (4/9) Detection of AD server and fetching domain information from AD server. (5/9) Check whether AD server is reachable from Interface nodes. (6/9) Joining the domain of the specified ADS. (7/9) Updating the system with ADS configuration details. (8/9) Finalizing configuration. (9/9) Updating the database. EFSSG1000I The command completed successfully. 3. Submit the lsauth command to verify that the Active Directory authentication method is configured properly, as in the following example: # lsauth AUTH_TYPE = ad idmapconfig = , idmappingmethod = auto domain = SONAS clustername = st001.virtual1.com username = user1 idmaprole = master adhost = SONAS.COM passwordserver = * krbmode = off realm = SONAS.COM EFSSG1000I The command completed successfully. 46 IBM SONAS 1.5.2: Software Configuration Guide

73 See Authentication limitations for more information about the following authentication and ID mapping related limitations: v Limitations of configuring the IBM SONAS system with Active Directory v v Preventing loss of data access by using the correct procedure if you are changing from NIS ID mappings to Active Directory ID mappings Preventing loss of data access, while changing the ID mapping parameters of an already existing Active Directory configuration While using automatic ID mapping, in order to have same ID maps on systems sharing asynchronous replication or remote caching relationship, you need to export the ID mappings from the system whose ID map role is master to the system whose ID map role is subordinate. See Working with ID maps and ID map role for more information on how to export or import ID maps from one system to another. See Listing the configured ID maps for more information on how to see the ID maps configured with AD based authentication. This is useful when you plan to use asynchronous replication or remote replication feature of the IBM SONAS system. See Best practices for authentication and ID mapping configurations while using asynchronous replication or remote caching for more information. The following list provides the preconditions to configure AD based authentication and automatic ID mapping: v IBM SONAS system is configured. v v ID map role of the system is identified. See Specifying the ID map role for more information. IBM SONAS administrator has calculated the range depending upon the maximum RID (allocated + expected growth). See Using the ID map configuration option for more information. Configuring ID mapping using SFU The following example describes configuring AD server with the SFU extension schema and then configures the IBM SONAS system with AD authentication and SFU ID mapping. For this example, the following prerequisites must be met: v Microsoft Windows Server 2008 is installed v IBM SONAS version 1.1 or later is installed Perform the following steps: 1. Configure an authoritative time server in the Windows Server. 2. On the Windows Server Manager (ADS2008), install Identity Management for UNIX components (SFU in Windows 2003). The software is part of the Windows package; there is no need for additional downloads or upgrades from the web. Add the following Roles: v Active Directory Domain Services, user and group management v DNS Server, name resolution, including IBM SONAS system round robin v Network Policy and Access Services v File Services, which replaces the package named Services for Unix. The File Services role provides NFS client and NFS server capabilities as well as Unix Extensions. Chapter 4. Software configuration procedures 47

74 Note: To verify the installation, ensure that the UNIX Attributes tab is available in the Administrator Properties. 3. Terminal Services is optional, and might be used to increase the number of parallel setups 4. Configure a test user, for example, Administrator v v v Select Administrator. Set the UID to a value in the range defined using the IBM SONAS CLI command cfgsfu in the next step. Click Member Of tab and ensure that primary group is set to Domain users. Select group Domain Users and set the GID to a value in the range defined using the using the IBM SONAS CLI command cfgsfu in the next step. 5. Ensure that no authentication is configured on the IBM SONAS system. Submit the lsauth command to verify this. For example: # lsauth EFSSG0571I Cluster st001.virtual1.com is not configured with any type of \ authentication server. 6. Submit the cfgad command to configure AD, define ID map role for the IBM SONAS system, and configure the ID map ranges for automatic ID mapping, as in the following example: # cfgad -s u user1 -p test01 --idmaprole master \ --idmapconfig : Submit cfgsfu command for SFU ID mapping, as in the following example: # cfgsfu --configparameters ST001, ,rfc2307 EFSSG1000I The command completed successfully. Note: Schema mode is based on the operating system of the domain. Specify 'rfc2307' for Microsoft Windows 2008 or Windows 2003 with R2 and 'sfu' for Windows 2000 and Windows 2003 releases prior to R2. 8. Submit the lsauth command to verify the ID mapping method and the ID mapping range for the domain, as in the following example: # lsauth AUTH_TYPE = ad idmapconfig = , domain = SONAS idmappingmethod = sfu clustername = st001.virtual1.com username = user1 idmaprole = master SFU_ST001 = ad, ,rfc2307 adhost = SONAS.COM krbmode = off passwordserver = * realm = SONAS.COM EFSSG1000I The command completed successfully. 9. Submit the chkauth command with userinfo option to check the UID and GID of the user and its primary group, as in the following example: # chkauth -i -u ST001\\testuser1 UID GID Home_Directory Template_Shell FETCH USER INFO SUCCEEDED /var/opt/ibm/sofs/scproot /usr/bin/rssh EFSSG1000I The command completed successfully. 48 IBM SONAS 1.5.2: Software Configuration Guide

75 Configure for authentication using Lightweight Directory Access Protocol (LDAP) The IBM SONAS system requires a method to authenticate a user. One method uses communications with a remote authentication server running Lightweight Directory Access Protocol (LDAP) software. The LDAP software provides authentication services. Note: Netgroups, managed by an LDAP server, are enabled when the cfgldap command is executed. You must define netgroups on the LDAP server, and create the NFS export. When creating the NFS export for use by LDAP netgoups, the NFS option must be specified in the The following procedure configures the IBM SONAS system to communicate with the remote LDAP authentication server. For more information, refer to the manpage for cfgldap in the SONAS Information Center. If you want to use SSL or TLS, a certificate file must be copied from the customer's LDAP server to the management node. Ask the customer's storage administrator to obtain the certificate file from the LDAP server and copy it to a directory on the management node The IBM SONAS system must not be configured with any authentication method before using the cfgldap IBM SONAS CLI command. Use the cfgldap command to configure the IBM SONAS system with an LDAP server. For SSL/TLS use the --cacertfile and --sslmode options; for Kerberos, use the --krbkdc, --krbrealm and --krbkeytabfile options. Note: If you configure multiple LDAP servers, you must add the server certificates of all of the LDAP servers into a single certificate file. Certificates are created with a specific LDAP server name, and if the server name does not match the LDAP server host names, the configuration can fail. The following example configures a IBM SONAS system with an external LDAP server. 1. Submit the lsauth command to verify that no authentication method is configured, as in the following example: # lsauth Output is displayed in the following format: EFSSG0571I Cluster st001.virtual1.com is not configured with any type of authentication server(ldap/ldap_krb/nt4/ad). 2. Submit the cfgldap command to configure the IBM SONAS system with an LDAP server, as in the following example: # cfgldap -s sonash1 -b dc=sonasldap,dc=com -D cn=manager,dc=sonasldap,dc=com -p secret --sslmode off Output is displayed in the following format: (1/9) Fetching the list of CTDB cluster Nodes. (2/9) Check if cfgcluster has done the basic configuration successfully. (3/9) Check whether Interface nodes are reachable from management node (4/9) LDAP Configuration started (5/9) Check whether LDAP server is reachable from Interface nodes (6/9) Verification of LDAP server from a node using credentials provided (7/9) Updating the system with LDAP configuration details (8/9) Finalizing configuration (9/9) Updating the database EFSSG1000I The command completed successfully. Note: The cfgldap command requires the ID and password of the LDAP administrator because the LDAP administrator (rootdn) and password is stored on the IBM SONAS system and is used during LDAP simple bind and for Chapter 4. Software configuration procedures 49

76 LDAP searches. The password stored on the IBM SONAS system is not accessible by IBM SONAS system administrative users. 3. Submit the lsauth command to verify that the LDAP server authentication method is configured, as in the following example: # lsauth Output is displayed in the following format: ldapusersuffix = ou=people clustername = st001 ldapuri = ldap://sonash1 ldapgroupsuffix = ou=group nscdmode = on ldapbinddn = cn=manager,dc=sonasldap,dc=com sslmode = off AUTH_TYPE = ldap ldapversion = 3 ldapbase = dc=sonasldap,dc=com krbmode = off EFSSG1000I The command completed successfully. Prerequisites for configuring the IBM SONAS system with Secure LDAP You must configure an LDAP server certificate to support secure communication between the IBM SONAS system and the LDAP server using SSL/TLS. The following example configures a IBM SONAS system with Secure LDAP. 1. Submit the lsauth command to verify that no authentication method is configured, as in the following example: # lsauth Output is displayed in the following format: EFSSG0571I Cluster st001.virtual1.com is not configured with any type of authentication server(ldap/ldap_krb/nt4/ad). 2. Submit the cfgldap command to configure the IBM SONAS system with an LDAP server, as in the following example: # cfgldap -s sonash1 -b dc=sonasldap,dc=com -D cn=manager,dc=sonasldap,dc=com -p secret --sslmode ssl --cacertfile /etc/cacert/cacert.pem Output is displayed in the following format: (1/9) Fetching the list of CTDB cluster Nodes. (2/9) Check if cfgcluster has done the basic configuration successfully. (3/9) Check whether Interface nodes are reachable from management node (4/9) LDAP Configuration started (5/9) Check whether LDAP server is reachable from Interface nodes (6/9) Verification of LDAP server from a node using credentials provided (7/9) Updating the system with LDAP configuration details (8/9) Finalizing configuration (9/9) Updating the database EFSSG1000I The command completed successfully. 3. Submit the lsauth command to verify that the LDAP server authentication method is configured, as in the following example: # lsauth Output is displayed in the following format: ldapusersuffix = ou=people clustername = st001 ldapuri = ldaps://sonash1 ldapgroupsuffix = ou=group nscdmode = on ldapbinddn = cn=manager,dc=sonasldap,dc=com sslmode = on AUTH_TYPE = ldap ldapversion = 3 ldapbase = dc=sonasldap,dc=com cacertfile = /etc/cacerts/cacert.pem krbmode = off EFSSG1000I The command completed successfully. Prerequisites for configuring the IBM SONAS system with Secure LDAP and MIT Kerberos An existing Kerberos infrastructure must be configured and accessible from the IBM SONAS system, and you must configure a KeyTab file to authenticate to the Kerberos Key Distribution Server (KDC). 50 IBM SONAS 1.5.2: Software Configuration Guide

77 Limitations of configuring the IBM SONAS system with Secure LDAP and MIT Kerberos Only CIFS protocol access is supported over Kerberos; Kerberized NFS, FTP, SCP and HTTPS are not supported. The following example configures a IBM SONAS system with Secure LDAP and MIT Kerberos. 1. Submit the lsauth command to verify that no authentication method is configured, as shown in the following example: # lsauth Output is displayed in the following format: EFSSG0571I Cluster st001.virtual1.com is not configured with any type of authentication server(ldap/ldap_krb/nt4/ad). 2. Submit the cfgldap command to configure the IBM SONAS system with an LDAP server, as in the following example: # cfgldap -s sonash1 -b dc=sonasldap,dc=com -D cn=manager,dc=sonasldap,dc=com -p secret --krbkdc sonash1 --krbrealm PUNE-KDC.COM --krbkeytabfile /home/scpuser/files/fvt4.kt --sslmode ssl --cacertfile /root/cacert.pem Output is displayed in the following format: (1/9) Fetching the list of CTDB cluster Nodes. (2/9) Check if cfgcluster has done the basic configuration successfully. (3/9) Check whether Interface nodes are reachable from management node (4/9) LDAP Kerberos Configuration started (5/9) Check whether LDAP server is reachable from Interface nodes (6/9) Verification of LDAP server from a node using credentials provided (7/9) Updating the system with LDAP-KRB configuration details (8/9) Finalizing configuration (9/9) Updating the database EFSSG1000I The command completed successfully. 3. Submit the lsauth command to verify that the LDAP server authentication method is configured, as in the following example: # lsauth Output is displayed in the following format: ldapusersuffix = ou=people ldapuri = ldaps://sonash1 clustername = st001 ldapgroupsuffix = ou=group nscdmode = on krbkeytabfile = /etc/krb5.keytab ldapbinddn = cn=manager,dc=sonasldap,dc=com krbkdc = sonash1 sslmode = on AUTH_TYPE = ldap_krb ldapversion = 3 krbrealm = PUNE-KDC.COM ldapbase = dc=sonasldap,dc=com krbmode = on cacertfile = /etc/cacerts/cacert.pem EFSSG1000I The command completed successfully. Configuring the LDAP server against an existing preconfigured cluster To use the graphical user interface (GUI) to configure the LDAP server against an existing preconfigured cluster, log on to the GUI and select Settings > Directory Services. Configure for authentication using Samba PDC Follow this procedure to configure the IBM SONAS system for authenticating users using remote server that runs Samba Primary Domain Controller (PDC) software. If you have selected NIS as the ID mapping method, go to Configuring IBM SONAS system with Samba PDC and NIS ID mapping on page 52. If you have selected ID mapping method as automatic ID mapping, go to Configuring the IBM SONAS system with Samba PDC and automatic ID mapping on page 52. Chapter 4. Software configuration procedures 51

78 The following procedures configurethe IBM SONAS system to communicate with the remote authentication server. For more information, refer to the manpage for cfgnt4 in the IBM SONAS Information Center. Configuring IBM SONAS system with Samba PDC and NIS ID mapping Prerequisites v No data files are stored on the IBM SONAS system. v NIS is used for all User ID Mapping. v Ensure that existing NIS IDs are not contained within the idmapuserrange or idmapgrouprange. See the --usermap of the cfgnis IBM SONAS CLI command documentation for more information. v All NIS user and group names must be in lower case, with white space replaced by the underscore character _. For example, an Active Directory user name CAPITAL Name should have a corresponding name on NIS as capital_name. Limitations of configuring the IBM SONAS system with Samba PDC and NIS The lowest value of idmapuserrange and idmapgrouprange cannot be less than Configuring the IBM SONAS system with Samba PDC and NIS The IBM SONAS system must be configured with Samba PDC before using the cfgnis IBM SONAS CLI command to configure IBM SONAS system authentication using Samba PDC with NIS, as in the following example: 1. Submit the lsauth command to verify that the Samba PDC authentication method is configured, as in the following example: # lsauth Output is displayed in the following format: AUTH_TYPE = nt4 idmappingmethod = auto domain = SMBPDC nt4netbiosname = sonash1 clustername = st001 nt4host = username = root EFSSG1000I The command completed successfully. 2. Submit the cfgnis IBM SONAS CLI command to configure the IBM SONAS system with Samba PDC and NIS, as in the following example: # cfgnis --extend -d PuneNis --servermap :Nis --domainmap SONAS:Nis --idmapuserrange idmapgrouprange useasidmap 3. Submit the lsauth command to verify that the Samba PDC authentication method is configured with NIS, as in the following example: # lsauth Output is displayed in the following format: AUTH_TYPE = nt4 idmapuserrange = NIS_ServerMap = :Nis domain = SMBPDC idmappingmethod = nis clustername = st001 nt4netbiosname = sonash1 username = root nt4host = NIS_Domain = Nis NIS_SONAS = Nis;none idmapgrouprange = EFSSG1000I The command completed successfully. Configuring the IBM SONAS system with Samba PDC and automatic ID mapping The IBM SONAS system can be configured with Samba PDC based authentication and automatic ID mapping by using the cfgnt4 command. 52 IBM SONAS 1.5.2: Software Configuration Guide

79 Configure for NIS Configuring the IBM SONAS system with Samba PDC and automatic ID mapping To configure IBM SONAS system with Samba PDC and automatic ID mapping, perform the following: 1. Submit the lsauth to verify that no authentication method is configured. # lsauth EFSSG0571I Cluster st001.virtual1.com is not configured with any type of authentication server. 2. Run cfgnt4 to configure IBM SONAS with Samba PDC based authentication. # cfgnt4 -s nt4netbiosname sonash1 -d SMBPDC -u root -p test01 3. Run lsauth to verify that the Samba PDC authentication method is configured. The following output is displayed: [st001.mgmt001st001 ~]# lsauth AUTH_TYPE = nt4 idmappingmethod = auto domain = SMBPDC nt4netbiosname = sonash1 clustername = st001.virtual1.com nt4host = username = root EFSSG1000I The command completed successfully. GUI navigation To work with this function in the management GUI, log on to the GUI and select Settings > Directory Services. Follow this procedure to configure the IBM SONAS system for authenticating users using Network Information Service (NIS) software. The IBM SONAS system requires a method to determine what access a user should be granted. One method uses communications with a remote server running Network Information Service (NIS) software. The NIS software provides information about NetGroup membership, and may optionally provide information about User ID Mapping. NetGroups are based on a server, not a user. The NIS server contains a list of NetGroups and the servers that are part of each NetGroup. When a server attempts to access the IBM SONAS, the NIS NetGroup support is used to determine if the server should be granted access. The IBM SONAS system supports netgroups using an NIS database. Table 23. IBM SONAS netgroup support CLI command to Netgroup database Authentication ID mapping configure NIS None None cfgnis NIS Active Directory Auto cfgad, cfgnis (AD) NIS Active Directory SFU cfgad, cfgsfu, cfgnis LDAP LDAP LDAP cfgldap Chapter 4. Software configuration procedures 53

80 The IBM SONAS system supports netgroups only for the purpose of grouping hosts to restrict access to NFS file systems exported by the IBM SONAS system. You can define a netgroup host in one of the following formats: v By name. For example, myhost v By fully qualified domain name. For example, myhost.mydom.com Because NFS inherently works with host names for netgroups, using IP addresses in netgroup definitions is not recommended. Note: The host name in the netgroup definition must have both forward and reverse DNS lookup configured, so that the IBM SONAS system can resolve both the host name and the host IP address, with which the mount service is requested on the IBM SONAS system. Otherwise, a mount request fails with an access denied error. There is no IBM SONAS CLI command to verify how the IBM SONAS system resolves a netgroup reference. You can submit the lsauth IBM SONAS CLI command to display the IBM SONAS system authentication method configuration. Use the methods that are appropriate to the authentication method that you have configured to verify the configuration of external authentication servers. The following the IBM Scale Out Network Attached Storage Software to communicate with the remote NIS server. For more information, refer to the manpage for cfgnis command in the IBM SONAS Information Center. Configuring authentication None and id mapping None NIS netgroups are implicitly supported when the IBM SONAS system is configured with no authentication, and with ID mapping in NIS. To configure NIS for the IBM SONAS system, perform the following steps: 1. Submit the lsauth IBM SONAS CLI command to verify that no authentication method is configured: # lsauth The following message is displayed if no authentication method is configured: EFSSG0571I Cluster cluster_name is not configured with any type of authentication server(ldap/ldap_krb/nt4/ad). 2. Submit the cfgnis IBM SONAS CLI command to configure the IBM SONAS system with the NIS authentication method, as in the following example: # cfgnis -d PuneNis --servermap "sonas8s1:punenis" 3. Resubmit the lsauth IBM SONAS CLI command to verify that the NIS authentication method is configured: # lsauth A message is displayed in the following format if the NIS authentication method is configured: AUTH_TYPE = nis NIS_ServerMap = sonas8s1:punenis idmappingmethod = none clustername = st001 NIS_Domain = PuneNis EFSSG1000I The command completed successfully. Configuring authentication Active Directory and id mapping Auto When the IBM SONAS system is configured with Active Directory authentication and auto ID mapping, you must use the cfgnis IBM SONAS CLI command to configure NIS netgroup lookup, as in the following example: 54 IBM SONAS 1.5.2: Software Configuration Guide

81 1. Submit the lsauth IBM SONAS CLI command to verify that the Active Directory authentication method is configured: # lsauth A message is displayed in the following format if the Active Directory authentication method is configured: AUTH_TYPE = ad idmapconfig = , idmappingmethod = auto domain = virtual1 clustername = st001 username = administrator adhost = ad1.virtual1.com passwordserver = * realm = virtual1.com EFSSG1000I The command completed successfully. 2. Submit the cfgnis IBM SONAS CLI command to configure the IBM SONAS system to use NIS with the Active Directory authentication method, as in the following example: # cfgnis --extend -d PuneNis --servermap " :PuneNis" 3. Resubmit the lsauth IBM SONAS CLI command to verify that the Active Directory authentication method is configured with NIS: # lsauth A message is displayed in the following format: AUTH_TYPE = ad NIS_ServerMap = :PuneNis idmapconfig = , domain = VIRTUAL1 idmappingmethod = auto clustername = st002 username = administrator adhost = AD1.VIRTUAL1.COM NIS_Domain = PuneNis passwordserver = * realm = VIRTUAL1.COM EFSSG1000I The command completed successfully. Note: The bolded entries are added to the previous display format. Configuring authentication Active Directory and id mapping SFU When the IBM SONAS system is configured with Active Directory authentication and SFU ID mapping, you must use the cfgnis IBM SONAS CLI command to configure NIS netgroup lookup, as in the following example: 1. Submit the lsauth IBM SONAS CLI command to verify that the Active Directory authentication method is configured and that ID mapping uses SFU: # lsauth A message is displayed in the following format if the Active Directory authentication method is configured: AUTH_TYPE = ad SFU_virtual1 = ad, ,sfu idmapconfig = , domain = orionis idmappingmethod = sfu clustername = st001 username = administrator adhost = win2k3r2.orionis.com passwordserver = * realm = orionis.com EFSSG1000I The command completed successfully. 2. Submit the cfgnis IBM SONAS CLI command to configure the IBM SONAS system to use NIS with the Active Directory authentication method and SFU ID mapping, as in the following example: # cfgnis --extend -d PuneNis --servermap " :PuneNis" 3. Resubmit the lsauth IBM SONAS CLI command to verify that the Active Directory authentication method is configured with SFU ID mapping and NIS: # lsauth A message is displayed in the following format: AUTH_TYPE = ad SFU_virtual1 = ad, ,sfu NIS_ServerMap = :PuneNis idmapconfig = , domain = orionis idmappingmethod = sfu clustername = st001 Chapter 4. Software configuration procedures 55

82 username = administrator adhost = win2k3r2.orionis.com NIS_Domain = PuneNis passwordserver = * realm = orionis.com EFSSG1000I The command completed successfully. Note: The bolded entries are added to the previous display format. Configuring authentication LDAP and id mapping LDAP When the IBM SONAS system is configured with LDAP authentication and LDAP ID mapping, netgroups are implicitly supported by the IBM SONAS system. Use the cfgldap command to configure LDAP netgroup lookup, as in the following example: 1. Submit the lsauth Storwize V7000 Unified CLI command to verify that no authentication method is configured: # lsauth The following message is displayed if no authentication method is configured: EFSSG0571I Cluster cluster_name is not configured with any type of authentication server(ldap/ldap_krb/nt4/ad). 2. Submit the cfgldap command to configure the IBM SONAS system to use the LDAP authentication method and LDAP ID mapping, as in the following example: # cfgldap -s sonash1 -b dc=sonasldap,dc=com -D cn=manager,dc=sonasldap,dc=com -p secret 3. Resubmit the lsauthcommand to verify that the LDAP authentication method is configured with LDAP ID mapping: # lsauth A message is displayed in the following format: AUTH_TYPE = ldap ldapversion = 3 ldapusersuffix = ou=people clustername = st001 ldapuri = ldap://sonash1 ldapbase = dc=sonasldap,dc=com ldapgroupsuffix = ou=group nscdmode = on ldapbinddn = cn=manager,dc=sonasldap,dc=com krbmode = off sslmode = off EFSSG1000I The command completed successfully. GUI usage To use the graphical user interface (GUI) to configure NIS as an authentication server or for ID mapping, log on to the GUI and select Settings > Directory Services. Configure local authentication Plan to use the IBM SONAS local authentication server to configure IBM SONAS system authentication when you do not have an external server for authentication and ID mapping and have a requirement of a limited number of data access users and groups. A CLI/GUI user with only SecurityAdmin role can create, modify, and delete users and groups stored on the internal authentication server used for authentication and ID mapping for NFS, CIFS, HTTPS, SCP, and FTP NAS protocols. Netgroups are not supported, nor is Kerberos for NFS or CIFS. The IBM SONAS local internal authentication server cannot be used as an external authentication server for other systems, including any other IBM SONAS system. The local data access user and local data access user group names stored on internal authentication server are case insensitive. 56 IBM SONAS 1.5.2: Software Configuration Guide

83 You can create a maximum of 100 local data access user groups and a maximum of 1000 local data access users. You can assign a local data access user to a maximum of 16 local data access user groups. Important: User and user group names of system, CLI, and data access / local authentication users and user groups should not be the same. Using duplicate names might result in unexpected behavior. To work with this function in the management GUI, do the following: 1. Select Settings > Directory Services > Authentication. 2. Select Configure. 3. Select Local Authentication and click Finish. Use the cfglocalauth IBM SONAS CLI command to configure internal authentication. Important: The cfglocalauth command disrupts all client connections, and all client file operations are interrupted. File services resume a few seconds after the command completes. To create a local data access user group on the internal authentication server, use the mknasgroup IBM SONAS CLI command and specify a group name using a minimum of 3, and a maximum of 32, ASCII characters. You can optionally use the -g option to specify a group ID (GID). If not specified, the GID is automatically generated. If you use the -g option, specifying a GID greater than 1024 avoids potential conflict with system and IBM SONAS CLI users. If you specify a GID less than or equal to 1024, a warning is displayed, and you must use the --force option to override the warning. The maximum GID value is 2,147,482,648. You can use the lsnasgroup IBM SONAS CLI command to display the group name and group ID (GID) of all of the local data access user groups stored on internal authentication server. An authorized CLI administrative user can use the rmnasgroup IBM SONAS CLI command, specifying a group name, to remove the definition of the specified local data access group. The local data access user group planned to be removed cannot be the primary group for any local data access user at that point in time. To create a local data access user on the internal authentication server, use the mknasusercommand and specify a user name using a minimum of 3, and a maximum of 32, ASCII characters. Use the following options with the mknasuser command: v -p: To specify a password, which must be a minimum of 8 characters in length. v v v v -g: To specify a primary group name. The specified primary group must already be defined as a local data access user group. -u: Optional. To specify a user ID (UID). If not specified, the UID is automatically generated. If you are specifying a UID greater than 1024, it avoids potential conflict with system and IBM SONAS CLI users. If you specify a UID less than or equal to 1024, a warning is displayed, and you must use the --force option to override the warning. The maximum UID value is 2,147,482,648. -e: Optional. To modify an address for the specified user. -G: Optional. To specify a comma-separated list of up to 15 supplementary local data access groups for the specified user. Each specified group name in the list must already be defined as a local data access group. Chapter 4. Software configuration procedures 57

84 To change the attributes of a local data access user on the internal authentication server, an authorized CLI/GUI administrative user can use the chnasuser command and specify a defined user name. You can use the following options with the chnasuser command: v v v v v Export the File Access Protocols -p: Optional. An authorized CLI/GUI administrative user can change the password, which must be a minimum of 8 characters in length. -g: Optional. To modify a primary group assignment. On modifying the current primary group it will automatically become part of the supplementary groups for the specified user. The specified primary group must already be defined as a local data access group. -e: Optional. To specify an address for the specified user. -a: Optional. To specify a comma-separated list, with no white space, of supplementary local data access user groups to be added to the list of supplementary local data access user groups for the specified user. -d: To specify a comma-separated list, with no white space, of supplementary local data access user groups to be removed from the list of supplementary authentication server local data access groups for the specified user. Each specified primary group in the list for either of these two options must already be defined as a local data access user group. The UID and user name cannot be changed. Follow this procedure for configuring a shared disk space to be accessible through the file access protocols. An export is a shared disk space accessible through the protocols specified during its creation. FTP, CIFS, or NFS exports can all be created, provided the protocol is enabled for the cluster. The specified directory (/ibm/gpfs0/shared) will be created by the mkexport command. Notes: 1. Do not mount the same NFS export on one client from two different IBM SONAS nodes. Data corruption might occur. 2. Do not export both a directory and any of its subdirectories from a server if both are part of the same file system. Do not export the same file system, or the same file, through multiple exports to the same set of clients. A client should never access the same file through two different server:export paths. The client cannot distinguish that the two objects are the same, so write ordering is not possible. Also, client-side caching will not function properly. In the IBM SONAS system, each export is assigned a new file system ID even if the exports are from the same file system. This could lead to data corruption, which is why it is not good practice. However, exporting both a parent and its child should not be necessary because exporting a parent directory causes all of its underlying directories within that file system to be exported. 3. Do not mount the same export twice on the same client. 4. While the use of nested mounts on the same filesystem is strongly discouraged, it is possible to create nested mounts using the IBM SONAS system. If nested mounts are configured on the IBM SONAS system, it is the customer's responsibility to exercise extreme caution to avoid the possibility of corruption. 5. POSIX ACLs for NFSv3 are not supported on the IBM SONAS system. 6. Clients should only mount IBM SONAS NFS exports using an IP address. Do not mount an IBM SONAS NFS export using a DNS RR entry name. If you 58 IBM SONAS 1.5.2: Software Configuration Guide

85 mount an IBM SONAS NFS export using a host name, ensure that the name is unique and remains unique. This restriction prevents data corruption and data unavailability, because the lock manager on the IBM SONAS system is not "clustered-system-aware." 1. Type mkexport shared /ibm/gpfs0/shared [--cifs [cifsoptions] [--http] [--ftp] [--scp] [--nfs <nfsoptions>] [--owner <owner>] where v --cifs [cifsoptions] is included if the CIFS protocol is checked in Table 15 on page 16. cifsoptions is a comma-separated key-value pair list. Valid CIFS options are: browseable=yes comment="place comment here" Example: -cifs browseable=yes,comment="ibm SONAS" v --http is included if the HTTP protocol is checked in Table 15 on page 16. v --ftp is included if the FTP protocol is checked in Table 15 on page 16. v --scp is included if the SCP protocol is checked in Table 15 on page 16. v --nfs [nfsoptions] is included if the NFS protocol is checked in Table 15 on page 16. nfsoptions must be specified or the export will not be accessible by clients. The nfsoptions must be provided by the customer's NFS administrator. For descriptions of the nfsoptions see Table 15 on page 16. clientip/subnetmask ro (enabled by default) or rw root_squash (enabled by default) or no_root_squash sync (enabled by default) or async. (Note that using the async flag enhances performance, but can result in undetectable data loss if the system crashes before all data has been written to disk.) Example: --nfs " /16(rw,no_root_squash,sync)" v <owner> is the owner of the shared disk space as specified in Table 15 on page 16. Note: If <owner> contains any spaces or special characters such as a backslash, the owner parameter should be enclosed in double quotes. Example: "domain1\admin1" Example: mkexport shared /ibm/gpfs0/shared --cifs browseable=yes --nfs " /16(rw,no_root_squash,sync)" --owner "domain1\admin1" 2. To verify that the export was successful, perform the following sub-steps: a. Type lsexport -v and press Enter. Name Path Protocol Active Timestamp Options shared /ibm/gpfs0/shared FTP true 1/22/10 1:00 PM shared /ibm/gpfs0/shared NFS true 1/22/10 1:00 PM *=(rw,sync,insecure,fsid= ) shared /ibm/gpfs0/shared CIFS true 1/22/10 1:00 PM browseable,comment=ibm SONAS b. Verify that the File Access Protocols and any associated parameters match what you specified with the mkexport command. 3. To verify that the owner was assigned correctly, perform the following sub-steps: a. Type ls -al /ibm/gpfs0 and press Enter. b. A screen will be displayed showing the contents of the shared file system. Here is a sample: Chapter 4. Software configuration procedures 59

86 ls -al /ibm/gpfs0 total 1716 drwxr-xr-x 9 root root Oct 6 10:01. drwxr-xr-x 3 root root 4096 Oct 5 15:50.. drwxr-xr-x 4 root root 8192 Oct 5 15:58.ctdb root root 640 Oct 8 07:18 fileset.quota root root 1664 Oct 8 07:18 group.quota drwxr-xr-x 2 DOMAIN1\admin1 root 8192 Jan 22 13:30 shared root root 1664 Oct 8 07:18 user.quota In the preceding sample, notice the "DOMAIN1\admin1" entry. The domain and user will be the values you specified with the --owner parameter to the mkexport command. Modify the Access Control List for the Shared folder Follow this procedure to modify the Access Control List (ACL) for a shared disk space. Access Control Lists (ACLs) are used to specify the authority a user or group has to access a file, directory, or file system. As an example, a user or group could be granted read-only access to files in directory abc, while given full (create/write/read/execute) access to files in directory xyz. Only a user who has been granted authorization in the ACLs will be able to access files on the IBM SONAS. To improve the manageability and to improve the interoperability with CIFS, IBM SONAS uses Access Control Administrative model that supports the following models for access control list (ACL) management: v ACL-only: IBM SONAS uses this model for UNIX clients that use NFSv4 ACLs for Windows clients. You can retrieve mode permission bits, but cannot change permissions using mode bits by using the --chmod option. v Mixed: IBM SONAS uses this model for an environment where both UNIX and Windows clients share data. Both mode bits and ACLs are effective. 1. If a CIFS export was created using the mkexport command, notify the customer storage administrator (owner) that they should use the Windows utilities (from a Windows workstation on their network) to modify the ACLs for CIFS shares to provide the appropriate authorization. The following sub-steps can be used as a guide: a. Access the shared folder using Windows Explorer. Note: This procedure must be used while logged into Windows as the owner. b. Right click on the folder, and select 'Sharing and Security...'. c. Use the functions on the Sharing tab and/or the Security tab to set the appropriate authorization. Note: a. The procedure for modifying ACLs using Windows utilities must not be attempted until after the rest of the Software Configuration process has been completed. b. Different versions of Windows may access the Sharing and Security settings differently, so the procedure may be slightly different from the preceding sub-steps. 60 IBM SONAS 1.5.2: Software Configuration Guide

87 c. For a more detailed procedure, refer to the IBM SONAS information center. See Access rights and ACL management of clients. 2. If an NFS export was created using the mkexport command, notify the customer storage administrator (owner) that they should use the NFS utilities (from a workstation on their network) to modify the ACLs for NFS shares to provide the appropriate authorization. Note: a. The procedure for modifying ACLs using NFS utilities must not be attempted until after the rest of the Software Configuration process has been completed. b. Different NFS applications may use different utilities to modify the ACLs. The customer storage administrator should refer to the documentation for their NFS application for instructions. 3. If it is not possible to use Windows or NFS utilities to modify the ACLs, use the following sub-steps to manually edit the ACLs: Note: This method requires manual editing of the ACL file using the VI editor, so it should only be used by those who are familiar with the VI editor. a. Type export EDITOR=/bin/vi and press Enter. This specifies that you want to use the VI editor to modify ACLs. Type mmeditacl /ibm/gpfs0/shared and press Enter. The following screen is displayed: #NFSv4 ACL #owner: domain1\administrator #group: domain1\domain users special:owner@:rwxc:allow (X)RbEAD/LIST (X)WRITE/CREATE (X)MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (-)READ_NAMED (-)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH (X)WRITE_ACL (X)WRITE_ATTR (-)WRITE_NAMED special:group@:rwx-:allow (X)READ/LIST (-)WRITE/CREATE (-)MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (-)READ_NAMED (-)DELETE (-)DELETE_CHILD (-)CHOWN (X)EXEC/SEARCH (-)WRITE_ACL (-)WRITE_ATTR (-)WRITE_NAMED special:everyone@:r-x-:allow (X)READ/LIST (-)WRITE/CREATE (-)MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (-)READ_NAMED (-)DELETE (-)DELETE_CHILD (-)CHOWN (X)EXEC/SEARCH (-)WRITE_ACL (-)WRITE_ATTR (-)WRITE_NAMED Change the ACLs by adding the text shown below in bold. #NFSv4 ACL #owner: domain1\administrator #group: domain1\domain users group:domain1\domain admins:rwxc:allow:fileinherit:dirinherit (X)READ/LIST (X)WRITE/CREATE (X)MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (X)READ_NAMED (X)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH (X)WRITE_ACL (X)WRITE_ATTR (X)WRITE_NAMED special:owner@:rwxc:allow:fileinherit:dirinherit (X)READ/LIST (X)WRITE/CREATE (X)MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (-)READ_NAMED (X)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH (X)WRITE_ACL (X)WRITE_ATTR (-)WRITE_NAMED special:group@:rwx-:allow:fileinherit:dirinherit (X)READ/LIST (X)WRITE/CREATE (X)MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (-)READ_NAMED (-)DELETE (-)DELETE_CHILD (-)CHOWN (X)EXEC/SEARCH (-)WRITE_ACL (-)WRITE_ATTR (-)WRITE_NAMED special:everyone@:r-x-:allow:fileinherit:dirinherit (X)READ/LIST (-)WRITE/CREATE (-)MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (-)READ_NAMED (-)DELETE (-)DELETE_CHILD (-)CHOWN (X)EXEC/SEARCH (-)WRITE_ACL (-)WRITE_ATTR (-)WRITE_NAMED Verify that you have made the following changes: v Added the new group (shown in the example as the first 5 bold lines). Important: the group owner shown in the first bold line as domain1\domain is a changeable parameter. It must be the same as the <owner> parameter used with the mkexport command. v Added :FileInherit:DirInherit to the existing 3 groups. v Changed the Delete for the special:owner. Chapter 4. Software configuration procedures 61

88 v Changed the Write/Create and MKDIR for the special:group. Press ESC to save the changes. When prompted if you want to apply the modified ACL, select Yes. Schedule a periodic backup of the TDB Follow this procedure to schedule a periodic backup of the Trivial DataBase (TDB). The Trivial DataBase (TDB) is used by the IBM SONAS Software to store various types of information used to manage the system. It is strongly recommended that you set up a periodic backup of the TDB so backups are available to support personnel in the event a TDB becomes lost or corrupted. 1. Type mktask BackupTDB --minute 0 --hour 2 --dayofweek "*". Note: a. This command will schedule a backup of the Trivial DataBase at 2:00am every day. b. If you want to schedule the backup at a different time, The number following the hour parameter (2 in the command as shown above) can range from 0 (midnight) to 23 (11pm). 2. Press Enter. IBM Tivoli Assist On-site (AOS) These topics provide information about enabling and setting up IBM Tivoli AOS. IBM Tivoli Assist On-site (AOS) is a lightweight remote support program intended primarily for help desks and support engineers to diagnose and fix problems without the need of any external dependencies. Assist On-site is based on the IBM Tivoli Remote Control technology. Assist On-site has been developed specifically to meet functionality, security, and privacy requirements of IBM and IBM customers. Support engineers and their customers can run it on various platforms. It currently has a native version for the 32 bit Windows environment and generic Linux compatible operating systems. Assist On-site uses IBM AES MARS encryption, NTLM authentication, and IBM intranet authentication for IBM support engineers. Assist On-site can also support lightweight Rational Host Access Transformation Services emulator sessions for computers running z/os and Power i. Assist On-site provides a launch-in-context feature such that support engineers can start Assist On-site from within the session of the third-party support tool. For restricted use only, Assist On-site supports IBM diagnostic tools to function over the Assist On-site connection for the purpose of debugging hardware devices and IBM software. For more information about AOS, access the IBM SONAS Information Center at: Enable IBM Tivoli Assist On-site (AOS) Follow this procedure to enable IBM Tivoli AOS. The AOS feature is disabled by default. If you wish to enable it, complete the following procedure 62 IBM SONAS 1.5.2: Software Configuration Guide

89 1. At the management node command line type cnrsmenu and the following menu will display: #=============================================================================# # SONAS RAS Menus passive@mgmt002st001 # #=============================================================================# # 1. Show System Information Menus... # # 2. System Checkout Menus... # # 3. Cluster Tools... # # 4. Common Node Menus... # # 5. Management Menus... # # 6. Interface Menus... # # 7. Storage Menus... # # 8. MES tasks... # # 9. Call Home/Remote Support Tools... # # 10. Data Collection and Offload Tools... # # # # E. Exit # #=============================================================================# Choice:9 2. Type 9 and push Enter. The Call Home/Remote Support Tools menu is displayed. #=============================================================================# # SONAS RAS Menus passive@mgmt002st001 # # ->Call Home/Remote Support Tools... # #=============================================================================# # 1. Display and Configure Call Home Settings # # 2. Perform Test Call Home # # 3. Test Full Call Home Path for All Machine Type/Models # # 4. View Call Home Log Events that Occurred After Service Login # # 5. View Call Home Log # # 6. Test ECC Connectivity # # 7. Refresh Machine Type/Models Database # # 8. Launch the AOS utility # # 9. AOS Configuration... # # # # B. Back # # E. Exit # #=============================================================================# Choice:9 3. Type 9 and push Enter. The AOS Configuration menu is displayed. #=============================================================================# # SONAS RAS Menus passive@mgmt002st001 # # ->Call Home/Remote Support Tools... # # --->AOS Configuration... # #=============================================================================# # 1. Check AOS status # # 2. Enable Lights Out # # 3. Enable Lights On # # 4. Start AOS Processes # # 5. End AOS Processes # # 6. Enable/Disable Proxy Server for AoS # # # # B. Back # # E. Exit # #=============================================================================# Choice:6 4. Type 6 and push Enter. The Enable/Disable Proxy Server for AoS menu is displayed. * * Enter the proxy server URL (or leave blank to disable): 5. Enter the proxy server information from Table 5 on page 6. Chapter 4. Software configuration procedures 63

90 Setting up AOS service You can use the command-line interface (CLI) or the graphical user interface (GUI) to start, end, configure, or query Assist on Site (AOS) service. If the service is running and lights-out mode is enabled, a remote user can log on without the presence of anyone on site to confirm the takeover. If the service is running and lights-out mode is disabled, confirmation is needed by an on-site individual. Any settings are saved and read on reboot of the management node. GUI navigation To work with this function in the management GUI, log on to the GUI and select Settings > Support > AOS. CLI usage Using the CLI, issue the cfgaos command. 64 IBM SONAS 1.5.2: Software Configuration Guide

91 Chapter 5. Test Procedures Test the IBM SONAS Follow this procedure to test and monitor components of the IBM SONAS system. 1. If you are not logged in already, log into the management node admin as user ID and password. If you encounter any problems, refer the service information in the IBM Scale Out Network Attached Storage Information Center. To view the infocenter, select Brower functions > Launch infocenter and select the Information Center from the left-hand menu. 2. At the management node, complete the following sub-steps to view the Health Center: a. Click Applications > SONAS > SONAS GUI. Note: If this system is a gateway to any Storwize V7000, SAN Volume Controller, IBM XIV Storage System, IBM DCS3700 or IBM SONAS Storage 2 the GUI will not accurately reflect the actual location of that storage. However, unless otherwise noted, the system is configured properly. b. If an 'Invalid security certificate' alert displays, click OK. c. If a 'Secure Connection Failed' message is displayed, click Add Exception, click Get Certificate, and click Confirm Security Exception. d. At the Scale Out File Services login screen, log in with User ID and password as admin. e. If you are asked if you want Firefox to remember this password, click Never for This Site. f. The first time you log into the GUI, you will be asked to accept the software license agreement. Follow the instructions on the screen to accept the software license agreement. g. Click Monitoring. h. Click Events then click on Actions, and then click on Clear Log. This will clear any errors that occurred during the installation and configuration process. Note: Errors typically occur during installation and configuration. These errors should have already been corrected, but they have not yet been cleared from the Events Log. Any errors that have not yet been corrected will be logged again when you refresh Monitoring. i. Click Monitoring > System Details. A list of system components is displayed in the left navigation panel. j. Review Status for each component. Resolve all issues by right clicking the item and selecting Mark Event as Resolved. k. Click Monitoring > Events, and then Refresh. Note: Ignore the informational entries (entries with an info severity) that might display in the log following the installation. l. If any problems are logged, click on the Event ID for more information. The SONAS Information Center will be displayed with information about the Event ID. Copyright IBM Corp. 2009,

92 m. If a 'Firefox prevented this site from opening a pop-up window.' message is displayed, click Preferences, and click on Allow pop-ups for localhost. n. If you cannot resolve a problem, contact the next level of support. o. Clear the Events Log by clicking Monitoring > Events and then click Clear Log. p. Click Logout when you finish using the IBM SONAS GUI. The Scale Out File Services login screen is displayed. q. Close the browser by clicking X. The Linux desktop is displayed. r. Log out by selecting System > Log Out root. 66 IBM SONAS 1.5.2: Software Configuration Guide

93 Chapter 6. Connect the customer Ethernet network cables to the 2851-SIx interface nodes Follow this procedure to connect the TCP/IP data network Ethernet cables to the 2851-SIx interface nodes. 1. During hardware installation, the customer must connect the TCP/IP data network Ethernet cables to the 2851-SIx interface nodes. Complete the following steps if the cables were not available and not installed during hardware installation. 2. Start installing with the lowest numbered rack to be installed (typically this will be rack 1). Record the number of the rack for use in the rest of this section. Refer to Table 3 on page Locate the rack you selected in the previous step. 4. Locate a not-yet-connected 2851-SIx interface nodes in the rack. Start with the interface node closest to the bottom of the rack. Note: To determine if an interface node is connected, look at the back of the server. It there are Ethernet cables connected to any of the ports listed in Table 24, the server is connected. 5. Locate the customer Ethernet cables to be used for this interface node. Note: Ensure that the cables are labeled according to the Labeling kit provided with this document. This will simplify service actions in the future. Table SIx interface node Ethernet cable connections U Ethernet cable connection 2851-SIx interface nodes port location 1 Gb Ethernet cable 1 (if applicable System Board port 3 1 Gb Ethernet cable 2 (if applicable System Board port 4 1 Gb Ethernet cable 3 (if applicable) PCIe Card slot 2 port 1 1 Gb Ethernet cable 4 (if applicable) PCIe Card slot 2 port 2 1 Gb Ethernet cable 5 (if applicable) PCIe Card slot 2 port 3 1 Gb Ethernet cable 6 (if applicable) PCIe Card slot 2 port 4 10 Gb Ethernet cable 1 (if applicable) PCIe Card slot 4 port 1 10 Gb Ethernet cable 2 (if applicable) PCIe Card slot 4 port 2 Copyright IBM Corp. 2009,

94 Ethernet 3 Ethernet 4 optional Power supply 1 Power supply 2 Systems-management (Ethernet) Ethernet 1 Ethernet 2 Video Serial USB 3 USB 4 Power cord connectors bb1gs006 Figure 1. Customer Ethernet connections to the 2851-SIx interface nodes 6. Connect each cable to an available Ethernet port on the interface node. 7. If the rack contains another interface node, repeat the steps in this section until all interface nodes in the rack have been cabled. 8. If you are installing more than one rack, repeat the steps in this section until all interface nodes in all of the racks you are installing have been cabled. 68 IBM SONAS 1.5.2: Software Configuration Guide

95 Chapter 7. Completing installation and configuration You can use this procedure to complete the IBM SONAS installation. 1. Change the password of the admin user at this time using the chuser command, or the Access > Users panel in the IBM SONAS GUI, to ensure that the system remains secure. 2. Use the chpasswordpolicy command to implement password policies that are required to ensure that the password is changed on a regular basis. 3. If you have not already done so, log out of the management node. a. If you logged in at the KVM, click System, and then click Log Out root. b. If you logged in from a network-attached workstation, type exit and press Enter. The IBM SONAS system is now ready for use. Copyright IBM Corp. 2009,

96 70 IBM SONAS 1.5.2: Software Configuration Guide

97 Appendix A. Time zone list This topic provides a worldwide list of time zones. 0 Etc/UTC 1 Africa/Abidjan 2 Africa/Accra 3 Africa/Addis_Ababa 4 Africa/Algiers 5 Africa/Asmara 6 Africa/Bamako 7 Africa/Bangui 8 Africa/Banjul 9 Africa/Bissau 10 Africa/Blantyre 11 Africa/Brazzaville 12 Africa/Bujumbura 13 Africa/Cairo 14 Africa/Casablanca 15 Africa/Ceuta 16 Africa/Conakry 17 Africa/Dakar 18 Africa/Dar_es_Salaam 19 Africa/Djibouti 20 Africa/Douala 21 Africa/El_Aaiun 22 Africa/Freetown 23 Africa/Gaborone 24 Africa/Harare 25 Africa/Johannesburg 26 Africa/Juba 27 Africa/Kampala 28 Africa/Khartoum 29 Africa/Kigali 30 Africa/Kinshasa 31 Africa/Lagos 32 Africa/Libreville 33 Africa/Lome 34 Africa/Luanda 35 Africa/Lubumbashi 36 Africa/Lusaka 37 Africa/Malabo 38 Africa/Maputo 39 Africa/Maseru 40 Africa/Mbabane 41 Africa/Mogadishu 42 Africa/Monrovia 43 Africa/Nairobi 44 Africa/Ndjamena 45 Africa/Niamey 46 Africa/Nouakchott 47 Africa/Ouagadougou 48 Africa/Porto-Novo 49 Africa/Sao_Tome 50 Africa/Tripoli Copyright IBM Corp. 2009,

98 51 Africa/Tunis 52 Africa/Windhoek 53 America/Adak 54 America/Anchorage 55 America/Anguilla 56 America/Antigua 57 America/Araguaina 58 America/Argentina/Buenos_Aires 59 America/Argentina/Catamarca 60 America/Argentina/Cordoba 61 America/Argentina/Jujuy 62 America/Argentina/La_Rioja 63 America/Argentina/Mendoza 64 America/Argentina/Rio_Gallegos 65 America/Argentina/Salta 66 America/Argentina/San_Juan 67 America/Argentina/San_Luis 68 America/Argentina/Tucuman 69 America/Argentina/Ushuaia 70 America/Aruba 71 America/Asuncion 72 America/Atikokan 73 America/Bahia 74 America/Bahia_Banderas 75 America/Barbados 76 America/Belem 77 America/Belize 78 America/Blanc-Sablon 79 America/Boa_Vista 80 America/Bogota 81 America/Boise 82 America/Cambridge_Bay 83 America/Campo_Grande 84 America/Cancun 85 America/Caracas 86 America/Cayenne 87 America/Cayman 88 America/Chicago 89 America/Chihuahua 90 America/Costa_Rica 91 America/Creston 92 America/Cuiaba 93 America/Curacao 94 America/Danmarkshavn 95 America/Dawson 96 America/Dawson_Creek 97 America/Denver 98 America/Detroit 99 America/Dominica 100 America/Edmonton 72 IBM SONAS 1.5.2: Software Configuration Guide

99 101 America/Eirunepe 102 America/El_Salvador 103 America/Fortaleza 104 America/Glace_Bay 105 America/Godthab 106 America/Goose_Bay 107 America/Grand_Turk 108 America/Grenada 109 America/Guadeloupe 110 America/Guatemala 111 America/Guayaquil 112 America/Guyana 113 America/Halifax 114 America/Havana 115 America/Hermosillo 116 America/Indiana/Indianapolis 117 America/Indiana/Knox 118 America/Indiana/Marengo 119 America/Indiana/Petersburg 120 America/Indiana/Tell_City 121 America/Indiana/Vevay 122 America/Indiana/Vincennes 123 America/Indiana/Winamac 124 America/Inuvik 125 America/Iqaluit 126 America/Jamaica 127 America/Juneau 128 America/Kentucky/Louisville 129 America/Kentucky/Monticello 130 America/Kralendijk 131 America/La_Paz 132 America/Lima 133 America/Los_Angeles 134 America/Lower_Princes 135 America/Maceio 136 America/Managua 137 America/Manaus 138 America/Marigot 139 America/Martinique 140 America/Matamoros 141 America/Mazatlan 142 America/Menominee 143 America/Merida 144 America/Metlakatla 145 America/Mexico_City 146 America/Miquelon 147 America/Moncton 148 America/Monterrey 149 America/Montevideo 150 America/Montreal Appendix A. Time zone list 73

100 151 America/Montserrat 152 America/Nassau 153 America/New_York 154 America/Nipigon 155 America/Nome 156 America/Noronha 157 America/North_Dakota/Beulah 158 America/North_Dakota/Center 159 America/North_Dakota/New_Salem 160 America/Ojinaga 161 America/Panama 162 America/Pangnirtung 163 America/Paramaribo 164 America/Phoenix 165 America/Port-au-Prince 166 America/Port_of_Spain 167 America/Porto_Velho 168 America/Puerto_Rico 169 America/Rainy_River 170 America/Rankin_Inlet 171 America/Recife 172 America/Regina 173 America/Resolute 174 America/Rio_Branco 175 America/Santa_Isabel 176 America/Santarem 177 America/Santiago 178 America/Santo_Domingo 179 America/Sao_Paulo 180 America/Scoresbysund 181 America/Shiprock 182 America/Sitka 183 America/St_Barthelemy 184 America/St_Johns 185 America/St_Kitts 186 America/St_Lucia 187 America/St_Thomas 188 America/St_Vincent 189 America/Swift_Current 190 America/Tegucigalpa 191 America/Thule 192 America/Thunder_Bay 193 America/Tijuana 194 America/Toronto 195 America/Tortola 196 America/Vancouver 197 America/Whitehorse 198 America/Winnipeg 199 America/Yakutat 200 America/Yellowknife 74 IBM SONAS 1.5.2: Software Configuration Guide

101 201 Antarctica/Casey 202 Antarctica/Davis 203 Antarctica/DumontDUrville 204 Antarctica/Macquarie 205 Antarctica/Mawson 206 Antarctica/McMurdo 207 Antarctica/Palmer 208 Antarctica/Rothera 209 Antarctica/South_Pole 210 Antarctica/Syowa 211 Antarctica/Vostok 212 Arctic/Longyearbyen 213 Asia/Aden 214 Asia/Almaty 215 Asia/Amman 216 Asia/Anadyr 217 Asia/Aqtau 218 Asia/Aqtobe 219 Asia/Ashgabat 220 Asia/Baghdad 221 Asia/Bahrain 222 Asia/Baku 223 Asia/Bangkok 224 Asia/Beirut 225 Asia/Bishkek 226 Asia/Brunei 227 Asia/Choibalsan 228 Asia/Chongqing 229 Asia/Colombo 230 Asia/Damascus 231 Asia/Dhaka 232 Asia/Dili 233 Asia/Dubai 234 Asia/Dushanbe 235 Asia/Gaza 236 Asia/Harbin 237 Asia/Hebron 238 Asia/Ho_Chi_Minh 239 Asia/Hong_Kong 240 Asia/Hovd 241 Asia/Irkutsk 242 Asia/Jakarta 243 Asia/Jayapura 244 Asia/Jerusalem 245 Asia/Kabul 246 Asia/Kamchatka 247 Asia/Karachi 248 Asia/Kashgar 249 Asia/Kathmandu 250 Asia/Kolkata Appendix A. Time zone list 75

102 251 Asia/Krasnoyarsk 252 Asia/Kuala_Lumpur 253 Asia/Kuching 254 Asia/Kuwait 255 Asia/Macau 256 Asia/Magadan 257 Asia/Makassar 258 Asia/Manila 259 Asia/Muscat 260 Asia/Nicosia 261 Asia/Novokuznetsk 262 Asia/Novosibirsk 263 Asia/Omsk 264 Asia/Oral 265 Asia/Phnom_Penh 266 Asia/Pontianak 267 Asia/Pyongyang 268 Asia/Qatar 269 Asia/Qyzylorda 270 Asia/Rangoon 271 Asia/Riyadh 272 Asia/Sakhalin 273 Asia/Samarkand 274 Asia/Seoul 275 Asia/Shanghai 276 Asia/Singapore 277 Asia/Taipei 278 Asia/Tashkent 279 Asia/Tbilisi 280 Asia/Tehran 281 Asia/Thimphu 282 Asia/Tokyo 283 Asia/Ulaanbaatar 284 Asia/Urumqi 285 Asia/Vientiane 286 Asia/Vladivostok 287 Asia/Yakutsk 288 Asia/Yekaterinburg 289 Asia/Yerevan 290 Atlantic/Azores 291 Atlantic/Bermuda 292 Atlantic/Canary 293 Atlantic/Cape_Verde 294 Atlantic/Faroe 295 Atlantic/Madeira 296 Atlantic/Reykjavik 297 Atlantic/South_Georgia 298 Atlantic/Stanley 299 Atlantic/St_Helena 300 Australia/Adelaide 76 IBM SONAS 1.5.2: Software Configuration Guide

103 301 Australia/Brisbane 302 Australia/Broken_Hill 303 Australia/Currie 304 Australia/Darwin 305 Australia/Eucla 306 Australia/Hobart 307 Australia/Lindeman 308 Australia/Lord_Howe 309 Australia/Melbourne 310 Australia/Perth 311 Australia/Sydney 312 Europe/Amsterdam 313 Europe/Andorra 314 Europe/Athens 315 Europe/Belgrade 316 Europe/Berlin 317 Europe/Bratislava 318 Europe/Brussels 319 Europe/Bucharest 320 Europe/Budapest 321 Europe/Chisinau 322 Europe/Copenhagen 323 Europe/Dublin 324 Europe/Gibraltar 325 Europe/Guernsey 326 Europe/Helsinki 327 Europe/Isle_of_Man 328 Europe/Istanbul 329 Europe/Jersey 330 Europe/Kaliningrad 331 Europe/Kiev 332 Europe/Lisbon 333 Europe/Ljubljana 334 Europe/London 335 Europe/Luxembourg 336 Europe/Madrid 337 Europe/Malta 338 Europe/Mariehamn 339 Europe/Minsk 340 Europe/Monaco 341 Europe/Moscow 342 Europe/Oslo 343 Europe/Paris 344 Europe/Podgorica 345 Europe/Prague 346 Europe/Riga 347 Europe/Rome 348 Europe/Samara 349 Europe/San_Marino 350 Europe/Sarajevo Appendix A. Time zone list 77

104 351 Europe/Simferopol 352 Europe/Skopje 353 Europe/Sofia 354 Europe/Stockholm 355 Europe/Tallinn 356 Europe/Tirane 357 Europe/Uzhgorod 358 Europe/Vaduz 359 Europe/Vatican 360 Europe/Vienna 361 Europe/Vilnius 362 Europe/Volgograd 363 Europe/Warsaw 364 Europe/Zagreb 365 Europe/Zaporozhye 366 Europe/Zurich 367 Indian/Antananarivo 368 Indian/Chagos 369 Indian/Christmas 370 Indian/Cocos 371 Indian/Comoro 372 Indian/Kerguelen 373 Indian/Mahe 374 Indian/Maldives 375 Indian/Mauritius 376 Indian/Mayotte 377 Indian/Reunion 378 Pacific/Apia 379 Pacific/Auckland 380 Pacific/Chatham 381 Pacific/Chuuk 382 Pacific/Easter 383 Pacific/Efate 384 Pacific/Enderbury 385 Pacific/Fakaofo 386 Pacific/Fiji 387 Pacific/Funafuti 388 Pacific/Galapagos 389 Pacific/Gambier 390 Pacific/Guadalcanal 391 Pacific/Guam 392 Pacific/Honolulu 393 Pacific/Johnston 394 Pacific/Kiritimati 395 Pacific/Kosrae 396 Pacific/Kwajalein 397 Pacific/Majuro 398 Pacific/Marquesas 399 Pacific/Midway 400 Pacific/Nauru 401 Pacific/Niue 402 Pacific/Norfolk 403 Pacific/Noumea 404 Pacific/Pago_Pago 405 Pacific/Palau 406 Pacific/Pitcairn 407 Pacific/Pohnpei 408 Pacific/Port_Moresby 409 Pacific/Rarotonga 410 Pacific/Saipan 411 Pacific/Tahiti 412 Pacific/Tarawa 413 Pacific/Tongatapu 414 Pacific/Wake 415 Pacific/Wallis 78 IBM SONAS 1.5.2: Software Configuration Guide

105 Appendix B. Remote Connection to the Active management node Do not use this procedure until the IBM SSR completes hardware installation and the management node is connected to the customer network. The following procedures assumes that you are using Windows XP Workstation. 1. Do not use the following procedure if you want to log into the management node using the Display Module (KVM) on the front of the base rack. Go to section Logging on to the management node on page Use the following procedure if you want to log in to the management node from a workstation on the customer's network. Note: If you are logged in remotely, you should have an SSH client program installed on your workstation. A Linux or Unix (including AIX ) workstation will typically have an SSH client preloaded, but a Windows workstation will not have a client preloaded. A freeware Windows-compatible SSH client called PuTTY is available at The following steps must be completed if you have an SSH client program installed on your workstation. 3. Locate the active management node cluster name and domain name. They are specified in Table 4 on page 4. Example: cluster1.company.com Also locate the CLI user ID and password. They are specified in Table 6 on page 7. You will need them later in this procedure. 4. Use the PING command to ensure that you have a working network connection to the management node. Complete the following substeps to use the PING command on your Windows XP workstation. a. Start a Command Prompt session by clicking Start > All Programs > Accessories > Command Prompt. b. Type ping <cluster name>.<domain name> Example: ping cluster1.company.com c. If an error displays or if there is a problem with the connection, correct the problem before you continue. 5. If you are using PuTTY, complete the following sub-steps: a. Start the PuTTY program. b. Set the Connection type to SSH. c. In the Host Name (or IP address) field, type myuserid@clustername.domainname where myuserid is the CLI User ID specified in Table 6 on page 7. Example: admin@cluster1.company.com d. In the Port field, type 1602 e. Click Open. f. If a software firewall is installed on the workstation, a warning might display on the screen. Accept the connection to continue. If this is the first time you are connecting to this cluster, you might see a security alert as shown in the example below. If you see this warning, click Yes to create a certificate. Copyright IBM Corp. 2009,

106 Figure 2. PuTTY Security Alert The following screen should be displayed: Using username "admin". s password: g. Type the CLI password listed in Table 6 on page 7. Note: The password will not be displayed for security reasons. If the password is correct, the following screen is displayed, indicating that you have successfully logged in: Using username "admin". admin@cluster1.company.com s password: Last login: Thu Nov 12 23:01: from admin.company.com [admin@ovalsquid.storage.tucson.ibm.com.mgmt001st001 /]# 6. If you are using a Linux or Unix (including AIX) SSH client, follow the same process but in a command prompt session. Complete the following sub-steps: a. Start a Command Prompt session. b. Type ssh myuserid@clustername.domainname where myuserid is the CLI User ID specified in Table 6 on page 7. Example: ssh admin@cluster1.company.com c. The following screen should be displayed: Using username "admin". admin@cluster1.company.com s password: d. Type the CLI password listed in Table 6 on page 7. Note: The password will not be displayed for security reasons. If the password is correct, the following screen is be displayed, indicating that you have successfully logged in: 80 IBM SONAS 1.5.2: Software Configuration Guide

107 Using username "admin". s password: Last login: Thu Nov 12 23:01: from admin.company.com /]# 7. Type help and press Enter to display a list of commonly used commands. 8. Type exit and press Enter to close the connection. Appendix B. Remote Connection to the Active management node 81

108 82 IBM SONAS 1.5.2: Software Configuration Guide

109 Appendix C. Remote Access to the InfoCenter Do not use this procedure until the IBM SSR has completed the hardware installation and the management node is connected to the customer network. The following procedure assumes you are using Windows XP workstation. 1. Do not use this procedure if you want to access the Information Center using the Display Module (KVM) on the front of the base rack. Go to the section Appendix D, Local Access to the Information Center, on page Use the following procedure if you want to access the Information Center from a workstation on the customer's network. 3. Locate the Active management node cluster name (the one specified during the first time installation) and domain name. They are specified in Table 4 on page 4. Example: cluster1.company.com 4. Ensure that you have a working network connection from your workstation to the Active management node. The following sub-steps guide you through using the PING command to ensure you have a working network connection. Note: This procedure assumes you are using a Windows XP workstation. The procedure on other types of workstation is similar. a. Start a Command Prompt session by clicking Start > All Programs > Accessories > Command Prompt. b. Type ping <cluster name>.<domain name> Example: ping cluster1.company.com c. If an error displays or if there is a problem with the connection, correct the problem before you continue. 5. Open a web browser. Note: If you are using Microsoft Windows, click on the Internet Explorer icon. 6. In the Web Browser's Address field, type <clustername>.<domainname>/help/index.jsp where <clustername> is the Cluster Name and <domainname> is the Domain Name as specified in Table 4 on page 4. Example: 7. You may see a Security Alert message similar to the example below. If you see this alert, click on Yes to continue. Copyright IBM Corp. 2009,

110 Figure 3. InfoCenter Security Alert The Information Center is displayed. 8. Click IBM Scale Out Network Attached Storage in the left panel of the screen. 9. Close the web browser after you finish using the Information Center. 84 IBM SONAS 1.5.2: Software Configuration Guide

111 Appendix D. Local Access to the Information Center This procedure must not be used until after the IBM SSR has completed the hardware installation. 1. If you want to access the Information Center from a workstation on the customer's network, do not use the following procedure. Go to section Appendix C, Remote Access to the InfoCenter, on page If you want to access the Information Center using the Display Module on the front of the base rack, continue with the following steps. 3. Locate the management node cluster name and domain name. They are specified in Table 4 on page 4. Example: cluster1.company.com 4. If you are not yet logged into the Active management node, go to section Logging on to the management node on page 33 and log in. When you have logged in and the Linux desktop is displayed, return to this procedure. 5. Click on Applications on the Linux desktop, then select Internet > Firefox Web Browser. The Web Browser program will start. 6. In the Web Browser's URL field, type help/index.jsp where <clustername> is the Cluster Name and <domainname> is the Domain Name as specified in Table 4 on page 4. Example: 7. The first time you access the Information Center locally, you may see security alerts. If you see security alerts, perform the following sub-steps to process these alerts: a. You may see a Security Alert message similar to the following example. If you see this alert, click on OK to continue. Alert! cluster1.company.com uses an invalid security certificate The certificate is not trusted because it is self signed. The certificate is only valid for (Error code: sec_error_ca_cert_invalid) [OK] b. You may see another Security Alert message similar to the following example. If you see this alert, click on Add Exception to continue. Secure Connection Failed! localhost uses an invalid security certificate The certificate is not trusted because it is self signed. The certificate is only valid for (Error code: sec_error_ca_cert_invalid) [ Get me out of here! ] [ Add Exception... ] c. You may see an Add Security Exception message similar to the following example. If you see this alert, click on Get Certificate to continue, then click on Confirm Security Exception. Copyright IBM Corp. 2009,

112 Add Security Exception You are about to override how Firefox identifies this site. Server Locaton: [ Get Certificate ] Certificate Status [ Cancel ] 8. The Information Center will be displayed. In the table of contents, select IBM Scale Out Network Attached Storage information. 9. When you have finished using the Information Center, just close the web browser. 86 IBM SONAS 1.5.2: Software Configuration Guide

113 Appendix E. Glossary This glossary includes terms for the IBM Scale Out Network Attached Storage (IBM SONAS). A B C D E F G H I J K L M N O P Q R S T U V W X Z This glossary includes selected terms and definitions from the IBM Terminology Web site. This glossary uses the following cross-reference forms: See Refers the reader to one of two kinds of related information: v A term that is the expanded form of an abbreviation or acronym. This expanded form of the term contains the full definition. v A synonym or more preferred term See also Refers the reader to one or more related terms. Contrast with Refers the reader to a term that has an opposite or substantively different meaning. A absolute path The full path name of an object. Absolute path names begin at the highest level or root directory (which is identified by the forward slash (/) or backward slash (\) character). access The ability to read, update, or otherwise use a resource. Access to protected resources is usually controlled by system software. access control entry (ACE) An entry in an access control list (ACL) that contains a set of access rights, for a particular grantee, such as a machine, user, or group, and whether the right is allowed or denied. An ACE can also contain information about the source, whether directly applied, inherited, or from a security template. access control list (ACL) In computer security, a list associated with an object that identifies all the subjects that can access the object and their access rights access permission A group of designations that determine the users who can access a particular file and how the users can access the file. The access permissions are read, write, and run (execute). access right A security setting that controls access to the objects in an object store or workflow. Copyright IBM Corp. 2009,

114 account An entity that contains a set of parameters that define the application-specific attributes of a user, which include the identity, user profile, and credentials. ACE See access control entry. ACL See access control list. Active Directory A hierarchical directory service that enables centralized, secure management of an entire network which is a central component of the Microsoft Windows platform. address A unique code or identifier for a register, device, workstation, system, or storage location. advisory lock A type of lock that a process holds on a region of a file that signals any other process to not use or lock the region or an overlapping region. Other processes are not forced to comply. agent A process that performs an action on behalf of a user or other program without user intervention or on a regular schedule, and reports the results back to the user or program. alert A message or other indication that signals an event or an impending event. alias An alternative name used instead of a primary name. API See application programming interface. application programming interface (API) An interface that allows an application program that is written in a high-level language to use specific data or functions of the operating system or another program. application server A server program in a distributed network that provides the execution environment for an application program. architectural limit An inherent limit within a system due to its design or implementation that imposes some restriction on one or more characteristics of the system. architecture The fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution. archive A service that copies inactive files from disk to removable media for longer term storage and removes the files from disk to free disk storage space. The user can select specific objects or groups of objects to include or exclude from the archive process. argument A value passed to or returned from a function or procedure at run time. argument string An ordered list of parameters passed between programs or routines. 88 IBM SONAS 1.5.2: Software Configuration Guide

115 array A structure that contains an ordered collection of elements of the same data type in which each element can be referenced by its index value or ordinal position in the collection. asynchronous replication In replication, the process of copying data from a source table to a target table outside the scope of the original transaction that updated the source table. Related term synchronous replication. atime In UNIX and Linux, the time when the file was last accessed. audit log An unalterable log file that records all successful configuration commands and the identity of who issued them. authenticated user A user who has logged in to the system with a valid account (user ID and password). authentication In computer security, a process that ensures that the identities of both the sender and the receiver of a network transaction are true. automated task A task in a task library that is automatically run when specific criteria are met, such as when a specific alarm level is triggered. automatic migration The process that is used to automatically move files from a local file system to storage, based on options and settings that are chosen by a root user on a workstation. availability The condition allowing users to access and use their applications and data. Back to top B background The conditions under which low-priority, noninteractive programs are run. background process A process that does not require operator intervention but can be run by the computer while the workstation is used to do other work. background task A task that is running even though the user is not currently interacting with it. backplane A hardware part that has (in one or more planes) logic paths, low-voltage distribution paths, and grounding paths of a section of a machine. backslash The character \. The backslash enables a user to escape the special meaning of a character. That is, typing a backslash before a character tells the system to ignore any special meaning the character might have. backup A copy of a data set or object to be used in case of accidental loss. Appendix E. Glossary 89

116 backup-archive client A program that runs on a workstation or file server and provides a means for users to back up, archive, restore, and retrieve files. base The core product, upon which features can be separately ordered and installed. baseboard management controller (BMC) A controller that monitors system platform management events such as fan failure and temperature or voltage increases, and logs their occurrence. The BMC is also used for hardware control, such as powering the node on and off. base package The name and version of a software package that is installed on a system. bash shell An sh-compatible shell that incorporates the positive aspects of Korn shell and C shell. It serves as the GNU operating system's command language interpreter. Basic Input/Output System (BIOS) The code that controls basic hardware operations, such as interactions with diskette drives, hard disk drives, and the keyboard. bay A physical space into which a device can be physically mounted and connected to power and data. For example, a power supply or a disk drive might be inserted into a bay. binary Property of a selection, choice, or condition that has two possible values. BIOS See Basic Input/Output System. bit The smallest unit of computer information, which has two possible states that are represented by the binary digits 0 or 1. black box An abstraction of a device or system in which only its externally visible behavior is considered and not its implementation or inner workings. block A unit of data storage on a device. block size A measure of the size of a block, usually specified in units such as records, words, computer words, or characters. Block size is sometimes referred to as block length and physical record size. BMC See baseboard management controller. bond To aggregate multiple network interfaces into a single, logical interface. bottleneck A place in the system where contention for a resource is affecting performance. buffer An area of storage that compensates for the different speeds of data flow or timings of events by temporarily holding a block of data to be processed or written to an I/O device. byte Back to top A string that represents a character and usually consists of eight binary digits that are treated as a unit. A byte is the smallest unit of storage that can be addressed directly. 90 IBM SONAS 1.5.2: Software Configuration Guide

117 C cache Storage used to improve access times to instructions, data, or both. For example, data that resides in cache memory is normally a copy of data that resides elsewhere in slower, less expensive storage, such as on a disk or on another network node. certificate In computer security, a digital document that binds a public key to the identity of the certificate owner, thereby enabling the certificate owner to be authenticated. A certificate is issued by a certificate authority and is digitally signed by that authority. character Any symbol that can be entered on a keyboard, printed, or displayed. For example, letters, numbers, and punctuation marks are all characters. chassis The metal frame in which various electronic components are mounted. check box A square box with associated text that represents a choice. When a user selects the choice, the check box is filled to indicate that the choice is selected. The user can clear the check box by selecting the choice again, thereby deselecting the choice. CIDR See Classless Inter-Domain Routing. CIFS See Common Internet File System. cipher A cryptographic algorithm used to encrypt data that is unreadable until converted into plain data with a predefined key. Classless Inter-Domain Routing (CIDR) A method for adding class C Internet Protocol (IP) addresses. The addresses are given to Internet Service Providers (ISPs) for use by their customers. CIDR addresses reduce the size of routing tables and make more IP addresses available within organizations. CLI See command-line interface. client A software program or computer that requests services from a server. See also server, host. client-side node See interface node. cloud computing A computing platform where users can have access to applications or compute resources, as services, from anywhere through their connected devices. A simplified user interface and application programming interface (API) makes the infrastructure supporting such services transparent to users. cloud storage A network of virtual servers that store data, usually hosted by third parties. cluster A loosely coupled collection of independent systems (or nodes) organized into a network for the purpose of sharing resources and communicating with each other. See also GPFS cluster. Appendix E. Glossary 91

118 cluster configuration A user definition of all cluster components. Component information is stored in the ODM. Components include cluster name and ID, and information about member nodes, network interface, and network modules. cluster configuration data The configuration data that is stored on the cluster configuration servers. clustered system (or system) A collection of nodes that are placed in pairs (I/O groups) for redundancy, which provide a single management interface. See also: system. clustered trivial database (CTDB) A cluster implementation of the trivial database (TDB) used by Samba and other projects to store temporary data. clustering The ability to group independent systems to work together as a single system. cluster manager The node that monitors node status using disk leases, detects failures, drives recovery, and selects file system managers. The cluster manager is the node with the lowest node number among the quorum nodes that are operating at a particular time. cluster node A system that is a member of a cluster. See also system. coherent Pertaining to an object in which all data values satisfy the invariant properties. If any invariant property is not satisfied, the object is not coherent. collection Data obtained by a collector that represents the system status at a given point in time. Collections are timestamped and stored in a management collection object. command A statement used to initiate an action or start a service. A command consists of the command name abbreviation, and its parameters and flags if applicable. command line The blank line on a display where commands, option numbers, or selections can be entered. command-line interface (CLI) A type of computer interface in which the input command is a string of text characters. command prompt A displayed character (or string of characters) that indicates that a user may enter a command to be processed. Common Internet File System (CIFS) A protocol that manages shared, remote file access for applications to files, printers, serial ports, and so on over a TCP/IP network. common service A function available to applications on a variety of operating system 92 IBM SONAS 1.5.2: Software Configuration Guide

119 platforms, accessible through any supported programming language. A common service can include support for character classification, collation, case conversion, data formatting, and so on. compression A function that removes repetitive characters, spaces, or strings of characters from the data being processed and replaces the repetitive characters with control characters. Compression reduces the amount of storage space that is required for the data. concurrent Pertaining to the occurrence of two or more activities within a given interval of time. Concurrent processes can alternately use shared common resources. configuration The manner in which the hardware and software of a system, subsystem, or network are organized and interconnected. configuration file A file that specifies the characteristics of a program, system device, system, or network. configuration parameter A parameter whose value limits or defines the resources that can be used by the database manager or a database. Some configuration parameters are informational and define characteristics about the environment that cannot be changed. confirmation A transmission by a receiver that permits a sender to continue. controller A device that coordinates and controls the operation of one or more input/output devices (such as workstations) and synchronizes the operation of such devices with the operation of the system as a whole. cookie Information that a server stores on a client machine and accesses during subsequent sessions. Cookies allow servers to retrieve specific information about clients. credential Information acquired during authentication that describes a user, group associations, or other security-related identity attributes, and that is used to perform services such as authorization, auditing, or delegation. For example, a user ID and password are credentials that allow access to network and system resources. cron A command that is used to schedule a job or process. cron table A table that is used to schedule application programs and processes. CSV file A text file that contains comma-separated values. A CSV file is commonly used to exchange files between database systems and applications that use different formats. CTDB See clustered trivial database. Back to top Appendix E. Glossary 93

120 D daemon A program that runs unattended to perform continuous or periodic functions, such as network control. dark fiber In fiber-optic communications, the fiber infrastructure that is in place but not being used. database A collection of interrelated or independent data items that are stored together to serve one or more applications. database file One of several types of the system object type *FILE kept in the system that contains descriptions of how input data is to be presented to a program from internal storage and how output data is to be presented to internal storage from a program. database recovery The process of restoring data by merging the backup copy with changes accumulated since the backup was made. data management The task of systematically identifying, organizing, storing, and cataloging data in an operating system. data management application program interface (DMAPI) The interfaces defined by the Open Group's Data Storage management (XDSM) specification. These interfaces support the monitoring of events on files and the management and maintenance of the data in a file. data migration The movement of data from one physical location to another without disruption of application I/O operations. The movement of data when the software is upgraded or the data is transferred to a different hardware server or model. data mover A device that moves data on behalf of the server. A network-attached storage (NAS) file server is a data mover. debug To detect, diagnose, and eliminate errors in programs. definition A declaration that reserves storage and can provide an initial value for a data object or define a function. definition file Defines the content that is displayed within the navigation and workarea frames. delegation The act of giving other users or groups the authority to perform operations. dense wavelength division multiplexing (DWDM) A technology that places many optical signals onto one single-mode fiber using slightly different optical frequencies. DWDM enables many data streams to be transferred in parallel. 94 IBM SONAS 1.5.2: Software Configuration Guide

121 dependency A requirement that one managed resource has on another managed resource in order to operate correctly. device A piece of equipment such as a workstation, printer, disk drive, tape unit, or remote system. Device-Mapper Multipathing (DM-Multipath) A method used to configure multiple I/O paths among nodes and storage arrays into a single device. DIMM See dual inline memory module. direct access A file access method allowing reading and writing of records in an arbitrary order. direct memory access (DMA) The transfer of data between memory and an input/output device without processor intervention. directory service A facility such as Lightweight Directory Access Protocol (LDAP) or Microsoft Active Directory that provides information about users and groups in an organization. disk A storage device that includes one or more flat, circular plates with magnetic or optical surfaces on which information is stored. disk drive module A field-replaceable unit (FRU) that consists of a single disk drive and its associated packaging. disk storage pool A collection of disks or RAID arrays used to create tiers of storage by grouping storage-based devices based on performance, locality, or reliability characteristics. distinguished name The name that uniquely identifies an entry in a directory. A distinguished name is made up of attribute:value pairs, separated by commas. distribution A software package that is ready to install. A distribution often refers to a Linux package that contains the Linux operating system, an installation program, utilities, and documentation. DMA See direct memory access. DMAPI See data management application program interface. DM-Multipath See Device-Mapper Multipathing. DNS See Domain Name System. DNS server A computer or server that matches an IP address to a domain name. domain A logical grouping of resources in a network for the purpose of common management and administration. Appendix E. Glossary 95

122 domain controller For a Windows NT Server or Windows 2000 Server domain, the server that authenticates domain logons and maintains the security policy and the security accounts master database for a domain. Domain controllers manage user access to a network, which includes logging on, authentication, and access to the directory and shared resources. domain name In Internet communications, a name of a host system. A domain name consists of a sequence of subnames that are separated by a delimiter character, for example, See also Domain Name System. Domain Name System (DNS) The distributed database system that maps domain names to IP addresses. See also domain name. downtime The time during which a functional unit cannot be used because of a fault within the functional unit or within the environment. drive The mechanism used to seek, read, and write information on a storage medium. dual inline memory module (DIMM) A small circuit board with memory-integrated circuits containing signal and power pins on both sides of the board. DWDM See dense wavelength division multiplexing. Back to top E encryption In computer security, the process of transforming data into an unintelligible form in such a way that the original data either cannot be obtained or can be obtained only by using a decryption process. entity A person, object, or concept about which information is stored. Ethernet A packet-based networking technology for local area networks (LANs) that supports multiple access and handles contention by using Carrier Sense Multiple Access with Collision Detection (CSMA/CD) as the access method. Ethernet is standardized in the IEEE specification. event An occurrence of significance to a task or system. Events can include completion or failure of an operation, a user action, or the change in state of a process. exception A condition or event that cannot be handled by a normal process. execution The process of carrying out an instruction or instructions of a computer program by a computer. export See share. Back to top 96 IBM SONAS 1.5.2: Software Configuration Guide

123 F fabric A complex network of hubs, switches, adapter endpoints, and connecting cables that support a communication protocol between devices. For example, Fibre Channel uses a fabric to connect devices. failback The restoration of an appliance to its initial configuration after detection and repair of a failed network or component. failover An automatic operation that switches to a redundant or standby system in the event of a software, hardware, or network interruption. failure The inability of a system or component to perform its required functions within specified performance requirements. A failure is characterized by the observable symptoms of one or more defects that have a root cause in one or more faults. failure group A collection of disks that share common access paths or adapter connection, and could all become unavailable through a single hardware failure. Fibre Channel A technology for transmitting data between computer devices. It is especially suited for attaching computer servers to shared storage devices and for interconnecting storage controllers and drives. file A collection of related data that is stored and retrieved by an assigned name. file module A module that functions as an interface node that connects a system to an Internet Protocol (IP) network for file-serving capabilities by using service protocols. file set A subset of a file system that provides granularity of functions such as snapshots or quotas within the file system. file system A collection of files and certain attributes associated with those files. file system manager The provider of services for all the nodes using a single file system. A file system manager processes changes to the state or description of the file system, controls the regions of disks that are allocated to each node, and controls token management and quota management. File Transfer Protocol (FTP) In TCP/IP, an application layer protocol that uses TCP and Telnet services to transfer bulk-data files between machines or hosts. filter A device or program that separates data, signals, or material in accordance with specified criteria. FQDN See fully qualified domain name. fragmentation An operating system's process of writing different parts of a file to Appendix E. Glossary 97

124 discontiguous sectors on a computer storage medium when contiguous space that is large enough to contain the entire file is not available. When data is thus fragmented, the time that it takes to access the data may increase because the operating system must search different tracks for information that should be in one location. free space The total amount of unused space in a page, data set, file, or storage medium. Free space is the space that is not used to store records or control information. FTP See File Transfer Protocol. FTP server A software or hardware server that responds to File Transfer Protocol. fully qualified domain name (FQDN) In Internet communications, the name of a host system that includes all of the subnames of the domain name. An example of a fully qualified domain name is rchland.vnet.ibm.com. fully qualified path A string that begins with the root directory of a file system, followed by an ordered list of subdirectories and terminated by a file name. function Any instruction or set of related instructions that performs a specific operation. Back to top G gateway A device or program used to connect networks or systems with different network architectures. Gbps See gigabits per second. General Parallel File System (GPFS) A high-performance shared-disk file system that can provide data access from nodes in a cluster environment. General Public License (GPL) A GNU term for a free, copyleft license for software and other kinds of works. Refer to the GNU General Public License site for more information. GID See group identifier. gigabit In data communications, 10 to the power of 9 or 1,000,000,000 bits. gigabits per second (Gbps) A measure of high speed bandwidth on a digital data transmission medium such as optical fiber. GPFS See General Parallel File System. GPFS node set A mounted, defined group of GPFS file systems. GPFS portability layer The interface module that each installation must build for its specific hardware platform and Linux distribution. 98 IBM SONAS 1.5.2: Software Configuration Guide

125 GPFS recovery log A file that contains a record of metadata activity and that exists for each node of a cluster. In the event of a node failure, the recovery log for the failed node is replayed, restoring the file system to a consistent state and allowing other nodes to continue working. GPFS snapshot A point-in-time copy of a file system or file set. GPFS system A cluster of nodes defined as being available for use by GPFS file systems. See also clustered system (or system). GPL See General Public License. granularity The extent to which a larger entity is subdivided. For example, a meter broken into millimeters has finer granularity than a meter broken into centimeters. graphical user interface (GUI) A computer interface that presents a visual metaphor of a real-world scene, often of a desktop, by combining high-resolution graphics, pointing devices, menu bars and other menus, overlapping windows, icons and the object-action relationship. grep A UNIX utility that allows the user to search one or more files for a specific string of text and outputs all the lines that contain the string. The user also has the option to replace the string with another. group identifier (GID) A numeric value associated with a group name that represents a specific group of users. GUI See graphical user interface. Back to top H HBA See host bus adapter. HCA See host channel adapter. heartbeat A signal that one entity sends to another to convey that it is still active. hierarchical storage management client (HSM client) A client program that works with the server to provide hierarchical storage management (HSM) for a system. hierarchical storage management (HSM) A function that automatically distributes and manages data on disk, tape, or both by regarding devices of these types and potentially others as levels in a storage hierarchy that ranges from fast, expensive devices to slower, cheaper, and possibly removable devices. The objectives are to minimize access time to data and maximize available media capacity. high availability The ability of IT services to withstand all outages and continue providing processing capability according to some predefined service level. Covered Appendix E. Glossary 99

126 outages include both planned events, such as maintenance and backups, and unplanned events, such as software failures, hardware failures, power failures, and disasters. home directory The current directory associated with the user at the time of login. host A computer that is connected to a network and that provides an access point to that network. The host can be a client, a server, or both a client and server simultaneously. See also server, client. host bus adapter (HBA) An interface card that connects a host bus, such as a peripheral component interconnect (PCI) bus, to the storage area network. host channel adapter (HCA) Based on InfiniBand technology, a port connection on a system allowing a network fabric interconnect. host computer In a computer network, a computer that provides services such as computation, database access, and network control functions. host list A comma-separated-value list of hosts used to add large numbers of hosts to the provisioning server without having to start the hosts individually on the network. host name In Internet communication, the name given to a computer. The host name might be a fully qualified domain name such as mycomputer.city.company.com, or it might be a specific subname such as mycomputer. HSM See hierarchical storage management. HSM client See hierarchical storage management client. HTTP See Hypertext Transfer Protocol. HTTPS See Hypertext Transfer Protocol Secure. Hypertext Transfer Protocol (HTTP) An Internet protocol that is used to transfer and display hypertext and XML documents on the web. Hypertext Transfer Protocol Secure (HTTPS) An Internet protocol that is used by web servers and web browsers to transfer and display hypermedia documents securely across the Internet. hypervisor A program or a portion of Licensed Internal Code that allows multiple instances of operating systems to run simultaneously on the same hardware. Back to top I ID See identifier. 100 IBM SONAS 1.5.2: Software Configuration Guide

127 identification In computer security, the process that allows a system to recognize an entity by means of personal, equipment, or organizational characteristics or codes. identifier (ID) A sequence of bits or characters that identifies a user, program, device, or system to another user, program, device, or system. ILM See information lifecycle management. incident An event that is not part of the standard operation of a service and causes or can cause a disruption to or a reduction in the quality of services and customer productivity. InfiniBand An industry-standard specification that defines an I/O architecture used to connect servers, communications infrastructure equipment, storage, and embedded systems. information lifecycle management (ILM) A policy-based file-management system for storage pools and file sets that is part of network-attached storage (NAS) features. See network-attached storage. infrastructure All the components, excluding the application framework, listed in the computing model (below) are considered as part of the infrastructure framework: data access services, application/workgroup services, presentation services, communication services, object management services, distribution services, common transport semantics, transport services (SNA/APPN, TCP/IP, OSI, etc.), signaling and control plane, LAN, WAN, channel, emerging, and base operating system. initiator The role of a node using the two-phase commit protocol when its local transaction program issues a commit operation that begins the two-phase commit flows. The initiator is the root node of a transaction program network. inode The internal structure that describes the individual files on AIX, UNIX, or Linux systems. An inode contains the node, type, owner, and location of a file. input Data entered for processing or storage input/output (I/O) Pertaining to a device, process, channel, or communication path involved in data input, data output, or both. input/output operations per second (IOPS) A standard computing benchmark used to determine the best configuration settings for servers. installation The process of adding a hardware or software component to a computing environment. Appendix E. Glossary 101

128 installation package An installable unit of a software product. Software product packages are separately installable units that can operate independently from other packages of that software product. Integrated Solutions Console (ISC) The core technology of the Autonomic Computing initiative that provides a common, consistent portal-based user interface, which is based on industry standards and component reuse. The Integrated Solutions Console can host common system administrative functions that are provided by server, software, or storage products. Intelligent Peripheral Management Interface (IPMI) A standard for controlling intelligent devices that monitor a system. It provides for dynamic discovery of sensors in the system and the ability to monitor the sensors and be informed when the sensor's values change or go outside certain boundaries. intelligent power distribution unit (ipdu) An electrical device that controls power distribution, provides circuit protection, and monitors the power and temperature of the environment. interface node A node that connects a system to an Internet Protocol (IP) network for file-serving capabilities using service protocols. I/O See input/output. I/O error An error in the processing of input or output device data. IOPS See input/output operations per second. IP address A unique address for a device or logical unit on a network that uses the Internet Protocol standard. ipdu See intelligent power distribution unit. IPMI See Intelligent Peripheral Management Interface. ISC See Integrated Solutions Console. Back to top J Java An object-oriented programming language for portable interpretive code that supports interaction among remote objects. Java was developed and specified by Sun Microsystems, Incorporated. job A separately executable unit of work. junction A special directory entry that connects a name in a directory of one file set to the root directory of another file set. Back to top K KB See kilobyte. 102 IBM SONAS 1.5.2: Software Configuration Guide

129 Kerberos A network authentication protocol that is based on symmetric key cryptography. Kerberos assigns a unique key, called a ticket, to each user who logs on to the network. The ticket is embedded in messages that are sent over the network. The receiver of a message uses the ticket to authenticate the sender. kernel The part of an operating system that contains programs for such tasks as input/output, management and control of hardware, and the scheduling of user tasks. key A cryptographic mathematical value that is used to digitally sign, verify, encrypt, or decrypt a message. key file In computer security, a file that contains public keys, private keys, trusted roots, and certificates. key pair In computer security, a public key and a private key. When the key pair is used for encryption, the sender uses the public key to encrypt the message, and the recipient uses the private key to decrypt the message. When the key pair is used for signing, the signer uses the private key to encrypt a representation of the message, and the recipient uses the public key to decrypt the representation of the message for signature verification. keytab file A file on the service's host system that contains entries each of which contains the service principal's name and encrypted secret key. kickstart To automate and facilitate unattended installation and configuration of a Red Hat Linux operating system. kilobyte For processor storage, real and virtual storage, and channel volume, 2 10 or bytes. For disk storage capacity and communications volume, bytes. Back to top L LAN See local area network. latency The time interval between the initiation of a send operation by a source task and the completion of the matching receive operation by the target task. More generally, latency is the time between a task initiating data transfer and the time that transfer is recognized as complete at the data destination. LDAP See Lightweight Directory Access Protocol. Lightweight Directory Access Protocol (LDAP) An open protocol that uses TCP/IP to provide access to directories that support an X.500 model and that does not incur the resource requirements of the more complex X.500 Directory Access Protocol (DAP). For example, LDAP can be used to locate people, organizations, and other resources in an Internet or intranet directory. Appendix E. Glossary 103

130 Linux An open source operating system that runs on a wide range of hardware platforms and has many features that are similar to the UNIX system. load balancing The monitoring of application servers and management of the workload on servers. If one server exceeds its workload, requests are forwarded to another server with more capacity. local area network (LAN) A network that connects several devices in a limited area (such as a single building or campus) and that can be connected to a larger network. local database A database that is located on the workstation in use. lock A means of preventing uncommitted changes made by one application process from being perceived by another application process and for preventing one application process from updating data that is being accessed by another process. A lock ensures the integrity of data by preventing concurrent users from accessing inconsistent data. log A collection of records that sequentially describes the events that occur in a system. log event The record of an event. log file The file where the log of events is recorded. logging The recording of data about specific events on the system, such as errors. logical unit number (LUN) In the Small Computer System Interface (SCSI) standard, a unique identifier used to differentiate devices, each of which is a logical unit (LU). login logon LUN Back to top The process of signing on to a given computer system by typing in one's user ID and password. The process of connecting to a computer system, network, or terminal session See logical unit number. M MAC See Media Access Control. MAC address See Media Access Control (MAC) address. management node A node used for configuring, administering, and monitoring a system. manager The part of a distributed management application that issues requests and receives notifications; that is, uses the services of one or more agents. man command In UNIX-based operating systems, a command that displays the specified man page. 104 IBM SONAS 1.5.2: Software Configuration Guide

131 man page In UNIX systems, one page of online documentation. Each UNIX command, utility, and library function has an associated man page. Media Access Control (MAC) In networking, the lower of two sublayers of the Open Systems Interconnection model data link layer. The MAC sublayer handles access to shared media, such as whether token passing or contention will be used. Media Access Control (MAC) address A hardware address that uniquely identifies each node of a network. On a local area network (LAN), the MAC address is the unique hardware number of a computer's network adapter card. megabyte per second (MBps) A unit of data transfer rate equal to 1024 * 1024 bytes. memory Program-addressable storage from which instructions and other data can be loaded directly into registers for subsequent running or processing. metadata Data that describes the characteristics of data; descriptive data. migration policy A user-defined schedule for moving objects from one storage class to the next. It describes the retention and class transition characteristics for a group of objects in a storage hierarchy. mirroring The process of writing the same data to multiple disks at the same time. The mirroring of data protects it against data loss within the database or within the recovery log. mode A method of operation in which the actions that are available to a user are determined by the state or setting of the system, program, or device. module A packaged functional hardware unit designed for use with other components. mount To place a data medium in a position to operate. Back to top N name An alphanumeric term that identifies a data set, statement, program, or cataloged procedure. The first character of the name must be alphabetic. name resolution In Internet communications, the process of mapping a machine name to the corresponding Internet Protocol (IP) address. name server In networking, the server that converts network names to addresses. namespace Space reserved by a file system to contain the names of its objects. naming An operation that is used to obtain references to objects that are related to applications. Appendix E. Glossary 105

132 NAS See network-attached storage. NAT See network address translation. NDMP See Network Data Management Protocol. nearline Pertaining to a type of storage in which data is available in a short amount of time, but not instantly. nearline SAS drive A drive that combines the high capacity data storage technology of a Serial Advanced Technology Attachment (SATA) drive with the benefits of a serial-attached SCSI (SAS) interface for improved connectivity. NetBIOS A standard interface to networks and personal computers that is used on local area networks to provide message, print-server, and file-server functions. Application programs that use NetBIOS do not have to handle the details of LAN data link control (DLC) protocols. network address translation (NAT) The conversion of a network address that is assigned to a logical unit in one network into an address in an adjacent network. network-attached storage (NAS) A task-optimized storage device directly attached to a network that operates independently of the general-purpose file servers. network configuration In SNA or TCP/IP, the group of links, nodes, machine features, devices, and programs that make up a data processing system, a network, or a communication system. Network Data Management Protocol (NDMP) A protocol that allows a network storage-management application to control the backup and recovery of an NDMP-compliant file server, without installing vendor-acquired software on that file server. Network File System (NFS) A protocol, developed by Sun Microsystems, Incorporated, that allows a computer to access files over a network as if they were on its local disks. Network Information Service (NIS) A set of protocols, developed by Sun Microsystems, that are used to provide directory services for network information. network interface The software that formats packets at the network layer into packets that specific network adapters can understand and transmit. Network Shared Disk (NSD) A component for cluster-wide disk naming and access. Network Time Protocol (NTP) A protocol that synchronizes the clocks of computers in a network. NFS See Network File System. NFS client A program or system that mounts remote file directories from another host called a Network File System (NFS) server. 106 IBM SONAS 1.5.2: Software Configuration Guide

133 NFS server A program or system that allows authorized remote hosts called Network File System (NFS) clients to mount and access its local file directories. NIS See Network Information Service. node A single processing unit within a system. Each node within a pair provides virtualization, cache, and Copy Services to the storage area network (SAN). node list A system object that contains a list of SNA nodes identified by an APPN network ID and control point name. The system-recognized identifier for the object type is *NODL. notification An occurrence within a process that can trigger an action. Notifications can be used to model conditions of interest to be transmitted from a sender to a (typically unknown) set of interested parties (the receivers). NSD See Network Shared Disk. NTP See Network Time Protocol. Back to top O open source Pertaining to software whose source code is publicly available for use or modification. Open source software is typically developed as a public collaboration and made freely available, although its use and redistribution might be subject to licensing restrictions. Linux is a well known example of open source software. opportunistic locking A file locking mechanism in the Server Message Block (SMB) protocol used to improve performance by controlling the caching of files on a client. optimistic locking A locking strategy whereby no lock is held between the time that a row is selected and the time that an update or a delete operation is attempted on that row. See also pessimistic locking. option A specification in a statement that can influence the running of the statement. out-of-band Pertaining to user-specific data that has meaning only for connection-oriented (stream) sockets. The server generally receives stream data in the same order that it was sent. OOB data is received independent of its position in the stream (independent of the order in which it was sent). Back to top P package An installable unit of a software product. Software product packages are separately installable units that can operate independently from other packages of that software product. Appendix E. Glossary 107

134 packet In data communication, a sequence of binary digits, including data and control signals, that are transmitted and switched as a composite whole. page The information that can be displayed at one time on the screen of a display device or in a window. panel A formatted display of information on a screen that can also include entry fields. parameter A value or reference passed to a function, command, or program that serves as input or controls actions. The value is supplied by a user or by another program or process. password In computer and network security, a specific string of characters used by a program, computer operator, or user to access the system and the information stored within it. path The route through a file system to a specific file. PDC See primary domain controller. performance A measure of a system's ability to perform its functions, including response time, throughput, and number of transactions per second. Perl A scripting language that was originally designed as a tool for writing programs in the UNIX environment but has evolved to include the power and flexibility of a high-level programming language such as C. Perl is an open-source language. permission The ability to access a protected object, such as a file or directory. The number and meaning of permissions for an object are defined by the access control list. pessimistic locking A locking strategy whereby a lock is held between the time that a row is selected and the time that a searched update or delete operation is attempted on that row. See also optimistic locking. petabyte A measure of memory or storage capacity that is 2 to the 50th power bytes or approximately a thousand terabytes. PFS See physical file system. physical file system (PFS) The part of the operating system that handles the actual storage and manipulation of data on a storage medium. platform The combination of an operating system and hardware that makes up the operating environment in which a program runs. policy A set of considerations that influence the behavior of a managed resource or a user. policy rule A programming statement within a policy that defines a specific action to be performed. pool A group of resources with similar characteristics and attributes. 108 IBM SONAS 1.5.2: Software Configuration Guide

135 port An end point for communication between applications, generally referring to a logical connection. A port provides queues for sending and receiving data. Each port has a port number for identification. Portable Operating System Interface (POSIX) An IEEE family of standards designed to provide portability between operating systems that are based on UNIX. POSIX describes a wide spectrum of operating-system components ranging from C language and shell interfaces to system administration. POSIX See Portable Operating System Interface. Preboot Execution Environment (PXE) An industry standard target/server interface that allows networked computers that are not yet loaded with an operating system to be configured and booted remotely. PXE is based on Dynamic Host Configuration Protocol (DHCP). primary domain controller (PDC) See domain controller. primary GPFS cluster configuration server In a GPFS cluster, the node chosen to maintain the GPFS cluster configuration data. priority A rank assigned to a task that determines its precedence in receiving system resources. project prefix An identifier used for requirements in cross-project traceability. propagation A process in which groups of configuration parameters are updated and take effect at different rates. protocol A set of rules controlling the communication and transfer of data between two or more devices or systems in a communication network. provisioning The process of configuring servers, software, networks, and storage resources. public IP address An Internet Protocol (IP) address used to communicate on a public network. PXE See Preboot Execution Environment. Back to top Q QoS See quality of service. qualified name A name made unique by the addition of one or more qualifiers. Appendix E. Glossary 109

136 quality of service (QoS) Any operation that allows traffic priorities to be designated. Through quality of service, different traffic throughout a network can be classified and administered. query quota Back to top R rack A request for information from a database that is based on specific conditions: for example, a request for a list of all customers in a customer table whose balances are greater than USD1000. The amount of disk space and number of files and directories assigned as upper limits for a specified user, group of users, or file set. A free-standing structure or frame that can hold multiple servers and expansion units. RAID See Redundant Array of Independent Disks. range The set of values that a quantity or function may take. read access In computer security, permission to read information. Redundant Array of Independent Disks (RAID) A collection of two or more physical disk drives that present to the host an image of one or more logical disk drives. In the event of a physical device failure, the data can be read or regenerated from the other disk drives in the array due to data redundancy. Reliable Scalable Cluster Technology (RSCT) A set of software components that together provide a comprehensive clustering environment for AIX and Linux. RSCT is the infrastructure used by a variety of IBM products to provide clusters with improved system availability, scalability, and ease of use. remote access In computer networking, communication with a data-processing facility by means of a data link. Remote Supervisor Adapter (RSA) An IBM service processor that is built into some System x servers and available as an optional adapter for use with others. When used as a gateway service processor, the RSA can communicate with all service processors on the Advanced System Management (ASM) interconnect. response file A file containing predefined values that is used instead of someone having to enter those values one at a time. role A job function that identifies the tasks that a user can perform and the resources to which a user has access. A user can be assigned one or more roles. rolling upgrade In clustered systems, updating the system software on a cluster without interrupting service to the users of the cluster. root The user name for the system user with the most authority. 110 IBM SONAS 1.5.2: Software Configuration Guide

137 root directory In the operating systems for personal computers, the directory on a disk or diskette that contains the list of files stored on that disk or diskette. If more than one directory is on a disk or diskette, the root directory is at the top of the hierarchy of directories. The root directory is created by the operating system when the disk or diskette is formatted. root squash In the Network File System (NFS) Protocol, a reduction of the access rights for the remote superuser (root) when using identity authentication (the local user is the same as remote user). root user A system user who operates without restrictions. A root user has the special rights and privileges needed to perform administrative tasks. round-robin Pertaining to an operation in which the database manager provides a continuous, even distribution of data within memory, across data partitions, or across storage containers. RSA See Remote Supervisor Adapter. RSCT See Reliable Scalable Cluster Technology. rule Back to top A list of conditions and actions that are triggered when certain conditions are met. Conditions include attributes about an object (file name, type or extension, dates, owner, and groups), the requesting client, and the container name associated with the object. S SAN See storage area network. SAS See serial-attached SCSI. SATA See Serial Advanced Technology Attachment. scalability The ability of a system to expand as resources, such as processors, memory, or storage, are added. Scale out File Service (SoFS) A highly-scalable, grid-based network-attached storage (NAS) solution. It is based on the General Parallel File System (GPFS). scheduled job A batch job that becomes eligible to run at a specified date and time. scheduler A multithread, multiprocess background server designed to handle the scheduling and launching of jobs, based on a simple timing scheme. schema A collection of database objects such as tables, views, indexes, or triggers that define a database. A schema provides a logical classification of database objects. SCP See Secure Copy Protocol. SCM See service configuration management. Appendix E. Glossary 111

138 SCP program A client program that implements the SCP protocol. screen The physical surface of a display device upon which information is shown to a user. script A series of commands, combined in a file, that carry out a particular function when the file is run. Scripts are interpreted as they are run. SCS See Storage Cloud Services. SCSI See Small Computer System Interface. secondary GPFS cluster configuration server In a GPFS cluster, the node chosen to maintain the GPFS cluster configuration data in the event that the primary GPFS cluster configuration server fails or becomes unavailable. Secure Copy Protocol (SCP) The secure transfer of computer files between a local and a remote host or between two remote hosts, using the Secure Shell (SSH) protocol. Secure Shell (SSH) A network protocol for secure data exchange between two networked devices. The client can use public-key and private-key authentication, or password authentication, to access the remote server. Secure Sockets Layer (SSL) A security protocol that provides communication privacy. With SSL, client/server applications can communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery. security The protection of data, system operations, and devices from accidental or intentional ruin, damage, or exposure. security certificate A certificate containing information used by the SSL protocol to establish a secure connection. The information can include who a certificate belongs to, who issued it, its unique serial number, its valid dates, and its encrypted 'fingerprint' that is used to verify the contents of the certificate. security identifier (SID) On Windows systems, a supplement to the user ID that identifies the full user account details on the Windows security account manager database where the user is defined. Serial Advanced Technology Attachment (SATA) A standard for connecting storage devices such as hard drives and CD ROM drives to computer systems that is based on serial signaling technology. serial-attached SCSI (SAS) A data-transfer technology that moves data to and from computer storage devices. Serial-attached SCSI uses a point-to-point serial protocol, which replaces the traditional, parallel SCSI bus technology. server A software program or a computer that provides services to other software programs or other computers. See also host, client. Server Message Block (SMB) A protocol that manages requests and responses in a client/server 112 IBM SONAS 1.5.2: Software Configuration Guide

139 environment so that clients on a network can share files, directories, and devices. See also Server Message Block2. Server Message Block 2.0 (SMB2) A higher performing, more scalable version of Server Message Block (SMB). This protocol can send multiple commands in the same packet and uses larger buffer sizes. See also Common Internet File System and Server Message Block.. server name An identifier that designates an application server. In a federated system, the server name also designates the local name of a data source. service configuration management (SCM) A component that can generate the configuration files to run services such as GPFS, NFS, NIS, VSFTP, HTTP, and SCP, and can monitor, stop, or start the services. service-oriented architecture (SOA) A conceptual description of the structure of a software system in terms of its components and the services they provide, without regard for the underlying implementation of these components, services and connections between components. Services for UNIX (SFU) An interoperability toolkit from Microsoft Windows, it enables Windows-based and UNIX-based computers to share data, security credentials, and scripts. session setup SFU share A logical or virtual connection between two stations, software programs, or devices on a network that allows the two elements to communicate and exchange data for the duration of the session. The preparation of a computing system to perform a job or job step. Setup is usually performed by an operator and often involves the performance of routine functions. See Services for UNIX. The process of making file systems, file sets, or directories accessible to authorized remote clients by using supported services. See also export. shared file system An operating system extension that allows multiple users or computers to use the same set of files at the same time, across a network. To each user, the shared file system appears to be an extension of the local file system. shell A software interface between users and an operating system. Shells generally fall into one of two categories: a command line shell, which provides a command line interface to the operating system; and a graphical shell, which provides a graphical user interface (GUI). shutdown A status condition that describes when the cluster is shut down as intended. SID See security identifier. Simple Network Management Protocol (SNMP) A set of protocols for monitoring systems and devices in complex networks. Information about managed devices is defined and stored in a Management Information Base (MIB). Appendix E. Glossary 113

140 site A location in a network that holds Active Directory servers. A site is defined as one or more well-connected TCP/IP subnets. Small Computer System Interface (SCSI) An ANSI-standard electronic interface that allows personal computers to communicate with peripheral hardware, such as disk drives, tape drives, CD-ROM drives, printers, and scanners faster and more flexibly than previous interfaces. Smart Business Desktop Cloud A virtualized IT environment to help provide security-rich, anytime, anywhere access to applications, information and resources. SMIT See System Management Interface Tool. snapshot 1. A point-in-time copy of an entire active file system. 2. An image backup type that consists of a point-in-time view of a volume. SNMP See Simple Network Management Protocol. SNMP trap An SNMP message sent from the SNMP agent to the SNMP manager. The message is initiated by the SNMP agent and is not a response to a message sent from the SNMP manager. SOA See service-oriented architecture. SoFS See Scale out File System. split-brain scenario A type of failure in which communication with the remote site is lost, but the remote site does not fail. This situation leads to a mirror split with two live sites where neither site mirrors the data. SQL See Structured Query Language. SQL connection An association between an application process and a local or remote application server or database server. SQL query A component of certain SQL statements that specifies a result table. SSH See Secure Shell. SSL See Secure Socket Layer. stack An area in memory that typically stores information such as temporary register information, values of parameters, and return addresses of subroutines and is based on the principle of last in, first out (LIFO). stanza A group of lines in a file that together have a common function or define a part of the system. Stanzas are usually separated by blank lines or colons, and each stanza has a name. statesave Binary data collection that is used in problem determination. station An input or output point of a system that uses telecommunication 114 IBM SONAS 1.5.2: Software Configuration Guide

141 facilities; for example, one or more systems, computers, terminals, devices, and associated programs at a particular location that can send or receive data over a telecommunication line. storage A functional unit into which data can be placed, in which it can be retained, and from which it can be retrieved. storage area network (SAN) A dedicated storage network tailored to a specific environment, combining servers, systems, storage products, networking products, software, and services. Storage Cloud Services (SCS) A high-performance, secured, and shared storage cloud infrastructure used to provide enterprise-class storage capacity and multitenancy for multiple customers. storage controller A device, such as a Redundant Array of Independent Disks (RAID) controller, that creates and manages other storage devices. storage device A logical unit number (LUN) that terminates a collection of ports on the storage network. storage node A node used to provide the back-end storage and file system to store the data in a system. storage pod A logical entity of components of a system that consists of two storage nodes and one or two storage systems. storage pool A grouping of storage space consisting of volumes, logical unit numbers (LUNs), or addresses that share a common set of administrative characteristics. storage port An engine's connection point to a storage client network. A storage port is a member of a single fabric. storage-side node See storage node. storage subsystem A storage control and its attached storage devices. string In programming languages, the form of data used for storing and manipulating text. Structured Query Language (SQL) A standardized language for defining and manipulating data in a relational database. stub A shortcut on the Windows file system that is generated by the hierarchical storage management (HSM) client for a migrated file that allows transparent user access. A stub is the sparse file representation of a migrated file, with a reparse point attached. subdirectory A directory contained within another directory in a file system hierarchy. Appendix E. Glossary 115

142 subnet A network that is divided into smaller independent subgroups, which still are interconnected. See subnetwork. subnetwork A network that is divided into smaller independent subgroups, which still are interconnected. superuser authority The unrestricted ability to access and modify any part of the operating system, usually associated with the user who manages the system. swap In a system with virtual storage, to write the main storage image of a job to auxiliary storage and read the image of another job into processor storage. switch A network infrastructure component to which multiple nodes attach. Unlike a hub, a switch typically has internal bandwidth that is a multiple of link bandwidth and the ability to rapidly switch a node connection from one to another. A typical switch can accommodate several simultaneous full-link bandwidth transmissions between different pairs of nodes. synchronous replication A type of replication that delivers updates continuously and within the scope of source transactions. Related term asynchronous replication. syntax The rules for the construction of a command or statement. syslog A standard for transmitting and storing log messages from many sources to a centralized location to enhance system management. system A functional unit, consisting of one or more computers and associated software, that uses common storage for all or part of a program and also for all or part of the data necessary for the execution of the program. A system can be a stand-alone unit, or it can consist of multiple connected units. system administrator The person who controls and manages a computer system. System Management Interface Tool (SMIT) An interface tool of the AIX operating system for installing, maintaining, configuring, and diagnosing tasks. system pool A storage pool that contains the system metadata (system and file attributes, configuration information, and metadata server state) that is accessible to all metadata servers in the cluster. There is only one system pool. system time The amount of time that the operating system spends providing services to an application. System time includes time spent by the operating system allocating storage or devices to a program and time spent processing operating system calls that a program makes. Back to top T tar A UNIX archive utility for storing data on tape media. 116 IBM SONAS 1.5.2: Software Configuration Guide

143 tar file A compressed file that uses a method of compression that compresses the entire file rather than breaking it up, often used for distributing open source code. TCP/IP See Transmission Control Protocol/Internet Protocol. TCP/IP port A 2-byte value that identifies a TCP/IP network application within a TCP/IP host. TDB See trivial database. terabyte (TB) For processor storage, real and virtual storage, and channel volume, 2 to the 40th power or bytes. For disk storage capacity and communications volume, bytes. terminal emulator A program that allows a device such as a microcomputer or personal computer to enter and receive data from a computer system as if it were a particular type of attached terminal. throughput A measure of the amount of information transmitted over a network in a given period of time. It is generally measured in bits per second (bps), kilobits per second (Kbps), or megabits per second (Mbps). time stamp The value of an object that indicates the system time at some critical point in the object's history. Tivoli Storage Manager A client/server product that provides storage management and data access services in a heterogeneous environment. Tivoli Storage Manager supports various communication methods, provides administrative facilities to manage the backup and storage of files, and provides facilities for scheduling backups. TLS See Transport Layer Security. traffic In data communication, the quantity of data transmitted past a particular point in a path. transfer To send data from one location to another. Transmission Control Protocol/Internet Protocol (TCP/IP) An industry-standard, nonproprietary set of communication protocols that provides reliable end-to-end connections between applications over interconnected networks of different types. Transport Layer Security (TLS) An Internet Engineering Task Force (IETF)-defined security protocol that is based on Secure Sockets Layer (SSL) and is specified in RFC trap In the Simple Network Management Protocol (SNMP), a message sent by a managed node (agent function) to a management station to report an exception condition. Appendix E. Glossary 117

144 trivial database (TDB) An extremely small database that allows multiple simultaneous writers and uses internal locking to keep writers from overwriting each other. troubleshoot To diagnose and solve a problem. trunk Back to top In telephony, circuits that connect two switching systems, as opposed to connecting a customer line to a switching system. U UDP See User Datagram Protocol. UEFI See Unified Extensible Firmware Interface. UID See user name. UNC See Universal Naming Convention. Unicode A character encoding standard that supports the interchange, processing, and display of text that is written in the common languages around the world, plus many classical and historical texts. Unified Extensible Firmware Interface (UEFI) A specification that details the interface between the operating system and the platform firmware at boot time. It is not specific to any processor architecture. Universal Naming Convention (UNC) The server name and network name combined. These names together identify the resource on the domain. UNIX A highly portable operating system that features multiprogramming in a multiuser environment. The UNIX operating system was originally developed for use on minicomputers, but was adapted for mainframes and microcomputers. The AIX operating system is IBM's implementation of the UNIX operating system. UNIX file system A section of the UNIX file tree that is physically contained on a single device or disk partition, and that can be separately mounted, unmounted, and administered. update Software maintenance such as a manufacturing refresh, refresh pack, or fix pack that changes the modification level of a product. upgrade To install a new version or release of a product to replace an earlier version or release of the same product. user Any individual, organization, process, device, program, protocol, or system that uses the services of a computing system. user account The login directory and other information that gives a user access to the system. User Datagram Protocol (UDP) An Internet protocol that provides unreliable, connectionless datagram 118 IBM SONAS 1.5.2: Software Configuration Guide

145 service. It enables an application program on one machine or process to send a datagram to an application program on another machine or process. user ID The name used to associate the user profile with a user when a user signs on to a system. user number (UID) In UNIX systems, a number that uniquely identifies a user to the system. The UID is the internal number associated with a user ID. user name A string of characters that uniquely identifies a user to a system. See also user ID. Back to top V validation The checking of data or code for correctness or for compliance with applicable standards, rules, and conventions. value In programming, the alphabetic or numeric contents of a variable or a storage location. variable A user-defined default value specified in an access definition. virtualized A property of the on-demand operating environment that makes the best use of technology resources and minimizes complexity for users. Virtualized networks deliver computing as needed. virtualized storage Physical storage that has virtualization techniques applied to it by a virtualization engine. virtual local area network (VLAN) A logical association of switch ports based upon a set of rules or criteria, such as Medium Access Control (MAC) addresses, protocols, network address, or multicast address. This concept permits the LAN to be segmented again without requiring physical rearrangement. virtual processor A multithreaded process that makes up the database server and is similar to the hardware processors in the computer. It can serve multiple clients and, where necessary, run multiple threads to work in parallel for a single query. VLAN See virtual local area network. volume A discrete unit of storage on disk, tape or other data recording medium that supports some form of identifier and parameter list, such as a volume label or input/output control. Volume Shadow Copy Service (VSS) A set of Microsoft application-programming interfaces (APIs) that are used to create shadow copy backups of volumes, exact copies of files, including all open files, and so on. VSS See Volume Shadow Copy Service. Appendix E. Glossary 119

146 Back to top W white space A sequence of one or more characters, such as the blank character, the newline character, or the tab character, that belong to the space character class. wildcard character A special character such as an asterisk (*) or a question mark (?) that can be used to represent one or more characters. Any character or set of characters can replace the wildcard character. winbind A system in the Samba suite of programs that provides a unified logon between UNIX and Microsoft Windows NT. window An area of the screen with visible boundaries in which an application program or information is displayed or in which a dialog is presented. write access In computer security, permission to write to an object. writing The action of making a recording of data on an external storage device or other data medium. Back to top X X Window System A software system, developed by the Massachusetts Institute of Technology, that enables the user of a display to concurrently use multiple application programs through different windows of the display. The application programs can execute on different computers. Back to top Z zone A collection of fibre-channel device ports that are permitted to communicate with each other using the fabric. Types of device ports for zone purposes are node ports (N_ports) or node loop ports (NL_ports). Any two N_ports or NL_ports that are not members of at least one common zone are not permitted to communicate using the fabric. zone configuration The set of groups of fabric ports (F_ports) that define the zones for a given fabric. zoning Back to top In fibre-channel environments, the grouping of multiple ports to form a virtual, private, storage network. Ports that are members of a zone can communicate with each other, but are isolated from ports in other zones. 120 IBM SONAS 1.5.2: Software Configuration Guide

147 Appendix F. Accessibility features for IBM SONAS Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully. Accessibility features These are the major accessibility features in the IBM SONAS: v You can use screen-reader software and a digital speech synthesizer to hear what is displayed on the screen. HTML documents have been tested using JAWS version v This product uses standard Windows navigation keys. v Interfaces that are commonly used by screen readers. v Keys that are discernible by touch but do not activate just by touching them. v Industry-standard devices for ports and connectors. v The attachment of alternative input and output devices. Keyboard navigation You can use keys or key combinations to perform operations and initiate menu actions that can also be done through mouse actions. You can navigate the IBM SONAS information from the keyboard by using the shortcut keys for your browser or screen-reader software. See your browser or screen-reader software Help for a list of shortcut keys that it supports. IBM and accessibility See the IBM Human Ability and Accessibility Center for more information about the commitment that IBM has to accessibility: Copyright IBM Corp. 2009,

148 122 IBM SONAS 1.5.2: Software Configuration Guide

149 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATIONS "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been Copyright IBM Corp. 2009,

150 estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at Copyright and trademark information at Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries. 124 IBM SONAS 1.5.2: Software Configuration Guide

151 Homologation statement Electronic emission notices This product may not be certified in your country for connection by any means whatsoever to interfaces of public telecommunications networks. Further certification may be required by law prior to making any such connection. Contact an IBM representative or reseller for any questions. This section contains the electronic emission notices or statements for the United States and other countries. Federal Communications Commission (FCC) statement This explains the Federal Communications Commission's (FCC s) statement. This equipment has been tested and complies 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, might 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. Properly shielded and grounded cables and connectors must be used to meet FCC emission limits. IBM is not responsible for any radio or television interference caused by using other than recommended cables and connectors, or by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could void the users authority to operate the equipment. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device might not cause harmful interference, and (2) this device must accept any interference received, including interference that might cause undesired operation. Industry Canada compliance statement This Class A digital apparatus complies with Canadian ICES-003. Cet appareil numérique de la classe A est conform à la norme NMB-003 du Canada. Australia and New Zealand Class A Statement Attention: This is a Class A product. In a domestic environment this product might cause radio interference in which case the user might be required to take adequate measures. European Union Electromagnetic Compatibility Directive This product is in conformity with the protection requirements of European Union (EU) Council Directive 2004/108/EC on the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the fitting of non-ibm option cards. Notices 125

152 Attention: This is an EN Class A product. In a domestic environment this product might cause radio interference in which case the user might be required to take adequate measures. Responsible Manufacturer: International Business Machines Corp. New Orchard Road Armonk, New York European community contact: IBM Deutschland GmbH Technical Regulations, Department M372 IBM-Allee 1, Ehningen, Germany Tele: lugi@de.ibm.com Germany Electromagnetic Compatibility Directive Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie zur Elektromagnetischen Verträglichkeit Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 2004/108/EG zur Angleichung der Rechtsvorschriften über die elektromagnetische Verträglichkeit in den EU-Mitgliedsstaaten und hält die Grenzwerte der EN Klasse A ein. Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der IBM verändert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne Empfehlung der IBM gesteckt/eingebaut werden. EN Klasse A Geräte müssen mit folgendem Warnhinweis versehen werden: Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbereich Funk-Störungen verursachen; in diesem Fall kann vom Betreiber verlangt werden, angemessene Mabnahmen zu ergreifen und dafür aufzukommen. Deutschland: Einhaltung des Gesetzes über die elektromagnetische Verträglichkeit von Geräten Dieses Produkt entspricht dem Gesetz über die elektromagnetische Verträglichkeit von Geräten (EMVG). Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in der Bundesrepublik Deutschland. Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagnetische Verträglichkeit von Geräten (EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) für Geräte der Klasse A Dieses Gerät ist berechtigt, in übereinstimmung mit dem Deutschen EMVG das EG-Konformitätszeichen - CE - zu führen. 126 IBM SONAS 1.5.2: Software Configuration Guide

153 Verantwortlich für die Einhaltung der EMV Vorschriften ist der Hersteller: International Business Machines Corp. New Orchard Road Armonk,New York Tel: Der verantwortliche Ansprechpartner des Herstellers in der EU ist: IBM Deutschland GmbH Technical Regulations, Abteilung M372 IBM-Allee 1, Ehningen, Germany Tele: Generelle Informationen: Das Gerät erfüllt die Schutzanforderungen nach EN und EN Klasse A. People's Republic of China Class A Statement Taiwan Class A Statement Taiwan Contact Information This topic contains the product service contact information for Taiwan. IBM Taiwan Product Service Contact Information: IBM Taiwan Corporation 3F, No 7, Song Ren Rd., Taipei Taiwan Tel: Notices 127

154 Japan Voluntary Control Council for Interference Class A Statement This explains the Japan Voluntary Control Council for Interference (VCCI) statement. Japan Electronics and Information Technology Industries Association Statement This explains the Japan Electronics and Information Technology Industries Association (JEITA) statement for less than or equal to 20 A per phase. This explains the JEITA statement for greater than 20 A per phase. jjieta2 Korean Communications Commission Class A Statement This explains the Korean Communications Commission (KCC) statement. Russia Electromagnetic Interference Class A Statement This statement explains the Russia Electromagnetic Interference (EMI) statement. 128 IBM SONAS 1.5.2: Software Configuration Guide