Cisco WS-C2960S-24PD-L Software Guide - Page 284

Recovery Procedures, Recovering from Lost Member Connectivity

Page 284 highlights

Recovery Procedures Chapter 9 Troubleshooting Recovery Procedures The recovery procedures in this section require that you have physical access to the switch. Recovery procedures include these topics: • Recovering from Lost Member Connectivity, page 9-18 • Recovering from a Command Switch Failure, page 9-18 • Recovering from a Lost or Forgotten Password, page 9-24 • Recovering from Corrupted Software, page 9-26 Recovering from Lost Member Connectivity Some configurations can prevent the command switch from maintaining contact with member switches. If you are unable to maintain management contact with a member, and the member switch is forwarding packets normally, check for these port-configuration conflicts: • Member switches cannot connect to the command switch through a port that is defined as a network port. For information on the network port feature, see the "Enabling a Network Port" section on page 7-6. • Member switches must connect to the command switch through a port that belongs to the same management VLAN. For more information, see the "Management VLAN" section on page 5-18. • Member switches connected to the command switch through a secured port can lose connectivity if the port is disabled due to a security violation. Secured ports are described in the "Enabling Port Security" section on page 7-10. Recovering from a Command Switch Failure You can prepare for a command switch failure by assigning an IP address to a member switch that is command-capable, making a note of the command-switch password, and cabling your cluster to provide redundant connectivity between all member switches and the replacement command switch. Hot Standby Router Protocol (HSRP) is the preferred method for providing a redundant command switch to a cluster. For more information, see the "HSRP and Standby Command Switches" section on page 5-12 and the "Creating a Cluster Standby Group" section on page 5-23. For a list of command-capable Catalyst desktop switches, see the release notes (http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/index.htm). If you have not configured a standby command switch, and your command switch loses power or fails in some other way, management contact with the member switches is lost, and a new command switch must be installed. However, connectivity between switches that are still connected is not affected, and the member switches forward packets as usual. You can manage the members as standalone switches through the console port or, if they have IP addresses, through CMS Device Manager. These sections describe how to recover if a standby command switch was not available when the command switch failed: • "Replacing a Failed Command Switch with a Cluster Member" section on page 9-19 • "Replacing a Failed Command Switch with Another Switch" section on page 9-21 • "Recovering from a Failed Command Switch Without Replacing the Command Switch" section on page 9-23 9-18 Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide 78-6511-08

  • 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
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368

9-18
Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide
78-6511-08
Chapter 9
Troubleshooting
Recovery Procedures
Recovery Procedures
The recovery procedures in this section require that you have physical access to the switch. Recovery
procedures include these topics:
Recovering from Lost Member Connectivity, page 9-18
Recovering from a Command Switch Failure, page 9-18
Recovering from a Lost or Forgotten Password, page 9-24
Recovering from Corrupted Software, page 9-26
Recovering from Lost Member Connectivity
Some configurations can prevent the command switch from maintaining contact with member switches.
If you are unable to maintain management contact with a member, and the member switch is forwarding
packets normally, check for these port-configuration conflicts:
Member switches cannot connect to the command switch through a port that is defined as a network
port. For information on the network port feature, see the
“Enabling a Network Port” section on
page 7-6
.
Member switches must connect to the command switch through a port that belongs to the same
management VLAN. For more information, see the
“Management VLAN” section on page 5-18
.
Member switches connected to the command switch through a secured port can lose connectivity if
the port is disabled due to a security violation. Secured ports are described in the
“Enabling Port
Security” section on page 7-10
.
Recovering from a Command Switch Failure
You can prepare for a command switch failure by assigning an IP address to a member switch that is
command-capable, making a note of the command-switch password, and cabling your cluster to provide
redundant connectivity between all member switches and the replacement command switch. Hot
Standby Router Protocol (HSRP) is the preferred method for providing a redundant command switch to
a cluster. For more information, see the
“HSRP and Standby Command Switches” section on page 5-12
and the
“Creating a Cluster Standby Group” section on page 5-23
. For a list of command-capable
Catalyst desktop switches, see the release notes
(
).
If you have not configured a standby command switch, and your command switch loses power or fails
in some other way, management contact with the member switches is lost, and a new command switch
must be installed. However, connectivity between switches that are still connected is not affected, and
the member switches forward packets as usual. You can manage the members as standalone switches
through the console port or, if they have IP addresses, through CMS Device Manager.
These sections describe how to recover if a standby command switch was not available when the
command switch failed:
“Replacing a Failed Command Switch with a Cluster Member” section on page 9-19
“Replacing a Failed Command Switch with Another Switch” section on page 9-21
“Recovering from a Failed Command Switch Without Replacing the Command Switch” section on
page 9-23