<?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: NSR - Identifying polling hosts in StoreEver Tape Storage</title>
    <link>https://community.hpe.com/t5/storeever-tape-storage/nsr-identifying-polling-hosts/m-p/4529236#M24925</link>
    <description>I've attached our NSR report. Thank you for your help.</description>
    <pubDate>Mon, 09 Nov 2009 16:14:06 GMT</pubDate>
    <dc:creator>smw</dc:creator>
    <dc:date>2009-11-09T16:14:06Z</dc:date>
    <item>
      <title>NSR - Identifying polling hosts</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/nsr-identifying-polling-hosts/m-p/4529234#M24923</link>
      <description>We have several servers (primarily Red Hat, but on a couple of occasions HPUX) which cannot see all our tape drives. They can see all of them fine when the servers are first booted up, and can be used perfectly. After a short while (usually a few days) they stop being able to use them/see them via DP. &lt;BR /&gt;&lt;BR /&gt;An HP engineer who was working on another case for us, suggested that he had seen problems before when Windows machines poll SAN devices excessively, causing problems for other systems. &lt;BR /&gt;&lt;BR /&gt;So viewing NSR trace logs, I see the following snippits, which I believe is one of these machines polling:&lt;BR /&gt;&lt;BR /&gt;0ms 27us PS_DrvSend: Bus:1 Target:2 Lun:0 CDB:x00  &lt;BR /&gt;0ms 0us SCSI msg out c0000000 cdb 00000000000000000000000000000000  &lt;BR /&gt;0ms 378us FrmHdr 06040100 00041a00 08290000 06000000 01a0ffff Port 0  &lt;BR /&gt;0ms 2us FCP_LUN 00010000 00000000 FCP_CNTRL 00000000 FCP_DL 00000000  &lt;BR /&gt;0ms 0us FCP_CDB 00000000 00000000 00000000 00000000 IOCB 80F3397C  &lt;BR /&gt;0ms 18us RMI_getPortIdforRoute: routeIndex: x4, Route_Port: x0  &lt;BR /&gt;0ms 3us fcpTrns_cleanupPersistentCommand: Leaving ....  &lt;BR /&gt;&lt;BR /&gt;So my question is, how can one identify which host/s are doing this? They seem to be doing it several times a minute. &lt;BR /&gt;&lt;BR /&gt;Failing this, how can one fully rescan devices within Red Hat, as it does on start up? An hp_rescan has only once managed to reclaim any devices, yet a reboot works each time, but obviously is not desirable.&lt;BR /&gt;&lt;BR /&gt;All our firmware and drivers are current.&lt;BR /&gt; &lt;BR /&gt;Thanks for any help.&lt;BR /&gt;</description>
      <pubDate>Fri, 06 Nov 2009 13:17:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/nsr-identifying-polling-hosts/m-p/4529234#M24923</guid>
      <dc:creator>smw</dc:creator>
      <dc:date>2009-11-06T13:17:12Z</dc:date>
    </item>
    <item>
      <title>Re: NSR - Identifying polling hosts</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/nsr-identifying-polling-hosts/m-p/4529235#M24924</link>
      <description>Can you attach the nsr report in *.mth format?&lt;BR /&gt;</description>
      <pubDate>Mon, 09 Nov 2009 09:05:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/nsr-identifying-polling-hosts/m-p/4529235#M24924</guid>
      <dc:creator>Marino Meloni_1</dc:creator>
      <dc:date>2009-11-09T09:05:02Z</dc:date>
    </item>
    <item>
      <title>Re: NSR - Identifying polling hosts</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/nsr-identifying-polling-hosts/m-p/4529236#M24925</link>
      <description>I've attached our NSR report. Thank you for your help.</description>
      <pubDate>Mon, 09 Nov 2009 16:14:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/nsr-identifying-polling-hosts/m-p/4529236#M24925</guid>
      <dc:creator>smw</dc:creator>
      <dc:date>2009-11-09T16:14:06Z</dc:date>
    </item>
    <item>
      <title>Re: NSR - Identifying polling hosts</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/nsr-identifying-polling-hosts/m-p/4529237#M24926</link>
      <description>seems you have polling going on,&lt;BR /&gt;I hope you can identify it with the attached decoded nsr report</description>
      <pubDate>Mon, 09 Nov 2009 16:38:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/nsr-identifying-polling-hosts/m-p/4529237#M24926</guid>
      <dc:creator>Marino Meloni_1</dc:creator>
      <dc:date>2009-11-09T16:38:03Z</dc:date>
    </item>
    <item>
      <title>Re: NSR - Identifying polling hosts</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/nsr-identifying-polling-hosts/m-p/4529238#M24927</link>
      <description>Thank you for your help. Hopefully we can have a look at what is polling.&lt;BR /&gt;&lt;BR /&gt;Strange thing is we did a DR-test this week and even though none of the problem-servers were failed over or rebooted etc, they can now see all the tape drives. Some of the servers are in the same room as the tape drives they couldn't see, yet by failing the OTHER room over + back again, they now work. It'll be interesting to see if this continues.&lt;BR /&gt;&lt;BR /&gt;Anyway, thank you for your assistance. &lt;BR /&gt;&lt;BR /&gt;If anyone else knows if there is a good alternative to hp_rescan on Red Hat, please reply.&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Nov 2009 11:56:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/nsr-identifying-polling-hosts/m-p/4529238#M24927</guid>
      <dc:creator>smw</dc:creator>
      <dc:date>2009-11-10T11:56:23Z</dc:date>
    </item>
  </channel>
</rss>

