- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- NSR - Identifying polling hosts
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-06-2009 05:17 AM
тАО11-06-2009 05:17 AM
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.
So viewing NSR trace logs, I see the following snippits, which I believe is one of these machines polling:
0ms 27us PS_DrvSend: Bus:1 Target:2 Lun:0 CDB:x00
0ms 0us SCSI msg out c0000000 cdb 00000000000000000000000000000000
0ms 378us FrmHdr 06040100 00041a00 08290000 06000000 01a0ffff Port 0
0ms 2us FCP_LUN 00010000 00000000 FCP_CNTRL 00000000 FCP_DL 00000000
0ms 0us FCP_CDB 00000000 00000000 00000000 00000000 IOCB 80F3397C
0ms 18us RMI_getPortIdforRoute: routeIndex: x4, Route_Port: x0
0ms 3us fcpTrns_cleanupPersistentCommand: Leaving ....
So my question is, how can one identify which host/s are doing this? They seem to be doing it several times a minute.
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.
All our firmware and drivers are current.
Thanks for any help.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2009 01:05 AM
тАО11-09-2009 01:05 AM
Re: NSR - Identifying polling hosts
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2009 08:14 AM
тАО11-09-2009 08:14 AM
Re: NSR - Identifying polling hosts
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2009 08:38 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-10-2009 03:56 AM
тАО11-10-2009 03:56 AM
Re: NSR - Identifying polling hosts
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.
Anyway, thank you for your assistance.
If anyone else knows if there is a good alternative to hp_rescan on Red Hat, please reply.