Load Balancing: Server-Based Routing Protocol Or Nic Teaming; Overview Of Team Types; Using Nic Teaming For Server Network Redundancy - HP Integrity rx2800 - i2 White Paper

Figure 3-3 Using NIC teaming for server network redundancy
Integrity Server
Teaming
Driver
1.1.1.1
•Server has redundant path for
outgoing traffic.
From the Server's IP perspective,
single "virtual" adapter provides
access to the network.

Load Balancing: Server-Based Routing Protocol or NIC Teaming?

There are two widely used solutions for achieving load balancing for a server's network traffic.
An SA can deploy a server-based routing protocol that supports load balancing (for example,
OSPF, EIGRP, IS-IS, etc.) or the SA can deploy teaming. Server-based routing protocols are much
more difficult to deploy and manage. In addition, they do not allow for load balancing between
end devices that don't support the routing protocol (for example, clients on the same local area
network (LAN) with the server would have to 'speak' the routing protocol).
Teaming is simpler to understand and easier to deploy than server-based routing protocols. In
addition, teaming supports load balancing without requiring any kind of special configuration
or feature support on the network devices (for example, clients) with which the team is
communicating.

Overview of Team Types

HP Integrity Network Adapter Teaming is a collection of fault-tolerant and load-balancing
features that work together in different combinations called team types. These team types provide
HP Integrity Network Adapter Teaming with the flexibility to support almost every network
environment.
redundancy and load-balancing features.
Figure 3-4 provides a graphical overview of which team types support which
Switch
C o n s o l e
•Provides redundant connectivity
from Clients to Server for same
Server IP address.
Server is known by single IP for
DNS/NetBIOS/etc.
Clients
1.1.1.3
1.1.1.4
1.1.1.5
Overview of Team Types 17