6.2 HP IBRIX 9000 Storage Network Best Practices Guide (TA768-96069, December 2012)

When correctly configured the following should work:
FSNs should be able to ICMP ping all of the other network attached components, both on the
user/cluster subnet and the management subnet.
File Clients should be able to ICMP ping the FSNs.
The protocols listed in Table 3 (page 25) must work between the components, and should not
be blocked by intervening firewalls or routers.
IP address usage
In this configuration, the IBRIX 9730 requires the following IP addresses:
Table 10 IBRIX 9730 IP addresses for one additional physical user network
Maximum number of addressesMinimum number of addressesSubnetComponent
162user/clusterFile serving nodes
1616managementiLO
88managementInterconnect
22managementOA module
11clusterFM VIF
Variable. At least 2 per FSN (32
included in total)
4userUser VIF
75 for maximum configuration33 for minimum configuration
Table 11 IBRIX 9730 IP addresses for two additional physical user networks
Maximum number of addressesMinimum number of addressesSubnetComponent
162user/clusterFile serving nodes
1616managementiLO
88managementInterconnect
22managementOA module
11clusterFM VIF
Variable. At least 3 per FSN (48
included in total)
6userUser VIF
91for maximum configuration35 for minimum configuration
Because of the manner in which the OA dynamically assigns the addresses to the enclosure
components, all of the enclosure bays must have addresses assigned for potential management
components even if the bay will not be populated in the shipped configuration. The enclosure
management IP addresses are assigned when the enclosure is initially configured.
Customer use of VLANs or multiple user network VIFs may require additional IP addresses beyond
those specified in this table.
46 IBRIX 9730 platform networking