Digisol DG-GS4826S, Руководство по управлению

Страница: 78 / 1344

C
HAPTER
2 | Initial Switch Configuration
Stack Operations
– 78 –
R
ESILIENT
IP I
NTERFACE FOR
M
ANAGEMENT
A
CCESS
The stack functions as one integral system for management and
configuration purposes. You can therefore manage the stack through any
IP interface configured on the stack. The Master unit does not even have to
include an active port member in the VLAN interface used for management
access. However, if the unit to which you normally connect for
management access fails, and there are no active port members on the
other units within this VLAN interface, then this IP address will no longer be
available. To retain a constant IP address for management access across
fail over events, you should include port members on several units within
the primary VLAN used for stack management.
R
ESILIENT
C
ONFIGURATION
If a unit in the stack fails, the unit numbers will not change. This means
that when you replace a unit in the stack, the original configuration for the
failed unit will be restored to the replacement unit. This applies to both the
Master and Slave units.
R
ENUMBERING THE
S
TACK
The startup configuration file maps configuration settings to each switch in
the stack based on the unit identification number. If the units are no longer
numbered sequentially after several topology changes or failures, you can
reset the unit numbers using the “Renumbering” command in the web
interface or CLI. Just remember to save the new configuration settings to a
startup configuration file prior to powering off the stack Master.
E
NSURING
C
ONSISTENT
C
ODE IS
U
SED
A
CROSS THE
S
TACK
Consistent Runtime Code in Each Switch – The main board runtime
firmware version for each unit in the stack must be the same as the Master
unit’s runtime firmware. After Auto-ID assignment is completed, the
Master unit checks the image versions for consistency. If the firmware
versions (i.e., runtime code) configured for bootup on any slave units are
not the same as those on the Master Unit, the stack will operate in Special
Stacking Mode in which all backup units are disabled as described below:
u
The master unit starts normal operation mode in standalone mode.
u
The master unit can see all units in the stack and maintain stack
topology.
u
None of the other units can function (all ports will be disabled).
u
All user-initiated commands to configure the non-functioning units are
dropped. The master unit, however, will be able to communicate the
following information to the non-functioning units:
n
Image downloads
n
Stack topology information
n
System configuration information already stored on the master.