HP 2500 manual IP Addr Optional, Stack Name N/A

Configuring Advanced Features

Configuring Advanced Features

HP ProCurve Stack Management

	IP Addressing and	Number Allowed	Passwords	SNMP Communities
	Stack Name	Per Stack
Candidate	IP Addr: Optional.	n/a	Passwords optional. If the	Uses standard SNMP
	Configuring an IP		Candidate becomes a stack	community operation if the
	address allows access		Member, it assumes the	Candidate has its own IP
	via Telnet or web		Commander’s Manager and	addressing.
	browser interface		Operator passwords.
	while the switch is not
	a stack member. In the		If a candidate has a password,
	factory default configu-
			it cannot be automatically
	ration the switch auto-
			added to a stack. In this case,
	matically acquires an
			if you want the Candidate in a
	IP address if your
			stack, you must manually add
	networkincludesDHCP
			it to the stack.
	service.
	Stack Name: N/A
Member	IP Addr: Optional.	Up to 15 Members	When the switch joins the	Belongs to the same SNMP
	Configuring an IP	per stack.	stack, it automatically	communities as the
	address allows access		assumes the Commander’s	Commander (which serves
	via Telnet or web		Manager and Operator pass-	as an SNMP proxy to the
	browser interface		words and discards any pass-	Member for communities to
	without going through		words it may have had while a	which the Commander
	the Commander switch.		Candidate.	belongs). To join other
	This is useful, for			communities that exclude
	example, if the stack		Note: If a Member leaves a	the Commander, the
	Commander fails and			Member must have its own
			stack for any reason, it retains
	you need to convert a			IP address. Loss of stack
			the passwords assigned to the
	Member switch to			membership means loss of
			stack Commander at the time
	operate as a replace-			membership in any commu-
			of departure from the stack.
	ment Commander.			nity that is configured only
	Stack Name: N/A			in the Commander. See
				"SNMP Community Opera-
				tion in a Stack" on page 9-46.

N o t e	In the default stack configuration, the Candidate Auto Join parameter is
	enabled, but the Commander Auto Grab parameter is disabled. This prevents
	Candidates from automatically joining a stack prematurely or joining the
	wrong stack (if more than one stack Commander is configured in a subnet or
	broadcast domain). If you plan to install more than one stack in a subnet, HP
	recommends that you leave Auto Grab disabled on all Commander switches and
	manually add Members to their stacks. Similarly, if you plan to install a stack
	in a subnet (broadcast domain) where stacking-capable switches are not
	intended for stack membership, you should set the Stack State parameter (in
	the Stack Configuration screen) to Disabled on those particular switches.

9-10