Capturing Image from BL680c G5 Server

[Mitchell Kulberg]

Mario,

Above you listed out the stack trace error you got.

How did you copy that?

Did you copy it off the screen or do you have some type of terminal connected to the console?

We would be interested in getting the surrounding text from the crash.

By the way, we are continuing to try and reproduce what you are seeing.

Mitch

[Mario Couthino]

I tried it with the restoring of the bios to default factory setting but no luck.

The stack trace was typed by hand. The surrounding text is of uncompressing linux ..... kernel..

[Mario Couthino]

this is what I see in the sim page

[Mario Couthino]

Here is the complete message on the stack trace

loading /icletoolkitboot/kernel
loading /icletoolkitboot/initrd.img

uncompress linux ok booting kernel

Than I get the stack error

[Christopher Grandinetti]

Hello Mario,

We installed a a BL680c with(4) quad-core cpus into our c7000 enclosure that had 5 existing nodes installed with SUSE 10 SP1 running ICE-Linux. The BL680c was previously installed with RHEL4U5 and had BIOS version 10/18/2007 and iLO version 1.50.

We tried the image capture and it worked fine; we saw no issues:

puma1:/opt/repository/image/puma6-1f29-6f64-3-61-200804250320 # ls -ltr
total 1422660
-rw------- 1 root root 1455380480 Apr 25 15:25 puma6-1f29-6f64-3-61-200804250320.tar.gz

So, then we upgraded the BIOS firmware to the latest version: 02/13/2008.

We again tested the image capture and it worked fine too:

puma1:/opt/repository/image # ls -ltr
total 0
drwxr-xr-x 2 root root 104 Apr 25 15:20 puma6-1f29-6f64-3-61-200804250320
drwxr-xr-x 2 root root 112 Apr 25 16:21 puma6-2-1f29-6f64-3-61-200804250421
puma1:/opt/repository/image # cd puma6-2-1f29-6f64-3-61-200804250421
puma1:/opt/repository/image/puma6-2-1f29-6f64-3-61-200804250421 # ls -ltr
total 1423929
-rw------- 1 root root 1456680960 Apr 25 16:26 puma6-2-1f29-6f64-3-61-200804250421.tar.gz
puma1:/opt/repository/image/puma6-2-1f29-6f64-3-61-200804250421 #

We'll continue to try to reproduce this issue your are seeing.

In the meantime, can you send us the output of 'hplog -v' from the BL680c.

Also, please type 'hpasmcli' to get to the hpasmcli> prompt and reply with the following output: from your blade:

hpasmcli> show serial bios
BIOS console redirection port is currently set to COM1/9600.

hpasmcli> show serial embedded
Embedded serial port A: COM2
Embedded serial port B: Disabled

hpasmcli> show serial virtual
The virtual serial port is currently COM1.

hpasmcli> show server (lots of output so I won't paste it here)

Thanks,
-Chris

[Mario Couthino]

Please find the output in the attached text format file

[Mario Couthino]

Just a couple of views that have come across.

When I try to install an agent I get the following in the stdout screen
Warning: Specified node(s) are not configured for monitoring
admelprd1,

When I run identify system I get the following

Starting identification process...
Checking for known running web servers.
Checking for System Management Home Page and other HP web agents.
Received a response from the system management homepage, this system supports SMH.
Checking for WBEM support on system.
WBEM is globally disabled, skipping WBEM identification.
Running WBEM rules based identification.
WBEM is globally disabled, skipping WBEM identification.
Running VM Identification
The system is not a VMware ESX Host, or WBEM credentials may not be specified, skipping VM Identification
Running WS-Man identification.
The system did not respond to WS-Management, verify credentials.
Checking for SNMP support on system.
The system did not respond to SNMP, verify security settings and community strings.
Running SNMP base Cluster identification using common cluster MIB.
This was not a system with the common cluster MIBs supported.
Running HP ProLiant management agent identification
The system does not support SNMP.
Running HP NetServer identification.
The system does not support SNMP.
Running HP-UX SNMP identification.
The system does not support SNMP.
Running SNMP System Type Manager identification.
The system does not support SNMP.
Checking for DMI protocol support.
DMI is globally disabled, skipping DMI identification.
Running DMI System Type Manager identification.
The non Windows CMS cannot communicate with Windows DMI, skipping.
Running HP-UX DMI identification.
DMI is globally disabled, skipping DMI identification.
Running HP/Compaq Desktop identification.
The non Windows CMS cannot communicate with Windows DMI, skipping.
Running HP DMI Desktop identification.
DMI is globally disabled, skipping DMI identification.
Running Generic DMI identification.
The non Windows CMS cannot communicate with Windows DMI, skipping.
Checking for SSH protocol support.
The system supports SSH protocol
Running Storage identification.
Did not detect WBEM support on this system. Will not attempt storage identification. If this is a storage host, check WBEM credentials and make sure the providers and CIMOM are operational on the host.
Storage identification completed.
Running HP Service Guard Identification.
The system is not part of HP Service Guard cluster
Running VM identification.
VMM Integration is not enabled, skipping VM Identification
Checking if this system is supported by Insight Power Manager.
Insight Power Manager is not supported.
Building system relationships.
Running limited data collection for common attribute.
Done with limited data collection, checking retrieved data.
The SSH is configured on this system
SMH trust status is true.
Running node communication diagnosis
System identification done with this system.

[Rigoberto Corujo]

Hello Mario,

From your BL680cG5, can you please provide the output of:

1. lspci
2. lshw
3. dmidecode
4. full console output showing all the text leading up to the error.

Is this the only system that you can't capture from?

Thank you.

Rigoberto

[Mario Couthino]

Decode and lspci. Cant get any output for the other command and cant get a screen shot of the console

[Mario Couthino]

I tried to capture an image from a similar system on the same C-class Chasis and came up with the same result.