Figure 30 Port usage: make_net_recovery initiated from the client
make_net_recovery Initiated from Client
check_version
| Client |
|
| Timeline | Server | ||||
|
|
|
| ping (icmp) |
|
|
|
| |
|
|
|
|
|
|
| |||
|
|
|
| tftp (udp) |
|
|
| 9 | |
|
|
|
| 69 |
| ||||
|
|
|
| [/opt/ignite/data/Version from server to client] |
|
| |||
|
|
|
| swlist@server (tcp/udp) |
|
|
| ||
|
|
|
| 2121 |
|
| |||
|
|
|
|
|
|
|
|
| |
|
|
|
| [Port to listen to] |
|
| 10 | ||
|
|
|
|
|
| ||||
|
|
|
|
|
|
|
|
| |
|
|
|
| (tcp/udp) |
|
|
| ||
|
| P n |
| P n |
|
| |||
|
|
| [Output of swlist] |
|
| ||||
|
|
|
|
|
|
| |||
|
|
|
| swinstall (tcp/udp) |
|
|
| ||
|
|
|
| 2121 |
|
| |||
|
|
|
|
|
|
|
|
| |
|
|
|
| [Port to listen to] |
|
|
| ||
|
|
|
|
|
| 11 | |||
|
|
|
| swinstall (tcp/udp) |
|
| |||
|
| P n |
| P n |
|
| |||
|
|
|
|
|
|
|
| ||
|
|
|
|
| |||||
|
|
|
|
|
|
| |||
|
|
|
|
|
|
|
|
|
|
|
|
|
| NFS (tcp/udp) |
|
|
|
| |
|
|
|
| 2049 | 5 | ||||
|
|
|
| [Recovery image] | |||||
|
|
|
|
|
|
| |||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
9.The server pings the client with an ICMP type 8 echo request. The client answers the ping with an ICMP type 0 echo reply. If tftp is enabled, the version check is done with the file /opt/ ignite/data/Version.
10.If tftp is not enabled, the version check is done with swlist using the swinstall depot sequence described in Figure 28 (page 86).
11.If the client has a lower version of Ignite than the server, a depot of recovery commands is transferred to the client using the swinstall depot sequence described in Figure 28 (page 86).
NOTE: Although swinstall is illustrated here, the install can use one or more of swinstall with remsh (port 514), NFS (ports
88 Security