<?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 MUX Mess in Servers - General</title>
    <link>https://community.hpe.com/t5/servers-general/mux-mess/m-p/2902842#M1390</link>
    <description>Hi all&lt;BR /&gt; &lt;BR /&gt;Any suggestions as to the root cause of this?...&lt;BR /&gt; &lt;BR /&gt;One of our clients has a very old A1000 A990 which refuses to boot up. &lt;BR /&gt;Error message:  I/O error on LU 1 &lt;BR /&gt;[LU 1 is the terminal, which is on a MUX card.] &lt;BR /&gt; &lt;BR /&gt;He's tried 2 terminals and the only common thing is the MUX Card. &lt;BR /&gt;[HP part # 12040D]&lt;BR /&gt;He then tried another spare Mux [12040B version], &lt;BR /&gt;but when he tried putting this one in it wouldn't even get to the vcp prompt. &lt;BR /&gt;&lt;BR /&gt;He then put the old one back in, &lt;BR /&gt;but the disc will not boot and &lt;BR /&gt;his attempts to load an ARSTR from tape come up with an exec call error?&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;Just a bit more info..&lt;BR /&gt;He gets vcp prompt, &lt;BR /&gt;but when he tries to boot he get loader error 411 which is indicative of HP-IB Problem. &lt;BR /&gt; &lt;BR /&gt;He changed the HP-IB card and cable, but the problem persists. &lt;BR /&gt;&lt;BR /&gt;He tried to boot from tape using the 9144A &lt;BR /&gt;the tape loads and the CI prompt is there, &lt;BR /&gt;but the minute he tries to do something he gets:&lt;BR /&gt;ARSTR aborted at address 16020 reason is RQ RQ = bad or too many exec parameters. &lt;BR /&gt; &lt;BR /&gt;Loading from the DAT unit gives:&lt;BR /&gt;rte_a ready, but no ci prompt and the machine locks up.&lt;BR /&gt; &lt;BR /&gt;Over to you !!&lt;BR /&gt;&lt;BR /&gt;Regards - Mike</description>
    <pubDate>Wed, 12 Feb 2003 15:53:43 GMT</pubDate>
    <dc:creator>Mike Fisher_3</dc:creator>
    <dc:date>2003-02-12T15:53:43Z</dc:date>
    <item>
      <title>MUX Mess</title>
      <link>https://community.hpe.com/t5/servers-general/mux-mess/m-p/2902842#M1390</link>
      <description>Hi all&lt;BR /&gt; &lt;BR /&gt;Any suggestions as to the root cause of this?...&lt;BR /&gt; &lt;BR /&gt;One of our clients has a very old A1000 A990 which refuses to boot up. &lt;BR /&gt;Error message:  I/O error on LU 1 &lt;BR /&gt;[LU 1 is the terminal, which is on a MUX card.] &lt;BR /&gt; &lt;BR /&gt;He's tried 2 terminals and the only common thing is the MUX Card. &lt;BR /&gt;[HP part # 12040D]&lt;BR /&gt;He then tried another spare Mux [12040B version], &lt;BR /&gt;but when he tried putting this one in it wouldn't even get to the vcp prompt. &lt;BR /&gt;&lt;BR /&gt;He then put the old one back in, &lt;BR /&gt;but the disc will not boot and &lt;BR /&gt;his attempts to load an ARSTR from tape come up with an exec call error?&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;Just a bit more info..&lt;BR /&gt;He gets vcp prompt, &lt;BR /&gt;but when he tries to boot he get loader error 411 which is indicative of HP-IB Problem. &lt;BR /&gt; &lt;BR /&gt;He changed the HP-IB card and cable, but the problem persists. &lt;BR /&gt;&lt;BR /&gt;He tried to boot from tape using the 9144A &lt;BR /&gt;the tape loads and the CI prompt is there, &lt;BR /&gt;but the minute he tries to do something he gets:&lt;BR /&gt;ARSTR aborted at address 16020 reason is RQ RQ = bad or too many exec parameters. &lt;BR /&gt; &lt;BR /&gt;Loading from the DAT unit gives:&lt;BR /&gt;rte_a ready, but no ci prompt and the machine locks up.&lt;BR /&gt; &lt;BR /&gt;Over to you !!&lt;BR /&gt;&lt;BR /&gt;Regards - Mike</description>
      <pubDate>Wed, 12 Feb 2003 15:53:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/mux-mess/m-p/2902842#M1390</guid>
      <dc:creator>Mike Fisher_3</dc:creator>
      <dc:date>2003-02-12T15:53:43Z</dc:date>
    </item>
    <item>
      <title>Re: MUX Mess</title>
      <link>https://community.hpe.com/t5/servers-general/mux-mess/m-p/2902843#M1391</link>
      <description>You have posted to a HP-UX, i.e. non-HP1000 Forum. As far as I know, there is no (ITRC) Forum for HP1000 systems.&lt;BR /&gt;&lt;BR /&gt;If you get no other responses, then it is probably best to post to the public Usenet Newsgroup comp.sys.hp.misc. If you have no access to Usenet Newsgroups, you can access them through Google Groups: &lt;A href="http://groups.google.com/groups?group=comp.sys.hp.misc" target="_blank"&gt;http://groups.google.com/groups?group=comp.sys.hp.misc&lt;/A&gt;</description>
      <pubDate>Thu, 13 Feb 2003 11:15:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/mux-mess/m-p/2902843#M1391</guid>
      <dc:creator>Frank Slootweg</dc:creator>
      <dc:date>2003-02-13T11:15:28Z</dc:date>
    </item>
    <item>
      <title>Re: MUX Mess</title>
      <link>https://community.hpe.com/t5/servers-general/mux-mess/m-p/2902844#M1392</link>
      <description>Well it is a LONG time since I worked on an A9xx, but this sounds like you have a more serious error on the hardware.&lt;BR /&gt;I would suggest logging a call with HP, as there may be more than one failure here.</description>
      <pubDate>Thu, 13 Feb 2003 12:45:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/servers-general/mux-mess/m-p/2902844#M1392</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2003-02-13T12:45:21Z</dc:date>
    </item>
  </channel>
</rss>

