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

Notification, Keepalive, Route-refresh, BGP update message format

Page 129 highlights

Figure 45 BGP update message format Each update message can advertise a group of feasible routes with identical attributes, and the routes are contained in the network layer reachability information (NLRI) field. The path attributes field carries the attributes of these routes. Each update message can also carry multiple withdrawn routes in the withdrawn routes field. Major fields of the BGP update message are as follows: • Unfeasible routes length-The total length of the withdrawn routes field in bytes. A value of 0 indicates no route is withdrawn from service, nor is the withdrawn routes field present in this update message. • Withdrawn routes-This is a variable length field that contains a list of withdrawn IP prefixes. • Total path attribute length-Total length of the path attributes field in bytes. A value of 0 indicates that no NLRI field is present in this update message. • Path attributes-List of path attributes related to NLRI. Each path attribute is a triple of variable length. BGP uses these attributes to avoid routing loops, and perform routing and protocol extensions. • NLRI-Each feasible route is represented as . Notification A notification message is sent when an error is detected. The BGP connection is closed immediately after sending it. Figure 46 BGP notification message format 0 7 15 31 Error code Error subCode Data Major fields of the BGP notification message are as follows: • Error code-Type of notification. • Error subcode-Specific information about the nature of the reported error. • Data-Used to diagnose the reason for the notification. The contents of the data field depend on the error code and error subcode. Erroneous data can be recorded in the data field. The data field length is variable. Keepalive Keepalive messages are sent between peers to maintain connectivity. Its format contains only the message header. Route-refresh A route-refresh message is sent to a peer to request the specified address family routing information. 119

  • 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

119
Figure 45
BGP update message format
Each update message can advertise a group of feasible routes with identical attributes, and the routes
are contained in the network layer reachability information (NLRI) field. The path attributes field carries
the attributes of these routes. Each update message can also carry multiple withdrawn routes in the
withdrawn routes field.
Major fields of the BGP update message are as follows:
Unfeasible routes length
—The total length of the withdrawn routes field in bytes. A value of 0
indicates no route is withdrawn from service, nor is the withdrawn routes field present in this update
message.
Withdrawn routes
—This is a variable length field that contains a list of withdrawn IP prefixes.
Total path attribute length
—Total length of the path attributes field in bytes. A value of 0 indicates
that no NLRI field is present in this update message.
Path attributes
—List of path attributes related to NLRI. Each path attribute is a triple <attribute type,
attribute length, attribute value> of variable length. BGP uses these attributes to avoid routing loops,
and perform routing and protocol extensions.
NLRI
—Each feasible route is represented as <length, prefix>.
Notification
A notification message is sent when an error is detected. The BGP connection is closed immediately after
sending it.
Figure 46
BGP notification message format
Major fields of the BGP notification message are as follows:
Error code
—Type of notification.
Error subcode
—Specific information about the nature of the reported error.
Data
—Used to diagnose the reason for the notification. The contents of the data field depend on the
error code and error subcode. Erroneous data can be recorded in the data field. The data field
length is variable.
Keepalive
Keepalive messages are sent between peers to maintain connectivity. Its format contains only the
message header.
Route-refresh
A route-refresh message is sent to a peer to request the specified address family routing information.
0
7
15
31
Data
Error code
Error subCode