01.12.2012 Views

Problem Solving and Troubleshooting in AIX 5L - IBM Redbooks

Problem Solving and Troubleshooting in AIX 5L - IBM Redbooks

Problem Solving and Troubleshooting in AIX 5L - 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.

7.2.5 Dynamic or static rout<strong>in</strong>g<br />

If you are us<strong>in</strong>g dynamic rout<strong>in</strong>g, verify that the gateway is listed <strong>and</strong> correct <strong>in</strong><br />

the kernel rout<strong>in</strong>g tables by issu<strong>in</strong>g the netstat -r comm<strong>and</strong>.<br />

If the gateway host is us<strong>in</strong>g the Rout<strong>in</strong>g Information Protocol (RIP) with the<br />

routed daemon, make sure that a static route to the target host is set up <strong>in</strong> the<br />

/etc/gateways file.<br />

Note: You need to do this only if the rout<strong>in</strong>g daemon cannot identify the route<br />

to a distant host through queries to other gateways.<br />

If the gateway host is us<strong>in</strong>g the RIP with the gated daemon, make sure that a<br />

static route to the target host is set up <strong>in</strong> the gated.conf file.<br />

If you are us<strong>in</strong>g dynamic rout<strong>in</strong>g with the routed daemon:<br />

► If routed cannot identify the route through queries, for example, if the target<br />

host is not runn<strong>in</strong>g the RIP, check the /etc/gateways file to verify that a route to<br />

the target host is def<strong>in</strong>ed.<br />

► Make sure that gateways responsible for forward<strong>in</strong>g packets to the host are up<br />

<strong>and</strong> runn<strong>in</strong>g the RIP. Otherwise, you will need to def<strong>in</strong>e a static route.<br />

► Run the routed daemon us<strong>in</strong>g the debug option to log such <strong>in</strong>formation as bad<br />

packets received. Invoke the daemon from the comm<strong>and</strong> l<strong>in</strong>e us<strong>in</strong>g the<br />

follow<strong>in</strong>g comm<strong>and</strong>:<br />

# startsrc -s routed -a "-d"<br />

► Run the routed daemon us<strong>in</strong>g the -t flag, which causes all packets sent or<br />

received to be written to st<strong>and</strong>ard output. When routed is run <strong>in</strong> this mode, it<br />

rema<strong>in</strong>s under the control of the term<strong>in</strong>al that started it. Therefore, an<br />

<strong>in</strong>terrupt from the controll<strong>in</strong>g term<strong>in</strong>al kills the daemon.<br />

If you are us<strong>in</strong>g dynamic rout<strong>in</strong>g with the gated daemon:<br />

► Verify that the /etc/gated.conf file is configured correctly <strong>and</strong> that you are<br />

runn<strong>in</strong>g the correct protocols.<br />

► Make sure the gateway on the source network is us<strong>in</strong>g the same protocol as<br />

the gateway on the dest<strong>in</strong>ation network.<br />

► Make sure that the mach<strong>in</strong>e with which you are try<strong>in</strong>g to communicate has a<br />

route back to your host mach<strong>in</strong>e.<br />

► Verify that the gateway names <strong>in</strong> the gated.conf file correspond to the<br />

gateway names listed <strong>in</strong> the /etc/networks file.<br />

204 <strong>Problem</strong> <strong>Solv<strong>in</strong>g</strong> <strong>and</strong> <strong>Troubleshoot<strong>in</strong>g</strong> <strong>in</strong> <strong>AIX</strong> <strong>5L</strong>

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

Saved successfully!

Ooh no, something went wrong!