<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Procurve on sigtar.com</title>
		<link>https://sigtar.com/tags/procurve/</link>
		<description>Recent content in Procurve on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Mon, 02 May 2011 00:00:00 +1200</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/procurve/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>HP ProCurve 5400zl Switch Series - How to Enable Jumbo Frames?</title>
				<link>https://sigtar.com/2011/05/02/hp-procurve-5400zl-switch-series-how-to-enable-jumbo-frames/</link>
				<pubDate>Mon, 02 May 2011 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2011/05/02/hp-procurve-5400zl-switch-series-how-to-enable-jumbo-frames/</guid>
				<description>&lt;p&gt;I couldn&amp;rsquo;t find how to do this via the web GUI (hate the new 5400 web console - what happened to the performance graphs??) &amp;ndash; anyhow this is the commands to do it via commandline&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;5406zl-A# show vlan 200&lt;/strong&gt; Status and Counters - VLAN Information - Ports - VLAN 200   VLAN ID : 200  Name : VLAN200   Status : Port-based   Voice : No   Jumbo : No&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;5406zl-A# configure 5406zl-A(config)# vlan 200 jumbo 5406zl-A(config)# end 5406zl-A# sho vlan 200&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>vmware - hp procurve lacp / trunk</title>
				<link>https://sigtar.com/2010/09/21/vmware-hp-procurve-lacp-trunk/</link>
				<pubDate>Tue, 21 Sep 2010 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2010/09/21/vmware-hp-procurve-lacp-trunk/</guid>
				<description>&lt;p&gt;Cisco&amp;rsquo;s Etherchannel and HP&amp;rsquo;s LACP are very similar – probably why I assumed both are supported by vmware. But as per below – it is not the case.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1004048&#34;&gt;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1004048&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;From a procurve perspective the differences between a “trunk” and “static lacp” trunk is the total bandwidth &lt;strong&gt;per connection&lt;/strong&gt;. A typical end point on a “trunk” trunk can transmit various connections down both pipes, but only receive down one – sometimes refered to as TLB (transmit load balancing). In vmwares case when you are using a &amp;ldquo;trunk&amp;rdquo; trunk you will have ip hash set as a load balancer, effectively meaning a different nic will be used on the vmware side for each connection a virtual machine makes.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
