<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Moving a fibre channel card - LVM Implications in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600259#M648166</link>
    <description>Hi (again) Denise, Dave &amp;amp; Wodisch:&lt;BR /&gt;&lt;BR /&gt;If the hardware paths (and hence device files) are changing, then, obviously the 'vgexport/vgimprt' method is in order.  The primary and alternate links can easily be defined at that time in one-stroke.&lt;BR /&gt;&lt;BR /&gt;In cases where one merely wishes to switch primary and alternate links to achieve load balancing between two channels, then Wodisch is absolutely correct, too.  Simply 'vgreduce' the primary link(s) thereby causing the alternate to become the primary and follow that with a 'vgextend' of the original primaray link as the new alternate.&lt;BR /&gt;&lt;BR /&gt;In situations where either method would work, the biggest downside of the export/import is the need to unmount filesystems associated with the volume groups.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
    <pubDate>Wed, 31 Oct 2001 12:24:49 GMT</pubDate>
    <dc:creator>James R. Ferguson</dc:creator>
    <dc:date>2001-10-31T12:24:49Z</dc:date>
    <item>
      <title>Moving a fibre channel card - LVM Implications</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600252#M648159</link>
      <description>Hi. Dead simple configuration. V class connected to VA7400 directly via 2 x Tachlite cards. The VA is carved up into 14 x 10Gb LUNS. Each LUN holds 1 x Logical Volume. All LV's are in 1 VG (vg7401). When I set it up I alternated the PV paths allocated to the LV's between the FC cards to load balance between them. Alternate paths have been set up for each LV. OK so far? &lt;BR /&gt;&lt;BR /&gt;Now here is the question. When it was set up both FC cards went into one card cage because of space problems. We now have the opportunity to move one FC card to the other cage for better resilience. I hope to vgexport vg7401, move the card, and then vgimport vg7401 from the new location. If I alternate the PV paths between the controllers when I do the import will I achieve the same load balancing? Anyone aware of any problems or 'gotcha's' in doing this?&lt;BR /&gt;&lt;BR /&gt;Any help greatly appreciate.&lt;BR /&gt;&lt;BR /&gt;Dave</description>
      <pubDate>Wed, 24 Oct 2001 08:08:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600252#M648159</guid>
      <dc:creator>Denise Doyle</dc:creator>
      <dc:date>2001-10-24T08:08:49Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a fibre channel card - LVM Implications</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600253#M648160</link>
      <description>Hi Denise.&lt;BR /&gt;The answer is no, is you do an vgexport and vgimport, you will loose all you load balancing, new imported vg, will be seen by one controller and the other just for alternate path. At this point you must vgreduce all paths that you're seeing as primary and you want to be alternate, and the vgextend the same. Finally, you will see vg with load balancing, as you want.&lt;BR /&gt;&lt;BR /&gt;I Hope It help you !</description>
      <pubDate>Wed, 24 Oct 2001 08:22:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600253#M648160</guid>
      <dc:creator>David Navarro</dc:creator>
      <dc:date>2001-10-24T08:22:25Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a fibre channel card - LVM Implications</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600254#M648161</link>
      <description>Hi Denise:&lt;BR /&gt;&lt;BR /&gt;When you 'vgimport' simply define the order of the paths (primary and alternate) you want in a file (e.g. /tmp/vgXX.newpaths) something like this:&lt;BR /&gt;&lt;BR /&gt;# vgimport -m /tmp/vgXX.mapfile -v -f /tmp/vgXX.newpaths /dev/vgXX&lt;BR /&gt;&lt;BR /&gt;Your import will arrange your primary and alternate links as you choose in one step.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;</description>
      <pubDate>Thu, 25 Oct 2001 10:41:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600254#M648161</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-10-25T10:41:23Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a fibre channel card - LVM Implications</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600255#M648162</link>
      <description>James solution will work fine, however, if you have olar (I don't think it's possible on the V's) you could do it online with vgreduce - olar card - vgextend.&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Thu, 25 Oct 2001 10:44:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600255#M648162</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2001-10-25T10:44:10Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a fibre channel card - LVM Implications</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600256#M648163</link>
      <description>Denise,&lt;BR /&gt;&lt;BR /&gt;  Yes, you should be able to do it. &lt;BR /&gt;Make sure you have the current VGdisplay -v&lt;BR /&gt;and ioscan output, as a reference.&lt;BR /&gt;Do a vgexport of the vg's; (make note of&lt;BR /&gt;VG control number in /dev/vg**/group).&lt;BR /&gt;&lt;BR /&gt;Move the card to the different cage.&lt;BR /&gt;&lt;BR /&gt;Bring the system up; make a note of ioscan&lt;BR /&gt;output and see whether all the PV paths&lt;BR /&gt;are visible. &lt;BR /&gt;&lt;BR /&gt;Then, get onto figuring out the PV links&lt;BR /&gt;of one card vs other. (should be easy, once&lt;BR /&gt;you see the pattern of cxtydz).&lt;BR /&gt;&lt;BR /&gt;Next,  create mkdir /dev/vg**  and group file&lt;BR /&gt;&lt;BR /&gt;Vgimport -  Do the vgimport with the&lt;BR /&gt;FC1-FC2-FC2-FC1-FC1-FC2.. combination. In that&lt;BR /&gt;way, you spread the load across the two cards.&lt;BR /&gt;(instead of FC1-FC2-FC1-FC2, which has&lt;BR /&gt;all the load on one card, unless a failure&lt;BR /&gt;occurs).&lt;BR /&gt;&lt;BR /&gt;    If it is a busy system and your disk loads&lt;BR /&gt;are estimated to increase , then this&lt;BR /&gt;is a worthwhile process. Otherwise, it may&lt;BR /&gt;not be worth the pain. You can do the&lt;BR /&gt;FC1-FC2-FC2-FC1, even with the current setup&lt;BR /&gt;and improve the channel distribution.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;raj</description>
      <pubDate>Thu, 25 Oct 2001 10:49:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600256#M648163</guid>
      <dc:creator>Roger Baptiste</dc:creator>
      <dc:date>2001-10-25T10:49:29Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a fibre channel card - LVM Implications</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600257#M648164</link>
      <description>Hello Denise,&lt;BR /&gt;&lt;BR /&gt;I do not see the reason for "vgimport" and "vgexport" at all!&lt;BR /&gt;Since good ol' LVM does NOT do load balancing (have I missed something here?) it ONLY uses the "primary" PV link.&lt;BR /&gt;Hence all you have to do is to "vgreduce" the PV links of the FCcard you want to move, then move it, then "vgextend" the new paths to the volume group.&lt;BR /&gt;That's it.&lt;BR /&gt;Just my $0.02,&lt;BR /&gt;Wodisch&lt;BR /&gt;PS: We are talking LVM here, not VxLM, right?&lt;BR /&gt;</description>
      <pubDate>Thu, 25 Oct 2001 13:52:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600257#M648164</guid>
      <dc:creator>Wodisch</dc:creator>
      <dc:date>2001-10-25T13:52:10Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a fibre channel card - LVM Implications</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600258#M648165</link>
      <description>Thanks all. yes it is LVM - I understand that LVM does not load balance but at least we are splitting the traffic across controllers by using the pri/alt alt/pri routine. I am taking the old SCSI disks off this weekend and re-arranging the cards next. Keep your fingers crossed and thanks again;-)&lt;BR /&gt;&lt;BR /&gt;(Dave, btw, working for Denise.)</description>
      <pubDate>Wed, 31 Oct 2001 09:58:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600258#M648165</guid>
      <dc:creator>Denise Doyle</dc:creator>
      <dc:date>2001-10-31T09:58:00Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a fibre channel card - LVM Implications</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600259#M648166</link>
      <description>Hi (again) Denise, Dave &amp;amp; Wodisch:&lt;BR /&gt;&lt;BR /&gt;If the hardware paths (and hence device files) are changing, then, obviously the 'vgexport/vgimprt' method is in order.  The primary and alternate links can easily be defined at that time in one-stroke.&lt;BR /&gt;&lt;BR /&gt;In cases where one merely wishes to switch primary and alternate links to achieve load balancing between two channels, then Wodisch is absolutely correct, too.  Simply 'vgreduce' the primary link(s) thereby causing the alternate to become the primary and follow that with a 'vgextend' of the original primaray link as the new alternate.&lt;BR /&gt;&lt;BR /&gt;In situations where either method would work, the biggest downside of the export/import is the need to unmount filesystems associated with the volume groups.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Wed, 31 Oct 2001 12:24:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/moving-a-fibre-channel-card-lvm-implications/m-p/2600259#M648166</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-10-31T12:24:49Z</dc:date>
    </item>
  </channel>
</rss>

