<?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: EVA configuration in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509224#M67554</link>
    <description>Can you show me the document number and page?&lt;BR /&gt;&lt;BR /&gt;I have never set an identifier for the EVA's LUN 0 - in fact, I have never seen a way to do that.&lt;BR /&gt;&lt;BR /&gt;It was a requirement in early versions of OpenVMS (before EVA was introduced), but as far as I can tell, this is no longer the case - even on HSG-based storage arrays.</description>
    <pubDate>Tue, 22 Mar 2005 13:39:08 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2005-03-22T13:39:08Z</dc:date>
    <item>
      <title>EVA configuration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509223#M67553</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;In the intallation guide for EVA they state that it's very important to set the console LUN id to number other than zero.&lt;BR /&gt;&lt;BR /&gt;Can any one tell me why it should be set to none zero value?&lt;BR /&gt;&lt;BR /&gt;Regards, Torfi.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 22 Mar 2005 04:22:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509223#M67553</guid>
      <dc:creator>Torfi Olafur Sverrisson_1</dc:creator>
      <dc:date>2005-03-22T04:22:59Z</dc:date>
    </item>
    <item>
      <title>Re: EVA configuration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509224#M67554</link>
      <description>Can you show me the document number and page?&lt;BR /&gt;&lt;BR /&gt;I have never set an identifier for the EVA's LUN 0 - in fact, I have never seen a way to do that.&lt;BR /&gt;&lt;BR /&gt;It was a requirement in early versions of OpenVMS (before EVA was introduced), but as far as I can tell, this is no longer the case - even on HSG-based storage arrays.</description>
      <pubDate>Tue, 22 Mar 2005 13:39:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509224#M67554</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-03-22T13:39:08Z</dc:date>
    </item>
    <item>
      <title>Re: EVA configuration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509225#M67555</link>
      <description>It's in initialized system properties - you set the console LUN ID. This sets the lun of the GGA device for the controller pair. If you are using command scripter with HSG80s you actually use this device, so if you don't set it you will probably have problems if you have multiple controller pairs.</description>
      <pubDate>Tue, 22 Mar 2005 18:49:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509225#M67555</guid>
      <dc:creator>Tom O'Toole</dc:creator>
      <dc:date>2005-03-22T18:49:15Z</dc:date>
    </item>
    <item>
      <title>Re: EVA configuration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509226#M67556</link>
      <description>Uwe Zessin: The information comes from HP StorageWorks OpenVMS Kit for Enterprise Virtual Array (Installation and Reference Guide) page 17.&lt;BR /&gt; &lt;BR /&gt;Tom O'Toole: What I do not quit understand is the need for setting another number than zero.  We have EVA 5000 boxes so they are installed with the HSV110 controller type and I donâ  t think that we are going to have any command script accessing/managing the boxes and therefore why should we need to change the default setting.  As I understand the default of zero means that the console isnâ  t presented to the OS.  So if we arenâ  t going to do any direct management from the VMS side what's the need for changing this or am I missing something here?&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Mar 2005 06:26:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509226#M67556</guid>
      <dc:creator>Torfi Olafur Sverrisson_1</dc:creator>
      <dc:date>2005-03-23T06:26:51Z</dc:date>
    </item>
    <item>
      <title>Re: EVA configuration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509227#M67557</link>
      <description>Tom sorry for some bad charaters in between, but here is the text again:&lt;BR /&gt; &lt;BR /&gt;What I do not quit understand is the need for setting another number than zero.  We have EVA 5000 boxes so they are installed with the HSV110 controller type and I do not think that we are going to have any command script accessing/managing the boxes and therefore why should we need to change the default setting.  As I understand the default of zero means that the console is not presented to the OS.  So if we are not going to do any direct management from the VMS side what's the need for changing this or am I missing something here?</description>
      <pubDate>Wed, 23 Mar 2005 06:29:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509227#M67557</guid>
      <dc:creator>Torfi Olafur Sverrisson_1</dc:creator>
      <dc:date>2005-03-23T06:29:57Z</dc:date>
    </item>
    <item>
      <title>Re: EVA configuration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509228#M67558</link>
      <description>Yes, realized my error as already written here:&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=840631" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=840631&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Again, sorry for that.&lt;BR /&gt;&lt;BR /&gt;The LUN #0 (sometimes called the CCL), by the way, will always be presented by the EVA no matter if you set a 'unit identifier' or not. In case of 0, OpenVMS will not configure a $1$GGA device.&lt;BR /&gt;&lt;BR /&gt;Now, the manual you quoted clearly contradicts with the OpenVMS documentation (I'm not complaining about you, OK?):&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/732FINAL/6318/6318pro_012.html#index_x_443" target="_blank"&gt;http://h71000.www7.hp.com/doc/732FINAL/6318/6318pro_012.html#index_x_443&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;""Defining a unique device identifier for the Command Console LUN (CCL) of the HSG and HSV is not required by OpenVMS, but it may be required by some management tools.""&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;It took a bit to find it - the search for "CCL" did not come up with a reference to this page. It would be very nice, if OpenVMS had a working search engine :-(</description>
      <pubDate>Wed, 23 Mar 2005 15:57:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509228#M67558</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-03-23T15:57:30Z</dc:date>
    </item>
    <item>
      <title>Re: EVA configuration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509229#M67559</link>
      <description>"It would be very nice, if OpenVMS had a working search engine :-("&lt;BR /&gt;It could have - remember altavista ? &lt;BR /&gt;I usually use google and specify site as hp.com&lt;BR /&gt;to search for VMS related material.</description>
      <pubDate>Thu, 24 Mar 2005 13:26:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509229#M67559</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-03-24T13:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: EVA configuration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509230#M67560</link>
      <description>Hi guys&lt;BR /&gt;&lt;BR /&gt;Thank you for your greate input.  I appreciate it.&lt;BR /&gt;&lt;BR /&gt;Torfi.</description>
      <pubDate>Thu, 24 Mar 2005 16:28:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509230#M67560</guid>
      <dc:creator>Torfi Olafur Sverrisson_1</dc:creator>
      <dc:date>2005-03-24T16:28:08Z</dc:date>
    </item>
    <item>
      <title>Re: EVA configuration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509231#M67561</link>
      <description>right, for eva you definitely don't need to present the console lun. I suppose you could write some programs that would speak to that device, but considering it's totally undocumented, and considered 'don't mess with' by HP, it wouldn't be a good idea outside of a totally play environment.</description>
      <pubDate>Thu, 24 Mar 2005 19:20:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509231#M67561</guid>
      <dc:creator>Tom O'Toole</dc:creator>
      <dc:date>2005-03-24T19:20:30Z</dc:date>
    </item>
    <item>
      <title>Re: EVA configuration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509232#M67562</link>
      <description>Nit pick: the 'console LUN' is always presented by the EVA, but OpenVMS will only configure a $1$GGA device when you assign it a 'unit identifier'.</description>
      <pubDate>Fri, 25 Mar 2005 01:20:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509232#M67562</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-03-25T01:20:28Z</dc:date>
    </item>
    <item>
      <title>Re: EVA configuration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509233#M67563</link>
      <description>Just for interest - I experienced a problem during disaster recovery testing where newly recovered disks weren't presented to the operating system for booting, even though we'd been able to build them.  After setting the LUN ID to a non-zero value the disks were then available.</description>
      <pubDate>Tue, 29 Mar 2005 11:47:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509233#M67563</guid>
      <dc:creator>Chris Davis_9</dc:creator>
      <dc:date>2005-03-29T11:47:20Z</dc:date>
    </item>
    <item>
      <title>Re: EVA configuration</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509234#M67564</link>
      <description>Sounds, well, 'interesting'. Can you describe that in more detail and/or do you have a log?</description>
      <pubDate>Tue, 29 Mar 2005 12:55:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/eva-configuration/m-p/3509234#M67564</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-03-29T12:55:30Z</dc:date>
    </item>
  </channel>
</rss>

