- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- N4000 Alert Level 2
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
тАО11-29-2004 02:59 AM
тАО11-29-2004 02:59 AM
N4000 Alert Level 2
System performance seems to be unnaffected and no other errors have been logged.
This seems to have followed on since a memory & internal disk upgrade.
Can anyone tell me what the chassis code specifically means please?
Log Entry # 0 :
SYSTEM NAME: uninitialized
DATE: 11/25/2004 TIME: 14:20:22
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 8 = I/O
SOURCE DETAIL: 2 = system bus adapter SOURCE ID: 0
PROBLEM DETAIL: B = parity error
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 33 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 01
0x7000102B82006332 00000000 00571800 type 14 = Problem Detail
0x5800182B82006332 0000680A 190E1416 type 11 = Timestamp 11/25/2004 14:20:22
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2004 07:41 AM
тАО11-29-2004 07:41 AM
Re: N4000 Alert Level 2
As per the table points there should be a parity error on the newly added module.You can remove the modules you have added to the server recently and see what happens. See whether the logs are generated again.
Also view the chasis codes through GSP once.
I am attaching the IO chasis code table with this.
Other docs will be attached with my next mesg.
Regards,
Syam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2004 07:43 AM
тАО11-29-2004 07:43 AM
Re: N4000 Alert Level 2
Find the attached PDF.
Regards,
Syam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-29-2004 07:45 AM
тАО11-29-2004 07:45 AM
Re: N4000 Alert Level 2
Find the attached PDF.
Regards,
Syam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2004 01:26 AM
тАО11-30-2004 01:26 AM
Re: N4000 Alert Level 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2004 02:41 AM
тАО11-30-2004 02:41 AM
Re: N4000 Alert Level 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2004 04:18 AM
тАО11-30-2004 04:18 AM
Re: N4000 Alert Level 2
Is your problem solved. If yes pls close the thread.
Thanks,
Syam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-30-2004 08:00 PM
тАО11-30-2004 08:00 PM