<?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: Disk Numbering Changes - Reboot required ? in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/disk-numbering-changes-reboot-required/m-p/3658060#M72188</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;you can set the old devices&lt;BR /&gt;&lt;BR /&gt;$SET DEVICE/NOERROR/NOAVAIL&lt;BR /&gt;&lt;BR /&gt;to disable error loging and availability.&lt;BR /&gt;&lt;BR /&gt;Mike</description>
    <pubDate>Wed, 26 Oct 2005 14:42:25 GMT</pubDate>
    <dc:creator>Mike Reznak</dc:creator>
    <dc:date>2005-10-26T14:42:25Z</dc:date>
    <item>
      <title>Disk Numbering Changes - Reboot required ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-numbering-changes-reboot-required/m-p/3658056#M72184</link>
      <description>One for the panel.&lt;BR /&gt;&lt;BR /&gt;Example Case.&lt;BR /&gt;I have a shadow set as follows:&lt;BR /&gt;&lt;BR /&gt;DSA1 = DGA100 + DGA300 + DGA400&lt;BR /&gt;The disk are HSG80 based disk.&lt;BR /&gt;I need to change the disk id for DGA300.&lt;BR /&gt;From DGA300 to DGA800.&lt;BR /&gt; &lt;BR /&gt;1) Connect to OpenVMS (sign into System account).&lt;BR /&gt;$DISMOUNT $1$DGA400:/CLUSTER&lt;BR /&gt;Check removed from shadow set&lt;BR /&gt;$SHOW DEV DSA1&lt;BR /&gt;&lt;BR /&gt;2) On HSG80&lt;BR /&gt;Find disk id (In this case say D100).&lt;BR /&gt;HSG&amp;gt;SHOW D100&lt;BR /&gt;HSG&amp;gt;SET D100 ID=800&lt;BR /&gt;HSG&amp;gt;SHOW D100&lt;BR /&gt;&lt;BR /&gt;3) On OpenVMS.&lt;BR /&gt;From each node in cluster.&lt;BR /&gt;$MC SYSMAN IO AUTO&lt;BR /&gt;$SHOW DEV DGA800&lt;BR /&gt;&lt;BR /&gt;4) Add back into shadow set ...&lt;BR /&gt;$MOUNT DSA1:/SYS/CLUSTER/CONFIRM/SHAD=$1$DGA800: label&lt;BR /&gt;&lt;BR /&gt;....edit script files that reference disk..mountdisk etc..etc... &lt;BR /&gt;&lt;BR /&gt;Will OpenVMS configure disk with a new id after the sysman io auto.&lt;BR /&gt;The disk already has a data structure under the old ID (DGA400). Will I get new one for the disk known as DGA800 ?&lt;BR /&gt;&lt;BR /&gt;Or is it reboot time ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 26 Oct 2005 07:56:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-numbering-changes-reboot-required/m-p/3658056#M72184</guid>
      <dc:creator>VMS Support</dc:creator>
      <dc:date>2005-10-26T07:56:29Z</dc:date>
    </item>
    <item>
      <title>Re: Disk Numbering Changes - Reboot required ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-numbering-changes-reboot-required/m-p/3658057#M72185</link>
      <description>I would do a reboot to create a fresh I/O database in memory - there is more going on behind the scene than just management of the unit identifier.</description>
      <pubDate>Wed, 26 Oct 2005 08:07:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-numbering-changes-reboot-required/m-p/3658057#M72185</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-10-26T08:07:43Z</dc:date>
    </item>
    <item>
      <title>Re: Disk Numbering Changes - Reboot required ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-numbering-changes-reboot-required/m-p/3658058#M72186</link>
      <description>Well,&lt;BR /&gt;&lt;BR /&gt;I think a reboot sometime convenient would be cleaner, but AFAIK no need to hurry.&lt;BR /&gt;And the reboot may be executed as a 'rolling reboot'.&lt;BR /&gt;The ONE thing you definitely have to make REAL sure of, is NOT to re-use the old ID (DGA400) for another drive until ALL nodes of the cluster have rebooted!&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Wed, 26 Oct 2005 08:37:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-numbering-changes-reboot-required/m-p/3658058#M72186</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-10-26T08:37:38Z</dc:date>
    </item>
    <item>
      <title>Re: Disk Numbering Changes - Reboot required ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-numbering-changes-reboot-required/m-p/3658059#M72187</link>
      <description>&lt;BR /&gt;After you change the ID for each node in the cluster you can delete the old path and reconfigure the new device.  &lt;BR /&gt;&lt;BR /&gt;$ MCR SYSMAN IO SCSI_PATH_VERIFY&lt;BR /&gt;$ MCR SYSMAN IO AUTOCONFIGURE&lt;BR /&gt;&lt;BR /&gt;No need for a reboot, after all this is VMS.&lt;BR /&gt;&lt;BR /&gt;Andy&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 26 Oct 2005 11:20:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-numbering-changes-reboot-required/m-p/3658059#M72187</guid>
      <dc:creator>Andy Bustamante</dc:creator>
      <dc:date>2005-10-26T11:20:30Z</dc:date>
    </item>
    <item>
      <title>Re: Disk Numbering Changes - Reboot required ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-numbering-changes-reboot-required/m-p/3658060#M72188</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;you can set the old devices&lt;BR /&gt;&lt;BR /&gt;$SET DEVICE/NOERROR/NOAVAIL&lt;BR /&gt;&lt;BR /&gt;to disable error loging and availability.&lt;BR /&gt;&lt;BR /&gt;Mike</description>
      <pubDate>Wed, 26 Oct 2005 14:42:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-numbering-changes-reboot-required/m-p/3658060#M72188</guid>
      <dc:creator>Mike Reznak</dc:creator>
      <dc:date>2005-10-26T14:42:25Z</dc:date>
    </item>
  </channel>
</rss>

