- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- MSL6000 and HSG80/Windows 2000 problems.
StoreEver Tape Storage
1756161
Members
3621
Online
108842
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО05-18-2004 07:02 PM
тАО05-18-2004 07:02 PM
MSL6000 and HSG80/Windows 2000 problems.
We have a MSL6000 with an e1200 NSR connected to a HSG80, last week we had a simultaneous IO error on both tape drives in the MSL6000. This IO error was generated whilst backing up our servers using Veritas Backup Exec 9.1 (SAN SSO and library expansion installed). This caused any Windows 2000 SAN connected server to lose it's disks and several of these servers blue screened or became very unresponsive.
After some investigation we are unable to find the root cause of this "crash", anyone seen anything like this before?
After some investigation we are unable to find the root cause of this "crash", anyone seen anything like this before?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-19-2004 11:47 AM
тАО05-19-2004 11:47 AM
Re: MSL6000 and HSG80/Windows 2000 problems.
I would ask someone to have a look at the switch logs, It seems strange that an I/O error from a tape drive cause problems on disks, something may happens on the SAN, and the logs may tell you something
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-21-2004 12:34 AM
тАО10-21-2004 12:34 AM
Re: MSL6000 and HSG80/Windows 2000 problems.
yes, we have had the same issue as described by you, speaking to hp but no resolution as yet. It seems to bed down after a few shutdown and restarts. We have replaced the gbic on the sanswitch where the msl6000 was connected as there were quite a few errors logged on the port. we have also run the fibre channel utility to reset the registry under HKLM > SYSTEM > CURRENTCONTROLSET > SERVICES > CPQKGPSA > PARAMETRS > DEVICE > DRIVE PARAMETERS...
which should be set to...
Enabledpc=1;queuetarget=1;Queuedepth=15;Topology=2;NodeTimeout=10;LinkTimeOut=40;HLinkTimeOut=5;ElsRetryCount=6;SimulateDevice=1;ResetTPRLO=2;EmulexOption=0xAA00;ErrRetryMax=0;
NOTE resetTPRLO=2 should be set.
these settings are for multipath and extended configuration only, this may be different for you.
other recommendations by HP are to upgrade secure path to 4.0b for windows with sp4.
create the LUNS on the san with default MAX_READ_CACHED_TRANFER_SIZE=32 AND
MAX_WRITE_CACHED_TRANFER_SIZE=32.
make sure the MSL is plugged into port 0 of the sanswitch and therefore persistent bindings can then be removed using lputilnt.
make sure all luns have a preferred_path=(this or other) as when the hsg's a restarted they can be load balanced when started, instead of one controller doing all the work and the other doing none.
which should be set to...
Enabledpc=1;queuetarget=1;Queuedepth=15;Topology=2;NodeTimeout=10;LinkTimeOut=40;HLinkTimeOut=5;ElsRetryCount=6;SimulateDevice=1;ResetTPRLO=2;EmulexOption=0xAA00;ErrRetryMax=0;
NOTE resetTPRLO=2 should be set.
these settings are for multipath and extended configuration only, this may be different for you.
other recommendations by HP are to upgrade secure path to 4.0b for windows with sp4.
create the LUNS on the san with default MAX_READ_CACHED_TRANFER_SIZE=32 AND
MAX_WRITE_CACHED_TRANFER_SIZE=32.
make sure the MSL is plugged into port 0 of the sanswitch and therefore persistent bindings can then be removed using lputilnt.
make sure all luns have a preferred_path=(this or other) as when the hsg's a restarted they can be load balanced when started, instead of one controller doing all the work and the other doing none.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP