5.5 HP StorageWorks X9720 Network Storage System Administrator Guide (AW549-96026, March 2011)

ibrix_replicate -f FSNAME -b EVACUATED_SEGNUM
If you evacuated the root segment (segment 1 by default), include the -F option in the command.
The segment number associated with the storage is not reused.
6. If quotas were disabled on the file system, unmount the file system and then re-enable quotas
using the following command:
ibrix_fs -q -E -f FSNAME
Then remount the file system.
To evacuate a segment using the CLI, use the ibrix_rebalance -e command, as described in
the HP StorageWorks X9000 File Serving Soft ware CLI Reference Guide.
Maintaining networks
Cluster and user network interfaces
X9000 Software supports the following logical network interfaces:
• Cluster network interface. This network interface carries management console traffic, traffic between
file serving nodes, and traffic between file serving nodes and clients. A cluster can have only one
cluster interface. For backup purposes, each file serving node and management console can have
two cluster NICs.
• User network interface. This network interface carries traffic between file serving nodes and clients.
Multiple user network interfaces are permitted.
The cluster network interface was created for you when your cluster was installed. For clusters with
an agile management console configuration, a virtual interface is used for the cluster network interface.
One or more user network interfaces may also have been created, depending on your site's
requirements. You can add user network interfaces as necessary.
Adding user network interfaces
Although the cluster network can carry traffic between file serving nodes and either NFS/CIFS or
X9000 clients, you may want to create user network interfaces to carry this traffic. If your cluster must
accommodate a mix of NFS/CIFS clients and X9000 clients, or if you need to segregate client traffic
to different networks, you will need one or more user networks. In general, it is better to assign a user
network for NFS/CIFS traffic because the cluster network cannot host the virtual interfaces (VIFs)
required for NFS/CIFS failover. HP recommends that you use a Gigabit Ethernet port (or faster) for
user networks.
When creating user network interfaces for file serving nodes, keep in mind that nodes needing to
communicate for file system coverage or for failover must be on the same network interface. Also,
nodes set up as a failover pair must be connected to the same network interface.
HP recommends that the default network be routed through the base User Network interface.
For a highly available cluster, HP recommends that you put NFS traffic on a dedicated user network
and then set up automated failover for it (see “Setting up automated failover” on page 33). This
method prevents interruptions to NFS traffic. If the cluster interface is used for NFS traffic and that
interface fails on a file serving node, any NFS clients using the failed interface to access a mounted
file system will lose contact with the file system because they have no knowledge of the cluster and
cannot reroute requests to the standby for the node.
X9720 Network Storage System Administrator Guide 71