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

RIP operation, RIP versions, RIP message format, Supports masks, route summarization

Page 28 highlights

• Split horizon-Disables RIP from sending routing information on the interface from which the information was learned to prevent routing loops and save bandwidth. • Poison reverse-Enables RIP to set the metric of routes received from a neighbor to 16 and sends back these routes to the neighbor so the neighbor can delete such information from its routing table. • Triggered updates-RIP immediately advertises triggered updates for topology changes to reduce the possibility of routing loops and to speed up network convergence. RIP operation RIP works as follows: 1. RIP sends request messages to neighboring routers. Neighboring routers return response messages containing their routing tables. 2. RIP uses the received responses to update its local routing table and sends triggered update messages to its neighbors. All RIP routers on the network do this to learn latest routing information. 3. RIP periodically sends the local routing table to its neighbors. After a RIP neighbor receives the message, it updates its routing table, selects optimal routes, and sends an update to other neighbors. RIP ages routes to keep only valid routes. RIP versions There are two RIP versions, RIPv1 and RIPv2. RIPv1 is a classful routing protocol. It advertises messages through broadcast only. RIPv1 messages do not carry mask information, so RIPv1 can only recognize natural networks such as Class A, B, and C. For this reason, RIPv1 does not support discontiguous subnets. RIPv2 is a classless routing protocol. It has the following advantages over RIPv1: • Supports route tags to implement flexible route control through routing policies. • Supports masks, route summarization, and Classless Inter-Domain Routing (CIDR). • Supports designated next hops to select the best ones on broadcast networks. • Supports multicasting route updates so only RIPv2 routers can receive these updates to reduce resource consumption. • Supports simple authentication and MD5 authentication to enhance security. NOTE: RIPv2 supports two transmission modes: broadcast and multicast. Multicast is the default mode using 224.0.0.9 as the multicast address. An interface operating in RIPv2 broadcast mode can also receive RIPv1 messages. RIP message format A RIP message consists of a header and up to 25 route entries. (A RIPv2 authentication message uses the first route entry as the authentication entry, leaving 24 available.) 18

  • 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

18
Split horizon
—Disables RIP from sending routing information on the interface from which the
information was learned to prevent routing loops and save bandwidth.
Poison reverse
—Enables RIP to set the metric of routes received from a neighbor to 16 and sends
back these routes to the neighbor so the neighbor can delete such information from its routing table.
Triggered updates
—RIP immediately advertises triggered updates for topology changes to reduce
the possibility of routing loops and to speed up network convergence.
RIP operation
RIP works as follows:
1.
RIP sends request messages to neighboring routers. Neighboring routers return response
messages containing their routing tables.
2.
RIP uses the received responses to update its local routing table and sends triggered update
messages to its neighbors. All RIP routers on the network do this to learn latest routing information.
3.
RIP periodically sends the local routing table to its neighbors. After a RIP neighbor receives the
message, it updates its routing table, selects optimal routes, and sends an update to other
neighbors. RIP ages routes to keep only valid routes.
RIP versions
There are two RIP versions, RIPv1 and RIPv2.
RIPv1 is a classful routing protocol. It advertises messages through broadcast only. RIPv1 messages do
not carry mask information, so RIPv1 can only recognize natural networks such as Class A, B, and C. For
this reason, RIPv1 does not support discontiguous subnets.
RIPv2 is a classless routing protocol. It has the following advantages over RIPv1:
Supports route tags to implement flexible route control through routing policies.
Supports masks, route summarization, and Classless Inter-Domain Routing (CIDR).
Supports designated next hops to select the best ones on broadcast networks.
Supports multicasting route updates so only RIPv2 routers can receive these updates to reduce
resource consumption.
Supports simple authentication and MD5 authentication to enhance security.
NOTE:
RIPv2 supports two transmission modes: broadcast and multicast. Multicast is the default mode using
224.0.0.9 as the multicast address. An interface operating in RIPv2 broadcast mode can also receive
RIPv1 messages.
RIP message format
A RIP message consists of a header and up to 25 route entries. (A RIPv2 authentication message uses the
first route entry as the authentication entry, leaving 24 available.)