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

Associating Track with PBR, Configuration prerequisites, Configuration procedure

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

Associating Track with PBR PBR is a routing mechanism based on user-defined policies. Different from the traditional destination-based routing mechanism, PBR allows you to use a policy (based on such criteria as the source address and packet length) to route packets. You can specify the VPN instance, packet priority, outgoing interface, next hop, default outgoing interface, default next hop, and other parameters to guide the forwarding of packets that match specific ACLs or have specific lengths. For more information about PBR, see Layer 3-IP Routing Configuration Guide. PBR cannot detect the availability of any action taken on packets. When an action is not available, packets processed by the action might be discarded. For example, configure PBR to forward packets that match certain criteria through a user-specified interface. When the link of the interface fails, PBR cannot sense the failure, and continues to forward matching packets out of the interface. This problem can be solved by associating Track with PBR, which improves the flexibility of the PBR application and enables PBR to sense topology changes. After you associate a track entry with an apply clause, the detection module associated with the track entry sends the detection result of the availability of the object (an interface or an IP address) specified in the apply clause. • The Positive state of the track entry shows that the object is available, and the apply clause is valid. • The Negative state of the track entry shows that the object is not available, and the apply clause is invalid. • The NotReady state of the track entry shows that the apply clause is valid. The following objects can be associated with a track entry: • Outgoing interface. • Next hop. • Default outgoing interface. • Default next hop. Configuration prerequisites Before you associate Track with PBR, create a policy or a policy node and configure the match criteria as well. Configuration procedure You can associate a nonexistent track entry with PBR. The association takes effect only after you use the track command to create the track entry. To associate Track with PBR: Step 1. Enter system view. 2. Create a policy or policy node and enter PBR policy node view. Command system-view policy-based-route policy-name [ deny | permit ] node node-number Remarks N/A N/A 101

  • 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
101
Associating Track with PBR
PBR is a routing mechanism based on user-defined policies. Different from the traditional
destination-based routing mechanism, PBR allows you to use a policy (based on such criteria as the
source address and packet length) to route packets. You can specify the VPN instance, packet priority,
outgoing interface, next hop, default outgoing interface, default next hop, and other parameters to guide
the forwarding of packets that match specific ACLs or have specific lengths. For more information about
PBR, see
Layer 3—IP Routing Configuration Guide
.
PBR cannot detect the availability of any action taken on packets. When an action is not available,
packets processed by the action might be discarded. For example, configure PBR to forward packets that
match certain criteria through a user-specified interface. When the link of the interface fails, PBR cannot
sense the failure, and continues to forward matching packets out of the interface.
This problem can be solved by associating Track with PBR, which improves the flexibility of the PBR
application and enables PBR to sense topology changes.
After you associate a track entry with an apply clause, the detection module associated with the track
entry sends the detection result of the availability of the object (an interface or an IP address) specified
in the apply clause.
•
The Positive state of the track entry shows that the object is available, and the apply clause is valid.
•
The Negative state of the track entry shows that the object is not available, and the apply clause is
invalid.
•
The NotReady state of the track entry shows that the apply clause is valid.
The following objects can be associated with a track entry:
•
Outgoing interface.
•
Next hop.
•
Default outgoing interface.
•
Default next hop.
Configuration prerequisites
Before you associate Track with PBR, create a policy or a policy node and configure the match criteria as
well.
Configuration procedure
You can associate a nonexistent track entry with PBR. The association takes effect only after you use the
track
command to create the track entry.
To associate Track with PBR:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a policy or policy
node and enter PBR policy
node view.
policy-based-route
policy-name
[
deny
|
permit
]
node
node-number
N/A