[ Team LiB ] Previous Section Next Section

Checking on Remote System Status

This section describes commands you use to find out the status of remote systems: rup, ping, and rpcinfo -d.

Determining How Long a Remote System Has Been Up (rup)

To find out how long a system has been up and to determine the load average, type rup system-name and press Return. The host name, uptime, and load average are displayed.


oak% rup ash
ash    up 59 days,   3:42,   load average:  0.12,  0.12,  0.01
oak%

You can also display a list of all remote hosts in the subnet by typing rup and pressing Return. If you display a list, you can use the options shown in Table 78 to sort the output.

Table 78. Options to the rup Command

Option

Description

-h

Sort the display alphabetically by host name.

-l

Sort the display alphabetically by load average.

-t

Sort the display by uptime.

In the following example, the output is sorted alphabetically by host name.


oak% rup -h
ash    up  1 day,   1:42,   load average: 0.00, 0.31, 0.34

elm    up 14 days,  0 min,  load average: 0.07, 0.01, 0.00

maple  up 32 days,  14:39,  load average: 0.21, 0.05, 0.00

oak    up  8 days,  15:44,  load average: 0.02, 0.00, 0.00
oak%



Determining Whether a Remote System Is Up (ping, rup, rpcinfo -p)

Use the following steps to determine whether a remote system is up and to log in to the remote system.

  1. Type ping system-name and press Return.

    The message system-name is alive means the system is accessible over the network. The message ping: unknown host system-name means the system name is not known on the network. The message ping: no answer from system-name means the system is known on the network but is not up at this time.

  2. Type rup system-name and press Return.

    Information about how long the system has been up and the load average is displayed.

  3. Type rpcinfo -p system-name and press Return.

    Information about RPC services is displayed.

  4. Type rlogin system-name and press Return.

    You are logged in to the remote system.


cinderella% ping drusilla
drusilla is alive
cinderella% rup drusilla
   drusilla    up  3 days,  15:10   load average: 0.07, 0.08, 0.09
cinderella% rpcinfo -p drusilla
program  vers proto port  service
100000    3   udp    111  portmapper
100000    2   udp    111  portmapper
100000    3   tcp    111  portmapper
100000    2   tcp    111  portmapper
100007    3   tcp   1029  ypbind
100007    3   udp   1025  ypbind
100021    1   tcp   1030  nlockmgr
100021    1   udp   1026  nlockmgr
100024    1   tcp   1028  status
100024    1   udp   1027  status
100021    3   tcp   1030  nlockmgr
100021    3   udp   1026  nlockmgr
100020    2   tcp   4045  llockmgr
100020    2   udp   4045  llockmgr
100021    2   tcp   1030  nlockmgr
100021    2   udp   1026  nlockmgr
100087   10   udp   1031  adm_agent
100011    1   udp   1034  rquotad
100002    1   udp   1037  rusersd
100002    2   udp   1037  rusersd
100012    1   udp   1041  sprayd
100008    1   udp   1043  walld
100001    2   udp   1046  rstatd
100001    3   udp   1046  rstatd
100001    4   udp   1046  rstatd
100068    2   udp   1049  cmsd
100068    3   udp   1049  cmsd
100083    1   tcp   4049
cinderella% rlogin drusilla
Password:
Last login: Mon Mar  2 10:31:55 from cinderella
drusilla%

You can also use ping with a system's IP address by typing ping IP-address and pressing Return. The message IP-address is alive means the system is accessible over the network. The message ping: no answer from IP-address means the system is not available to the network. The message ping: unknown host IP-address means the system name is not known on the network.


oak% ping 129.144.52.119
129.144.52.119 is alive
oak% ping 129.137.67.234
ping: unknown host 129.137.67.234
oak% ping 129.145.52.119
ping: no answer from 129.145.52.119
oak%



    [ Team LiB ] Previous Section Next Section