Planning the Fabric
TCP / IP
TCP/IP Supported Configurations
Multiple TCP/IP HyperFabric configurations are supported to match the cost, scaling and performance requirements of each installation.
In the previous “Configuration Guidelines” section the maximum limits for TCP/IP enabled HyperFabric hardware configurations were outlined. In this section the TCP/IP enabled HyperFabric configurations that HP supports will be detailed. These recommended configurations offer an optimal mix of performance, availability and practicality for a variety of operating environments.
There are many variables that can impact HyperFabric performance. If you are considering a configuration that is beyond the scope of the following HP supported configurations, contact your HP representative.
Point-to-Point Configurations
Large servers like HP’s Superdome can be interconnected to run Oracle RAC 9i and enterprise resource planning applications. These applications are typically consolidated on large servers.
Point to point connections between servers support the performance benefits of HMP without investing in HyperFabric switches. This is a good solution in small configurations where the benefits of a switched HyperFabric cluster might not be required (see configuration A and configuration C in Figure
If there are multiple point to point connections between two nodes, the traffic load will be balanced over those links. If one link fails, the load will
Running applications using TCP/IP on a HyperFabric cluster provides major performance benefits compared to other technologies (such as ethernet). If a HyperFabric cluster is originally set up to run enterprise applications using TCP/IP and the computing environment stabilizes with a requirement for higher performance, migration to HMP is always an option.
Chapter 2 | 31 |
