Blue Arc Titan SiliconServer System Administration Manual

Table of Contents

Quick Links

Download this manual

Titan SiliconServer

System Administration Manual

Table of Contents

Summary of Contents for Blue Arc Titan SiliconServer

Page 1 Titan SiliconServer System Administration Manual...
Page 2 Publication Title Titan SiliconServer - System Administration Manual Publication Date February 2006 Neither BlueArc Corporation nor its affiliated companies (collectively, “BlueArc”) makes any warranties about the information in this guide. Under no circumstances shall BlueArc be liable for costs arising from the...
Page 3 Other Related Documents The documents, which are listed below, provide a full specification on how to configure and administer the storage enclosures in the Titan subsystem. Hardware Guide: This guide (in PDF format) provides an overview of the hardware, ❑ describes how to resolve any problems, and shows how to replace faulty components.
Page 4: About This Guide
Sun Microsystems Java Runtime Environment: Version 5.0, update 6, or later. ❑ A copy of all product documentation is included for download or viewing through the Web UI. The following software is required to view this documentation: Adobe Acrobat: Version 7.0.5 or later. ❑ Titan SiliconServer...
Page 5: Table Of Contents
Configuring the Titan SiliconServer ........
Page 6 Managing System Drives ..........133 Titan SiliconServer...
Page 7 Table of Contents Creating System Drives ........... 133 Viewing System Drives .
Page 8 The Titan SiliconServer and CIFS ........
Page 9 Table of Contents Quick Snapshot Restore ........... 303 Snapshot Rules .
Page 10 Titan SiliconServer Statistics ........
Page 11 Shutting Down / Resetting the Titan SiliconServer ....... . 472...
Page 12 Table of Contents Titan SiliconServer...
Page 13: Chapter 1. The Bluearc Storage System
The BlueArc Storage System is a highly scalable and modular Network Attached Storage (NAS) server with multi-gigabit throughput from network to disk. The Titan SiliconServer has a patented architecture structured around bi-directional data pipelines and a hardware-based file system. This allows the storage capacity to scale to 256 Terabytes, and sustain higher access loads without compromising performance.
Page 14: The Titan Siliconserver
The Titan SiliconServer chassis is 4U (7”) high, 48.3 cm (19”) rack mountable and a maximum of 63.5 cm (25”) deep, excluding the fascia. It consists of a passive backplane (that is not removable), three hot swappable fan trays and two hot swappable redundant power supplies.
Page 15: Enterprise Virtual Servers
All file services are provided by logical server entities referred to as Enterprise Virtual Servers (EVS). A Titan SiliconServer or High Availability (HA) cluster supports up to eight EVS. Each EVS is assigned unique network settings and storage resources. In a cluster, EVS are automatically migrated between servers when faults occur to ensure maximum availability.
Page 16: The System Management Unit (Smu)
Titan cluster. Although the SMU is an integral component of the BlueArc Storage System, it is not involved in any data movement between the network client and Titan. All network clients communicate directly with the Titan SiliconServer. The Private Management Network Titan operates in conjunction with a number of auxiliary devices such as RAID storage subsystems, Fibre Channel switches, and UPS units.
Page 17 Storage System Overview structure is divided into two discrete components: A public data network (i.e. the enterprise network). The public management interface ❑ from the BlueArc Storage System perspective consists of the first Ethernet port on the SMU (the public Ethernet interface). In addition, management access can be enabled on individual Gigabit Ethernet (GE) interfaces on Titan.
Page 18: Titan Siliconserver Initial Setup
❑ Perform the initial configuration of the Titan SiliconServer using the serial interface. When Titan is first installed, it requires the following configuration settings: An admin name. This is the server name. It should be unique as it will be used ❑...
Page 19: Managing The Titan Siliconserver
Managing the Titan SiliconServer Enter License Key(s) for the server. Run the SiliconServer Setup Wizard. Complete Titan setup: Network interface ❑ Storage management ❑ File services ❑ Data protection ❑ Optionally, configure Titan as part of a high availability cluster.
Page 20 Note: BlueArc recommends that this password be changed as soon as possible. Once the login procedure is completed, the Web Manager home page is displayed. Titan SiliconServer...
Page 21 Managing the Titan SiliconServer Using the Server Status Console Summary Status information pertaining to the currently managed server can be viewed from the Web Manager’s server console, in Titan SiliconServer’s home page. System Administration Manual...
Page 22 Routes, Link Aggregation, etc. Additional categories: • SMU Administration – used to manage the SMU itself (currently managed server selection, security, private management network, etc.). • Online Documentation – used to access documentation (like this manual) from the SMU. Titan SiliconServer...
Page 23 Managing the Titan SiliconServer Clicking on any of the shortcuts, such as Silicon File Systems and NFS Exports, starts the desired function. Clicking on the page categories loads a page, such as the Data Protection page shown below: System Administration Manual...
Page 24 The BlueArc Storage System Understanding Web Manager Tables Some of the pages in the Web Manager interface include tables, such as the one shown below. Titan SiliconServer...
Page 25: Using The Command Line Interface
Managing the Titan SiliconServer Using the Command Line Interface The Titan SiliconServer and the System Management Unit (SMU) each have a command line interface (CLI) used for configuration and management. Both support secure connections, configurable passwords, and other security mechanisms.
Page 26 Titan SiliconServer Command Line Reference. The Titan CLI can be accessed in the following ways: • Using Secure Shell (SSH) to connect into the Titan SiliconServer through the SMU. • Using SSH or Telnet to directly connect into the Titan SiliconServer.
Page 27 A connection to Titan’s Command Line Interface will be automatically initiated. To connect using SSH or Telnet When connecting to a Titan SiliconServer through SSH or Telnet, use the server’s administration name or IP address, and log in using the supervisor user account. Titan must be configured to accept SSH or Telnet connections over its Ethernet interfaces.
Page 28: Using The Embedded Web Ui
Using the Embedded Web UI Each Titan SiliconServer incorporates an embedded Web management tool. Although this is not the primary management interface for Titan, this tool can be used as an alternative to Web Manager, or if the SMU is offline.
Page 29: Chapter 2. System Configuration
Configuring the System Management Unit (SMU) System Configuration System Configuration Overview This section describes how to configure the BlueArc Storage System, during or after installation. It includes setup instructions for the System Management Unit (SMU), for the Titan SiliconServer, and the private management network. Network configuration (including IP address selection), storage management, file services, data protection, and clustering are discussed in separate sections.
Page 30: Using The Smu Setup Wizard
SMTP Relay Enter the host name (not the IP address) of the email server to which the SMU can send event notification emails. Date & Time Set the clock on the SMU and select one or more NTP servers. Titan SiliconServer...
Page 31: Configuring Security Options
Configuring the System Management Unit (SMU) Private management Configure the private management network. network When the wizard is complete a page will be displayed showing the details entered. To complete the setup, click finish, and then click OK to reboot. Configuring Security Options The SMU can be configured to control which hosts have access to it, as well as other auxiliary devices managed by the SMU.
Page 32: Smtp Relay Configuration
System Configuration SMTP Relay Configuration The SMU can be configured to forward emails from Titan SiliconServers and auxiliary devices on private management network to the public network. Titan SiliconServer...
Page 33: Selecting Managed Servers
Configuring the System Management Unit (SMU) From the SMU Administration page, click SMTP Configuration. The following screen will be displayed: Enter the host name of an SMTP Server on the public network. The SMU will then relay e-mails from the Titan servers on the private network to the public network. Ensure that the SMTP server on Titan’s Email Alert Configuration page is set to be the SMU’s eth1 IP address.
Page 34 Amber is displaying a warning (e.g. operating normally, however, action should be taken to maintain normal operation) Red indicates a critical condition (e.g. the server is no longer functioning). Details A link to a page displaying detailed information used to contact or to manage the server. Titan SiliconServer...
Page 35 Configuring the System Management Unit (SMU) Set as Current Select the server as the currently managed server. In the Actions frame it is possible to add or remove managed servers from the displayed list. To remove one or more servers, make a selection by putting a tick in the appropriate checkbox, or click check all to remove all servers.
Page 36: User Management
Management roles are controlled by the SMU. The information relating to administrative accounts like name, password, role or server list is maintained in the SMU's configuration database. Administrative Functions The following table shows the Web Manager functions for the different administrative roles listed Titan SiliconServer...
Page 37 Configuring the System Management Unit (SMU) for each type of user. The information contained in this table also shows a list of the SMU functions that are available to each user. Only the Web Manager menu pages for which access is allowed will be displayed for each administrator.
Page 38 Storage Management Silicon File Server Management Silicon File Systems Storage Pools Virtual Volumes & Quotas Quotes by File System File System Relocation Policy Based Data Migration Data Migration Data Migration Rules Data Migration Paths Complete Data Migrations Storage Graphics Titan SiliconServer...
Page 39 Configuring the System Management Unit (SMU) Data Protection Data Protection Virus Scanning Virus Statistics Replication Snapshots Snapshot Rules NDMP Configuration File Services Network Configuration SMU Administration Managed Servers Managed SiliconServers Management Network Management Access Documentation Access Notes: (1) Access is limited to relevant servers. (2) Cannot create/expand a File System.
Page 40 Description User Name Administrator’s user name. User Level Displays the user level or type of administrative role. Can Manage Storage Displays if the user Can Manage Storage systems. Advanced Displays if Advanced functions are available to this user. Titan SiliconServer...
Page 41 Configuring the System Management Unit (SMU) To Edit a SMU User’s Information From the Home page, click SMU Administration. Then, click SMU Users. Next, click details next to the desired SMU user. From the SMU User Details Screen: Click change. Change the SMU user’s password or role.
Page 42 Click the "Add" button. The following page is displayed. Enter a User Name for this SMU User. Enter a Password for this SMU User, and confirm the password. Click the Global Administrator option. Click next to continue. The following screen is displayed. Titan SiliconServer...
Page 43 Configuring the System Management Unit (SMU) This page displays the new SMU user’s profile. Click the Advanced Mode checkbox if this SMU user needs to have access to the advanced functions. Click next to continue. The following confirmation screen is displayed. Verify that the New SMU User’s profile is correct and click finish to apply your changes.
Page 44 To add an SMU User - Storage Administrator, follow these steps: Click the Add button. The following page is displayed. Enter a User Name for this SMU User. Enter a Password for this SMU User, and confirm the password. Click the Storage Administrator option. Titan SiliconServer...
Page 45 Configuring the System Management Unit (SMU) Click next to continue. The following screen is displayed. Highlight the servers that this SMU User has rights and privileges to manage from the Available Servers list and move them to the Selected Servers list. Click next to continue.
Page 46 Click the Add button. The following page is displayed. Enter a User Name for this SMU User. Enter a Password for this SMU User, and confirm the password. Click the Server Administrator option. Click next to continue. The following screen is displayed. Titan SiliconServer...
Page 47 Configuring the System Management Unit (SMU) Highlight the servers that this SMU User has rights and privileges to manage from the Available Servers list and move them to the Selected Servers list. Click the Can Manage Storage checkbox for users who have the necessary right and privileges to manage storage devices on the network.
Page 48: Configuring The Management Network
RAID storage subsystems, Fibre Channel switches, and power management units. Most of these devices are managed through Ethernet. In order to minimize the impact on an enterprise network, the Titan SiliconServer’s physical management structure is divided into two distinct components: A private (sideband) management network.
Page 49 Configuring the Management Network There are significant advantages to having a private management network: • Network traffic required for normal SMU monitoring of Titan and auxiliary devices will not be on the enterprise network. • Devices on the private management network will not take up valuable IP addresses on the enterprise network.
Page 50: Configuring The Management Network
IP address is 192.0.2.1 then the devices on the private management network must have addresses in the range of 192.0.2.2 – 192.0.2.254 in order to work on the private management network. Configuring the Management Network From the SMU Administration page, click Management Network. Titan SiliconServer...
Page 51 Configuring the Management Network The Management Network page configures the private management network on the SMU’s eth1 interface. An address of 192.0.2.1 will be suggested. This address will not be seen on the enterprise network, but must fall in a distinctly different range to the SMU's public address (i.e. the address on eth0).
Page 52: Configuring Devices On The System Monitor
Titan This component provides multiple Loads the Server Status page. SiliconServer Gigabit Ethernet interfaces to the network and multiple Fibre Channel interfaces to the main enclosure. In high availability configurations, there are two servers. Titan SiliconServer...
Page 53 Configuring the Management Network Main Enclosure An FC-14, SA-14, or FC-16 main Loads the Loads the enclosure contains disk slots, dual enclosure status System Drives power supplies, and dual RAID page. page. controllers. Expansion An FC-14, SA-14, or FC-16 expansion Loads the Loads the Enclosure...
Page 54 SNMP traps from the device. The SMU will periodically check if the device is still active and connected to the Titan SiliconServer. If a device is no longer responding to network “pings”, the device’s color will change to red and an alert will be issued.
Page 55 Email alert may be generated depending on how event logging and notification is configured for the Titan SiliconServer. Note: The SMU can also be configured to listen for SNMP Traps from supported storage devices. For more...
Page 56 Note: BlueArc recommends adding the SMU’s eth1 IP to the device’s list of servers. Also, if the device supports email notification, and if email forwarding is configured on the SMU, the SMU’s eth1 IP can also be configured as the device’s mail server. Titan SiliconServer...
Page 57: Configuring A System Power Unit
Configuring the Management Network Receiving SNMP Traps through the SMU SNMP traps are alert messages sent by storage devices on the network. These traps provide information about failures or other conditions on those devices. Set the SMU’s eth1 IP address as the receiving target for SNMP traps sent by managed devices on the private management network.
Page 58 Enter the authentication phrase for the UPS. Confirm the authentication phrase. Check the Enable SNMP Traps box if the Titan SiliconServer is to receive traps from the UPS. The UPS must also be configured to send SNMP traps to the Titan SiliconServer.
Page 59: Configuring The Titan Siliconserver
Click Apply. Configuring the Titan SiliconServer The Titan SiliconServer is at the heart of the BlueArc Storage System. Titan requires a number of configuration settings, such as system name, date and time, etc. License keys also need to be installed for the protocols and services purchased with the Titan SiliconServer.
Page 60 If the SMU is already managing other Titan SiliconServers and the selected server is being added to an existing server farm, an expanded list of settings can be cloned to the new server. Proceed Cloning from another Titan SiliconServer for more information about cloning settings from another server.
Page 61 Configuring the Titan SiliconServer Cloning from the SMU Check or uncheck the boxes next to configuration items to determine whether these settings will be cloned. The following is a list of configuration items that can be cloned from the SMU: •...
Page 62 System Configuration Cloning from another Titan SiliconServer Check or uncheck the boxes next to items to determine whether these settings will be cloned. The following is a list of configuration items that can be cloned from another Titan: • Time •...
Page 63: Screen Description
Configuring the Titan SiliconServer Proceed with the SiliconServer Setup Wizard to complete the setup of the following settings on Titan: Screen Description Password Configure a custom password to secure access to Titan’s management functions. Server Identification Set the system name and other identifying information used protocols such as SNMP and SMTP (email).
Page 64: Configuring Server Identification
SNMP and SMTP (email). To configure the server identification: From the SiliconServer Admin page, click Server Identification. Enter the details that will identify the server: Server Name, Description, Company Name, Department, Location, and Contacts 1 and 2. When all fields have been completed, click apply. Titan SiliconServer...
Page 65: Configuring Date And Time
Configuring the Titan SiliconServer Note: If Titan is configured for Microsoft Windows networking, then the value used for Description will also serve as the server’s comment for all configured CIFS names. Configuring Date and Time Titan’s current date, time, and time zone can be configured. The NTP Server from which Titan may synchronize its time can also be configured.
Page 66 NTP servers and use the results to set the most accurate time. Note: If the server is setup on the private management network, the SMU’s eth1 IP address should be added to the list of NTP servers. Titan SiliconServer...
Page 67 Configuring the Titan SiliconServer Using the SMU for NTP The SMU is configured as an NTP server so that every device on the private management network can be configured to synchronize with at least one NTP server. The SMU itself can synchronize with an NTP server on the public network.
Page 68: Controlling Direct Server Access
System Configuration Controlling Direct Server Access The Titan SiliconServer is primarily managed using Web Manager. In certain circumstances, however, it can also be managed directly through the following mechanisms: command line interface (CLI), accessible through SSH and Telnet. ❑ The SSC utility, available for both Windows and Linux/Unix.
Page 69 Configuring the Titan SiliconServer To configure server access From the Home page, click SiliconServer Admin. Then, click one of the items in the Management Access section, i.e. Telnet, SSC, or SNMP. For each facility used to manage the system, do one or more of the following:...
Page 70: About License Keys
System Configuration About License Keys License keys add powerful services to the Titan SiliconServer and can be purchased and added whenever needed. A BlueArc License Certificate identifies all of the purchased services and should be kept in a safe place. The License Certificate is included in the User Documentation Wallet that was shipped with the system.
Page 71: Using License Keys
Configuring the Titan SiliconServer Expiration of License Keys Licensed features that have been purchased from BlueArc have no expiration date. License keys may be obtained from BlueArc that enable features for use on a trial basis. When used for the purpose of a trial, the features will have a predefined expiration date.
Page 72 Click on the SiliconServer Admin heading to view the SiliconServer Admin page. From the Maintenance Tasks heading, click on License Keys to view the License Key page. From the scroll box at the top of the page, select a key. Click the Delete Key button to delete the key. Titan SiliconServer...
Page 73: Chapter 3. Network Configuration
RJ-45 ports. These four ports are internally wired to a 10/100 Ethernet switch, which is embedded inside the server unit. Gigabit Ethernet Data Interfaces Gigabit Ethernet data interfaces are used by network clients to access the Titan SiliconServer. System Administration Manual...
Page 74 Note: Titan supports Link Aggregation Control Protocol (LACP). LACP is used to automatically configure link aggregation settings defined for Titan on the switch to which it is connected. To use LACP, the switch to which the Titan GE interfaces are connected must also support LACP. Titan SiliconServer...
Page 75: Jumbo Frames
The configured equipment offers a MTU maximum of 9000 bytes. All the GE interfaces of a Titan SiliconServer support jumbo frames. • Jumbo frames are received unconditionally on all GE interfaces without any configuration changes.
Page 76: Network Statistics
Aggregated GE ports share a single MAC address and a single set of IP addresses. GE ports can be aggregated in arbitrary sets for all ports in a trunk. The Titan SiliconServer is initially configured with a single port aggregation containing GE port 1.
Page 77 Configuring the Gigabit Ethernet Interfaces Item/Field Description Name Name of the aggregation (ag1, ag2, ag3, ag4, ag5, ag6). Type Configuration Type of the aggregation: • Static: the switch to which the aggregated links are connected must be configured to match the link aggregation settings defined on the Titan.
Page 78 Click Apply. To View/Modify Configured Aggregations Select the aggregation from the list. Click Modify. Select the GE interfaces that should function as a part of the aggregation. If supported by the Ethernet switch, check Enable LACP. Click Apply. Titan SiliconServer...
Page 79 Configuring the Gigabit Ethernet Interfaces To Delete an Aggregation Select the aggregation from the list. Click Delete. Note: In order to delete a link aggregation group, all IP addresses and GE ports associated with the LAG must first be removed. To View an Aggregation’s Status From the Network Configuration page, click Link Aggregation Status.
Page 80: Ip Network Setup
Network Configuration IP Network Setup Titan SiliconServer IP addresses are assigned to various interfaces and used for the following purpose: • File services (CIFS, NFS, FTP, and iSCSI). IP addresses used to access file services using GE aggregations are assigned to an Enterprise Virtual Server (EVS).
Page 81 Configuring the Gigabit Ethernet Interfaces Item/Field Description IP Address The IP Address of the services or Cluster Node. Subnet Mask The subnet mask of the services or Cluster Node. One of the following: • The label of the Enterprise Virtual Server on which the File Services IP is bound.
Page 82 When the EVS is disabled the IP address assigned to the EVS may be deleted. Once the IP address has been removed, the EVS should be enabled. Disable the EVS From the SiliconServer Admin page, click EVS Management. Select the EVS to which the IP is assigned. Click Disable EVS. Titan SiliconServer...
Page 83 Configuring the Gigabit Ethernet Interfaces Delete the IP Address From the Network Configuration page, click IP Addresses. Select the IP Address to delete. Click delete. Enable the EVS From the SiliconServer Admin page, click EVS Management. Select the EVS that needs to be reactivated. Click Enable EVS.
Page 84 (GEs) it uses) will revert to the defaults as defined by the Global Settings. The Restore default settings button may be used to restore the default settings in the Global Settings box. After completing the IP network settings, follow the instructions to reset the server if instructed. Titan SiliconServer...
Page 85: Ip Routes
IP Routes IP Routes Titan can be configured to route IP traffic in three different ways: through Static Routes, Default Gateways, and Dynamic Routes. The illustration below shows how a Titan may be configured to communicate with various IP networks through routes. The following sections discuss Static Routes, Default Gateways, and Dynamic Host Routes in more detail.
Page 86: Default Gateways
Therefore, if Titan finds a host route for the outgoing IP packet, it will choose that route over a network route or gateway. Similarly, when a host route is not available, Titan will choose a corresponding network route or, in the absence of host and network routes, Titan will send the packet to a default gateway. Titan SiliconServer...
Page 87: Managing The Server's Route Table
IP Routes Managing the Server’s Route Table The routing table on the IP Routes page displays all the routes configured on the server. Any additions or modifications to the routes can be made on this page. To View/Modify the Route Table From the Network Configuration page, click IP Routes.
Page 88: Configuring Name Services
Click Flush to flush the cache immediately. Configuring Name Services The Titan SiliconServer supports standard name services. Name services are used to convert server or host names into IP addresses. In addition to the Domain Name System (DNS), Titan supports WINS (used by CIFS clients) and NIS (used by NFS clients).
Page 89 Configuring Name Services In addition to name services, NIS provides the following functionality: • Administering the names and IDs of UNIX users and groups if CIFS and NFS clients are accessing Titan. • Authenticating users. From the Network Configuration page, click Name Services. Item/Field Description DNS Servers...
Page 90 Name Services Order configuration page. Changing the Name Service Order From the Network Configuration page, click Name Services Ordering. The Name Services Ordering page displays a list of Available Name Services and the Selected Name Services in separate boxes. Titan SiliconServer...
Page 91 Configuring Name Services Select a Name Service that you wish to use from the Available Name Services box and move it to the Selected Name Services box using the right arrow button. If necessary repeat Step 2 for all the Name Services that should be used. Change the order that the system will use for the Name Services by selecting a service in the Selected Name Services box and clicking the Up or Down buttons.
Page 92: Configuring Network Information Services
Note: LDAP cannot be used to resolve NIS Netgroups. If Netgroups are required, local Netgroups must be used. The next section discusses how to enable and configure NIS and LDAP services using the Web Manager. Titan SiliconServer...
Page 93 Configuring Name Services Enabling Network Information Services After deciding which network information service to use, enable the service using the following instructions. From the Network Configuration page, click NIS/LDAP Configuration. The following screen is displayed: • Enable NIS - click this link to enable NIS. •...
Page 94 Item/Field Description Domain The name of the NIS Domain for which the system is a client. Rebind The frequency with which Titan attempts to connect to its configured NIS servers. Enter a value from 1 to 15 minutes. Titan SiliconServer...
Page 95 Configuring Name Services Timeout The period of time for a response from an NIS server when checking the Domain for servers. Enter a value from 100 to 10000 milliseconds. The default value is 300 milliseconds. Broadcast For This option allows Titan to discover available NIS servers on the network. Servers Servers must be in the same NIS domain and be present on the same network as Titan in order to be found.
Page 96: Configuring Nis Servers
A list of the servers to which the Titan may be bound can be specified. This list can contain a maximum of 16 NIS servers. To add server by IP Address From the Home page, click Network Configuration-> NIS Configuration. Titan SiliconServer...
Page 97 Configuring Name Services Click the add button. The following screen is displayed. Enter the IP address of the NIS server in the Server IP Address field. In the Priority field, assign a priority level from the drop-down list. The lowest value is the highest priority level.
Page 98 From the Home page, click Network Configuration-> NIS Configuration. Click details button next to the server. The following screen is displayed. Change the priority of a configured NIS server by selecting one of the available options listed in the drop down box. Click OK to continue. Titan SiliconServer...
Page 99: Configuring Ldap Settings
Configuring Name Services Configuring LDAP Settings If LDAP has been selected to provide Network Information Services, then from the Network Configuration page, click NIS/LDAP Configuration. From this screen you can perform the following tasks: • switch between NIS and LDAP configurations •...
Page 100 To make changes to the LDAP configuration, click modify. The following screen is displayed. Administrators can use this screen to directly manage LDAP configuration for specific users. Note: This option supports both registered and anonymous login of users. Titan SiliconServer...
Page 101 Configuring Name Services Change or modify the Domain Name. ❑ Change or modify the User Name. ❑ Enter the Password. ❑ Specify if TLS is Enabled/Disabled. ❑ Click OK to continue. ❑ System Administration Manual...
Page 102 Network Configuration Modifying the LDAP Server To modify the LDAP server, select Network Configuration->NIS Configuration->Modify LDAP Server. The following screen is displayed. Modify or change Port entry. Modify or change TLS Port entry. Click OK to continue. Titan SiliconServer...
Page 103: Chapter 4. Multi-Tiered Storage
Multi-Tiered Storage Multi-Tiered Storage Overview and Concepts Configuring the Multi-Tiered Storage (MTS) of the Titan SiliconServer is explained in this chapter. The storage subsystem consists of storage devices and the Fibre Channel (FC) infrastructure (such as FC switches and cables) used to connect these devices to Titan.
Page 104 AT-42 storage enclosures used for Tier 4 storage The five subsystems listed above have different capacity and performance characteristics. If one or more of the storage subsystems are configured, the server combines the storage resources into one or more File Systems. Titan SiliconServer...
Page 105: Fibre Channel Fabric And Arbitrated Loop
Multi-Tiered Storage Overview and Concepts Storage Supported Storage Disk RAID Performance Tier Enclosures Technology Technology Characteristics Tier 1 FC-14, Dual ported 15,000 RAID 1/5; Very high FC-16 FC disks RAID 1/5/10 performance Tier 2 FC-14, Dual ported 10,000 RAID 1/5; High FC-16 FC disks...
Page 106: Load Balancing And Failure Recovery
Load balancing is configured from the Command Line Interface (CLI), using the sdpath command. For more information, run man sdpath. This command can also be used to determine what FC path is used to communicate to each System Drive. Titan SiliconServer...
Page 107: Fibre Channel Statistics
FC-14 and SA-14 Storage Subsystems Fibre Channel Statistics Statistics are available to monitor the FC activity since Titan was last started or the statistics were reset. Both per-port and overall statistics are available. The statistics are updated every ten seconds. In addition, a Fibre Channel histogram which shows the number of bytes/second received and transmitted over the last few minutes is also available.
Page 108: Discovering And Adding Racks
System Drives System Drives are the basic storage element used by the Titan SiliconServer. A System Drive comprises a number of physical disks. The size of the System Drive depends on multiple factors such as the RAID level, the number of disks, and their capacity. RAID 5 is the only supported RAID level for the FC-14 and SA-14.
Page 109 FC-14 and SA-14 Storage Subsystems To add a RAID Rack From the Home page, click Storage Management. Then, click RAID Racks. Click Discover Racks. This may take some time to complete. System Administration Manual...
Page 110 SMU to maintain contact with the RAID Rack even if one of the controllers fails. Note: Deleting a RAID Rack only removes it as a device managed by the SMU. It will not affect any configured System Drives or File Systems. Titan SiliconServer...
Page 111: Creating System Drives
FC-14 and SA-14 Storage Subsystems Creating System Drives The storage system has been pre-configured by BlueArc. However, additional System Drives can be configured. A System Drive comprises a number of physical disks and has a unique identifying number (ID). Caution: Before creating System Drives, set aside at least one disk to be used as a hot spare.
Page 112 For many applications, RAID 5 offers the best compromise between capacity, reliability, and speed. Titan SiliconServer...
Page 113 FC-14 and SA-14 Storage Subsystems Click next. On the Create a System Drive page, select the System Drive’s size by clicking the appropriate button in the Capacity column. The System Drive’s size relies on the number of physical disks specified in the Number of Physical Disks column. Caution: To ensure optimal performance of the Storage Subsystem, do not change the value specified next to System Drive Capacity except under the direction of BlueArc Global Services.
Page 114: Managing Fc-14 And Sa-14 Storage
• Changing the name, password, media scan period, or cache block size settings. • Checking the status of media scan and other operations. • Reviewing events logged by the RAID rack. • Determining the status of physical disks. Titan SiliconServer...
Page 115 FC-14 and SA-14 Storage Subsystems To view a list of installed RAID racks Click on the Storage Management page, then click RAID Racks. Item/Field Description Name The name of the RAID Rack. Controller A/B Status of each controller in the RAID rack: Online or Offline. Status Firmware Firmware level in the RAID controllers.
Page 116 The View Active Tasks link shows the status of operations, such as media scans, which are in progress for a RAID rack. The details button brings up a RAID Rack Details page. This page provides information on the RAID rack. Titan SiliconServer...
Page 117 FC-14 and SA-14 Storage Subsystems Item/Field Description • Name of the RAID Rack. Enter a new RAID Rack name which is Identification used to identify the RAID Rack. • WWN: Worldwide name for the RAID Rack. • Media Scan Period: The number of days over which a complete scan of the system drives will occur.
Page 118 You can view the status of on-going activity (Media Scan, CopyBack, initializing, etc.) within the RAID Rack on the Active Tasks page. From the Home page, click Storage Management. Then, click RAID Racks. Check the check box next to the RAID Rack on which to view the Active Tasks. Titan SiliconServer...
Page 119 FC-14 and SA-14 Storage Subsystems Click View Active Tasks. Item/Field Description Task The Active Tasks (on-going activity) on the RAID Rack. Component The System Drive on which the Active Task is occurring. Percentage Complete The percentage of completion (%) for the Active Task. Not all Active Tasks will have a percentage complete shown.
Page 120: Reviewing Events Logged
Severe events are immediately forwarded to the Titan SiliconServer’s event log. This will trigger alert notifications (e.g. email or SNMP traps) if Titan is configured to do so. In addition, if the SMU is unable to connect to the RAID racks, a severe alert will be triggered on Titan.
Page 121: Monitoring Physical Disks
FC-14 and SA-14 Storage Subsystems The Event Log page will display a maximum of 1000 events (info or severe). Up to 3000 events are archived on the SMU and will be available for download by using the download button. This table can also be filtered to view the event log based on the severity level: All, Info, or Severe.
Page 122 Multi-Tiered Storage Click View Physical Disks. The status of the physical disks are displayed. Item/Field Description Manufacturer The name of the disk manufacturer. Slot The slot number in the storage enclosure in which the physical disk resides. Titan SiliconServer...
Page 123: Fc-16 Storage Subsystem
FC-16 Storage Subsystem Capacity The storage capacity of the disk. Type The type of physical disk in the enclosure, typically either Fibre (Channel) or SATA. Span The label of the Storage Pool, if the physical disk is in use within a Storage Pool.
Page 124: Storage Characteristics
System Drives System Drives are the basic storage element used by the Titan SiliconServer. A System Drive comprises a number of physical disks. The size of the System Drive depends on multiple factors, such as the RAID level, the number of disks, and their capacity. The RAID controller supports RAID levels 1, 5, and 10 (a combination of striping and mirroring).
Page 125 FC-16 Storage Subsystem To configure foreground/background initialization options From the Home page, click Storage Management. Then, click RAID Racks. Click details at the end of the row of the RAID Rack to which to view the initialization configuration. By default, the box is checked for background initialization (BGI). BGI sets up RAID parity non-destructively so the new System Drive used as soon as it has been created.
Page 126 Multi-Tiered Storage To create a System Drive On the Storage Management page, click System Drives. Titan SiliconServer...
Page 127 FC-16 Storage Subsystem Click create. On the Select RAID Rack page, select the RAID rack on which the System Drive will be created. Then, click next. Select the RAID level from the drop-down list. Select Speed or Size for Optimization. RAID Level System Notes...
Page 128 Column, the status of the System Drive displays if it is formatting or initializing. Once the System Drive has been initialized, a file system can be created. For more information on how to set up a file system, see "To Create a Silicon File System". Titan SiliconServer...
Page 129: Managing Fc-16 Storage
FC-16 Storage Subsystem Managing FC-16 Storage You can manage FC-16 RAID racks using Web Manager. Common operations are: • Performing consistency checks on System Drives. • Checking the status of consistency checks and other operations. • Determining the status of physical disks. On the Storage Management page, click RAID Racks.
Page 130 Firmware: The firmware number. • Monitor: Yes or No. Show The drop-down list allows the list to be displayed by: Show all (all of the RAID Racks are displayed), Show monitored RAID racks, and Show NOT monitored RAID racks. Titan SiliconServer...
Page 131 FC-16 Storage Subsystem RAID cache The size of the RAID cache. size Rack Name The name of the RAID Rack. Background By default, the box will be checked for background initialization (BGI). Initialization For foreground initialization, remove the check-mark and click Set Background Initialization.
Page 132 System Drives. During the consistency check, if parity errors are found, they will be logged in Titan’s Event Log. If a check was initiated with fault correction enabled, the parity will be updated to match the Titan SiliconServer...
Page 133 FC-16 Storage Subsystem data. Performing Background Consistency Checks Consistency checks can be performed periodically on every System Drive (SD), from the Command Line Interface (CLI) using the startbcc command. This command runs a background consistency check (BCC) on a SD for each rack, allowing all SDs to be checked in a ‘round robin’...
Page 134: Monitoring Physical Disks
RAID Rack or System Drive. It is also possible to change the status of the disks in cases where, for example, a disk needs to be removed or a new hot spare disk has been added. Titan SiliconServer...
Page 135 FC-16 Storage Subsystem To check and change the status of the physical disks From the Status & Monitoring page, click System Monitor. Then, click the FC-16 main enclosure. System Administration Manual...
Page 136 To change the status of one or more of the disks, select the new status from the drop-down list and then click Apply. It is possible to view more information on physical disks associated with a particular RAID rack, such as their physical position and the name of their manufacturer. Titan SiliconServer...
Page 137 FC-16 Storage Subsystem To view more information on the physical disks From the Storage Management page, click RAID Racks. Select the RAID Rack of interest and click details. Click Physical Disk Info>>. The table below describes the Item/Fields in this screen: Item/Field Shows Showing information...
Page 138: At-14 And At-42 Storage Subsystem
RAID 5 functionality and tolerance of single disk failures. System Drives System Drives are the basic storage element used by the Titan SiliconServer. A System Drive comprises a number of physical disks. The size of the System Drive depends on the number of disks and their capacity.
Page 139: Hot Spare Disk
AT-14 and AT-42 storage enclosures are managed using a Web management utility embedded in the storage subsystem. On a properly configured Titan SiliconServer, this utility is accessible from the System Monitor page. In addition, the Titan SiliconServer tracks alerts issued by the storage subsystem through SNMP.
Page 140: Creating System Drives
Click the Quick Start link on the left hand side of the page. Select the 2 Volume Config tab. On the next screen, click the Check this checkbox to confirm box, and click the Quickstart Configure for 2 Volumes button. Titan SiliconServer...
Page 141: Configuring The Storage Enclosure
AT-14 and AT-42 Storage Subsystem The next screen will show that the system is now initializing and will take several hours to complete (typically 3-4 hours). Configuring the AT-42 Storage Enclosure From the System Monitor page, click on the AT-42 enclosure that has to be configured. Click the Quick Start link on the left hand side of the page.
Page 142: Email Alerts
It should be unique, allowing the RAID system to be easily identified. This is useful when there are more than one ATA RAID systems. The When to send pull down menu will configure what type of email alerts need to be sent or, if required, this functionality can be switched off. Titan SiliconServer...
Page 143: Snmp Traps
SNMP Traps On a properly configured system, SNMP traps alert the Titan SiliconServer of failures or other unusual conditions. These alerts, when received, are logged as events in Titan’s event log. To setup SNMP traps click on the SNMP tab.
Page 144: Date And Time
Multi-Tiered Storage trap. Note: BlueArc recommends that the AT-14 and AT-42 storage enclosures be configured to send SNMP traps to the Titan SiliconServer for all levels. Also, Titan needs to be configured to accept these traps (see Configuring Devices on the System Monitor).
Page 145: System Drives
1. Technically, a Logical Unit Number (LUN) is a number that the RAID controller uses to identify a System Drive. Note that the LUN does not uniquely identify the System Drive on a Fibre Channel network, so the Titan SiliconServer uses an internally generated ID to track System Drives.
Page 146 Licensing Current capacity used The storage capacity currently in use. Limit The amount of storage that is licensed on this Titan SiliconServer, measured in Terabytes. Filter Filter by Access Select a filter for viewing the System Drives list: Show All, Access Allowed, Denied Access, Not Present.
Page 147 System Drives Label On FC-14 or SA-14 Storage Enclosures, the label assigned to the System Drive when it was created. If the label says Not known, the System Drive is present on the Fibre Channel network but the RAID controller is not accessible through an Ethernet managment network.
Page 148 SD which needs to be removed. Then, from the System Drives Detail page, click forget. To find System Drives which are not listed in System Drives table and to refresh the system drive list, click Discover System Drives. Titan SiliconServer...
Page 149 System Drives System Drive Details The System Drive Details page displays the details for a single System Drive (SD). From the Storage Management page, click System Drives. Then, click details next to the System Drive on which to view the additional details. System Administration Manual...
Page 150 System Drive. A foreground initialization will destroy all data on the System Drive. As a result, this option cannot be selected if a Storage Pool exists. • Start background initialization: click to start a background initialization of the System Drive. Titan SiliconServer...
Page 151 The Allow/Deny Access button will set the access to the System Drive: Allowed or Denied. The Forget button will remove a System Drive from the Titan SiliconServer’s configuration. The System Drive must be Not Present for it to be deleted.
Page 152: Chapter 5. Storage Management
The following diagram illustrates a simplified view of the architecture: System Drives System Drives (SDs) are the basic storage element used by the Titan SiliconServer. Storage subsystems use RAID technology to aggregate multiple disk storage devices into System Drives. For more information refer to "System...
Page 153: About Chunks
60 mounted file systems. The Titan 2000 Series supports up to 120 mounted file systems. The maximum size of the file system depends on three factors. • The model of the Titan SiliconServer. • The file system block size.
Page 154: About Virtual Volumes
Pool has been created, smaller file systems can be created in the pool for granular storage provisioning. This methodology should also be applied when expanding a Storage Pool. Move to the SMU Home page. From the Storage Management heading, click on Storage Pools to view a list of all Storage Pools. Titan SiliconServer...
Page 155 Using Storage Pools From the box at the bottom of the page, click create to view the Storage Pool Wizard page. Item/Field Description Raw Capacity of Shows a running total of selected System Drive sizes. Selected System Drives Usable Capacity of Shows the capacity of the Storage Pool that will be created based Selected System Drives on the selected System Drives.
Page 156 Storage Pools. For instructions about deleting a file system, see "To Delete a Silicon File System." Move to the SMU Home page. From the Storage Management heading, click on Storage Pools to view a list of all pools. Titan SiliconServer...
Page 157 Using Storage Pools From the right-hand column, click on the details button for the Storage Pool that must be deleted. From the list of Actions located on the bottom of the page, click delete to open a Confirmation dialog box. Click OK to delete the Storage Pool.
Page 158 Storage Pool, but it can also be used when a storage array that has been previously owned by another Titan SiliconServer has been physically relocated to be served by this server. The process involves restoring access to one of the System Drives that belong to the pool, and then restoring access to the pool itself.
Page 159 Using Storage Pools To Rename a Storage Pool The name for a Storage Pool can be changed at any time, and without affecting any clients. Move to the SMU Home page. From the Storage Management heading, click on Storage Pools to view a list of all pools.
Page 160: Using Silicon File Systems
From the box at the bottom of the page, click the create button to view the Create File System page. Click on An Existing Storage Pool link to view a list of available Storage Pools. From the Label column, select a Storage Pool. Titan SiliconServer...
Page 161 Using Silicon File Systems At the bottom of the page, click on next to view the Configuration page for the new file system. The following page will be displayed: Item/Field Description Storage Pool The name of the Storage Pool in which the file system is being created.
Page 162 Storage Pool. After a file system has been deleted, it cannot be recovered. A user must be either a Global Admin or Storage Admin, and must have Advanced Mode enabled to delete a file system. For more information, see "User Management". Titan SiliconServer...
Page 163 Using Silicon File Systems Move to the SMU Home page. From the Storage Management heading, click on Silicon File Systems to view a list of all file systems. From the right-hand column, click on details to view the Silicon File System Details page for the file system to be deleted.
Page 164 From the Label column, select one or more Silicon File Systems that need to be unmounted. From the list of Actions located on the bottom of the page, click on unmount to open a confirmation dialog box. Click the OK button to unmount the file system(s). Titan SiliconServer...
Page 165: Expanding A Silicon File System
Using Silicon File Systems Expanding a Silicon File System A Silicon File System can be expanded at any time and without interruption of service if the following conditions exist: There is sufficient available free space in its Storage Pool. ❑ The file system expansion will not cause the file system to exceed the maximum ❑...
Page 166 Relocating file systems that contain iSCSI Logical Units is not recommended. In doing so, not only will the relocation interrupt service to attached Initiators, but also manual reconfiguration of the Logical Units and Targets will be required once the relocation is complete. If relocating a Titan SiliconServer...
Page 167 Using Silicon File Systems file system with Logical Units is required, the following steps must be performed: Disconnect any iSCSI Initiators with connections to Logical Units on the file ❑ system to be relocated. Unmount the iSCSI Logical Unit. ❑ Relocate the file system as normal.
Page 168 Titan memory sizes can be either 2 GB or 4 GB. The table shown below shows the maximum file system size for different combinations of block and memory sizes. Titan Model 2100 Titan Model 2200 4 KB Blocks 16 TB 128 TB 32 KB Blocks 32 TB 256 TB Titan SiliconServer...
Page 169 Using Silicon File Systems To View Available File Systems From the Storage Management page, click Silicon File Systems. Item/Field Description Label The name of the File System. This is assigned when the File System is created, and used to identify the File System when performing certain operations, like creating an export or taking a snapshot.
Page 170 CLI to complete the expansion and restore the file system to normal operation. • Unformatted: No valid file system information was identified. The storage arrays may be offline. Format the file system to destroy any existing content or contact BlueArc support. Titan SiliconServer...
Page 171 Using Silicon File Systems • Recovering: The file system is in the process of rolling back to its last Status good checkpoint. If the server was reset uncleanly, the contents of (Other) NVRAM may be being replayed. • Failing: Rarely seen - the file system has failed but is being recovered or is in use by checkfs or fixfs.
Page 172 File System is created, and used to identify the File System when performed certain operations (e.g. creating an export or taking a snapshot). Status The current status of the file system, showing the amount of total used space and if the File System is mounted or unmounted. Titan SiliconServer...
Page 173 Using Silicon File Systems Current EVS to which the File System is assigned. If the file system is not currently assigned to an EVS, a list of EVS will appear to which the file system can be assigned. Status Indicates whether the EVS is online or offline. Security Displays the file system security...
Page 174 NVRAM. In extreme cases, it may be necessary to perform a forced recovery, which will discard the contents of NVRAM before mounting the file system. If a File System displays "Requires Recovery" in the status field: Titan SiliconServer...
Page 175: Worm File Systems
Using Silicon File Systems Click details to access the details page for the relevant file system. Click recover. This will initiate the file system recovery. Refresh the page and refer to the file system Status to check the progress of the recovery operation. If this does not recover the file system, choose from the following options: •...
Page 176 Once the retention date has been set, a file can be marked as WORM. To mark a file as WORM, configure the permissions of the file as read-only. To do this from a Unix client, remove the write attribute permissions. From a Windows client, mark the file as read-only through the file’s properties. Titan SiliconServer...
Page 177: Controlling File System Usage
Using Silicon File Systems Controlling File System Usage Titan can monitor space allocation on a File System and trigger alerts when certain pre-set thresholds are reached. It is also possible to prevent users from creating more files when one of these thresholds has been reached.
Page 178 Titan’s performance can be measured by how many operations per second (ops/sec) it is performing. Through the Web UI, a graphic representation of the number of ops/sec it is performing can be viewed. For details on displaying or downloading these statistics, see Server and File System Load (Ops per second). Titan SiliconServer...
Page 179: Setting Usage Quotas
Setting Usage Quotas Setting Usage Quotas Disk usage can be controlled and monitored by applying quotas, which can prevent network users from consuming more disk space (or creating more files) than allowed. Titan supports the following types of quotas: • User and group quotas.
Page 180 As soon as a set of Quota Defaults is defined in this way, a User or Group Quota (as appropriate) will be created for the owner of the directory at the root of the file system. Titan SiliconServer...
Page 181: Managing Usage Quotas
Setting Usage Quotas Managing Usage Quotas From the Storage Management page, click Quotas by File System. Section Description EVS/File System and the File System to which these quotas apply. To select a different EVS/File System, click change… Filter Since many quotas can exist on a single File System, it may be easier to find the quota information required by filtering the list.
Page 182 File Count The total number of files (in the File System) owned by the target of the quota. File Count (%) The file count as a percentage of the File Count Limit. Titan SiliconServer...
Page 183 Setting Usage Quotas To Set User Defaults From the Quotas by File System page, click User Defaults. Item/Field Description EVS/File and File System on which the User File System Quota applies. System Usage Limit The amount of space to enable in Bytes, KB, MB, GB or TB. Hard Limit If this box is ticked, the amount of space specified in the Limit field may not be exceeded.
Page 184 NT user in the quota, (unless each user's primary group has been explicitly set). To Add a File System Quota From the Quotas by File Systems page, click add. The table below describes the fields on this screen: Item/Field Description Titan SiliconServer...
Page 185 Setting Usage Quotas EVS/File System and the File System on which to add this quota. To select a different EVS/File System, click change… Quota Type The type of source of File System activity. Possible values are User or Group. User/Group A User/Group Account name may consist of: Account A CIFS domain and user or group name, such as ‘bb\Smith’...
Page 186: Using Virtual Volumes
• Files with multiple hard links are included only once. A symbolic link adds the size of the symbolic link file to a quota and not the size of the file to which it links. Titan SiliconServer...
Page 187: Managing Virtual Volumes
Using Virtual Volumes Managing Virtual Volumes From the Storage Management page, click Virtual Volumes & Quotas. Item/Field Description Filter Filters can be defined to reduce the number of Virtual Volumes displayed on the page. Filters can be configured based on the name or the path. EVS/File System The name of the selected and File System.
Page 188 Virtual Volume. the same name as Ticking this checkbox will ensure such a share or export, if it does not the Virtual Volume exist, is created. Note: The CIFS Share or NFS Export name may not exceed 80 characters. Titan SiliconServer...
Page 189 Using Virtual Volumes Allow exports to As overlapping exports can potentially expose security loopholes, the overlap condition can be tested for and, if found, the export creation can be denied. To prevent this check and allow overlapping NFS exports to be created, check the box labeled 'Allow exports to overlap'.
Page 190 Edit the values as required, and click OK to submit the changes. To Delete a Virtual Volume From the Storage Management page, click Virtual Volumes. Select the Virtual Volume(s) to be deleted. If all Virtual Volumes are to be deleted, click Check All. Titan SiliconServer...
Page 191: Managing Quotas On Virtual Volumes
Using Virtual Volumes On clicking delete, a warning will displayed asking for confirmation that this action is definitely required. Click OK to continue deleting the Virtual Volumes. Note: A Virtual Volume can only be removed from a directory when the directory is empty.
Page 192 Storage Management To View/Modify Virtual Volume Quotas From the Storage Management page, click Virtual Volumes & Quotas. From the Virtual Volumes page, select the Virtual Volume for which the Quotas are to be viewed. Click View Quotas. Titan SiliconServer...
Page 193 Using Virtual Volumes The table below describes the sections of this screen: Section Description Virtual Volume Identifies the Virtual Volume to which these quotas apply: EVS/File System: the and File System on which the Virtual Volume resides. Virtual Volume Name: the name of the Virtual Volume. Path: the directory on which the Virtual Volume has been created.
Page 194 File Count (%) The File Count as a percentage of File Count Limit. To Set User Defaults On the Quotas page, click User Quota Defaults. Item/Field Description EVS/File and File System on which the User Quota applies. System Titan SiliconServer...
Page 195 Using Virtual Volumes Virtual Volume The name of the Virtual Volume on which the User Quota is assigned. Name Usage Limit The amount of space to enable in Bytes, KB, MB, GB or TB. Hard Limit If this box is ticked, the amount of space specified in the Limit field may not be exceeded.
Page 196 An NFS user or group such as ‘richardb’ or ‘finance’ (where richardb is an NFS user and finance is an NFS group). If Virtual Volume has been selected as the Quota Target Type, it will not be possible to specify a Quota Name. Titan SiliconServer...
Page 197 Using Virtual Volumes Usage Limit The amount of space to enable in Bytes, KB, MB, GB or TB. Hard Limit If this box is ticked, the amount of space specified in the Limit field may not be exceeded. Warning Enter the percentage of the Limit at which a Warning alert will be sent. Severe Enter the percentage of the Limit at which a Severe alert will be sent.
Page 198: Retrieving Quota Usage Through Rquotad
The rquotad service has been implemented for use on Titan. It functions as a read-only protocol and is only responsible for procuring information about user and group quotas. Quotas can be created, deleted, or modified through the Storage Management section of the UI. Titan SiliconServer...
Page 199 Retrieving Quota Usage through rquotad Titan reports only the Hard Limit quota information through rquotad. As mentioned in the previous sections, there can be three different quota limitations defined: User and group quotas limiting the individual user or group’s space and file count usage within a Virtual Volume.
Page 200 The console command "rquotad" is provided to change between the two options, and also to disable access to quota information. For information on how to configure rquotad, please refer to the Command Line Reference. Note: If access is disabled, all requests to rquotad will be rejected with an error code of “EPERM”. Titan SiliconServer...
Page 201: Bluearc Data Migrator
BlueArc Data Migrator BlueArc Data Migrator Titan supports multiple storage technologies, with different performance and cost characteristics. In order to take full advantage of Multi-Tiered Storage (MTS), data should be organized using a tiered hierarchy of importance and need. BlueArc Data Migrator makes this possible.
Page 202: Data Migration Paths
Note: Once a Migration Path has been assigned to a Virtual Volume, a subsequent Migration Path cannot be created to its hosting file system. Also, once a Migration Path has been assigned to a file system, subsequent Migration Paths cannot be created from Virtual Volumes hosted by that file system. Titan SiliconServer...
Page 203 BlueArc Data Migrator To configure Data Migration Paths From the Home page, click Storage Management. Then, click Data Migration Paths. The fields on this screen are described in the table below: Item/Field Description Primary EVS/File Displays the EVS and file system from which data will be System migrated.
Page 204 By default, the entire file system is included in the data migration policies. To configure migrations on a Virtual Volume basis, check the box and select the Virtual Volume to be used as the primary storage for this Data Migration Path. Titan SiliconServer...
Page 205: Data Migration Rules
BlueArc Data Migrator Destination File System Select the destination file system from the drop-down menu. The file system selected should be on secondary storage. Click OK to create the Data Migration Path as configured. Click cancel to discard the current selection and return to the Data Migration Paths page. Data Migration Rules The Data Migration Rules page lists all existing rules, and allows new rules to be created.
Page 206 To add a Data Migration Rule by Template From the Home page, click Storage Management. Then, click Data Migration Rules. Click Add by Template. The Data Migration Rule Templates page appears with the choice of a number of Rule Templates. Titan SiliconServer...
Page 207 BlueArc Data Migrator Select one of the Rules Templates and click Next, to further define it. Rule Template Description By Last Access This template can be used to migrate all files that have remained inactive for a certain period of time. By File Name This template can be used to migrate all files with the same extension, i.e.
Page 208 The drop-down menu also has an option for selecting the opposite of the above scenario, i.e. choose exclude to select all files that are not in the path. Refer to Rule Syntax for important information about rule criteria. Titan SiliconServer...
Page 209 BlueArc Data Migrator Rules Template: By Last Access Time and File Name Item/Field Description Name Enter a name for the new rule. Description Enter a description of what the rule does. Case sensitive Select the checkbox if the rule checking must be case sensitive. pattern checks To specify the type of inactive files to be migrated to a secondary Include Criteria...
Page 210 Rule Syntax for important information about rule criteria. Click OK to create the rule as configured and return to the Data Migration Rules page. Click cancel to discard the configuration and return to the Data Migration Rules page. Titan SiliconServer...
Page 211 BlueArc Data Migrator Rule Syntax Data migration rules can be built with a series of INCLUDE and EXCLUDE statements, each containing a number of expressions identifying the criteria for data migration. Remember the following guidelines when building rules: Each rule must have at least one INCLUDE or EXCLUDE statement. If a rule ❑...
Page 212 The value is appended to the keyword and is defined by the threshold size in B, KB, MB, or GB. Usage: This will likely be used with INCLUDE statements to ensure files of very large sizes are migrated to secondary storage. For example: <FILE_SIZE_OVER 4GB> Titan SiliconServer...
Page 213 BlueArc Data Migrator Identifies file in the rule whose sizes fall below a specific FILE_SIZE_UNDER size threshold. The value is appended to the keyword and is defined by the threshold size in B, KB, MB, or GB. Usage: This will usually be used in an EXCLUDE statement to ensure that very small files are not migrated en masse.
Page 214 So, only .mp3 files that are 5 GB or more in size satisfy both conditions of the rule and will be included for migration. If OR was used instead of AND in the above example: INCLUDE (<FILENAME *.mp3> OR <FILE_SIZE_OVER 5GB>) Titan SiliconServer...
Page 215 BlueArc Data Migrator The same two conditions apply: All files with the .mp3 name must be included. All files that are 5 GB or bigger in size must be included. But the rule is specifying entirely different criteria. Where AND is used to satisfy two different conditions, OR is used to include either of the two conditions.
Page 216 EXCLUDE statements. But add these EXCLUDE statements above the INCLUDE, such as: EXCLUDE (<FILE_SIZE_UNDER 2MB>) EXCLUDE (<ACTIVE_WITHIN 14>) 3. The rule should finally appear this way: EXCLUDE (<FILE_SIZE_UNDER 2MB>) EXCLUDE (<ACTIVE_WITHIN 14>) INCLUDE (<PATH /Temp> AND <FILENAME *.mp3>) Titan SiliconServer...
Page 217: Data Migration Policies
BlueArc Data Migrator Given the guidelines for creating rules and the assortment of keywords and building blocks for rules shown in the samples above, creating rules for Data Migration should be easier. Data Migration Policies Having created both Data Migration Paths and Rules, Data Migration Policies can now be created.
Page 218 Click the details button next to the policy to view the complete details regarding it. To add a Data Migration Policy From the Data Migration Policies page, click add. The Add Data Migration Policy screen appears. Item Description Name Give the new policy a name. Titan SiliconServer...
Page 219 BlueArc Data Migrator Primary EVS/File System The EVS and file system name on primary storage; the migration source. Virtual Volume If a Virtual Volume has been selected as primary storage, then the Virtual Volume name will be displayed. Secondary File System The file system on secondary storage that will host the migrated data;...
Page 220 Volume, free space will be based on the limit defined by the Virtual Volume Quota. If a Virtual Volume quota has not been defined, then the free space available will be based on the free space of the file system hosting the Virtual Volume. Titan SiliconServer...
Page 221: Data Migration Schedules
BlueArc Data Migrator Data Migration Schedules Once a Data Migration Policy has been defined, it must then be scheduled to run. How often to run the Policy will be entirely dependent on the Rules defined. For example: A policy with a single Rule to migrate all .mp3 files may be scheduled to run once ❑...
Page 222 Interval Displays the frequency at which the data migration has been scheduled to run. Select a Migration Schedule and click Abort Migrations to abort the selected migration. Only in-progress migrations can be aborted. Titan SiliconServer...
Page 223 BlueArc Data Migrator Click Add to add a new schedule from the Add Data Migration Schedule page. Click Remove to clear a selected schedule from the list. To add a Data Migration Schedule From the Home page, click Storage Management. Then, click Data Migration Under Scheduled Migrations, click add to schedule a new data migration.
Page 224 Click OK to add the schedule and return to the Data Migration page. Click cancel to clear the screen and return to the Data Migration page. Titan SiliconServer...
Page 225 BlueArc Data Migrator To modify a Data Migration Schedule Once defined, schedules can be easily modified to meet the changing requirements of the Data Migration Policies. When modifying a schedule, the scheduled date and time, as well as the interval in which the schedule will run can be changed. From the Data Migration page, select a schedule to modify.
Page 226: Data Migration Reports
From the Home page, click Storage Management. Then, click Completed Data Migrations. The following will be displayed: Item Description Schedule ID Displays the ID number for the completed migration. Server Displays the primary file system's server. Displays the primary file system's EVS. Policy Displays the policy's name. Titan SiliconServer...
Page 227 BlueArc Data Migrator Completed Displays the month, date, year and time when the migration was completed. Files Migrated Displays the number of files that were migrated. Status Displays the status on whether the migration was successfully completed. Click details to view the completed migration report. Click remove to delete one or more completed migrations listed on the page.
Page 228 Storage Management To view Data Migration Reports From the Home page, click Storage Management. Then, Completed Migrations. Select the completed migration of interest and click details next to it. The following page appears: Titan SiliconServer...
Page 229 BlueArc Data Migrator The following will be displayed: Item Description Report Summary Migration Policy Displays the completed migration policy's name. Schedule ID Displays the migration schedule ID. Status Indicates whether the migration was successfully completed. Frequency Displays how often the Policy is scheduled to run. Start Time Displays the date and time when the migration began.
Page 230 Click Download Migration Report to view a report on the completed data migrations with details on the primary and secondary file systems and Virtual Volumes: their status, space utilization before and after the migration, the duration, start, and end time for the migrations, etc. Titan SiliconServer...
Page 231: Reverse Migration
BlueArc Data Migrator Reclaimed space Reclaimed space is the difference in space between the start of the migration and when the migration completed. It is not a report of the mount of data migrated from the source file system to the target. For this detail, refer to Amount Migrated. It is likely that the file system will be in use by network clients while the migration is in progress.
Page 232 Primary and Secondary Storage. Alternatively, use NDMP_BLUEARC_EXCLUDE_MIGRATED to isolate the backup dataset to only those files that are hosted natively on Primary Storage. Titan SiliconServer...
Page 233 BlueArc Data Migrator iSCSI Logical Units Mounted iSCSI Logical Units cannot be migrated, regardless what has been defined in the Data Migration Policy. Due to the types of applications typically hosted on iSCSI storage, BlueArc does not recommend migrating iSCSI Logical Units to secondary storage. However, if this is desired, it can be accomplished by performing the following: Disconnect any iSCSI Initiators with connections to Logical Unit.
Page 234: Chapter 6. File Services
Titan is a file-serving product, and its principal use is to satisfy incoming file access requests issued from network clients. The Titan SiliconServer supports the CIFS, NFS (TCP and UDP, version 2 and 3), and FTP protocols for client file access. In addition, Titan supports iSCSI for block-level access to storage.
Page 235: File System Security
File Service Protocols To enable file services From the Home page, click File Services. Then, click Enable File Services. The table below describes the fields on this screen: Item/Field Description Services Select the Services checkbox(es) that are required for the system: •...
Page 236: Mixed Security Mode
CIFS Access to Native CIFS Files When a CIFS client tries to access a native file, one with Windows security information, the server checks the user information against the file’s security information to determine whether or not an operation is permissible. Titan SiliconServer...
Page 237 File Service Protocols Security information on a user is contained in an access token, which comprises the user security identifier (SID), primary group SID, and other SIDs. The server gets the token from the domain controller and caches it for use throughout the user’s session. Security information on a file is contained in its security descriptor, which comprises the owner SID, group SID, and access control list (ACL).
Page 238: Unix Security Mode
DC failures. Security Mode Configuration Security modes can be configured per-EVS, per-file system, or per-Virtual Volume. Selecting security modes on such a tiered basis, rather than a system-wide selection, enhances the granularity and convenience of managing system security. Titan SiliconServer...
Page 239 File Service Protocols To view the server's Security Configuration From the Home page, click File Services. Then, click File System Security. Item/Field Description The list of all defined by the filter. File System If this column is blank, the security mode displayed is associated with the EVS.
Page 240 The Security Configuration page for the selected EVS displays the EVS name and a drop-down menu in which to specify the security Mode. Select the desired security mode for the EVS from the drop-down menu. Click OK. Click cancel to return to the File System Security page. Titan SiliconServer...
Page 241 File Service Protocols To change the security mode for a file system By default, the file system inherits the parent EVS security mode. In other words, when the parent EVS has a Unix security mode, the file system associated with the EVS will inherit the Unix security mode.
Page 242 Unix security mode. To apply a different security mode to a Virtual Volume, do the following: In the File System Security page, put a check in the box next to the EVS on which to view the Virtual Volumes. Titan SiliconServer...
Page 243 File Service Protocols Click View Virtual Volume Security. The Virtual Volume Security Configuration page displays a list of all Virtual Volumes corresponding to the defined filter. Item/Field Description The list of EVS defined by the filter. File System The list of file systems defined by the filter. Virtual Volume The names of all Virtual Volumes found on the file systems defined by the filter.
Page 244: Mixed Mode Operation
Click cancel to return to the File System Security page. Mixed Mode Operation The Titan SiliconServer allows network clients to share a common pool of storage from both Windows and UNIX clients. This is referred to as mixed mode operation. Although the Titan SiliconServer does this as seamlessly as possible, the protocols are considerably different, so mixed mode operation presents some challenges.
Page 245: File Locks In Mixed Mode
File Service Protocols Symbolic Links Symbolic links (symlinks) are commonly used in UNIX to aggregate disparate parts of the file system or as a convenience, similar to a shortcut in the Windows environment. Titan fully supports symlinks when the file system is accessed through NFS. Files marked as symbolic links are assumed, by UNIX clients, to contain a text pathname that can be read and interpreted by the client as an indirect reference to another file or directory.
Page 246 This happens regardless of the network protocol that the second client uses. In cases where a CIFS client requests an oplock on a file that has an Exclusive or Batch oplock, the server breaks the existing oplock and grants both clients Level II oplocks instead. Titan SiliconServer...
Page 247: Configuring User And Group Mappings
File Service Protocols Level II Oplocks A Level II oplock is a non-exclusive (read-only/deny-write) file lock that a CIFS client may obtain at the time it opens a file. The server grants the oplock only if all other applications currently accessing the file also possess Level II oplocks.
Page 248 To specify the NFS user names manually Each UNIX user name and numerical UID can be manually entered, along with its corresponding Windows user and domain name. Users configured manually will appear as ‘permanent’ in the NFS users list. Titan SiliconServer...
Page 249 File Service Protocols From the Home page click File Services. Then, click User Mapping. There are two steps to follow when setting up NFS users on the system: First specify each NFS user’s name and user ID, and then map the NFS user names to Windows NT user names. If the system has been setup to access the information on an server, it is only necessary to perform the second of these steps;...
Page 250 To specify NFS group names manually Each UNIX group name and numerical GID can be manually entered, along with its corresponding Windows group and domain name. Groups configured manually will appear as ‘permanent’ in the NFS group list. Titan SiliconServer...
Page 251 File Service Protocols From the Home page click File Services. Then, click the Group Mapping item. There are two steps to follow when setting up NFS groups on the system: First specify each NFS group’s name and group ID, and then map the NFS group names to Windows NT group names. If the system has been setup to access the information on an server, it is only necessary to perform the second of these steps;...
Page 252 A quick way to specify the user or group details is by importing them from a file. There are three possible formats for this file, as described below. Choose one format and use it consistently throughout the file. Titan SiliconServer...
Page 253 File Service Protocols NFS user/group data only The source of the user data can be a UNIX password file, such as /etc/passwd. When using the Network Information Service (NIS), typing this command can create the file: ypcat passwd > /tmp/x.pwd The following is an extract from a file in the required format.
Page 254: Sharing Resources With Nfs Clients
UNIX workstations to access each other's files transparently. This section describes how to set up NFS exports, users, and groups. The Titan SiliconServer and NFS The Titan SiliconServer implements the file-serving functions of an NFS server. The system provides the normal file-serving functions, such as: •...
Page 255: Configuring Nfs Exports
Sharing Resources with NFS Clients HP-UX 10, 11 Irix The system supports the following UNIX protocols: versions 2 and 3 Port Mapper version 2 Mount versions 1 and 3 Network Lock Manager (NLM) versions 1, 3, and 4 Network Status Monitor (NSM) version 1 NFS Statistics Statistics...
Page 256 Create path if it Check the box Create path if it does not exist to create the path does not exist entered in the Path field. Show snapshots Check the box to allow snapshot access from the NFS export. Titan SiliconServer...
Page 257 Sharing Resources with NFS Clients Ignore Overlap When checked (default option), this sets up nested NFS exports. For example, export the root directory of a File System and make it available to managerial staff only. This also allows the sub-directories of the root directory to be exported later and each of them can be made available to different groups of users.
Page 258 Be sure to specify the fully qualified domain name of the client. For example, type aclient.dept.mycompany.com rather than simply aclient. • To specify a partial name, a single wildcard, located at the start of the name, may be used. Titan SiliconServer...
Page 259 Sharing Resources with NFS Clients • The system determines the export options to apply to a specific client when the client mounts the NFS export. Subsequent changes to DNS, WINS, or NIS that would result in the client’s IP address resolving to a different computer name are only applied to any mounted exports when the client unmounts the exports and then remounts them.
Page 260 On the NFS Exports page, check the box next to the NFS Export of which to view/modify the properties. Click details. On the NFS Export details page, one or more fields can be modified. Click OK if any of the fields are changed. Titan SiliconServer...
Page 261: Using Cifs For Windows Access
The Titan SiliconServer and CIFS The Titan SiliconServer emulates the file-serving functions of a Windows NT 4.0, Windows 2000, or Windows 2003 server. As far as clients are concerned, the Titan is indistinguishable from a Windows file server. It provides all of the normal file-serving functions, such as: •...
Page 262 Titan relies on Windows domain controllers to authenticate users and get user information such as group membership. Titan automatically discovers and connects to the fastest and most reliable domain controllers. Since operating conditions may change over time, Titan selects the "best" domain controller every 10 minutes. Titan SiliconServer...
Page 263: Dynamic Dns
Using CIFS for Windows Access By default, when authenticating clients in an Active Directory, Titan uses the time maintained by the domain controller, automatically adjusting for any clock inconsistencies. Dynamic DNS On TCP/IP networks, servers communicate with each other through their IP addresses. The Domain Name System (DNS) is the most common method by which clients on a network or on the Internet resolve a host name with an IP address, facilitating IP-based communication between them.
Page 264: Configuring Cifs Security
Note: For security, the Microsoft AD requires that the time difference between the joining computer and the AD is not more than 5 minutes. Verify that the time on Titan is configured properly and is in sync with the domain before attempting to join the Directory. Titan SiliconServer...
Page 265 Using CIFS for Windows Access From the Home page, click File Services. Then, click CIFS Setup. From the EVS drop-down menu, select the EVS on which to create the CIFS name. Click Add>> to add a CIFS name. System Administration Manual...
Page 266 Note: When specifying a user account from a trusted domain, the user account must be entered using the Kerberos format. In other words, use administrator@ADdomain.mycompany.com, not ADdomain\administrator. DC Admin The correct password for the Domain Administrator user. Password Click Apply. Titan SiliconServer...
Page 267 A computer account must be created in the NT domain. A corresponding NT 4 CIFS name must be created on the Titan SiliconServer. To create a computer account in an NT 4 domain, run Server Manager from a Domain Controller in the NT 4 Domain and create a new “Windows NT Workstation or Server”...
Page 268 Titan by its name through DNS. Dynamic DNS registration of CIFS names and IP addresses is an easy way to ensure reliable connectivity. Caution: Disabling NetBIOS can cause connectivity problems for users of older versions of Windows. Titan SiliconServer...
Page 269: Configuring Local Groups
Using CIFS for Windows Access To disable NetBIOS: From the Home page, click File Services. Then, click CIFS Setup. Uncheck Enable NetBIOS. Reboot the server when prompted. Configuring Local Groups In a Windows security domain, users and groups exist to identify users (e.g. jamesg) and groups of users (e.g.
Page 270 File Services This is similar in the Titan SiliconServer. The administrator has the ability to add users to any of the local groups named above. Although users can be added to any of these groups, only three of them are currently effective: •...
Page 271: Configuring Cifs Shares
Using CIFS for Windows Access The items on this screen are described in the following table: Item/Field Description Administrators The local groups currently effective on the Titan SiliconServer. Backup Operators Forced Groups Select the where the local group resides Name / New The name of the user or group.
Page 272 The directory on which the CIFS share is located. Share Access Select a share and click Share Access Authentication to view or configure Authentication user and group access permissions on the selected share. Refer to Controlling Access to Shares for more information. Titan SiliconServer...
Page 273 Using CIFS for Windows Access Download Download a comma separated value (.csv) file containing a list of all Shares configured CIFS shares on the selected EVS and file system. To download a list of shares from another file system, click change... Click Add.
Page 274 Blank or * All clients can access the share. Specific addresses. Only clients with the specified IP Example: 10.168.20.2 address can access the share Partial addresses using Clients with matching addresses wildcards. can access the share. Example: 10.168.*.* Click OK. Titan SiliconServer...
Page 275: Controlling Access To Shares
Using CIFS for Windows Access Share qualifiers To specify which clients have access to a CIFS share, qualifiers can be appended to the IP address(es): Qualifier Description read_write, readwrite, rw Grants read/write access. This is the default setting. read_only, readonly, ro Grants the specified client read-only access to the CIFS share.
Page 276 This operation does not guarantee a user can obtain access to the specified files, because only files that have been used at least once are cached. The Automatic mode can be defined for documents or programs. Titan SiliconServer...
Page 277: Using Windows Server Management
Using CIFS for Windows Access Modifying or Deleting a Share Before modifying or deleting a share, verify that no-one is currently accessing it. Where this is the case, the Shares Configuration dialog box shows the number of Share users to be zero. If a share is modified or deleted while other users are accessing it, their CIFS sessions will be terminated and any unsaved data may be lost.
Page 278 File Services To Use the Computer Management tool Start Computer Management. Select Connect to another computer. Titan SiliconServer...
Page 279 Using CIFS for Windows Access If necessary, specify the domain in "look in". Select a name or an IP address that is used for file services on Titan. Note: Do not specify a server administration name or IP address for this purpose.
Page 280 File Services Do one or more of the following: To view the server’s event log, click Event Viewer. ❑ Titan SiliconServer...
Page 281 Using CIFS for Windows Access To list all the shares, click Shares. Some or all of the users can be disconnected ❑ from specific shares. To list all the open shared resources, click Open Files. Some or all of the shared ❑...
Page 282: Transferring Files With Ftp
File Systems to which to allow FTP access. Then, the login details of FTP users must be specified to associate them with the mount points. The Titan SiliconServer and FTP The Titan SiliconServer implements the file-serving functions of an FTP server. Titan provides the file-serving functions required for: •...
Page 283 Transferring files with FTP To Configure FTP Preferences From the Home page, click File Services. Then, click FTP Configuration. Select the Password Authentication Services: NT or NIS. The password authentication services are used to authenticate FTP users. The security mode in which the system is operating determines which of the services is available.
Page 284: Setting Up Ftp Mount Points
From the Home page, click File Services. Then, click FTP Mount Points. Item/Field Description Select the EVS, on which to view the configured Mount Points. Existing FTP mount points Mount name The box will list any existing mount point names. Current sessions The number of active current sessions. Titan SiliconServer...
Page 285 Transferring files with FTP File System Label The label for the file system to which the selected mount point is added. File System Size The size of the file system to which the selected mount point is added. System Drive The storage capacity of the system drive on which the file system Capacity resides.
Page 286: Setting Up Ftp Users
FTP users are currently connected. Click Modify FTP Mount Point. Setting Up FTP Users At least one FTP user for each mount point must be defined. FTP users can be manually setup or their details can be imported from a file. Titan SiliconServer...
Page 287 Transferring files with FTP To Set Up A FTP User From the Home page, click Files Services. Then, click FTP Users. Item/Field Description Select the on which to view configured FTP users. Existing FTP Users (Up to 500 users shown) The box will display a list of existing FTP users.
Page 288 Under the Import FTP User heading, enter the file name that contains the user details. Click Browse to search for the filename. The entries in the filename must follow this pattern: user_name mount_point initial_directory For example: carla Sales /Sales/Documents miles Sales /Sales john Marketing /Marketing Click Import File. Titan SiliconServer...
Page 289: Setting Up Ftp Audit Logging
Transferring files with FTP To View/Modify FTP Users From the Home page, click Files Services. Then, click FTP Users. Click Properties>>. To modify the to which the FTP User is added, select the EVS from the drop-down list. Using the drop-down list, select a new FTP Mount Point to which the FTP User is assigned.
Page 290 The directory on the specified file system in which to keep the log files. Ensure path exists If the box is checked, the Logging Directory is automatically created if it does not exist. No. Records per log The maximum number of records to store in each log file. file Titan SiliconServer...
Page 291: Block-Level Access Through Iscsi
Click Apply after completing the set up. Block-Level Access through iSCSI The Titan SiliconServer supports iSCSI. The Internet Small Computer System Interface (iSCSI) protocol enables block level data transfer between requesting applications and iSCSI Target devices. Using Microsoft’s iSCSI Software Initiator (version 1.06 or later), Windows servers can view iSCSI Targets as locally attached hard disks.
Page 292: The Titan Siliconserver And Iscsi
File Services The Titan SiliconServer and iSCSI To use iSCSI storage on Titan, one or more iSCSI Logical Units (LUs) must be defined. iSCSI Logical Units are blocks of SCSI storage that are accessed through iSCSI Targets. iSCSI Targets can be found through an iSNS database or through a Target Portal. Once an iSCSI Target has been found, an Initiator running on a Windows server can access the Logical Unit as a “local...
Page 293: Configuring Iscsi
Block-Level Access through iSCSI Prerequisites To enable iSCSI capability: Enter an iSCSI license key. ❑ Enable the iSCSI service. ❑ Offload Engines Titan currently supports the use of the Alacritech SES1001T and SES1001F offload engines when used with the Microsoft iSCSI initiator version 1.06 or later. Check with BlueArc Support for the latest list of supported offload engines.
Page 294 • A first iSNS server is added. • An iSCSI Target is added or deleted. • The iSCSI service is started. • The iSCSI domain is changed. • A server IP address is added or removed. Titan SiliconServer...
Page 295: Setting Up Iscsi Logical Units
Block-Level Access through iSCSI To Add an iSNS Server From the Home page, click File Services. Then, click iSNS. Select the on which to add the iSNS server. Click Add>>. Enter the IP Address of the iSNS server. The default Port number is 3205. Click Apply.
Page 296 CIFS shares or NFS exports. Concurrent Access to Logical Units The Titan SiliconServer's iSCSI implementation allows multiple initiators to connect to a single Logical Unit. This is necessary for applications and operating systems that support, or rely upon, concurrent file system access.
Page 297 Block-Level Access through iSCSI Taking Snapshots of Logical Units The contents of an iSCSI Logical Unit are controlled entirely by the client that's using it. Titan cannot interpret the file systems or other data contained within a Logical Unit in any way. Therefore, Titan has no knowledge of whether the data held within an iSCSI Logical Unit is in a consistent state.
Page 298 The size of the Logical Unit. Note: The maximum size of a Logical Unit is 2 TB. This limit is imposed by the SCSI protocol. File System The name of the file system used to host the Logical Unit. Label Titan SiliconServer...
Page 299 Block-Level Access through iSCSI File System Indicates whether the file system is mounted or not. Mounted Logical Unit Indicates whether the Logical Unit is mounted or not. Mounted To Add An iSCSI Logical Unit To configure an iSCSI Logical Unit, click Add>> on the iSCSI Logical Units page. Select the on which to create the Logical Unit.
Page 300: Setting Up Iscsi Targets
Titan supports a maximum of 32 iSCSI Targets per EVS and a maximum of 32 iSCSI sessions per Target. To Add, Delete, or Modify an iSCSI Target On the File Services page, click iSCSI Targets. Titan SiliconServer...
Page 301 Block-Level Access through iSCSI The table below describes the fields on this screen: Item / Field Description Select the on which to create the Target. Name Identifies the name of the Target. Comment Additional information related to the Target. Globally Unique Name The Target’s name.
Page 302 The password used to secure the Target from any unauthorized access. The initiator will need to authenticate against this password when connecting to the Target. The secret must be equal to or greater than 12 characters, but less than 17 characters in length. Titan SiliconServer...
Page 303 Block-Level Access through iSCSI Enable Authentication By default, the box is checked. This enables the authentication of the iSCSI Target. Access Configuration Enter the desired access configuration parameters. Refer to the Access Configuration table below for details on how to define the Access Configuration List.
Page 304: Iscsi Security (Mutual Authentication)
Use the drop-down list to select the associated with the Target for which mutual authentication is required. Enter the Initiator name. This is the same name found in the Change Initiator node name box on the Initiator Settings tab of the Microsoft iSCSI Initiator. Titan SiliconServer...
Page 305 Block-Level Access through iSCSI Enter the Secret for the Initiator. This is the secret which will be entered in the Initiator Chap Secret box on the iSCSI Initiator. Click Add. If you need to modify a secret, select the Initiator name and secret in the list. Enter a new secret in the Modify Secret box.
Page 306: Accessing Iscsi Storage
Using iSNS is the easiest way to find iSCSI Targets on the network. If the network is configured with an iSNS server, configure the Microsoft iSCSI Initiator to use iSNS. Click on the iSNS Servers tab. Click Add. Enter the iSNS Server’s IP Address or DNS name. Click OK. Titan SiliconServer...
Page 307 Target Portals. Add the Titan’s file services IP to the Target Portals list to find Targets associated with that server or EVS. Click on the Target Portals tab. Click Add. Enter the file service IP address for the Titan SiliconServer. System Administration Manual...
Page 308 File Services Click OK. To access available iSCSI Targets Click on the Available Targets tab. Titan SiliconServer...
Page 309 Block-Level Access through iSCSI Select the Target to which you want to connect. Each logon starts an iSCSI session. Note: A maximum of 32 iSCSI sessions are allowed per Target. Clock Log On. If authentication is enabled on the Target, click Advanced… Check the box for CHAP logon information.
Page 310 The iSCSI “local disk” will need to be configured through Computer Management, which can be found in Control Panel > Administrative Tools. Click on Disk Management. If this is the first connection to the iSCSI storage, the Write Signature and Upgrade Disk Wizard prompt further action. Titan SiliconServer...
Page 311 Block-Level Access through iSCSI Follow the prompts to add the Windows signature to your iSCSI “local disk”. Once the Write Signature Wizard has been finished, a Completed screen should appear. Click Finish. Prepare the disk for use through the Windows disk management tools. System Administration Manual...
Page 312: Chapter 7. Data Protection
The data protection services include snapshots, anti-virus support, data replication, NDMP backup, etc. The Titan SiliconServer uses a unique hardware based File System, which delivers outstanding performance, and, at the same time, preserves the data in the event of an unexpected failure such as a power loss.
Page 313 Data Protection Overview Buffering the requests in local NVRAM ensures that software failure or power failure will not result in data loss. Additionally, nodes in a Titan cluster will mirror the contents of their NVRAM to a partner node so that even a single server hardware failure will not result in data loss. Power Failure Recovery In the event of a power failure the contents of the NVRAM are preserved (using dedicated battery backup) for a maximum of 72 hours.
Page 314: Using Snapshots
This allows the control of who can access snapshot images. For example, create shares for users with snapshots disabled, and then create a second set of shares with restricted privileges, so that administrators can access snapshot images. Titan SiliconServer...
Page 315: Latest Snapshot
Using Snapshots Latest Snapshot Bluearc provides a filesystem view that can be used to access to the "latest snapshot" for a File System. This view automatically changes as new snapshots are taken, but is not affected by changes in the live filesystem. The latest snapshot is the most recent snapshot for the File System, and is accessible through .snapshot/.latest (or ~snapshot/~latest).
Page 316 If more than one snapshot is generated per minute by a particular rule, the names will be suffixed with .a, .b, .c etc. For example, a rule with the name ‘frequent’ generates snapshots called: 2002-06-17_1430+0100.frequent 2002-06-17_1430+0100.frequent.a 2002-06-17_1430+0100.frequent.b... and so on. Titan SiliconServer...
Page 317 Using Snapshots In the Queue Size field, specify the number of snapshots to keep before the system automatically deletes the oldest snapshot. The maximum is 32 snapshots per rule. Select the File System on which to take snapshots, and then click Apply. The Snapshot Rules page shows a summary of the details for the rule entered through the Add a Rule dialog box on the previous page.
Page 318: Managing Snapshots
To delete an individual snapshot, select it and then click Delete. To delete all the snapshots, select Check All and then click Delete. To take a new snapshot, click Take a Snapshot. Titan SiliconServer...
Page 319 Using Snapshots Select a File System for the snapshot. In the Name field, type a name for the snapshot containing up to 30 characters. Do not include spaces or special characters in the name. Click OK. Note: It is also possible to take a snapshot associated with a rule, without waiting for the next scheduled time.
Page 320: Performing Ndmp Backups
NDMP is used to transfer data between disks and tapes attached to the same server. Data can also be transferred between two separate NDMP servers over an Ethernet connection (in NDMP this is known as a 3-way backup or recovery). Titan SiliconServer...
Page 321: Configuring Ndmp
Backing up (recovering) data on a Titan SiliconServer to (from) an Ethernet attached NDMP tape library. • Backing up (recovering) data on a Titan SiliconServer without a Tape Library to (from) a second BlueArc Storage Server that has a Tape Library attached. •...
Page 322 Reference) is used to create such users. These user names could for instance be assigned to various users to allow them to use the ADC utility to copy data within limited areas of the file systems. The SSC command ndmp-ruser-pwd may be used to change the password for a Titan SiliconServer...
Page 323 Performing NDMP Backups selected restricted user. Note: The user name and password are for NDMP access only, and cannot be used to log in to the system or access files through other routes, such as Windows NT file sharing. However, anyone who knows the user name and password can use an NDMP-enabled storage management application to access data on the system.
Page 324: Ndmp Backup Devices
FC links. Backup devices are added to the configuration through the Backup SAN Management page. Backup SAN Management From the Home page, click Data Protection. Then, click Backup SAN Management. Titan SiliconServer...
Page 325 Performing NDMP Backups Item/Field Description All Tape Devices Displays the ID, Device Type, Serial Number, Location, and EVS. and Autochangers Show Filters the list: Show All, Show Allowed, Show Not Present, Show Denied, Show Tape Drives and Show Autochangers. Allow Access Clicking the Deny Access button will deny access to the selected tape device.
Page 326 The tape library is offline. • The autochanger does not support the mechanism that the Titan SiliconServer uses to query the tape drive location, or the autochanger has not been setup to accept this query. Where this is the case, compare the serial numbers of the tape drives with displays available in the tape library to verify the drive locations.
Page 327: Ndmp And Snapshots
Note: Devices will not be available or visible if they have not been enabled through the SAN Management page. NDMP and Snapshots The Titan SiliconServer uses snapshots to backup data consistently and without being affected by on-going file activity. Snapshots also facilitate incremental backups. However, it is also possible to backup data without using snapshots.
Page 328 By default, Titan automatically creates a snapshot before it starts a backup operation. The backup then proceeds from the snapshot image rather than the file system. However, if the file system cannot take the snapshot for any reason, the backup proceeds directly from the live file system. Titan SiliconServer...
Page 329 Performing NDMP Backups To Configure NDMP Snapshot Options From the Home page, click Data Protection. Click Backup Snapshot Options. In the Automated Snapshot Use section, select whether NDMP should automatically create a snapshot to be backed up. This selection only affects backups or adc copies where the path refers to the live file system.
Page 330: Backing Up Virtual Volumes And Quotas
Performing NDMP Backups In the Automated Snapshot Deletion section, select when to delete the snapshot. By default, NDMP keeps the snapshot to make incremental backups more accurate. The choices are: Delete snapshot after use ❑ This will delete an automatically created snapshot after the backup, for which it was taken, is completed.
Page 331: Clearing The Backup History Or Device Mappings
When replacing an existing tape library with a new one and keeping the original device names for the new devices, the device mappings must be cleared and then the devices must be re-added in the desired order. Titan SiliconServer...
Page 332: Using Storage Management Applications
Performing NDMP Backups To Clear the Backup History or NDMP Device Mappings From the Home page, click Data Protection. Then, click Backup History. Clear Backup History clears records of old backups. New backups will be full rather than incremental. Clear Device Mapping re-establishes mappings with fibre channel devices. Using Storage Management Applications Titan acts as the NDMP host and operates with leading storage management applications.
Page 333 • Start with the letters tmp in the directory /dir1 • Are called core • End with the characters .o The command is case-sensitive if backing up an NFS export but not if backing up a CIFS share. Titan SiliconServer...
Page 334 Performing NDMP Backups EXTRACT Possible value Notes y or n The default value y causes a recovery operation to extract files from a file list rather than recover the whole backup. FILESYSTEM Possible value Notes Name of directory to The Storage Management Application will set the FILESYSTEM variable to back up the name of the path to be backed up.
Page 335 “^a3^”. To avoid confusion the caret symbol itself is doubled in names in ASCII or ISO8859. Note that this usage varies from that in Si7500/Si8x00 and it may not be possible to explicitly select such files for recovery from old backups. Titan SiliconServer...
Page 336 Performing NDMP Backups NDMP_BLUEARC_FH_NAMETYPE Possible value Notes UNIX or NT Specifies the name type that the system passes to the storage management application in the file history information. NDMP allows files to be described as either UNIX files or NT files. By default, Titan’s NDMP implementation describes files under an NFS export as UNIX files and those under a CIFS share as NT files.
Page 337 “Delete snapshot after use”, LAST is the same as “Delete snapshot after next backup” and OBSOLETE is the same as “Delete snapshot when obsolete”. NDMP_BLUEARC_TAKE_SNAPSHOT Possible value Notes y or n Used to override the "Automatic Snapshot Creation" Backup configuration option. Titan SiliconServer...
Page 338 Performing NDMP Backups NDMP_BLUEARC_USE_CHANGE_LIST Possible value Notes y or n Indicates if incremental backups or replications will use a changed object list to direct the search for changed files. If the process were not use the changed object list, it will have to search the entire directory tree looking for changed files.
Page 339 This setting is not recommended as files backed up in this way are only partially included in the backup and cannot be recovered from this single backup - a full correct sequence of backups must be recovered to recreate the file. Titan SiliconServer...
Page 340 Performing NDMP Backups NDMP_BLUEARC_SPARSE_FILE Possible value Notes Comma-separated Allows control of sparse file/block level incremental processing. If this list of files or variable is specified then only files on the list will be considered for directories. sparse transfer. A list of files similar in format to that specified by the EXCLUDE variable.
Page 341: Important Notes
Similarly, if a directory has been moved there is no way of knowing that the contents of the moved directory have changed. Therefore contents of moved directories will not be backed up unless the individual files have themselves changed.” Titan SiliconServer...
Page 342: Compatibility With Other Siliconservers
Three possible actions are: ADC copies and incremental data replications between Si7500/Si8x00 servers ❑ and Titan SiliconServer will be performed correctly without requiring any specific action. Tape backups from a Si7500/Si8x00 server can be recovered to Titan without any ❑...
Page 343 File transfer times for Titan are in nanosecond units and on Si7500/Si8x00 ❑ servers in 100 nanosecond units. Transferring files, therefore, from Titan to a Si7500/Si8x00 server and back may cause a very small change in the file times seen. Titan SiliconServer...
Page 344: Policy-Based Data Replication
These optional settings are explained later in this section. Incremental Data Replication The Titan SiliconServer provides support for Incremental Data Replication (IDR). IDR is performed under control of the System Management Unit (SMU). IDR uses the same data...
Page 345: Incremental Block-Level Replication
Data Protection • A File System or directory within the same Titan SiliconServer. BlueArc’s Multi-Tiered Storage (MTS) technology ensures that replications that take place within a Titan SiliconServer are performed efficiently, without tying up network resources. • A File System, Virtual Volume, or directory on another Titan.
Page 346: Creating Replication Policies
Policy-Based Data Replication Creating Replication Policies The Titan SiliconServer provides a wizard where administrators can add and setup polices for how data replication will occur. The SMU can manage replication jobs from multiple Titan SiliconServers and their associated storage subsystems. Before administrators can add a replication policy the type of server that will be used for storing the replicated data must be determined.
Page 347: Replication Policies
Adding a replication policy - managed server From the Policy Destination Type page, click Next to display the following page. Item/Field Description Identification The name of the replication must not contain spaces, or any of the characters: \/<>"'!@#£$%^%&*(){}[] +=?:;,~`|.' Titan SiliconServer...
Page 348 Policy-Based Data Replication • SiliconServer: The name of the SiliconServer where the replication will Source be created. • EVS/File System: The name of the and File System to which the replication is mapped. Click change… to change the EVS/File System. •...
Page 349 From the Policy Destination Type page, click Next to display Policy Identification page. When the Not Manage Server option is selected, the following screen is displayed. Item/Field Description Identification The name of the replication must not contain spaces, or any of the characters: \/<>"'!@#£$%^%&*(){}[]+=?:;,~`|.' Titan SiliconServer...
Page 350 Policy-Based Data Replication SiliconServer: The name of the SiliconServer where the replication will ❑ Source be created. EVS/File System: The name of the and File System to which the ❑ replication is mapped. Click change… to change the EVS/File System. Path: select the Virtual Volume by using the drop-down list.
Page 351 The post-replication script is executed after a successful replication. Potential uses of pre-replication and post-replication scripts are illustrated in the following examples: To backup a database A pre-replication script can be used to backup database files. Typically, this pre-replication script will need to: Titan SiliconServer...
Page 352: Replication Rules
The Titan SiliconServer is configured with default values which should be optimal in most cases. However, these values can be changed to customize replication performance characteristics based on the data set.
Page 353 A check in the box indicates that the rule is being used by one or more policies. Details Click the details button next to the rule to view the complete details regarding it. Select a Rule and click remove to delete it Titan SiliconServer...
Page 354 Policy-Based Data Replication To add a Replication Rule From the Home page, click Data Protection. Then, click Replication Rules. Click Add. The Add Rule page appears. The fields on this screen are described in the table below: Item/Field Description Name Name of replication rule.
Page 355 In these cases, adding additional processes may speed up the replication operation. Note: Each additional read-ahead process takes up system resources, so it is best to limit the number of additional processes unless it makes a significant difference in performance. Titan SiliconServer...
Page 356 Policy-Based Data Replication Pause While Replication(s) By default the data management engine imposes an interlock Finish Writing to stop "NDMP" backups and "adc" copies from the destination of a replication while a replication copy is actively writing data. This is intended to help installations that replicate to a volume and back up from there.
Page 357 Data Migrator path to indicate the target volume. If set to disabled, all the files and their data will be written directly to the replication destination volume. Titan SiliconServer...
Page 358: Replication Files To Exclude Syntax
Policy-Based Data Replication Replication Files to Exclude Syntax Replication "Files to Exclude" statements, each containing a number of expressions identifying which directories or files to exclude from the replication can be written using the following guidelines: Note: BlueArc recommends creating the "Files to Exclude" list before the initial replication copy, and not changing it unless necessary.
Page 359 Failed replication jobs will display a red light and the reason for failure. Note: In case of a replication failure, the next time a replication is started the data management engine attempts to restart the failed replication instead of starting a new replication. Titan SiliconServer...
Page 360 Policy-Based Data Replication Actions Click Add to add a new schedule from the Add Replication Schedule page. Click Remove to clear a selected schedule from the list. To add a Replication Schedule From the Home page, click Data Protection. Then, click Replication. Under Schedules, click add schedule a new replication.
Page 361 That means waiting 8 or more days between replication runs could result in a full replication. Click OK to add the schedule and return to the Replication page. Click cancel to clear the screen and return to the Replication page. Titan SiliconServer...
Page 362 Policy-Based Data Replication To modify a Replication Schedule Once defined, schedules can be easily modified to meet the changing requirements of the Replication Policies. When modifying a schedule, the scheduled date and time, as well as the interval in which the schedule will run can be changed. From the Replication page, select a schedule to modify.
Page 363: Scheduling Incremental Replications
Summary page. The information contained in the Report Summary provides a detailed view of the replication job results. This information can be used to make adjustments in the replication policy and schedule that can improve the overall replication efficiency. Titan SiliconServer...
Page 364 Policy-Based Data Replication The fields on this screen are described in the table below. Item Description Schedule ID Displays the ID number for the completed replication. Policy Displays the policy's name. Completed Displays the month, date, year and time when the replication was completed.
Page 365 Item Description Replication Policy Displays the completed replication policy's name. Schedule ID Displays the replication schedule ID. Status Indicates whether the replication was successfully completed. Frequency Displays how often the Policy is scheduled to run. Titan SiliconServer...
Page 366: Troubleshooting Replication Failures
Policy-Based Data Replication Start Time Displays the date and time when the replication began. End Time Displays the date and time when the replication ended. Duration Displays the time taken to complete the replication. Server/EVS Displays the EVS on which the Source and Destination File System reside. Bytes Transferred Displays the volume of data in Bytes that were replicated.
Page 367 From the Data Protection heading, click on Replication to view the replication page. From the Schedules table, click on the Details button for the failed replication to view the Replication Schedule page. Click the Rollback button to rollback the target file system to the state of the last successful replication. Titan SiliconServer...
Page 368: Virus Scanning
As the spread of viruses increases, organizations are looking for solutions that can detect and quarantine them. To address this growing issue, BlueArc is working with industry leading anti- virus (AV) software vendors to ensure that the Titan SiliconServer integrates into an organization’s existing AV solutions and without requiring special installations of AV software and servers.
Page 369: Virus Scanning Overview
Titan provides statistics to monitor virus scanning activity. Configuring Virus Scanning To configure virus scanning, the following steps are required: Configure the Virus Scan Engine(s). Enable anti-virus support on Titan. Optionally disable virus scanning on selected CIFS shares. Titan SiliconServer...
Page 370 Virus Scanning Supported Platforms Symantec Anti Virus Scan Engine (SAVSE) 4.3 ❑ ® ® McAfee VirusScan with RPC support 7.1.0 ❑ Sophos Antivirus for NetApp 1.0.1 ❑ Trend Micro ServerProtect 5.31 with RPC support ❑ Important Information on Virus Scanning Configuration The account used to start the scanning services on the Virus Scan Engine must be added to ❑...
Page 371 Data Protection To Enable Virus Scanning on the Titan SiliconServer From the Data Protection page, click Virus Scanning. Titan SiliconServer...
Page 372 To Take a Virus Scan Engine Out of the Configuration When the IP address of a Titan SiliconServer is added to a Virus Scan Engine’s list of RPC clients, the Virus Scan Engine will automatically register itself with the Titan SiliconServer.
Page 373: Forcing Files To Be Rescanned
From the Home page, click Data Protection. Then, click Virus Scanning. Click Request Full Scan. This flags all file types in the Inclusion List to be re scanned the next time a user attempts to access them. Titan SiliconServer...
Page 374: Chapter 8. Scalability And Clustering
Scalability and Clustering Scalability and Clustering Overview The Titan SiliconServer can be configured for standalone operation or as a two-node Active/ Active (A/A) High-Availability (HA) cluster. Through shared storage and centralized management, multiple Titan SiliconServers and HA clusters can be joined together as a logical unit called a Server Farm.
Page 375: High Availability Clusters
Maximum performance - When maximum data throughput is required, EVS can be migrated to a high-end Titan or one on which no other EVS resides. This will ensure that the EVS enjoys the fully dedicated resources of a single Titan SiliconServer. •...
Page 376 Scalability and Clustering Overview A single SMU is used to manage every server and cluster within the Server Farm. The SMU hosts the management network for the Server Farm and provides quorum services for up to eight HA clusters. Managed devices must be located in the same data center, not distributed across a campus or MAN environment.
Page 377: Using Enterprise Virtual Servers
Pool Using Enterprise Virtual Servers Titan SiliconServer can have up to eight Enterprise Virtual Servers (EVS). Likewise, an Active/ Active (High-Availability) Cluster can have up to eight EVS. An EVS can be added, deleted, and changed based on the evolving needs of the network.
Page 378 Using Enterprise Virtual Servers To add an EVS From the Home page, click SiliconServer Admin. Then, click EVS Management. Click Add EVS. The Add EVS page appears. Enter a Label for the EVS. Enter the IP Address of the EVS. Enter the Subnet Mask.
Page 379 The File System will now appear as having been assigned to the EVS on the Silicon File Systems page. The File System is ready to be mounted. Check the box next to the File System Label. Click mount. The File System should appear as Mounted in the Status column. Titan SiliconServer...
Page 380: Evs Management
Using Enterprise Virtual Servers EVS Management The EVS Management page allows EVS to be added, deleted, enabled, and disabled. Item Description Type Type of service (administration or file). Label The EVS label. The label is used to help identify the different configured EVS.
Page 381 Click Disable EVS. Click Delete EVS. Note: Deleting an EVS does not affect the file system owned by the EVS. Once the EVS has been deleted, assign the file system to another EVS to make it available for use. Titan SiliconServer...
Page 382: Titan High Availability Clusters
Cluster Nodes Each Titan SiliconServer that is a member of a cluster is referred to as a Cluster Node. In a cluster, EVS can be hosted simultaneously on both Cluster Nodes. Titan clustering keeps file services separate from the Cluster Node on which these services reside. Network users use IP addresses that are associated with the EVS rather than with the Cluster Nodes.
Page 383 When the Titan SiliconServer is configured as a cluster, each Cluster Node mirrors the NVRAM of the other node, thus ensuring data consistency in the event of a hardware failure of a Cluster Node.
Page 384: Creating A Cluster
Titan High Availability Clusters Cluster Nodes are also connected directly using the High Speed Interconnect (HSI). This dedicated network consists of dual redundant Gigabit Ethernet (GE) links, and is used for clustering traffic and data protection, i.e. NVRAM mirroring. Creating a Cluster Configuring two Titan SiliconServers to operate in a cluster requires the following steps: Ensure that one of the servers has an A/A cluster license.
Page 385 Scalability and Clustering To configure the first Cluster Node From the Home page, click SiliconServer Admin. Then, click Cluster Wizard. Click Promote to Active/Active. Enter the Cluster Node IP Address and Subnet Mask. The Port is automatically assigned to mgmnt1. Titan SiliconServer...
Page 386 The following details the steps necessary to join a node to a cluster using the Web Manager GUI. Connect to the built-in RS232 port of the unconfigured Titan SiliconServer that will join the cluster as described in Using the Command Line Interface.
Page 387: Managing A Cluster
The server will automatically reboot. Managing a Cluster The following sections explain how to manage the cluster including cluster services (file services and server administration) and the physical elements which form the cluster (cluster nodes and the quorum device). Titan SiliconServer...
Page 388 Titan High Availability Clusters Configuring the Cluster On the SiliconServer Admin page, click Cluster Configuration. Item Description Cluster Mode Single node or Active/Active (A/A). Cluster Name Name of cluster. Overall Status Overall cluster status (online or offline). Cluster Health Cluster health: •...
Page 389: Managing Cluster Nodes
If the QD is removed from the cluster, the port will be released back to SMU’s pool of QDs and ports. Managing Cluster Nodes From the SiliconServer Admin page, click Cluster Nodes. This screen shows the following: Item Description Name Name of Cluster Node. IP Address IP address of Cluster Node. Titan SiliconServer...
Page 390 Titan High Availability Clusters Status Status of Cluster Node: • Online. The Cluster Node is a part of the cluster and is exchanging heartbeats with the other cluster members. • Offline. The Cluster Node is no longer exchanging heartbeats with the other cluster members. This may be caused by a reboot, or the Cluster Node may be have suffered a fault condition.
Page 391: Cluster Name Space
QD services provided to clusters throughout a Server Farm. Cluster Name Space When deployed on a Titan SiliconServer, the Cluster Name Space (CNS) allows separate and physically discrete file systems to appear as a single logical file system, i.e. a unified file system.
Page 392: Cns Topology
Cluster Name Space been created, create a single CIFS share and NFS export on the CNS root. Then, add a File System Link for each physical file system under the root directory. In such a configuration, all of the server’s storage resources will be accessible to network clients through a single share or export, and each file system will be accessible through its own subdirectory.
Page 393: Creating A Cluster Name Space
File System Links make physical file systems accessible through the CNS. A File System Link can be associated with either the root directory or a subdirectory in a physical file system. Once created, a File System Link will appear as a directory in the CNS. The directory name seen by a Titan SiliconServer...
Page 394: Editing A Cluster Name Space
Cluster Name Space client will be the name given to the File System Link. A client navigating through CNS and into a File System Link will see the contents of the directory that was linked. Move to the SMU Home page. From the File Services heading, click on CNS to view the CNS page.
Page 395 From the CNS tree, select the link that needs to be changed. From the box at the bottom of the page, click on Modify to view the Modify File System Link page. If the link name must be changed, use the Link Name text box to make the change. Titan SiliconServer...
Page 396: Considerations When Using Cns
Migrating an EVS If the parent directory must be changed, then from the Select a New Parent Directory options box, select a new location in the CNS tree. From the bottom of the page, click OK to add or change the CNS link. To Delete a File System Link Deleting a File System Link will erase the link from the CNS.
Page 397 From the SiliconServer Admin page, click EVS Migrate. Note: This screen will only appear if the SMU is managing multiple Titan SiliconServers in a Server Farm. Otherwise, clicking EVS Migrate will immediately launch the EVS Migrate page shown in step 2. Titan SiliconServer...
Page 398 Migrating an EVS Click the first option, Migrating an EVS from one node to another within the same AA Cluster. The EVS Migrate page appears with several options: To migrate all EVS between Cluster Nodes Select the Migrate all cluster services from Node ___ to Node ___ radio button. Using the drop-down menu, select the Cluster Node from which to migrate all EVS.
Page 399: Migrating An Evs Within A Server Farm
EVS, settings from the source server can be applied to it through Server Cloning. For information about specific settings that can be cloned, refer to Cloning from another Titan SiliconServer. To Clone Server settings Select the target of the EVS migration as the SMU’s managed server. Titan SiliconServer...
Page 400 Migrating an EVS From the Home page, click SiliconServer Admin. Then, click Clone SiliconServer Settings. Select the server currently hosting the EVS that will be migrated from the Clone the selected configuration from drop-down menu. Click next. Select the settings that should be migrated to the target server. Caution: Settings selected for cloning will overwrite the currently defined settings on the target server.
Page 401 From the SiliconServer Admin page, click EVS Migrate. Note: This screen will only appear if the current managed server is an HA cluster. Otherwise, clicking EVS Migrate will immediately launch the EVS Migration page shown in step 2. Titan SiliconServer...
Page 402 Migrating an EVS Click the second option, Migrating an EVS from one system to a different unconnected system. The EVS Migration page appears: Select the desired EVS on the source server or select a different source server by clicking Change…. Using the drop-down menu in the Destination Server field, select the server to which the EVS should be migrated.
Page 403: Chapter 9. Status & Monitoring
Status & Monitoring Status & Monitoring Overview Web Manager provides integrated and complete storage management of the Titan SiliconServer and its storage subsystem. Color-coded status information on the various devices installed on the BlueArc Storage System is provided through the management screens. In addition, Titan provides a comprehensive event logging and alerting mechanism, which can notify the system administrator as well as BlueArc Global Services as soon as a problem occurs.
Page 404 BlueArc Storage System Status Using the Server Status Console Summary status information pertaining to the Titan SiliconServer that is the currently managed server can be viewed from the Web Manager’s server console, in the home page of the Titan SiliconServer.
Page 405: Checking The System Status
(see table below). Status information is cached by the SMU and refreshed every 60 seconds; so it may take this long to see changes in the System Monitor. Titan SiliconServer...
Page 406 BlueArc Storage System Status When displaying status of a device using a colored LED, the following conventions apply: Color Status Means that the item is Information Is operating normally and not displaying an alarm condition Warning Needs attention, but does not necessarily represent an immediate threat to the operation of the system Severe Has failed in a way that poses a significant threat to the operation...
Page 407 Home page for the device. To change the position of any of the items on this screen, select the item (place a tick in the checkbox) and use the arrows in the Action box. Titan SiliconServer...
Page 408: Checking The Status Of A Server Unit
BlueArc Storage System Status Checking the Status of a Server Unit From the Status & Monitoring page, click Server Status. The table below describes the items on this screen: Item Description Primary cluster The status of the first cluster interconnect link. interconnect Secondary cluster The status of the second cluster interconnect link.
Page 409: Checking The Status Of A Power Unit
Node from the drop-down list. Checking the Status of a Power Unit In the SiliconServer Admin page, click UPS Status. The following dialog box will appear: This screen displays the following: This field Shows The IP address of the System Power Unit. Titan SiliconServer...
Page 410: Checking The Status Of A Storage Unit
BlueArc Storage System Status Status Indicates whether or not the unit is currently supplying battery power to the system, and whether or not the batteries are low or need replacing. Charge The percentage of battery capacity that is currently available. Runtime Remaining The number of minutes for which the System Power Unit is capable of providing battery power to the system.
Page 411 Status & Monitoring Click details. Titan SiliconServer...
Page 412 BlueArc Storage System Status Item/Field Description Identification Rack Information: • Name: Name of the FC-14 RAID Rack. Enter a new RAID Rack name which is used to identify the FC-14 RAID Rack. • WWN: Worldwide name for the FC-14 RAID Rack. •...
Page 413 To view detailed information on a RAID controller or physical disk, click the physical disk. The upper half of the dialog box shows the physical disks associated with the RAID racks. The color of a disk indicates its status. Titan SiliconServer...
Page 414 BlueArc Storage System Status Status Description Color Gray The disk is not present in the enclosure or it has not been configured. Blue The disk is present and, if there is no overlay, functioning normally and part of a System Drive. The Web Manager may qualify this status with the following overlays: •...
Page 415: Checking The Status Of The Smu
Status & Monitoring • RAID Controllers • Temperature • Physical Disks Checking the Status of the SMU To view the current status of the SMU, from the SMU Administration page, click SMU Status. Titan SiliconServer...
Page 416 BlueArc Storage System Status The SMU Status page displays the services available, the current status of each service and the option to restart each service if necessary: Services Description SMU Titan Proxy Used to allow communication from the SMU to Titan SiliconServers. Quorum Device Used by a Cluster which has become partitioned by a network failure, to determine which partition is allowed to talk to the storage.
Page 417: Monitoring Multiple Servers
The IP address of the server. This should be the Administration Services IP address as used on the private management network e.g. 192.0.2.x Username The username used to access the Titan SiliconServer. Model The model type, e.g. Titan. Cluster Type The cluster type, e.g.
Page 418: Titan Siliconserver Statistics
Titan SiliconServer Statistics Details A link to a page displaying detailed information used to contact or to manage the server. Set as Current Select the server as the currently managed server. In the Actions frame, managed servers can be added (Add) or removed (Remove) from the displayed list.
Page 419 The receive and transmit rates for both current (instantaneous) and peak throughput. Receive Errors The total number of errors received per source. Transmit Errors The total number of errors transmitted per source. The Reset Statistics button will reset all the values to zero. Titan SiliconServer...
Page 420 Titan SiliconServer Statistics To view Per Port Ethernet Statistics From the Status & Monitoring page, click Ethernet Statistics (per port). This will generate statistics for each defined port. System Administration Manual...
Page 421 From the Home page, click Status & Monitoring. Then, click Ethernet History. Both per-port and overall histograms are available. The screen displays the number of bytes/second received and transmitted. If configured as a cluster, select the Cluster Node for which to view the Fibre Channel History. Titan SiliconServer...
Page 422: Tcp/Ip Statistics
Titan SiliconServer Statistics TCP/IP Statistics The TCP/IP statistics display the activity since the last Titan reboot or since the TCP/IP statistics were last reset. Both per-port and overall statistics are available. The statistics are updated every ten seconds. To view TCP/IP statistics From the Status &...
Page 423 Transmitted: the number of transmitted IP packets. Received: the number of received IP packets. Unknown Protocol: the number of unknown protocol packets. Invalid: the number of invalid IP packets. The Reset Statistics button will reset the values in this dialog box. Titan SiliconServer...
Page 424 Titan SiliconServer Statistics To view Per Port TCP/IP Statistics From the Status & Monitoring page, click TCP/IP Statistics (per port). This will generate the detailed statistics for each of the defined ports. The Reset button will reset all the statistics of the selected port to zero.
Page 425 The Reset button will reset all the statistics of the selected port to zero. The Reset all ports button will reset all the statistics on all ports to zero. To view TCP/IP Detailed Statistics From the Status & Monitoring page, click TCP/IP Detailed Statistics. This field Shows the number of Titan SiliconServer...
Page 426: Fibre Channel Statistics
Titan SiliconServer Statistics Cluster Nodes If configured as a cluster, select the Cluster Node on which to display detailed TCP/IP Statistics. IP Errors Invalid Header Field IP errors from an invalid header field. Oversized Segment Fragmented TCP packets greater than the MTU size when re- assembled.
Page 427 FC: Instantaneous and Peak. I/O Requests The number of read and write requests that the attached storage devices have received and sent: Total Requests and Total Responses. Total Requests and The total number of requests received and responses Responses transmitted. Titan SiliconServer...
Page 428 Titan SiliconServer Statistics Cache The number of hits (requests that the cache has served) and misses (requests not served by the cache and passed to the storage subsystem). I/O Status Counters The numbers of failed and resubmitted input and output requests.
Page 429: File And Block Protocol Statistics
File and Block Protocol Statistics Titan provides statistics to monitor data access via the following network protocols: (NFS) • Network File System (CIFS) • Common Internet File System (FTP) • File Transfer Protocol (iSCSI) • Internet Small Computer System Interface Titan SiliconServer...
Page 430 Titan SiliconServer Statistics NFS Statistics statistics display the activity since the last Titan reboot or since the NFS statistics were last reset. The statistics are updated every ten seconds. From the Home page, click Status & Monitoring. Then, click NFS Statistics.
Page 431 PathConf Retrieves POSIX information for the file system. Commit Commits the cached data on the server to stable storage. Access Gets the file security accesses for a file. The Reset button will reset all the values to zero. Titan SiliconServer...
Page 432 Titan SiliconServer Statistics CIFS Statistics CIFS statistics display the activity since the last Titan reboot or since the CIFS statistics were last reset. The statistics are updated every ten seconds. From the Home page, click Status & Monitoring. Select CIFS Statistics.
Page 433 Connects the client to a file system resource. Tdis Breaks a connection that a TconX call previously established. Trans Multifunction command for operating subfunctions. Trans2 Multifunction command for operating subfunctions. UlogoffX Breaks a connection that a SessSetupX call previously established. Titan SiliconServer...
Page 434 Titan SiliconServer Statistics Unlink Deletes a file. Write Writes data to a file. WriteBraw Write a block of data with no CIFS header. WriteClose Writes data to a file and then closes the file. WriteX Writes data to a file.
Page 435 Total Data Bytes Bytes of data that the server has transferred to clients since you Outgoing last started the server or reset the statistics. The Reset button will reset all the values of the FTP Statistics to zero. Titan SiliconServer...
Page 436 SCSI statistics. To reset all the statistics to zero, click the Reset Statistics button. Item / Field Description Current Number of The number of iSCSI sessions currently hosted by Titan. Session iSCSI Requests NopOut No operation. Titan SiliconServer...
Page 437 Titan SiliconServer Statistics Task Management Requests used for task management functions. Text Requests used to negotiate behavior. Logout Logout requests SCSICommand Carries a SCSI Command Login Login requests SCSIDataOut Requests containing SCSI data. SCSI Requests TestUnitReady Tests that the target is ready to receive commands.
Page 438: Data Access And Performance Statistics
UI, a graphic representation of the number of ops/sec it is performing can be viewed. Ops/sec can be viewed at two levels: • The total number of operations performed by a specific Titan SiliconServer. • The number of operations performed by individual file systems.
Page 439 Titan SiliconServer Statistics To view ops/sec statistics From the Home page, click Status & Monitoring. Then, click Node Ops/Sec or File System Ops/Sec. If File System Ops/sec was selected, select between one and five file systems to view under Select 1-5 File Systems. Hold down the Ctrl key while clicking to select more than one file system.
Page 440: Management Statistics
The Web Manager updates the management statistics every ten seconds. From the Home page select Status & Monitoring then select one of the items in the Management Access Statistics section, i.e. Telnet, or SSC; a screen similar to the following will Titan SiliconServer...
Page 441 Titan SiliconServer Statistics be displayed: This statistic Shows Sessions Current Active The number of sessions that are currently in progress. Sessions Max Sessions The peak number of concurrent sessions. Total Sessions The total number of sessions. Rejected Sessions The number of failed attempts to establish a connection. A...
Page 442 Status & Monitoring Bytes Transmitted The number of data bytes that the system has sent to clients. Bytes Received The number of data bytes that clients have sent to the system. Titan SiliconServer...
Page 443 Titan SiliconServer Statistics SNMP Management Statistics SNMP management statistics are displayed since Titan was last started or when it was last reset. The Web Manager updates the management statistics every ten seconds. From the Status & Monitoring page, click SNMP Management Statistics.
Page 444 Sent PDUs receiving an error-status field value of genErr. Get Nexts Get-Next PDUs sent. Get Responses Get-Response PDUs sent. Too Bigs Sent PDUs receiving an error-status field value of tooBig. Bad Values Sent PDUs receiving an error-status field value of badValue. Titan SiliconServer...
Page 445 Titan SiliconServer Statistics Get Request Get-Request PDUs sent. Set Requests Set-Request PDUs sent. Traps Trap PDUs sent. Drops Silent Drops PDUs delivered but silently dropped because the size of a reply containing an alternate response PDU with an empty variable-bindings field was greater than either a local constraint or the maximum message size associated with the originator of the requests.
Page 446: Event Logging And Notification
Reset Statistics will reset all values to zero. Event Logging and Notification The Titan SiliconServer provides a comprehensive event logging and alert mechanism. In addition, auxiliary devices in the storage subsystem automatically direct any events and SNMP traps to Titan, or can be configured to do so.
Page 447: Using The Event Log
From the Home page, click Status & Monitoring. Then, click Event Log. In a cluster, select the Cluster Node for which to display the log. The default is the first Cluster Node. To view the other Cluster Node, select from the drop-down list (Cluster Nodes) the other Cluster Node. Titan SiliconServer...
Page 448 Information Green Warning Yellow Severe Orange Critical The Refresh Log button will regenerate the log according to the criteria selected. The Page Forward and Page Back buttons allow the events to be viewed one page at a time. Titan SiliconServer...
Page 449 Event Logging and Notification Click an event for more details. A dialog box will be displayed with the cause and resolution. To empty the log, click Clear Event Log. Titan SiliconServer...
Page 450: Setting Up Event Notification
A Syslog alert, enables the user to send alerts from a Titan Server to a UNIX’s system log, (the UNIX system must also have its syslog daemon configured to receive remote syslog messages). See Setting Up Syslog Notification for more information. Titan SiliconServer...
Page 451 Email Profiles: Email profiles allow distribution groups to be created so email recipients are properly notified based on alert threshold criteria. To Configure Email Alerts From the Home page, click Status & Monitoring. Then, click Email Alerts Setup. Titan SiliconServer...
Page 452 Name notifications to the defined SMTP Secondary Server. Tip: As the Titan SiliconServer should always be in contact with the SMU, it is recommended that the SMU’s eth1 IP address be defined as the Primary SMTP server. The SMU can be configured...
Page 453: Field Description
Send Empty By default, the Send Empty Emails button will be checked. Empty summary Emails emails will be sent to the specified recipient when this is selected. To avoid sending empty summarized Emails, remove the check in the box. Titan SiliconServer...
Page 454 Displays the current recipient's Email Address. Enter the Email Address of the recipient about to be added to the profile. Recipient Click X to delete the selected recipient from the current profile. Click add to add the specified recipient to the current profile. Titan SiliconServer...
Page 455 Titan, and the other from the SMU. Titan’s Daily Status Email Titan’s Daily Status Email contains logs of server performance and battery health, descriptive information regarding the health of the server and storage subsystem, and the current space utilization of the file systems. Titan SiliconServer...
Page 456 BlueArc Global Services should a problem occur, and, if necessary, the restoration of a known good configuration should it be required. Titan SiliconServer...
Page 457 Check to send a monthly diagnostic email to BlueArc. This email will Emails send a copy of all server, SMU, and storage array configuration to BlueArc. This information is kept private and will only be referenced if a service call is placed with BlueArc Global Services. Titan SiliconServer...
Page 458 Status & Monitoring Use the down arrow button to add more email addresses. Use the X button to delete selected email addresses. Use the apply button to register the additions, changes on the screen. Titan SiliconServer...
Page 459 To delete a recipient, select it from the Windows popup recipients list and click the Delete Recipient button. Delete All To delete all recipients click the Delete All Recipients button. Recipients When all fields have been completed, click Apply. Titan SiliconServer...
Page 460: Setting Up An Snmp Agent
The version of the SNMP protocol with which requests must comply. • The community names of the SNMP hosts and their associated access levels. • The IP address or name of hosts from which requests may be accepted (or just choose to accept requests from any host). Titan SiliconServer...
Page 461 Send Select this checkbox if the SNMP agent is to send a trap in the event of an Authentication authentication failure (caused, for example, by the SNMP host using an Trap incorrect community string when formulating a request). Titan SiliconServer...
Page 462 To send traps to a specific port number, enter the port number in the specified field. Receive traps To receive traps on a specific port, enter the port number in the specified field When all fields have been completed, click Apply. Titan SiliconServer...
Page 463 The status of the Ethernet link has changed from Down to Up. To set up SNMP notification From the Home page, click Status & Monitoring. Then, click SNMP Traps Setup. Item/Field Description Notification Frequency By using the drop-down list, select the notification frequency for each type of alert Titan SiliconServer...
Page 464 To delete all recipients click the Delete All Recipients button. Setting Up Syslog Notification From the Home page, click Status & Monitoring. Then, click Syslog Alerts Setup. The fields on this screen are described in the following table: Titan SiliconServer...
Page 465 From the Home page, click Status & Monitoring. Then, click Send Test Event. Select a type of message to send from the drop down page, information/warning/ critical, and then enter a test message in the empty box. Click Send Test Event Now. Titan SiliconServer...
Page 466: Chapter 10. Maintenance Tasks
Maintenance Tasks Maintenance Tasks Maintenance Tasks Overview Various administration tasks for the Titan SiliconServer, such as firmware upgrades, system configuration backup and restore, etc. are explained in this section. Checking Version Information When requesting technical support, it is important to have version information about Titan firmware and hardware.
Page 467 Checking Version Information To display version information for a Titan SiliconServer From the SiliconServer Admin page, click Version Information. If configured as a cluster, select the Cluster Node from the drop-down list to view the current version information. Titan SiliconServer...
Page 468 Maintenance Tasks To display version information for the SMU From the Web Manager home page, click the About button at the top right corner of the screen. Titan SiliconServer...
Page 469: Saving And Restoring The Server's Configuration
The configuration can be backed up at any time and saved files can be archived on a PC or workstation. Configuration files maintained on the SMU, or archived on a different system, can be restored to the Titan SiliconServer. Caution: Restored configurations may have different (older) passwords.
Page 470 Click the restore button. The file will be uploaded to Titan. Reboot the server for the changes to take effect. To Delete an Auto-Saved Configuration file To delete an Auto-Saved Configuration file, select it from the displayed list. Then, click delete. Titan SiliconServer...
Page 471: Saving And Restoring The Smu's Configuration
From the Home page, click SMU Administration. Then, click Standby SMU. Enter the host name or IP address of the Standby SMU in the Public Name/IP of standby SMU field. This IP address must be the eth0, not the eth1 IP address of the Standby SMU. Titan SiliconServer...
Page 472 SMU fails those backups would not be recoverable. Automatic Backup of the SMU Configuration The SMU is set up to have its configurations backed up automatically. The SMU backups are created: Titan SiliconServer...
Page 473 Log in as root, i.e. ‘su -’. When prompted enter the configured root password. Change into the directory in which the configuration backups reside. The value for <SMU_IP> should be the IP address of the eth0 interface on the Primary SMU. cd /var/cache/SMU/smu_backup/<SMU_IP>/ Titan SiliconServer...
Page 474: Upgrading System Software And Firmware
Click delete. Upgrading System Software and Firmware The System Management Unit (SMU) software and Titan SiliconServer firmware can be upgraded to a newer release. Note: SMU software and Titan Server firmware are upgraded at the same time.
Page 475: Upgrading Titan Server Firmware
SMU upgrade process. Upgrading Titan Server Firmware A Titan SiliconServer can store up to three firmware packages in flash memory. Any one of these images can be selected to run automatically when Titan is rebooted. Such a package is known as the default package. The package being run on Titan at any given time is known as the current package.
Page 476 If the server is a Managed Server, use the drop-down list to select the correct ❑ server to upgrade the firmware package. If the server is Not a managed server, enter the IP Address, Username, and ❑ Password of the SiliconServer. Titan SiliconServer...
Page 477 Check the box to reboot Titan once the package has been uploaded. on Completion Caution: If configured in a cluster, the package will be uploaded to each Cluster Node. If a reboot is requested, both Cluster Nodes will reboot. When all the fields have been completed, click Apply. Titan SiliconServer...
Page 478 Item/Field Description Free Space The amount of free space in flash. Package List Lists all the available packages in flash. Set Default Select the required package and click the Set Default button. Titan SiliconServer...
Page 479: Providing An Ssl Certificate
If other values must be used, a custom private key may be generated via the following steps: Log onto the SMU (through ssh or through its serial port) as the user manager, then type: sudo cert-gencustom.sh Enter the manager user’s password when prompted. Titan SiliconServer...
Page 480 Certificate Signing Request into the Web page. To generate a CSR Log onto the SMU (through ssh or through its serial port) as the user manager, then type: sudo cert-gencsr.sh Enter the manager user’s password when prompted. Titan SiliconServer...
Page 481: Acquiring A Ssl Certificate From A Certificate Authority (Ca)
Note: Any alias may be used so long as it’s unique. If the alias already exists, you will be prompted to replace the old certificate or cancel the import. Next, the signed “Certificate Reply” from the CA may imported (replacing the default SMU SSL certificate): sudo cert-importcert.sh <path to cert file> Titan SiliconServer...
Page 482: Accepting Self-Signed Certificates
For each server, click "details" and then "OK". Accepting Self-Signed Certificates If a self-signed certificate has been installed, users receive a security alert similar to the following when they first access the Web Manager over a secure connection: Titan SiliconServer...
Page 483 In Internet Explorer, from the Security Alert dialog box, click View Certificate to display the certificate: Click Install Certificate, and then follow the on-screen instructions to install the certificate in the Trusted Root Certification Authorities store. Mozilla-based browsers will see an alert message similar to the following. Selecting Accept the Titan SiliconServer...
Page 484: Shutting Down / Restarting The System
During normal operation, first shut down the server before turning off the power. The shutdown process flushes the data in the cache to disk as a safeguard against the risk of data loss. Shutting Down / Resetting the Titan SiliconServer To reset or shut down the server: From the Home page, click SiliconServer Admin.
Page 485 To shutdown Titan properly before it is shipped, or before it is to be left un-powered for any length of time: Using the Command Line Interface, run the command "shutdown --ship". For more information, refer to Using the Command Line Interface (CLI). Power down the Titan SiliconServer by switching off both PSU modules. Titan SiliconServer...
Page 486: Shutting Down / Restarting The Smu
If the NVRAM status LED is on (either green or amber), then remove both PSU modules simultaneously for at least 10 seconds and replace. Note: If the Titan SiliconServer fails to shutdown properly or to verify that the NVRAM has not entered the battery powered back up state when the PSUs are switched off, verify that both PSU modules are removed (refer to step 4).
Page 487: Default Username And Password
Default Username and Password Default Username and Password Username Password SMU Web Manager admin bluearc SMU CLI manager bluearc root bluearc Entering this specific username and password will provide unlimited access on the SMU. Titan SiliconServer (CLI) supervisor supervisor Titan SiliconServer...

Blue Arc Titan SiliconServer System Administration Manual

Chapter 1. The Bluearc Storage System

Chapter 2. System Configuration

Chapter 3. Network Configuration

Chapter 4. Multi-Tiered Storage

Chapter 5. Storage Management

Chapter 6. File Services

Chapter 7. Data Protection

Chapter 8. Scalability and Clustering

Chapter 9. Status & Monitoring

Chapter 10. Maintenance Tasks

Quick Links

Summary of Contents for Blue Arc Titan SiliconServer