<?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 FTAM error in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ftam-error/m-p/2435262#M768249</link>
    <description>What seems to be our problem? This message appears on our ftam for HP715 workstation running on 10.01 HP-UX.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Abnormal termination.&lt;BR /&gt;Message from host:&lt;BR /&gt;    Responder Error (unspecific)&lt;BR /&gt;    PROTOCOL ERROR: Could not make state transition to "I_TERRQ" from current state "SELECTED" (log_instance:4&lt;BR /&gt;29, FTAM error_id 1007 = "FTAM protocol error (unspecific)")&lt;BR /&gt;</description>
    <pubDate>Tue, 08 Aug 2000 06:59:51 GMT</pubDate>
    <dc:creator>ALLAN NAVARRO</dc:creator>
    <dc:date>2000-08-08T06:59:51Z</dc:date>
    <item>
      <title>FTAM error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftam-error/m-p/2435262#M768249</link>
      <description>What seems to be our problem? This message appears on our ftam for HP715 workstation running on 10.01 HP-UX.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Abnormal termination.&lt;BR /&gt;Message from host:&lt;BR /&gt;    Responder Error (unspecific)&lt;BR /&gt;    PROTOCOL ERROR: Could not make state transition to "I_TERRQ" from current state "SELECTED" (log_instance:4&lt;BR /&gt;29, FTAM error_id 1007 = "FTAM protocol error (unspecific)")&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Aug 2000 06:59:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftam-error/m-p/2435262#M768249</guid>
      <dc:creator>ALLAN NAVARRO</dc:creator>
      <dc:date>2000-08-08T06:59:51Z</dc:date>
    </item>
    <item>
      <title>Re: FTAM error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftam-error/m-p/2435263#M768250</link>
      <description>&lt;BR /&gt;Wow, you must be suffering from the lack of replies! however, I simply cant find any info on your error at all, anywhere, and I work at HP. Not the specific error you have anyway. All the info Ive scoured suggests the only way to fix this is to reboot your workstation.</description>
      <pubDate>Tue, 08 Aug 2000 08:15:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftam-error/m-p/2435263#M768250</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2000-08-08T08:15:41Z</dc:date>
    </item>
    <item>
      <title>Re: FTAM error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftam-error/m-p/2435264#M768251</link>
      <description>Well I couldn't find specific answers to your problems...but I hope I'm not out of line by just rambling on some information...FTAM (File Access Transfer, and Management Protocol) is the utility with the problem. Your error indicates possibly a protocol recognition problem, thus causing the process to time out and 'die'.  Maybe you could run some diagnostic tools that would give you a little more information when the condition occurs again while your running some diag tools.  Here's some info I found on the IT Resource...it may or may not help. But it is a start:&lt;BR /&gt;&lt;BR /&gt;               OTS and FTAM Tracing/Formatting Tools&lt;BR /&gt;&lt;BR /&gt;               The best tool to use is ositrace, which is available from the HP Response&lt;BR /&gt;               Center.  It is not on the product media.  ositrace starts nettl tracing and&lt;BR /&gt;               logging, gives the user a shell to reproduce the problem, and then creates an&lt;BR /&gt;               output file that contains the OTS and FTAM configuration, status, and nettl&lt;BR /&gt;               log/trace information.&lt;BR /&gt;&lt;BR /&gt;               Use ositrace in conjunction with osidiag.  For example, to do OTS Transport&lt;BR /&gt;               tests or FTAM tests.  osidiag is menu driven and fairly easy to use.&lt;BR /&gt;&lt;BR /&gt;               In the absence of ositrace, use other commands such as osidiag and osipdufmt  which often can get you an extremely useful nettl trace of the problem.&lt;BR /&gt;               The OSI Troubleshooting Guide, available from the HP Documentation Website, &lt;A href="http://docs.hp.com," target="_blank"&gt;http://docs.hp.com,&lt;/A&gt; under the Networking/Communications OSI section, contains excellent step by step troubleshooting procedures to follow.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;Regards,</description>
      <pubDate>Tue, 08 Aug 2000 16:47:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftam-error/m-p/2435264#M768251</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2000-08-08T16:47:05Z</dc:date>
    </item>
  </channel>
</rss>

