- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- NVSRAM checksum does not match
Disk Enclosures
1752301
Members
4799
Online
108786
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
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
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
10-21-2001 07:47 PM
10-21-2001 07:47 PM
NVSRAM checksum does not match
Hi,
FC60 from command amdsp -c , I found that NVSRAM checksum in controller A and controller B , does not match , does it would be the problem ?
I got EMS message:
Array at hardware path 0/5/0/0.8.0.5.0.0.0, path 0/4/0/0.8.0.4.0.0.0: Both controllers may not have the same RAM image.
There is a loss of NVRAM redundancy.
Associated OS error log entry id(s):
0000000000000000000
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/fc60mon.htm#9
Description of Error:
This event message is displayed when the mirroring hardware is unable
to keep the two RAM images synchronized across the two controllers.
Probable Cause / Recommended Action:
Investigate the hardware log and use other warning conditions as a
guide to the problem. You may need to replace the controller.
Possible Causes Include:
1. A controller has failed, but no obvious failure mode is evident.
2. A controller is not communicating at all.
---------------
I check all Hardware error log , using mstm , logtool , but no error reported and array can working as normal.
FC60 from command amdsp -c , I found that NVSRAM checksum in controller A and controller B , does not match , does it would be the problem ?
I got EMS message:
Array at hardware path 0/5/0/0.8.0.5.0.0.0, path 0/4/0/0.8.0.4.0.0.0: Both controllers may not have the same RAM image.
There is a loss of NVRAM redundancy.
Associated OS error log entry id(s):
0000000000000000000
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/fc60mon.htm#9
Description of Error:
This event message is displayed when the mirroring hardware is unable
to keep the two RAM images synchronized across the two controllers.
Probable Cause / Recommended Action:
Investigate the hardware log and use other warning conditions as a
guide to the problem. You may need to replace the controller.
Possible Causes Include:
1. A controller has failed, but no obvious failure mode is evident.
2. A controller is not communicating at all.
---------------
I check all Hardware error log , using mstm , logtool , but no error reported and array can working as normal.
enjoy any little thing in my life
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2001 02:28 AM
10-22-2001 02:28 AM
Re: NVSRAM checksum does not match
Assuming you have the latest patch bundles, I'd place a call to HP. It sounds like your array took some kind of hit. good luck.
harry
live free or die
harry
live free or die
Live Free or Die
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP