<?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 Bootup Errors Reported In SYSLOG in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/bootup-errors-reported-in-syslog/m-p/3072044#M140940</link>
    <description>The following is reported in syslog&lt;BR /&gt;&lt;BR /&gt;vmunix: SCSI: Ultra160 Controller at 0/10/0/0:&lt;BR /&gt;&lt;BR /&gt;Warning:Data transfer rate stepped down for target 6. Now operating at 20 MB/s (Fast Wide). Possible causes are improper termination, improper cabling, or malfunctioning hardware.&lt;BR /&gt;&lt;BR /&gt;rpcbind: svc_tli_create: t_getname failed; T_IDLE&lt;BR /&gt;rpcbind: svc_dg_create: could not get transport information&lt;BR /&gt;rpcbind: init_transport: Could not create rmtcall fd for ticlts&lt;BR /&gt;&lt;BR /&gt;Do any of you know what the likely cause is or have you seen it before?  Any help on this would be greatly appreciated!!</description>
    <pubDate>Tue, 16 Sep 2003 09:16:37 GMT</pubDate>
    <dc:creator>Managed Services</dc:creator>
    <dc:date>2003-09-16T09:16:37Z</dc:date>
    <item>
      <title>Bootup Errors Reported In SYSLOG</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bootup-errors-reported-in-syslog/m-p/3072044#M140940</link>
      <description>The following is reported in syslog&lt;BR /&gt;&lt;BR /&gt;vmunix: SCSI: Ultra160 Controller at 0/10/0/0:&lt;BR /&gt;&lt;BR /&gt;Warning:Data transfer rate stepped down for target 6. Now operating at 20 MB/s (Fast Wide). Possible causes are improper termination, improper cabling, or malfunctioning hardware.&lt;BR /&gt;&lt;BR /&gt;rpcbind: svc_tli_create: t_getname failed; T_IDLE&lt;BR /&gt;rpcbind: svc_dg_create: could not get transport information&lt;BR /&gt;rpcbind: init_transport: Could not create rmtcall fd for ticlts&lt;BR /&gt;&lt;BR /&gt;Do any of you know what the likely cause is or have you seen it before?  Any help on this would be greatly appreciated!!</description>
      <pubDate>Tue, 16 Sep 2003 09:16:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bootup-errors-reported-in-syslog/m-p/3072044#M140940</guid>
      <dc:creator>Managed Services</dc:creator>
      <dc:date>2003-09-16T09:16:37Z</dc:date>
    </item>
    <item>
      <title>Re: Bootup Errors Reported In SYSLOG</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bootup-errors-reported-in-syslog/m-p/3072045#M140941</link>
      <description>The first one looks like you have a non ultra scsi device plugged into your ultra160 scsi controller. It looks to be a Fast/Wide device (which only runs at 20MB/s). What device is it ? (a tape drive?)&lt;BR /&gt;&lt;BR /&gt;ioscan -fnH 0/10/0/0&lt;BR /&gt;&lt;BR /&gt;will show what device it is. Possibly it should not be plugged into your ultra160 card but into a FWD card instead, or it can stay on your ultra160 card but it wont run at full speed - its limited by the device plugged in to only 20MB/s.&lt;BR /&gt;&lt;BR /&gt;The 2nd error for rpcbind doesnt look like too much to worry about. Do you have the latest rpcbind patch installed first ?&lt;BR /&gt;&lt;BR /&gt;eg. for 11.0;&lt;BR /&gt;  PHNE_28567.NFS-CORE: /usr/sbin/rpcbind&lt;BR /&gt;&lt;BR /&gt;Its part of the NFS General release patch. You can check for the latest in the patch database on the itrc.hp.com&lt;BR /&gt;</description>
      <pubDate>Tue, 16 Sep 2003 09:40:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bootup-errors-reported-in-syslog/m-p/3072045#M140941</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2003-09-16T09:40:05Z</dc:date>
    </item>
    <item>
      <title>Re: Bootup Errors Reported In SYSLOG</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bootup-errors-reported-in-syslog/m-p/3072046#M140942</link>
      <description>Thanks for the quick response on this one.  We've checked the device with ioscan as suggested and this is a tape device (Quantum DLT8000).  The system is rebooted every week and as far as we know this is the first time this has been reported so it's surprising it's only reporting this now.&lt;BR /&gt;&lt;BR /&gt;Nothing has been changed.....</description>
      <pubDate>Tue, 16 Sep 2003 09:55:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bootup-errors-reported-in-syslog/m-p/3072046#M140942</guid>
      <dc:creator>Managed Services</dc:creator>
      <dc:date>2003-09-16T09:55:12Z</dc:date>
    </item>
    <item>
      <title>Re: Bootup Errors Reported In SYSLOG</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bootup-errors-reported-in-syslog/m-p/3072047#M140943</link>
      <description>On all our servers DLT8000's (and 7000's) are plugged into Fast-Wide controllers, NOT ultra scsi controllers;&lt;BR /&gt;&lt;BR /&gt;Class     I  H/W Path     Driver S/W State   H/W Type     Description&lt;BR /&gt;=====================================================================&lt;BR /&gt;ext_bus  22  0/8/0/0      c720  CLAIMED     INTERFACE    SCSI C875 Fast Wide Differential&lt;BR /&gt;target    7  0/8/0/0.1    tgt   CLAIMED     DEVICE       &lt;BR /&gt;tape      2  0/8/0/0.1.0  stape CLAIMED     DEVICE       QUANTUM DLT8000&lt;BR /&gt;&lt;BR /&gt;Class     I  H/W Path      Driver S/W State   H/W Type     Description&lt;BR /&gt;======================================================================&lt;BR /&gt;ext_bus  14  1/12/0/0      c720  CLAIMED     INTERFACE    SCSI C87x Fast Wide Differential&lt;BR /&gt;target   40  1/12/0/0.3    tgt   CLAIMED     DEVICE       &lt;BR /&gt;tape      0  1/12/0/0.3.0  stape CLAIMED     DEVICE       QUANTUM DLT8000&lt;BR /&gt;&lt;BR /&gt;Im not sure if youre even supposed to plug them into an ultra scsi controller as they are LVD and the DLT is HVD - you could blow the bus. This explains your error message, but the question now is should it stay connected or you plug it into a DF card instead. If it works then maybe its ok. Only HP can answer this one I think.&lt;BR /&gt;</description>
      <pubDate>Tue, 16 Sep 2003 10:31:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bootup-errors-reported-in-syslog/m-p/3072047#M140943</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2003-09-16T10:31:25Z</dc:date>
    </item>
    <item>
      <title>Re: Bootup Errors Reported In SYSLOG</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bootup-errors-reported-in-syslog/m-p/3072048#M140944</link>
      <description>Thanks for the help on this one, Stefan.  We'll get in touch with HP and see where we go from there.  Thanks.</description>
      <pubDate>Wed, 17 Sep 2003 10:31:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bootup-errors-reported-in-syslog/m-p/3072048#M140944</guid>
      <dc:creator>Managed Services</dc:creator>
      <dc:date>2003-09-17T10:31:40Z</dc:date>
    </item>
  </channel>
</rss>

