

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Bienvenido a la WEB</title>
	<atom:link href="http://www.robertomm.com/wordpress/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.robertomm.com/wordpress</link>
	<description>WEB personal de Roberto Martínez Martín</description>
	<lastBuildDate>Tue, 01 May 2012 22:58:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>VMM 2008 R2 SP1: Error 3140 when trying to offline P2V WS2008R2</title>
		<link>http://www.robertomm.com/wordpress/english-vmm-2008-r2-sp1-error-3140-when-trying-to-offline-p2v-ws2008r2/?lang=en</link>
		<comments>http://www.robertomm.com/wordpress/english-vmm-2008-r2-sp1-error-3140-when-trying-to-offline-p2v-ws2008r2/?lang=en#comments</comments>
		<pubDate>Sat, 28 Apr 2012 14:02:42 +0000</pubDate>
		<dc:creator>MasterAdminROBIT</dc:creator>
				<category><![CDATA[Hyper-V Server]]></category>
		<category><![CDATA[Windows Server 2008]]></category>
		<category><![CDATA[3140 error during offline P2V]]></category>
		<category><![CDATA[P2V migration]]></category>

		<guid isPermaLink="false">http://www.robertomm.com/wordpress/?p=43</guid>
		<description><![CDATA[I just want to share some info from our recent P2V migration. We have received 3140 error during offline P2V of Windows Server 2008 R2 (or Windows 7) using Virtual Machine Manager 2008 R2 SP1. The progress bar stuck at 40% (step 1.3.1) with error 3140 without any description in VMM. When googling I&#8217;ve found the following [...]]]></description>
			<content:encoded><![CDATA[<p>I just want to share some info from our recent P2V migration.</p>
<p>We have received <strong>3140 error </strong>during offline P2V of Windows Server 2008 R2 (or Windows 7) using Virtual Machine Manager 2008 R2 SP1.</p>
<p>The progress bar stuck at 40% (step 1.3.1) with error 3140 without any description in VMM. When googling I&#8217;ve found the following link: <a href="http://social.technet.microsoft.com/Forums/en-US/virtualmachinemgrp2vv2v/thread/83cf649a-686a-4ecc-9aa0-bf005c7f9f53">http://social.technet.microsoft.com/Forums/en-US/virtualmachinemgrp2vv2v/thread/83cf649a-686a-4ecc-9aa0-bf005c7f9f53</a> . Per instructions I sent an email to Mike Briggs. However, Mike is no longer with the VMM Team but he go through the debug logs for me and find out that the final failure is &#8220;3140/80990C44&#8243; which translates to NETLOG_MSG_SHUTDOWN.</p>
<p>Finally i give up and ask Microsoft PSS for support, surprisingly the bug is quite simple: The boot image that VMM is using for offline conversion cannot fit into the 100MB default (classic install) system partiton [just a side note: the system partition is used for booting the system = boot sector, bootmgr, while the Boot partition contains Windows files]. In order to fix the issue:</p>
<ol>
<li>Open an elevated command prompt and run : bcdboot c:\windows /s c:</li>
<li>This will copy the required boot files to the C drive. Notice the hidden boot folder on the root of the C drive and also the bootmgr file.</li>
<li>Set the C drive as active : You can do this from disk management or using diskpart</li>
<li>Reboot the server</li>
<li>Open disk management and make sure the C drive is marked as SYSTEM.</li>
<li>Try the P2V process again and this time it should work fine</li>
</ol>
<p>Obtained from this link <a href="http://www.rozmazat.cz/articles/2011/08/22/vmm-2008-r2-sp1-error-3140-when-trying-to-offilne-p2v-ws2008r2.html">http://www.rozmazat.cz/articles/2011/08/22/vmm-2008-r2-sp1-error-3140-when-trying-to-offilne-p2v-ws2008r2.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.robertomm.com/wordpress/english-vmm-2008-r2-sp1-error-3140-when-trying-to-offline-p2v-ws2008r2/?lang=en/feed/&#038;lang=en</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Deshabilitar IPv6 en Windows Server 2008</title>
		<link>http://www.robertomm.com/wordpress/deshabilitar-ipv6-en-windows-server-2008/?lang=en</link>
		<comments>http://www.robertomm.com/wordpress/deshabilitar-ipv6-en-windows-server-2008/?lang=en#comments</comments>
		<pubDate>Sat, 21 Apr 2012 00:11:48 +0000</pubDate>
		<dc:creator>MasterAdminROBIT</dc:creator>
				<category><![CDATA[Hyper-V Server]]></category>
		<category><![CDATA[Windows Server 2008]]></category>
		<category><![CDATA[Windows Server 8]]></category>

		<guid isPermaLink="false">http://www.robertomm.com/wordpress/?p=41</guid>
		<description><![CDATA[IPv6 está habilitado por defecto en Windows Server 2008. Normalmente no es necesario tenerlo activo, en instalación completa (full) es fácil, simplemete se desmarca IPv6 en los adaptadores que tengamos en cada conexión de red, pero en versión core, se nos complica un poco.  Para deshabilitar IPv6 en cualquiera de las versiones lo que tenemos [...]]]></description>
			<content:encoded><![CDATA[<p>IPv6 está habilitado por defecto en Windows Server 2008. Normalmente no es necesario tenerlo activo, en instalación completa (full) es fácil, simplemete se desmarca IPv6 en los adaptadores que tengamos en cada conexión de red, pero en versión core, se nos complica un poco.  Para deshabilitar IPv6 en cualquiera de las versiones lo que tenemos que realizar es un pequeño cambio en el registro de windows a tráves de la herramienta regedit:</p>
<p>Necesitamos crear un nuevo valor en la siguiente ruta:</p>
<p><strong>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters</strong></p>
<p>Ejecuta &#8220;regedit&#8221; y busca el registro <strong>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters</strong> ,en la carpeta Parameters creamos una nueva clave de tipo Valor de DWORD de 32 bits, en el panel derecho, click derecho y selecciona New &#8211; DWORD, poner como nombre de atributo <strong>&#8220;DisabledComponents&#8221;</strong>, luego hacemos click derecho del ratón, modificar y le asignamos el valor <strong>&#8220;FF&#8221;</strong>; una vez realizado, reinicia el equipo para que los cambios se hagan efectivos. Si mas adelante requieres habilitarlo tan solo borra la entrada añadida en el registro y reinicia el equipo.</p>
<p>Esto básicamente nos sirve porque la mayoría de nosotros utilizamos tráfico de red IPv4 y el IPv6 lo tenemos activo pero sin ninguna utilidad, también se deshabilita porque a veces suele ocurrir que tenemos es tráfico de la red a través de un Firewall que monitoriza sólo el tráfico que pasa a través del IPv4 dejándo un gran agujero de seguridad en el protocolo IPv6.</p>
<p>Tambien es valido, y más comodo, &#8220;ejecutar como administrador&#8221; el siguiente comando:</p>
<p>reg add hklm\system\currentcontrolset\services\tcpip6\parameters /v DisabledComponents /t REG_DWORD /d 255</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.robertomm.com/wordpress/deshabilitar-ipv6-en-windows-server-2008/?lang=en/feed/&#038;lang=en</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Configuring Advanced Network Card Settings in Windows Server 2008 Server Core</title>
		<link>http://www.robertomm.com/wordpress/english-configuring-advanced-network-card-settings-in-windows-server-2008-server-core/?lang=en</link>
		<comments>http://www.robertomm.com/wordpress/english-configuring-advanced-network-card-settings-in-windows-server-2008-server-core/?lang=en#comments</comments>
		<pubDate>Fri, 20 Apr 2012 20:54:49 +0000</pubDate>
		<dc:creator>MasterAdminROBIT</dc:creator>
				<category><![CDATA[Hyper-V Server]]></category>
		<category><![CDATA[COMPUTING]]></category>
		<category><![CDATA[Windows Server 2008]]></category>
		<category><![CDATA[Windows Server 8]]></category>
		<category><![CDATA[Jumbo Frames]]></category>
		<category><![CDATA[MTU]]></category>
		<category><![CDATA[Windows Server 2008 Core]]></category>
		<category><![CDATA[Windows Server 8 Core]]></category>

		<guid isPermaLink="false">http://www.robertomm.com/wordpress/?p=38</guid>
		<description><![CDATA[When conducting network troubleshooting exercises on a daily basis, you start to take some of your simpler and more common tools for granted, until you lose them that is.  One of these basic tools for troubleshooting network connectivity issues is the ability to manipulate the advanced parameters on your network card.  I ran into this [...]]]></description>
			<content:encoded><![CDATA[<div class="layout-region-inner content">When conducting network troubleshooting exercises on a daily basis, you start to take some of your simpler and more common tools for granted, until you lose them that is.  One of these basic tools for troubleshooting network connectivity issues is the ability to manipulate the advanced parameters on your network card.  I ran into this issue while trying to hard code the Speed and Duplex settings of a card in a Windows Server 2008 Server Core machine.</p>
<div id="fragment-10140" class="content-fragment blog-post no-wrapper">
<div class="content-fragment-inner fiji-content-fragment-inner">
<div class="content-fragment-content">
<div class="content-fragment-inner fiji-content-fragment-inner">
<div class="post-content user-defined-markup">
<p>I was recently working with a customer on their Server Core system and he wanted to set these parameters since other servers in his network were set similarly.  I understood why he wanted to be able to control these settings on his server.  Also, when facing a network connectivity issue, one of the most basic things that you can rule out is any mismatch in the speed and duplex settings between the network card and the switch by hard coding them both to the same configuration.  On any other Windows server this is accomplished from the properties for the Network Interface Card (NIC) where you can select the Advanced tab. Figure-1 shows an example of how this looks from the GUI:</p>
<p>Figure-1</p>
<p><img style="border-width: 0px; border-style: none; border-color: -moz-use-text-color; display: inline;" title="clip_image001" src="http://blogs.technet.com/blogfiles/networking/WindowsLiveWriter/ConfiguringAdvancedNetworkCardSettingsin_99E5/clip_image001_642e8487-cb7b-4164-955f-45db5bc9e000.gif" alt="clip_image001" width="402" height="444" border="0" /></p>
<p>This Advanced tab contains all of the Parameters that the NIC manufacturer has available for that card via the drivers associated with it.  Now this is all well and good as long as you have a GUI.  But, when that interface is removed as is the case with Server Core, you are left wondering, “What now?”  To date I have not seen any command line tools created by the network card vendors to take the place of the GUI tools that no longer exist in Server Core.</p>
<p>Luckily, as with most things in the O/S, there are registry entries that are associated with these parameters.  In the case of network cards you are going to want to start with this key:</p>
<p>HKLM\System\CurrentControlSet\Control\Class\{4D36E972-E325<br />
-11CE-BFC1-08002bE10318}</p>
<p>In this registry key you will be able to see all of the interfaces that are detected by the O/S.  Now, some of these will be WANminiport adapters, etc, so you will have to find the key associated with the NIC you wish to configure.  In Figure-2 you can see that I was able to recognize the description of the adapter as the NIC I was after:</p>
<p>Figure-2</p>
<p><img style="border-width: 0px; border-style: none; border-color: -moz-use-text-color; display: inline;" title="clip_image002" src="http://blogs.technet.com/blogfiles/networking/WindowsLiveWriter/ConfiguringAdvancedNetworkCardSettingsin_99E5/clip_image002_6fd6c4dc-eb51-435e-9985-c4136332bfc4.jpg" alt="clip_image002" width="567" height="410" border="0" /></p>
<p>Once you have found the adapter of interest in the registry, drill down to the NDI\Params key.  Once there, all of the parameters available on the card should be listed.  You can see from Figure-3 that I chose the SpeedDuplex setting and under the Enum portion you can see the list of possible settings to choose from.  Therefore, if I want to set my NIC to 100Mb/Full duplex I need to use a value of 4.  It is very important to examine each parameter and determine what value you must use to get the expected result.  Each vendor seems to use their own system choosing a value.</p>
<p>Figure-3</p>
<p><img style="border-width: 0px; border-style: none; border-color: -moz-use-text-color; display: inline;" title="clip_image002[5]" src="http://blogs.technet.com/blogfiles/networking/WindowsLiveWriter/ConfiguringAdvancedNetworkCardSettingsin_99E5/clip_image002%5B5%5D_21a65036-0b63-4d6e-a744-3cd122abbf22.jpg" alt="clip_image002[5]" width="563" height="470" border="0" /></p>
<p>Now that I have the value that I need for the SpeedDuplex setting, I navigate back up the tree and enter the value into the configuration for the card.  Figure-4 shows where I would make the change.  In this case I would change the value from 0, as seen in the figure, to a 4:</p>
<p>Figure-4</p>
<p><img style="border-width: 0px; border-style: none; border-color: -moz-use-text-color; display: inline;" title="clip_image002[7]" src="http://blogs.technet.com/blogfiles/networking/WindowsLiveWriter/ConfiguringAdvancedNetworkCardSettingsin_99E5/clip_image002%5B7%5D_5a75956c-329a-4c6a-bb98-d0db7da23134.jpg" alt="clip_image002[7]" width="567" height="397" border="0" /></p>
<p>Now, in my case I wanted to set the SpeedDuplex setting.  This method should also be useful for turning off other features on the NIC such as “Large Send Offload” and “Jumbo Frames”.</p>
<p>I hope this article helps someone with their Windows Server 2008 Server Core configurations, but before you use this please consider all of the usual disclaimers about editing the registry and how badly it can screw up your day if you get things wrong.</p>
<p>Until next time.</p>
<p>- Steve Martin</p>
<p>Obtained from this link <a href="http://blogs.technet.com/b/networking/archive/2009/01/08/configuring-advanced-network-card-settings-in-windows-server-2008-server-core.aspx" target="_blank">http://blogs.technet.com/b/networking/archive/2009/01/08/configuring-advanced-network-card-settings-in-windows-server-2008-server-core.aspx</a></p>
</div>
</div>
</div>
</div>
</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.robertomm.com/wordpress/english-configuring-advanced-network-card-settings-in-windows-server-2008-server-core/?lang=en/feed/&#038;lang=en</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Jumbo Frames/MTU en Hyper-V Server (Windows Server 2008/8 Core)</title>
		<link>http://www.robertomm.com/wordpress/cambiar-jumbo-framesmtu-en-hyper-v-server-windows-server-20088-core/?lang=en</link>
		<comments>http://www.robertomm.com/wordpress/cambiar-jumbo-framesmtu-en-hyper-v-server-windows-server-20088-core/?lang=en#comments</comments>
		<pubDate>Fri, 20 Apr 2012 20:45:17 +0000</pubDate>
		<dc:creator>MasterAdminROBIT</dc:creator>
				<category><![CDATA[Hyper-V Server]]></category>
		<category><![CDATA[COMPUTING]]></category>
		<category><![CDATA[Windows Server 2008]]></category>
		<category><![CDATA[Windows Server 8]]></category>
		<category><![CDATA[Jumbo Frames]]></category>
		<category><![CDATA[MTU]]></category>
		<category><![CDATA[Windows Server 2008 Core]]></category>
		<category><![CDATA[Windows Server 8 Core]]></category>

		<guid isPermaLink="false">http://www.robertomm.com/wordpress/?p=31</guid>
		<description><![CDATA[Enabling Jumbo Frame support in Hyper-V Server 2008 R2 (or Windows Server Core) has proven to be a bit of an adventure.  It really just involves setting the MTU size, but it has to be done in the OS (to affect the TCP/IP stack) as well as the network cards’ driver.  Since Core versions of Windows do [...]]]></description>
			<content:encoded><![CDATA[<p>Enabling Jumbo Frame support in <a title="Microsoft Hyper-V Server" href="http://www.microsoft.com/hyper-v-server/">Hyper-V Server 2008 R2</a> (or Windows Server Core) has proven to be a bit of an adventure.  It really just involves setting the <a href="http://en.wikipedia.org/wiki/Maximum_transmission_unit">MTU size</a>, but it has to be done in the OS (to affect the TCP/IP stack) as well as the network cards’ driver.  Since Core versions of Windows do not have a network control, setting the MTU on the cards proves to be a bit of a trick.  This is what I had to do to enable Jumbo Frames on several iSCSI nics, and since it differs for Intel vs Broadcom adapters, there are two procedures.</p>
<p>I should point out that this does not address configuring the network switch that these nics are attached to.  That is a whole ‘nother can of worms, but suffice it to say that the switch must not only support Jumbo Frames but have that support enabled, along with a whole host of other settings.</p>
<h3>Enable Jumbo Frames on the OS</h3>
<p>The first thing you need to do is make sure that your server will allow jumbo frames.  You do this by setting the MTU on your adapters to 9000.  The easiest way to do this is by running a netsh command on each adapter you want to use Jumbo Frames.</p>
<p>Get a list of interface names by running “<strong><em>netsh int show int</em></strong>”</p>
<div id="highlighter_911689" class="syntaxhighlighter nogutter  ">
<div class="lines no-wrap">
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Admin State    State          Type             Interface Name</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">-------------------------------------------------------------------------</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Enabled        Disconnected   Dedicated        Local Area Connection 2</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2 highlighted">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Enabled        Connected      Dedicated        Bcom-GB3-iSCSI-A</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Enabled        Connected      Dedicated        Local Area Connection</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Enabled        Connected      Dedicated        Local Area Connection 3</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Enabled        Connected      Dedicated        Local Area Connection 4</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2 highlighted">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Enabled        Connected      Dedicated        Bcom-GB4-iSCSI-B</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Enabled        Connected      Dedicated        Intel-GB1-Guest-B</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Enabled        Connected      Dedicated        Bcom-GB2-Guest-A</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Enabled        Connected      Dedicated        Intel-GB2-Guest-C</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Enabled        Connected      Dedicated        Bcom-GB1-Mgmnt</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1 highlighted">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Enabled        Connected      Dedicated        Intel-GB3-iSCSI-C</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2 highlighted">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Enabled        Connected      Dedicated        Intel-GB4-Migration</code></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<p>In this case I have already re-named the Interfaces that I intend to use for iSCSI.  You might just see a whole list of “Local Area Connection” interfaces.  You can use ipconfig or netsh to further identify which ones you want to use.</p>
<p>Now for each interface you want jumbo frames enabled, run this command:</p>
<p style="padding-left: 30px;"><strong><em>netsh int ipv4 set subint “” mtu=9000 store=persistent</em></strong></p>
<p>Now you have to configure Jumbo Frames in the driver for each interface.</p>
<h3>Enable Jumbo Frames on Intel cards</h3>
<p>The Intel driver stores it’s “Jumbo Frame” settings in the registry.  Thankfully, Hyper-V Server (and Windows Core) comes with Regedit, so you can just launch that from command line (<strong><em>regedit.exe</em></strong>) and browse to the following key:</p>
<div id="highlighter_792358" class="syntaxhighlighter nogutter  ">
<div class="lines no-wrap">
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces</code></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<p>Here you will see all the network interfaces listed by GUID.  I have found that the easiest way to determine which GUID is which adapter is by finding the IP address and being able to correlate it to the right Interface name.</p>
<p><a href="http://mrshannon.files.wordpress.com/2010/01/jumboframes-intelregistry-ipaddress.png"><img class="alignnone size-full wp-image-47" title="JumboFrames-IntelRegistry-IPAddress" src="http://mrshannon.files.wordpress.com/2010/01/jumboframes-intelregistry-ipaddress.png?w=600" alt="" /></a></p>
<p>At this point you should start making a list to help keep things straight.  Copy the GUID into notepad and list the IP address next to it and do this for each card you want to configure.  So for this server, my list looks like this:</p>
<div id="highlighter_778262" class="syntaxhighlighter nogutter  ">
<div class="lines no-wrap">
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">SERVERNAME {7A310D71-217C-4E4A-9DA7-43299A76CBD5} 172.16.0.9</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">SERVERNAME {7BC7F3B9-B245-4579-82CB-C94161BFDBC1} 172.16.0.7</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">SERVERNAME {8BA5076E-0FC3-4D20-9609-654F228EE6BD} 172.16.0.6</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">SERVERNAME {98ABBECA-B8A2-41D2-9550-8B571E50F49A} 172.16.0.8</code></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<p>Now we have to navigate to a new registry key to configure the driver.  Go here:</p>
<div id="highlighter_590403" class="syntaxhighlighter nogutter  ">
<div class="lines no-wrap">
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}</code></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<p>Here you will again see a list of all network interfaces, only this time they are under 4 digit identifiers.  From here, search for the GUID that you copied to your list and you should find it as the “NetCfgInstanceId” key of one of the adapters.  Once found, it’s not a bad idea to update your list to keep track of what’s what.  Mine looks like this now:</p>
<div id="highlighter_868332" class="syntaxhighlighter nogutter  ">
<div class="lines no-wrap">
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">SERVERNAME {7A310D71-217C-4E4A-9DA7-43299A76CBD5} 172.16.0.9  0009 Intel</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">SERVERNAME {7BC7F3B9-B245-4579-82CB-C94161BFDBC1} 172.16.0.7  0005 Broadcom</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">SERVERNAME {8BA5076E-0FC3-4D20-9609-654F228EE6BD} 172.16.0.6  0004 Broadcom</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">SERVERNAME {98ABBECA-B8A2-41D2-9550-8B571E50F49A} 172.16.0.8  0008 Intel</code></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<p>Scroll up to find the “*JumboPacket” key and double click it to change the default value of 1514 to <strong>9014</strong>.  Note the extra 14 bytes here represents packet headers that normally are not counted in MTU size.</p>
<p><a href="http://mrshannon.files.wordpress.com/2010/01/jumboframes-intelregistry-packetsize.png"><img class="alignnone size-full wp-image-48" title="JumboFrames-IntelRegistry-PacketSize" src="http://mrshannon.files.wordpress.com/2010/01/jumboframes-intelregistry-packetsize.png?w=600" alt="" /></a></p>
<p>Repeat this for each Intel adapter you need to configure, and then reboot the server for the setting to take effect.</p>
<h3>Enable Jumbo Frames on Broadcom cards</h3>
<p>First make sure you have <a href="http://www.broadcom.com/support/ethernet_nic/netxtremeii.php">the latest Broadcom drivers</a>.  Make sure you get the 2008 R2 x64 set.</p>
<p>If you haven’t already, then download and install the driver and then reboot the host.  Note: Make sure you migrate any existing guest servers off the host before you install the drivers.  The temporary outage of the card due to the update seems to make a failover cluster angry.</p>
<p>Now get the <a href="http://www.broadcom.com/support/ethernet_nic/netxtremeii.php#mgmt_apps">Broadcom Management Application suite</a>.  Again, get the x64 set from the same page.</p>
<p>Install the management app.  I opt’d not to install the BASP component (see screenshot below) since we do not want failover or teaming in this scenario.  It’ll likely warn you that you need the dotNet Framework 2.0 and you should be able to ignore this because the installer just does not recognize the “Core” framework, but the application still runs.  To make sure you do in fact have the framework installed, run “<strong>oclist | findstr /i netfx</strong>” and look for a line stating that NetFx is installed.  For example, “Installed:NetFx2-ServerCore”.  If not, you can install it by running “<strong>start /w ocsetup NetFx2-ServerCore</strong>” or instead you can install dotNet 3.0 and 3.5 by running “<strong>start /w ocsetup NetFx3-ServerCore</strong>”.</p>
<p><a href="http://mrshannon.files.wordpress.com/2010/01/jumboframes-bcom-install.png"><img class="alignnone size-full wp-image-46" title="JumboFrames-Bcom-Install" src="http://mrshannon.files.wordpress.com/2010/01/jumboframes-bcom-install.png?w=600" alt="" /></a></p>
<p>From C:\Program Files\Broadcom\BACS run “<strong><em>BACSCLi</em></strong>” to run in interactive mode.  It will show you a list of all network adapter drivers installed.  You only care about the “NDIS” adapters so enter “<strong><em>list ndis</em></strong>” and you’ll see something like this:</p>
<div id="highlighter_531927" class="syntaxhighlighter nogutter  ">
<div class="lines no-wrap">
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">C  MAC          Dev Type Name</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">-  ------------ -------- ----------------------------------------------------</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">0  001B214285B8 NDIS     [0000] Intel(R) Gigabit ET Quad Port Server Adapter</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">1  001B214285B9 NDIS     [0007] Intel(R) Gigabit ET Quad Port Server Adapter #2</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">2  001B214285BC NDIS     [0008] Intel(R) Gigabit ET Quad Port Server Adapter #3</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">3  001B214285BD NDIS     [0009] Intel(R) Gigabit ET Quad Port Server Adapter #4</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">4  0026B9429866 NDIS     [0002] Broadcom BCM5709C NetXtreme II GigE (NDIS VBDClient)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">5  0026B9429868 NDIS     [0003] Broadcom BCM5709C NetXtreme II GigE (NDIS VBDClient) #2</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">6  0026B942986A NDIS     [0004] Broadcom BCM5709C NetXtreme II GigE (NDIS VBDClient) #3</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">7  0026B942986C NDIS     [0005] Broadcom BCM5709C NetXtreme II GigE (NDIS VBDClient) #4</code></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<p>If you did the Intel configuration you’ll notice the four digit number in square braces of the Name field matches the Control\Class registry key.</p>
<p>Use some combination of “<strong><em>ipconfig /all</em></strong>” in another window or CtxAdmTools’ <a title="Download Visual Core Config" href="http://ctxadmtools.musumeci.com.ar/VisualCore2008/VisualCoreDownload.html">Visual Core Configurator 2008</a> or the four digit registry code to identify the adapter that you want to configure.  In this example we want Connection #6.  Select it by using “<strong><em>select 6</em></strong>” or whatever number is in the “C” column that matches your adapter.  Now validate that you have selected the correct adapter by reviewing some of its details.  Run “<strong><em>info</em></strong>” to see it’s MAC/IP, etc.</p>
<div id="highlighter_85290" class="syntaxhighlighter nogutter  ">
<div class="lines no-wrap">
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Vital Signs</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">-----------</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">MAC Address:              : 00-26-B9-42-98-6A</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2 highlighted">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Permanent MAC Address:    : 00-26-B9-42-98-6A</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1 highlighted">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">IPV4 Address              : 172.16.0.6</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Link Status               : UP</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Duplex:                   : Full</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Speed(in Mbps):           : 1000</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Offload Capabilities      : TOE,LSO,CO,RSS</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2 highlighted">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Mtu                       : 1500</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Driver Information</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">-----------</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Driver Status:            : Loaded</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Driver Name:              : bxnd60a.sys</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Driver Version:           : 5.0.13.0</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Driver Date:              : 07/30/2009</code></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<p>Notice the MTU setting is set to 1500 by default.  Now run “<strong><em>cfg advanced</em></strong>” to list its advanced properties.</p>
<div id="highlighter_60734" class="syntaxhighlighter nogutter  ">
<div class="lines no-wrap">
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Advanced</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">--------</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Ethernet@WireSpeed:                     Enable (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2 highlighted">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Flow Control:                           Disable</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">IPv4 Checksum Offload:                  Tx/Rx enabled (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">IPv4 Large Send Offload:                Enable (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">IPv6 Checksum Offload:                  Tx/Rx enabled (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">IPv6 Large Send Offload:                Enable (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Interrupt Moderation:                   Enable (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2 highlighted">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Jumbo MTU:                              1500 (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Locally Administered Address:           Not Present (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Number Of RSS Queues:                   8 (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Priority &amp; VLAN:                        Priority &amp; VLAN enabled (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Receive Buffers:                        750 (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Receive Side Scaling:                   Enable (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Speed &amp; Duplex:                         Auto (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">TCP Connection Offload (IPv4):          Enable (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">TCP Connection Offload (IPv6):          Enable (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Transmit Buffers:                       1500 (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt2">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">VLAN ID:                                0 (Default)</code></td>
</tr>
</tbody>
</table>
</div>
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">Wake Up Capabilities:                   Both (Default)</code></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<p>Run “<strong><em>cfg advanced “Jumbo MTU”=9000</em></strong>” to set Jumbo frames to 9000 bytes.  Note that you do not have to account for the 14 bytes of header data here.  It’ll take a few seconds to apply the change but you should not need to reboot (yay!).  You can now run “<strong><em>cfg advanced</em></strong>” and “<strong><em>info</em></strong>” to list the settings and ensure that the MTU is in fact set to 9000.</p>
<p>You should also enable Flow Control for Transmit (Tx) and Receive (Rx).  With the correct adapter already selected, run “<strong><em>cfg advanced “Flow Control”=”Rx &amp; Tx enabled”</em></strong>”.</p>
<p>Once that is complete you can enter “<strong><em>q</em></strong>” to exit BACScli or start over using “<strong><em>list ndis</em></strong>” and select another interface to configure.  You can also use this utility to select non-Broadcom adapters to display some of their info like MTU size.</p>
<h3>Testing Jumbo Frames</h3>
<p>To test if Jumbo Frames are working you can ping another host target that also supports Jumbo Frames.  The easiest way that I have found to do this was to just change the IP of your test NIC and your test target NIC to something that no other adapter has.  This is because there is no way to tell windows specifically what NIC to send traffic over, so setting the NIC’s to their own network ip space is the only way to ensure that the ping traverses a particular adapter.</p>
<p>For example, I changed the source test nic to 172.16.1.4 and the target to 172.16.1.8 and no other adapters on either host saw set in the 172.16.1.* range.</p>
<p>First try a normal “<strong><em>ping 172.16.1.8</em></strong>” and it should work fine.  Then use “<strong><em>ping -f -l 6000 172.16.1.8</em></strong>” to test jumbo frames and it should also work, only this time you’ll see it sending 6000 bytes instead of 32.</p>
<p>So that about covers it.  I had to do this for each of the 32 iSCSI nics spread across the 8 host servers, but it works!  You should be aware that if you do a driver update or if you share a NIC with a virtual network (as a Hyper-V Host) your settings may be lost and you’ll have to go through this again.</p>
<p>Obtained from this link <a href="http://mrshannon.wordpress.com/2010/01/13/jumbo-frames-on-hyper-v-server/#comment-13" target="_blank">http://mrshannon.wordpress.com/2010/01/13/jumbo-frames-on-hyper-v-server/#comment-13</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.robertomm.com/wordpress/cambiar-jumbo-framesmtu-en-hyper-v-server-windows-server-20088-core/?lang=en/feed/&#038;lang=en</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

