<?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: VA7410 and hostname in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/va7410-and-hostname/m-p/3181345#M10987</link>
    <description>find / -exec grep -l -i 'hostname' {} \;&lt;BR /&gt;&lt;BR /&gt;This will identify every config file that has the old hostname. You will need to change them after figureing out the impact.&lt;BR /&gt;&lt;BR /&gt;Afterwards a system restart is a good idea.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Tue, 03 Feb 2004 09:51:27 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2004-02-03T09:51:27Z</dc:date>
    <item>
      <title>VA7410 and hostname</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7410-and-hostname/m-p/3181344#M10986</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;we have installed an rp7410 attached to a VA7410. We installed CVSDM: everything worked fine until we changed the hostname.&lt;BR /&gt;Armdiscover shows old hostname and there's some problem in managing the array (e.g. dual path is not available).&lt;BR /&gt;We removed and reinstalled CVSDM, hoping this worked, but we were not lucky at all.&lt;BR /&gt;&lt;BR /&gt;Do you have any suggestions?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Alessio</description>
      <pubDate>Tue, 03 Feb 2004 09:42:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7410-and-hostname/m-p/3181344#M10986</guid>
      <dc:creator>Alessio_3</dc:creator>
      <dc:date>2004-02-03T09:42:49Z</dc:date>
    </item>
    <item>
      <title>Re: VA7410 and hostname</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7410-and-hostname/m-p/3181345#M10987</link>
      <description>find / -exec grep -l -i 'hostname' {} \;&lt;BR /&gt;&lt;BR /&gt;This will identify every config file that has the old hostname. You will need to change them after figureing out the impact.&lt;BR /&gt;&lt;BR /&gt;Afterwards a system restart is a good idea.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 03 Feb 2004 09:51:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7410-and-hostname/m-p/3181345#M10987</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-02-03T09:51:27Z</dc:date>
    </item>
    <item>
      <title>Re: VA7410 and hostname</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7410-and-hostname/m-p/3181346#M10988</link>
      <description>Hi Allesio,&lt;BR /&gt;&lt;BR /&gt;If you have change the hostname properly, with "set_params".&lt;BR /&gt;You could try the following procedure to manage your array with new hostname.&lt;BR /&gt;&lt;BR /&gt;1- Stop the daemon responsible of array management&lt;BR /&gt;&lt;BR /&gt;# /opt/sanmgr/commandview/server/sbin/HA_Dial_Stop&lt;BR /&gt;&lt;BR /&gt;2 - Restart the daemons&lt;BR /&gt;&lt;BR /&gt;# /opt/sanmgr/commandview/server/sbin/HA_Dial_Start&lt;BR /&gt;&lt;BR /&gt;3 - Run armdiscover&lt;BR /&gt;&lt;BR /&gt;The result must show entrys for both old and new name&lt;BR /&gt;&lt;BR /&gt;4 - Delete the old_hostname from the db&lt;BR /&gt;&lt;BR /&gt;# armdiscover -h "old_hostname" -delete&lt;BR /&gt;&lt;BR /&gt;5 - Re-run armdiscover to see if change taker effect.&lt;BR /&gt;&lt;BR /&gt;Hope this help!&lt;BR /&gt;&lt;BR /&gt;--Vincent&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 04 Feb 2004 04:46:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7410-and-hostname/m-p/3181346#M10988</guid>
      <dc:creator>Vincent Abad</dc:creator>
      <dc:date>2004-02-04T04:46:27Z</dc:date>
    </item>
    <item>
      <title>Re: VA7410 and hostname</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7410-and-hostname/m-p/3181347#M10989</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;we had the same problem and I tried to profit by the given hints.&lt;BR /&gt;I got the SDM working again with the following procedure:&lt;BR /&gt;&lt;BR /&gt;1. the command "set_parms hostname" does not change the configuration of the sanmgr.&lt;BR /&gt;&lt;BR /&gt;2. to search for files containing  &lt;OLD hostname=""&gt; I used the command:&lt;BR /&gt;   find / -type f -exec grep -l -i &lt;OLD_HOSTNAME&gt; {} \;&lt;BR /&gt;   ( wihtout "-type f"  option the find command does not return beause of pipes )&lt;BR /&gt;&lt;BR /&gt;3. change hostname in:&lt;BR /&gt;   /etc/opt/sanmgr/commandview/server/config/PanConfigParams.txt&lt;BR /&gt;   ...&lt;BR /&gt;   EMS_HOST=&lt;NEW_HOSTNAME&gt;&lt;BR /&gt;&lt;BR /&gt;4. restart the management daemons:&lt;BR /&gt;   /opt/sanmgr/commandview/client/sbin/HA_Dial_Stop&lt;BR /&gt;   /opt/sanmgr/commandview/client/sbin/HA_Dial_Start&lt;BR /&gt;   ( it is not at .../server/... )&lt;BR /&gt;&lt;BR /&gt;5. delete the &lt;OLD_HOSTNAME&gt; from the db&lt;BR /&gt;   armdiscover -h &lt;OLD_HOSTNAME&gt;  -delete&lt;BR /&gt;&lt;BR /&gt;After this procedure the "armdsp" -commands are now working as before. &lt;BR /&gt;&lt;BR /&gt;regards Wolfgang Maier&lt;/OLD_HOSTNAME&gt;&lt;/OLD_HOSTNAME&gt;&lt;/NEW_HOSTNAME&gt;&lt;/OLD_HOSTNAME&gt;&lt;/OLD&gt;</description>
      <pubDate>Thu, 05 Feb 2004 08:56:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7410-and-hostname/m-p/3181347#M10989</guid>
      <dc:creator>Wolfgang Maier</dc:creator>
      <dc:date>2004-02-05T08:56:05Z</dc:date>
    </item>
  </channel>
</rss>

