Cisco SGE2000P Administration Guide - Page 32

Splitting a Stack, The Stack Master and Backup Master Units Remain in a Group - last ports not working

Get Cisco SGE2000P - Small Business Managed Switch PDF manuals and user guides
UPC - 745883572137
View all Cisco SGE2000P manuals
Add to My Manuals
Save this manual to your list of manuals

Page 32 highlights

3. The Stack Master performs unit and port configuration for the incoming unit. • Any configuration information that is relevant to the number assigned to the incoming unit is applied by the Stack Master. For example, if the incoming unit is assigned the same Unit ID of the unit it replaced, then when possible, it receives the same configuration as the failed unit. • If the incoming unit is identical to the replaced unit, the entire configuration of the replaced unit is applied to the incoming unit and the stack returns to the state it was in before unit failure. Splitting a Stack A working stack can be split into two groups, either by failure of a stacking link connecting two units in the stack, or by a failed unit in a chain topology that causes disconnection between two units in the stack. In this case, each group is considered as an independent running stack configuration. For each group, there are three scenarios. The Stack Master and Backup Master Units Remain in a Group In this scenario, the Stack Master routes around the missing units. The Master Discovery, Master Election and Unit ID Allocation & Duplicate Unit ID Conflict Resolution processes occur with the following results: • Any configuration information contained in the Stack Master that is relevant to the units which remained in the split group remains unchanged. • Topology information (the information for each unit on how to send traffic to any other unit in the stack) managed by the Stack Master includes only units that are reachable (connected) following the split. • The split stack continues to work as it previously did, but with fewer units. - No unit ID changes are performed in each of the split stacks. - The Stack Master notifies the system administrator of the removed units and ports that belong to the unreachable units by sending SYSLOG messages and SNMP traps. They are reported as "not present." 27 Linksys One Ready Communications Solution 3 Chapter 3: Connecting the Switch Stack Troubleshooting and Maintenance Chapter

  • 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
Chapter
3
27
Chapter 3: Connecting the Switch
Stack Troubleshooting and Maintenance
Linksys One Ready Communications Solution
3.
The Stack Master performs unit and port configuration for the incoming unit.
•
Any configuration information that is relevant to the number assigned to the
incoming unit is applied by the Stack Master. For example, if the incoming unit is
assigned the same Unit ID of the unit it replaced, then when possible, it receives the
same configuration as the failed unit.
•
If the incoming unit is identical to the replaced unit, the entire configuration of the
replaced unit is applied to the incoming unit and the stack returns to the state it was
in before unit failure.
Splitting a Stack
A working stack can be split into two groups, either by failure of a stacking link connecting
two units in the stack, or by a failed unit in a chain topology that causes disconnection
between two units in the stack. In this case, each group is considered as an independent
running stack configuration. For each group, there are three scenarios.
The Stack Master and Backup Master Units Remain in a Group
In this scenario, the Stack Master routes around the missing units. The Master Discovery,
Master Election and Unit ID Allocation & Duplicate Unit ID Conflict Resolution processes
occur with the following results:
•
Any configuration information contained in the Stack Master that is relevant to the units
which remained in the split group remains unchanged.
•
Topology information (the information for each unit on how to send traffic to any other
unit in the stack) managed by the Stack Master includes only units that are reachable
(connected) following the split.
•
The split stack continues to work as it previously did, but with fewer units.
-
No unit ID changes are performed in each of the split stacks.
-
The Stack Master notifies the system administrator of the removed units and ports
that belong to the unreachable units by sending SYSLOG messages and SNMP
traps. They are reported as “not present.”