User s Guide. Lattus A X Rev A

Transcription

1 User s Guide Lattus A X Rev A

2 Lattus A X Access Node User s Guide, Rev A, October 2013, Product of USA. Quantum Corporation provides this publication as is without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability or fitness for a particular purpose. Quantum Corporation may revise this publication from time to time without notice. COPYRIGHT STATEMENT 2013 Quantum Corporation. All rights reserved. Your right to copy this manual is limited by copyright law. Making copies or adaptations without prior written authorization of Quantum Corporation is prohibited by law and constitutes a punishable violation of the law. TRADEMARK STATEMENT Quantum, the Quantum Logo, Backup. Recovery. Archive. It's What We Do., Be Certain, Be Quantum Certain, DLT, the DLT Logo, DLTSage, DLTtape, the DLTtape Logo, DXi, DXi Accent, Dynamic Powerdown, FastSense, FlexLink, GoProtect, GoVault, ilayer, Lattus, MediaShield, Optyon, Pocket-sized., Wellarmored., Preserving the World's Most Important Data. Yours., Q-Cloud, Quantum Certain, Quantum Certainty, Quantum vmpro, Scalar, SDLT, SiteCare, SmartVerify, StorageCare, StorNext, Super DLTtape, SuperLoader, and Vision are either registered trademarks or trademarks of Quantum Corporation and its affiliates in the United States and/or other countries. All other trademarks are the property of their respective owners. Products mentioned herein are for identification purposes only and may be registered trademarks or trademarks of their respective companies. All other brand names or trademarks are the property of their respective owners. Quantum specifications are subject to change. ii Lattus A X Access Node User s Guide

3 Contents Chapter 1 Introduction 1 Overview Audience Notes, Cautions, and Warnings Chapter 2 Available Documentation and Training 3 Documentation Lattus Documentation Lattus A10 Access for NFS/CIFS Documentation Training Chapter 3 Product Overview 5 Chapter 4 Lattus A10 Access Node Hardware Overview 7 Chapter 5 Lattus A10 Access Node Licensing 9 Lattus A X Access Node User s Guide iii

4 Contents Chapter 6 Basic Operations 11 Logging in to the Lattus A10 Access Node CLI Logging in to the Lattus A10 Access Node GUI Accessing Help Creating CIFS Shares Creating NFS Shares Configuring Wide Area Storage Policies Entering the Namespace, Source Directories and Advanced Tabs Finishing the Policy Managing Permissions for NFS and CIFS Shares Updating Your Centrify Configuration Shutting Down the Lattus A10 Access Node Chapter 7 Monitoring the System From the Lattus A10 Access Node 25 Monitoring the Connection Between the Lattus A10 Access Node and Lattus C10 Controller Nodes Configuring Server Settings Configuring Notifications Chapter 8 Configuring NFS and CIFS Clients 33 Configuring Linux NFS Clients Configuring Windows CIFS Clients Chapter 9 Troubleshooting 37 Monitoring LEDs on the Lattus A10 Access Node Hardware Monitoring LEDs on the Front of the Lattus A10 Access Node.38 Monitoring LEDs on the Rear of the Lattus A10 Access Node..39 Monitoring the Lattus A10 Access Node for Alerts iv Lattus A X Access Node User s Guide

5 Contents Monitoring the Lattus A10 Access Node for Tickets Viewing Ticket Information Editing Ticket Information Closing Tickets Chapter 10 Getting Help 47 Locating the System Serial Number Contacting Quantum Support Lattus A X Access Node User s Guide v

6 Contents vi Lattus A X Access Node User s Guide

7 Chapter 1 Introduction Overview This User s Guide includes the following chapters: Available Documentation and Training on page 3 Product Overview on page 5 Lattus A10 Access Node Hardware Overview on page 7 Lattus A10 Access Node Licensing on page 9 Basic Operations on page 11 Troubleshooting on page 37 Getting Help on page 47 Audience This document is intended for users of the Lattus A10 Access Node. Lattus A X Access Node User s Guide 1

8 Chapter 1: Introduction Overview Notes, Cautions, and Warnings The following formats used throughout this guide indicate important information: Note: A Note emphasizes important information related to the main topic. There are no hazardous or damaging consequences. Caution: A Caution indicates potential hazards to equipment or data. Failure to take or avoid this action could result in loss of data or harm to equipment. WARNING: A Warning indicates potential hazards to personal safety. Failure to take or avoid this action could result in physical harm to the user or hardware. 2 Lattus A X Access Node User s Guide

9 Chapter 2 Available Documentation and Training This chapter describes the documentation and training resources available for your Lattus system. Documentation The following documentation is available on the Lattus Object Storage Support page: Lattus Documentation Lattus User s Guide This guide provides instructions to assist users in monitoring, maintaining, and performing basic operations on their Lattus system. Lattus Release Notes Provides important information, latebreaking news, and a list of known issues Lattus users should know about. Lattus Site Planning Guide Provides component specifications and assists end-users in preparing the site for Lattus installation. Lattus User Essentials Provides essential information and instructions about Quantum Lattus Object Storage. Lattus A X Access Node User s Guide 3

10 Chapter 2: Available Documentation and Training Training Lattus A10 Access for NFS/CIFS Documentation Lattus A10 User Essentials Provides essential information and instructions about the Lattus A10 Access Node. Training To access training and support materials related to your Lattus system, such as video demos, visit the Quantum Lattus Object Storage Support page on Quantum.com, and go to the Training tab ( 4 Lattus A X Access Node User s Guide

11 Chapter 3 Product Overview The Lattus A10 Access Node is the gateway between your applications and the Lattus object storage. The Lattus A10 Access Node leverages industry-standard NAS protocols (CIFS and NFS) without rewriting applications to utilize the proprietary HTTP/REST API. Using the Lattus A10 GUI, you will configure Wide Areas Storage (WAS) Policies that associate your NFS and CIFS shares with namespaces in the Lattus object storage. Each NFS and CIFS share configured on your Lattus A10 Access Node should be associated with a single namespace, and each namespace should only be used for a single NFS or CIFS share. Lattus A X Access Node User s Guide 5

12 Chapter 3: Product Overview 6 Lattus A X Access Node User s Guide

13 Chapter 4 Lattus A10 Access Node Hardware Overview This chapter provides graphical representations of the Lattus A10 Access Node hardware. Front View Lattus A X Access Node User s Guide 7

14 Chapter 4: Lattus A10 Access Node Hardware Overview Rear View 8 Lattus A X Access Node User s Guide

15 Chapter 5 Lattus A10 Access Node Licensing Software licensing on the Lattus A10 Access Node includes: Maintenance - A Maintenance license verifies that your site has purchased Lattus upgrade licenses, and is required for Lattus upgrades. It is also used at run time to verify the Lattus version in the software matches what was purchased. SNFS Wide Area Storage (SNFS-WAS) - An SNFS Wide Area Storage license enables you to access Lattus object storage features. Lattus A X Access Node User s Guide 9

16 Chapter 5: Lattus A10 Access Node Licensing 10 Lattus A X Access Node User s Guide

17 Chapter 6 Basic Operations This chapter describes the following basic operations related to the Lattus A10 Access Node: Logging in to the Lattus A10 Access Node CLI on page 12 Logging in to the Lattus A10 Access Node GUI on page 12 Accessing Help on page 13 Creating CIFS Shares on page 14 Creating NFS Shares on page 16 Configuring Wide Area Storage Policies on page 17 Managing Permissions for NFS and CIFS Shares on page 22 Updating Your Centrify Configuration on page 23 Shutting Down the Lattus A10 Access Node on page 23 Lattus A X Access Node User s Guide 11

18 Chapter 6: Basic Operations Logging in to the Lattus A10 Access Node CLI Logging in to the Lattus A10 Access Node CLI Some tasks require you to use the Lattus A10 Access Node command line interface (CLI). To log in to the Lattus A10 Access Node's CLI, do the following: 1 Connect to the Lattus A10 Access Node through SSH by using the following command: ssh root@[lattus A10 IP] 2 At the password prompt, enter the root password Note: The root password should have been set during system installation. Logging in to the Lattus A10 Access Node GUI Some tasks require you to use the Lattus A10 Access Node GUI. To log in to the Lattus A10 Access Node's GUI, do the following: 1 Open a Web browser (such as Internet Explorer or Firefox,) and in the address field enter address (where IP address is the IP address of the Lattus A10 Access Node whose GUI you want to access). 2 When the login screen appears, enter your user name and password. Note: The default user name is admin, and the default password is password. If you changed the user name and password to something other than the defaults, write them in the spaces below for reference: User name: Password: 12 Lattus A X Access Node User s Guide

19 Chapter 6: Basic Operations Accessing Help 3 Click Login. Accessing Help If you need help performing tasks in the GUI, the Lattus A10 Access Node provides two forms of online help: a searchable list of all available help topics, and context-appropriate help pages. Searchable List: To access the online Help system, click the Help icon (question mark) located at the upper right corner of the screen. A list of available help topics appears in a separate browser window. Context-appropriate help: To view help pertaining specifically to the page currently displayed, click the blue question mark icon located on the upper right side of the screen. Lattus A X Access Node User s Guide 13

20 Chapter 6: Basic Operations Creating CIFS Shares In addition to the online help options above, the GUI's Help menu contains the following options: Documentation: Access the Lattus Object Storage documentation How-to Videos: Access the Lattus Object Storage how-to videos Support: Access Quantum Technical Support information About: Access detailed information about your version of the Lattus A10 Access Node, supporting components, and your operating system and version. Also shows Lattus A10 Access Node patent information. Creating CIFS Shares To add a CIFS share to the Lattus A10 Access Node, do the following: 1 Log in to the Lattus A10 Access Node's CLI (See Logging in to the Lattus A10 Access Node CLI on page 12 for instructions). 14 Lattus A X Access Node User s Guide

21 Chapter 6: Basic Operations Creating CIFS Shares 2 Use a text editor (e.g., vi, vim, gedit) to open /etc/samba/ smb.conf. 3 Go to the bottom of the file. 4 To add a CIFS share, add the following lines to the bottom of file: [CIFS share name] path = /stornext/snfs1/[cifs share name] writeable = yes Note: The value for CIFS share name will vary. Enter the actual name that you want to use for the share. For example, to create a CIFS share called CIFSshare01, you would add the following lines to /etc/samba/smb.conf: CIFSshare01 path = /stornext/snfs1/cifsshare01 writeable = yes 5 If you need to add more than one CIFS share, repeat step 4 for each additional share. 6 Once all updates have been made, save the file. 7 Issue the following command:. #killall -HUP smbd This will restart the smbd server daemon and reload the configuration from /etc/samba/smb.conf. All of the added shares will be visible. Notes: Exporting any directory through both NFS and CIFS is not supported on the Lattus A10 Access Node. You will need to associate each share with a namespace using the Lattus A10 Access Node's GUI. Each namespace should only be associated with a single share, so the ratio of namespaces to shares is 1:1. If you need to create additional shares, create an equal number of additional namespaces with which you can associate the shares. For details on creating namespaces, refer to Basic Operations section of the Lattus User's Guide. Lattus A X Access Node User s Guide 15

22 Chapter 6: Basic Operations Creating NFS Shares Creating NFS Shares To add an NFS share to the Lattus A10 Access Node, do the following: 1 Log in to the Lattus A10 Access Node's CLI (See Logging in to the Lattus A10 Access Node CLI on page 12 for instructions). 2 Use a text editor (e.g., vi, vim, gedit) to open /etc/exports. 3 To add NFS shares, add the following to the bottom of the file for each share you want to create: /stornext/snfs1/[nfs share name] *(rw,insecure,no_root_squash) Notes: The value for NFS share name will vary. Enter the actual name that you want to use for the share. For example, to create an NFS share called NFSshare01, you would add the following to /etc/exports: /stornext/snfs1/nfsshare01 *(rw,insecure,no_root_squash) When creating NFS shares on the Lattus A10 Access Node, the key exports option to use is rw which allows both read and write access. Other security-related options may be supplied as needed. See the exports (5) man page for additional details. The example above also permits access by any system (including some AIX NFS clients that require the insecure option), and allows full privileges to superuser running on an NFS client. 4 Once all exports are defined, re-export file systems: # exportfs -av Notes: Exporting any directory through both NFS and CIFS is not supported on the Lattus A10 Access Node. You will need to associate each share with a namespace using the Lattus A10 Access Node's GUI. Each namespace should only be associated with a single share, so the ratio of namespaces to shares is 1:1. If you need to create additional shares, create an equal number of additional namespaces with which you can 16 Lattus A X Access Node User s Guide

23 Chapter 6: Basic Operations Configuring Wide Area Storage Policies associate the shares. For details on creating namespaces, refer to the Basic Operations section of the Lattus User's Guide. Configuring Wide Area Storage Policies Note: Before configuring your Wide Area Storage Policies, be sure that you have created your NFS and/or CIFS shares on the Lattus A10 Access Node. See the instructions for Creating NFS Shares on page 16, and the instructions for Creating CIFS Shares on page 14. To add a new Wide Area Storage policy, do the following: 1 Select Configuration > Storage policies. 2 Click New... Lattus A X Access Node User s Guide 17

24 Chapter 6: Basic Operations Configuring Wide Area Storage Policies 3 Enter the appropriate values for the following parameters: Policy Class: The name of the new policy you are creating. The policy class name must be unique. You cannot enter the name of an existing policy class. Also, if you use uppercase characters when entering the policy class name, the name will be converted to lowercase characters when the policy class is created. File System: In the File System list, select the WAS file system. Wide Area Storage: In the Wide Area Storage list, click the appropriate Wide Area Storage destination 4 Click Configure... to continue. Entering the Namespace, Source Directories and Advanced Tabs Enter information on the Wide Area Storage Namespace, Source Directories, and Advanced tabs. (See below for more information about the parameters on these tabs.) The Namespace Tab The Namespace tab enables you to select the Wide Area Storage namespace. 18 Lattus A X Access Node User s Guide

25 Chapter 6: Basic Operations Configuring Wide Area Storage Policies Using the Wide Area Storage Namespace list, select the appropriate namespace. The Source Directories Tab The Source Directories tab enables you to select or create the file system directory used for the policy. Lattus A X Access Node User s Guide 19

26 Chapter 6: Basic Operations Configuring Wide Area Storage Policies The Source Directories tab contains the following parameters and buttons: Directory: In the Directory list, click an existing directory you want to use for the policy. Create Directory button: To create a new directory, enter a directory location at the field to the left of this button, and then click Create Directory to create the specified directory. Add button: After either selecting a directory from the Directory list or creating a new directory, click Add to add the directory as the one used by the storage policy. To delete a directory on this tab, select the desired directory from the Source Directories list and then click Delete. Confirm the deletion by answering Yes to the confirmation prompt. 20 Lattus A X Access Node User s Guide

27 Chapter 6: Basic Operations Configuring Wide Area Storage Policies The Advanced Tab The Advanced tab enables you to configure Wide Area Storage, and Truncation parameters for the policy. Caution: Contact Quantum support prior to modifying the default values on the Advanced tab. Wide Area Storage The Advanced tab s Wide Area Storage section contains the following parameters: Minimum File Idle Time before Storing: Specify the interval of time for a file to remain idle before storage begins. This parameter uses the format 00:00:00:00, which refers to days:hours:minutes:seconds. Minimum File Size to Store: Specify the minimum size a file must be in order to be eligible for storage. Segment File: Enter a scaled integer to specify the maximum segment size for objects stored in the Lattus Object Storage. If a file's size is greater than the segment size, it is broken down to multiple segments to be stored. If this is not configured, the whole file is stored as one object in Lattus. Note that limits may be set on the maximum size for an object stored in Lattus. If your file size can be greater than the maximum object size, you need to configure this parameter. Values representing sizes can be postfixed by k, m or g to represent multipliers of 1024, 1024*1024 and 1024*1024*1024. Lattus A X Access Node User s Guide 21

28 Chapter 6: Basic Operations Managing Permissions for NFS and CIFS Shares Filenames Excluded from Storing: Specify any filenames you want excluded from the storage process. Relative Priority: If desired, indicate relative storage priority. Preference is given to files from policies with a lower priority number when the Lattus A10 Access Node considers storage candidates. Truncation The Advanced tab s Truncation section contains the following parameters: Minimum File Idle Time before Truncation: Specify the interval of time for a file to remain idle before truncation begins. Minimum File Size to Truncate: Specify the minimum size a file must be in order to be eligible for truncation. Filenames Excluded from Truncation: Specify any filenames you want excluded from the truncation process. Stub File Size: The stub file is the readable portion of the file that remains after truncation. Enter the desired target size to allocate for the truncated file stub. Finishing the Policy 1 When you are finished entering information about the new policy, click Apply, or click Cancel to exit without saving. 2 After the Status screen informs you that the policy was created successfully, click OK. Managing Permissions for NFS and CIFS Shares There are two options for setting permissions for the Lattus A10 Access Node's CIFS and NFS shares. The details are platform-specific and depend on how you set up your shares. Option 1: Set permissions directly on the Lattus A10 Access Node 22 Lattus A X Access Node User s Guide

29 Chapter 6: Basic Operations Updating Your Centrify Configuration Log in to the Lattus A10 Access Node's CLI (see Logging in to the Lattus A10 Access Node CLI on page 12 for instructions), then use the chmod, chown and chgrp commands to modify your shares' permissions directly on the Lattus A10 Access Node. See the commands' man pages for detailed instructions. Option 2: Set Permissions on the clients Use the standard permissions commands specific to your NFS or CIFS client. Updating Your Centrify Configuration If you're using Active Directory to manage access to CIFS shares on your Lattus system, and you make updates to your Active Directory server's configuration, you need to update your Lattus A10 Access Node's Centrify configuration to ensure that users can still access the shares. To update Centrify after updating the Active Directory server's configuration, log in to the Lattus A10 Access Node's CLI (see Logging in to the Lattus A10 Access Node CLI on page 12 for instructions) run /usr/share/centrifydc/bin/adbindproxy.pl and accept all the default responses. Shutting Down the Lattus A10 Access Node To shut down the Lattus A10 Access Node, do the following: 1 Stop I/O to the Lattus A10 Access Node. 2 Type /sbin/shutdown -h now. Note: The -h means halt and will shut down the system. The Lattus A10 Access Node should shut down gracefully and unmount the file systems. Lattus A X Access Node User s Guide 23

30 Chapter 6: Basic Operations Shutting Down the Lattus A10 Access Node You can specify a delay by replacing the word now with a + and a number. For example, shutdown -h +5 will shut down and halt the system after five minutes have passed. 24 Lattus A X Access Node User s Guide

31 Chapter 7 Monitoring the System From the Lattus A10 Access Node This chapter describes the following topics related to monitoring your Lattus A10 Access Node's status: Monitoring the Connection Between the Lattus A10 Access Node and Lattus C10 Controller Nodes on page 25 Configuring Server Settings on page 27 Configuring Notifications on page 29 Monitoring the Connection Between the Lattus A10 Access Node and Lattus C10 Controller Nodes When you create Storage Policies on the Lattus A10 Access Node, you associate your CIFS and NFS shares with specific namespaces configured on the Lattus Object Storage. If the connection between your Lattus A10 Access Node and the Lattus C10 Controller Nodes is lost, the Lattus A10 Storage Policies will not be able to move the data saved in your CIFS and NFS shares to the Lattus Object Storage. If you receive tickets or notifications related to a lost connection between your Lattus A10 Access Node and the Lattus C10 Controller Nodes, do the following to check the status of the connection: Lattus A X Access Node User s Guide 25

32 Chapter 7: Monitoring the System From the Lattus A10 Access Node Monitoring the Connection Between the Lattus A10 Access Node and Lattus C10 Controller Nodes 1 Log in to the Lattus A10 Access Node's GUI (See Logging in to the Lattus A10 Access Node GUI on page 12). 2 Select Configuration > Storage Destinations. 3 In the Wide Area Storage screen, select the radio button next to the storage destination whose status you wish to view. 4 Click View. 5 In the screen that appears, look at the Status field for the Lattus C10 Controller Nodes' IP addresses. A status of Online (a green icon with a check mark) indicates a good connection between the Lattus A10 Access Node and the Lattus C10 Controller Node. If a status is Offline (a red icon with an x ), there is a problem with the connection between your Lattus A10 Access Node and the Lattus C10 Controller Node. 26 Lattus A X Access Node User s Guide

33 Chapter 7: Monitoring the System From the Lattus A10 Access Node Configuring Server Settings 6 Verify that your network settings are correct and that there isn't a problem with the physical connection between your Lattus A10 Access Node and the rest of the Lattus system. 7 If you can't resolve the problem, contact Quantum Support for assistance. Configuring Server Settings The Server option allows you to specify the server used for processing Lattus A10 Access Node notification messages. On this screen you will enter basic information such as the server name and sending entity. You also have the option of sending a test message so you can verify that Lattus A10 Access Node recognizes the server whose information you entered. Note: The Server option does not configure your server. Instead, it allows you to specify a previously configured server so the Lattus A10 Access Node knows which server is responsible for processing notification messages. Before you use the Server option, make sure your SMTP server is already configured. Lattus A X Access Node User s Guide 27

34 Chapter 7: Monitoring the System From the Lattus A10 Access Node Configuring Server Settings To configure your Lattus A10 Access Node's server settings, do the following: 1 Select Configuration > Server. 2 Complete the following fields related to your system configuration on the Configuration > Server screen. Required fields are marked with an asterisk (*). SMTP Server: Enter the identification for the server that stores and processes your account information. This might be a valid server name or an IP address. Verify SMTP Connectivity: Enable this option if you want Lattus A10 to verify that the SMPT server you entered is valid and reachable. Authentication: If your provider requires a password upon sign on, select the PASSWORD option. Otherwise, select 28 Lattus A X Access Node User s Guide

35 Chapter 7: Monitoring the System From the Lattus A10 Access Node Configuring Notifications NONE. When you select the PASSWORD option, the following fields will appear: Account: Enter a valid account for outgoing messages. Password: Enter the account's sign-on password, if required. Sender Address: Enter the address for the entity responsible for sending alert messages to designated recipients. Send Test Enter an address to which you can send test messages in order to confirm successful configuration. 3 Click Apply to save your changes. Configuring Notifications The Notification feature allows you to specify parties who should receive Lattus A10 Access Node messages about backup statuses, service tickets, admin alerts, and policy class messages. Note: In order for this feature to work properly, make sure you have specified a configured server as described in Configuring Server Settings on page 27. To add an recipient for notifications from the Lattus A10 Access Node, do the following: 1 Select Configuration > Notification. Lattus A X Access Node User s Guide 29

36 Chapter 7: Monitoring the System From the Lattus A10 Access Node Configuring Notifications 2 In the Configuration > Notifications screen, select the Notify Quantum Technical Assistance Center on Service Ticket check box to automatically send the Quantum Technical Assistance Center a message whenever a service ticket is generated. 3 To add other recipients, click New. The Configuration > Notifications > New screen appears. 4 Enter the following fields for the new recipient: Contact Address: Enter the address of the person who should receive notifications. Contact Name: Enter the name of the person who should receive notifications. Admin Alerts: Select this option to send an message to the recipient whenever an admin alert is generated. For more information about Admin Alerts, go to the Lattus A10 Access Node's Online Help and select Service Menu Options > Admin Alerts. 30 Lattus A X Access Node User s Guide

37 Chapter 7: Monitoring the System From the Lattus A10 Access Node Configuring Notifications Lattus A10 Backups: Select this option to send an message to the recipient after a backup has occurred on your system. Service Tickets: Specify the way you want Lattus A10 Access Node to handle notifications whenever a service ticket for your system is generated. Choose one of the following: Disabled: No notification messages are sent for service tickets. Alert Level High: An notification message is sent only when the alert level is High. Alert Level Middle: An notification message is sent when the alert level is Middle and higher. Alert Level Low: An notification message is sent when the alert level is Low and higher. 5 Click Apply to save your changes, or click Cancel to exit without saving. (You can also clear all fields and start over by clicking Reset.) 6 When the confirmation message appears, click Yes to proceed or No to abort. 7 When a message informs you that the notification recipient was successfully added, click OK to return to the Configuration > Notifications screen. Lattus A X Access Node User s Guide 31

38 Chapter 7: Monitoring the System From the Lattus A10 Access Node Configuring Notifications 32 Lattus A X Access Node User s Guide

39 Chapter 8 Configuring NFS and CIFS Clients The following information should be used to configure NAS clients for correct operation and best performance: Configuring Linux NFS Clients on page 33 Configuring Windows CIFS Clients on page 35 Configuring Linux NFS Clients Below are examples of NFS client mount options for connecting to a Lattus A10 system. Note that in this example the clients are mounting the exported directory /stornext/snfs1/nfsshare01. If a different directory is to be mounted, that path should be reflected in the mount options: Here is an example /etc/fstab entry for a Linux NFS client that includes the sync mount option: [Your Lattus A10 hostname or IP Address]:/stornext/ snfs1/nfsshare01 /nfs/stornext/snfs1/nfsshare01 nfs tcp,vers=3, wsize= ,rsize= ,sync 0 0 Lattus A X Access Node User s Guide 33

40 Chapter 8: Configuring NFS and CIFS Clients Configuring Linux NFS Clients Here is an example /etc/vfstab entry for a Solaris NFS client that includes the forcedirectio mount option: [Your Lattus A10 hostname or IP Address]:/stornext/ snfs1/nfsshare01 - /nfs/stornext/snfs1/nfsshare01 nfs 0 yes proto=tcp,vers=3,wsize= ,rsize= ,forcedirec tio Once the fstab/vfstab has been updated, run the following commands to mount the share. mkdir -p /nfs/stornext/snfs1/nfsshare01 mount /nfs/stornext/snfs1/nfsshare01 If you receive errors when trying to mount NFS shares, double-check the entry in the fstab/vfstab file to ensure that the IP address, path, and arguments are correct. Notes on mount options: NFS version 3 should be specified as well as TCP. In addition, the read and write maximum request sizes should be set to 1MB. And, for best performance, the sync (Linux and most Unix versions) or forcedirectio (Solaris) options should be used, provided that the ingest application generally does I/O in a block size that is a multiple of 1MB (although occasional non-compliant writes such as when ingesting the tail end of a file will not significantly affect performance). If the primary ingest applications perform writes in chunks smaller than 64K and cannot be modified, the sync and forcedirectio options should not be used. The Linux and Solaris cp commands will both perform compliant writes by default when operating on a StorNext file system over NFS. Other programs might need to run with special options. For example, the UNIX tar command should be run with -b Commands such as strace (Linux) and truss (Solaris) can be run against the ingest application to determine the size of writes being performed. Note: The use of NFS clients running RHEL4 or earlier, SLES9 or earlier, and Solaris-9 or earlier is not recommended. 34 Lattus A X Access Node User s Guide

41 Chapter 8: Configuring NFS and CIFS Clients Configuring Windows CIFS Clients Configuring Windows CIFS Clients To map CIFS shares to a Windows client, do the following: 1 Open Windows Explorer and select Computer. 2 Select Map Network Drive at the top of the window. 3 Select a drive letter, and enter the Lattus A10 share path under the Folder text box. 4 Select Finish to map the drive. Note: Windows clients running Windows 7 or Windows 2008 R2 or newer and having fast (10 GbE) connectivity should make the following registry adjustment for best performance: 1 In the registry, under HKLM\System\CurrentControlSet\Services\LanmanWorkstation\P arameters, create a DWORD named DisableLargeMtu. 2 Set the value to 0. 3 Restart the computer. If you receive errors when trying to mount CIFS shares, check the following on the Lattus A10 Access Node: Verify that the settings in the smb.conf file (/etc/samba/ smb.conf) are correct. Verify that the Samba services are running. Lattus A X Access Node User s Guide 35

42 Chapter 8: Configuring NFS and CIFS Clients Configuring Windows CIFS Clients 36 Lattus A X Access Node User s Guide

43 Chapter 9 Troubleshooting This chapter describes the following troubleshooting tasks: Monitoring LEDs on the Lattus A10 Access Node Hardware on page 37 Monitoring the Lattus A10 Access Node for Alerts on page 40 Monitoring the Lattus A10 Access Node for Tickets on page 42 Monitoring LEDs on the Lattus A10 Access Node Hardware The following graphics show the LEDs on the Lattus A10 hardware that can help you monitor the node's status. Lattus A X Access Node User s Guide 37

44 Chapter 9: Troubleshooting Monitoring LEDs on the Lattus A10 Access Node Hardware Monitoring LEDs on the Front of the Lattus A10 Access Node Power-on Indicator: The power-on indicator lights when the system power is on. The power button controls the DC power supply output to the system. Hard Drive Activity Indicators: Lights when the hard drive is being accessed Hard Drive Status Indicators: Blinks green two times per second = Identifying drive/ preparing for removal Off = Drive ready for insertion or removal. When system power is applied, the drive status indicator remains off until all hard drives are initialized. Drives are not ready for insertion or removal during this time. Blinks green, amber, and off = Drive-predicted failure Blinks amber four times per second = Drive failed Blinks green slowly = Drive rebuilding Steady green = Drive online 38 Lattus A X Access Node User s Guide

45 Chapter 9: Troubleshooting Monitoring LEDs on the Lattus A10 Access Node Hardware Monitoring LEDs on the Rear of the Lattus A10 Access Node Power Indicators (handles): Each power supply has an illuminated translucent handle that serves as an indicator to show whether power is present or whether a power fault has occurred. Each of the power indicator's states are listed below with an explanation of what each one indicates: Not lit = Power is not connected Green = A valid power source is connected to the power supply and the power supply is operational Flashing amber = Indicates a problem with the power supply Flashing green = When hot-adding a power supply, this indicates that the power supply is mismatched with the other power supply (in terms of efficiency, feature set, health status, and supported voltage). Replace the power supply that has the flashing indicator with a power supply that matches the capacity of the other installed power supply. Lattus A X Access Node User s Guide 39

46 Chapter 9: Troubleshooting Monitoring the Lattus A10 Access Node for Alerts Caution: When correcting a power supply mismatch, replace only the power supply with the flashing indicator. Swapping the opposite power supply to make a matched pair can result in an error condition and unexpected system shutdown. To change from a High Output configuration to a Low Output configuration or vice versa, you must power down the system. AC power supplies support both 220 V and 110 V input voltages. When two identical power supplies receive different input voltages, they can output different wattages, and trigger a mismatch. Hard Drive Activity and Status Indicators: (See information for these LEDs in the section Hard Drive Status Indicators: on page 38.) NIC Link and Activity Indicators: Link and activity indicators are off = The NIC is not connected to the network Link indicator is green = The NIC is connected to a valid network link at 1000 Mbps Link indicator is amber = The NIC is connected to a valid network link at 10/100 Mbps Activity indicator is blinking green = Network data is being sent or received Monitoring the Lattus A10 Access Node for Alerts Admin alerts are informational messages about system activities you might want to be aware of, but are not necessarily an error condition. For example, issues related to the Distributed Data Mover feature generate admin alerts. Admin alerts typically do not require any action from Lattus A10 users. The Service > Admin Alerts screen provides the following information: 40 Lattus A X Access Node User s Guide

47 Chapter 9: Troubleshooting Monitoring the Lattus A10 Access Node for Alerts Alert ID: The unique identifier for the alert Date: The date the alert was generated Request ID: The unique Lattus A10 identifier which generated the alert Identifier: The specific Lattus A10 software component which generated the alert Detail: A description of the alert To view admin alerts, select Service > Admin Alerts. The Admin Alerts screen appears. On the Admin Alerts screen you can do any of the following: View a specific alert by scrolling to the right of the screen (if the alert is longer than can be displayed on one screen) Refresh (update) the list by clicking the Refresh button Delete an individual alert by selecting the desired alert and then clicking the Delete button Delete all alerts by clicking the Delete All button Lattus A X Access Node User s Guide 41

48 Chapter 9: Troubleshooting Monitoring the Lattus A10 Access Node for Tickets Monitoring the Lattus A10 Access Node for Tickets The Service menu's Tickets option allows you to view a list of RAS tickets that relate to system faults or errors. Ticket details provide a summary of the system fault, an area for Analysis notes, and contains a Recommended Actions link to help you correct the fault. On this screen you can view the ticket number, current status, priority, date and time the ticket was last updated, and a brief summary of the error condition. By default, tickets are listed with the most recently opened tickets displayed first. If desired, you can click the column headers to change the sorting. For example, click the Ticket heading to display tickets in ascending or descending numerical order. See the sections below for details on the following: Viewing Ticket Information on page 42 Editing Ticket Information on page 45 Closing Tickets on page 46 Viewing Ticket Information 1 From the Lattus A10 Access Node home page, choose Service > Tickets. The Tickets screen appears. 42 Lattus A X Access Node User s Guide

49 Chapter 9: Troubleshooting Monitoring the Lattus A10 Access Node for Tickets The Tickets screen provides the following information: Ticket: The RAS ticket number, displayed in the order in which it was created Status: The ticket's current status: OPEN or CLOSED Priority: The ticket's priority based on system impact: HIGH, MEDIUM, or LOW Last Update: The date of the last system status update Summary: A short summary of the fault that triggered creating the RAS ticket 2 If desired, change the display by choosing Show All Tickets, Show Closed Tickets, or Show Open Tickets in the dropdown list at the bottom of the screen. 3 Highlight the ticket you wish to view, and then click View. The Service > Tickets > View Ticket > [number] screen appears. Lattus A X Access Node User s Guide 43

50 Chapter 9: Troubleshooting Monitoring the Lattus A10 Access Node for Tickets This screen provides the following information: Ticket Number: The number of the ticket in the displayed ticket list Date Opened: The date and time the ticket was created Status: The current status of the ticket: OPEN or CLOSED Priority: The ticket's priority based on system impact: HIGH, MEDIUM, and LOW Summary: A brief description of the ticket. Event Details: Detailed information about event that triggered the ticket, including a link that allows you to View Recommended Actions which will help you correct the fault or condition Analysis: Any user-entered comments pertaining to the fault or condition, such as a recommended action 4 To see recommended actions for the ticket, click the View Recommended Actions link. The Recommended Actions screen appears provides information and steps to correct the condition or fault that generated the RAS ticket. Follow the instructions on the screen to correct the condition or fault. When you are finished viewing the recommended actions, close the window. 5 When you are finished viewing ticket information, click Done to return to the Service > Tickets screen. 44 Lattus A X Access Node User s Guide

51 Chapter 9: Troubleshooting Monitoring the Lattus A10 Access Node for Tickets Editing Ticket Information Follow this procedure to add comments or notes to the ticket in the Analysis field: 1 Select the desired ticket and then click Edit. The Edit Ticket > [number] screen appears. 2 Make your comments or notes in the Analysis field. 3 Click Apply to save your changes. When you are ready to return to the previous screen, click Close. (To return to the previous screen without saving your changes, click Cancel.) Lattus A X Access Node User s Guide 45

52 Chapter 9: Troubleshooting Monitoring the Lattus A10 Access Node for Tickets Closing Tickets When you no longer need to retain ticket information, you can close (delete) selected tickets or all tickets by following this procedure: 1 To close a specific ticket, select the desired ticket and then click Close. 2 To delete all tickets, click Close All. 46 Lattus A X Access Node User s Guide

53 Chapter 10 Getting Help This chapter describes the following tasks: Locating the System Serial Number on page 47 Contacting Quantum Support on page 49 Locating the System Serial Number You will need to provide your system serial number for technical support. Lattus system serial numbers begin with the characters CX and contain the characters CKC in the number - for example, CX1234CKC Here's how to find it: From the Lattus A10 Access Node GUI: You can find the serial number in the Lattus A10 Access Node GUI in the following three places: Along the top of the GUI In the Configuration > Licenses screen In the Help > About screen Lattus A X Access Node User s Guide 47

54 Chapter 10: Getting Help Locating the System Serial Number On the Lattus A10 Access Node(s): The presence of a printed serial number on your Lattus A10 Access Node hardware will depend on whether or not the Lattus A10 Access Node was purchased with the rest of your Lattus system. If you purchased one or more Lattus A10 Access Nodes separately from your Lattus system (e.g., to provide NAS file access in a Lattus-M system): The system serial number will NOT be printed on the Service Tag. You will need to access the system serial number from the Lattus A10 Access Node GUI, the Lattus CMC, or from the serial number sticker on one of your Lattus C10 Controller Nodes (see the Lattus User's Guide for details). If you purchased the Lattus A10 Access Node with the rest of your Lattus system: The system serial number will be printed on the Service Tag. To locate it, do the following: 1 From front of the Lattus A10 Access Node, pull out the Service Tag. 2 The system serial number (SYSTEM SN) is printed on the white sticker. 48 Lattus A X Access Node User s Guide

55 Chapter 10: Getting Help Contacting Quantum Support Lattus A10 Access Node Contacting Quantum Support You can contact Quantum Support in two ways: Access the Online Service Center by opening an Online Service Request at jtflogin.jsp Call Tech Support. You can find a list of contact numbers for Tech Support at: ProductSelect/Index.aspx Lattus A X Access Node User s Guide 49

56 Chapter 10: Getting Help Contacting Quantum Support 50 Lattus A X Access Node User s Guide