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

Configuring a BGP confederation, Configuring confederation compatibility

Page 166 highlights

Step Command 1. Enter system view. system-view 2. Enter BGP view. bgp as-number 3. Configure the router as a route reflector and specify a peer or peer { group-name | ip-address } peer group as its client. reflect-client 4. Enable route reflection between clients. reflect between-clients 5. Configure the cluster ID of the route reflector. reflector cluster-id cluster-id Remarks N/A N/A Not configured by default. Optional. Enabled by default. Optional. By default, a route reflector uses its router ID as the cluster ID. Configuring a BGP confederation Configuring a BGP confederation is another way for reducing IBGP connections in an AS. A confederation contains sub ASs. In each sub AS, IBGP peers are fully meshed. Between sub ASs, EBGP connections are established. If routers not compliant with RFC 3065 exist in the confederation, use the confederation nonstandard command to make the local router compatible with these routers. Configuring a BGP confederation After you split an AS into multiple sub ASs, you can configure a router in a sub AS as follows: 1. Enable BGP and specify the AS number of the router. 2. Specify the confederation ID. From an outsider's perspective, the sub ASs of the confederation is a single AS, which is identified by the confederation ID. 3. If the router must establish EBGP connections to other sub ASs, you must specify the peering sub ASs in the confederation. A confederation contains a maximum of 32 sub ASs. The AS number of a sub AS is effective only in the confederation. To configure a BGP confederation: Step 1. Enter system view. 2. Enter BGP view. 3. Configure a confederation ID. 4. Specify peering sub ASs in the confederation. Command system-view bgp as-number confederation id as-number confederation peer-as as-number-list Remarks N/A N/A Not configured by default. Not configured by default. Configuring confederation compatibility If some other routers in the confederation do not comply with RFC 3065, enable confederation compatibility to allow the router to work with those routers. 156

  • 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

156
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Configure the router as a route
reflector and specify a peer or
peer group as its client.
peer
{
group-name
|
ip-address
}
reflect-client
Not configured by default.
4.
Enable route reflection
between clients.
reflect between-clients
Optional.
Enabled by default.
5.
Configure the cluster ID of the
route reflector.
reflector cluster-id
cluster-id
Optional.
By default, a route reflector uses its
router ID as the cluster ID.
Configuring a BGP confederation
Configuring a BGP confederation is another way for reducing IBGP connections in an AS.
A confederation contains sub ASs. In each sub AS, IBGP peers are fully meshed. Between sub ASs, EBGP
connections are established.
If routers not compliant with RFC 3065 exist in the confederation, use the
confederation nonstandard
command to make the local router compatible with these routers.
Configuring a BGP confederation
After you split an AS into multiple sub ASs, you can configure a router in a sub AS as follows:
1.
Enable BGP and specify the AS number of the router.
2.
Specify the confederation ID. From an outsider’s perspective, the sub ASs of the confederation is
a single AS, which is identified by the confederation ID.
3.
If the router must establish EBGP connections to other sub ASs, you must specify the peering sub
ASs in the confederation.
A confederation contains a maximum of 32 sub ASs. The AS number of a sub AS is effective only in the
confederation.
To configure a BGP confederation:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Configure a confederation ID.
confederation id
as-number
Not configured by
default.
4.
Specify peering sub ASs in the
confederation.
confederation peer-as
as-number-list
Not configured by
default.
Configuring confederation compatibility
If some other routers in the confederation do not comply with RFC 3065, enable confederation
compatibility to allow the router to work with those routers.