- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: System Firmware A500
HPE 9000 and HPE e3000 Servers
1753905
Members
9824
Online
108810
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
08-23-2005 04:17 AM
08-23-2005 04:17 AM
System Firmware A500
Hi, I have a server Hp9000 A500
this one present a error when boot.
the error is the next
SL
Select Chassis Code Buffer to be displayed:
Incoming, Activity, Error, Current boot or Last boot? (I/A/E/C/L) e
e
Set up filter options on this buffer? (Y/[N])
The first entry is the most recent Chassis Code
Type + CR and CR to go up (back in time),
Type - CR and CR to go down (forward in time),
Type Q/q CR to quit.
Log Entry # 0 :
SYSTEM NAME: uninitialized
DATE: 08/23/2005 TIME: 02:11:22
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail
F
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 40 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x0000002000FF6402 00000000 00000000 type 0 = Data Field Unused
0x5800082000FF6402 00006907 17020B16 type 11 = Timestamp 08/23/2005 02:11:22
Type CR for next entry, Q CR to quit.
Log Entry # 1 :
SYSTEM NAME: uninitialized
DATE: 08/23/2005 TIME: 02:11:22
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 41 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x0000002000FF6412 00000000 00000000 type 0 = Data Field Unused
0x5800082000FF6412 00006907 17020B16 type 11 = Timestamp 08/23/2005 02:11:22
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 2 :
SYSTEM NAME: uninitialized
DATE: 08/23/2005 TIME: 02:11:22
ALERT LEVEL: 2 = Non-Urgent operator attention required
this one present a error when boot.
the error is the next
SL
Select Chassis Code Buffer to be displayed:
Incoming, Activity, Error, Current boot or Last boot? (I/A/E/C/L) e
e
Set up filter options on this buffer? (Y/[N])
The first entry is the most recent Chassis Code
Type + CR and CR to go up (back in time),
Type - CR and CR to go down (forward in time),
Type Q/q CR to quit.
Log Entry # 0 :
SYSTEM NAME: uninitialized
DATE: 08/23/2005 TIME: 02:11:22
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail
F
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 40 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x0000002000FF6402 00000000 00000000 type 0 = Data Field Unused
0x5800082000FF6402 00006907 17020B16 type 11 = Timestamp 08/23/2005 02:11:22
Type CR for next entry, Q CR to quit.
Log Entry # 1 :
SYSTEM NAME: uninitialized
DATE: 08/23/2005 TIME: 02:11:22
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 41 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x0000002000FF6412 00000000 00000000 type 0 = Data Field Unused
0x5800082000FF6412 00006907 17020B16 type 11 = Timestamp 08/23/2005 02:11:22
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 2 :
SYSTEM NAME: uninitialized
DATE: 08/23/2005 TIME: 02:11:22
ALERT LEVEL: 2 = Non-Urgent operator attention required
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2005 05:15 PM
08-23-2005 05:15 PM
Re: System Firmware A500
Hi Raul,
From the system logs, looks the logs has been generated by the machine check. The alert level is ALERT LEVEL 2.
If the system cannot boot-up, you need to check whether the system can boot-up or not until BCH mode. If the system can boot up until BCH mode, you can get the PIM information.
But if the system up & running, you can ignore the messages. Or try to upgrade the firmware, below is the url for the latest firmware for A500 :
http://www1.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PF_CHAW4350&context=firmware:cpu
Hope this information can help.
Cheers,
AW
From the system logs, looks the logs has been generated by the machine check. The alert level is ALERT LEVEL 2.
If the system cannot boot-up, you need to check whether the system can boot-up or not until BCH mode. If the system can boot up until BCH mode, you can get the PIM information.
But if the system up & running, you can ignore the messages. Or try to upgrade the firmware, below is the url for the latest firmware for A500 :
http://www1.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PF_CHAW4350&context=firmware:cpu
Hope this information can help.
Cheers,
AW
now working, next not working ... that's unix
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