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

Configuring RIP between MCE and VPN site, Layer 3-IP Routing Configuration Guide

Get HP 6125G PDF manuals and user guides View all HP 6125G manuals
Add to My Manuals
Save this manual to your list of manuals

Page 286 highlights

route with a VPN instance, so that the static routes of different VPN instances can be isolated from each other. To configure static routing between MCE and VPN site: Step Command Remarks 1. Enter system view. system-view N/A • ip route-static dest-address { mask | mask-length } { gateway-address | interface-type interface-number [ gateway-address ] | vpn-instance d-vpn-instance-name gateway-address } [ preference preference-value ] Use either command. [ tag tag-value ] [ description description-text ] Perform this 2. Configure a static route • ip route-static vpn-instance configuration on the for a VPN instance. s-vpn-instance-name& dest-address { mask | MCE. On a VPN site, mask-length } { gateway-address [ public ] | configure a normal interface-type interface-number static route. [ gateway-address ] | vpn-instance d-vpn-instance-name gateway-address } [ preference preference-value ] [ tag tag-value ] [ description description-text ] 3. Configure the default precedence for static routes. ip route-static default-preference default-preference-value Optional. 60 by default. Configuring RIP between MCE and VPN site A RIP process belongs to the public network or a single VPN instance. If you create a RIP process without binding it to a VPN instance, the process belongs to the public network. By configuring RIP process-to-VPN instance bindings on a IPv6 MCE, you allow routes of different VPNs to be exchanged between the MCE and the sites through different RIP processes, ensuring the separation and security of VPN routes. For more information about RIP, see Layer 3-IP Routing Configuration Guide. To configure RIP between MCE and VPN site: Step Command Remarks 1. Enter system view. system-view N/A 2. Create a RIP process for a VPN instance and enter RIP view. rip [ process-id ] vpn-instance vpn-instance-name Perform this configuration on the MCE. On a VPN site, create a normal RIP process. 3. Enable RIP on the interface attached to the specified network. network network-address By default, RIP is disabled on an interface. import-route protocol [ process-id ] 4. Redistribute remote site routes [ allow-ibgp ] [ cost cost | By default, no route is redistributed advertised by the PE. route-policy route-policy-name | into RIP. tag tag ] * 5. Configure the default cost value for the redistributed routes. default cost value Optional. 0 by default. 276

  • 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
276
route with a VPN instance, so that the static routes of different VPN instances can be isolated from each
other.
To configure static routing between MCE and VPN site:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Configure a static route
for a VPN instance.
•
ip
route-static
dest-address
{
mask
|
mask-length
}
{
gateway-address
|
interface-type
interface-number
[
gateway-address
] |
vpn-instance
d-vpn-instance-name
gateway-address
} [
preference
preference-value
]
[
tag
tag-value
] [
description
description-text
]
•
ip route-static
vpn-instance
s-vpn-instance-name&
<1-6
>
dest-address
{
mask
|
mask-length
} {
gateway-address
[
public
] |
interface-type interface-number
[
gateway-address
] |
vpn-instance
d-vpn-instance-name gateway-address
}
[
preference
preference-value
] [
tag
tag-value
]
[
description
description-text
]
Use either command.
Perform this
configuration on the
MCE. On a VPN site,
configure a normal
static route.
3.
Configure the default
precedence for static
routes.
ip route-static default-preference
default-preference-value
Optional.
60 by default.
Configuring RIP between MCE and VPN site
A RIP process belongs to the public network or a single VPN instance. If you create a RIP process without
binding it to a VPN instance, the process belongs to the public network. By configuring RIP
process-to-VPN instance bindings on a IPv6 MCE, you allow routes of different VPNs to be exchanged
between the MCE and the sites through different RIP processes, ensuring the separation and security of
VPN routes.
For more information about RIP, see
Layer 3—IP Routing Configuration Guide
.
To configure RIP between MCE and VPN site:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a RIP process for a
VPN instance and enter RIP
view.
rip
[
process-id
]
vpn-instance
vpn-instance-name
Perform this configuration on the
MCE. On a VPN site, create a
normal RIP process.
3.
Enable RIP on the interface
attached to the specified
network.
network
network-address
By default, RIP is disabled on an
interface.
4.
Redistribute remote site routes
advertised by the PE.
import-route
protocol
[
process-id
]
[
allow-ibgp
] [
cost
cost
|
route-policy
route-policy-name
|
tag
tag
] *
By default, no route is redistributed
into RIP.
5.
Configure the default cost
value for the redistributed
routes.
default cost
value
Optional.
0 by default.