<?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>cyborgworkshop.org &#187; lun</title>
	<atom:link href="http://cyborgworkshop.org/tag/lun/feed/" rel="self" type="application/rss+xml" />
	<link>http://cyborgworkshop.org</link>
	<description>Blurring the line</description>
	<lastBuildDate>Wed, 22 Feb 2012 14:31:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Adding a LUN with an existing VMFS into an ESXi node</title>
		<link>http://cyborgworkshop.org/2008/09/14/adding-a-lun-with-an-existing-vmfs-into-an-esxi-node/</link>
		<comments>http://cyborgworkshop.org/2008/09/14/adding-a-lun-with-an-existing-vmfs-into-an-esxi-node/#comments</comments>
		<pubDate>Mon, 15 Sep 2008 02:53:53 +0000</pubDate>
		<dc:creator>jason</dc:creator>
				<category><![CDATA[VMWare]]></category>
		<category><![CDATA[ESXi]]></category>
		<category><![CDATA[iscsi]]></category>
		<category><![CDATA[lun]]></category>
		<category><![CDATA[san]]></category>
		<category><![CDATA[vmfs]]></category>

		<guid isPermaLink="false">http://cyborgworkshop.org/?p=101</guid>
		<description><![CDATA[I really only have 1 lun that is important to me on my home san. It stores a VM running ubuntu that I remote into using NoMachine on a fairly constant basis from all over the place. When I upgraded the SAN and did a zfs send and receive from one SAN to another, I [...]]]></description>
			<content:encoded><![CDATA[<p>I really only have 1 lun that is important to me on my home san. It stores a VM running ubuntu that I remote into using NoMachine on a fairly constant basis from all over the place. When I upgraded the SAN and did a zfs send and receive from one SAN to another, I neglected to think about the iscsi IDs getting changed between SANs thus screwing up my ESXi machine. I could reimport the LUNs easy enough, but when you import a LUN into an ESX node, the first thing it does is format it! Not good. So after digging around, I found a way to tell ESXi to simply scan the SAN for available LUNs and to allow access to VMFS that might be on them.<br />
In your VI client, do the following.</p>
<blockquote><ul>
<li> Select the Configuration tab</li>
<li> Select Advanced Settings</li>
<li> Select LVM in the left pane</li>
<li> Set LVM.EnableResignature to 1 and hit OK</li>
<li> Go back to Configuration</li>
<li> Click Storage Adapters</li>
<li> Right click on your iscsi adapter and select rescan. This will take a minute or two.</li>
<li> In storage, you&#8217;ll now see a bunch of LUNs labeled snapshot-whatever_you_called_the_LUN</li>
<li> Rename the snapshots to just be whatever_you_called_the_LUN and go along your merry way</li>
</ul>
</blockquote>
<p>Crisis averted!</p>
]]></content:encoded>
			<wfw:commentRss>http://cyborgworkshop.org/2008/09/14/adding-a-lun-with-an-existing-vmfs-into-an-esxi-node/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>connecting a solaris 10 machine to an iscsi LUN</title>
		<link>http://cyborgworkshop.org/2008/06/25/connecting-a-solaris-10-machine-to-an-iscsi-lun/</link>
		<comments>http://cyborgworkshop.org/2008/06/25/connecting-a-solaris-10-machine-to-an-iscsi-lun/#comments</comments>
		<pubDate>Wed, 25 Jun 2008 19:23:44 +0000</pubDate>
		<dc:creator>jason</dc:creator>
				<category><![CDATA[Solaris]]></category>
		<category><![CDATA[devfsadm]]></category>
		<category><![CDATA[iscsi]]></category>
		<category><![CDATA[iscsiadm]]></category>
		<category><![CDATA[lun]]></category>

		<guid isPermaLink="false">http://cyborgworkshop.org/?p=59</guid>
		<description><![CDATA[It couldn&#8217;t get much easier then this. Assuming that your SAN is on 192.168.168.168 and that your lun doesn&#8217;t need CHAP authentication, give these commands a run. iscsiadm add discovery-address 192.168.168.168:3260 iscsiadm list target devfsadm -i iscsi Now you can run format and access that disk, enjoy!]]></description>
			<content:encoded><![CDATA[<p>It couldn&#8217;t get much easier then this. Assuming that your SAN is on 192.168.168.168 and that your lun doesn&#8217;t need CHAP authentication,  give these commands a run.</p>
<blockquote><p>iscsiadm add discovery-address 192.168.168.168:3260<br />
iscsiadm list target<br />
devfsadm -i iscsi</p></blockquote>
<p>Now you can run format and access that disk,<br />
enjoy!</p>
]]></content:encoded>
			<wfw:commentRss>http://cyborgworkshop.org/2008/06/25/connecting-a-solaris-10-machine-to-an-iscsi-lun/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

