<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Hacking Xenserver</title>
	<atom:link href="http://hackingxenserver.wordpress.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://hackingxenserver.wordpress.com</link>
	<description>Advanced use of Citrix Xenserver</description>
	<lastBuildDate>Sat, 13 Jun 2009 18:49:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='hackingxenserver.wordpress.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>Hacking Xenserver</title>
		<link>http://hackingxenserver.wordpress.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://hackingxenserver.wordpress.com/osd.xml" title="Hacking Xenserver" />
	<atom:link rel='hub' href='http://hackingxenserver.wordpress.com/?pushpress=hub'/>
		<item>
		<title>Attaching Management Network to a virtual NIC</title>
		<link>http://hackingxenserver.wordpress.com/2009/06/13/attaching-management-network-to-a-virtual-nic/</link>
		<comments>http://hackingxenserver.wordpress.com/2009/06/13/attaching-management-network-to-a-virtual-nic/#comments</comments>
		<pubDate>Sat, 13 Jun 2009 18:49:31 +0000</pubDate>
		<dc:creator>foscarini</dc:creator>
				<category><![CDATA[Unsupported configurations]]></category>
		<category><![CDATA[management network]]></category>
		<category><![CDATA[vlan]]></category>

		<guid isPermaLink="false">http://hackingxenserver.wordpress.com/?p=3</guid>
		<description><![CDATA[Citrix doesn&#8217;t support the use of management interface via VLAN, as said in the XenServer documentation. Despite of the lack of official support, this configuration is possible and can be arranged via XenServer management tools. The procedures described in this howto can be performed in standalone XenServers and was tested with versions 5.0U3 e 5.5Beta. [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=hackingxenserver.wordpress.com&amp;blog=8142257&amp;post=3&amp;subd=hackingxenserver&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>Citrix doesn&#8217;t support the use of management interface via VLAN, as said in the <a href="http://docs.xensource.com/XenServer/5.0.0/1.0/en_gb/reference.html#networking-changing_network_config-mgmt_nic">XenServer documentation</a>. Despite of the lack of official support, this configuration is possible and can be arranged via XenServer management tools. The procedures described in this howto can be performed in standalone XenServers and was tested with versions 5.0U3 e 5.5Beta.</p>
<ul>
<li> Create the virtual NIC via XenCenter following these steps:
<ol>
<li>In Network tab, click &#8220;Add Network&#8221;</li>
<li>Keep selected &#8220;External Network&#8221; and click &#8220;Next&#8221;</li>
<li>Type a name and a optional description</li>
<li>Select the NIC which is connected to the trunk interface and type the VLAN ID</li>
</ol>
<p>The Network tab should look like the following image. In this example &#8220;management-vlan&#8221; will be the interface used for the Management Network. I&#8217;m assuming that the network level configuration was done previously.</li>
</ul>
<div id="attachment_12" class="wp-caption aligncenter" style="width: 550px"><img class="size-full wp-image-12" title="Management Vlan" src="http://hackingxenserver.files.wordpress.com/2009/06/management-vlan.png" alt="configured management-vlan virtual NIC" width="540" height="360" /><p class="wp-caption-text">configured management-vlan virtual NIC</p></div>
<ul>
<li>Tell to XenServer which interface use for the Management Network
<ol>
<li>Access the server via console (real console, not Console tab in XenCenter)</li>
<li>Select &#8220;Network and Management Interface&#8221;</li>
<li>Select &#8220;Configure Management Interface&#8221; and type the administrator password as required</li>
<li>The screen will show a list of the available real and virtual NICs. Select the &#8220;eth1: Virtual PIF with management-vlan (connected)&#8221;</li>
<li>Configure the IP to be used, either static or DHCP</li>
<li>Apply the configuration and tell to &#8220;Copy Hostname to XenCenter Name&#8221;</li>
</ol>
</li>
</ul>
<div id="attachment_13" class="wp-caption aligncenter" style="width: 537px"><img class="size-full wp-image-13" title="list of network interfaces" src="http://hackingxenserver.files.wordpress.com/2009/06/list-of-network-interfaces.png" alt="list of network interfaces" width="527" height="302" /><p class="wp-caption-text">List of available network interfaces</p></div>
<p>Between steps 5 and 6 the XenServer host may be inaccessible via network, specifically if the new and old management interfaces are in the same ethernet addressing. In such case you need to access the Linux Console by typing &#8220;Alt + F3&#8243; in the XenServer real console. Once authenticated, you should run the following commands:</p>
<ol>
<li>
<pre>[root@xenserver ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 xapi1
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 xenbr0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 xenbr0
0.0.0.0         192.168.0.254   0.0.0.0         UG    0      0        0 xapi1</pre>
<p>verify which network is configured with the interface xenbr0 and run the following command to remove this route</li>
<li>
<pre>[root@xenserver ~]# route del -net 192.168.0.0 netmask 255.255.255.0 dev xenbr0</pre>
<p>After removing the route you can return to the XenServer console, typing &#8220;Alt + F1&#8243;</li>
</ol>
<p>If you changed the IP address of the XenServer host, the XenCenter connection should be removed and a new one must be created with the new IP.</p>
<p>If the IP is the same, for a short period of time the connection will freeze, but will return as soon as the routers/switches propagate the new path to the XenServer host.</p>
<p>A workaround to use VLAN for the management network in a XenServer host that will be added to a XenServervers Pool will be discussed later.</p>
<br />Posted in Unsupported configurations Tagged: management network, vlan <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/hackingxenserver.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/hackingxenserver.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/hackingxenserver.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/hackingxenserver.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/hackingxenserver.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/hackingxenserver.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/hackingxenserver.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/hackingxenserver.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/hackingxenserver.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/hackingxenserver.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/hackingxenserver.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/hackingxenserver.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/hackingxenserver.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/hackingxenserver.wordpress.com/3/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=hackingxenserver.wordpress.com&amp;blog=8142257&amp;post=3&amp;subd=hackingxenserver&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://hackingxenserver.wordpress.com/2009/06/13/attaching-management-network-to-a-virtual-nic/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/583a1a7e7a7aad6e61c73b35c0baacaa?s=96&#38;d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D96&#38;r=X" medium="image">
			<media:title type="html">foscarini</media:title>
		</media:content>

		<media:content url="http://hackingxenserver.files.wordpress.com/2009/06/management-vlan.png" medium="image">
			<media:title type="html">Management Vlan</media:title>
		</media:content>

		<media:content url="http://hackingxenserver.files.wordpress.com/2009/06/list-of-network-interfaces.png" medium="image">
			<media:title type="html">list of network interfaces</media:title>
		</media:content>
	</item>
	</channel>
</rss>