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 <slrngb8d98.mme.joliver@ns.sdsitehosting.net>, John Oliver <joliver@john-oliver.net> 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 <slrngb8d98.mme.joliver@ns.sdsitehosting.net>, > John Oliver <joliver@john-oliver.net> 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 <vilain@nospamcop.net> 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 <joliver@john-oliver.net> wrote: > On Tue, 26 Aug 2008 10:13:43 -0700, Michael Vilain wrote: >> In article <slrngb8d98.mme.joliver@ns.sdsitehosting.net>, >> John Oliver <joliver@john-oliver.net> 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 <joliver@john-oliver.net> wrote: >> On Tue, 26 Aug 2008 10:13:43 -0700, Michael Vilain wrote: >>> In article <slrngb8d98.mme.joliver@ns.sdsitehosting.net>, >>> John Oliver <joliver@john-oliver.net> 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 <slrngbbdh8.1rq.joliver@ns.sdsitehosting.net>, John Oliver <joliver@john-oliver.net> wrote: > On Wed, 27 Aug 2008 05:26:59 +0000 (UTC), Cydrome Leader wrote: > > John Oliver <joliver@john-oliver.net> wrote: > >> On Tue, 26 Aug 2008 10:13:43 -0700, Michael Vilain wrote: > >>> In article <slrngb8d98.mme.joliver@ns.sdsitehosting.net>, > >>> John Oliver <joliver@john-oliver.net> 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 <joliver@john-oliver.net> wrote: > On Wed, 27 Aug 2008 05:26:59 +0000 (UTC), Cydrome Leader wrote: >> John Oliver <joliver@john-oliver.net> wrote: >>> On Tue, 26 Aug 2008 10:13:43 -0700, Michael Vilain wrote: >>>> In article <slrngb8d98.mme.joliver@ns.sdsitehosting.net>, >>>> John Oliver <joliver@john-oliver.net> 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 <slrngbc5c8.jpv.joliver@ns.sdsitehosting.net>, John Oliver <joliver@john-oliver.net> 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]

John Oliver <joliver@john-oliver.net> wrote: > 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. There are several different interactions with the network. I think people are talking about different things here. The first bit is the interface that the SPARC hardware (OBP) uses for booting (RARP or DHCP). That interface (or interfaces) can be given by keyword ('net') or by a device path. Another bit is that long after the Solaris kernel has loaded (over the network) and the installer is running, the installer probes all the hardware on the system for DHCP responses. Because this is the same installer that can from CD, there is no communication between the boot process using a particular interface and the installer searching for configurable interfaces. I *think* you're talking about the second case (which I responded to in an earlier post), while others are talking about the first case. Jumpstart is just some scripts running for the most part, so yes it can be tweaked to ignore some of the installed devices. But that's not part of the spec, so I can't tell you how to do it easily. > 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. There you are telling kickstart where to find it's information. At this point in the jumpstart, you are well past that. The installer is already running (from the network). What you see instead is that the installer likes to probe all networks for configuration (not for installation). -- Darren

Michael Vilain <vilain@nospamcop.net> wrote: > 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. You are wrong. It has always been possible to boot jumpstart from other adapters than from the integrated ones. Some systems do not even have integrated adapters. Sami -- .signature: no such file or directory

In article <mhklo5-ffs.ln1@mankeli.baana.suomi.net>, Sami Ketola <Sami.Ketola@iki.finland.invalid> wrote: > Michael Vilain <vilain@nospamcop.net> wrote: > > 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. > > You are wrong. It has always been possible to boot jumpstart from > other adapters than from the integrated ones. Some systems do not even > have integrated adapters. > > Sami Yep. It turns out, after looking at some really old notes, that you can boot from other network interfaces from a SPARC OBP. You just have to specify the entire path: http://www.pir.net/pir/hacks/js/#2.4 -- DeeDee, don't press that button! DeeDee! NO! Dee... [I filter all Goggle Groups posts, so any reply may be automatically by ignored]

Similiar Articles:

Specify interface in Jumpstart? - comp.unix.solaris
Is it possible to tell jumpstart which interface to use, so as to avoid Using RPC Bootparams for network configuration information. Attempting to con...

Solaris 10 Jumpstart issue - comp.unix.solaris
Specify interface in Jumpstart? - comp.unix.solaris comp.unix.solaris - page 246 Solaris 10 Jumpstart issue 6 195 Hi everyone, I am trying to ... How to dynamically set ...

Question: Jumpstart/Hardware Config - comp.sys.sun.admin ...
Specify interface in Jumpstart? - comp.unix.solaris Is it possible to tell jumpstart which interface to use, so as to avoid Using RPC Bootparams for network configuration ...

Jumpstart - NFS server not responding still trying - eventually ...
Specify interface in Jumpstart? - comp.unix.solaris Jumpstart doesn't work that way. To initiate the process ... Jumpstart - NFS server not responding still trying ...

OBP devalias question. - comp.unix.solaris
Specify interface in Jumpstart? - comp.unix.solaris... Post Question | Groups ... You have to type a command at the OBP on SPARC ... comp.unix.solaris Check net is ...

Netra T1 goes to OK> prompt - but why? - comp.sys.sun.admin ...
Specify interface in Jumpstart? - comp.unix.solaris at the ok prompt do a show net or show ... example, ksdevice=eth0, and it goes right to eth0 There is just no good ...

bootenv.rc - comp.unix.solaris
... Custom Jumpstart, etc)... i.e. the menu where you have to specify "2" to initiate Custom Jumpstart. ... network_interface=primary {dhcp protocol_ipv6=no} network_interface ...

How to configure LOM ip address on V210,V490? - comp.unix.solaris ...
... on V210, V490 machines and how to add sun-ray interfaces on ... engineer has installed the RSC Software into our Jumpstart ... sbin ../scadm set netsc_ipaddr 10.x.x.x ../scadm set ...

Ldom Issue - comp.unix.solaris
Hi, Trying to jumpstart an LDOM on T200 sun4v. I am getting the following error with my virtual network set-up. ... the interfaces to e1000g interface names ...

Solaris 10 defaultrouter: No default route is being set? - comp ...
Specify interface in Jumpstart? - comp.unix.solaris Solaris 10 defaultrouter: No default route is being set? - comp ..... created a script in /etc/rc3.d to plumb and ...

Solaris 10 issue? Failed dlopen() leaves library loaded. - comp ...
... versions of the library being loaded, and when I set ... more useful for dynamically loaded ... kind of interface ... Solaris Operating System: Solaris 10 Jumpstart tftp problem ...

Solaris ARP bug? - comp.sys.sun.admin
Quite a few examples why arp bugs have appeared are documented at the Cisco bug ... Can ping by ip but not hostname - comp.unix.solaris HSRP and Interface IP will not ...

MAILX and host/system address setup - comp.sys.hp.hpux
... ether connection setup - comp.os.vxworks MAILX and host/system address setup - comp.sys.hp.hpux remote ether connection setup - comp.os.vxworks... print network interface ...

eeprom local-mac-address? - comp.unix.solaris
I don't have hme0 set-up. Only '/etc/hostname.eri0'. ... Rich Teer's site @ rite-group.com. > The only interfaces ... address verification - comp.unix.solaris Fujitsu jumpstart ...

CDE does not start after installing Solaris 10 - comp.unix.solaris ...
Later set it manually. The month is always written ... My jumpstart install fails to open my flash archive. ... Server on Solaris 9? - comp.unix.solaris ..... interface ...

Specify interface in Jumpstart? - Database Support @ dbaspot.com ...
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 ...

Specify interface in Jumpstart? - comp.unix.solaris | Computer Group
Is it possible to tell jumpstart which interface to use, so as to avoid Using RPC Bootparams for network configuration information. Attempting to con...

7/24/2012 6:48:58 PM