GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Identify MSA1500cs
Server Management - Systems Insight Manager
1847822
Members
4104
Online
104021
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
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-10-2005 12:37 AM
05-10-2005 12:37 AM
Identify MSA1500cs
Hello,
normally a MSA1500 is managed via the agents. So far so bad. Last weekend a complete bay with 12 SATA HD was disconnected and I got mails from all connected servers about failed harddisks, failed logical and failed physical drives. Certain other mails were also sent (controller error ......) . About 50 mails were sent with errors and the summary about it gave the result that the bay connection was lost.
There is no other way to monitor, but has anybody an idea about creating a task in SIM to identify errors like that? I cannot use the "external......" traps because of other servers with external storage bays.
Greetings
Guido
normally a MSA1500 is managed via the agents. So far so bad. Last weekend a complete bay with 12 SATA HD was disconnected and I got mails from all connected servers about failed harddisks, failed logical and failed physical drives. Certain other mails were also sent (controller error ......) . About 50 mails were sent with errors and the summary about it gave the result that the bay connection was lost.
There is no other way to monitor, but has anybody an idea about creating a task in SIM to identify errors like that? I cannot use the "external......" traps because of other servers with external storage bays.
Greetings
Guido
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2005 01:47 PM
05-15-2005 01:47 PM
Re: Identify MSA1500cs
Hi Guido,
Same thing has happened to me several times. I suggest you log a call with HP support for your MSA issue. There is a firmware upgrade available which may prevent the failure form occuring again. (I've had 5 such failures in as many months)
As for alerting, I am looking into the Event Notifier. There are a number of Storage related alerts there that I am hoping will detect these type of alerts in the future. You need to load this on one, or all of the servers attached.
Dean.
Same thing has happened to me several times. I suggest you log a call with HP support for your MSA issue. There is a firmware upgrade available which may prevent the failure form occuring again. (I've had 5 such failures in as many months)
As for alerting, I am looking into the Event Notifier. There are a number of Storage related alerts there that I am hoping will detect these type of alerts in the future. You need to load this on one, or all of the servers attached.
Dean.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2005 06:40 PM
05-16-2005 06:40 PM
Re: Identify MSA1500cs
Hi Dean,
there is a known bug with older firmware loosing the connection but upgrading the firmware gave no success. The complete scsi environment needed to be changed.
Alerting is still a problem, I want to create tasks that identify the msa-problems as a msa-problem. Must I declare a master server and deny all messages from other attached servers? Is there no simplier way?
Greetings
Guido
there is a known bug with older firmware loosing the connection but upgrading the firmware gave no success. The complete scsi environment needed to be changed.
Alerting is still a problem, I want to create tasks that identify the msa-problems as a msa-problem. Must I declare a master server and deny all messages from other attached servers? Is there no simplier way?
Greetings
Guido
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2005 07:20 PM
05-17-2005 07:20 PM
Re: Identify MSA1500cs
Hmmm. May need to contact that handy HP Presales person to find out.
I suspect that it may not be possible given that the MSA is effectivly a SMART Array on drugs, and uses the same interface as an internal controller.
I suspect that it may not be possible given that the MSA is effectivly a SMART Array on drugs, and uses the same interface as an internal controller.
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