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

Advanced Redundancy, Community Address ARP, Fast Path, Active Path Failover

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 27 highlights

4. 4. Enable and configure advanced redundancy mechanisms. a. Select the Advanced Redundancy tab from the Team Properties page. b. Enable Active Path Failover by checking the box. c. Select Community Address ARP as the Echo Node Response Mechanism. d. Type the IP address of the designated Echo Node (for example, gateway router) in the Echo Node IP Address field. e. Select an unused IP address on the same subnet as the Echo Node and type it in the Community Probe IP Address field. (Note: The same Community Probe IP address can be used for all Active Path-enabled teams on the same subnet. HP recommends this type of configuration.) f. OPTIONAL STEP: If Spanning Tree is enabled on the switches connected to the server, enable Fast Path by checking the box. g. OPTIONAL STEP: In the Mechanism Priority window, highlight Active Path Failover and move it above Fast Path Failover by using the up arrow on the right. h. Click the OK button at the bottom of the Team Properties page when finished. 5. Apply all changes. a. Click the OK button at the bottom of the NCU main page. b. Click Yes when asked if all configuration changes should be applied. c. Wait until the All Configuration Changes Were Made Successfully dialog box appears. 6. Assign an IP address to the team. a. Open the Network Connections (in other words, Network and Dial-up Connections) window from the Control Panel. b. Under Device Name (in the Details view), open the Properties page for the device with the same name as noted in Step 3. c. Assign the appropriate IP address information based on the connected network requirements. Getting Started 27

  • 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
4.
4. Enable and configure advanced redundancy mechanisms.
a.
Select the
Advanced Redundancy
tab from the Team Properties page.
b.
Enable Active Path Failover by checking the box.
c.
Select
Community Address ARP
as the Echo Node Response Mechanism.
d.
Type the IP address of the designated Echo Node (for example, gateway router) in the
Echo Node IP Address field.
e.
Select an unused IP address on the same subnet as the Echo Node and type it in the
Community Probe IP Address field. (Note: The same Community Probe IP address can
be used for all Active Path-enabled teams on the same subnet. HP recommends this
type of configuration.)
f.
OPTIONAL STEP: If Spanning Tree is enabled on the switches connected to the server,
enable
Fast Path
by checking the box.
g.
OPTIONAL STEP: In the Mechanism Priority window, highlight
Active Path Failover
and move it above
Fast Path Failover
by using the up arrow on the right.
h.
Click the
OK
button at the bottom of the Team Properties page when finished.
5.
Apply all changes.
a.
Click the
OK
button at the bottom of the NCU main page.
b.
Click
Yes
when asked if all configuration changes should be applied.
c.
Wait until the All Configuration Changes Were Made Successfully dialog box appears.
6.
Assign an IP address to the team.
a.
Open the Network Connections (in other words, Network and Dial-up Connections)
window from the Control Panel.
b.
Under Device Name (in the Details view), open the Properties page for the device with
the same name as noted in Step 3.
c.
Assign the appropriate IP address information based on the connected network
requirements.
Getting Started
27