HP 6125XLG R2306-HP 6125XLG Blade Switch High Availability Configuration Guide - Page 105

track, Command, Remarks

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

Page 105 highlights

The disadvantage of using static routes is that they cannot adapt to network topology changes. Faults or topological changes in the network can make the routes unreachable, causing network breaks. To prevent this problem, configure another route to back up the static route. When the static route is reachable, packets are forwarded through the static route. When the static route is unreachable, packets are forwarded through the backup route, avoiding network breaks and enhancing network reliability. To check the accessibility of a static route in real time, establish an association between Track and the static route. If you specify the next hop but not the egress interface when configuring a static route, you can establish collaborations among the static route, the Track module, and detection modules. This enables you to check the accessibility of the static route by the status of the track entry. • The Positive state of the track entry shows that the next hop of the static route is reachable, and that the configured static route is valid. • The Negative state of the track entry shows that the next hop of the static route is not reachable, and that the configured static route is invalid. • The NotReady state of the track entry shows that the accessibility of the next hop of the static route is unknown, and that the static route is valid. Follow these guidelines when you associate Track with static routing: • 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. • If the Track module detects the next hop accessibility of the static route in a private network through NQA, the VPN instance name of the next hop of the static route must be consistent with that configured for the NQA test group. Otherwise, the accessibility detection cannot function properly. • If a static route needs route recursion, the associated track entry must monitor the next hop of the recursive route instead of that of the static route. Otherwise, a valid route may be considered invalid. To associate Track with static routing: Step 1. Enter system view. 2. Associate the static route with a track entry to check the accessibility of the next hop. Command Remarks system-view N/A • Method 1: ip route-static dest-address { mask | mask-length } { next-hop-address [ track track-entry-number ] | interface-type interface-number [ next-hop-address ] | vpn-instance d-vpn-instance-name next-hop-address [ track track-entry-number ] } [ permanent ] [ preference preference-value ] [ tag tag-value ] [ description description-text ] • Method 2: Not configured by default. ip route-static vpn-instance s-vpn-instance-name dest-address { mask | mask-length } { next-hop-address [ public ] [ track track-entry-number ] | interface-type interface-number [ next-hop-address ] | vpn-instance d-vpn-instance-name next-hop-address [ track track-entry-number ] } [ permanent ] [ preference preference-value ] [ tag tag-value ] [ description description-text ] 100

  • 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
100
The disadvantage of using static routes is that they cannot adapt to network topology changes. Faults or
topological changes in the network can make the routes unreachable, causing network breaks.
To prevent this problem, configure another route to back up the static route. When the static route is
reachable, packets are forwarded through the static route. When the static route is unreachable, packets
are forwarded through the backup route, avoiding network breaks and enhancing network reliability.
To check the accessibility of a static route in real time, establish an association between Track and the
static route.
If you specify the next hop but not the egress interface when configuring a static route, you can establish
collaborations among the static route, the Track module, and detection modules. This enables you to
check the accessibility of the static route by the status of the track entry.
•
The Positive state of the track entry shows that the next hop of the static route is reachable, and that
the configured static route is valid.
•
The Negative state of the track entry shows that the next hop of the static route is not reachable, and
that the configured static route is invalid.
•
The NotReady state of the track entry shows that the accessibility of the next hop of the static route
is unknown, and that the static route is valid.
Follow these guidelines when you associate Track with static routing:
•
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.
•
If the Track module detects the next hop accessibility of the static route in a private network through
NQA, the VPN instance name of the next hop of the static route must be consistent with that
configured for the NQA test group. Otherwise, the accessibility detection cannot function properly.
•
If a static route needs route recursion, the associated track entry must monitor the next hop of the
recursive route instead of that of the static route. Otherwise, a valid route may be considered
invalid.
To associate Track with static routing:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Associate the static
route with a track
entry to check the
accessibility of the
next hop.
•
Method 1:
ip route-static
dest-address { mask |
mask-length
} {
next-hop-address [
track
track-entry-number ] | interface-type
interface-number [ next-hop-address ] |
vpn-instance
d-vpn-instance-name
next-hop-address [
track
track-entry-number ] }
[
permanent
] [
preference
preference-value ]
[
tag
tag-value ] [
description
description-text ]
•
Method 2:
ip route-static
vpn-instance
s-vpn-instance-name dest-address { mask
|
mask-length } { next-hop-address
[
public
]
[
track
track-entry-number
] | interface-type
interface-number [ next-hop-address ] |
vpn-instance
d-vpn-instance-name
next-hop-address
[
track
track-entry-number
] }
[
permanent
] [
preference
preference-value ]
[
tag
tag-value ] [
description
description-text ]
Not configured by default.