<?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: VA7400 Controller replacement in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/va7400-controller-replacement/m-p/4146376#M26189</link>
    <description>Thanks! I read the document and I am going to give it another shot tonight. I will report tomorrow.</description>
    <pubDate>Tue, 19 Feb 2008 17:28:21 GMT</pubDate>
    <dc:creator>Lawrence Kaufman</dc:creator>
    <dc:date>2008-02-19T17:28:21Z</dc:date>
    <item>
      <title>VA7400 Controller replacement</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7400-controller-replacement/m-p/4146372#M26185</link>
      <description>My ongoing project has been setting up two VA7400 disk arrays in a SAN. I submitted a couple of questions in the past few weeks and you guys put me on the right track- Thanks all. However, my latest issue is that I had a bad controller. The HP CE replaced it...and it seemed to work OK. However, the N_port ID/WWN for that new controller is different and it created new device files. Now, I have to export and import VGs again. The CE told me that if I did not have a fibre switch it would have retained the same instance number on the device files. &lt;BR /&gt; My question is: Is there an easier way to replace a VA controller in a SAN environment?</description>
      <pubDate>Mon, 18 Feb 2008 01:56:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7400-controller-replacement/m-p/4146372#M26185</guid>
      <dc:creator>Lawrence Kaufman</dc:creator>
      <dc:date>2008-02-18T01:56:46Z</dc:date>
    </item>
    <item>
      <title>Re: VA7400 Controller replacement</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7400-controller-replacement/m-p/4146373#M26186</link>
      <description>If you exchange a controller this part will have a new WWN, but the device files for all the LUNs should not change.&lt;BR /&gt;&lt;BR /&gt;Because of the changed WWN the "fcmsutil ... replace_dsk ..." command or a server reboot is needed to make the new controller accessible.&lt;BR /&gt;&lt;BR /&gt;You wiull see related messages in your syslog file.</description>
      <pubDate>Mon, 18 Feb 2008 13:22:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7400-controller-replacement/m-p/4146373#M26186</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-02-18T13:22:17Z</dc:date>
    </item>
    <item>
      <title>Re: VA7400 Controller replacement</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7400-controller-replacement/m-p/4146374#M26187</link>
      <description>I tried the fcmsutil /dev/tdx replace_dsk command. I did not have any luck. I must have done something wrong. I used the "display all" command to get the N_port ID. The man page was not a lot of help.</description>
      <pubDate>Tue, 19 Feb 2008 16:26:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7400-controller-replacement/m-p/4146374#M26187</guid>
      <dc:creator>Lawrence Kaufman</dc:creator>
      <dc:date>2008-02-19T16:26:39Z</dc:date>
    </item>
    <item>
      <title>Re: VA7400 Controller replacement</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7400-controller-replacement/m-p/4146375#M26188</link>
      <description>Hi Lawrence, &lt;BR /&gt;&lt;BR /&gt;As Torsten says, check your syslog or dmesg for the relevant message and N Port ID. See the attached which i put together a while ago for a colleague.&lt;BR /&gt;&lt;BR /&gt;Please note, for fcmsutil replace_dsk to be the answer to your problem, you should be seeing NO_HW in tdlist / ioscan for the controller. If it has actually changed your device files i think it could be another issue.&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 19 Feb 2008 17:17:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7400-controller-replacement/m-p/4146375#M26188</guid>
      <dc:creator>Crewescontrol</dc:creator>
      <dc:date>2008-02-19T17:17:47Z</dc:date>
    </item>
    <item>
      <title>Re: VA7400 Controller replacement</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7400-controller-replacement/m-p/4146376#M26189</link>
      <description>Thanks! I read the document and I am going to give it another shot tonight. I will report tomorrow.</description>
      <pubDate>Tue, 19 Feb 2008 17:28:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7400-controller-replacement/m-p/4146376#M26189</guid>
      <dc:creator>Lawrence Kaufman</dc:creator>
      <dc:date>2008-02-19T17:28:21Z</dc:date>
    </item>
    <item>
      <title>Re: VA7400 Controller replacement</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7400-controller-replacement/m-p/4146377#M26190</link>
      <description>Be aware "fcmsutil ... replace_dsk" is only needed if a WWN is changed while the nPort ID stays the same and there is no reboot for the server. If you reboot the server, the effect is the same.&lt;BR /&gt;&lt;BR /&gt;this only affects the driver and the device authentication. &lt;BR /&gt;&lt;BR /&gt;Can you confirm you have new device files now?</description>
      <pubDate>Tue, 19 Feb 2008 17:42:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7400-controller-replacement/m-p/4146377#M26190</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-02-19T17:42:27Z</dc:date>
    </item>
  </channel>
</rss>

