1. Home
    2. /
  2. Manuals
    3. /
  3. NETGEAR
    4. /
  4. FSM7328S
    5. /
  5. 66
Page 326 / 400 Scroll up to view Page 321 - 325
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
12-14
Managing Switch Stacks
202-10088-01, March 2005
Moving a Master to a Different Unit in the Stack
1.
Using the “movemanagement” command, move the master to the desired unit number. The
operation may take between 30 seconds and 3 minutes depending on the stack size and
configuration. The command is
movemanagement
<fromunit-id> <tounit-id>
2.
Make sure that you can log in on the console attached to the new master. Use the
show
switch
command to verify that all units rejoined the stack.
3.
It is recommended that the stack be reset with the
reload
command after moving the master.
Removing a Master Unit from an Operating Stack
1.
First, move the designated master to a different unit in the stack using
“Moving a Master to a
Different Unit in the Stack” on page 12-14
.
2.
Second, using
“Removing a Unit from the Stack” on page 12-12
, remove the unit from the
stack.
Merging Two Operational Stacks
1.
It is strongly recommended that two functioning stacks (each having an independent master)
not be merged simply by the reconnection of stack cables. That process may result in a number
of unpredictable results and should be avoided.
2.
Always power off all units in one stack before connecting into another stack.
3.
Add the units as a group by unplugging one stacking cable in the operational stack and
physically connecting all unpowered units at that point.
4.
Completely cable the stacking connections, making sure the redundant link is also in place.
5.
Then, power up each unit, one at a time, by following
“Adding a Unit to an Operating Stack”
on page 12-12
.
Page 327 / 400
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
Managing Switch Stacks
12-15
202-10088-01, March 2005
Preconfiguration
1.
General Information: All configuration on the stack except unit numbers is stored on the
management unit. This means that a stack unit may be replaced with another device of the
same type without having to reconfigure the switch. Unit numbers are stored independently on
each switch, so that after power cycling the stack the units always come back with the same
unit numbers. The unit type associated with each unit number may be learned by the
management unit automatically as the units are connected or preconfigured by the
administrator.
2.
Issue the
member
<unit-id> <switchindex> command to preconfigure a unit. Supported unit
types are shown by the
show supported switchtype
command.
3.
Next, configure the unit you just defined with configuration commands, just as if the unit were
physically present.
4.
Ports for the preconfigured unit come up in “detached” state and can be seen with the
show
port all
command. The detached ports may now be configured for VLAN membership and
any other port-specific configuration.
5.
After a unit type is preconfigured for a specific unit number, attaching a unit with different unit
type for this unit number causes the switch to report an error. The
show switch
command
indicates “config mismatch” for the new unit and the ports on that unit don’t come up. To
resolve this situation the customer may change the unit number of the mismatched unit or
delete the preconfigured unit type using the
no member
<unit-id> command.
Upgrading Firmware
1.
New code is downloaded via TFTP or xmodem to the management unit using the
copy
command. Once code is successfully loaded on the management unit, it automatically
propagates the code to the other units in the stack. If some error occurs during code
propagation to stack units then the
archive
command (in stack configuration mode) may be
issued to make another attempt to copy the software to the unit(s) that did not get updated.
Errors during code propagation to stack members could be caused by stack cable movement or
unit reconfiguration during the propagation phase. An error could also occur in the presence of
excessive network traffic (such as a broadcast event).
Page 328 / 400
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
12-16
Managing Switch Stacks
202-10088-01, March 2005
2.
All units in the stack must run the same code version. Ports on stack units that don’t match the
management unit code version don’t come up and
the show switch
command shows a “code
mismatch” error. To resolve this situation the administrator may issue
archive
command. This
command copies management unit’s software to the other units with mismatched code version.
Before issuing this command, be sure the code running on the management unit is the desired
code revision for all units in the stack. Once code is loaded to all members of the stack, the
units must be reset in order for the new code to start running.
Migration of Configuration With a Firmware Upgrade
In some cases, a configuration may not be carried forward in a code update. For updates where this
issue is to be expected, the following procedure should be followed:
1.
Save the current configuration by uploading it from the stack, using the copy command from
the CLI.
2.
Load new code into the stack manager. Reboot the stack.
3.
Upon reboot, go into the boot menu and erase the configuration (“restore to factory defaults”)
4.
Continue with boot of operational code.
5.
Once the stack is up, download the saved configuration back to the master. This configuration
should then be automatically propagated to all members of the stack
Code Mismatch
If a unit is added to a stack and it does not have the same version of code as that of the master, the
following should happen:
•
“New” unit will boot up and become a “member” of the stack
•
Ports on the added unit should remain in the “detached” state
•
A message should appear on the CLI indicating a code mismatch with the newly added unit.
•
To have the newly added unit to merge normally with the stack, code should be loaded to the
newly added unit from the master using the copy command. The newly added member should
then be reset, and should reboot normally and join the stack.
Page 329 / 400
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
IS CLI Mapping
A-1
202-10088-01, March 2005
Appendix A
IS CLI Mapping
This chapter illustrates the mapping between CLI commands and the previous 7300S Series L3
Switch commands. The Package column indicates the 7300S Series L3 Switch package in which
the command is located.
Table 12-3.
IS CLI Mapping
Package
7300S Series L3 Switch
Command
CLI Command
Mode
Syntax
QOS
show acl detailed <aclid>
Privileged
EXEC
show ip access-lists [<1-199>]
QOS
show acl summary
Privileged
EXEC and
User
EXEC
QOS
config acl create <aclid>
Global
Config
access-list {(<1-99> {deny | permit}
<srcip> <srcmask>) | ( {<100-199>
{deny | permit} {every | {{icmp | igmp |
ip | tcp | udp | <number>} <srcip>
<srcmask> [{eq {<0-65535> |
<portkey>} | range <startport>
<endport>}] <dstip> <dstmask> [{eq
{<0-65535> | <portkey>} | range
<startport> <endport>}] {[precedence
<precedence>] | [tos <tos>
<tosmask>] | [dscp <dscp>]}}}})}
QOS
config acl delete <aclid>
Global
Config
no access-list {<1-99> | <100-199>}
QOS
config acl rule create <aclid>
<rulenum>
QOS
config acl rule delete <aclid>
<rulenum>
Page 330 / 400
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
A-2
IS CLI Mapping
202-10088-01, March 2005
QOS
config acl rule action <aclid>
<rulenum> <permit/deny>
QOS
config acl rule match dstip <aclid>
<rulenum> <ipaddr> <ipmask>
QOS
config acl rule match dstl4port
keyword <aclid> <rulenum>
<portkey>
QOS
config acl rule match dstl4port
range <aclid> <rulenum>
<startport> <endport>
QOS
config acl rule match every <aclid>
<rulenum> <true/false>
QOS
config acl rule match ipdscp
<aclid> <rulenum> <dscpval>
QOS
config acl rule match ipprecedence
<aclid> <rulenum>
<precedenceval>
QOS
config acl rule match iptos <aclid>
<rulenum> <tosbits> <tosmask>
QOS
config acl rule match protocol
keyword <aclid> <rulenum>
<protocolkey>
QOS
config acl rule match protocol
number <aclid> <rulenum>
<protocolnum>
QOS
config acl rule match srcip <aclid>
<rulenum> <ipaddr> <ipmask>
QOS
config acl rule match srcl4port
keyword <aclid> <rulenum>
<portkey>
Table 12-3.
IS CLI Mapping
(continued)
Package
7300S Series L3 Switch
Command
CLI Command
Mode
Syntax

Rate

4.5 / 5 based on 2 votes.

Popular NETGEAR Models

Famous Router IPs
Famous Router Companies
Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top