<?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>unixpowered.com &#187; fibre channel</title>
	<atom:link href="http://www.unixpowered.com/blog/category/fibre-channel/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.unixpowered.com/blog</link>
	<description></description>
	<lastBuildDate>Wed, 21 Jul 2010 13:42:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Linux multipathing</title>
		<link>http://www.unixpowered.com/blog/2009/11/27/linux-multipathing/</link>
		<comments>http://www.unixpowered.com/blog/2009/11/27/linux-multipathing/#comments</comments>
		<pubDate>Fri, 27 Nov 2009 22:40:46 +0000</pubDate>
		<dc:creator>somedude</dc:creator>
				<category><![CDATA[centos]]></category>
		<category><![CDATA[fibre channel]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[linux tips]]></category>
		<category><![CDATA[multipathing]]></category>
		<category><![CDATA[redhat]]></category>
		<category><![CDATA[san]]></category>
		<category><![CDATA[storage]]></category>

		<guid isPermaLink="false">http://www.unixpowered.com/blog/?p=381</guid>
		<description><![CDATA[I use MPxIO in Solaris quite often and it works very well for me. This time I needed to test out I/O multipathing in RedHat. What I really needed to do: have a server with two HBA&#8217;s manage a mirror which has submirrors on separate SAN&#8217;s; so that the server has multiple paths to each [...]]]></description>
			<content:encoded><![CDATA[<p>I use MPxIO in Solaris quite often and it works very well for me. This time I needed to test out I/O multipathing in RedHat. What I really needed to do: have a server with two HBA&#8217;s manage a mirror which has submirrors on separate SAN&#8217;s; so that the server has multiple paths to each submirror. That way, if an HBA goes the server has still connection to both submirrors through the remaining HBA. </p>
<p>Gear used in this &#8220;experiment&#8221;:</p>
<ul>
<li>Dell Poweredge server.</li>
<li>Two Qlogic QLA2310 HBA&#8217;s.</li>
<li>RHEL Server 5.3 x86.</li>
<li>Two SAN&#8217;s presenting one LUN each.</li>
</ul>
<p>Rough steps I took to get this working:</p>
<ol>
<li>Make sure device mapper package is installed.</li>
<li>Present two LUN&#8217;s from two SAN&#8217;s.</li>
<li>Probe HBA&#8217;s for presented LUN&#8217;s.</li>
<li>Configure multipathing.</li>
</ol>
<p>First and foremost, make sure <em>qla2xxx</em> driver is loaded. You also have to make sure you have <em>device-mapper-multipath-0.4.7-23.el5</em> installed. Next, configure multipathing daemon so that it starts on boot:</p>
<p><code>[root@carbon ~]# <strong>chkconfig multipathd on</strong></code></p>
<p>When that&#8217;s done you need to make the system aware of the presented LUN&#8217;s. One way to do so is to reboot the server. Another option is to force HBA scan:</p>
<p><code>[root@carbon ~]# <strong>echo "- - -" &gt; /sys/class/scsi_host/host1/scan</strong></code></p>
<p>During this you should watch <em>/var/log/messages</em> to see if your LUN&#8217;s are detected. When done, make <em>multipathd</em> aware of the LUN&#8217;s:</p>
<p><code>[root@</code><code>carbon</code><code> ~]# <strong>multipath -v2 -d</strong></code></p>
<p>The above command is a &#8220;dry run&#8221;. There will be no device map changes committed. You will only be shown device mapper changes that will be made. To commit device map changes run:</p>
<p><code>[root@carbon ~]# <strong>multipath -v2</strong></code></p>
<p>Once this is done you can see what <em>multipathd</em> is seeing:</p>
<p><code>[root@carbon ~]# <strong>multipath -ll</strong><br />
mpath2 (3600508d311100a300000f00001a90000) dm-3 COMPAQ,HSV111 (C)COMPAQ<br />
[size=15G][features=1 queue_if_no_path][hwhandler=0][rw]<br />
\_ round-robin 0 [prio=100][enabled]<br />
&nbsp;\_ 1:0:3:1 sde 8:64  [active][ready]<br />
&nbsp;\_ 2:0:3:1 sdh 8:112 [active][ready]<br />
\_ round-robin 0 [prio=20][enabled]<br />
&nbsp;\_ 1:0:2:1 sdd 8:48  [active][ready]<br />
&nbsp;\_ 2:0:2:1 sdg 8:96  [active][ready]<br />
mpath1 (3600508c362d0a1250000900001490000) dm-2 COMPAQ,HSV111 (C)COMPAQ<br />
[size=15G][features=1 queue_if_no_path][hwhandler=0][rw]<br />
\_ round-robin 0 [prio=100][enabled]<br />
&nbsp;\_ 1:0:0:1 sdb 8:16  [active][ready]<br />
&nbsp;\_ 2:0:4:1 sdi 8:128 [active][ready]<br />
\_ round-robin 0 [prio=20][enabled]<br />
&nbsp;\_ 1:0:1:1 sdc 8:32  [active][ready]<br />
&nbsp;\_ 2:0:1:1 sdf 8:80  [active][ready]</code></p>
<p>If everything looks good, you can create configuration file for <em>multipathd</em>. You will need to edit <em>/etc/multipath.conf</em> and depending on your environment, add or modify some parameters. The configuration file contains enough comments and examples to figure out what different parameters mean. When in doubt, consult the man pages.</p>
<p>First, add a <em>blacklist</em> section, which will make certain device exempt from multipathing. I have my internal drives listed in blacklist section:</p>
<p><code>blacklist&nbsp;{<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;devnode&nbsp;"^sd[a-b].*"<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;devnode&nbsp;"^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;devnode&nbsp;"^hd[a-z]"<br />
}</code></p>
<p>Next, you are going to need <em>device</em> section. This is going to be specific to your SAN. The one below is for EVA5000. I got the parameters from HP&#8217;s device mapper package:</p>
<p><code>device&nbsp;{<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;vendor&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"HP|COMPAQ"<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;product&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"HSV1[01]1&nbsp;\(C\)COMPAQ|HSV[2][01]0|HSV300"<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;path_grouping_policy&nbsp;&nbsp;&nbsp;&nbsp;group_by_prio<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;getuid_callout&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"/sbin/scsi_id&nbsp;-g&nbsp;-u&nbsp;-s&nbsp;/block/%n"<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;path_checker&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;tur<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;path_selector&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"round-robin&nbsp;0"<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;prio_callout&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"/sbin/mpath_prio_alua&nbsp;/dev/%n"<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;rr_weight&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;uniform<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;failback&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;immediate<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;hardware_handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"0"<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;no_path_retry&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;12<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;rr_min_io&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;100<br />
}</code></p>
<p>You should also look at <em>defaults</em> section to make sure it is configured for your setup. Again, the parameters in mine are specific to EVA5000:</p>
<p><code>defaults&nbsp;{<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;udev_dir&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/dev<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;polling_interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;10<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;selector&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"round-robin&nbsp;0"<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;path_grouping_policy&nbsp;&nbsp;&nbsp;&nbsp;failover<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;getuid_callout&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"/sbin/scsi_id&nbsp;-g&nbsp;-u&nbsp;-s&nbsp;/block/%n"<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;prio_callout&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"/bin/true"<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;path_checker&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;tur<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;rr_min_io&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;100<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;rr_weight&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;uniform<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;failback&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;immediate<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;no_path_retry&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;12<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;user_friendly_names&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;yes<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bindings_file&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"/var/lib/multipath/bindings"<br />
}</code></p>
<p>Finally, you will need to specify configuration for the presented LUN&#8217;s. This applies to the <em>multipaths</em> section of <em>multipath.conf</em> file:</p>
<p><code>multipath&nbsp;{<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;wwid&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3600508b4001031250000900001490000<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;alias&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;san1data<br />
}<br />
multipath&nbsp;{<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;wwid&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3600508b400011c300000f00001a90000<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;alias&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;san2data<br />
}</code></p>
<p>After you are done, restart multipathd and check output of <em>multipath -ll</em> command:</p>
<p><code>[root@carbon ~]# <strong>multipath -ll</strong><br />
san2data (3600508d311100a300000f00001a90000) dm-3 COMPAQ,HSV111 (C)COMPAQ<br />
[size=15G][features=1 queue_if_no_path][hwhandler=0][rw]<br />
\_ round-robin 0 [prio=100][active]<br />
&nbsp;\_ 1:0:3:1 sde 8:64  [active][ready]<br />
&nbsp;\_ 2:0:3:1 sdh 8:112 [active][ready]<br />
\_ round-robin 0 [prio=20][enabled]<br />
&nbsp;\_ 1:0:2:1 sdd 8:48  [active][ready]<br />
&nbsp;\_ 2:0:2:1 sdg 8:96  [active][ready]<br />
san1data (3600508c362d0a1250000900001490000) dm-2 COMPAQ,HSV111 (C)COMPAQ<br />
[size=15G][features=1 queue_if_no_path][hwhandler=0][rw]<br />
\_ round-robin 0 [prio=50][enabled]<br />
&nbsp;\_ 1:0:0:1 sdb 8:16  [active][ready]<br />
&nbsp;\_ 2:0:4:1 sdi 8:128 [active][ready]<br />
\_ round-robin 0 [prio=20][enabled]<br />
&nbsp;\_ 1:0:1:1 sdc 8:32  [active][ready]<br />
&nbsp;\_ 2:0:1:1 sdf 8:80  [active][ready]</code></p>
<p>That should be it. You should test the setup by disabling paths to see if your LUN&#8217;s stay up.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.unixpowered.com/blog/2009/11/27/linux-multipathing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disabling MPxIO for onboard disks</title>
		<link>http://www.unixpowered.com/blog/2008/09/01/disabling-mpxio-for-onboard-disks/</link>
		<comments>http://www.unixpowered.com/blog/2008/09/01/disabling-mpxio-for-onboard-disks/#comments</comments>
		<pubDate>Mon, 01 Sep 2008 18:36:21 +0000</pubDate>
		<dc:creator>somedude</dc:creator>
				<category><![CDATA[fibre channel]]></category>
		<category><![CDATA[mpxio]]></category>
		<category><![CDATA[san]]></category>
		<category><![CDATA[solaris]]></category>
		<category><![CDATA[solaris tips]]></category>
		<category><![CDATA[storage]]></category>
		<category><![CDATA[sun hardware]]></category>

		<guid isPermaLink="false">http://wayciak.wordpress.com/?p=40</guid>
		<description><![CDATA[I was configuring MPxIO on Sun Fire V490. After issuing stmsboot -e command and rebooting the server, internal disks were under MPxIO&#8217;s control.
This was not something I wanted and I needed to disable it. In order to do so I had to edit /kernel/drv/fp.conf file and tell Solaris not to enable MPxIO on internal disks. [...]]]></description>
			<content:encoded><![CDATA[<p>I was configuring <acronym title="Solaris Multiplexed I/O">MPxIO</acronym> on <a title="Sun Fire V490" href="http://www.sun.com/servers/midrange/v490/index.xml" target="_self">Sun Fire V490</a>. After issuing <em>stmsboot -e</em> command and rebooting the server, internal disks were under MPxIO&#8217;s control.</p>
<p>This was not something I wanted and I needed to disable it. In order to do so I had to edit <em>/kernel/drv/fp.conf</em> file and tell Solaris not to enable MPxIO on internal disks. So I added the following line at the end of <em>fp.conf</em> file:</p>
<p><code>name="fp" parent="/pci@8,600000/SUNW,qlc@4" port=0 mpxio-disable="yes";</code></p>
<p>This line tells Solaris to disable MPxIO on port 0 for all devices whose parent device is <em>/pci@8,600000/SUNW,qlc@4</em>. Of course, similar line should be added for all HBA&#8217;s and ports you do not want to have under MPxIO&#8217;s control. You can get the parent device from your <em>/var/adm/messages</em> file or from device links pointing to the internal disks. Here is a partial list of device links:</p>
<pre>&lt;-----------------SNIP----------------&gt;</pre>
<p><code>lrwxrwxrwx   1 root     other         70 Jun 12 11:50 c1t0d0s0 -&gt; ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037c3e2ef,0:a<br />
lrwxrwxrwx   1 root     other         70 Jun 12 11:50 c1t0d0s1 -&gt; ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037c3e2ef,0:b<br />
lrwxrwxrwx   1 root     other         70 Jun 12 11:50 c1t0d0s2 -&gt; ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037c3e2ef,0:c<br />
lrwxrwxrwx   1 root     other         70 Jun 12 11:50 c1t0d0s3 -&gt; ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037c3e2ef,0:d<br />
lrwxrwxrwx   1 root     other         70 Jun 12 11:50 c1t0d0s4 -&gt; ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037c3e2ef,0:e<br />
lrwxrwxrwx   1 root     other         70 Jun 12 11:50 c1t0d0s5 -&gt; ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037c3e2ef,0:f<br />
lrwxrwxrwx   1 root     other         70 Jun 12 11:50 c1t0d0s6 -&gt; ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037c3e2ef,0:g<br />
lrwxrwxrwx   1 root     other         70 Jun 12 11:50 c1t0d0s7 -&gt; ../../devices/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037c3e2ef,0:h</code></p>
<pre>&lt;-----------------SNIP----------------&gt;</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.unixpowered.com/blog/2008/09/01/disabling-mpxio-for-onboard-disks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Gathering fibre channel info using fcinfo</title>
		<link>http://www.unixpowered.com/blog/2008/08/19/gathering-fibre-channel-info-using-fcinfo/</link>
		<comments>http://www.unixpowered.com/blog/2008/08/19/gathering-fibre-channel-info-using-fcinfo/#comments</comments>
		<pubDate>Tue, 19 Aug 2008 19:47:25 +0000</pubDate>
		<dc:creator>somedude</dc:creator>
				<category><![CDATA[fibre channel]]></category>
		<category><![CDATA[san]]></category>
		<category><![CDATA[solaris]]></category>
		<category><![CDATA[solaris tips]]></category>
		<category><![CDATA[solaris utilities]]></category>
		<category><![CDATA[storage]]></category>

		<guid isPermaLink="false">http://wayciak.wordpress.com/?p=41</guid>
		<description><![CDATA[I came across fcinfo command reading some man page. So, I decided to see what kind of useful fibre channel information it could give me. It turns out fcinfo knows quite a bit.
We can list all local fibre channel ports:
bash-3.00# fcinfo hba-port
HBA Port WWN: 21000003ba16dbd2
OS Device Name: /dev/cfg/c1
Manufacturer: QLogic Corp.
Model: 2200
Firmware Version: 2.1.144
FCode/BIOS Version: ISP2200 [...]]]></description>
			<content:encoded><![CDATA[<p>I came across <a title="fcinfo man page" href="http://docs.sun.com/app/docs/doc/819-2240/6n4htdn4t?l=en&amp;a=view&amp;q=fcinfo" target="_self"><em>fcinfo</em></a> command reading some man page. So, I decided to see what kind of useful fibre channel information it could give me. It turns out <em>fcinfo</em> knows quite a bit.</p>
<p>We can list all local fibre channel ports:</p>
<p><code>bash-3.00# <strong>fcinfo hba-port</strong><br />
HBA Port WWN: 21000003ba16dbd2<br />
OS Device Name: /dev/cfg/c1<br />
Manufacturer: QLogic Corp.<br />
Model: 2200<br />
Firmware Version: 2.1.144<br />
FCode/BIOS Version: ISP2200 FC-AL Host Adapter Driver: 1.12 01/01/16<br />
Type: L-port<br />
State: online<br />
Supported Speeds: 1Gb<br />
Current Speed: 1Gb<br />
Node WWN: 20000003ba16dbd2<br />
HBA Port WWN: 2100001b320e3853<br />
OS Device Name: /dev/cfg/c3<br />
Manufacturer: QLogic Corp.<br />
Model: QLA2462<br />
Firmware Version: 4.0.27<br />
FCode/BIOS Version: QLA2462 Host Adapter Driver(SPARC): 1.24  11/15/06<br />
Type: N-port<br />
State: online<br />
Supported Speeds: 1Gb 2Gb 4Gb<br />
Current Speed: 2Gb<br />
Node WWN: 2000001b320e3853<br />
HBA Port WWN: 2101001b322e3853<br />
OS Device Name: /dev/cfg/c4<br />
Manufacturer: QLogic Corp.<br />
Model: QLA2462<br />
Firmware Version: 4.0.27<br />
FCode/BIOS Version: QLA2462 Host Adapter Driver(SPARC): 1.24  11/15/06<br />
Type: N-port<br />
State: online<br />
Supported Speeds: 1Gb 2Gb 4Gb<br />
Current Speed: 2Gb<br />
Node WWN: 2001001b322e3853</code></p>
<p>We can take a look what remote ports are seen by particular local fibre channel port, in this case 2100001b320e3853:</p>
<p><code>bash-3.00# <strong>fcinfo remote-port -p 2100001b320e3853</strong><br />
Remote Port WWN: 100000e00216aef3<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 100000e01124b88f<br />
Remote Port WWN: 50001fe15003b384<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 50001fe15037e759<br />
Remote Port WWN: 100000e0022744f3<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 100000e0020744f3<br />
Remote Port WWN: 50001fe150216de9<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 50001fe11025bb53<br />
Remote Port WWN: 100000e00228f492<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 100000e00208f492<br />
Remote Port WWN: 50001fe15076b59b<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 50001fe15037e759<br />
Remote Port WWN: 50001fe150216ded<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 50001fe11025bb53</code></p>
<p>Here, we get link statistics for remote fibre channel device whose WWN is 100000e0020744f3:</p>
<p><code>bash-3.00# <strong>fcinfo remote-port -l -p 2100001b320e3853 100000e0020744f3</strong><br />
Remote Port WWN: 100000e0022744f3<br />
Active FC4 Types: SCSI<br />
SCSI Target: unknown<br />
Node WWN: 100000e0020744f3<br />
Link Error Statistics:<br />
Link Failure Count: 0<br />
Loss of Sync Count: 0<br />
Loss of Signal Count: 0<br />
Primitive Seq Protocol Error Count: 0<br />
Invalid Tx Word Count: 0<br />
Invalid CRC Count: 0</code></p>
<p>We can also get link statistics and SCSI target information for all remote fibre channel devices see on local port whose WWN is 2100001b320e3853:</p>
<p><code>bash-3.00# <strong>fcinfo remote-port -sl -p 2100001b320e3853</strong><br />
Remote Port WWN: 100000e00216aef3<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 100000e01124b88f<br />
Link Error Statistics:<br />
Link Failure Count: 0<br />
Loss of Sync Count: 0<br />
Loss of Signal Count: 0<br />
Primitive Seq Protocol Error Count: 0<br />
Invalid Tx Word Count: 0<br />
Invalid CRC Count: 0<br />
LUN: 0<br />
Vendor: HP<br />
Product: MSL6000 Series<br />
OS Device Name: /devices/pci@8,600000/SUNW,qlc@1/fp@0,0/sgen@w100000e00216aef3,0<br />
LUN: 1<br />
Vendor: HP<br />
Product: Ultrium 2-SCSI<br />
OS Device Name: /dev/rmt/2n<br />
Remote Port WWN: 50001fe15003b384<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 50001fe15037e759<br />
Link Error Statistics:<br />
Link Failure Count: 0<br />
Loss of Sync Count: 0<br />
Loss of Signal Count: 0<br />
Primitive Seq Protocol Error Count: 0<br />
Invalid Tx Word Count: 0<br />
Invalid CRC Count: 0<br />
LUN: 0<br />
Vendor: COMPAQ<br />
Product: HSV111 (C)COMPAQ<br />
OS Device Name: Unknown<br />
LUN: 1<br />
Vendor: COMPAQ<br />
Product: HSV111 (C)COMPAQ<br />
OS Device Name: /dev/rdsk/c5t600508B4001031250000900000540000d0s2<br />
Remote Port WWN: 100000e0022744f3<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 100000e0020744f3<br />
Link Error Statistics:<br />
Link Failure Count: 0<br />
Loss of Sync Count: 0<br />
Loss of Signal Count: 0<br />
Primitive Seq Protocol Error Count: 0<br />
Invalid Tx Word Count: 0<br />
Invalid CRC Count: 0<br />
LUN: 0<br />
Vendor: HP<br />
Product: MSL6000 Series<br />
OS Device Name: /devices/pci@8,600000/SUNW,qlc@1/fp@0,0/sgen@w100000e0022744f3,0<br />
LUN: 1<br />
Vendor: HP<br />
Product: Ultrium 2-SCSI<br />
OS Device Name: /dev/rmt/1n<br />
LUN: 2<br />
Vendor: HP<br />
Product: Ultrium 2-SCSI<br />
OS Device Name: /dev/rmt/0n<br />
Remote Port WWN: 50001fe150216de9<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 50001fe11025bb53<br />
Link Error Statistics:<br />
Link Failure Count: 0<br />
Loss of Sync Count: 0<br />
Loss of Signal Count: 0<br />
Primitive Seq Protocol Error Count: 0<br />
Invalid Tx Word Count: 0<br />
Invalid CRC Count: 0<br />
LUN: 0<br />
Vendor: COMPAQ<br />
Product: HSV111 (C)COMPAQ<br />
OS Device Name: Unknown<br />
LUN: 1<br />
Vendor: COMPAQ<br />
Product: HSV111 (C)COMPAQ<br />
OS Device Name: /dev/rdsk/c5t600508B400011C370000C00003210000d0s2<br />
Remote Port WWN: 100000e00228f492<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 100000e00208f492<br />
Link Error Statistics:<br />
Link Failure Count: 0<br />
Loss of Sync Count: 0<br />
Loss of Signal Count: 0<br />
Primitive Seq Protocol Error Count: 0<br />
Invalid Tx Word Count: 0<br />
Invalid CRC Count: 0<br />
LUN: 0<br />
Vendor: HP<br />
Product: Ultrium 2-SCSI<br />
OS Device Name: /dev/rmt/4n<br />
LUN: 1<br />
Vendor: HP<br />
Product: Ultrium 2-SCSI<br />
OS Device Name: /dev/rmt/3n<br />
Remote Port WWN: 50001fe15076b59b<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 50001fe15037e759<br />
Link Error Statistics:<br />
Link Failure Count: 0<br />
Loss of Sync Count: 0<br />
Loss of Signal Count: 0<br />
Primitive Seq Protocol Error Count: 0<br />
Invalid Tx Word Count: 0<br />
Invalid CRC Count: 0<br />
LUN: 0<br />
Vendor: COMPAQ<br />
Product: HSV111 (C)COMPAQ<br />
OS Device Name: Unknown<br />
LUN: 1<br />
Vendor: COMPAQ<br />
Product: HSV111 (C)COMPAQ<br />
OS Device Name: /dev/rdsk/c5t600508B4001031250000900000540000d0s2<br />
Remote Port WWN: 50001fe150216ded<br />
Active FC4 Types: SCSI<br />
SCSI Target: yes<br />
Node WWN: 50001fe11025bb53<br />
Link Error Statistics:<br />
Link Failure Count: 0<br />
Loss of Sync Count: 0<br />
Loss of Signal Count: 0<br />
Primitive Seq Protocol Error Count: 0<br />
Invalid Tx Word Count: 0<br />
Invalid CRC Count: 0<br />
LUN: 0<br />
Vendor: COMPAQ<br />
Product: HSV111 (C)COMPAQ<br />
OS Device Name: Unknown<br />
LUN: 1<br />
Vendor: COMPAQ<br />
Product: HSV111 (C)COMPAQ<br />
OS Device Name: /dev/rdsk/c5t600508B400011C370000C00003210000d0s2</code></p>
<p>This command is quite handy when troubleshooting fibre channel. Very cool&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.unixpowered.com/blog/2008/08/19/gathering-fibre-channel-info-using-fcinfo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- www.000webhost.com Analytics Code -->
<script type="text/javascript" src="http://analytics.hosting24.com/count.php"></script>
<noscript><a href="http://www.hosting24.com/"><img src="http://analytics.hosting24.com/count.php" alt="web hosting" /></a></noscript>
<!-- End Of Analytics Code -->
