HP 2610, Руководство по продвинутому управлению трафиком

Страница: 316 / 364

ProCurve Stack Management
Configuring Stack Management
Configuring Stack Management
Overview of Configuring and Bringing Up a Stack
This process assumes that:
■
All switches you want to include in a stack are connected to the same
subnet (broadcast domain).
■ If VLANs are enabled on the switches you want to include in the stack,
then the ports linking the stacked switches must be on the primary
VLAN in each switch (which, in the default configuration, is the
default VLAN). If the primary VLAN is tagged, then each switch in the
stack must use the same VLAN ID (VID) for the primary VLAN. (Refer
to “The Primary VLAN” on page 2-7, and “Stacking Operation with
Multiple VLANs Configured” on page 8-45.)
■ If you are including an ProCurve Switch 8000M, 4000M, 2424M,
2400M, or 1600M in a stack, you must first update all such devices
to software version C.08.03 or later
. (You can get a copy of the latest
software version from the ProCurve Networking website and/or copy
it from one switch to another. For downloading instructions, see
appendix A, “File Transfers”, in the
Management and Configuration
Guide for these switch models.)
Options for Configuring a Commander and Candidates. Depending on
how Commander and Candidate switches are configured, Candidates can join
a stack either automatically or by a Commander manually adding (“pulling”)
them into the stack. In the default configuration, a Candidate joins only when
manually pulled by a Commander. You can reconfigure a Commander to
automatically pull in Candidates that are in the default stacking configura­
tion. You can also reconfigure a Candidate switch to either “push” itself into
a particular Commander’s stack, convert the Candidate to a Commander (for
a stack that does not already have a Commander), or to operate as a standa­
lone switch without stacking. The following table shows your control options
for adding Members to a stack.
8-10