Some helpful network trouble shooting commands.

Use netconfig (or scoadmin and pick 'Network Configuration Manager') to setup a TCP/IP, NFS, IPX connection. netconfig is also used to setup and configure the various network cards.

Once the board is recognised some commands:

ping Check basic connectivity:
ping localhost will check out the basic tcp/ip setup on the local machine.
ping <machine> e.g. ping bdsedin this will check out the connection to the remote machine.
arp -a This will show you the MAC and IP addresses that have been detected trying to talk to this machine.
netstat -r This lists the routing tables
netstat -m If there have been any failures on the different classes.
rlogin <site> Login remotely to site <site>
telnet <site> Start a telnet connection to <site>
If user equivalence has been set up then the following can be used:
rcp Remote copy, same syntax as cp but you include the sitename e.g
rcp server-name:/tmp/file . Copy the file /tmp/file from machine servername to the current directory of the local machine.

rcmd Run a command on the remote machine e.g.
rcmp bdsl who Run the command who on the machine bdsl and display the output on the local machine.

ping	Check basic connectivity:
	ping localhost will check out the basic tcp/ip setup on the local machine.
	ping <machine> e.g. ping bdsedin this will check out the connection to the remote machine.
arp -a	This will show you the MAC and IP addresses that have been detected trying to talk to this machine.
netstat -r	This lists the routing tables
netstat -m	If there have been any failures on the different classes.
rlogin <site>	Login remotely to site <site>
telnet <site>	Start a telnet connection to <site>
If user equivalence has been set up then the following can be used:
rcp	Remote copy, same syntax as cp but you include the sitename e.g rcp server-name:/tmp/file . Copy the file /tmp/file from machine servername to the current directory of the local machine.
rcmd	Run a command on the remote machine e.g. rcmp bdsl who Run the command who on the machine bdsl and display the output on the local machine.

There are other commands but these should allow you to troubleshoot and configure a TCP/IP link. Refer to the on-line manual 'Network Documentation set' for the full syntax of the commands and other trouble shooting tips.

Files:

/etc/hosts Host table which MUST be correct
/etc/hosts.equiv Which user has equivalence on which machine
$HOME/.rhosts Personel equivalence file
/etc/default/tcp TCP/IP setup file
/etc/tcp Start up/stop tcp
/etc/exports List of filesystems that can be exported with nfs.

/etc/hosts	Host table which MUST be correct
/etc/hosts.equiv	Which user has equivalence on which machine
$HOME/.rhosts	Personel equivalence file
/etc/default/tcp	TCP/IP setup file
/etc/tcp	Start up/stop tcp
/etc/exports	List of filesystems that can be exported with nfs.

Recovering a networked machine - If an OSR 5 box goes down, rather than restore the whole lot via tape/CD you can use the network install version. This is detailed fully in the OpenServer Release 5 Handbook which is shipped with every copy of OSR 5.

Support Guide

Some helpful network trouble shooting commands.