On Wed, Jan 14, 2009 at 9:54 AM, Mike Gerdts <mgerdts at gmail.com> wrote:
> On Fri, Feb 15, 2008 at 3:06 AM, Liam Merwick <Liam.Merwick at sun.com> wrote:
>> nthai at jpl.nasa.gov wrote:
>>
>>> I'm having problem jumpstarting my guest domain. Below is the message
>>> when I try to jumpstart. Can anyone help?
>>>
>>> Thanks
>>>
>>> {0} ok boot dev11i-vnet1 -v install
>>
>> You are using the name of the vnet in the LDoms configuration - you'll need
>> to
>> use the device path or a devalias to it.
>>
>> Example:
>> {0} ok show-nets
>> a) /virtual-devices at 100/channel-devices at 200/network at 0
>> q) NO SELECTION Enter Selection, q to quit: a
>> /virtual-devices at 100/channel-devices at 200/network at 0 has been
>> selected.
>> Type ^Y ( Control-Y ) to insert it in the command line. e.g. ok nvalias
>> mydev ^Y for creating devalias mydev for
>> /virtual-devices at 100/channel-devices at 200/network at 0
>> {0} ok boot /virtual-devices at 100/channel-devices at 200/network at 0 -
>> install
>
> Are there any other known causes of this problem? I'm seeing it on a
> T2000 with LDoms_Manager-1.1-earlyaccess. I'm working on getting to
> 1.1-RR but am fighting a proxy server that seems to have switched to
> dial-up. In any case, I'm suspecting a hardware reset will clear it
> up as this config has worked in the past. I'd like to figure this out
> without a reset so that this doesn't become the standard
> outage-inducing answer whenever it comes up.
>
> {0} ok show-nets
> a) /virtual-devices at 100/channel-devices at 200/network at 0
> b) /virtual-devices at 100/channel-devices at 200/network at 1
> q) NO SELECTION
> Enter Selection, q to quit: a
> /virtual-devices at 100/channel-devices at 200/network at 0 has been selected.
> Type ^Y ( Control-Y ) to insert it in the command line.
> e.g. ok nvalias mydev ^Y
> for creating devalias mydev for
> /virtual-devices at 100/channel-devices at 200/network at 0
> {0} ok boot /virtual-devices at 100/channel-devices at 200/network at 0 -
> install
> Boot device: /virtual-devices at 100/channel-devices at 200/network at 0 File
> and args: - install
> WARNING: /virtual-devices at 100/channel-devices at 200/network at 0:
> Receiving
> packet from LDC but LDC is Not Up!
>
> WARNING: /virtual-devices at 100/channel-devices at 200/network at 0:
> Communication error with Virtual Network Server!
>
> ERROR: boot-read fail
My trial and error to fix this problem involved:
1) stop and start the ldom
2) stop, unbind, bind, start the ldom
3) stop, unbind ldoms; upgrade Ldoms Manager to 1.1 RR; bind, start ldoms
4) stop, unbind ldom; reboot primary domain; bind, start ldom
5) stop, unbind ldom; poweroff & poweron server; bind start ldom
6) remove non-native vlans from ldom; try boot net - install
7) stop, unbind, bind, start ldom; try boot net - install
Since it worked once I got to step 7, I decided to stop trying. :)
It seems as though the non-native vlan configuration is causing some
sort of conflict. Is anyone aware of an open bug related to this? A
search for keywords "ldom AND vlan" shows no bugs.
--
Mike Gerdts
http://mgerdts.blogspot.com/
