Startup Flow

The events that take place when the SSP boots are as follows:

1. User powers on the SSP (monitor, CPU/disk, and CD-ROM). The SSP boots automatically.

2. During the SSP boot process, the /etc/rc2.d/s99ssp startup script is called when the system enters run level 2. This script starts ssp_startup, which is responsible for starting other SSP daemons. If any of these SSP daemons die, ssp_startup restarts them.

3. ssp_startup first initiates the following SSP daemons on both the main and spare SSP: machine_server, fad, and fod. The fod daemon determines the role of the SSP by first querying the fod daemon on the other SSP. If this query is not successful, fod will connect to the control board to determine the SSP role.

   If the SSP is the main, ssp_startup also initiates the following daemons: datasyncd, cbs, straps, snmpd, edd, and if domains are running, obp_helper and netcon_server. ssp_startup also calls cb_reset to start control board initialization. The control board server (CBS) connects to the primary control board, which is responsible for the JTAG interface.

   If the SSP is the spare, ssp_startup is complete.

   ssp_startup monitors the role of the SSP. If a role change is detected, ssp_startup initiates an SSP failover. After the failover, ssp_startup will configure the spare SSP as the new main SSP and initiate the daemons (listed above) needed for the new main SSP.

4. When you get a message in the platform message file indicating that the startup of the SSP as the main or spare is complete, you can use SSP 3.5 commands such as domain_create(1M) or bringup(1M).