<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Server NIC Aggregation to a Cisco Switch</title>
	<atom:link href="http://aconaway.com/2009/04/14/server-nic-aggregation-to-a-cisco-switch/feed/" rel="self" type="application/rss+xml" />
	<link>http://aconaway.com/2009/04/14/server-nic-aggregation-to-a-cisco-switch/</link>
	<description>It&#039;s possible that someone somewhere needs to see this.</description>
	<lastBuildDate>Fri, 10 Feb 2012 15:03:12 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Aaron Conaway</title>
		<link>http://aconaway.com/2009/04/14/server-nic-aggregation-to-a-cisco-switch/comment-page-1/#comment-19315</link>
		<dc:creator>Aaron Conaway</dc:creator>
		<pubDate>Fri, 17 Jul 2009 22:44:14 +0000</pubDate>
		<guid isPermaLink="false">http://aconaway.com/?p=305#comment-19315</guid>
		<description>The bonded interfaces on the server shouldn&#039;t switch traffic, so there&#039;s no danger of creating a switching loop.  I wouldn&#039;t expect any problems having multiple bonded pairs from the server to two different switches that are EtherChannelled together.

I hope that works for you.  Let me know the result.</description>
		<content:encoded><![CDATA[<p>The bonded interfaces on the server shouldn&#8217;t switch traffic, so there&#8217;s no danger of creating a switching loop.  I wouldn&#8217;t expect any problems having multiple bonded pairs from the server to two different switches that are EtherChannelled together.</p>
<p>I hope that works for you.  Let me know the result.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kolars</title>
		<link>http://aconaway.com/2009/04/14/server-nic-aggregation-to-a-cisco-switch/comment-page-1/#comment-19312</link>
		<dc:creator>Kolars</dc:creator>
		<pubDate>Fri, 17 Jul 2009 20:11:55 +0000</pubDate>
		<guid isPermaLink="false">http://aconaway.com/?p=305#comment-19312</guid>
		<description>Good, I&#039;m glad you suggested the 2nd option.  My thought was to attempt the &quot;2 pairs - one to each switch&quot; solution but since the switches have an etherchannel between them I was curious how that would work since that would basically create a loop.  My instinct would tell me that spanning tree would block one logical pair to break the loop but I&#039;m not entirely sure if it works the same with all the bonding and channeling that would be happening.  Any further thoughts?</description>
		<content:encoded><![CDATA[<p>Good, I&#8217;m glad you suggested the 2nd option.  My thought was to attempt the &#8220;2 pairs &#8211; one to each switch&#8221; solution but since the switches have an etherchannel between them I was curious how that would work since that would basically create a loop.  My instinct would tell me that spanning tree would block one logical pair to break the loop but I&#8217;m not entirely sure if it works the same with all the bonding and channeling that would be happening.  Any further thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Conaway</title>
		<link>http://aconaway.com/2009/04/14/server-nic-aggregation-to-a-cisco-switch/comment-page-1/#comment-19307</link>
		<dc:creator>Aaron Conaway</dc:creator>
		<pubDate>Fri, 17 Jul 2009 16:58:58 +0000</pubDate>
		<guid isPermaLink="false">http://aconaway.com/?p=305#comment-19307</guid>
		<description>Thanks for the question, Kolars.

I&#039;m not sure what the best practice for 4 NICs in an ESX server is, so let&#039;s simplify it for me.  Let&#039;s say you have 2 NICs in the ESX server doing VLAN tagging.  You would cable these to two different modules of the 4500 (or the same if you&#039;re adventurous) and configure those ports as an EtherChannel like in the example above.  The difference is that you would configure the Port-Channel as a trunk the same way you do between your 4500s.

&lt;blockquote&gt;&lt;pre&gt;int Port-channel 1
 speed 100
 duplex full
 switchport
 switchport trunk encapsulation dot1q
 switchport mode trunk&lt;/pre&gt;&lt;/blockquote&gt;

Since the 4500s don&#039;t support StackWise, you can&#039;t put all the NICs across both switches and have them in the same channel-group.  Can you bond two pairs of NICs into two separate logical interfaces to use?  If so, you could have a pair into one 4500 on a channel-group and the other pair on the other 4500 in another channel-group.</description>
		<content:encoded><![CDATA[<p>Thanks for the question, Kolars.</p>
<p>I&#8217;m not sure what the best practice for 4 NICs in an ESX server is, so let&#8217;s simplify it for me.  Let&#8217;s say you have 2 NICs in the ESX server doing VLAN tagging.  You would cable these to two different modules of the 4500 (or the same if you&#8217;re adventurous) and configure those ports as an EtherChannel like in the example above.  The difference is that you would configure the Port-Channel as a trunk the same way you do between your 4500s.</p>
<blockquote><pre>int Port-channel 1
 speed 100
 duplex full
 switchport
 switchport trunk encapsulation dot1q
 switchport mode trunk</pre>
</blockquote>
<p>Since the 4500s don&#8217;t support StackWise, you can&#8217;t put all the NICs across both switches and have them in the same channel-group.  Can you bond two pairs of NICs into two separate logical interfaces to use?  If so, you could have a pair into one 4500 on a channel-group and the other pair on the other 4500 in another channel-group.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kolars</title>
		<link>http://aconaway.com/2009/04/14/server-nic-aggregation-to-a-cisco-switch/comment-page-1/#comment-19305</link>
		<dc:creator>Kolars</dc:creator>
		<pubDate>Fri, 17 Jul 2009 16:29:32 +0000</pubDate>
		<guid isPermaLink="false">http://aconaway.com/?p=305#comment-19305</guid>
		<description>What if you have a need to trunk multiple VLANs to an ESX server in the following environment?  We recently had a supervisor die in one switch and didn&#039;t have NIC&#039;s connected to the other switch.

- Have 2 4500&#039;s etherchanneled together.
- Have 3 line cards in each switch
- Switches are running GLBP
- 4 NIC&#039;s in each ESX servers.

How do I use multiple NICs to truck multiple VLAN to servers from each switch?  Will spanning tree play a role in this?</description>
		<content:encoded><![CDATA[<p>What if you have a need to trunk multiple VLANs to an ESX server in the following environment?  We recently had a supervisor die in one switch and didn&#8217;t have NIC&#8217;s connected to the other switch.</p>
<p>- Have 2 4500&#8242;s etherchanneled together.<br />
- Have 3 line cards in each switch<br />
- Switches are running GLBP<br />
- 4 NIC&#8217;s in each ESX servers.</p>
<p>How do I use multiple NICs to truck multiple VLAN to servers from each switch?  Will spanning tree play a role in this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DoDzMaNo</title>
		<link>http://aconaway.com/2009/04/14/server-nic-aggregation-to-a-cisco-switch/comment-page-1/#comment-16815</link>
		<dc:creator>DoDzMaNo</dc:creator>
		<pubDate>Mon, 11 May 2009 06:58:18 +0000</pubDate>
		<guid isPermaLink="false">http://aconaway.com/?p=305#comment-16815</guid>
		<description>thanks, Aaron..</description>
		<content:encoded><![CDATA[<p>thanks, Aaron..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Conaway</title>
		<link>http://aconaway.com/2009/04/14/server-nic-aggregation-to-a-cisco-switch/comment-page-1/#comment-15441</link>
		<dc:creator>Aaron Conaway</dc:creator>
		<pubDate>Wed, 15 Apr 2009 13:44:18 +0000</pubDate>
		<guid isPermaLink="false">http://aconaway.com/?p=305#comment-15441</guid>
		<description>Good question.  Mode 1, which is active-backup, has a primary NIC running as normal, and, in case of link failure, the backup NIC takes over.  From the switch&#039;s perspective, it just looks like the server was recabled to another port.  No additional switch configuration is required; just make sure both ports are in the same VLAN.</description>
		<content:encoded><![CDATA[<p>Good question.  Mode 1, which is active-backup, has a primary NIC running as normal, and, in case of link failure, the backup NIC takes over.  From the switch&#8217;s perspective, it just looks like the server was recabled to another port.  No additional switch configuration is required; just make sure both ports are in the same VLAN.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: welbow</title>
		<link>http://aconaway.com/2009/04/14/server-nic-aggregation-to-a-cisco-switch/comment-page-1/#comment-15400</link>
		<dc:creator>welbow</dc:creator>
		<pubDate>Wed, 15 Apr 2009 01:41:24 +0000</pubDate>
		<guid isPermaLink="false">http://aconaway.com/?p=305#comment-15400</guid>
		<description>So is this required if the server&#039;s NICs are in active-passive mode where only one NIC is active at a time?</description>
		<content:encoded><![CDATA[<p>So is this required if the server&#8217;s NICs are in active-passive mode where only one NIC is active at a time?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

