 




<?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>The Real (and Virtual) Adventures of Nathan the IT Guy &#187; cannot bind a vmnic to a vswif</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/information-technology/tag/cannot-bind-a-vmnic-to-a-vswif/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/information-technology</link>
	<description></description>
	<lastBuildDate>Wed, 22 May 2013 13:01:54 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>vSwitch and vSwif Problems</title>
		<link>http://itknowledgeexchange.techtarget.com/information-technology/vswitch-and-vswif-problems/</link>
		<comments>http://itknowledgeexchange.techtarget.com/information-technology/vswitch-and-vswif-problems/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 04:44:57 +0000</pubDate>
		<dc:creator>Nathan Simon</dc:creator>
				<category><![CDATA[cannot bind a vmnic to a vswif]]></category>
		<category><![CDATA[cannot connect to service console]]></category>
		<category><![CDATA[ESX 3.5]]></category>
		<category><![CDATA[esx networking]]></category>
		<category><![CDATA[service console issues]]></category>
		<category><![CDATA[vmnic not bound to service console]]></category>
		<category><![CDATA[vmware]]></category>
		<category><![CDATA[vnetworking]]></category>
		<category><![CDATA[vsphere]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/information-technology/vswitch-and-vswif-problems/</guid>
		<description><![CDATA[What happens when you cannot connect to the service console anymore, and even if you had a backup service console and it wasn&#8217;t working either, well i happened to me. When I attempted to attach a vmnic to a vSwitch, I got an error message, no matter what I tried I could not get it [...]]]></description>
				<content:encoded><![CDATA[<p>What happens when you cannot connect to the service console anymore, and even if you had a backup service console and it wasn&#8217;t working either, well i happened to me. When I attempted to attach a vmnic to a vSwitch, I got an error message, no matter what I tried I could not get it reconnected. Last ditch effort is to recreate the vswif interface. Below are the steps I took. I had to do the first 4 steps twice, as i had to vSwitches.</p>
<p>Note: On your system the vswif, vmnic, vSwitch numbers and network settings are different.</p>
<p>1.Run the following command to list the name of the vswif adapter:</p>
<p><em>esxcfg-vswif -l</em></p>
<p>2.Run the following command to delete the vswif adapter:</p>
<p><em>esxcfg-vswif &#8211;del vswif0</em></p>
<p>3.Run the following command to list the name of the vSwitch:</p>
<p><em>esxcfg-vswitch -l</em></p>
<p>4.Run the following command to delete the vSwitch:</p>
<p><em>esxcfg-vswitch -d vSwitch0</em></p>
<p>5.Run the following command to create the vSwitch:</p>
<p><em>esxcfg-vswitch -a vSwitch0</em></p>
<p>6.Run the following commands to create default port groups for vSwitch:</p>
<p><em>esxcfg-vswitch -A &#8220;VM Network&#8221; vSwitch0<br />
esxcfg-vswitch -A &#8220;Service Console&#8221; vSwitch0</em></p>
<p>7.Run the following command to create the vswif adapter:</p>
<p><em>esxcfg-vswif &#8211;add &#8211;portgroup &#8220;Service Console&#8221; &#8211;ip=nnn.nnn.nnn.nnn &#8211;netmask=255.255.255.0 vswif0 </em></p>
<p>8.Run the following command to verify that the settings in the network file are correct:</p>
<p><em>cat /etc/sysconfig/network</em></p>
<p>NETWORKING=yes<br />
GATEWAYDEV=vswif0<br />
HOSTNAME=host.domain.com<br />
GATEWAY=nnn.nnn.nnn.nnn</p>
<p>9.Run the following commands to list all of the network adapters and associate a vmnic which has a link status of up:</p>
<p><em>esxcfg-nics -l<br />
esxcfg-vswitch -L vmnic1 vSwitch0</em></p>
<p>10.Run the following command to verify that the vmnic is associated with the vSwitch:</p>
<p><em>esxcfg-vswitch -l</em></p>
<p>11.Ping an IP address to check for network connectivity. If the ping fails remove the previous vmnic from the vSwitch and try another adapter that has a link status of up.</p>
<p>12.Once you have verified connectivity, you can then connect to Virtual Infrastructure client of the affected ESX Server, you may or may not have a bit a work ahead of you at this point, depending on iSCSI, etc&#8230;</p>
<p>Good Luck</p>
<p>-NS</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/information-technology/vswitch-and-vswif-problems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
