HP 6125XLG R2306-HP 6125XLG Blade Switch Layer 3 - IP Routing Configuration Gu - Page 359

Configuring if-match clauses

Page 359 highlights

Configuring if-match clauses You can either specify no if-match clauses or multiple if-match clauses for a routing policy node. If no if-match clause is specified for a permit-mode node, all routing information can pass the node. If no if-match clause is specified for a deny-mode node, no routing information can pass the node. The if-match clauses of a routing policy node have a logical AND relationship. A route must satisfy all if-match clauses before it can be executed by the apply clauses of the node. If an if-match command exceeds the maximum length, multiple identical if-match clauses are generated. These clauses have a logical OR relationship. A route only needs to match one of them. To configure if-match clauses: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter routing policy node view. route-policy route-policy-name { deny | permit } node node-number N/A • Match IPv4 routes whose By default, no IPv4 or IPv6 destination, next hop, or source matches the IPv4 prefix list: prefix list match criterion is configured. if-match ip { address | next-hop | If the ACL used by an if-match route-source } { acl acl-number | clause does not exist, the 3. Match routes whose destination, prefix-list prefix-list-name } clause is always satisfied. If next hop, or source matches a • Match IPv6 routes whose no rules of the specified ACL specified prefix list. destination, next hop, or source are matched or the match matches the IPv6 prefix list: rules are inactive, the clause if-match ipv6 { address | is not satisfied. next-hop | route-source } { acl acl6-number | prefix-list prefix-list-name } The ACL specified in an if-match clause must be a non-VPN ACL. 4. Match BGP routes whose AS_PATH attribute matches a specified AS path list. if-match as-path as-path-number& By default, no AS path match criterion is configured. if-match community 5. Match BGP routes whose { { basic-community-list-number | COMMUNITY attribute matches name comm-list-name } a specified community list. [ whole-match ] | By default, no COMMUNITY match criterion is matched. adv-community-list-number }& 6. Match routes having the specified cost. 7. Match BGP routes whose extended community attribute matches a specified extended community list. if-match cost value if-match extcommunity ext-comm-list-number& By default, no cost match criterion is configured. By default, no extended community list match criterion is configured. 8. Match routes having the specified output interface. if-match interface { interface-type interface-number }& By default, no output interface match criterion is configured. This command is not supported by BGP. 348

  • 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
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414

348
Configuring if-match clauses
You can either specify no
if-match
clauses or multiple
if-match
clauses for a routing policy node. If no
if-match
clause is specified for a permit-mode node, all routing information can pass the node. If no
if-match
clause is specified for a deny-mode node, no routing information can pass the node.
The
if-match
clauses of a routing policy node have a logical AND relationship. A route must satisfy all
if-match
clauses before it can be executed by the
apply
clauses of the node. If an
if-match
command
exceeds the maximum length, multiple identical
if-match
clauses are generated. These clauses have a
logical OR relationship. A route only needs to match one of them.
To configure
if-match
clauses:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter routing policy node view.
route-policy
route-policy-name
{
deny
|
permit
}
node
node-number
N/A
3.
Match routes whose destination,
next hop, or source matches a
specified prefix list.
Match IPv4 routes whose
destination, next hop, or source
matches the IPv4 prefix list:
if-match ip
{
address
|
next-hop
|
route-source
} {
acl
acl-number
|
prefix-list
prefix-list-name
}
Match IPv6 routes whose
destination, next hop, or source
matches the IPv6 prefix list:
if-match ipv6
{
address
|
next-hop
|
route-source
} {
acl
acl6-number
|
prefix-list
prefix-list-name
}
By default, no IPv4 or IPv6
prefix list match criterion is
configured.
If the ACL used by an
if-match
clause does not exist, the
clause is always satisfied. If
no rules of the specified ACL
are matched or the match
rules are inactive, the clause
is not satisfied.
The ACL specified in an
if-match
clause must be a
non-VPN ACL.
4.
Match BGP routes whose
AS_PATH attribute matches a
specified AS path list.
if-match as-path
as-path-number
&<1-32>
By default, no AS path match
criterion is configured.
5.
Match BGP routes whose
COMMUNITY attribute matches
a specified community list.
if-match community
{
{
basic-community-list-number
|
name
comm-list-name
}
[
whole-match
] |
adv-community-list-number
}&<1-32>
By default, no COMMUNITY
match criterion is matched.
6.
Match routes having the
specified cost.
if-match cost
value
By default, no cost match
criterion is configured.
7.
Match BGP routes whose
extended community attribute
matches a specified extended
community list.
if-match extcommunity
ext-comm-list-number
&<1-32>
By default, no extended
community list match criterion
is configured.
8.
Match routes having the
specified output interface.
if-match interface
{
interface-type
interface-number
}&<1-16>
By default, no output interface
match criterion is configured.
This command is not
supported by BGP.