6.3 HP StoreAll 9300/9320 Storage Administrator Guide (AW549-96072, June 2013)

14. Uninstall the StoreALL OS software from FSN4:
/usr/local/ibrix/local/installation/ibrix/ibrixinit -u -F
NOTE: If the same StoreAll OS version will be reinstalled on FSN4, use the following
command instead:
/usr/local/ibrix/local/installation/ibrix/ibrixinit -U
The node is no longer in the cluster.
Maintaining networks
Cluster and user network interfaces
StoreAll software supports the following logical network interfaces:
• Cluster network interface. This network interface carries Fusion Manager 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 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. (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/SMB/HTTP/FTP or StoreAll clients, you may want to create user network interfaces to carry
this traffic. If your cluster must accommodate a mix of NFS/SMB/FTP/HTTP clients and StoreAll
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 protocol (NFS/SMB/HTTP/FTP)
traffic because the cluster network cannot host the virtual interfaces (VIFs) required for 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.
For a highly available cluster, HP recommends that you put protocol traffic on a user network and
then set up automated failover for it (see “Configuring High Availability on the cluster” (page 53)).
This method prevents interruptions to the traffic. If the cluster interface is used for protocol traffic
and that interface fails on a file serving node, any protocol 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.
Link aggregation and virtual interfaces
When creating a user network interface, you can use link aggregation to combine physical resources
into a single VIF. VIFs allow you to provide many named paths within the larger physical resource,
each of which can be managed and routed independently, as shown in the following diagram.
See the network interface vendor documentation for any rules or restrictions required for link
aggregation.
Maintaining networks 121