HP 6125G HP 6125G & 6125G/XG Blade Switches High Availability Configur - Page 196

Displaying and maintaining track entries, Track configuration examples

Get HP 6125G PDF manuals and user guides View all HP 6125G manuals
Add to My Manuals
Save this manual to your list of manuals

Page 196 highlights

Step Command Approach 1: ip route-static dest-address { mask | mask-length } { next-hop-address | vpn-instance d-vpn-instance-name next-hop-address } track track-entry-number [ preference preference-value ] 2. Associate the static [ tag tag-value ] [ description description-text ] route with a track entry to check the Approach 2: accessibility of the next ip route-static vpn-instance hop. s-vpn-instance-name& dest-address { mask | mask-length } { next-hop-address [ public ] track track-entry-number | vpn-instance d-vpn-instance-name next-hop-address track track-entry-number } [ preference preference-value ] [ tag tag-value ] [ description description-text ] Remarks Use either approach. Not configured by default. NOTE: You can associate a nonexistent track entry with a static route. The association takes effect only after you use the track command to create the track entry. Displaying and maintaining track entries Task Display information about the specified or all track entries. Command Remarks display track { track-entry-number | all } [ | { begin | exclude | Available in any view include } regular-expression ] Track configuration examples VRRP-track-NQA collaboration configuration example (the master monitors the uplink) Network requirements • As shown in Figure 49, Host A needs to access Host B on the Internet. The default gateway of Host A is 10.1.1.10/24. • Switch A and Switch B belong to VRRP group 1, whose virtual IP address is 10.1.1.10. • When Switch A operates properly, packets from Host A to Host B are forwarded through Switch A. When VRRP finds that a fault is on the uplink of Switch A through NQA, packets from Host A to Host B are forwarded through Switch B. 189

  • 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
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
189
Step
Command
Remarks
2.
Associate the static
route with a track entry
to check the
accessibility of the next
hop.
Approach 1:
ip route-static
dest-address
{
mask
|
mask-length
}
{
next-hop-address
|
vpn-instance
d-vpn-instance-name next-hop-address
}
track
track-entry-number
[
preference
preference-value
]
[
tag
tag-value
] [
description
description-text
]
Approach 2:
ip route-static
vpn-instance
s-vpn-instance-name
&<1-6>
dest-address
{
mask
|
mask-length
} {
next-hop-address
[
public
]
track
track-entry-number
|
vpn-instance
d-vpn-instance-name
next-hop-address
track
track-entry-number
} [
preference
preference-value
]
[
tag
tag-value
] [
description
description-text
]
Use either approach.
Not configured by
default.
NOTE:
You can associate a nonexistent track entry with a static route. The association takes effect only after you
use the
track
command to create the track entry.
Displaying and maintaining track entries
Task
Command
Remarks
Display information about the
specified or all track entries.
display
track
{
track-entry-number
|
all
} [
|
{
begin
|
exclude
|
include
}
regular-expression
]
Available in any view
Track configuration examples
VRRP-track-NQA collaboration configuration example (the
master monitors the uplink)
Network requirements
•
As shown in
Figure 49
, Host A needs to access Host B on the Internet. The default gateway of Host
A is 10.1.1.10/24.
•
Switch A and Switch B belong to VRRP group 1, whose virtual IP address is 10.1.1.10.
•
When Switch A operates properly, packets from Host A to Host B are forwarded through Switch A.
When VRRP finds that a fault is on the uplink of Switch A through NQA, packets from Host A to Host
B are forwarded through Switch B.