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

Configuring OSPF between MCE and VPN site, Con the MCE

Page 287 highlights

Configuring OSPF between MCE and VPN site An OSPF process belongs to the public network or a single VPN instance. If you create an OSPF process without binding it to a VPN instance, the process belongs to the public network. By configuring OSPF process-to-VPN instance bindings on a MCE, you allow routes of different VPNs to be exchanged between the MCE and the sites through different OSPF processes, ensuring the separation and security of VPN routes. An OSPF process can belong to only one VPN instance, but one VPN instance can use multiple OSPF processes to advertise the VPN routes. An OSPF process that is bound with a VPN instance does not use the public network router ID configured in system view. Therefore, you must configure a router ID when starting the OSPF process. All OSPF processes for the same VPN must be configured with the same OSPF domain ID to ensure correct route advertisement. For more information about OSPF, see Layer 3-IP Routing Configuration Guide. To configure OSPF between MCE and VPN site: Step Command Remarks 1. Enter system view. system-view N/A 2. Create an OSPF process for a ospf [ process-id | router-id VPN instance and enter OSPF router-id | vpn-instance view. vpn-instance-name ] * Perform this configuration on the MCE. On a VPN site, create a normal OSPF process. 3. Configure the OSPF domain ID. domain-id domain-id [ secondary ] Optional. 0 by default. Perform this configuration on the MCE. On a VPN site, perform the common OSPF configuration. import-route protocol [ process-id 4. Redistribute remote site routes | allow-ibgp ] [ cost cost | type advertised by the PE. type | tag tag | route-policy route-policy-name ] * By default, no route of any other routing protocol is redistributed into OSPF. 5. Create an OSPF area and enter OSPF area view. area area-id By default, no OSPF area is created. 6. Enable OSPF on the interface By default, an interface neither attached to the specified network ip-address wildcard-mask belongs to any area nor runs network in the area. OSPF. Configuring EBGP between MCE and VPN site To use EBGP for exchanging routing information between an MCE and VPN sites, you must configure a BGP peer for each VPN instance on the MCE, and redistribute the IGP routes of each VPN instance on the VPN sites. If EBGP is used for route exchange, you also can configure filtering policies to filter the received routes and the routes to be advertised. 1. Configure the MCE: Step 1. Enter system view. Command system-view 277 Remarks N/A

  • 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

277
Configuring OSPF between MCE and VPN site
An OSPF process belongs to the public network or a single VPN instance. If you create an OSPF process
without binding it to a VPN instance, the process belongs to the public network.
By configuring OSPF process-to-VPN instance bindings on a MCE, you allow routes of different VPNs to
be exchanged between the MCE and the sites through different OSPF processes, ensuring the separation
and security of VPN routes.
An OSPF process can belong to only one VPN instance, but one VPN instance can use multiple OSPF
processes to advertise the VPN routes.
An OSPF process that is bound with a VPN instance does not use the public network router ID configured
in system view. Therefore, you must configure a router ID when starting the OSPF process. All OSPF
processes for the same VPN must be configured with the same OSPF domain ID to ensure correct route
advertisement.
For more information about OSPF, see
Layer 3—IP Routing Configuration Guide
.
To configure OSPF between MCE and VPN site:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create an OSPF process for a
VPN instance and enter OSPF
view.
ospf
[
process-id
|
router-id
router-id
|
vpn-instance
vpn-instance-name
] *
Perform this configuration on the
MCE. On a VPN site, create a
normal OSPF process.
3.
Configure the OSPF domain
ID.
domain-id
domain-id
[
secondary
]
Optional.
0 by default.
Perform this configuration on the
MCE. On a VPN site, perform the
common OSPF configuration.
4.
Redistribute remote site routes
advertised by the PE.
import-route
protocol
[
process-id
|
allow-ibgp
] [
cost
cost
|
type
type
|
tag
tag
|
route-policy
route-policy-name
] *
By default, no route of any other
routing protocol is redistributed
into OSPF.
5.
Create an OSPF area and
enter OSPF area view.
area
area-id
By default, no OSPF area is
created.
6.
Enable OSPF on the interface
attached to the specified
network in the area.
network
ip-address wildcard-mask
By default, an interface neither
belongs to any area nor runs
OSPF.
Configuring EBGP between MCE and VPN site
To use EBGP for exchanging routing information between an MCE and VPN sites, you must configure a
BGP peer for each VPN instance on the MCE, and redistribute the IGP routes of each VPN instance on
the VPN sites.
If EBGP is used for route exchange, you also can configure filtering policies to filter the received routes
and the routes to be advertised.
1.
Configure the MCE:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A