HP Integrity rx2800 HP Integrity Network Adapter Teaming Whitepaper - Page 17

Load Balancing: Server-Based Routing Protocol or NIC Teaming?, Overview of Team Types

Get HP Integrity rx2800 - i2 PDF manuals and user guides View all HP Integrity rx2800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 17 highlights

Figure 3-3 Using NIC teaming for server network redundancy Integrity Server Teaming Driver 1.1.1.1 Switch C on so le Clients 1.1.1.3 1.1.1.4 1.1.1.5 •Server has redundant path for outgoing traffic. From the Server's IP perspective, single "virtual" adapter provides access to the network. •Provides redundant connectivity from Clients to Server for same Server IP address. Server is known by single IP for DNS/NetBIOS/etc. 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. Figure 3-4 provides a graphical overview of which team types support which redundancy and load-balancing features. Overview of Team Types 17

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
Figure 3-3 Using NIC teaming for server network redundancy
Integrity Server
Switch
Clients
•
Server has redundant path for
outgoing traffic.
From the Server’s IP perspective,
single “virtual” adapter provides
access to the network.
•
Provides redundant connectivity
from Clients to Server for same
Server IP address.
Server is known by single IP for
DNS/NetBIOS/etc.
1.1.1.1
Teaming
Driver
1.1.1.5
1.1.1.4
1.1.1.3
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.
Figure 3-4
provides a graphical overview of which team types support which
redundancy and load-balancing features.
Overview of Team Types
17