Specify interface in Jumpstart?

Is it possible to tell jumpstart which interface to use, so as to avoid

Using RPC Bootparams for network configuration information.
Attempting to configure interface e1000g3...
Skipped interface e1000g3
Attempting to configure interface e1000g2...
Skipped interface e1000g2
Attempting to configure interface e1000g1...
Skipped interface e1000g1
Attempting to configure interface e1000g0...
Configured interface e1000g0


--
* John Oliver http://www.john-oliver.net/ *

In article ,
John Oliver wrote:

> Is it possible to tell jumpstart which interface to use, so as to avoid
>
> Using RPC Bootparams for network configuration information.
> Attempting to configure interface e1000g3...
> Skipped interface e1000g3
> Attempting to configure interface e1000g2...
> Skipped interface e1000g2
> Attempting to configure interface e1000g1...
> Skipped interface e1000g1
> Attempting to configure interface e1000g0...
> Configured interface e1000g0

I don't know if this has changed with the newer systems, but it used to
be a restriction that a system could only boot via jumpstart via it's
motherboard interface. If you plugged in a quad-ethernet card or
gigabit ethernet card, you couldn't use that interface to boot jumpstart.

Don't know if that's still the case or totally different on x86 systems.

--
DeeDee, don't press that button! DeeDee! NO! Dee...
[I filter all Goggle Groups posts, so any reply may be automatically by ignored]

On Tue, 26 Aug 2008 10:13:43 -0700, Michael Vilain wrote:
> In article ,
> John Oliver wrote:
>
>> Is it possible to tell jumpstart which interface to use, so as to avoid
>>
>> Using RPC Bootparams for network configuration information.
>> Attempting to configure interface e1000g3...
>> Skipped interface e1000g3
>> Attempting to configure interface e1000g2...
>> Skipped interface e1000g2
>> Attempting to configure interface e1000g1...
>> Skipped interface e1000g1
>> Attempting to configure interface e1000g0...
>> Configured interface e1000g0
>
> I don't know if this has changed with the newer systems, but it used to
> be a restriction that a system could only boot via jumpstart via it's
> motherboard interface. If you plugged in a quad-ethernet card or
> gigabit ethernet card, you couldn't use that interface to boot jumpstart.
>
> Don't know if that's still the case or totally different on x86 systems.

I'm dealing with T2000s and V240s, which have four on-board interfaces.

--
* John Oliver http://www.john-oliver.net/ *

Michael Vilain wrote:
>> Attempting to configure interface e1000g0...
>> Configured interface e1000g0
>
> I don't know if this has changed with the newer systems, but it used to
> be a restriction that a system could only boot via jumpstart via it's
> motherboard interface. If you plugged in a quad-ethernet card or
> gigabit ethernet card, you couldn't use that interface to boot jumpstart.

Not true on most systems. I recall a problem in the Solaris 8 period
where you couldn't jumpstart off a 'ge' interface, but that was a
specific driver error.

You just need to give the correct device rather than 'net', which will
be pointing at one of the onboard interfaces.

But that's a separate issue from the OP, where the jumpstart has already
loaded the OS. This is just the install script probing interfaces.

I recall someone poking through the installer and found a rather elegant
way to disable specific interfaces from being probed. Unfortunately
after several minutes of searching for it, I cannot find it.

So it's possible to do, but it's not made easy.

> Don't know if that's still the case or totally different on x86 systems.

Somewhat different. On x86 you need to get the bios to do a PXE boot.
How to get that to happen or not, or which interface to use appears to
be very system dependent. On SPARC, you just need to feed the name of a
supported interface as the boot argument. I've personally done it with
expansion 'hme', 'qfe', and 'ce' interfaces.

--
Darren

John Oliver wrote:
> On Tue, 26 Aug 2008 10:13:43 -0700, Michael Vilain wrote:
>> In article ,
>> John Oliver wrote:
>>
>>> Is it possible to tell jumpstart which interface to use, so as to avoid
>>>
>>> Using RPC Bootparams for network configuration information.
>>> Attempting to configure interface e1000g3...
>>> Skipped interface e1000g3
>>> Attempting to configure interface e1000g2...
>>> Skipped interface e1000g2
>>> Attempting to configure interface e1000g1...
>>> Skipped interface e1000g1
>>> Attempting to configure interface e1000g0...
>>> Configured interface e1000g0
>>
>> I don't know if this has changed with the newer systems, but it used to
>> be a restriction that a system could only boot via jumpstart via it's
>> motherboard interface. If you plugged in a quad-ethernet card or
>> gigabit ethernet card, you couldn't use that interface to boot jumpstart.
>>
>> Don't know if that's still the case or totally different on x86 systems.
>
> I'm dealing with T2000s and V240s, which have four on-board interfaces.

yes, you can.

at the ok prompt do a

show net or show-nets or whatever the hell it is, select the interface you want by typing in the letter

then do a

boot net and hit control y to paste in the nic you selected.

On Wed, 27 Aug 2008 05:26:59 +0000 (UTC), Cydrome Leader wrote:
> John Oliver wrote:
>> On Tue, 26 Aug 2008 10:13:43 -0700, Michael Vilain wrote:
>>> In article ,
>>> John Oliver wrote:
>>>
>>>> Is it possible to tell jumpstart which interface to use, so as to avoid
>>>>
>>>> Using RPC Bootparams for network configuration information.
>>>> Attempting to configure interface e1000g3...
>>>> Skipped interface e1000g3
>>>> Attempting to configure interface e1000g2...
>>>> Skipped interface e1000g2
>>>> Attempting to configure interface e1000g1...
>>>> Skipped interface e1000g1
>>>> Attempting to configure interface e1000g0...
>>>> Configured interface e1000g0
>>>
>>> I don't know if this has changed with the newer systems, but it used to
>>> be a restriction that a system could only boot via jumpstart via it's
>>> motherboard interface. If you plugged in a quad-ethernet card or
>>> gigabit ethernet card, you couldn't use that interface to boot jumpstart.
>>>
>>> Don't know if that's still the case or totally different on x86 systems.
>>
>> I'm dealing with T2000s and V240s, which have four on-board interfaces.
>
> yes, you can.
>
> at the ok prompt do a
>
> show net or show-nets or whatever the hell it is, select the interface you want by typing in the letter
>
> then do a
>
> boot net and hit control y to paste in the nic you selected.

There's no way to specify this in the profile or something? Doing a
bunch of manual steps kind of defeats the purpose of an automated
install.

--
* John Oliver http://www.john-oliver.net/ *

In article ,
John Oliver wrote:

> On Wed, 27 Aug 2008 05:26:59 +0000 (UTC), Cydrome Leader wrote:
> > John Oliver wrote:
> >> On Tue, 26 Aug 2008 10:13:43 -0700, Michael Vilain wrote:
> >>> In article ,
> >>> John Oliver wrote:
> >>>
> >>>> Is it possible to tell jumpstart which interface to use, so as to avoid
> >>>>
> >>>> Using RPC Bootparams for network configuration information.
> >>>> Attempting to configure interface e1000g3...
> >>>> Skipped interface e1000g3
> >>>> Attempting to configure interface e1000g2...
> >>>> Skipped interface e1000g2
> >>>> Attempting to configure interface e1000g1...
> >>>> Skipped interface e1000g1
> >>>> Attempting to configure interface e1000g0...
> >>>> Configured interface e1000g0
> >>>
> >>> I don't know if this has changed with the newer systems, but it used to
> >>> be a restriction that a system could only boot via jumpstart via it's
> >>> motherboard interface. If you plugged in a quad-ethernet card or
> >>> gigabit ethernet card, you couldn't use that interface to boot jumpstart.
> >>>
> >>> Don't know if that's still the case or totally different on x86 systems.
> >>
> >> I'm dealing with T2000s and V240s, which have four on-board interfaces.
> >
> > yes, you can.
> >
> > at the ok prompt do a
> >
> > show net or show-nets or whatever the hell it is, select the interface you
> > want by typing in the letter
> >
> > then do a
> >
> > boot net and hit control y to paste in the nic you selected.
>
> There's no way to specify this in the profile or something? Doing a
> bunch of manual steps kind of defeats the purpose of an automated
> install.

Umm. Perhaps you should describe what you're trying to accomplish
first? I confused by your original post, what I responded (which was
pointedly wrong), and what you just said.

Basically, Jumpstart isn't 100% automatic. You have to type a command
at the OBP on SPARC systems to initiate the network load. I don't know
the steps for X86, but I would think they'd be similar. If properly
configured, the "boot net - install" is all you need to type to install
Solaris.

Are you looking for something that will just load an OS when the machine
is turned on? Or automagically turn the system on and load the OS as
soon as it's connected to power and the net?

What are you looking for?

--
DeeDee, don't press that button! DeeDee! NO! Dee...
[I filter all Goggle Groups posts, so any reply may be automatically by ignored]

John Oliver wrote:
> On Wed, 27 Aug 2008 05:26:59 +0000 (UTC), Cydrome Leader wrote:
>> John Oliver wrote:
>>> On Tue, 26 Aug 2008 10:13:43 -0700, Michael Vilain wrote:
>>>> In article ,
>>>> John Oliver wrote:
>>>>
>>>>> Is it possible to tell jumpstart which interface to use, so as to avoid
>>>>>
>>>>> Using RPC Bootparams for network configuration information.
>>>>> Attempting to configure interface e1000g3...
>>>>> Skipped interface e1000g3
>>>>> Attempting to configure interface e1000g2...
>>>>> Skipped interface e1000g2
>>>>> Attempting to configure interface e1000g1...
>>>>> Skipped interface e1000g1
>>>>> Attempting to configure interface e1000g0...
>>>>> Configured interface e1000g0
>>>>
>>>> I don't know if this has changed with the newer systems, but it used to
>>>> be a restriction that a system could only boot via jumpstart via it's
>>>> motherboard interface. If you plugged in a quad-ethernet card or
>>>> gigabit ethernet card, you couldn't use that interface to boot jumpstart.
>>>>
>>>> Don't know if that's still the case or totally different on x86 systems.
>>>
>>> I'm dealing with T2000s and V240s, which have four on-board interfaces.
>>
>> yes, you can.
>>
>> at the ok prompt do a
>>
>> show net or show-nets or whatever the hell it is, select the interface you want by typing in the letter
>>
>> then do a
>>
>> boot net and hit control y to paste in the nic you selected.
>
> There's no way to specify this in the profile or something? Doing a
> bunch of manual steps kind of defeats the purpose of an automated
> install.

nope.

you can specify on the machine which nic to try to boot from, but it's a
manual process. Otherwise, the machine will try to boot of every device
you don't care about until it finds one that works.

the entire sun jumpstart process is pretty hands on, and far more complex
than it needs to be. Sun should take notes from microsoft on booting and
installing things over a network.

On Wed, 27 Aug 2008 14:20:06 -0700, Michael Vilain wrote:
> Umm. Perhaps you should describe what you're trying to accomplish
> first? I confused by your original post, what I responded (which was
> pointedly wrong), and what you just said.
>
> Basically, Jumpstart isn't 100% automatic. You have to type a command
> at the OBP on SPARC systems to initiate the network load. I don't know
> the steps for X86, but I would think they'd be similar. If properly
> configured, the "boot net - install" is all you need to type to install
> Solaris.
>
> Are you looking for something that will just load an OS when the machine
> is turned on? Or automagically turn the system on and load the OS as
> soon as it's connected to power and the net?
>
> What are you looking for?

In this thread, a way to tell Jumpstart which network interface to use,
so it doesn't have to try every one it finds. This isn't a huge deal,
but once I get this dialed in, it would be nice to not have to take the
extra few minutes of the boot process trying each and every interface.

With Linux kickstart, I can specify, for example, ksdevice=eth0, and it
goes right to eth0 There is just no good reason why I shouldn't be able
to tell Jumpstart the same thing. If there's no way to do this, I'm not
surprised, and it certainly isn't a show-stopper, but it is a little
annoying.

Thanks to everyone for all the feedback.

--
* John Oliver http://www.john-oliver.net/ *

In article ,
John Oliver wrote:

> On Wed, 27 Aug 2008 14:20:06 -0700, Michael Vilain wrote:
> > Umm. Perhaps you should describe what you're trying to accomplish
> > first? I confused by your original post, what I responded (which was
> > pointedly wrong), and what you just said.
> >
> > Basically, Jumpstart isn't 100% automatic. You have to type a command
> > at the OBP on SPARC systems to initiate the network load. I don't know
> > the steps for X86, but I would think they'd be similar. If properly
> > configured, the "boot net - install" is all you need to type to install
> > Solaris.
> >
> > Are you looking for something that will just load an OS when the machine
> > is turned on? Or automagically turn the system on and load the OS as
> > soon as it's connected to power and the net?
> >
> > What are you looking for?
>
> In this thread, a way to tell Jumpstart which network interface to use,
> so it doesn't have to try every one it finds. This isn't a huge deal,
> but once I get this dialed in, it would be nice to not have to take the
> extra few minutes of the boot process trying each and every interface.
>
> With Linux kickstart, I can specify, for example, ksdevice=eth0, and it
> goes right to eth0 There is just no good reason why I shouldn't be able
> to tell Jumpstart the same thing. If there's no way to do this, I'm not
> surprised, and it certainly isn't a show-stopper, but it is a little
> annoying.
>
> Thanks to everyone for all the feedback.

Jumpstart doesn't work that way. To initiate the process requires you
to type a command at the open boot prompt (or the equivalent on X86).
At that level, the hardware doesn't know what interface you want to try
so it cycles through until it finds a network which responds to the
initial bootp request. AFAIK, there's no way around this.

--
DeeDee, don't press that button! DeeDee! NO! Dee...
[I filter all Goggle Groups posts, so any reply may be automatically by ignored]