HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

BCH on L2000

 
Sigma
Advisor

BCH on L2000

I'm unable to get to the BCH on an L2000. There are no erros being reported from the GSP.The Power LED is on, Run LED is Blinking, ATTN and Fault LED's are off. Any Ideas?

Thanks
Steve
5 REPLIES 5
Devender Khatana
Honored Contributor

Re: BCH on L2000

Hi,

The LED status displayed here shows that the system is still functional and for appearing the BCH the system should be rebooted. Have you tried that ?

A good option will be to use reboot through ts command in GSP which will leave some logs for bebugging the cause if required.

HTH,
Devender
Impossible itself mentions "I m possible"
Andrew Rutter
Honored Contributor

Re: BCH on L2000

hi steve,

How exactly are you trying to get to the BCH? local console/remote?

It sounds like its up and running possibly at pdc, youre just not getting the output.

Do you get anything output on the local console at all, can you see the tests been started and initializing chassis codes.

From GSP you should be able to just type the co command to return to PDC

Andy
Sigma
Advisor

Re: BCH on L2000

Devender,
I have done a reset from the GSP, still nothing. SL logs are below.

Andrew,
I've tried using both the local and remote console. Here's the VFP output and Logs.


LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH OFF OFF ON ON
LED State: Running non-OS code. (i.e. Boot or Diagnostics)

platform operation 6203


Proceed with Live Mode of VFP? (Y/[N]) y
y


GSP Host Name: L2000
GSP>
********** VIRTUAL FRONT PANEL **********
VFP command executing...
Q/q: to quit Virtual Front Panel Display
->Choice:
*****************************************

*************** LIVE VFP ****************
VFP command exit. Activating Console...
*****************************************

Logs:

Select Chassis Code Buffer to be displayed:
Incoming, Activity, Error, Current boot or Last boot? (I/A/E/C/L) c
c

Set up filter options on this buffer? (Y/[N]) n
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: L2000
DATE: 10/12/2004 TIME: 20:39:08
ALERT LEVEL: 0 = No failure detected, forward progress

SOURCE: 3 = PDH
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 2 = config STATUS: 0
CALLER SUBACTIVITY: 2F = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x00000000300022F0 00000000 00000000 type 0 = Data Field Unused
0x58000800300022F0 00006809 0C142708 type 11 = Timestamp 10/12/2004 20:39:08


Log Entry # 1 :
SYSTEM NAME: L2000
DATE: 10/12/2004 TIME: 20:39:08
ALERT LEVEL: 1 = Information only, no action required

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: E = processor is monarch

CALLER ACTIVITY: 1 = test STATUS: 2
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x0000001E11001002 00000000 00000000 type 0 = Data Field Unused
0x5800081E11001002 00006809 0C142708 type 11 = Timestamp 10/12/2004 20:39:08
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 2 :
SYSTEM NAME: L2000
DATE: 10/12/2004 TIME: 20:39:08
ALERT LEVEL: 1 = Information only, no action required

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 3
PROBLEM DETAIL: 7 = added to configuration

CALLER ACTIVITY: 1 = test STATUS: 2
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x0000001711031002 00000000 00000000 type 0 = Data Field Unused
0x5800081711031002 00006809 0C142708 type 11 = Timestamp 10/12/2004 20:39:08


Log Entry # 3 :
SYSTEM NAME: L2000
DATE: 10/12/2004 TIME: 20:39:08
ALERT LEVEL: 1 = Information only, no action required

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 3
PROBLEM DETAIL: D = processor is de-installed

CALLER ACTIVITY: 1 = test STATUS: 2
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x0000001D11031002 0000003A 00000000 type 0 = Data Field Unused
0x5800081D11031002 00006809 0C142708 type 11 = Timestamp 10/12/2004 20:39:08
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 4 :
SYSTEM NAME: L2000
DATE: 10/12/2004 TIME: 20:39:08
ALERT LEVEL: 1 = Information only, no action required

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 2
PROBLEM DETAIL: 7 = added to configuration

CALLER ACTIVITY: 1 = test STATUS: 2
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x0000001711021002 00000000 00000000 type 0 = Data Field Unused
0x5800081711021002 00006809 0C142708 type 11 = Timestamp 10/12/2004 20:39:08


Log Entry # 5 :
SYSTEM NAME: L2000
DATE: 10/12/2004 TIME: 20:39:08
ALERT LEVEL: 1 = Information only, no action required

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 2
PROBLEM DETAIL: D = processor is de-installed

CALLER ACTIVITY: 1 = test STATUS: 2
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x0000001D11021002 00000000 00000000 type 0 = Data Field Unused
0x5800081D11021002 00006809 0C142708 type 11 = Timestamp 10/12/2004 20:39:08
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 6 :
SYSTEM NAME: L2000
DATE: 10/12/2004 TIME: 20:39:08
ALERT LEVEL: 1 = Information only, no action required

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 1
PROBLEM DETAIL: 7 = added to configuration

CALLER ACTIVITY: 1 = test STATUS: 2
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x0000001711011002 00000000 00000000 type 0 = Data Field Unused
0x5800081711011002 00006809 0C142708 type 11 = Timestamp 10/12/2004 20:39:08


Log Entry # 7 :
SYSTEM NAME: L2000
DATE: 10/12/2004 TIME: 20:39:08
ALERT LEVEL: 1 = Information only, no action required

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 1
PROBLEM DETAIL: D = processor is de-installed

CALLER ACTIVITY: 1 = test STATUS: 2
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x0000001D11011002 00000000 00000000 type 0 = Data Field Unused
0x5800081D11011002 00006809 0C142708 type 11 = Timestamp 10/12/2004 20:39:08
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 8 :
SYSTEM NAME: L2000
DATE: 10/12/2004 TIME: 20:39:08
ALERT LEVEL: 1 = Information only, no action required

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 7 = added to configuration

CALLER ACTIVITY: 1 = test STATUS: 2
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x0000001711001002 00000000 00000000 type 0 = Data Field Unused
0x5800081711001002 00006809 0C142708 type 11 = Timestamp 10/12/2004 20:39:08

Log Entry # 9 :
SYSTEM NAME: L2000
DATE: 10/12/2004 TIME: 20:39:08
ALERT LEVEL: 1 = Information only, no action required

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: C = processor is installed

CALLER ACTIVITY: 1 = test STATUS: 2
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x0000001C11001002 00000000 00000000 type 0 = Data Field Unused
0x5800081C11001002 00006809 0C142708 type 11 = Timestamp 10/12/2004 20:39:08
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 10 :
SYSTEM NAME: L2000
DATE: 10/12/2004 TIME: 20:39:08
ALERT LEVEL: 0 = No failure detected, forward progress

SOURCE: 1 = processor
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 1 = test STATUS: 0
CALLER SUBACTIVITY: 42 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x0000000010001420 00000000 00000000 type 0 = Data Field Unused
0x5800080010001420 00006809 0C142708 type 11 = Timestamp 10/12/2004 20:39:08


Log Entry # 11 :
SYSTEM NAME: L2000
DATE: 10/12/2004 TIME: 20:39:08
ALERT LEVEL: 1 = Information only, no action required

SOURCE: 6 = platform
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 2 = config STATUS: 0
CALLER SUBACTIVITY: 6F = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0xA0000010600026F0 00000000 00000710 type 20 = major change in system state
0x58000810600026F0 00006809 0C142708 type 11 = Timestamp 10/12/2004 20:39:08
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 12 :
SYSTEM NAME: L2000
DATE: 10/12/2004 TIME: 20:39:08
ALERT LEVEL: 0 = No failure detected, forward progress

SOURCE: 3 = PDH
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 2 = config STATUS: 0
CALLER SUBACTIVITY: 78 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x5800080030002780 00006809 0C142708 type 11 = Timestamp 10/12/2004 20:39:08


Thanks for the Help.
Steve
Highlighted
AwadheshPandey
Honored Contributor

Re: BCH on L2000

Steve,

just try to boot the system with minimum configuration, ie. memory etc,

Awadhesh
It's kind of fun to do the impossible
Sigma
Advisor

Re: BCH on L2000

Yes, I've done that. It's current config is 1 CPU and two sticks of memory.

Thanks for the response.
Steve