AIX Network Commands
AIX Network Commands
In this case, the DESTINATION PACKET will go to the DEFAULT GATEWAY ADDRESS
In this case, the DESTINATION PACKET will NOT go to the DEFAULT GATEWAY ADDRESS and
will be routed within the local network.
To determine via the SUBNET MASK if a destination packet goes to the GATEWAY node or not, follow
these simple rules:
1. Perform a LOGICAL AND of the destination address of the mask of the local subnet address
2. Perform an EXCLUSIVE OR on the result of the previous operation and the local net address of the
local interface (eg., source address)
3. If the result of the previous operation is a ZERO, the destination is assummed to be reachable
directly through one of the local interfaces ELSE the packet is forwarded to the DEFAULT
GATEWAY ADDRESS.
$HOME/.netrc
The file .netrc must exist on the client that your executing the ftp or rexec command from and the
<hostname> must specify the name of server to connect to.
For FTP only, you can initiate file transfers via a macro definition (up to 16 macros can be defined). This
file resides on the client machine.
$HOME/.rhosts
Defines which client users are not required to supply a login password for the rcp, rlogin, or rsh
commands using a user account on the server. The file resides on the server machine under the home
directory of the user account being logged into. An ALIAS entry cannot be specified.
/etc/hosts.equiv
Defines which clients are permitted to execute commands by the lpd, rlogind, rcpd, or rshd daemons
without supplying a password.
syntax: <hostname>
/etc/hosts.lpd
Defines which clients are permitted to print jobs to the print server.
Displays the translation table between TCP/IP addresses and network addresses. This physical address is six
bytes long and is unique for every network board. The first three bytes of the address represent a vendor's
ID. The last three bytes are assigned by the manufacturer.
Some examples...
NOVELL 00 00 1B
NOVELL 08 00 14
3COM 02 60 8C
SUN 08 00 20
IBM 08 00 5a
DEC AA 00 04
Note that an IP address is really assigned to a network interface and not a host. A host may have more than 1
network interface as illustrated by the output of the netstat -i command.
• For example, if you are using the DOS SERVER daemons to connect PCs to the RS/6000 and
connections aren't being made, check the arp table to see if there is a hostname entry for the name of
the PC you are connecting from. If there is an entry in the arp table, then you know that packets are
getting across and the problem lies with the DOS SERVER or PC DOS CLIENT software.
• Further, you may have configured two or more hosts with the same internet address. If this is the
case, its possbile that one connection may get hung. That's because the entry in your arp table gets
overwritten by the new connection. View the arp table and you'll find that the internet address may
now be bound to a new physical network address. The connection that is hung, will not show the
correct physical address for that IP address. It shows the new physical address of the machine that
has the same IP address of the previous connection.
• Another reason to use this utility for a debugging tool is to show what network adapter card address
is mapped to an internet address. If by chance, you have two nodes on your network with the same
internet address, you will have periodic problems keeping a connection to one of those two machines
until a unique internet address is assigned to each machine.
Examples: arp -a (Displays all addresses that have been translated by the address resolution protocol.)
Outputs: dospc (193.0.0.8) at 10:0:5a:2b:69:64 [token ring]
eai1 (192.0.0.3) at (incomplete)
An incomplete entry in the network address field means the node in question could not be contacted.
Probably reasons are:
arp -d dospc (Remove the dospc entry from the arp table)
finger
Lists the current users logged in from remote machines, including username, hostname, idle time, and so on
host
This command returns the internet address when a hostname is specified or the hostname when the internet
address is specified.
nameserver (resolv.conf)
Examples What it does
host ahinc or If the arp -a or host commands hang, usually means the name server daemon
arp -a (/etc/named) is not running. Use the command ps -ef|grep named to check if named is
running.
Telnet login responce Make sure the /etc/resolv.conf file has a valid entry in it and the /etc/hosts file has the
is very slow. appropriate entries for all known client nodes.
• If a network interface shows an asterik next to it (en0*), this means your interface is
down. Use the ifconfig command to bring the network back up.
• If the Ierrs field (input errors) is nonzero, this means their are no more kernel
memory buffers left to store an incoming frame or indicates a frame error has been
detected.
• If the field Coll field has a colllision rate greater than 1% of the packets
sent/received, then a serious network problem exists.
netstat -r If the non-loopback entry has a G in Flags field (g=gateway), then the ping command may
hang. Change the Flags field to U only. Make sure the ROUTED daemon is running. To
start: startsrc -s routed.
netstat -nr Route Tree for Protocol Family 2:
netstat -sr Displays statistics for each protocol (ip, icmp, tcp, udp)
netstat -s
netstat -v Shows statistics about network interface cards installed.
• If the Xmit Carrier Lost field contains a non-zero value, you most likely have a
problem with your ethernet cable.
• The errpt command should contain entries for the eth? device where
o ? is=first ethernet adapter
o 2=second ethernet adapter, etc
• These error entries should cycle between ENT_ERR6 and ENT_ERR2 and
reference problems with the ethernet cable itself.
• Use the ping command to further identify the problem and also validate through
diagnostics that the network adapter card is good.
• XMIT MAX COLLISIONS gets bumped when the transmitter has tried to transmit a
frame 16 times and each of the 16 failed due to a collision.
• XMIT UNDERRUN gets bumped when the transmitter is getting under-runs.
• XMIT TIMEOUTS gets bumped when the transmitter on the adapter times out
while trying to transmit.
• PACKETS TOO LONG get bumped when a packet is detected that is larger than the
interface can handle (en0 of 1514+ bytes)
• RECEIVE DMA LOCKUPS gets bumped when the adapter card has detected itself
in a lockup state. The microcode will then restart the 82586 to correct this problem
and get things working again.
• INTERRUPTS LOST is the number of interrupts which are not caught by that NIC
device driver. When this counter is not 0, a problem exists with the device driver or
NIC.
• NO MBUF ERRORS is the number of failed receive MBUF requests from the NIC
device driver.
• RECV OVERRUN COUNT is stating the the NIC is getting overrun. This is not a
big problem unless you see many of these. New microcode/EPROMS may reduce
this number.
• RECV PKTS DISCARDED is stating packets are being received that can't be
matched to the TYPE field. For Ethernet cards, the type of frames being received
would only be 802.3/Ethernet Ver 2.0
• PACKETS REJECTED NO NETID is stating that a packet came in at the LLC level
and it didn't have a SAP bound to send it up to. In other words, the device driver
didn't recognize the packet type that came in. Could be because your co-existing
with a Novell network using IPX and your using TCP/IP.
netstat -v chdev -l ent0 -a receive_size=60
nfsstat
Lists statistics about network file system (NFS) and remote procedure calls (RPC). Also distinguishes
between client and server information.
no
Configures network options. The no command ONLY operates on the currently running kernel. This
command must be run each time the system is rebooted.
Sends a specified number of packets over the network and reports back performance statistics.