D-Link DGS-3100 Stack Management Examples, Replacing Failed Stacking-Members in a Running Stack

DGS-3100 Series Gigabit Stackable Managed Switch User Manual

This section contains the following topics:

•Building New Manually Ordered Stacks

•Adding Stacking Members to an Existing Manually Ordered Stack

Building New Manually Ordered Stacks

To build new a self ordered stack:

1.Connect the units physically through the stacking ports.

2.Turn on the units, one at a time.

3.Assign the Stack Master the Unit ID of 1 using a Stack Management Interfaces either the console port, Telnet, or Embedded Web Interface.

4.Assign the Backup Master the Unit ID of 2 using a Stack Management Interfaces either the console port, Telnet, or Embedded Web Interface.

5.Assign the remaining stacking members using a Stack Management Interfaces either the console port, Telnet, or Embedded Web Interface.

6.Ensure that none of the stacking members have the same Unit ID.

7.Reboot all the stack units.

Adding Stacking Members to an Existing Manually Ordered Stack

To add units to an existing manually ordered stack:

1.Reset the new stacking units to the factory defaults by pressing the Reset button.

2.Connect the stacking members physically to the stack.

3.Turn on the switches, the new units become stacking members, but with automatically assigned Unit IDs.

4.Reassign the Unit ID manually to each of the newly added stacking members using a Stack Management Interfaces either the console port, Telnet, or Embedded Web Interface. This step is optional, and the stack is operational even if some unit IDs were manually configured while others are self-assigned.

5.Reboot the stacking members to ensure the Unit ID is permanent.

Stack Management Examples

This section contains information for troubleshooting stacking, and includes the following topics:

•Replacing Failed Stacking-Members in a Running Stack

•Replacing a Failed Stack Master

•Dividing Stacks

•Merging Stacks

•Stacking Cable Failure

•Inserting Excess Stacking Members

Replacing Failed Stacking-Members in a Running Stack

This example assumes that a stacking member, other than master, has failed in a running stack, when the system administrator is notified of the system failure the stacking member is removed and replaced with a new switch.

When the stacking member fails, the Stack Master identifies the failed stacking member using the Master Discovery process. The Stack Master recognizes that the stacking member no longer responds. If the stack topology was ring topology, the Stack Master directs all other stack members to route traffic around the failed stacking member. At the same time the Stack Master notifies the system administrator of the failure using SYSLOG messages and SNMP traps.

When the failed stacking member is disconnected from the stack, all traffic is routed around the failed stacking member as stated above. As long as all other stacking connections are intact, the stack continues to run.

When a new stacking member is inserted and the stack is powered up, the following occurs:

•The new stacking member which is in stacking mode, performs the Master Discovery process, and perhaps participates in a Master Election .For more information on the Master Election process, see Electing a Stacking Master.

20