Home » HP Manuals » Servers » HP Integrity rx2800 » Manual Viewer

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

–7 HP Integrity Network Adapter Teaming Configuration and Deployment with Integrity Essentials Rapid Deployment Pack (RDP)

View all HP Integrity rx2800 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 86 highlights

4-7 HP Integrity Network Adapter Teaming Configuration and Deployment with Integrity Essentials Rapid Deployment Pack (RDP) One of the methods of deployment for HP Integrity Network Adapter Teaming is to use HP Integrity Essential's Rapid Deployment Pack (RDP) remote scripting feature. This feature allows an SA to deploy a specific teaming configuration to any number of target servers in a single action. RDP is a server deployment solution that facilitates the installation, configuration, and deployment of high-volumes of servers through either a GUI-based or a web-based console, using either scripting or imaging technology. For additional information on RDP, refer to http:// h18004.www1.hp.com/products/servers/management/rdp.html. Example steps for HP Integrity Network Adapter Teaming deployment using RDP: 1. Create the desired team on one server manually. When satisfied with the teaming configuration, click the Save button in the NCU tool and save the file as hpteam.xml to a location on the RDP server. 2. Create a new job in the RDP console called "NIC Teaming Job". 3. Edit the job properties and include a copy file task that copies the latest NCU (for example, cp123456.exe) to the target server's %windir%\temp folder (if you do not need to upgrade the NCU tool, you may omit this step). 4. Add an additional copy file task that copies the Hpteam.xml file (from Step 1) to the same location on the server as the NCU tool copied in Step 3. 5. If needed, add a Run Script task that executes the NCU installer (for example:%windir%\temp\cp123456.exe /s) 6. Add an additional Run Script task that executes the teaming CLI tool and uses the HPteam.xml configuration file (for example:c:\windows\system32\cqniccmd.exe /c %windir%\temp\hpteam.xml). 7. Test the new job on a target server with no teaming installed to ensure the desired result. NOTE: If any of the target servers already have a team in place and your intention is to overwrite that team, consider the cqniccmd.exe /d parameter to delete existing teams. Note that in doing so, your target may lose the connection to the RDP server and may be unable to complete the job. This can be reconciled by putting all of the above scripts into one batch file that is sent to the server via the RDP console and then told to execute locally. Lastly, if your network does not use DHCP on the subnet where the team is created, you will lose access to the target server once the new team is created. You can overcome this by using netsh.exe included with Windows Server 2008. 86 The Mechanics of Teaming for the Advanced User

Section	Page
Network Adapter Teaming White Paper	1
Table of Contents	3
1 Introduction	9
Abstract	9
How to Read This Document	9
Section Layout	9
2 An Executive Overview of Teaming	11
What is HP Integrity Network Adapter Teaming?	11
The Goals of HP Integrity Network Adapter Teaming	11
Fault Tolerance: Self-Healing Network Connectivity	11
Load Balancing: RAID 5 for Server Network Adapters	12
Why HP Integrity Network Adapter Teaming?	13
3 Teaming Fundamentals for the First-Time User	15
A Technical Overview of HP Integrity Network Adapter Teaming	15
Fault Tolerance: Dual Homing or Network Adapter Teaming?	15
Load Balancing: Server-Based Routing Protocol or NIC Teaming?	17
Overview of Team Types	17
Network Fault Tolerance Only (NFT)	18
Network Fault Tolerance Only with Preference Order	18
Transmit Load Balancing with Fault Tolerance (TLB)	19
Transmit Load Balancing with Fault Tolerance and Preference Order	19
Switch-assisted Load Balancing with Fault Tolerance (SLB)	19
802.3ad Dynamic with Fault Tolerance	19
Switch-assisted Dual Channel Load Balancing	19
802.3ad Dynamic Dual Channel Load Balancing	20
Automatic	20
How to Choose the Best Team Type	20
Basic Teaming Versus Advanced Teaming	22
Basic Deployment Steps for HP Integrity Network Adapter Teaming	23
Download	23
Install	23
Launch	23
Overview of the HP Network Configuration Utility	23
NCU Main Page	24
Primary Actions from the NCU Main Page	24
Team Properties Page	24
Team Properties Page Tabs	25
Adapter Properties Page	25
Adapter Properties Page Tabs	25
Getting Started	26
Example Deployment of Basic Teaming	26
Example Deployment of Advanced Teaming	26
4 The Mechanics of Teaming for the Advanced User	29
Section Objectives and Prerequisites	29
Architecture of HP Integrity Networking Adapter Teaming	29
The “Networking Layers” of an Operating System	29
Teaming Software Components	30
Network Adapter Miniport Driver	30
Teaming Intermediate Driver	30
HP Network Configuration Utility	30
HP Teaming and Layer 2 Versus Layer 3 Addresses	30
Types of HP Integrity Network Adapter Teams	31
Network Fault Tolerance Only (NFT)	31
Network Addressing and Communication with NFT	32
Scenario 4–A: A Device Pings an NFT Team on the Same Layer 2 Network	32
NFT Redundancy Mechanisms	34
Basic Redundancy Mechanisms	34
Advanced Redundancy Mechanisms	37
Active Path	37
General Description of Active Path Operation	38
Active Path Configuration	45
Fast Path	47
General Description of Fast Path Operation	51
Fast Path Configuration	52
Redundancy Mechanism Priority	54
Redundancy Mechanism Comparison Chart	54
Failover Events	55
NFT Network Adapter Failure Recovery	56
NFT Applications	56
Recommended Configurations for NFT Environments	57
Network Fault Tolerance Only with Preference Order	57
NFT with Preference Order Applications	57
Transmit Load Balancing with Fault Tolerance (TLB)	57
Network Addressing and Communication with TLB	58
Scenario 4–B: A Device Pings a TLB Team on the Same Layer 2 Network	58
Transmit Load Balancing Methods (Algorithms)	60
TLB Automatic Method	61
TLB TCP Connection Method	62
TLB Destination IP Address Method	62
Scenario 4-C: A TLB Team Using IP Address-Based Load Balancing	63
TLB Destination MAC Address Method	64
Scenario 4-D: A TLB Team Using Destination MAC Address Load-Balancing Method	65
TLB Round Robin Method for Outbound Load Balancing	66
TLB Redundancy Mechanisms	67
TLB Network Adapter Failure Recovery	67
TLB Applications	67
Recommended Configurations for TLB Environments	67
Transmit Load Balancing with Fault Tolerance and Preference Order	68
Transmit Load Balancing with Fault Tolerance and Preference Order Applications	68
Switch-Assisted Load Balancing with Fault Tolerance (SLB)	68
Network Addressing and Communication with SLB	69
SLB Outbound Load-Balancing Algorithms	69
SLB Inbound Load-Balancing Algorithm	69
Cisco EtherChannel	70
Switch Vendor Port Trunking Technology Supported by SLB	71
SLB Redundancy Mechanisms	72
SLB Network Adapter Failure Recovery	72
SLB Applications	72
Recommended Configurations for SLB Environments	72
802.3ad Dynamic with Fault Tolerance	73
Switch-assisted Dual Channel Load Balancing	73
Dual Channel Configuration	76
Dual Channel Transmit Balancing Algorithm	77
Dual Channel Receive Load-Balancing Algorithm	77
Receive Load Balancing on a Per-Port Trunk Basis	77
Receive Load Balancing on Multiple Trunks	77
Dual Channel Redundancy Mechanisms	78
Basic Redundancy Mechanisms	78
Advanced Redundancy Mechanisms	78
Dual Channel Network Adapter Failure Recovery	78
Dual Channel Applications	78
Recommended Configurations for Dual Channel Environments	78
802.3ad Dynamic Dual Channel Load Balancing	79
802.3ad Dynamic Dual Channel Configuration	79
Automatic	79
Team Types and Redundancy Mechanisms Interoperation	79
Team Type and Redundancy Mechanisms Compatibility Chart	79
Mechanism Priority	80
Team Status and Icons	81
Network Adapter Teamed Status	81
Team State	83
Team Icons	83
HP Integrity Network Adapter Teaming and Advanced Networking Features	84
Checksum Offloading	84
802.1p QoS Tagging	84
Large Send Offload (LSO)	84
Maximum Frame Size (Jumbo Frames)	84
802.1Q Virtual Local Area Networks (VLAN)	85
4–7 HP Integrity Network Adapter Teaming Configuration and Deployment with Integrity Essentials Rapid Deployment Pack (RDP)	86
5 Teaming Feature Matrix	87
A – Overview of Network Addressing and Communication	89
Layer 2 Versus Layer 3	89
Address – Unicast Versus Broadcast Versus Multicast	89
Example Scenarios of Network Addressing and Communication	89
Scenario A-1: One Device Pings Another on the Same Layer 2 Network	90
Scenario A-2: One Device Pings Another on a Different Layer 2 Network	91
B – Frequently Asked Questions	95
C – Overview of Utilities Included with HP Integrity Network Adapter Teaming	99

Match case Limit results 1 per page

4–7 HP Integrity Network Adapter Teaming Configuration and Deployment

with Integrity Essentials Rapid Deployment Pack (RDP)

One of the methods of deployment for HP Integrity Network Adapter Teaming is to use HP

Integrity Essential’s Rapid Deployment Pack (RDP) remote scripting feature. This feature allows

an SA to deploy a specific teaming configuration to any number of target servers in a single

action. RDP is a server deployment solution that facilitates the installation, configuration, and

deployment of high-volumes of servers through either a GUI-based or a web-based console,

using either scripting or imaging technology. For additional information on RDP, refer to

http://

h18004.www1.hp.com/products/serv

ers/management/rdp.html

Example steps for HP Integrity Network Adapter Teaming deployment using RDP:

Create the desired team on one server manually. When satisfied with the teaming

configuration, click the Save button in the NCU tool and save the file as

hpteam.xml

to a

location on the RDP server.

Create a new job in the RDP console called “NIC Teaming Job”.

Edit the job properties and include a copy file task that copies the latest NCU (for example,

cp123456.exe

) to the target server’s

%windir%\temp

folder (if you do not need to upgrade

the NCU tool, you may omit this step).

Add an additional copy file task that copies the

Hpteam.xml

file (from Step 1) to the same

location on the server as the NCU tool copied in Step 3.

If needed, add a Run Script task that executes the NCU installer (for

example:

%windir%\temp\cp123456.exe /s

)

Add an additional Run Script task that executes the teaming CLI tool and uses the

HPteam.xml

configuration file (for example:

c:\windows\system32\cqniccmd.exe

/c %windir%\temp\hpteam.xml

Test the new job on a target server with no teaming installed to ensure the desired result.

NOTE:

If any of the target servers already have a team in place and your intention is to overwrite

that team, consider the

cqniccmd.exe /d

parameter to delete existing teams. Note that in

doing so, your target may lose the connection to the RDP server and may be unable to complete

the job. This can be reconciled by putting all of the above scripts into one batch file that is sent

to the server via the RDP console and then told to execute locally. Lastly, if your network does

not use DHCP on the subnet where the team is created, you will lose access to the target server

once the new team is created. You can overcome this by using

netsh.exe

included with Windows

Server 2008.

The Mechanics of Teaming for the Advanced User