<?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: Monitoring MSA1000 from OpenVMS - MSA$UTIL questions in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083198#M87794</link>
    <description>The MSA1000 is supposed to log errors into ERRLOG.SYS, but this may depend on the patch level of your OpenVMS system. Make sure you have the most recent FIBRE_SCSI patch installed.&lt;BR /&gt;&lt;BR /&gt;WEBES V4.5.1 (SEA) claims to support Modular SAN Array 1000&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
    <pubDate>Mon, 10 Dec 2007 14:31:09 GMT</pubDate>
    <dc:creator>Volker Halle</dc:creator>
    <dc:date>2007-12-10T14:31:09Z</dc:date>
    <item>
      <title>Monitoring MSA1000 from OpenVMS - MSA$UTIL questions</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083193#M87789</link>
      <description>I need a way to monitor the MSA1000 attached to a vms system 7.3-2.  I looked at the msa_util but can't get past the SET CONTROLLER option.  I don't know what to tell it to user for the controller id.  The name that was manually given to the controller was MSA-RMC but that doesn't work.  I've also tried $1$gga1: and that did not work.   &lt;BR /&gt;&lt;BR /&gt;(1) what controller id does the command want and (2) is there a better way to monitor the MSA from VMS for failures?</description>
      <pubDate>Thu, 06 Dec 2007 17:42:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083193#M87789</guid>
      <dc:creator>Layne Burleson_1</dc:creator>
      <dc:date>2007-12-06T17:42:39Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring MSA1000 from OpenVMS - MSA$UTIL questions</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083194#M87790</link>
      <description>&lt;BR /&gt;Do a $ show dev gg /full to find out which device(s) are your MSA controllers.  You can then use that in MSA_UTIL.&lt;BR /&gt;&lt;BR /&gt;Example:&lt;BR /&gt;&lt;BR /&gt;CLCC&amp;gt; sho dev gg/full&lt;BR /&gt; &lt;BR /&gt;Device $1$GGA101:, device type COMPAQ MSA1000, is online, shareable.&lt;BR /&gt; &lt;BR /&gt;    Error count                    0    Operations completed                 13&lt;BR /&gt;    Owner process                 ""    Owner UIC                      [SYSTEM]&lt;BR /&gt;    Owner process ID        00000000    Dev Prot    S:RWPL,O:RWPL,G:RWPL,W:RWPL&lt;BR /&gt;    Reference count                0    Default buffer size                   0&lt;BR /&gt;    WWID   02000008:5008-05F3-0010-F680&lt;BR /&gt;&lt;BR /&gt;CLCC&amp;gt; run sys$etc:msa_util&lt;BR /&gt;MSA&amp;gt; set controller $1$gga101:&lt;BR /&gt;MSA&amp;gt; show controller&lt;BR /&gt; &lt;BR /&gt;Controller: _$1$GGA101: (DEFAULT)&lt;BR /&gt;   MSA1000          (c) COMPAQ                     P56350DX3PQ08F Software 4.48&lt;BR /&gt;   Controller Identifer: 101&lt;BR /&gt;   NODE_ID = 500805f3-0010f680&lt;BR /&gt;   SCSI_VERSION = SCSI-3&lt;BR /&gt;   Supported Redundancy Mode: Active/Standby&lt;BR /&gt;   Current Redundancy mode: Active/Standby&lt;BR /&gt;   Current Role:            Active&lt;BR /&gt;   Device Port SCSI address 7&lt;BR /&gt;Host Port_1:&lt;BR /&gt;   REPORTED PORT_ID = 500805f3-0010f681&lt;BR /&gt;   PORT_1_TOPOLOGY = Not available to this program&lt;BR /&gt;Cache:&lt;BR /&gt;   256 megabyte read cache   256 megabyte write cache&lt;BR /&gt;   Cache is GOOD, and Cache is enabled.&lt;BR /&gt;   No unflushed data in cache.&lt;BR /&gt;Battery:&lt;BR /&gt;   Battery is fully charged.&lt;BR /&gt;MSA&amp;gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Dec 2007 20:21:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083194#M87790</guid>
      <dc:creator>EdgarZamora</dc:creator>
      <dc:date>2007-12-06T20:21:49Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring MSA1000 from OpenVMS - MSA$UTIL questions</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083195#M87791</link>
      <description>When I do what you suggested, I don't have any gg devices.  Yet, I know the MSA is connected because I can access the data on the drives in the MSA.</description>
      <pubDate>Thu, 06 Dec 2007 21:04:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083195#M87791</guid>
      <dc:creator>Layne Burleson_1</dc:creator>
      <dc:date>2007-12-06T21:04:51Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring MSA1000 from OpenVMS - MSA$UTIL questions</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083196#M87792</link>
      <description>If you don't have a $1$GG device, then your MSA1000 isn't fully configured.  &lt;BR /&gt;&lt;BR /&gt;Tthe command console lun (CCL) or the Storage Array ControSACD, depending on what generation widget) probably needs a UDID.&lt;BR /&gt;&lt;BR /&gt;On some of the fibre channel controllers, it's the command "set this_controller identifier=[identifier]" to get the CCL visible, while the Modular Smart Array (MSA) 1000 and 1500 (MSA1000, MSA1500) series use "set this_controller_id [identifier]", where the identifier is a numeric value unique to each controller; each controller gets its own value.  Try configuring that, and see if the $1$GGA (GG; console) device pops into existence on next controller and OpenVMS boot.&lt;BR /&gt;&lt;BR /&gt;The documentation in this area is weak, at best, and I don't have an MSA1000 handy to check.  This is from memory.&lt;BR /&gt;&lt;BR /&gt;Stephen Hoffman&lt;BR /&gt;HoffmanLabs LLC&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Dec 2007 22:59:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083196#M87792</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2007-12-06T22:59:30Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring MSA1000 from OpenVMS - MSA$UTIL questions</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083197#M87793</link>
      <description>thanks, Hoff.  That got my GG devices to show.  It was documented that it had to be numeric for OpenVMS... I put it in my notes but obviously overlooked it at configuration time.&lt;BR /&gt;&lt;BR /&gt;Any ideas how I can monitor for errors on the MSA1000?  With the Smart Arrays, I could use WBEM and some home grown tools to look over the error log.</description>
      <pubDate>Mon, 10 Dec 2007 14:11:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083197#M87793</guid>
      <dc:creator>Layne Burleson_1</dc:creator>
      <dc:date>2007-12-10T14:11:14Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring MSA1000 from OpenVMS - MSA$UTIL questions</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083198#M87794</link>
      <description>The MSA1000 is supposed to log errors into ERRLOG.SYS, but this may depend on the patch level of your OpenVMS system. Make sure you have the most recent FIBRE_SCSI patch installed.&lt;BR /&gt;&lt;BR /&gt;WEBES V4.5.1 (SEA) claims to support Modular SAN Array 1000&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Mon, 10 Dec 2007 14:31:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083198#M87794</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2007-12-10T14:31:09Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring MSA1000 from OpenVMS - MSA$UTIL questions</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083199#M87795</link>
      <description>Thanks to everyone for their input.... once I get monitoring up and running I'll try to post my results for the record.</description>
      <pubDate>Wed, 02 Jan 2008 18:33:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083199#M87795</guid>
      <dc:creator>Layne Burleson_1</dc:creator>
      <dc:date>2008-01-02T18:33:24Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring MSA1000 from OpenVMS - MSA$UTIL questions</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083200#M87796</link>
      <description>I'm closing this thread for now until I get a chance to try out WBEM and see what statistics I call pull from the MSA.  Thanks again.</description>
      <pubDate>Wed, 02 Jan 2008 18:54:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitoring-msa1000-from-openvms-msa-util-questions/m-p/5083200#M87796</guid>
      <dc:creator>Layne Burleson_1</dc:creator>
      <dc:date>2008-01-02T18:54:51Z</dc:date>
    </item>
  </channel>
</rss>

