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

Defining an extended community list, Configuring a routing policy, Configuration prerequisites

Page 267 highlights

Defining an extended community list You can define multiple items for an extended community list that is identified by number. During matching, the relation between items is logic OR. If routing information matches one of these items, it passes the extended community list. To define an extended community list: Step 1. Enter system view. 2. Define an extended community list. Command system-view ip extcommunity-list ext-comm-list-number { deny | permit } { rt route-target }& Remarks N/A Not defined by default. Configuring a routing policy A routing policy is used to filter routing information and modify attributes of matching routing information. The match criteria of a routing policy can be configured by referencing the appropriate filters. A routing policy can comprise multiple nodes, and each routing policy node contains the following: • if-match clauses-Define the match criteria that routing information must satisfy. The matching objects are some attributes of routing information. • apply clauses-Specify the actions to be taken on routing information that has satisfied the match criteria, such as route attribute modification. • continue clauses-Specify the next routing policy node to be matched. With this clause configured, when a route matches the current routing policy node, it continues to match against the specified next node in the same routing policy. Configuration prerequisites Before configuring this task, you need to configure the filters and routing protocols. You also need to decide on the name of the routing policy and node numbers, match criteria, and attributes to be modified. Creating a routing policy Follow these guidelines when you create a routing policy: • If a routing policy node has the permit keyword specified, routing information matching all the if-match clauses of the node will be handled using the apply clauses of this node, without needing to match against the next node. If routing information does not match the node, it goes to the next node for a match. • If a routing policy node has the deny keyword specified, the apply clauses of the node is not executed. When routing information matches all the if-match clauses of the node, it cannot pass the node, or go to the next node. If route information cannot match all the if-match clauses of the node, it goes to the next node for a match. • When a routing policy has more than one node, at least one node must be configured with the permit keyword. If the routing policy is used to filter routing information, routing information that does not meet any node cannot pass the routing policy. If all nodes of the routing policy are set with the deny keyword, no routing information can pass it. 257

  • 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

257
Defining an extended community list
You can define multiple items for an extended community list that is identified by number. During
matching, the relation between items is logic OR. If routing information matches one of these items, it
passes the extended community list.
To define an extended community list:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Define an extended
community list.
ip extcommunity-list
ext-comm-list-number
{
deny
|
permit
} {
rt
route-target
}&<1-16>
Not defined by default.
Configuring a routing policy
A routing policy is used to filter routing information and modify attributes of matching routing information.
The match criteria of a routing policy can be configured by referencing the appropriate filters.
A routing policy can comprise multiple nodes, and each routing policy node contains the following:
if-match clauses
—Define the match criteria that routing information must satisfy. The matching
objects are some attributes of routing information.
apply clauses
—Specify the actions to be taken on routing information that has satisfied the match
criteria, such as route attribute modification.
continue clauses
—Specify the next routing policy node to be matched. With this clause configured,
when a route matches the current routing policy node, it continues to match against the specified
next node in the same routing policy.
Configuration prerequisites
Before configuring this task, you need to configure the filters and routing protocols. You also need to
decide on the name of the routing policy and node numbers, match criteria, and attributes to be
modified.
Creating a routing policy
Follow these guidelines when you create a routing policy:
If a routing policy node has the
permit
keyword specified, routing information matching all the
if-match
clauses of the node will be handled using the
apply
clauses of this node, without needing
to match against the next node. If routing information does not match the node, it goes to the next
node for a match.
If a routing policy node has the
deny
keyword specified, the
apply
clauses of the node is not
executed. When routing information matches all the
if-match
clauses of the node, it cannot pass the
node, or go to the next node. If route information cannot match all the
if-match
clauses of the node,
it goes to the next node for a match.
When a routing policy has more than one node, at least one node must be configured with the
permit
keyword. If the routing policy is used to filter routing information, routing information that
does not meet any node cannot pass the routing policy. If all nodes of the routing policy are set with
the
deny
keyword, no routing information can pass it.