- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- MSL6000 and Windows Server 2003 communication prob...
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
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
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
02-11-2014 09:25 AM
02-11-2014 09:25 AM
MSL6000 and Windows Server 2003 communication problems
Hi Everyone,
I´m having problems with hardware communications between MSL6000 tape drives and my Cell Manager (Wins 2003 x32). I have 2 MSL6000 series as passthru with 8 drives in total. I can discover all drives in Data Protector and in Device manager from Cell Manager, but during a backup the communication is lost with the following message
No cleaning signal of any drive.
Between Cell Manager and MSL6000 exist a HP StorageWorks SAN switch FabricOS 6.1
[Major]
From: BMA@server.domain "DRIVE_SERVER_3" Time: 11/02/2014 08:41:25 a.m.
[
90:51] Tape4:0:1:0C
Cannot write to device (Details unknown.)
[Major]
From: BMA@server.domain "DRIVE_SERVER_3" Time: 11/02/2014 08:41:25 a.m.
[
90:173] REQUEST SENSE call failed. Possible cleanme signal detection failure.
([55] The specified network resource or device is no longer available. )
and then I cannot discover all 8 drives either cell manager and data protector. only 5 drives are discovered
Some idea about this?
thanks in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2014 11:09 AM - edited 02-11-2014 11:09 AM
02-11-2014 11:09 AM - edited 02-11-2014 11:09 AM
Re: MSL6000 and Windows Server 2003 communication problems
I understand you have 2 MSL6060 stacked with 4 drives installed in each box, right?
You have 2 NSR installed in each box, right?
First connect to the SAN switch and check if all 4 NSR are visible.
Then point the browser to each NSR and check if the are functional.
Find out where is inaccessible drives are and tell.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2014 08:36 PM
02-20-2014 08:36 PM
Re: MSL6000 and Windows Server 2003 communication problems
I did some modification within the NSR configuration in one of four cards, because one of them had "auto asigned" configuration and the another ones was as "indexed", so, now all 4 NSR are as indexed with a mapping as follows:
Port Map Display
FC PORT 0 Map: 'Indexed' -------+----+--+--+---+----+----+----+---+-+--+-+---------------------------- | P | P| | | T | S |X R | O |W| O|I| FC- | R | O| T| L | Y | T |F A | F |D| P|D| LUN | O | R| G| U | P | A |E T | S |T| T|P|DEVICE | T | T| T| N | E | T |R E | T |H| S| |DESCRIPTION -------+----+--+--+---+----+----+----+---+-+--+-+---------------------------- 0|SCSI| 0| 3| 0|TAPE| UP | 320| 64|W| 3|Y|HP Ultrium 3-SCSI G65W HU10814CRU 1|SCSI| 1| 4| 0|TAPE| UP | 320| 64|W| 3|Y|HP Ultrium 3-SCSI G65W HU10614UV4 2| AF| 0|--| 2|CTLR| UP | -- | - |-|--|-|HP NS E1200-320 -------+----+--+--+---+----+----+----+---+-+--+-+------------------------------
but now a received errors like:
[Major]
From: BMA@mxnt10201.asefi.mex "DRIVE_MXNT10201-8" Time: 20/02/2014 08:52:12 p.m.
[
90:173] REQUEST SENSE call failed. Possible cleanme signal detection failure.
([1117] The request could not be performed because of an I/O device error. )
[Major]
From: BMA@mxnt10201.asefi.mex "DRIVE_MXNT10201-8" Time: 20/02/2014 09:02:21 p.m.
[
90:51] scsi3:1:3:2C
Cannot write to device (Details unknown.)
[Major]
From: BMA@mxnt10201.asefi.mex "DRIVE_MXNT10201-8" Time: 20/02/2014 09:02:21 p.m.
[
90:159] Apparently SCSI Unit Attention.
All drives are connected properly and all FC cables links well. I did cleaning in all drives and still the problem
any idea about what happens??!!