Table 7-3. Stacking Configuration Guide
Automatically add Candidate to Stack
(Causes the first 15 eligible, discovered
switches in the subnet to automatically join
Manually add Candidate to Stack
(Prevent automatic joining of switches you
don't want in the stack)
Prevent a switch from being a Candidate
The Commander's Manager and Operator passwords propagate to the candidate when it joins the stack.
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.
(IP Addressing Required)
The easiest way to automatically create a stack is to:
Configure a switch as a Commander.
Configure IP addressing and a stack name on the Commander.
Set the Commander's Auto Grab parameter to Yes.
Connect Candidate switches (in their factory default configuration) to
This approach automatically creates a stack of up to 16 switches (including
the Commander). However this replaces manual control with an automatic
process that may bring switches into the stack that you did not intend to
include. With the Commander's Auto Grab parameter set to Yes, any switch
conforming to all four of the following factors automatically becomes a stack
ProCurve Stack Management
Configuring Stack Management
(IP Addressing Optional)
Yes (default) or No