Netgear M4300-28G (GSM4328S) - Stackable Managed Switch with 24x1G and 4x10G including 2x10GBASE-T and 2xSFP+ Layer 3 管理者ガイド
Switch Stacks
447
Managed Switches
Verify, by monitoring the master switch console port, that the new switch successfully
joins the stack by issuing the show switch command. The new switch must join as a
member (not as master; the existing master of the stack must not change).
joins the stack by issuing the show switch command. The new switch must join as a
member (not as master; the existing master of the stack must not change).
8.
If the firmware version of the newly added member is not the same as the existing stack,
update the firmware (see
update the firmware (see
Switch Stack Configuration Files
The configuration files include all global and interface-specific settings that define the
operation of the stack and its individual members. If you issue the save config command,
all stack members store a copy of the configuration settings. If a stack master becomes
unavailable, the stack member that assumes the role of stack master operates from the
saved configuration files.
operation of the stack and its individual members. If you issue the save config command,
all stack members store a copy of the configuration settings. If a stack master becomes
unavailable, the stack member that assumes the role of stack master operates from the
saved configuration files.
When a new, out-of-box switch joins a switch stack, the switch uses the system-level settings
of that switch stack. However, if you want the store to store this system level configuration,
you must issue the save config command.
of that switch stack. However, if you want the store to store this system level configuration,
you must issue the save config command.
You can back up and restore the stack configuration by using the copy command in the
same way as you back up and restore a standalone switch configuration.
same way as you back up and restore a standalone switch configuration.
The following table provides switch stack configuration scenarios. Most of the scenarios
assume that at least two switches are connected through their stack ports.
assume that at least two switches are connected through their stack ports.
Table 2. Switch stack master scenarios
Scenario
Action
Result
Stack master election specifically
determined by existing stack
masters.
determined by existing stack
masters.
Note:
NETGEAR does not
recommend this scenario.
Connect two powered-on switch stacks
through the stack ports.
through the stack ports.
Only one of the stack masters
becomes the new stack master.
No other stack members
become the stack master.
becomes the new stack master.
No other stack members
become the stack master.
Stack master election specifically
determined by the stack member
priority value.
determined by the stack member
priority value.
•
Connect two switches through their
stack ports.
stack ports.
•
To set a stack member to a higher
member priority value, issue the
switch stack-member-number
member priority value, issue the
switch stack-member-number
priority new-priority-number
global configuration command.
•
Restart both stack members at the
same time.
same time.
The stack member with the
higher-priority value is elected
stack master.
higher-priority value is elected
stack master.
Stack master election specifically
determined by the MAC address.
determined by the MAC address.
Assuming that both stack members have
the same priority value and firmware
image, restart both stack members at the
same time.
image, restart both stack members at the
same time.
The stack member with the
higher MAC address is elected
stack master.
higher MAC address is elected
stack master.