- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Re: Reboot of MSCS node causes MSA1500 controller ...
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
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
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-14-2008 10:06 AM
тАО02-14-2008 10:06 AM
Reboot of MSCS node causes MSA1500 controller failover
Has anyone seen anything like this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2008 01:19 AM
тАО02-15-2008 01:19 AM
Re: Reboot of MSCS node causes MSA1500 controller failover
When using an active/passive array-controller configuration it could be one of the hosts uses controler-1 and the other controller-2.
If you have multiple connections from the host to the controller, you can try switching the two connections, so both hosts use controler-1 at boottime.
It could be the application in use is not cluster-aware so it tries to access resources that are now active on the other node.
Check your cluster groups and
dependencies of the resources. a misconfiguration here can lead to similar problems.
You need to have a cluster-group with cluster resources (quorum-disk, clustername, cluster-adres) and one ore more application groups.
An application should only use resources in its own group, so not(!) the quorum disk and don't(!) use the clustername or adres to share an application . Instead create aditional names/adresses in the respective application group.
Another cause can be that one of the volums on the array is not configured as a cluster-resource. so it cannot be shared.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2008 05:22 AM
тАО02-15-2008 05:22 AM
Re: Reboot of MSCS node causes MSA1500 controller failover
You should also be using the ACU's SSP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2008 05:25 AM
тАО02-15-2008 05:25 AM
Re: Reboot of MSCS node causes MSA1500 controller failover
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2008 09:38 AM
тАО02-24-2008 09:38 AM
Re: Reboot of MSCS node causes MSA1500 controller failover
Please upload "show tech_support" logs.