HP StoreAll Storage Network Best Practices Guide

Table Of Contents
The cluster in Figure 3 (page 10), shows FM failover from StoreAll node 1 to StoreAll node 2:
StoreAll node 1 is servicing file client requests to 10.30.214.202 (StoreAll node 1–bond0:2).
StoreAll node 2 is servicing file client requests to 10.30.214.203 (StoreAll node 2–bond0:2).
Fusion Manager is active on StoreAll node 2, accepting requests to 10.30.214.201 (StoreAll
node 1–bond0:0).
After FM migration, StoreAll node 1 has two active interfaces:
bond0 is the cluster network interface
bond0:0 is not active; the Fusion Manager could move back to this interface if requested
bond0:2 is a user network VIF for file services from StoreAll node 1
bond0:3 is not active, but is provisioned for failover of file services duties from StoreAll node
2
After FM migration, StoreAll node 2 has two active interfaces:
bond0 is the cluster network interface
bond0:0 is handling requests for the active Fusion Manager
bond0:2 is a user network VIF for file services from StoreAll node 2
bond0:3 is not active, but is provisioned for failover of file services duties from StoreAll node
1
The ibrix_nic command shows the following after the FM migrates from StoreAll node 1 to
StoreAll node 2:
Sample ifconfig output for node 1 after migrating the FM from node 1 to node 2:
StoreAll node failover 11