When the system is shipped from the factory, the management interface has a preconfigured IP address. When using the Setup Wizard, you connect a laptop to that interface in order to perform the initial setup tasks. For information on the Setup Wizard, see Chapter 2, “Initial System Setup”.

The management interface is always configured as an individual network interface and cannot be part of an aggregated interface.

You can modify the management interface by selecting eth0 from the following screen:

For information on the network configuration parameters you can modify, see “Standalone Network Interfaces”.

---

Caution: If you configure an incorrect IP address for the management interface, you can make NAS Manager inaccessible.

---

To see the available network interfaces and change their parameters, select the following:

To modify an interface, select it. You can change the following fields:

Enabled		Enables the interface. You cannot disable the management interface.
Set speed		Specifies the port speed of the Ethernet card. Under some circumstances, it may be useful to explicitly set the speed and duplex of a port to overcome problems with Ethernet autonegotiation. This is rarely needed so it should normally be set to the default Autonegotiate.
Set duplex		Specifies the duplex of the Ethernet connection. Under some circumstances, it may be useful to explicitly set the speed and duplex of a port to overcome problems with Ethernet autonegotiation. This is rarely needed so it should normally be set to the default Autonegotiate.
DHCP		Specifies that DHCP will be used to configure the Ethernet interface. (Another system must be the DHCP server.)
Static		Specifies that a particular IP address is required for the network interface. If you select this, you must provide the IP address and netmask.
Dedicated		Specifies the dedicated interface if the source and destination host are plugged directly in with cable or another dedicated VLAN network. This increases the speed of replication. The dedicated interface is designed for remote replication use. Note: Dedicated interfaces are an advanced option that may require configuration changes to the network infrastructure and on the remote host. You should only use dedicated interfaces if they are specifically required. A dedicated network interface is an interface, such as eth2, that has been configured to use a point-to-point connection with a single remote host. In this case, it is possible to select an interface that will communicate with the remote replication server. All network traffic to and from that server will go via the local dedicated network interface and no other traffic will appear on that interface. Dedicated network interfaces can be useful when there may be a large amount of network traffic to and from the local host and you wish to isolate the remote replication traffic to prevent interference with other network traffic such as NFS and CIFS. See “Remote Replication”.

An aggregated (bonded) interface is a virtual network interface that consists of real interfaces working in tandem. A virtual interface can provide the aggregated bandwidth of all of the interfaces that you used to create it.

---

Note: Any single client can achieve the bandwidth of only a single interface at a time. An aggregated interface increases the aggregate bandwidth for multiple clients.

---

For example, if you have three interfaces each with a bandwidth of 10, the aggregate bandwidth is 30. For an individual client, however, the maximum bandwidth remains 10. When additional clients access the aggregated interface, the clients are assigned to the subinterfaces, and up to three clients can use a bandwidth of 10 at the same time. Thus multiple clients accessing the system increase the aggregate bandwidth, improving the performance to a maximum bandwidth of 30.

For example, Figure 3-2 shows a configuration in which all clients connect to a single IP address (192.168.0.3 ). The switch is responsible for sharing the load across 4 aggregated interfaces (eth1-eth4). Therefore, 4 times as many clients can communicate with the same server without a loss in overall performance.

Figure 3-2. Aggregated (Bonded) Network Interfaces

Output load balancing controls how the server chooses which subinterface to send replies. Input load balancing controls how clients are assigned to subinterfaces, and how and when clients are moved from one subinterface to another. Load balancing happens on a per-packet basis. When a client sends a packet, it traverses a switch, which determines at which subinterface the packet arrives. Input load balancing ensures that each client arrives at a different subinterface. The clients see only one interface because the balancing is done by the system.

In addition to configuring an aggregated interface in NAS Manager, you must configure the ports on the switch so that they use either static trunking or 802.3ad dynamic trunking. For more information, refer to the user manual for your switch.

To create an aggregated interface, select the following:

The available interfaces are displayed for selection.

When you configure an aggregated interface, you specify the following:

IP address

Specifies the IP address of the new aggregated interface. Note: The IP address for an aggregated interface must be configured statically. NAS Manager does not support DHCP and dedicated IP addresses for aggregated interfaces.

Click Create to create the bond.

This section describes how to list, create, grow, and destroy filesystems on an SGI RAID device:

For background information about how NAS manager works, see Appendix A, “How NAS Manager Configures Filesystems”.

Listing Filesystems

To display a brief description of the RAID to which NAS Manager is connected, use the List option:

Management -> Resources -> Storage -> Filesystems -> List

This includes the worldwide name (WWN) of the RAID device and an indication of the RAID status, which will be ONLINE unless a hardware or software failure mode has prevented communication between NAS Manager and the array firmware (such as if the array is powered down or a cable has been pulled out).

---

Note: NAS Manager displays only the filesystems you have created through NAS Manager.

---

The Type field on this screen indicates whether the listing is a filesystem, a snapshot repository, or iSCSI storage.

If you have created a snapshot repository but have not scheduled any snapshots to be taken and stored on that repository, its size will appear as 0 on this display.

Creating Filesystems

The Create option steps you through a filesystem creation wizard. The steps that the wizard will take are listed in a box to the left of the screen, with the current step highlighted.

The filesystem creation procedure is mostly automatic. You provide the name, size, and general characteristics of the filesystem to create and NAS Manager determines the underlying layout of the filesystem on the disk devices. For information on how NAS Manager calculates how best to configure a filesystem and allocate the disk resources, see Appendix A, “How NAS Manager Configures Filesystems”.

There is a limit to the number of filesystems on a particular array. This limit is less than 30 filesystems for a 4-tray array, but it can be smaller on large arrays (because each filesystem will use 2 or 3 of the total 254 LUN numbers per tray of disks in the array). For this reason, SGI recommends that you use as few filesystems as possible on a disk array.

---

Note: When you create the filesystem, the system detects whether the disk configuration is supported and issues a warning if it is not. You can continue to create the filesystem under these circumstances, but the filesystem will not be an efficient one.

---

You can grow a filesystem after you have created it, by whatever size you choose. It is most efficient, however, if you create a filesystem that fills the disk array and add additional disks if you need to grow the filesystem, filling those disks when you do.

Perform the following steps to create a filesystem:

1. Select the Create option:

   Management -> Resources -> Storage -> Filesystems -> Create

2. NAS Manager searches for the RAID arrays on the system and displays them on the Arrays screen. Click Next.

3. The Options screen displays the filesystem configuration options. These are based on the devices that are available to the system and include the following categories:

   Drive Type		The drive type may be Serial ATA (SATA) or Fibre Channel (FC). You cannot create a filesystem that spans both types of disks.
   Goal		You can select a filesystem optimized for performance or capacity. If you select for capacity, NAS Manager will use all the available disk space to create the filesystem, although this will usually come at the cost of slower performance.
   Workload		You can select a filesystem optimized for bandwidth or for I/O per second (IOPS). Select Bandwidth when you will have a small set of files and you must perform streaming reads and streaming writes as fast as possible. Select IOPS when you will be performing random reads and writes to different sets of files. Normally, IOPS will be the better choice. If you are optimizing for IOPS, it is best to build one large filesystem. In general, there is a cost to having multiple filesystems.
   Available Space		This displays the available space in gigabytes.

   Click Next.

4. On the Name & Size screen, enter the filesystem name and the filesystem size, in gigabytes.

   The default filesystem size is the size of a filesystem that will completely fill the disk devices. If you choose less than this maximum size, the filesystem will be divided up among the disks. For example, if you create a filesystem that is 20% of the maximum size, it will be spread out among the first 20% of each disk. If you create a second filesystem that is also 20% of that maximum size, it will be spread out among the second 20% of each disk.

   ---

   Note: If you plan to use the snapshot feature you must leave enough room on the RAID disks for the snapshot repository. For example, if you have 3000 GiB of space on the RAID, you should not create a filesystem of more than 2400 GiB so that you can later create a repository of 600 GiB (20% of the size of the base filesystem). For information, see “Snapshots”.

   ---

   Click Next.

5. The Confirmation screen summarizes the filesystem options you have selected. Click Next to confirm you choices and create the filesystem.

6. The Creating screen displays a "please wait" message during the filesystem creation process. Click Next after the operation is finished and the completion message displays.

7. The NFS and CIFS screen lets you configure the filesystem so that it can be exported with NFS or CIFS network protocols. For information, see “NFS” and “CIFS”. Click Next.

8. The Finished screen indicates that the filesystem has been created. Click Done .

Growing Filesystems

To increase the size of an existing filesystem, do the following:

---

Note: You can use a filesystem normally as you grow it. (You do not need to disable access or unmount it, or take any other special actions before growing the filesystem.)

---

1. Select the Grow option:

   Management -> Resources -> Storage -> Filesystems -> Grow

2. The Filesystem screen in the wizard lists the current filesystems along with their usage and size. Select the filesystem you want to grow and click Next .

3. The Size screen displays. Enter the size in gigabytes by which the filesystem should be grown and click Next.

4. The Confirmation screen displays the current size of the filesystem and the amount to grow the filesystem. Click Next.

5. The Growing screen displays a "please wait" message during the growing process. Click Next after the operation is finished and the completion message displays.

6. The Finished screen indicates that the larger filesystem is available. Select Done.

Internet Small Computer Systems Interface (iSCSI) is a protocol that is used to transport SCSI commands across a TCP/IP network. This allows a system to access storage across a network just as if the system were accessing a local physical disk. To a client accessing the iSCSI storage, the storage appears as a disk drive would appear if the storage were local.

In an iSCSI network, the client accessing the storage is called the initiator and runs iSCSI Initiator software. The remote storage that the client accesses is called the target, which is what appears to the initiator as a disk drive.

A common application of an iSCSI network is to configure an Exchange Server as an iSCSI initiator that uses an iSCSI target as its mail store.

Figure 3-3 illustrates iSCSI storage. Each client (initiator) is configured to connect to a specific iSCSI target (an area allocated in the RAID iSCSI storage pool), and views this target as if it were a local disk. The lines in Figure 3-3 indicate data flow.

Figure 3-3. iSCSI Storage

You can use NAS Manager to create iSCSI targets on the RAID storage. An iSCSI initiator will be able to connect to the system and access those targets, format them as NTFS, and use the targets as it would use a disk drive. After the target is formatted by the initiator, it will appear by default as a drive letter.

You cannot configure NAS Manager itself as an initiator, and you cannot re-export iSCSI targets with NFS or CIFS. In addition, you cannot export existing filesystems that you have created with NAS Manager as iSCSI targets; you can create filesystems and configure them to be exported by NFS and CIFS, but you must configure iSCSI targets separately on the RAID device.

Creating iSCSI Pool and Targets

You create iSCSI targets with a creation wizard, just as you create filesystems.

Before you can create iSCSI targets with NAS Manager, you must create the iSCSI storage pool for the targets.

---

Note: Although you can grow this storage pool at a later time when you create additional targets, SGI recommends that you create a storage pool that is large enough to contain all of the targets that you will need. Creating the iSCSI storage pool can be a slow process, but once you have created the pool, creating the targets themselves is a fast process.

---

Perform the following steps to create an iSCSI target:

1. Select the Create Target option:

   Management -> Resources -> Storage -> iSCSI ->  Create Target

2. If this is the first target, the system will display a message indicating that you must create the iSCSI storage pool before you can create a target. If you have previously created iSCSI storage, you can grow the storage at this time; in this case, the screen displays how much storage you have available. To create or grow iSCSI storage, click Next and proceed to step 3 below. If you do not need to create or grow iSCSI storage, select Skip this step and proceed to step 8 below.

3. NAS Manager searches for the RAID arrays on the system and displays them on the Arrays screen. Click Next.

4. The Options screen displays the iSCSI storage configuration options. For information, see “Creating Filesystems”.

5. Enter the size in gigabytes for the iSCSI storage pool. Click Next.

6. The Confirmation screen summarizes the options you have selected. Click Next to confirm your choices and create the pool.

7. The Creating screen displays a "please wait" message during the target creation process. Click Next after the operation is finished and the completion message displays.

8. The Target Name screen lets you specify the target information. Enter the domain and optional identifier for the iSCSI name and the size of the target in the following fields:

   Domain		Specifies an iSCSI qualified name (iqn), which is a unique name that starts with iqn, then a year and month, then an internet domain name in reverse order. A default name appears based on the current system configuration. If in doubt, leave this field as is.
   Identifier		Specifies a string that will be used to uniquely identify the target. If you create only one target, this is optional. If you create more than one target, each must have a unique identifier. By default, a unique target identifier is provided for you.
   Target Size (GiB)		Specifies the size, in gigabytes, of the target.

   Click Next.

9. The Target Options screen defines access to the target. You must specify at least one authentication option:

   ---

   Note: If more than one initiator were to write to the same target at the same time, there is a high risk of data loss. By using one or more authentication options, you ensure that only one client (initiator) can access an individual target at a time.

   ---

   
   

   • IP address authentication:

     IP Address

     Specifies the IP addresses of the initiators that will be allowed access to this target

   • Challenge Handshake Authentication Protocol (CHAP) authentication:

     Target Username		Specifies the username that the initiator must supply to connect to the target using CHAP authentication. (This is not the username with which you logged in to NAS Manager; it is specific to the iSCSI target you are defining.)
     Target CHAP Secret		Specifies the password that the initiator must supply to connect to the target using CHAP authentication. It must be in the range from 12 through 16 characters. (This is not the password with which you logged in to NAS Manager; it is specific to the iSCSI target you are defining.)
     Re-enter Target CHAP Secret		Verifies the CHAP secret.

   • Mutual CHAP authentication:

     Mutual Username		Specifies the target username for mutual CHAP authentication. With mutual CHAP authentication, after the initiator supplies a username, the target must supply a username and password back to the initiator. If you leave the Mutual Username field blank, it defaults to the target username. The mutual name is usually ignored by initiators, which only care about the mutual secret. When the client connects to a target, the iSCSI initiator software verifies that the mutual secret specified in NAS Manager matches the secret specified in the initiator.
     Mutual CHAP Secret		Specifies the mutual CHAP secret.
     Re-enter Mutual CHAP Secret		Verifies the mutual CHAP secret.

   You must enter the CHAP username and secret specified on this screen in the iSCSI initiator software on the client in order for the initiator to be able to authenticate with and connect to the target. For a Windows client, this is the username and secret you enter in Microsoft's iSCSI Initiator program.

10. The Confirmation screen summarizes the target options you have selected. Click Next to confirm your choices and create the iSCSI target.

11. The Finished screen indicates that the iSCSI target has been created. Select Done .

After you have created iSCSI targets, select the following to see what initiators are connected to what targets:

Monitoring -> Clients -> iSCSI

The snapshot feature provides the ability to create virtual point-in-time images of a filesystem without causing a service interruption. The snapshot feature requires a minimal amount of storage because it uses a copy-on-write mechanism that copies only the data areas that change after the snapshot is created.

Snapshot copies of a filesystem are virtual copies, not actual media backup for a filesystem. You can, however, use a snapshot copy of a filesystem to create a backup dump of a filesystem, allowing you to continue to use and modify the filesystem while the backup runs.

You can also use a snapshot copy of a filesystem to provide a recovery mechanism in the event of data loss due to user errors such as accidental deletion. A full filesystem backup, however, is necessary in order to protect against data loss due to media failure.

---

Note: Use of the snapshot feature requires a license.

---

Creating filesystem snapshots requires that you first create a snapshot repository in which original copies of regions of data that have changed on the filesystem are stored. If you plan to use the snapshot feature, you must allow room for the snapshot repository on the RAID device when you create the filesystems.

---

Note: Be default, the NAS Manager system is shipped with a single filesystem already created. If you wish to use snapshots, you must delete the existing filesystem and create a smaller one, allowing room for the snapshot repository.

---

Scheduling Snapshots

To schedule how often the system will create a snapshot of a filesystem, do the following:

1. Select the Schedule Snapshots menu:

   Management -> Resources -> Storage -> Snapshots ->  Schedule Snapshots

2. Select the filesystem for which you want to schedule snapshots.

3. Specify the following options:

   Scheduled?
   	Specifies that a snapshot will take place for the filesystem
   Scheduled Snapshot Times
   	Specifies the hours at which a snapshot should take place. You can select multiple boxes.
   Custom Time Specification
   	Specifies the times and frequency that a snapshot should take place. You can specify this value using one of the following forms: Spelled out using the following syntax: every XX minute/s|hour/s|day/s [from XX:XX to XX:XX] The specific times listed within brackets are optional. For example: every 1 hour every 20 minutes from 8:00 to 22:00 every 4 days Exact times. For example: 12:45 23:00 9:30 The word never, which disables snapshots.
   Maximum number of snapshots
   	Specifies the maximum number of snapshots that will be retained in the repository before the oldest snapshot is deleted when a new snapshot is taken. By default, the system will retain 32 snapshots. The maximum number is 256. SGI recommends that you use the default.
   Repository
   	Specifies the repository name.

   Click Schedule snapshots to apply your settings.

4. Verify that you want to update the snapshot schedule by clicking Yes. (To return to the previous screen, click No.)

---

Note: The system will delete the oldest snapshot if it determines that repository space is running low.

---

Snapshots are made available in the /SNAPSHOTS directory of the base filesystem. They are named according to the date and time at which they are taken. For example, a snapshot might be named as follows:

/mnt/data/SNAPSHOTS/2006_07_30_113557_Sun

NAS Manager supports the remote replication of filesystems through the use of NetVault:Replicator version 4.1 or greater, a product of Bakbone Software, Inc. With remote replication, local filesystem writes are duplicated on a separate machine. The writes are mirrored over IP, and are asynchronous.

When using NetVault:Replicator with NAS Manager, the system on which you are running NAS Manager is the replication source and another host serves as the replication destination.

In order to use NetVault:Replicator with NAS Manager, you must install and configure the NetVault:Replicator on both the source and destination machines. After NetVault:Replicator has been installed and configured in both places, you can modify the configuration with NAS Manager.

---

Note: NAS Manager does not support advanced Netvault:Replicator features such as bi-directional replication, inclusion and exclusion regular-expressions, and alternates. NAS Manager supports the One-to-One Replication feature of NetVault:Replicator, allowing you to configure one-to-one replication of the filesystems from the local machine to the destination host. It does not support the One-to-Many Replication and Many-to-One Replication features of NetVault:Replicator. If you wish to use these features, you must configure them manually.

---

You can select local filesystems to be replicated on a destination host that is also running Netvault:Replicator. This means that all data written to the local filesystem will be duplicated on the remote replication filesystem, creating a filesystem on the remote server that contains the same files and directory structure as on the local machine.

To use the remote replication functionality, the following must be true:

This section provides information on the following procedures:

For further information on NetVault:Replicator, see:

http://www.bakbone.com/products/replication/

Configuring Remote Replication

To list and configure all the filesystems you have created on the system, select the following:

Management -> Resources -> Storage -> Remote Replication -> Configure

You can configure remote replication for one filesystem at a time or you can configure all of the filesystems at once by clicking the appropriate link.

For each existing filesystem, you can check the Enabled box to select whether to enable remote replication for the filesystem. This lets you configure remote replication but to wait until a later time to enable the feature.

Configure the following options for each filesystem:

Destination host
	Specifies the hostname for the replication destination.
Destination directory
	Specifies the directory on the destination host in which to put the data. Note: This directory must already exist on the remote server.
Strip path segments
	Specifies that the highest-level path segment or segments be stripped on the destination directory by indicating the number of path segments to strip. By default, the entire filesystem directory structure is replicated on the destination directory; for example, if the destination directory is set to /store, the filesystem /mnt/data would be replicated to /store/mnt/data on the destination host. However, if the destination directory is set to /store and you specify 1 in this field, then /mnt/data would be replicated to /store/data on the destination host.
Exclude files or directories
	Specifies files or directories that you do not want to mirror. Use a file glob to specify any files or directories you do not want to mirror. File globs are widely used in UNIX shells. In a glob, * can stand for any character sequence. For example, the glob *.mp3 *.o */tmp matches all files or directories whose names end in either the string .mp3 or .o or whose full path ends with the string /tmp.
Dedicated network interface
	Specifies the dedicated interface if the source and destination host are plugged directly in with cable or another dedicated VLAN network. This increases the speed of replication. Note: Dedicated interfaces are an advanced option that may require configuration changes to the network infrastructure and on the remote host. You should only use dedicated interfaces if they are specifically required. A dedicated network interface is an interface, such as eth2, that has been configured to use a point-to-point connection with a single remote host. In this case, it is possible to select an interface that will communicate with the remote replication server. All network traffic to and from that server will go via the local dedicated network interface and no other traffic will appear on that interface. Dedicated network interfaces can be useful when there may be a large amount of network traffic to and from the local host and you wish to isolate the remote replication traffic to prevent interference with other network traffic such as NFS and CIFS. When using dedicated interfaces with remote replication, you must be careful not to have two filesystems replicated to the same remote host via two or more interfaces (this includes using a dedicated interface with one replicated filesystem and None for another). In this case, only one of the filesystems will be configured to be replicated. This is because the remote host will be known locally by two different IP addresses so that it appears to actually be two different remote hosts. When the replication configuration is sent to the remote host, NetVault:Replicator will unfortunately replace the first filesytem with the second replicated filesystem.

After configuring these options, select one of the following:

• Apply configuration to apply your changes

• Apply configuration and synchronize to apply your changes and synchronize the existing data

After the configuration has been applied, any writes to the selected filesystem will appear on the remote replication server in the destination directory nominated. Synchronizing the data performs an initial sync of all the data from the source files to the destination files. The synchronization will begin copying across the entire filesystem as fast possible, and it could take some time depending on the amount of data.

If you apply the configuration without synchronizing at this point, you can synchronize at a later time by selecting the Synchronize option from the Remote Replication menu.

Select the Pause/Resume option of the Remote Replication menu to stop or restart the remote mirroring activity.

NAS Manager supports most common DMF configurations. There are some limitations to this support, however. Specifically, the following are assumed to be true:

The Empty Tape Volume screen uses the herr, hvfy, and hlock DMF database flags to record the progress of the emptying procedure. If you use the dmvoladm(8) command to inspect the database entry for a tape while it is being emptied, you may see unexpected settings of these flags. NAS Manager's use of these flags does not interfere with DMF's.

NAS Manager does not make any use of the VOL database flags reserved for site use, although the Import and Export screens do allow you to manipulate them.

The Empty Tape Volume screen's Empty Volume, Remove Volume and Reuse Volume options cannot remove soft-deleted files from a tape volume, unlike the Merge Volume button. You must wait until they have been hard-deleted by the scheduled run_hard_deletes.sh task or by the dmhdelete(8) command.

Also, these three buttons may need access to the output file from the previous run of the scheduled run_filesystem_scan.sh task or the dmscanfs(8) command. If it cannot be found or is older than the files remaining on the tape, some files may be misreported in the Alerts screen as soft-deleted and remain on the tape as described above. Trying again after the next run of run_filesystem_scan.sh is likely to succeed in this case.

For more information, see the dmemptytape (8) man page for more information.^[1]

---

Note: NAS Manager does not support the initial configuration of DMF, TMF, OpenVault.

---

You can use the DMF Configuration screens to modify some aspects of the current DMF configuration. By default, it presents the most commonly altered parameters for inspection and alteration. If you click Switch to Expert Mode on the Global page, NAS Manager presents more parameters. You should use expert mode with care. To return to normal mode, click Switch to Normal Mode.

Excluded from both modes are parameters that are:

The screens allow you to edit the contents of existing stanzas; creating new stanzas and deleting old stanzas is not supported. Parameters that can be dangerous to change are displayed but may not be altered. This includes those parameters that control the search order of volume groups and media-specific processes (MSPs) when recalling files.

To work around these restrictions, another screen lets you edit the DMF configuration file directly. However, you must ensure that the changes you make are safe. For more information, see the dmf.conf(5) man page and the DMF Administrator's Guide for SGI InfiniteStorage.^[2]

There is also a screen that invokes the dmcheck command, which performs a syntax and sanity check on a DMF configuration. You should run this command after making changes.

---

Note: On the DMF Configuration screens, disk sizes use multipliers that are powers of 1000, such as kB, MB and GB. This is for consistency with the DMF documentation and log files. However, the rest of NAS Manager, including the DMF Monitoring screens, use multipliers that are powers of 1024, such as kiB, MiB and GiB.

---

The Name Service Client screen lets you specify a name service (or directory service) for the system. A name service is the application that manages the information associated with the network users. For example, it maps user names with user IDs and group names with group IDs. It allows for centralized administration of these management tasks.

You can specify whether you are using the sitewide network information service (NIS), lightweight directory access protocol (LDAP), Active Directory services, or local files (if you have no sitewide protocol and names and IDs are kept locally on server).

---

Note: When specifying servers on the Name Service Client screen, you must use IP addresses rather than hostnames, because the system may require a name service client to determine the IP address from the hostname.

---

NAS Manager can create and add local user and group accounts to access the fileserver locally. This is a local database only; these users and groups do not interact with the users and groups provided by the name server. If you search the site directory and do not find the user or group data you are looking for, the system searches this local database.

---

Caution: If you create a local user and subsequently add that user in the sitewide directory, access problems may result. For example, if you create local user Fred with a UID of 26, Fred will be able to create local files. But if you subsequently add a user Fred on a sitewide name services directory with a different UID, user Fred will be unable to access those local files because the system will use the sitewide name and UID first.

---

If you are using Active Directory as a name service client, a user must be present in LDAP or Kerberos and you will not be able to authenticate local users and groups. In this case, adding local users and groups can be useful for ID mapping, but authentication does not use the local password files.

When you select the Import option for either Local Users or Local Groups , you can choose among the following actions:

Accounts with a UID or GID of less than 100 are considered restricted and are not imported or replaced.

If you use a shadow file, which is a file that is protected from all access by non-root users and stores the encrypted passwords, then you can use the Import Users screen to import this file as well as the password file itself.

You can use NAS Manager to set and modify user and group quotas for filesystems if you have mounted the filesystem with quotas enabled.

You cannot enable quotas on a filesystem directory through NAS Manager. You must use the ssh command to log in to the system, edit the fstab file, and remount the filesystem.

To configure filesystems so that they are available for network clients by means of the NFS network protocol, select the following:

All of the filesystems created with NAS Manager are displayed on this screen, whether or not they have been enabled for export. When you enable a filesystem for export, you can choose one of the following:

After specifying the configuration parameters, click Apply changes at the bottom of the screen.

NFS Export Options and Access

Specify the following under Export Options:

Read-only		Specifies that the client has access to the filesystem but cannot modify files or create new files.
Asynchronous writes		Specifies whether or not to use asynchronous writes. Data that is written by the client can be buffered on the server before it is written to disk. This allows the client to continue to do other work as the server continues to write the data to the disk. By default, writes are performed synchronously, which ensures that activity on the client is suspended when a write occurs until all outstanding data has been safely stored onto stable storage. You should choose to use asynchronous writes if you wish to increase performance at the risk of possibly losing some unwritten data, should there be a power failure or other serious problem affecting the server.

Select an Access option:

Anyone		Allows connections from anywhere on a network. This option does not take precedence over the Deny anonymous users share option.
Local subnet		Allows connections from the indicated subnet. You can select any subnet from those that have been defined for the network interfaces.
Custom Access Definition		Specifies the set of hosts that are permitted to access the NFS filesystem. You can specify the hosts by hostname or IP address; separate values with a space or tab. For example, you could restrict access to only the hosts on a Class C subnet by specifying something like the following: 150.203.5 To allow hosts of IP address 150.203.5.* and myhost.mynet.edu.au, specify the following: 150.203.5. myhost.mynet.edu.au You can also specify hosts by network/netmask pairs and by netgroup names if the system supports netgroups. To allow hosts that match the network/netmask of 150.203.15.0/255.255.255.0 , you would specify the following: 50.203.15.0/255.255.255.0 To allow two hosts, lapland and arvidsjaur , specify the following: lapland arvidsjaur Note: Access still requires suitable user-level passwords. The localhost address 127.0.0.1 will always be allowed.

192.168.10.1 (rw) * (ro)

To configure filesystems so that they are available for network clients by means of the CIFS network protocol, select the following:

All of the filesystems created with NAS Manager are displayed on this screen, whether or not they have been enabled for sharing. To share a file, select it and click the Shared? box.

Specify the following Share Options:

Specify the following Access options:

Anyone		Allows connections from anywhere on a network. This option does not take precedence over the Deny anonymous users share option.
Local subnets		Allows connections from the indicated subnet. You can select one subnet in this field and you must choose it from the available interfaces as set in the Network Interfaces screen.
Custom Access Definition		Specifies the set of hosts that are permitted to access the CIFS filesystem. You can specify the hosts by name or IP number; separate values by a space or tab. For example, you could restrict access to only the hosts on a Class C subnet by specifying something like the following: 150.203.5 To allow hosts of IP address 150.203.5.* and myhost.mynet.edu.au, specify the following: 150.203.5. myhost.mynet.edu.au You can also specify hosts by network/netmask pairs and by netgroup names if the system supports netgroups. You can use the EXCEPT keyword to limit a wildcard list. For example, to allow all IP address in 150.203.*.* except one address (150.203.6.66), you would specify the following: 150.203. EXCEPT 150.203.6.66 To allow hosts that match the network/netmask of 150.203.15.0/255.255.255.0 , you would specify the following: 50.203.15.0/255.255.255.0 To allow two hosts, lapland and arvidsjaur , specify the following: lapland, arvidsjaur Note: Access still requires suitable user-level passwords. The localhost address 127.0.0.1 will always be allowed.

After specifying the configuration parameters, select Apply changes at the bottom of the screen.

Use the System Name & Address screen to set the following system components:

Hostname		Specifies the fully qualified domain name (FQDN) for this NAS server. The default hostname is sginas.
Email gateway		Specifies the gateway server where email should be directed. The email gateway is also known as the smart host. Email sent from this system should not be sent to NAS server except for system warnings. If you do not specify an email gateway in this field, email sent on a system will collect locally in /var/spool/mail.
Administrator email address		Specifies the address where system email, such as system alerts, will be sent. If you do not specify an address, the messages go to root. This field can be any valid email address. Note: The administrator email address is used only for forwarding system notices. It is not sent to SGI or used for any other purposes.

You can also use the System Name & Address screen to configure or modify the management interface. For information on these options, see “Standalone Network Interfaces”.

You can use the DNS & Hostnames screen to specify how to map hostnames to IP addresses for the system. Click Edit local hosts table to access the Hosts screen, where you can edit the /etc/hosts file that contains local mappings or import the contents of a file you specify. For information on the /etc/exports file, see the exports(5) man page. ^[4]

You can also specify the DNS servers to map hostnames to IP addresses and to resolve hostnames that are incomplete.

The default network gateway is the IP address of the router that this system should use to communicate with machines that are outside of its subnet.

Use the Date and Time screen to set the following.

AEST-10AEDT,M10.5.0,M4.1.0

The Licenses screen provides a text box in which you can type in or paste FLEXlm licenses obtained from SGI. Some licenses, such as the license for xvm snapshot, will not take affect until you reboot the system.

---

Note: You cannot use this screen to supply the license information for NetVault:Replicator. You must install this license manually when you install NetVault:Replicator.

---

The Administrator Password screen changes the NAS Manager administrator password, which is the password required to perform server configuration and management. This password is not required to view the NAS Manager monitoring screens.

From the Shutdown screen, you can specify to reboot or power down the system in a specified number of seconds.

If there is a problem with the system, SGI Call Center Support may request support data in order to find and resolve the problem. The Gather Support Data screen lets you generate an archive containing copies of the NAS server's software and hardware configuration and log files.

To collect the data, select Yes, gather information. This process can take more than 30 seconds on large RAID configurations and requires at least 200 MB of free space in /tmp.