GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- HSZ80 transparent failover problem
HPE EVA Storage
1847606
Members
5903
Online
110265
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
08-03-2006 05:44 AM
08-03-2006 05:44 AM
HSZ80 transparent failover problem
Greetings,
I'm having an issue with two HSZ80's connected in transparent failover mode. I had an alarm from the HSZ80 which I later assumed to be a controller failure as there were no failedsets. I found that one controller appeared to be accessible but the other was not. The accessible controller had the usual reset LED blinking green, while the other's LED was on solid. A software reset of the hung controller was not possible and a hard reset of the other controller also did not register.
I continued by restarting the working controller. The behaviour I experienced at this time is that both appeared to go through the restart sequence and eventually resulted in an alarm. The strange behaviour is that the controller that was hung came back successfully and the other controller then appeared to hang. I could repeat the process switching which controller appeared to be hung, always generating an alarm. I'm not sure if this is default behaviour caused by something or not.
Eventually I took the controllers out of failover mode. At this point a restart of the active controller would result in the same behaviour (it would become hung, the other active) the only difference when this was done in non failover mode is that there was no alarm associated with the restarts and the 'hung' controller would now accept the restart other from the active controller.
Can anyone help me understand what might be happening here? Both controllers appear to communicate with me via the console cable, but only one at a time. While in failover mode each controller also served up disks to the host, but during the long restart disk access was unavailable. It appears that both controllers are functional, but something is preventing them from functioning together simultaneously and I'm not sure what that would be.
Any input is appreciated.
Thanks,
Mike
I'm having an issue with two HSZ80's connected in transparent failover mode. I had an alarm from the HSZ80 which I later assumed to be a controller failure as there were no failedsets. I found that one controller appeared to be accessible but the other was not. The accessible controller had the usual reset LED blinking green, while the other's LED was on solid. A software reset of the hung controller was not possible and a hard reset of the other controller also did not register.
I continued by restarting the working controller. The behaviour I experienced at this time is that both appeared to go through the restart sequence and eventually resulted in an alarm. The strange behaviour is that the controller that was hung came back successfully and the other controller then appeared to hang. I could repeat the process switching which controller appeared to be hung, always generating an alarm. I'm not sure if this is default behaviour caused by something or not.
Eventually I took the controllers out of failover mode. At this point a restart of the active controller would result in the same behaviour (it would become hung, the other active) the only difference when this was done in non failover mode is that there was no alarm associated with the restarts and the 'hung' controller would now accept the restart other from the active controller.
Can anyone help me understand what might be happening here? Both controllers appear to communicate with me via the console cable, but only one at a time. While in failover mode each controller also served up disks to the host, but during the long restart disk access was unavailable. It appears that both controllers are functional, but something is preventing them from functioning together simultaneously and I'm not sure what that would be.
Any input is appreciated.
Thanks,
Mike
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