Operating System - Linux
1748261 Members
3715 Online
108760 Solutions
New Discussion юеВ

Re: c -class Blade Server discovery problems

 
Teemu Turpeinen
Advisor

c -class Blade Server discovery problems

Hello.

We've been trying to discover a c -class Blade Server with Control Tower 1.5, but at the point of "starting tincan" a following error is displayed:

Fatal error: Uncaugh SoapFault exception: [Client] looks like we got no XML document in /var/rct/includes/provision/tincan/public/startTinCan.php:28
Stack trace:
#0 /var/rct/includes/provision/tincan/public/startTinCan.php(28): SoapClient->__call('handshake', Array)
#1 {main}
thrown in /var/rct/includes/provision/tincan/public/startTinCan.php on line 28

Anyone faced any similar problems with c -class Blades (BL460c G1)?

In Control Tower GUI nothing is shown. No Events, nothing in Component Manager and so on. We have currently 4 Blades in the Chassis (3 + CT), but CT cannot discover any of them. All ILO interfaces and OA has been set to DHCP and can be seen from CT DHCP leases view and accessed with a browser.

Please find attached a screenshot of an ILO Remote Console window showing the error.

Br,


/teemu
14 REPLIES 14
Teemu Turpeinen
Advisor

Re: c -class Blade Server discovery problems

Hi.

Ok, most likely problem solved. Further look at the manuals by a collegue resulted in the following discovery from Onboard Administrator User Guide.

Control Tower makes XML queries to OA of HW and by default, OA does not respond. On page 69, Network Access:

XML Reply ├в This checkbox is not selected by default. Selecting this checkbox enables XML replies from the Onboard Administrator onto the network.

So we'll try it out later this week.



Br,


/teemu
klemerS
Frequent Advisor

Re: c -class Blade Server discovery problems

Hello Teemu.

I am not expert & hope Robert Crockett will see your Question soon.

I installed 16 bl460c in 2 encl. With no problem at all regarding the Discover Step.

Did you connect NIC1 ( eth1 ) to the management network ?

You can check if the CT create a user "ctadmin" in thr bl460 ILOs.

Maybe something realy wrong with the /var/rct/includes/provision/tincan/public directory.

Hope you will solve the problem soon.

Shalom.
Teemu Turpeinen
Advisor

Re: c -class Blade Server discovery problems

Hello.

Yes, the interfaces are connected to the mgmt network.

We used CT for deploying a bunch of p -series blades without any problems, so I was quite amazed when this error appeared.

But, we'll check the OA configuration and other stuff later this week and hopefully after that can continue with deployment.

Thanks for the reply.

Br,

/teemu
Robert Crockett
Valued Contributor

Re: c -class Blade Server discovery problems

Hello Teemu, the main issue with the BL460c's registration process is the NIC's. Be sure that ONLY NIC1 is in the VLAN that connects to the ICLE's Management network. There is a known problem with that specific blade (BL460c) where all NIC's try to work on the expected isolated ICLE Management network. It is written up in the Release Notes for the next upgrade (v.1.60).
The easiest way to test for this scenario is to use the VGA console (or remote VGA console via the iLO) and when the blade PXE boots to the error mentioned in your first thread, go to that console prompt (which is a linux ramdisk) and type 'ifconfig'. Look for more than one NIC with a '10.128.xxx.xxx' IP, if this is the case you must setup a VLAN that only has NIC1 in it for the blades you are trying to register. This scenario is ONLY on the BL460c.

Robert
Teemu Turpeinen
Advisor

Re: c -class Blade Server discovery problems

Hi.

Thanks for the reply. The problem was with the network interfaces being connected to the same VLAN.

What's strange though is that before connecting the other NIC, it did not work either. But after removing it, it worked. Go figure...



/teemu
Robert Crockett
Valued Contributor

Re: c -class Blade Server discovery problems

Glad to hear you were able to resolve this issue... not sure why it worked the way you describe ? my assumption is a routing or NIC issue, that specific blade gave us trouble when developing ICLE - but none of the other HP blades had this issue ?

Robert
Teemu Turpeinen
Advisor

Re: c -class Blade Server discovery problems

Hi.

Ok. Thanks for the information.

We also have problems with image capture from that particular blade type. Is that also just 460c specific and will there be enhancements to that in the next release?

Br,

/teemu
Robert Crockett
Valued Contributor

Re: c -class Blade Server discovery problems

What kind of image capture problem are you having ? How many partitions do you have on the OS you are trying to capture ? and what type are they ? (ext2, ext3, reiserfs, etc.)
What OS and version ?
Can you give me an error log from ICLE on a failed capture ?

Robert
Teemu Turpeinen
Advisor

Re: c -class Blade Server discovery problems

Hi.

The image capture times out on "wait for RAPIDS" in ICLE.

-- klip --
[2007-05-22 10:14:02] Failed to contact ramdisk () after 921 seconds
[2007-05-22 10:14:02] Failed
-- klip --

In console, "mount error 101 - Network is unreachable" message is displayed. It seems that the RAPIDS image is unable to get ip address with DHCP.


Br,


/teemu