GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- MSA-1000 v4.24 w/ 2003 and Secure Path 4.0c Proble...
HPE EVA Storage
1846649
Members
2392
Online
110256
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
Forums
Discussions
Discussions
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
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
12-08-2003 02:18 PM
12-08-2003 02:18 PM
MSA-1000 v4.24 w/ 2003 and Secure Path 4.0c Problem
Here's my current configuration:
MSA-1000, two fibre channel ports, two controllers, only one port connected to the 2/16 switch at the moment (firmware 4.24 and 3.1.1, respectively), and Windows Server 2003 Enterprise on a DL360 G2.
Old Config: With secure path 4.0B, and MSA-1000 2.38, all was well. I know having the 2nd fibre port not connected isn't the best configuration, but that's how it currently is.
Problem: Now when the server boots, during the boot process the system mounts the secure path volume, and then it is rudely 'un plugged', Windows complains loudly in the system logs, and then it is re-mounted all before the login screen appears. The effect is that SQL, Exchange, and other programs are quite unhappy with the volume being rudely dismounted (duh). This absolutely never happend with 2.38 and SP 4.0B, and always does with the new config.
I have a second SAN setup, MSA-1000 v4.24, two old Gadzooks built-in switches cascaded to each other, and 2003 hosts with SP 4.0c with single connections to the build in switches. They reboot just find and never once had the error.
So I conclude that 2003 with MSA-1000 4.24, Secure Path 4.0c, and a single connection to a dual controller MSA-1000 storage array has a problem that didn't exist before.
I'll probably end up connecing the 2nd fibre port off the MSA, but our 16 port switch is already full.
The long term answer is of course to get another switch or get the 2/32, but I'd like to get the 4.24/SP4.0c config working like it did with 2.38 and SP4.0B.
MSA-1000, two fibre channel ports, two controllers, only one port connected to the 2/16 switch at the moment (firmware 4.24 and 3.1.1, respectively), and Windows Server 2003 Enterprise on a DL360 G2.
Old Config: With secure path 4.0B, and MSA-1000 2.38, all was well. I know having the 2nd fibre port not connected isn't the best configuration, but that's how it currently is.
Problem: Now when the server boots, during the boot process the system mounts the secure path volume, and then it is rudely 'un plugged', Windows complains loudly in the system logs, and then it is re-mounted all before the login screen appears. The effect is that SQL, Exchange, and other programs are quite unhappy with the volume being rudely dismounted (duh). This absolutely never happend with 2.38 and SP 4.0B, and always does with the new config.
I have a second SAN setup, MSA-1000 v4.24, two old Gadzooks built-in switches cascaded to each other, and 2003 hosts with SP 4.0c with single connections to the build in switches. They reboot just find and never once had the error.
So I conclude that 2003 with MSA-1000 4.24, Secure Path 4.0c, and a single connection to a dual controller MSA-1000 storage array has a problem that didn't exist before.
I'll probably end up connecing the 2nd fibre port off the MSA, but our 16 port switch is already full.
The long term answer is of course to get another switch or get the 2/32, but I'd like to get the 4.24/SP4.0c config working like it did with 2.38 and SP4.0B.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2003 02:29 AM
12-09-2003 02:29 AM
Re: MSA-1000 v4.24 w/ 2003 and Secure Path 4.0c Problem
It's not surprising that you are getting error messages with your config. The MSA1000 is designed to run either ALL single path or ALL dual path. If you have a mix of single and dual components like you do, it would be normal for error messages to occur.
It may be that the 4.0C/4.24FW combination has additional error condition identification code in there that the old combination didn't have.
Bottom line is you should run either all single path or all dual path, but not a mix.
Thanks,
Doug
It may be that the 4.0C/4.24FW combination has additional error condition identification code in there that the old combination didn't have.
Bottom line is you should run either all single path or all dual path, but not a mix.
Thanks,
Doug
I am an HPE employee
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.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP