Figure 28 Port Usage: Client Cold Boot and Installation
Client Cold Boot and Installation
Initiated from Client Firmware
Client | Timeline | Server |
Initiate LAN Boot - see the diagram for your hardware
Download and | Boot Kernel |
based |
|
tftp (udp)
[Initial boot content]
69 3
Server- |
all |
NFS (tcp/udp)
2049
[Record log information on server]
tftp (udp)
4
69
[INSTCMDS, SYSCMDS]
NFS (tcp/udp)
[Image]
2049 5
swinstall depot sequence
swinstall @ server (tcp/udp)
2121
|
| [Port to listen to] |
|
|
|
| 6 | ||||
|
|
| |||
|
| swinstall (tcp/udp) |
|
|
|
P | P |
|
| ||
| [Depots] |
|
| ||
|
|
|
|
| |
|
|
|
| ||
3.The initial boot content (kernel, file system, and required files) is downloaded from the server to the client, then the client is booted. For
4.The file install.log is updated on the server in the /var/opt/ignite/clients/client directory. A compressed tar archive of commands to set up disk volumes and file systems is downloaded (INSTCMDS for
5.If the installation is from an image, it is downloaded. Ports used by NFS to make RPC calls are not discussed here.
6.If the installation configuration requires software to be installed from depots on the server, a swinstall request is sent to the server's Software Distributor (SD) daemon, swagentd, on port 2121. An SD agent, swagent, is then spawned on the server that acquires a dynamically allocated communication port for the download. That communication port is then reported to the client on port 2121. The client then spawns a new swagent processes that communicates with the server on the acquired communication port P, where the depot download takes place. For more information on SD, see the Software Distributor Administration Guide available at
86 Security