NAME | SYNOPSIS | DESCRIPTION | OPTIONS | ENVIRONMENT VARIABLES | SEE ALSO
bringup executes the following steps to boot the domain specified in the SUNW_HOSTNAME environment variable. If any step fails, bringup displays an error message and aborts.
Executes the power(1M) command to check whether the domain is powered on. If so, bringup proceeds; if not, it displays a message instructing the user to turn on power to the domain, then aborts. Note that if -f is used, bringup does not execute the power(1M) command.
Executes check_host(1M) to determine whether the domain is already up. If not, bringup boots the domain. If the domain is already up, bringup displays a message to that effect and asks if it should continue. Type n and it aborts; type y and it asks if you are executing bringup because of a hung domain. Your response to this question is recorded for problem-tracking purposes only; in either case, bringup boots the domain.
Checks whether any other domains are up, or being brought up, to determine whether it should execute hpost(1M) with or without the -C (configure centerplane) option in the next step. If another domain is being brought up and is configuring the centerplane, this instance of bringup waits until that domain has finished configuring the centerplane, then proceeds. If no other domains are up or being brought up, bringup displays a message informing you that it intends to configure the centerplane, and asks you whether it should proceed. (If you specified -f on the command line, bringup continues without this message.)
If you type y, bringup configures the centerplane and continues. If the centerplane is already configured - for example, due to an earlier domain that no longer exists - it is reconfigured. No harm is done, but bringup might take a little longer.
If you type n and the centerplane is already configured, bringup continues without reconfiguring the centerplane.
If you type n and the centerplane is not already configured, hpost(1M) most likely will fail.
Note: If no domains are up and you do not know whether the centerplane is configured, the safest response is y.
At this point bringup determines whether the domain was created with a version earlier than the Solaris 2.6 operating environment. If so, bringup skips the next step and proceeds to Step 5. Otherwise, it executes the next step, then Step 5.
Executes domain_unlink(1M) on the respective domain to verify that it is not a member of an IDN.
bringup displays the following message during this period, which can take several seconds depending on the size of the domain's respective IDN and the state of those domain members:
Checking domain IDN configuration...
When this operation is completed, bringup displays the word done.
If an error occurs during the IDN operation, bringup displays error along with the captured output of the domain_unlink(1M) command. If another IDN operation is in progress at the time, it displays busy, then waits for the previous IDN operation to complete.
If the domain_unlink(1M) command fails because multiple IDN members are in unknown states, you may have to execute it manually to unlink those domains using a single command prior to performing the bringup.
Note that the unlinking of the domain from its respective IDN is a transient condition; the MIB is not updated. Once the domain boots, if the proper IDN software is present the SSP Event Detection Daemon, edd(1M), will detect the availability of the domain and automatically perform a domain_link(1M) to reconnect the domain to its IDN.
Executes hpost(1M) with its -C option to configure the centerplane then the domain, or without it to configure just the domain.
Starts obp_helper(1M) and netcon_server(1M) to proceed with the OBP and operating system boot sequence and set up the network console.
Updates the MIB according to the final domain configuration.
bringup also sets the system clock and clock source for the first domain before bringing it up.
The following options are supported:
Force execution, even if the domain is already up.
Warning: bringup passes -C to hpost(1M) when appropriate, regardless of whether you specify it on the bringup command line. However, if you specify -f with -C, bringup passes -C even if one or more other domains are up, causing those other domains to be reset. Therefore, be extremely careful about specifying -C and -f together. If you do use -f, bringup does not check whether the domain is powered up.
Do not use this option on the command line. It is reserved for automatic reboot scripts; see edd(1M).
Print a brief description of bringup command line options.
Send a request for hpost(1M) to execute a faster, limited version of POST.
Do not execute -Q on the command line. It is invoked by the SSP software (see edd(1M)) when a domain reboot is requested as a result of the uadmin(2) system call (which is used by the reboot(1M), uadmin(1M), shutdown(1M), and init(1M) commands) or a reset initiated by an OpenBoot. Depending on the state of the domain, manual use of bringup -Q might cause a bringup failure.
Send a request for hpost(1M) to use its -s and -v20 options, sending all output to the syslog.
Send a request for hpost(1M) to use its -v70 option, which produces more detailed information.
bringup passes this option to netcon_server(1M).
bringup assumes that arguments other than those described above are boot arguments and passes them to obp_helper(1M), which passes them verbatim to the OpenBoot boot(1M) command. All boot_args that take on additional arguments must be enclosed within a pair of quotes. For example,
bringup "kadb -d"
Arguments after "- -" are always passed to obp_helper(1M). This is useful for arguments that conflict with bringup(1M) arguments or for names that begin with a "-". For example, both of these commands are equivalent and the -D argument is passed to obp_helper(1M).
bringup -D
bringup - - -D
bringup passes these options to hpost(1M).
bringup(1M) passes these options to obp_helper(1M).
The environment variable SUNW_HOSTNAME must be set to the name of the domain.
check_host(1M), domain_unlink(1M), hpost(1M), netcon_server(1M), obp_helper(1M), snmpd(1M)
boot(1M) in the SunOS Reference Manual
NAME | SYNOPSIS | DESCRIPTION | OPTIONS | ENVIRONMENT VARIABLES | SEE ALSO