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

Configuring an MCE, Configuring VPN instances, Creating a VPN Instance

Page 283 highlights

The following routing protocols can be used between MCE and PE devices for routing formation exchange: • Static route • RIP • OSPF • IBGP • EBGP For information about routing protocol configuration and route import, see Layer 3-IP Routing Configuration Guide. Configuring an MCE Configuring VPN instances Configuring VPN instances is required in all MCE networking schemes. By configuring VPN instances on a PE, you isolate not only VPN routes from public network routes, but also routes of a VPN from those of another VPN. This feature allows VPN instances to be used in networking scenarios besides MCE. Creating a VPN Instance A VPN instance is associated with a site. It is a collection of the VPN membership and routing rules of its associated site. A VPN instance does not necessarily correspond to one VPN. A VPN instance takes effect only after you configure an RD for it. Before configuring an RD for a VPN instance, you can configure no other parameters for the instance but a description. You can configure a description for a VPN instance to record its related information, such as its relationship with a certain VPN. To create and configure a VPN instance: Step 1. Enter system view. 2. Create a VPN instance and enter VPN instance view. 3. Configure an RD for the VPN instance. 4. Configure a description for the VPN instance. Command system-view ip vpn-instance vpn-instance-name route-distinguisher route-distinguisher description text Remarks N/A N/A For easy management, set the same RD for the same VPN instance on the MCE and PE. Optional Associating a VPN instance with an interface In an MPLS L3VPN application, you must associate VPN instances with the interfaces connecting the PEs. In a tunneling application, you must associate VPN instances with the tunnel interfaces connecting the peer MCE devices or CE devices. You can add a management Ethernet interface on the switch to a VPN so that the IP address of the interface only participates in the route calculation of the specified VPN. 273

  • 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

273
The following routing protocols can be used between MCE and PE devices for routing formation
exchange:
Static route
RIP
OSPF
IBGP
EBGP
For information about routing protocol configuration and route import, see
Layer 3—IP Routing
Configuration Guide
.
Configuring an MCE
Configuring VPN instances
Configuring VPN instances is required in all MCE networking schemes.
By configuring VPN instances on a PE, you isolate not only VPN routes from public network routes, but
also routes of a VPN from those of another VPN. This feature allows VPN instances to be used in
networking scenarios besides MCE.
Creating a VPN Instance
A VPN instance is associated with a site. It is a collection of the VPN membership and routing rules of its
associated site. A VPN instance does not necessarily correspond to one VPN.
A VPN instance takes effect only after you configure an RD for it. Before configuring an RD for a VPN
instance, you can configure no other parameters for the instance but a description.
You can configure a description for a VPN instance to record its related information, such as its
relationship with a certain VPN.
To create and configure a VPN instance:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a VPN instance and
enter VPN instance view.
ip vpn-instance
vpn-instance-name
N/A
3.
Configure an RD for the VPN
instance.
route-distinguisher
route-distinguisher
For easy management, set the
same RD for the same VPN
instance on the MCE and PE.
4.
Configure a description for
the VPN instance.
description
text
Optional
Associating a VPN instance with an interface
In an MPLS L3VPN application, you must associate VPN instances with the interfaces connecting the PEs.
In a tunneling application, you must associate VPN instances with the tunnel interfaces connecting the
peer MCE devices or CE devices.
You can add a management Ethernet interface on the switch to a VPN so that the IP address of the
interface only participates in the route calculation of the specified VPN.