21.02.2013 Views

AIX 5L Problem Determination - IBM Redbooks

AIX 5L Problem Determination - IBM Redbooks

AIX 5L Problem Determination - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

► The host must be reached by a distant gateway (a gateway that is on a<br />

different autonomous system than the source host). The RIP can be used<br />

only among hosts on the same autonomous system.<br />

If you are using dynamic routing, you should not attempt to add static routes to<br />

the routing table using the route command.<br />

As a very last resort, you may flush the routing table using the route -f<br />

command, which will cause all the routes to be removed and eventually replaced<br />

by the routing daemons. Since any networking that was functioning before will be<br />

temporarily cut off once the routes are removed, be sure no other users will be<br />

affected by this.<br />

If your system is going to be configured as a router (it has two or more network<br />

interfaces), then it needs to be enabled as a router by the no command. The<br />

network option that controls routing from one network to another is ipforwarding<br />

and by default is disabled. To enable it, enter:<br />

# no -o ipforwarding=1<br />

This is not a permanent setting and after the next system reboot it will be lost. To<br />

make this permanent, add this command to the end of the /etc/rc.net file.<br />

Note: When you add the second network interface to your system, a new<br />

entry will appear in the routing table. This is a route associated with the new<br />

interface.<br />

8.3 Name resolution problems<br />

If network connections seem inexplicably slow sometimes but fast at other times,<br />

it is a good idea to check the name resolution configuration for your system. Do a<br />

basic diagnostic for name resolving. You can use either the host command or<br />

the nslookup command.<br />

# host dhcp240.itsc.austin.ibm.com<br />

dhcp240.itsc.austin.ibm.com is 9.3.240.2<br />

The name resolution can be served through either a remote DNS server or a<br />

remote NIS server. If one of them is down, you may have to wait until TCP<br />

timeout occurs. The name can be resolved by an alternate source, which can be<br />

a secondary name server or the local /etc/hosts file.<br />

First check the /etc/netsvc.conf file and the NSORDER environment variable for<br />

your particular name resolution ordering. The NSORDER variable overrides the<br />

hosts settings in the /etc/netsvc.conf file. Check the /etc/resolv.conf file for the IP<br />

Chapter 8. Network problem determination 185

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!