Filter
Top Products
DGS-3100 Series Gigabit Stackable Managed Switch User Manual
– If the Stack Master remains in this sub-group, the behavior is the same as described above. If the Backup
Master remains in this sub group the behavior is the same as described in
0 - Replacing a Failed Stack Master .
NOTE: If a stack is divided into two parts with one section which containing the Stack Master, and the
other section - Backup Master was operate.
The following occurs if either the Stack Master or the Backup Master remains in the divided group:
• TThe Master Discovery, Master Election and Unit ID Allocation & Duplicate Unit ID Conflict Resolution processes are
performed, resulting in the following:
– When the stack is divided and if the Stack Master remains in the split stack, the Stack Master recognizes that
the stacking units were no longer responds. This occurs using the Master Detection Process. The Stack Master
notifies the system administrator using SYSLOG messages and SNMP traps of the removed stacking members.
In addition the Stack Master also notifies the system administrator whichd ports belong to unreachable
stacking members and are reported as Not Present.
– if the Backup Master remains in the split stack, when the stack is divided, the Backup Master identifies this as
of the Stack Master failing. The Backup Master takes over and manages the remaining stacking members as a
stack. The Backup Master retains the same Unit ID as before the stack was divided. Since the Backup Master
was not acting as the Stack Master prior to the split, the Back Master initiates a Topology Database and port
learning process. Traffic can be halted for a short period until the stack is synchronized, i.e., stacking member
and port configuraiton is completed. New stacking members are learnt by the Backup Master are notified to
the system administrator using SYSLOG messages and SNMP traps.
– The divided stack continues to operate normally, the only difference is there are less stacking members than
prior to the stack division.No Unit ID changes are performed in each the divided stacks.
– Even if each stacking section has a Stack Master, one section retains the Stack Master and the other section the
Backup Master, both stacks have the same configuration and the same IP address.
NOTE
: If both stacks have the same IP Address, this can lead to network problem. There is
no way for users to connect to any stacks through the stack IP address
If neither the Stack Master nor the Backup Master remain in the divided group.
• This is identical to failed Stack Master, where no backup is available.
• Stacking members whose Unit IDs are 3, 4, 5 or 6 in original stack do not renumber themselves. The stacking
members’ network ports remains shut down until a Stack Master is enabled, is connected and is operating as the
Stack Master .The Master-Discovery process recognized that the Stack Master has been separated from the stack.
• The stacking members lose connection with the Stack Master. Since the stacking members started as a running
stack, and the stacking members are not in the Factory Default Mode, the stacking members are not reassigned Unit
IDs. Resetting the stacking members will initiate Unit ID auto-assignment. No Unit ID changes are performed in
each one of the two stacking sections of the original stacks.
NOTE: None of the stacking members in either stacking sections can remember themselves.
23