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

Defining a continue clause, Command, Remarks, apply, continue, community, apply extcommunity, additive

Page 270 highlights

Step 6. Set a cost for routing information. 7. Set a cost type for routing information. 8. Set the extended community attribute for BGP routing. Command Remarks apply cost [ + | - ] value Optional. Not set by default. apply cost-type [ internal | type-1 | Optional. type-2 ] Not set by default. apply extcommunity { { rt Optional. route-target }& [ additive ] } Not set by default. 9. Set the next hop. Optional. • Set the next hop for IPv4 routes: Not set by default. apply ip-address next-hop The setting does not apply to ip-address redistributed routing information. • Set the next hop for IPv6 routes: The apply ip-address next-hop apply ipv6 next-hop and apply ipv6 next-hop ipv6-address commands do not apply to redistributed IPv4 and IPv6 routes. 10. Set the local preference for BGP routing information. apply local-preference preference Optional. Not set by default. 11. Set the ORIGIN attribute for BGP routing information. apply origin { egp as-number | igp Optional. | incomplete } Not set by default. 12. Set the preference for the routing protocol. apply preference preference Optional. Not set by default. 13. Set a preferred value for BGP routing information. apply preferred-value preferred-value Optional. Not set by default. 14. Set a tag value for RIP, or OSPF routing information. apply tag value Optional. Not set by default. The difference between IPv4 and IPv6 apply clauses is the command for setting the next hop for routing information. Defining a continue clause Follow these guidelines when you define a continue clause: • If you configure the same type of apply clauses that set different values (including the apply community and apply extcommunity clauses with the additive keyword) on nodes that are combined by the continue clause, the apply clause configured on the last matching node takes effect. • If you configure the apply community clause for multiple nodes that are combined by the continue clause, the apply comm-list delete clause configured on the current node cannot delete the COMMUNITY attributes of preceding nodes. To define a continue clause: 260

  • 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

260
Step
Command
Remarks
6.
Set a cost for routing
information.
apply cost
[
+
|
-
]
value
Optional.
Not set by default.
7.
Set a cost type for routing
information.
apply cost-type
[
internal
|
type-1
|
type
-
2
]
Optional.
Not set by default.
8.
Set the extended community
attribute for BGP routing.
apply extcommunity
{ {
rt
route-target
}&<1-16> [
additive
] }
Optional.
Not set by default.
9.
Set the next hop.
Set the next hop for IPv4 routes:
apply ip-address next-hop
ip-address
Set the next hop for IPv6 routes:
apply ipv6 next-hop
ipv6-address
Optional.
Not set by default.
The setting does not apply to
redistributed routing information.
The apply ip-address next-hop
and apply ipv6 next-hop
commands do not apply to
redistributed IPv4 and IPv6
routes.
10.
Set the local preference for
BGP routing information.
apply local-preference
preference
Optional.
Not set by default.
11.
Set the ORIGIN attribute for
BGP routing information.
apply origin
{
egp
as-number
|
igp
|
incomplete
}
Optional.
Not set by default.
12.
Set the preference for the
routing protocol.
apply preference
preference
Optional.
Not set by default.
13.
Set a preferred value for BGP
routing information.
apply preferred-value
preferred-value
Optional.
Not set by default.
14.
Set a tag value for RIP, or OSPF
routing information.
apply tag
value
Optional.
Not set by default.
The difference between IPv4 and IPv6
apply
clauses is the command for setting the next hop for routing
information.
Defining a continue clause
Follow these guidelines when you define a
continue
clause:
If you configure the same type of
apply
clauses that set different values (including the
apply
community
and
apply extcommunity
clauses with the
additive
keyword) on nodes that are
combined by the
continue
clause, the
apply
clause configured on the last matching node takes
effect.
If you configure the
apply community
clause for multiple nodes that are combined by the
continue
clause, the
apply comm-list delete
clause configured on the current node cannot delete the
COMMUNITY attributes of preceding nodes.
To define a
continue
clause: