Sponsored Content
Operating Systems Solaris Jumpstart issues, help please. Post 302362343 by System Shock on Thursday 15th of October 2009 05:26:55 PM
Old 10-15-2009
Wrench

Code:
127.0.0.1 localhost loghost amd1

The above entry is wrong. You need to remove it from your hosts file. 127. is not routable. /etc/hosts should look like this:

Code:
127.0.0.1    localhost
100.3.3.2    loghost amd1  # if that's your primary NIC address

As for the client "not reading" sysidcfg:
you don't mention which Solaris 10 revision you are using (I can see it is Solaris 10 from the line you posted from /etc/bootparams).
If it is u4 or higher, you need to add the following line to sysidcfg:
Code:
 nfs_domain=dynamic

If it is u7 or higher, you need to add the line above plus:
Code:
keyboard=US-English # assuming you are using an English keyboard

Otherwise miniroot will read your sysidcfg, find it incomplete, then execute the interactive config routine.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Jumpstart?

I have been asked to research Jumpstart and don't know where to begin! Any ideas would be much appreciated! Thanks! :-) (1 Reply)
Discussion started by: avana100
1 Replies

2. UNIX for Dummies Questions & Answers

JumpStart

Hi, Which sites have general information on JumpStart for Solaris 8? I would like to know more about boot server, installation server, and configuration server.... and all other good things about JumpStart....Thanks..:p Doo... (2 Replies)
Discussion started by: dookeobih
2 Replies

3. UNIX for Advanced & Expert Users

JUmpstart on a pc

HI. i was wondering if you can jumpstart using the solaris intel platform? please help thanks (3 Replies)
Discussion started by: souldier
3 Replies

4. UNIX for Advanced & Expert Users

Jumpstart

Hi, where can i find documention on how to create a jumpstart system? dori (2 Replies)
Discussion started by: dorilevy
2 Replies

5. Solaris

help with jumpstart

Hello all, I configured a jumpstart server ( the server is in the same subnet as the client) and gave boot net - install in the client. The client boots up shows the banner and then displays error: cant read disk label cant open disk label package and then goes to OK prompt. What... (1 Reply)
Discussion started by: Pratik Gharti
1 Replies

6. Solaris

Jumpstart Help

Hi Peeps, Created a jumpstart server for an unattened install and it works, but got 2 bugs in the config which I would like to work out: when you boot net install It still asks you to select a language and locale, after you do this it kicks of an unattended install. So my question is,... (5 Replies)
Discussion started by: callmebob
5 Replies

7. Solaris

Jumpstart Issues Solaris 10

I'm trying to jumpstart my remote server. My /etc/hosts and /etc/ethers files have the correct data. Keep getting the following message at the ok prompt after running a boot net - install Link hasn't comeup yet Ran a test-net and got the following message. Link is -- down When... (7 Replies)
Discussion started by: soupbone38
7 Replies

8. Solaris

Jumpstart Issues

Hi all, I'm having an issue with jumpstart that I haven't seen before. After booting the server and selecting F12 to boot it from the network it finds the jumpstart profile that has been set up for it and proceeds with the build until I get the following error: SunOS Release 5.10 Version... (4 Replies)
Discussion started by: Chains
4 Replies

9. Solaris

jumpstart installation

hi friends, i dont know how to install jumpstart . i have solaris cds( 5 nos.). i tried to install jumpstart but there is no setup_install_server file. What i want to do for installing jumpstart server please help me thanks to all (8 Replies)
Discussion started by: sijocg
8 Replies

10. Solaris

Jumpstart Issues With T5220

I'm trying to use a V210 (sun4u) configured as a jumpstart server to flash install a number of T5220's (sunv4). The Facts: V210 - Solaris 10 (September 2010 Release / not patched) T5220's - Archive's created using prior (unknown) version of solaris 10. Flar -i <archive name> shows the... (6 Replies)
Discussion started by: Celtic_Monkey
6 Replies
kdmconfig(1M)						  System Administration Commands					     kdmconfig(1M)

NAME
kdmconfig - configure or unconfigure keyboard, display, and mouse options for OpenWindows and internationalization SYNOPSIS
kdmconfig kdmconfig [-fv] [-s hostname] -c | -t | -u | -d filename DESCRIPTION
The kdmconfig program configures or unconfigures the /etc/openwin/server/etc/OWconfig file with the keyboard, display, and mouse informa- tion relevant to a client's machine on x86 based systems for Solaris software. kdmconfig can also be used to set up the display, pointer, and keyboard entries in the bootparams(4) database on a server machine or the monitor, keyboard, display, and pointer keywords in a sysid- cfg(4) file. kdmconfig can only be run by the super-user. Upon completion of device selection, kdmconfig prompts the user to test the con- figuration, which is done by running the window system. The kdmconfig program is normally run during installation and upon reboot, but it can also be run from the command line after the system has been installed. When configuring a client during an initial installation or a reconfigure reboot, the sysidconfig(1M) program will invoke kdmconfig with the -c option, and when the user executes the sys-unconfig(1M) program, kdmconfig will be executed with the -u option. Similarly, when you run kdmconfig from the command line, use the -u option to unconfigure the existing OpenWindows configuration. You can then rerun kdmconfig with the -cf options to create a new OpenWindows configuration. To edit the existing configuration, run kdm- config from the command line without options. After each reboot, kdmconfig will be invoked by the system with the -t (test mode) option to ensure autoconfiguration capability and identify possible conflicts between the current configuration and the one recorded in the OWconfig file. OPTIONS
The valid options are: -c Run the program in the configuration mode. This mode is used to create or update the OWconfig file. When invoked in this way, kdmconfig first looks for the relevant configuration information in the bootparams(4) databases. It also takes into account the information returned from device probes, unless the -s option is also used. The bootparams(4) databases avail- able to the client are all of the /etc/bootparams files on servers on the same subnet as the client, provided the server machine is running the bootparamd(1M) daemon. kdmconfig is invoked with the -c option when called by sysidconfig(1M) -d filename Set up a sysidcfg(4) file. This option displays the same screens as the -c option, but the information you specify is saved as sysidcfg(4) keywords (monitor, keyboard, display, and pointer). This enables you to use a sysidcfg(4) file to precon- figure a system's device information and bypass kdmconfig during an installation. filename is the sysidcfg(4) file that is created, and it is created in the directory where kdmconfig is being run unless a path is specified. If filename already exists in the specified directory, the keywords are appended to the existing file. -f Force screens mode. When this option is invoked, no network probing will be performed. This is helpful when debugging the client's configuration environment. Note that the -s option implies the use of -f, bypassing network probing when setting up a server. -s hostname Set up the bootparams(4) database on this machine for the specified client. This option presents the same screens as it does when run on a client, but instead writes the resulting information to the /etc/bootparams file. Also, -s implies the use of the -f option. That is, the program will always present the screens to the user when invoked this way. This option will reconfigure the nsswitch.conf( 4) file to look for a bootparams(4) database on a local server. This option is only available to the super-user. -t Run the program in test mode. In this mode, kdmconfig will use device probe information to determine whether the OWconfig file contains complete and up-to-date information about the keyboard, display, and mouse. If the information is accurate, kdmconfig will exit silently. Otherwise, kdmconfig will prompt for the super-user password and proceed to a normal editing session (as though it had been run without options). -u Unconfigure the system, returning it to an "out-of-the-box" state. In this state, the factory default keyboard, mouse, and display are selected as a result of removing the device configuration entries from the /etc/openwin/server/etc/OWconfig file. This may result in an unusable configuration for the display server. -v Enable verbose mode. Normally, kdmconfig will not produce any output. This option is helpful for debugging, as it records the different actions taken by kdmconfig on stderr. No Options Run without options, kdmconfig is used to edit the current configuration. kdmconfig uses the information from the OWconfig file in addi- tion to information obtained from the bootparams(4) file and from device probes. In other respects, it is similar to using the -c option of kdmconfig. FILES
/etc/openwin/server/etc/OWconfig OpenWindows configuration file /etc/bootparams contains list of clients that diskless clients use for booting /etc/nsswitch.conf name service configuration file x86 Only /dev/openprom installed devices and properties ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |x86 | +-----------------------------+-----------------------------+ |Availability |SUNWos86r | +-----------------------------+-----------------------------+ SEE ALSO
bootparamd(1M), sys-unconfig(1M), sysidconfig(1M), bootparams(4), nsswitch.conf(4), sysidcfg(4), attributes(5) SunOS 5.10 12 Feb 1997 kdmconfig(1M)
All times are GMT -4. The time now is 02:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy