<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Sample HP Procurve Configuration</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/techstop/sample-hp-procurve-configuration/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/techstop/sample-hp-procurve-configuration/</link>
	<description></description>
	<pubDate>Sun, 08 Nov 2009 14:49:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Arr2036</title>
		<link>http://itknowledgeexchange.techtarget.com/techstop/sample-hp-procurve-configuration/#comment-3</link>
		<dc:creator>Arr2036</dc:creator>
		<pubDate>Mon, 28 Jul 2008 22:35:31 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/techstop/sample-hp-procurve-configuration/#comment-3</guid>
		<description>Don't force STP-Compatible spanning tree, the switch will automatically adjust spanning tree behaviour on ports that recieve legacy STP BPDUs, it's in the RSTP spec. Besides all managed ProCurve switches since the 2500 series support RSTP (Rapid Spanning Tree Protocol), which is much better to use. STP can have a delay of up to 30 seconds between a device being connected, and the port transitioning to a forwarding state, by which time most windows DHCP clients will have timed out.

As you appear to be configuring a 2610 in your example, just issuing the spanning-tree command will be sufficient, this should enable MSTP. Ports on which RSTP and STP BPDUs are detected will be added into a single default MST instance on the switch, thus allowing backwards compatiblity with 802.1D spanning stree protocols.

According to posts on the HP forums, memory is 'hard' allocated for VLANs depending on the max-vlan parameter. So I wouldn't set it to 256, but something more modest. If you're running GVRP i'd set it to the maximum number of VLANs on your network, plus 20 to allow for expansion (rebooting the switch every time you alter max-vlans gets to be annoying).

Additionally it's worth enabling SSH and disabling telnet.
crypto key generate ssh
ip ssh
no telnet-server

And disabling the plaintext http server
no web-management plaintext
web-management ssl</description>
		<content:encoded><![CDATA[<p>Don&#8217;t force STP-Compatible spanning tree, the switch will automatically adjust spanning tree behaviour on ports that recieve legacy STP BPDUs, it&#8217;s in the RSTP spec. Besides all managed ProCurve switches since the 2500 series support RSTP (Rapid Spanning Tree Protocol), which is much better to use. STP can have a delay of up to 30 seconds between a device being connected, and the port transitioning to a forwarding state, by which time most windows DHCP clients will have timed out.</p>
<p>As you appear to be configuring a 2610 in your example, just issuing the spanning-tree command will be sufficient, this should enable MSTP. Ports on which RSTP and STP BPDUs are detected will be added into a single default MST instance on the switch, thus allowing backwards compatiblity with 802.1D spanning stree protocols.</p>
<p>According to posts on the HP forums, memory is &#8216;hard&#8217; allocated for VLANs depending on the max-vlan parameter. So I wouldn&#8217;t set it to 256, but something more modest. If you&#8217;re running GVRP i&#8217;d set it to the maximum number of VLANs on your network, plus 20 to allow for expansion (rebooting the switch every time you alter max-vlans gets to be annoying).</p>
<p>Additionally it&#8217;s worth enabling SSH and disabling telnet.<br />
crypto key generate ssh<br />
ip ssh<br />
no telnet-server</p>
<p>And disabling the plaintext http server<br />
no web-management plaintext<br />
web-management ssl</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->