HP 6125G HP 6125G & 6125G/XG Blade Switches Layer 3 - IP Routing Confi - Page 268

Defining if-match clauses, You can specify any number

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

To create a routing policy: Step 1. Enter system view. 2. Create a routing policy, specify a node for it, and enter routing policy view. Command system-view route-policy route-policy-name { deny | permit } node node-number Defining if-match clauses Follow these guidelines when you define if-match clauses: • The if-match clauses of a routing policy node are in logic AND relationship. Routing information must satisfy all of its if-match clauses before being executed with its apply clauses. If an if-match command exceeds the maximum length, multiple identical if-match clauses are generated. These clauses are in logical OR relationship. Routing information only needs to match one of them. • You can specify any number of if-match clauses for a routing policy node. If no if-match clause is specified, and the routing policy node is in permit mode, all routing information can pass the node. If it is in deny mode, no routing information can pass it. • If the ACL referenced by an if-match clause does not exist, the clause is always satisfied; if no rules of the referenced ACL are matched or the matching rule is inactive, the clause is not satisfied. • An ACL specified in an if-match clause must be a non-VPN ACL. • The if-match commands for matching IPv4 destination, next hop, and source address are different from those for matching IPv6 ones. • BGP does not support criteria for matching against outbound interfaces of routing information. To define if-match clauses: Step 1. Enter system view. Command system-view Remarks N/A 2. Enter routing policy view. 3. Define match criteria for IPv4 routes. route-policy route-policy-name { deny | permit } node node-number N/A • Match IPv4 routing information specified in the ACL: if-match acl acl-number • Match IPv4 routing information specified in the IP prefix list: if-match ip-prefix ip-prefix-name. • Match IPv4 routing information whose next hop or source is specified in the ACL or IP prefix list: if-match ip { next-hop | route-source } { acl acl-number | ip-prefix ip-prefix-name } Optional. Not configured by default. 4. Match IPv6 routing information whose if-match ipv6 { address | next-hop | Optional. next hop or source is specified in the ACL route-source } { acl acl-number | or IP prefix list. prefix-list ipv6-prefix-name } Not configured by default. 258

  • 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
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
258
To create a routing policy:
Step
Command
1.
Enter system view.
system-view
2.
Create a routing policy,
specify a node for it, and
enter routing policy view.
route-policy
route-policy-name
{
deny
|
permit
}
node
node-number
Defining if-match clauses
Follow these guidelines when you define
if-match
clauses:
•
The
if-match
clauses of a routing policy node are in logic AND relationship. Routing information
must satisfy all of its
if-match
clauses before being executed with its
apply
clauses. If an
if-match
command exceeds the maximum length, multiple identical
if-match
clauses are generated. These
clauses are in logical OR relationship. Routing information only needs to match one of them.
•
You can specify any number of
if-match
clauses for a routing policy node. If no
if-match
clause is
specified, and the routing policy node is in
permit
mode, all routing information can pass the node.
If it is in
deny
mode, no routing information can pass it.
•
If the ACL referenced by an
if-match
clause does not exist, the clause is always satisfied; if no rules
of the referenced ACL are matched or the matching rule is inactive, the clause is not satisfied.
•
An ACL specified in an
if-match
clause must be a non-VPN ACL.
•
The
if-match
commands for matching IPv4 destination, next hop, and source address are different
from those for matching IPv6 ones.
•
BGP does not support criteria for matching against outbound interfaces of routing information.
To define
if-match
clauses:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter routing policy view.
route-policy
route-policy-name
{
deny
|
permit
}
node
node-number
N/A
3.
Define match criteria for IPv4 routes.
•
Match IPv4 routing information
specified in the ACL:
if-match
acl
acl-number
•
Match IPv4 routing information
specified in the IP prefix list:
if-match ip-prefix
ip-prefix-name.
•
Match IPv4 routing information
whose next hop or source is
specified in the ACL or IP prefix
list:
if-match ip
{
next-hop
|
route-source
}
{
acl
acl-number
|
ip-prefix
ip-prefix-name
}
Optional.
Not configured by
default.
4.
Match IPv6 routing information whose
next hop or source is specified in the ACL
or IP prefix list.
if-match ipv6
{
address
|
next-hop
|
route-source
} {
acl
acl-number
|
prefix-list
ipv6-prefix-name
}
Optional.
Not configured by
default.