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

Configuring route-related attributes of a VPN instance, target extended community attribute list

Page 284 highlights

After creating and configuring a VPN instance, you associate the VPN instance with the interface for connecting different VPN sites. To associate a VPN instance with an interface: Step Command 1. Enter system view. system-view 2. Enter interface view. interface interface-type interface-number 3. Associate the current interface ip binding vpn-instance with the VPN instance. vpn-instance-name Remarks N/A N/A No VPN instance is associated with an interface by default. NOTE: The ip binding vpn-instance command clears the IP address of the interface on which it is configured. Be sure to reconfigure an IP address for the interface after configuring the command. Configuring route-related attributes of a VPN instance The control process of VPN route advertisement is as follows: • When a VPN route learned from a site gets redistributed into BGP, BGP associates it with a route target extended community attribute list, which is usually the export target attribute of the VPN instance associated with the site. • The VPN instance determines which routes it can accept and redistribute according to the import-extcommunity in the route target. • The VPN instance determines how to change the route targets attributes for routes to be advertised according to the export-extcommunity in the route target. IMPORTANT: • Only when BGP runs between the MCE and PE can the route target attribute be advertised to the PE along with the routing information. In other cases, configuring this attribute makes no sense. • Before associating a routing policy with a VPN instance, you must first create the routing policy. Otherwise, the default routing policy is used. To configure route related attributes of a VPN instance: Step 1. Enter system view. 2. Enter VPN instance view. 3. Associate the current VPN instance with one or more route targets. Command Remarks system-view N/A ip vpn-instance vpn-instance-name N/A vpn-target vpn-target& [ both | export-extcommunity | import-extcommunity ] A single vpn-target command can configure up to eight route targets. You can configure up to 64 route targets for a VPN instance. 274

  • 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

274
After creating and configuring a VPN instance, you associate the VPN instance with the interface for
connecting different VPN sites.
To associate a VPN instance with an interface:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter interface view.
interface
interface-type
interface-number
N/A
3.
Associate the current interface
with the VPN instance.
ip binding vpn-instance
vpn-instance-name
No VPN instance is associated
with an interface by default.
NOTE:
The
ip binding vpn-instance
command clears the IP address of the interface on which it is configured. Be
sure to reconfigure an IP address for the interface after configuring the command.
Configuring route-related attributes of a VPN instance
The control process of VPN route advertisement is as follows:
When a VPN route learned from a site gets redistributed into BGP, BGP associates it with a route
target extended community attribute list, which is usually the export target attribute of the VPN
instance associated with the site.
The VPN instance determines which routes it can accept and redistribute according to the
import-extcommunity
in the route target.
The VPN instance determines how to change the route targets attributes for routes to be advertised
according to the
export-extcommunity
in the route target.
IMPORTANT:
Only when BGP runs between the MCE and PE can the route target attribute be advertised to the PE
along with the routing information. In other cases, configuring this attribute makes no sense.
Before associating a routing policy with a VPN instance, you must first create the routing policy.
Otherwise, the default routing policy is used.
To configure route related attributes of a VPN instance:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter VPN instance view.
ip vpn-instance
vpn-instance-name
N/A
3.
Associate the current VPN
instance with one or more
route targets.
vpn-target
vpn-target
&<1-8>
[
both
|
export-extcommunity
|
import-extcommunity
]
A single
vpn-target
command can
configure up to eight route targets.
You can configure up to 64 route
targets for a VPN instance.