Hi,
Thanks for the help.
This is an issue faced by a customer and I have told him to make these
changes.
He is using JET and he wants to make the changes manually.
He has tried both, by setting the value inside his template/vmclient
file and also by changing the menu.lst.<MAC> manually.
This is how his menu.lst.<MAC> file entry looks like:
menu.lst.010016366DBD85: kernel /I86PC.Solaris_10-8/multiboot
kernel/unix - install -B
console=ttyb,input-device=ttyb,output-device=ttyb,install_config=
129.148.53.204:/opt/jet,sysid_config=129.148.53.204:/opt/jet/Clients/gdg-74
,install_media=129.148.53.204:/export/install/media/Solaris_10u2.NGE
,install_boot=129.148.53.204:/export/install/media/Solaris_10u2.NGE/boot
Here is what is says, about the problem:
My server is both the jumpstart server and the dhcp server for our lab.
The issue is that for Solaris 10 update 2, there are additional files that
need to be edited. Editing these files, after the OS has been installed
works. And by works, I mean that after editing the files, and rebooting the
system, the console output goes out ttyb. My issue is that if you want the
jumpstart console output to go out ttyb, what files do you need to edit?
So, he is not able to get the jumpstart console output onto ttyb.
Is there anything more that needs to be done to get this working?
Regards,
Narendra
On 12/8/06, Sean McGrath - Sun Microsystems Ireland <sean.mcgrath at sun.com>
wrote:
>
> Dave Miner stated:
> < Narendra Kumar S.S wrote:
> < >Hello,
> < >
> < > If I am using add_install_client, I can use -b option to specify
> < >the serial console on an x86 machine.
> < > If I want to do this manually, which are the files that I need to
> < >modify?
> < > And do I need to execute any command after making the
> modifications?
> < >
> <
> < The man page on add_install_client has a clue:
> <
> < -b property=value
> <
> < Set a property value in the client specific bootenv.rc
> < file located on the boot server's TFTP directory,
> < /tftpboot by default. Use this option to set boot pro-
> < perties that are specific to this client. You can use
> < the bootpath property to automate the selection of the
> < boot device instead of manually using the Device Confi-
> < guration Assistant. You can use the boot-args property
> < to automatically select a jumpstart installation. See
> < eeprom(1M).
> <
> <
> < It could be more explicit, but typically you're looking for a file of
> < the form:
> <
> < /tftpboot/<dhcp client id>.bootenv.rc
>
> The <dhcp client id>.bootenv.rc hasn't been used since S10FCS ?
> Since things went the way of grub and a miniroot archive.
>
> Instead of the bootenv.rc file, theres the /tftpboot/menu.lst.<dhcp
> client id>
> file. You still have the '-b property=value' but it puts the settings
> in
> the menu.lst file. eg:
>
> tftpboot# cat menu.lst.0100C09FF4693F
> default=0
> timeout=30
> title Solaris_10 Jumpstart
> kernel /I86PC.Solaris_10-88/multiboot kernel/unix - install
> dhcp -B console=ttya
> module /I86PC.Solaris_10-88/x86.miniroot
> tftpboot#
>
> You don't need to do this manualy, add_install_client does the job.
> Regards,
>
> <
> < <dhcp client id> is, by default, constructed as a hex string consisting
> < of the media type code ("01" for Ethernet) plus the network interface
> < MAC address; it must be all-caps and must be zero-filled. So for
> < example, a system with an Ethernet network interface MAC address of
> < 0:a:e4:34:30:7 would have a DHCP client id of 01000AE4343007.
> <
> < And no, you don't need to run any commands after modifying the
> < bootenv.rc file; it will be automatically downloaded with tftp on the
> < next attempt to network boot the client.
> <
> < Dave
> < _______________________________________________
> < install-discuss mailing list
> < install-discuss at opensolaris.org
> < http://opensolaris.org/mailman/listinfo/install-discuss
>
> --
> Sean.
> .
>
--
Warm Regards,
Narendra
Visit my blogs at:
http://ssnarendrakumar.blogspot.com/
http://blogs.sun.com/roller/page/ssnkumar
___ ___ __ _
/ __/ / __/ / | / /
_\ \ _ \ \ / /| |/ /
\___/ \___/ /_/ |__/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/install-discuss/attachments/20061208/c849a8d0/attachment.html>
