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

Collaboration between the track module and an application module, Collaboration application example

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

• NQA • BFD • Interface management module Collaboration between the track module and an application module After being associated with an application module, when the status of the track entry changes, the track module notifies the application module, which then takes proper actions. The following application modules can be associated with the track module: • Virtual Router Redundancy Protocol (VRRP) • Static routing In some cases, the status of a track entry changes while a route is still recovering. This leads to problems if the track module immediately notifies the application modules of the status change and the application modules begin using the route before it is ready. For example, the master in a VRRP group monitors the uplink interface through the track module. When the uplink interface fails, the track module notifies the master to reduce its priority so that a backup with a higher priority can preempt as the master to forward packets. When failed uplink interface recovers, if the track module immediately notifies the original master to restore its priority, the master immediately will forward packets to that interface; however, this result in packet forwarding failure because the uplink route has not yet been recovered. To solve this problem, configure a delay before the track module notifies the application modules of the track entry status changes. Collaboration application example The following is an example of collaboration between NQA, track, and static routing. Configure a static route with next hop 192.168.0.88 on the device. If the next hop is reachable, the static route is valid. If the next hop becomes unreachable, the static route should become invalid. For this purpose, configure collaboration between the NQA, track, and static routing modules: 1. Create an NQA test group to monitor the reachability of IP address 192.168.0.88. 2. Create a track entry and associate it with the NQA test group. When the next hop 192.168.0.88 is reachable, the track entry is in Positive state. When the next hop becomes unreachable, the track entry is in Negative state. 3. Associate the track entry with the static route. When the track entry turns to the Positive state, the static route is valid. When the associated track entry turns to the Negative state, the static route is invalid. Track configuration task list To implement the collaboration function, establish associations between the track module and the detection modules, and between the track module and the application modules. Complete these tasks to configure the track module: 183

  • 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
183
•
NQA
•
BFD
•
Interface management module
Collaboration between the track module and an application module
After being associated with an application module, when the status of the track entry changes, the track
module notifies the application module, which then takes proper actions.
The following application modules can be associated with the track module:
•
Virtual Router Redundancy Protocol (VRRP)
•
Static routing
In some cases, the status of a track entry changes while a route is still recovering. This leads to problems
if the track module immediately notifies the application modules of the status change and the application
modules begin using the route before it is ready.
For example, the master in a VRRP group monitors the uplink interface through the track module. When
the uplink interface fails, the track module notifies the master to reduce its priority so that a backup with
a higher priority can preempt as the master to forward packets. When failed uplink interface recovers,
if the track module immediately notifies the original master to restore its priority, the master immediately
will forward packets to that interface; however, this result in packet forwarding failure because the uplink
route has not yet been recovered.
To solve this problem, configure a delay before the track module notifies the application modules of the
track entry status changes.
Collaboration application example
The following is an example of collaboration between NQA, track, and static routing.
Configure a static route with next hop 192.168.0.88 on the device. If the next hop is reachable, the static
route is valid. If the next hop becomes unreachable, the static route should become invalid. For this
purpose, configure collaboration between the NQA, track, and static routing modules:
1.
Create an NQA test group to monitor the reachability of IP address 192.168.0.88.
2.
Create a track entry and associate it with the NQA test group. When the next hop 192.168.0.88
is reachable, the track entry is in Positive state. When the next hop becomes unreachable, the track
entry is in Negative state.
3.
Associate the track entry with the static route. When the track entry turns to the Positive state, the
static route is valid. When the associated track entry turns to the Negative state, the static route is
invalid.
Track configuration task list
To implement the collaboration function, establish associations between the track module and the
detection modules, and between the track module and the application modules.
Complete these tasks to configure the track module: