Capturing Image from BL680c G5 Server

[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.

[Rigoberto Corujo]

Hello Mario,

Is your other "similar system" that you cannot capture from either also a BL680c G5 and does it have the same Fibre Channel HBA?

0d:00.0 Fibre Channel: Emulex Corporation Zephyr-X LightPulse Fibre Channel Host Adapter (rev 02)
0d:00.1 Fibre Channel: Emulex Corporation Zephyr-X LightPulse Fibre Channel Host Adapter (rev 02)

We're trying to determine if the presence of the Fibre Channel HBA may be the cause of the kernel panic.

Thank you for your cooperation.

Rigoberto

[Mario Couthino]

Yes the system is similar. with the same hardware. I have a 3rd system which is a DL385 with the same hardware as my HP SIM server and is on the same network. I am not able to capture the Operating system from this third server as well

[Christopher Grandinetti]

Mario,

The only difference we can see between your BL680c and ours is the Emulex Fibre Channel card:

0d:00.0 Fibre Channel: Emulex Corporation Zephyr-X LightPulse Fibre Channel Host Adapter (rev 02)
0d:00.1 Fibre Channel: Emulex Corporation Zephyr-X LightPulse Fibre Channel Host Adapter (rev 02)

Would it be possible for you to remove this card and retry capturing the image and letting us know the result?

[Mario Couthino]

The Emulex Card that we are using is below

Emulex LPe1105-HP 4Gb FC HBA for HP c-Class BladeSystem

[Christopher Grandinetti]

Hi Mario,

Sorry, I wasn't clear in my last reply.

We do not have a Fibre Channel card in our BL680c.

So, I was wondering if it was possible for you to remove your fibre channel card and try to capture the image with it removed to see if that card is causing the boot issue.

-Chris

[Mario Couthino]

I can do that but we have this blade connected to external storage which requires the fibre.

I am trying to do a test with another blade bl460c which has a qlogic fiber card and seeing if the issue arises

[Mitchell Kulberg]

Mario,

Does this system not have any local disks?
We just want to see if it is the fiber card that is causing the crash. If the Qlogic card doesn't work either, try removing all fiber cards. Even if the node has no local disks, I think it should still be able to boot the ramdisk and bare-metal discover onto the CMS.

Unfortunately, we don't have a fiber card here in our lab. We'll be ordering one today, but it will take at least a few days to arrive.

Thanks

[Mario Couthino]

We are atleast a bit closer. I tried it with the blade bl460c that has the qlogic card and it seemed to have gone through the pxe boot sequence and is currently on the following screen

EXT3-fs: mounted filesystem with order data
mode kjournald starting commit interval 5 seconds
EXT3-fs:mounted filesystem with order data mode.
Task engine failed

Please press enter to activate this console


Thanks

[Mario Couthino]

to follow the above message I can see

EXT3-fs: mounted filesystem with order data
mode kjournald starting commit interval 5 seconds
EXT3-fs:mounted filesystem with order data mode.
Task engine failed

Please press enter to activate this console
bnx2:eth0: using MSI
bnx2:eth0 nic serdes link is up, 1000 mbps full duplex
bnx2:eth0: using MSI
bnx2:eth0 nic serdes link is up, 1000 mbps
full duplex
bnx2:eth0: using MSI
bnx2:eth0 nic serdes link is up, 1000 mbps full duplex
bnx2:eth0: using MSI
bnx2:eth0 nic serdes link is up, 1000 mbps full duplex


In addition when I run discovery I can see the system but when I try to do a capture of an image it fails on step 2

[Mitchell Kulberg]

Mario,

When it says "Please press ENTER to activate this console" that is the completion of the ICE-Linux RAMdisk boot sequence.

I believe you will be able to bare-metal discover, capture, and deploy images now.

It looks like that card is not well liked by the ramdisk. We will have to sole this problem when we have a card in hand, and try to get a fix out.

Can you run with these Qlogic cards?

Mitch

[Mario Couthino]

After that message was received I waited for around 20 mins but there was no response. I then cold booted the blade and it booted to the os. I then ran discovery on the blade which was successful after which I proceed into trying to capture the image when I received the attached error ( see attachement)

[Mitchell Kulberg]

Well, the good news is that you are finally hitting "normal" problems :)

The error you see there is because SIM no longer understands which iLO belogs to the server you are working on. There needs to be a server to iLO "association". There are circumstances that cause this association to go away.

There are troubleshooting steps for repairing server to iLO associations in the troubleshooting sections of the ICE-Linux users' guide AND the release notes.

- For startes, make sure the iLO is discovered
- try selecting both the server and the iLO and do an Options -> identify system

This often can fix the problem.

Mitch

[Mario Couthino]

I tried the suggestion and have received the attached messages.

I have also attached the stdout from the identify system task

[Mitchell Kulberg]

Mario,

The following line in the log file:

"System does not have the SNMP ProLiant Server (foundation) agents installed."

Indicates that the managed system either does not have the appropriate Proliant Support Pack installed, or the PSP is not properly configured.

You need to be running hpasm and hp-ilo on your system and have them configured using 'configure or repair agents' in SIM.

These steps are WELL documented in the ICE-Linux docs, and it will take me too long to type it in this way :)

Once you get that squared away, you should be fine.

Mitch

[Mario Couthino]

the latest psp has been applied an appropriately configured. I was able to boot the server via pxe and it came up to the "Please Enter to return to console screen" which when I hit enter gave me a # prompt. If i did not hit enter it stays there. I then booted the server via local linux os as well as ran the identify server which identified the server eth0 successfully but was not able to identify the ilo. In addition if I try to capture the linux image it fails on step 2

Setting one time PXE.
Could not set one time PXE:
Error retrieving BMC for server. Root cause:Could not determine the BMC associated with the server (192.168.28
.212) in the database. Probably not discovered yet.


Any ideas

[Mitchell Kulberg]

Mario,

You're getting there, however, the CMS is still not able to associate the iLO with the server. That's what that error means.

This is USUALLY the result of the agents on the managed node either not being installed, not running, or not being properly configured. You need to double check these.

One thing you can try is to manually enter a snmp get command from the CMS to see if the managed node really returns any information.

Try the following command, replacing your information for and

snmpwalk -Os -c -v 1 .1.3.6.1.4.1.232.9.2.2

Remember, run this command ON the CMS but query the managed node, just like SIM would.

If your agents are properly configured, you should see assorted information about the iLO in that server, including the date and version of the firmware and the iLO system name.

If you don't get that back, then you still need to fix the agents.

Run 'configure or repair agents' from the SIM GUI against that node.

[Mario Couthino]

When i run configure/repair agent I get the following message

Configuration of agents started, waiting for it to be completed.
Configure Agents and Providers (START) ...
Configuring SSH authentication (START)...
Configure SSH for host based authentication (DONE)................. [SUCCESS]

LINUX configuration command (START)...
Configuring SNMP Settings (START)...
Stopping SNMP daemon...
Stopping snmpd: [ OK ]
Trap destination address ifdssim already in /etc/snmp/snmpd.conf
Restarting SNMP Daemon...
Starting snmpd: [ OK ]
Setting SNMP trap destination / SNMP read community string (DONE)....[SUCCESS]


Set Trust relationship to "Trust by Certificate" (START) ...
Setting Trust for System Management Home Page.
Stopping System Management Home Page
Stopping hpsmhd:
Copying /var/opt/mx/tmp/ifdssim.pem to /opt/hp/hpsmh/certs
Restarting System Management Home Page
Starting hpsmhd:
...hpsmhd: Could not determine the server´s fully qualified domain name, using 1
92.168.42.128 for ServerName
[ OK ]
Set Trust relationship to "Trust by Certificate" (DONE)............. [SUCCESS]


Setting admin password/Trust for Insight Management Agents 7.1/earlier (START)..
Setting admin password/Trust for legacy HP Server Management Agents..[SKIPPED] H
P Server Management Drivers and Agents, is not installed.


Linux configuration commands (DONE)................................. [SUCCESS]

Re-identifying system to get update information (START) ...
Re-Identification of system (DONE).............................. [SUCCESS].

Subscribing to WBEM / WMI indications ...
Subscribe to WBEM / WMI Indications (DONE).......................... [FAILED]
Check whether target system met the requirements and all of the software require
d to support indications is installed.
WBEM protocol settings are not valid/enabled for this system in HP SIM. Check yo
ur HP SIM settings.


I tried the snmpwalk and it was working fine

[Rigoberto Corujo]

Hello Mario,

Can you please attach the output of "mxnode -ld"?

Rigoberto

[Mitchell Kulberg]

Mario,

You 'configure and repair agents' output looks fine. It failed on the WBEM configuration because your system probably doesn't support WBEM. But everything else worked. We suggest unchecking the WBEM option. The only two things you really need are the SNMP config and the configure SSH access options.

Are you saying that AFTER you ran this tool, the server to iLO association is still not there?

[Mario Couthino]

The Server to ILO association is there but for some reason it does not want to capture the image and fails on step one.