<?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>Networknet.nl &#187; vlan</title>
	<atom:link href="http://www.networknet.nl/apps/wp/archives/tag/vlan/feed" rel="self" type="application/rss+xml" />
	<link>http://www.networknet.nl/apps/wp</link>
	<description>Stay Connected</description>
	<lastBuildDate>Fri, 10 Feb 2012 16:46:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>ESX: esxcfg-vswitch and special vlan switch</title>
		<link>http://www.networknet.nl/apps/wp/archives/452</link>
		<comments>http://www.networknet.nl/apps/wp/archives/452#comments</comments>
		<pubDate>Thu, 12 Jun 2008 14:56:36 +0000</pubDate>
		<dc:creator>Ivan Versluis</dc:creator>
				<category><![CDATA[ESX]]></category>
		<category><![CDATA[commandline]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[vlan]]></category>

		<guid isPermaLink="false">http://www.networknet.nl/apps/wp2/archives/452</guid>
		<description><![CDATA[If you need to create 5 or more of Virtual Port groups on a vSwtich and you don&#8217;t want to use the VI client than logon on the service console and run the commands below. For creating a new Virtual Port Group use: esxcfg-vswitch -A NAME-TO-GIVE vSwitch0 Assigning a special VLAN to this a Virtual Port Group: esxcfg-vswitch -v VLANID -p PORTGROUP vSwitch0 With these two simple commands I was able to push my sh script and create same &#8220;Networking&#8221; configuration on dozen of my ESX servers. [root@ESX-02 root]# esxcfg-vswitch -A VLAN282 vSwitch0[root@ESX-02 root]# esxcfg-vswitch -A VLAN283 vSwitch0[root@ESX-02 root]# esxcfg-vswitch -A VLAN284 vSwitch0[root@ESX-02 root]# esxcfg-vswitch -A VLAN285 vSwitch0[root@ESX-02 root]# esxcfg-vswitch -A VLAN299 vSwitch0[root@ESX-02 root]# esxcfg-vswitch -A VLAN220 vSwitch0[root@ESX-02 root]# esxcfg-vswitch -v 282 -p VLAN282 vSwitch0[root@ESX-02 root]# esxcfg-vswitch -v 283 -p VLAN283 vSwitch0[root@ESX-02 root]# esxcfg-vswitch -v 284 -p VLAN284 vSwitch0[root@ESX-02 root]# esxcfg-vswitch -v 285 -p VLAN285 vSwitch0[root@ESX-02 root]# esxcfg-vswitch -v 299 -p VLAN299 vSwitch0[root@ESX-02 root]# esxcfg-vswitch -v 220 -p VLAN220 vSwitch0 esxcfg-vswitch [options] [vswitch[:ports]] &#160; -a&#124;&#8211;add&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; Add a new virtual switch. &#160; -d&#124;&#8211;delete&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; Delete the virtual switch. &#160; -l&#124;&#8211;list&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; List all the virtual switches. &#160; -L&#124;&#8211;link=pnic&#160;&#160;&#160;&#160;&#160;&#160;&#160; Set pnic as an uplink for the vswitch. &#160; -U&#124;&#8211;unlink=pnic&#160;&#160;&#160;&#160;&#160; Remove pnic from the uplinks for the vswitch. &#160; -M&#124;&#8211;add-pg-uplink&#160;&#160;&#160; Add an uplink to the list of uplinks for a portgroup &#160; -N&#124;&#8211;del-pg-uplink&#160;&#160;&#160; Delete an uplink from the list of uplinks for a portgroup &#160; -p&#124;&#8211;pg=portgroup&#160;&#160;&#160;&#160; Specify a portgroup for operation &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; Use ALL to set VLAN IDs on all portgroups &#160; -v&#124;&#8211;vlan=id&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; Set vlan ...]]></description>
		<wfw:commentRss>http://www.networknet.nl/apps/wp/archives/452/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>VMWare ESX3i Cisco CDP protocol L2 overview</title>
		<link>http://www.networknet.nl/apps/wp/archives/374</link>
		<comments>http://www.networknet.nl/apps/wp/archives/374#comments</comments>
		<pubDate>Wed, 06 Feb 2008 18:57:05 +0000</pubDate>
		<dc:creator>Ivan Versluis</dc:creator>
				<category><![CDATA[VMWare]]></category>
		<category><![CDATA[3i]]></category>
		<category><![CDATA[cdp]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[trunk]]></category>
		<category><![CDATA[vlan]]></category>

		<guid isPermaLink="false">http://www.networknet.nl/apps/wp2/archives/374</guid>
		<description><![CDATA[Cisco Discovery Protocol (CDP) allows ESX Server 3 administrators to determine which Cisco switch port is connected to a given vSwitch. When CDP is enabled for a particular vSwitch, you can view properties of the Cisco switch (such as device ID, software version, and timeout) from the VI Client. You can use the service console command-line interface to enable CDP. &#160; Using this information and without going to the server room and locating the network cable in the rack I was able to configure the interface on the switch real time. The switchport should be set as trunk and for security reasons also configure the allowed vlan&#8217;s. interface GigabitEthernet0/15 description ** ESX-01 Trunk port LAN ** switchport trunk allowed vlan 1,200 switchport mode trunk spanning-tree portfast !]]></description>
		<wfw:commentRss>http://www.networknet.nl/apps/wp/archives/374/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Cisco: How to configure switchport for trunking Hyper-V?</title>
		<link>http://www.networknet.nl/apps/wp/archives/336</link>
		<comments>http://www.networknet.nl/apps/wp/archives/336#comments</comments>
		<pubDate>Wed, 16 Jan 2008 11:59:59 +0000</pubDate>
		<dc:creator>Ivan Versluis</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Hyper-V]]></category>
		<category><![CDATA[mode]]></category>
		<category><![CDATA[trunk]]></category>
		<category><![CDATA[trunk allowed]]></category>
		<category><![CDATA[vlan]]></category>
		<category><![CDATA[vlanid]]></category>
		<category><![CDATA[windows2008]]></category>

		<guid isPermaLink="false">http://www.networknet.nl/apps/wp2/archives/336</guid>
		<description><![CDATA[In the following example I installed my Windows Server 2008 Hyper-V server and connected the network uplink connection to the default 1 vlan switchport. I have a separated vlan 2200 for my lab environment. I wanted to test the new feature of enabling the VLAN ID on the new Microsoft&#8217;s hypervisor. How to configure the Cisco switch port to allow trunking for my Hyper-V server? Login into the Cisco Switch, go into privileged mode and open the configuration terminal. Enter or paste the configuration below. interface GigabitEthernet0/1 description ** Uplink to Hyper-V windows box ** switchport trunk allowed vlan 1,2200 switchport mode trunk ! In the Virtualization Management console I configured and installed a new Windows Server 2003 virtual machine. While testing I had an issue with the vm additions and network connectivity was not working. I removed current nic controller and added legacy network adapter. In the legacy network adapter, check enable virtual LAN identification and enter the VLAN ID. Click ok or Apply the configuration. This is really cool feature now integrated with Hyper-V. ESX supported VLAN&#8217;s for while and Microsoft is catching up now in the upcoming release of their hypervisor product.]]></description>
		<wfw:commentRss>http://www.networknet.nl/apps/wp/archives/336/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

