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

Troubleshooting RIP, No RIP updates received, Symptom, Analysis, Solution, Route oscillation occurred

Page 57 highlights

NextHop: 192.168.3.2 BkNextHop: 0.0.0.0 RelyNextHop: 0.0.0.0 Tunnel ID: 0x0 BKTunnel ID: 0x0 State: Active Adv Tag: 0 Interface: vlan-interface 300 BkInterface: Neighbor : 192.168.3.2 Label: NULL BKLabel: NULL Age: 00h18m40s Troubleshooting RIP No RIP updates received Symptom No RIP updates are received when the links function. Analysis After enabling RIP, you must use the network command to enable corresponding interfaces. Make sure no interfaces are disabled from handling RIP messages. If the peer is configured to send multicast messages, the same must be configured on the local end. Solution 1. Use the display current-configuration command to verify RIP configuration. 2. Use the display rip command to verify whether an interface is disabled. Route oscillation occurred Symptom When all links function, route oscillation occurs on the RIP network. After displaying the routing table, you may find some routes intermittently appear and disappear in the routing table. Analysis In the RIP network, make sure that all the same timers within the entire network are identical and have logical relationships between them. For example, the timeout timer value must be greater than the update timer value. Solution 1. Use the display rip command to verify the configuration of RIP timers. 2. Use the timers command to adjust timers properly. 47

  • 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

47
NextHop: 192.168.3.2
Interface: vlan-interface 300
BkNextHop: 0.0.0.0
BkInterface:
RelyNextHop: 0.0.0.0
Neighbor : 192.168.3.2
Tunnel ID: 0x0
Label: NULL
BKTunnel ID: 0x0
BKLabel: NULL
State: Active Adv
Age: 00h18m40s
Tag: 0
Troubleshooting RIP
No RIP updates received
Symptom
No RIP updates are received when the links function.
Analysis
After enabling RIP, you must use the
network
command to enable corresponding interfaces. Make sure
no interfaces are disabled from handling RIP messages.
If the peer is configured to send multicast messages, the same must be configured on the local end.
Solution
1.
Use the
display current-configuration
command to verify RIP configuration.
2.
Use the
display rip
command to verify whether an interface is disabled.
Route oscillation occurred
Symptom
When all links function, route oscillation occurs on the RIP network. After displaying the routing table, you
may find some routes intermittently appear and disappear in the routing table.
Analysis
In the RIP network, make sure that all the same timers within the entire network are identical and have
logical relationships between them. For example, the timeout timer value must be greater than the update
timer value.
Solution
1.
Use the
display rip
command to verify the configuration of RIP timers.
2.
Use the
timers
command to adjust timers properly.