NAME

init_attach - initiate a DR attach operation

SYNOPSIS

init_attach sb

AVAILABILITY

Sun Enterprise 10000 servers only.

DESCRIPTION

Execute this command at the dr (1M)shell prompt to begin a DR Attach operation. The system board to be attached must be present, powered-on, and currently in no domain. It is diagnosed and debuted to the Enterprise 10000 target domain specified by the SUNW_HOSTNAME environment variable. Upon completion of the init_attach, the board's resources - processors, memory, and I/O controllers - are prepared for attachment by the operating system. The board is added to the board list in the SSP's domain_config(4) file, and the Enterprise 10000 centerplane is reconfigured such that the board is visible to the target domain.

Upon successful completion of init_attach you can use complete_attach(1M) to complete the attach operation or abort_attach(1M) to abort it.

OPTIONS

sb

The board number (0 to 15) of the system board to be attached.

EXIT STATUS

If successful, init_attach returns a 0 in the dr_return global variable; if not, it returns a 1, along with one or more diagnostic messages.

EXAMPLE

ts4-ssp% domain_switch ts4

ts4-ssp% dr
Checking environment...
Establishing Control Board Server connection...
Initializing SSP SNMP MIB...
Establishing communication with DR daemon...

        ts4: System Status - Summary

BOARD #: 5 physically present.
BOARD #: 1 3 4 being used by the system.

dr> init_attach 5

Initiate attaching board 5 to domain ts4.
Adding board 5 to domain_config file.
/opt/SUNWssp/bin/hpost -H20,4
Opening SNMP server library...

Reading centerplane asics to obtain bus configuration...
Bus configuration established as 3F.
phase cplane_isolate: CP domain cluster mask clear...
phase init_reset: Initial system resets...
phase jtag_integ: JTAG probe and integrity test...

phase mem_probe: Memory dimm probe...
phase iom_probe: I/O module type probe...
phase jtag_bbsram: JTAG basic test of bootbus sram...
phase proc1: Initial processor module tests...
phase pc/cic_reg: PC and CIC register tests...
phase dtag: CIC DTAG tests...
phase mem: MC register and memory tests...
phase io: I/O controller tests...
phase procmem2: Processor vs. memory II tests...
phase lbexit: Centerplane connection tests...
phase final_config: Final configuration...
Configuring in 3F, FOM = 1024.00: 4 procs, 2 SCards, 1024 MBytes.
Creating OBP handoff structures...
Configured in 3F with 4 processors, 2 SBus cards, 1024 MBytes memory.
Interconnect frequency is   83.273 MHz, from SNMP MIB.
Processor    frequency is 166.589 MHz, from SNMP MIB.
Boot processor is 5.0 = 20
POST (level=16, verbose=20, -H4,0020) execution time 3:50
hpost is complete.
obp_helper -H -m20
Board debut complete.
Reconfiguring domain mask registers.
Probing board resources.
Board attachment initiated successfully.

Ready to COMPLETE board attachment.

dr>

init_attach ( 1M ) DIAGNOSTICS

add_board_to_domain returns entry not found

The target domain specified by the SUNW_HOSTNAME environment variable is not properly listed in the domain_config(4) file. Check the domain_config(4) file, then try the operation again at a later time.

add_board_to_domain returns entry not found
Unable to locate domain target domain in domain_config file.

DR was unable to locate an entry for the current target domain. Use the domain_status(1M) command to verify the contents of the domain_config(4) file. See the Ultra Enterprise 10000 SSP Reference Manual.

Board debut failed - return = value

The debut utility has failed (see obp_helper(1M) in Ultra Enterprise 10000 SSP Reference Manual). Consult the SSP message files for information regarding the failure.

Board brd is a member of a foreign hardware domain.

The board you are trying to attach has been identified as a member of another domain on this platform, which prevents it from being attached to the designated target domain. You must remove this board from the other domain before initiating an attach.

Board brd is not eligible for attach

One or more conditions is preventing this board from being attached to the target domain. The board must be physically present, powered on, and not a member of any domain to be eligible for attachment.

Board may be Black or Red listed.
        If this board is blacklisted or redlisted, it cannot be attached. Check the postrc(4)
        file for the location of the blacklist(4) and redlist(4) files.
DR Error: State for board brd can't be determined.

During initial domain contact an unexpected board condition was detected by dr_daemon(1M). (See dr_daemon(1M) in the Solaris Reference for SMCC-Specific Software.) Check the system log on the host for more information.

Error executing command

dr (1M)executed the indicated command, but it returned a failure indication. If the error message specifies a specific action you must take, do so, then retry the command. Otherwise, simply retry the init_attach operation at a later time. If that attempt fails, call your service provider.

FAD error detected, retrying...

A transient failure occurred during updating of the domain_config(4) file has been. init_attach will retry the operation. If all retries fail, consult the SSP messages files for more information.

Failed to initiate board attachment
        The init_attach operation on the target domain has failed.
Unable to execute command

dr (1M)could not execute the indicated command. Check that the program file exists and is assigned the appropriate modes.

NOTES

If DR detects a usage syntax error, it immediately aborts the dr (1M)command, displays the dr (1M)shell prompt, and leaves dr_return unmodified. See dr (1M).

SEE ALSO

dr (1M)in this Reference Manual

blacklist(4), domain_config(4), domain_status(1M), domain_switch(1M), postrc(4), redlist(4) in Section 4 of the Ultra Enterprise 10000 SSP Reference Manual

dr_daemon(1M) in the Solaris Reference for SMCC-Specific Software