Ignite


 
Thread Tools Search this Thread
Operating Systems HP-UX Ignite
# 8  
Old 10-14-2016
Either your D class had the FWSCSI controller option giving you hot swap disks but only 2 disk internal allowed or you had standard on hot swap but could have up to 5 disks in it... Trying to find Ignite-UX to reinstall WILL NOT solve you issue as so far I see no proof Ignite isnt working but as I said above you have a system issue, I have been helping CERN to maintain the running D classes they had so I know what kind of message you get when things go wrong, you dont want to answer what you have been asked, I think its time to close the thread so others dont loose their time too
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. HP-UX

Error with ignite

Works all. Depot shared via nfs dhcp working setting file system,network,root password,etc But when i start "go!" with installation,give me this error. How to fix,debug? Thanks http://s24.postimg.org/5hzbgk551/unixbell3.png (3 Replies)
Discussion started by: Linusolaradm1
3 Replies

2. HP-UX

Ignite - make_net_recovery

I've read the Ignite User/Admin Guide but I'm having trouble figuring out if I can do a make_net_recovery if the ignite server and client server are on completely different networks? If this can be done is there any special configuration? If I initiate the command from the server it looks like it... (3 Replies)
Discussion started by: gonzotonka
3 Replies

3. HP-UX

Ignite and HP-UX 09.XX

I am looking to make bootable tape backups of four machines running HP-UX 09.02, 09.05 and 09.07. I successfully located Ignite 10.20 and installed it and made a backup on the one machine running HP-UX 10.20. I am having trouble locating information about Ignite for HP-UX 9. Does it exist? Is... (3 Replies)
Discussion started by: whack_job
3 Replies

4. AIX

ignite equivalent in AIX

Hi All, Does AIX has utility like ignite server to make remote os installation using image (2 Replies)
Discussion started by: jayannair
2 Replies

5. HP-UX

vpar ignite

Hi Can I use a vpar as an ignite server? (1 Reply)
Discussion started by: mahlathini
1 Replies

6. HP-UX

Need Ignite for HP-UX 10.20

Hello All, I need to bring down our old 9000 series d350, but my supervisor wants an ignite backup created. I cannot find ignite in the usual places (/opt/ignite) nor can I find it in swlist. As far as I can tell the cd's are long gone. Is there anywhere else I could look for ignite being... (6 Replies)
Discussion started by: stay0ut
6 Replies

7. HP-UX

HP-UX Ignite server

Sorry if this has been asked and answered, but I can't find this particual problem. I've had an Ignite server running for years on a small internal network with images we load on daily basis. Tried to load two servers, L2000 and C3600 , both with same problem. # boot lan.192.168.2.2 install ... (0 Replies)
Discussion started by: ddeblance
0 Replies

8. HP-UX

make_sys_image + Ignite problem

could any one help me I have a HP UX 11.0 with a lot of VG and disks connected to SAN. I need to create a Golden Image having only the vg00 of this system. How do i do this using make_sys_image? In case any have some docs, I would appreciate if You could share it. Thanks Dhanish (5 Replies)
Discussion started by: i2admin
5 Replies

9. UNIX for Advanced & Expert Users

without an ignite server ??

system: HP-UX 10.20 with HFS mounted. How can I convert the HFS to VxFS without an ignite server ? Is this possible ? thanks simon2000 (4 Replies)
Discussion started by: simon2000
4 Replies

10. HP-UX

ignite tapes

can any1 tell me how to make ignite tapes for the HP-ux. this company said it was: "make_tape_recovery_A", but that don't work. (4 Replies)
Discussion started by: JBX
4 Replies
Login or Register to Ask a Question
set_parms(1M)															     set_parms(1M)

NAME
set_parms - set system initial identity parameters: hostname, date/time, root password, and networking SYNOPSIS
DESCRIPTION
The command is an interactive system set-up command that allows you to specify various "initial identity parameters" when first booting a newly installed operating system (whether preinstalled, or installed locally from media or an install server), and to revise these parame- ters later on a running system. Initial identity parameters are a minimal set of values required to bring a system to an initially useful state. They include the following: o system hostname o timezone for the system's location o date and time o root password o IP address, netmask o routemask, routing gateway, DNS, and NIS information o local language In a first-boot situation, is invoked automatically by For purposes, "first-boot" is defined as having no hostname set when the system starts up. This causes to step through all of its sub-areas to help you set all of the initial identity parameters. After the system has booted and is running, may also be called directly from the command line to step through all areas (via similar to how it works at first-boot, or to finish setting up a particular sub-area (the latter forms above). There are certain limitations to its actions when it's run after first-boot, as described see below. Note: The command only sets the root (superuser) password during "initial" processing, and then only if it is not already set. If so, it uses the command, so the effect is immediate. See the passwd(1) manpage. The command is also DHCP-aware. If you attempt to change DHCP-supplied data such as the hostname or IP address, issues a warning. If you continue with the changes, relinquishes the DHCP lease. On first-boot, asks if you would like to try getting set-up data from a DHCP server. However invoked, the command often knows and provides default values for many of the initial identity parameters, based on values specified to Ignite-UX in a previous or recent installation of the system or found in system configuration files. The command can be run only by the user with appropriate privilege. Options Each sub-area of is described below. In a first-boot situation all of the sub-areas are run sequentially. Special first-boot behavior is noted below if applicable, along with any special cases when invoking on a running system. When calling a sub-area directly, only a unique portion of the sub-area name is required to be given; for example, This allows the user to sequentially invoke all the sub-areas mentioned below. The user can configure multiple interfaces which are physically connected to the network using the Termi- nal User Interface (TUI). A in the user interface field indicates a lan which is not physically connected to the network. If lan interfaces are configured as DHCP, the options and are skipped. Set the system hostname: Validates a user-supplied hostname according to host-naming conventions and sets various system initialization variables to operate with that hostname. Particularly, edits to associate the new hostname with the current IP address of the system, if that can be determined. Note: It does not notify DNS (Domain Name Servers), etc. This higher level of configuration is handled later by broader configuration tools. WARNING: When changing the hostname, does not know about optionally-installed software. If any such software remembers the previous hostname, it might not work properly after the hostname is changed. A mechanism is provided that helps generalize the hostname changing function. The command calls, in sorted order, any exe- cutable commands found in the directory This occurs for both first-boot and non-first-boot calls. HP may in the future sup- ply special commands in this location. The system administrator may also supply custom commands (programs or scripts) for site installations using, for example, Ignite-UX. The system must be rebooted for any change to take full effect. Select a timezone based on your country of location. Also allows you to set a user-supplied timezone. The system must be rebooted for any change to take effect. Set the system date and time interactively: This is similar to calling as a privileged user, but without having to format a time specification string. The change takes effect immediately. Set or change the IP address and subnet mask for the system. This function edits the file to associate the new IP address with the current hostname. Note: it does not notify DNS (Domain Name Servers), etc. This higher level of configuration is handled later by broader configuration tools. If multiple lan interfaces are present, the user can select each LAN interface (network interface card or NIC) separately to configure it. The system must be rebooted for any change to take effect. Set the route mask (which defines the network and local subnet portions of a network address), set the routing gateway, and define access to the Domain Name System (DNS) and Network Information Service (NIS). First-boot: These changes take effect immediately, without a reboot, because starts networking after setting the parameters. Non-first-boot: A reboot is required for all of these changes to take effect. Allow the user to set the local language settings. The user can either select one of the languages from the menu or they can set new valid language. will verify whether the new language is installed. If it is not installed, the user must install the language before executing this option. set_parms, Ignite-UX or Cold Install After "cold-installing" HP-UX from tape, CD-ROM, or DVD, or using Ignite-UX to install HP-UX from any source including an install server, the file is generally left on the system. This file is used to communicate to and other tools the hostname, networking, and other informa- tion that was used during the installation, to make it easier to use any of these values as final system parameters. In particular, uses as defaults the shell-style variables in this file that begin with For example, indicates which LAN interface was used during a network cold install. This is the LAN interface that configures. In general, first looks in for default information, then in the system configuration files in the directory. If any parameter is defined in both locations, the latter takes precedence. If Ignite-UX is installed on your system, see the manpage entries for ignite(5) and instl_adm(4). In particular, read instl_adm(4) for descriptions of the and variables. Interaction with auto_parms During the boot-up sequence, always invokes which in turn detects the first-boot situation and it calls if either or both of these condi- tions are true. The starts its interface and, based on user input, might call back into to obtain and set up the management of a DHCP lease. After completes this and other system set-up tasks, control passes back to which completes the boot-up sequence using the newly- created system initial identity parameters. See the rc(1M) manpage for information about for invocation context in the first-boot case. If the system has multiple lan interfaces and the user wishes to configure some with DHCP and others with static IP, the user must invoke first to configure all the lan interfaces which they wish to configure as DHCP. The user should not allow the system to be rebooted while doing this configuration. Then the user should invoke to configure the remaining lan interfaces. also allows the user to specify the DHCP server from which to get hostname and networking parameters and Class ID. If multiple interfaces are configured with DHCP, there is a chance that multiple hostnames will be returned through different DHCP enabled lan interfaces. If hostname is not set in and none of the interfaces are configured with addresses, then the hostname returned by the interface is updated in FILES
The command itself. Common subroutines used by and the sub-area commands. Directory holding all of sub-area commands called by which runs them in sorted order. Directory containing any hostname-change commands defined by the user. These are standalone commands run, in sorted order, by when setting or changing the hostname. File set by Ignite-UX or Cold Install that contains networking and other system information used during the installation. System configuration files modified by AUTHOR The command was developed by HP. SEE ALSO
passwd(1), auto_parms(1M), dhcpdb2conf(1M), rc(1M), instl_adm(4), ignite(5). set_parms(1M)