<?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: monitor an MSA 1000 in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405601#M65173</link>
    <description>As far as I can tell, concerning the MSA1000, OpenVMS is a third-class citizen meaning there is nothing provided.&lt;BR /&gt;&lt;BR /&gt;You might receive the usual SCSI data into the error log, but I am not aware if there is a bit-to-text translator for the MSA.&lt;BR /&gt;&lt;BR /&gt;You can watch the controllers through the CLI interface at the front and there is a program (SYS$ETC:MSA_UTIL.EXE) that can query a controller. Unfortunately the output from the controller CLI and MSA_UTIL is quite different - try it, you will see what I mean.&lt;BR /&gt;</description>
    <pubDate>Fri, 22 Oct 2004 03:06:53 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2004-10-22T03:06:53Z</dc:date>
    <item>
      <title>monitor an MSA 1000</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405600#M65172</link>
      <description>Hello&lt;BR /&gt;&lt;BR /&gt;Vms 7.3-2, DS25 and MSA 1000.&lt;BR /&gt;&lt;BR /&gt;I would like to know how I can monitor the disks of the MSA 1000, in order to know if some disks have failed.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Gerard</description>
      <pubDate>Fri, 22 Oct 2004 02:38:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405600#M65172</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2004-10-22T02:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: monitor an MSA 1000</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405601#M65173</link>
      <description>As far as I can tell, concerning the MSA1000, OpenVMS is a third-class citizen meaning there is nothing provided.&lt;BR /&gt;&lt;BR /&gt;You might receive the usual SCSI data into the error log, but I am not aware if there is a bit-to-text translator for the MSA.&lt;BR /&gt;&lt;BR /&gt;You can watch the controllers through the CLI interface at the front and there is a program (SYS$ETC:MSA_UTIL.EXE) that can query a controller. Unfortunately the output from the controller CLI and MSA_UTIL is quite different - try it, you will see what I mean.&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Oct 2004 03:06:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405601#M65173</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-10-22T03:06:53Z</dc:date>
    </item>
    <item>
      <title>Re: monitor an MSA 1000</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405602#M65174</link>
      <description>MSA1000 errors will be written to the OpenVMS errorlog. That mean that tools like webes reading the errorlog will report the error.</description>
      <pubDate>Fri, 22 Oct 2004 07:07:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405602#M65174</guid>
      <dc:creator>Åge Rønning</dc:creator>
      <dc:date>2004-10-22T07:07:05Z</dc:date>
    </item>
    <item>
      <title>Re: monitor an MSA 1000</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405603#M65175</link>
      <description>You can write a tool that connects to the MSA1000 over the console port (e.g. via a console server) and lists the status with the "show units" command at regular intervals. &lt;BR /&gt;&lt;BR /&gt;I prefer the CLI over MSA_UTIL, since it provides progress information about the  mirroring, and it also is more clear on which disk is being replaced by the spare disk.&lt;BR /&gt;</description>
      <pubDate>Mon, 25 Oct 2004 01:37:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405603#M65175</guid>
      <dc:creator>Peter Hofman</dc:creator>
      <dc:date>2004-10-25T01:37:53Z</dc:date>
    </item>
    <item>
      <title>Re: monitor an MSA 1000</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405604#M65176</link>
      <description>I don't know if this works on a msa1000 but I use "set ho /scsi dev show failed" where dev is a disk name. You need hszterm$scsipad.exe to be able to use it (unsupported).&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Mon, 25 Oct 2004 02:30:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405604#M65176</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-10-25T02:30:11Z</dc:date>
    </item>
    <item>
      <title>Re: monitor an MSA 1000</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405605#M65177</link>
      <description>Please be *VERY* careful when trying HSZTERM -  you can send your HSG 'into space' (make it hang).</description>
      <pubDate>Mon, 25 Oct 2004 02:35:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405605#M65177</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-10-25T02:35:21Z</dc:date>
    </item>
    <item>
      <title>Re: monitor an MSA 1000</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405606#M65178</link>
      <description>Uwe,&lt;BR /&gt;&lt;BR /&gt;When is is giving problems ? I dayly use set ho/scsi several times per day without problems (towards hsg80).&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Mon, 25 Oct 2004 06:46:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405606#M65178</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-10-25T06:46:19Z</dc:date>
    </item>
    <item>
      <title>Re: monitor an MSA 1000</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405607#M65179</link>
      <description>HSZTERM does not lock the controller against other agents (SWCC, SMA). The controller can also become confused when it is fed commands via HSZTERM and the maintenance port.&lt;BR /&gt;&lt;BR /&gt;If you are running ACS V8.7-7, I suggest you read the customer advisory embedded in the following archive:&lt;BR /&gt;&lt;A href="ftp://ftp.compaq.com/pub/products/storageworks/acs/HSG80_V87F-7.zip" target="_blank"&gt;ftp://ftp.compaq.com/pub/products/storageworks/acs/HSG80_V87F-7.zip&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;While this only talks about the ability to process commands we have customers who were able to completely freeze their controllers.</description>
      <pubDate>Mon, 25 Oct 2004 06:56:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405607#M65179</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-10-25T06:56:41Z</dc:date>
    </item>
    <item>
      <title>Re: monitor an MSA 1000</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405608#M65180</link>
      <description>This bank doesn't allow to open zips.&lt;BR /&gt;&lt;BR /&gt;I tested it several times on a dual hsg80. The commands are serialized (v86f-13).&lt;BR /&gt;&lt;BR /&gt;May be it can be used but test it first.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Mon, 25 Oct 2004 08:06:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/monitor-an-msa-1000/m-p/3405608#M65180</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-10-25T08:06:29Z</dc:date>
    </item>
  </channel>
</rss>

