- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: GSP Incoming log
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-21-2006 04:19 AM
тАО02-21-2006 04:19 AM
GSP Incoming log
Any ideas will be appreciated.
Log Entry # 0 :
SYSTEM NAME: uninitialized
DATE: 02/21/2006 TIME: 17:02:35
ALERT LEVEL: 0 = No failure detected, forward progress
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: F = display_activity() update STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0x58E008001100F000 00006A01 15110223 type 11 = Timestamp 02/21/2006 17:02:35
Type CR for next entry, Q CR to quit.
Log Entry # 1 :
SYSTEM NAME: uninitialized
DATE: 02/21/2006 TIME: 16:52:35
ALERT LEVEL: 0 = No failure detected, forward progress
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: F = display_activity() update STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0x58E008001100F000 00006A01 15103423 type 11 = Timestamp 02/21/2006 16:52:35
Type CR for next entry, - CR for previous entry, Q CR to quit.
Thank you
Juan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2006 04:23 AM
тАО02-21-2006 04:23 AM
Re: GSP Incoming log
What type system?
What OS?
What firmware level?
Looks like a FW bug to me.
In this case, I'd say "no news is good news", but it looks "harmless" to me.
My $0.02,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2006 04:30 AM
тАО02-21-2006 04:30 AM
Re: GSP Incoming log
9000/800/L3000-7x
HP-UX B.11.11 U 9000/800
Firmware Revision B.02.20
--- Apr 14 2003,11:03:46
The thing that bugs me is that this message started occuring over the weekend and repeats every 10 minutes, triggering the attention light on the front panel.
i.e. why is it alerting out-of-the blue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2006 04:47 AM
тАО02-21-2006 04:47 AM
Re: GSP Incoming log
My guess would be on OnLine Diag / firmware incompatibility.
If one / either is old - update both.
The "No failure detected, forward progress" tells me that you're in no imminent danger here.
BUT - these type conflicts can lead to "false" problems reported or even - worse - *real* problems unreported.
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2006 04:58 AM
тАО02-21-2006 04:58 AM
Re: GSP Incoming log
Have a look into the *error* logs:
GSP> sl
Select Chassis Code Buffer to be displayed:
Incoming, Activity, Error, Current boot or Last boot? (I/A/E/C/L)
e
Some errors here?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2006 05:21 AM
тАО02-21-2006 05:21 AM
Re: GSP Incoming log
In addition to what torsten said also have a look at EMS log if they are reporting any error or you can go through cstm to check whether there is really any problem. Otherwise i don't see any issue as such since your server is up and runninig.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2006 06:57 AM
тАО02-21-2006 06:57 AM
Re: GSP Incoming log
a few things to check,
check the firmware of the PDC on the L3000, just in case the memory upgrade nneds an update.
The latest version is 44.12 available here
http://h20000.www2.hp.com/bc/docs/support/SupportManual/lpv38355/lpv38355.pdf?jumpid=reg_R1002_USEN
This does have a fix for erroneous memory errors for example
Also check the GSP error logs for errors aswell, if its hardware error it will show up there. The incoming logs will keep coming if the error logs are not read and actioned on.
Also check in the syslog.log file for any errors
post the outputs if you have any doubts
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2006 07:17 AM
тАО02-21-2006 07:17 AM