GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Reboots on Nodes connetected to MSA1000
HPE EVA Storage
1846618
Members
1433
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
09-09-2003 12:41 PM
09-09-2003 12:41 PM
Reboots on Nodes connetected to MSA1000
Greetings!
Has anyone seen DL580's with Win2000 reboot
when expanding the volume on MSA1000?
We have 2 MSA 1000 in a fabric(all reduandant) with 6 servers (2 Adv server 2000 and 4 Win2000 server )configured with SSP. 2 Adv servers only access MSA1000 -1 using SSP and other 4 Win 2000 servers access the other MSA1000 - 2
All the servers are with Smartstart 6.1 , secure path ver 3.5.0.60, Virtual Replicator ver 3.0 build 176, HBA driver ver 5-4.82a9.
When we expand a drive using ACU xe on MSA1000-1 , any one of the 2 adv server Blue screens and comes back up with ASR bugcheck
Blue Screen Trap (BugCheck, STOP: 0x0000000A (0x39B6F120, 0x00000002, 0x00000001, 0xDD4485B6)). This is random .It happend to the other adv server a while ago when we expanded the drive. the Bug check code was same 0x0000000A . It also happend on the server that has access to MSA1000-2.
Also we noticed that when the rebuild on the hardware level is complete any one of the server reboots with ASR.
All in common here is that When the rebuild is going on on completion occurs the servers get a Status change notifiacation from the server agents and that is the time when one of the server reboots. like this-> (Compaq External Array Logical Drive Status Change. Logical drive number 1 on array "MSA1000-1" has a new status of 12.
(Logical Drive status values: 1=other, 2=ok, 3=failed, 4=unconfigured, 5=recovering, 6=readyForRebuild, 7=rebuilding, 8=wrongDrive, 9=badConnect, 10=overheating, 11=shutdown, 12=expanding, 13=notAvailable, 14=queuedForExpansion)
[SNMP TRAP: 16022 in CPQFCA.MIB]
So we disabled the Compaq agnets on the servers while the rebuild was going on assuming the Status change notification was triggering the reboots., When completed we dint see any reboots..
Any one seen this kind of a bug? we have had randomly ateast 5-6 reboots so far...
We logged a call earlier at Hp and at that time they instructed us to get all the servers/compaq versions up todate which was latest at that time and we did it. But it didn't help.
Can Someone help us out here.
Appreciate your responce !
thanks
Has anyone seen DL580's with Win2000 reboot
when expanding the volume on MSA1000?
We have 2 MSA 1000 in a fabric(all reduandant) with 6 servers (2 Adv server 2000 and 4 Win2000 server )configured with SSP. 2 Adv servers only access MSA1000 -1 using SSP and other 4 Win 2000 servers access the other MSA1000 - 2
All the servers are with Smartstart 6.1 , secure path ver 3.5.0.60, Virtual Replicator ver 3.0 build 176, HBA driver ver 5-4.82a9.
When we expand a drive using ACU xe on MSA1000-1 , any one of the 2 adv server Blue screens and comes back up with ASR bugcheck
Blue Screen Trap (BugCheck, STOP: 0x0000000A (0x39B6F120, 0x00000002, 0x00000001, 0xDD4485B6)). This is random .It happend to the other adv server a while ago when we expanded the drive. the Bug check code was same 0x0000000A . It also happend on the server that has access to MSA1000-2.
Also we noticed that when the rebuild on the hardware level is complete any one of the server reboots with ASR.
All in common here is that When the rebuild is going on on completion occurs the servers get a Status change notifiacation from the server agents and that is the time when one of the server reboots. like this-> (Compaq External Array Logical Drive Status Change. Logical drive number 1 on array "MSA1000-1" has a new status of 12.
(Logical Drive status values: 1=other, 2=ok, 3=failed, 4=unconfigured, 5=recovering, 6=readyForRebuild, 7=rebuilding, 8=wrongDrive, 9=badConnect, 10=overheating, 11=shutdown, 12=expanding, 13=notAvailable, 14=queuedForExpansion)
[SNMP TRAP: 16022 in CPQFCA.MIB]
So we disabled the Compaq agnets on the servers while the rebuild was going on assuming the Status change notification was triggering the reboots., When completed we dint see any reboots..
Any one seen this kind of a bug? we have had randomly ateast 5-6 reboots so far...
We logged a call earlier at Hp and at that time they instructed us to get all the servers/compaq versions up todate which was latest at that time and we did it. But it didn't help.
Can Someone help us out here.
Appreciate your responce !
thanks
Power
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2003 05:53 AM
09-10-2003 05:53 AM
Re: Reboots on Nodes connetected to MSA1000
If you implement zoning on the switches, and thereby seperate each server from one another, allowing each server to see only the MSA1000, then the occurences should only be limited to a particular server and not all the connected hosts.
regards
christian
regards
christian
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