White Paper

Figure 9. Adding a New Member to an Existing Stack

If all went well, traffic on the exiting members was minimally interrupted. There were at least two interruptions. The

first occurred when the FlexStack cable was removed in step 3. The other interruption occurred when the new

switch joined the stack after being powered on (step 7). In between the two interruptions, traffic will continue to be

switched over the existing members and the operational FlexStack links.

Removing Members from an Existing Stack

FlexStack remembers all members that have been members. When a member is physically removed or just

powered down, FlexStack still considers that switch a member, just not currently active. The reason that the stack

remembers members that have been removed is because most of the time the member comes back. For example,

when a member is powered off, then powered back on, the member will rejoin the existing stack, and all the

member-specific configuration will be reapplied when it completes the boot process. This is the most common

occurrence.

If the removal is permanent, then it is recommended that the stack configuration be “cleaned up.” The member will

be deleted from the stack configuration. Here is an example of a command to remove stack member 4 from the

configuration after it has been physically removed from the stack:

C2960-48(config)#no switch 4 provision