Ignite-UX Administration Guide for HP-UX 11i (B3921-90079, October 2013)

NOTE: Although swinstall is illustrated here, the install could use one or more of
swinstall with remsh (port 514), NFS (ports 49152–65535), ftp data (port 20), and
ftp (port 21).
Figure 29 Port Usage: Live System Reinstall
P
P
swinstall depot sequence
[Depots]
Environment
Get Install
Kernel Boot Sequence
remsh (tcp)
[bootsys_prep, OS & hardware information]
514
22
514
22
ssh (tcp)
[bootsys_prep, OS & hardware information]
Client Timeline
Server
rcp (tcp)
[*INSTALL, ISL, AUTO, HPUX, *INSTALLFS]
2049
2049
NFS (tcp/udp)
[Record log information on server]
69
tftp (udp)
[INSTCMDS, SYSCMDS]
Common to all Server-based
Installations
NFS (tcp/udp)
[Image]
2121
Live System Reinstall via bootsys from Server
or
or
Run bootsys
scp (tcp)
[*INSTALL, ISL, AUTO, HPUX, *INSTALLFS]
swinstall @ server (tcp/udp)
[Port to listen to]
ping (icmp)
swinstall (tcp/udp)
7
8
6
4
5
7. The server pings the client with an ICMP type 8 echo request. The client answers the ping with
an ICMP type 0 echo reply. Files required for bootsys are transferred from the server to the
client. These files are transferred with remsh by default, or by ssh if the bootsys -S option
is used.
8. The kernel, file system, and required files are downloaded from the server to the client, then
the client is booted. These files are transferred with rcp by default, or by scp if the bootsys
-S option is used.
NOTE:
The client can specify to use privileged ports (1–1023) or not via the ssh_config directive. The
default is non-privileged ports. If you want to configure ssh to use privileged ports, you have to
make the client an suid program.
Ignite-UX Server Ports 87