<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Routing Diagnostics on Oracle Scripts</title><link>https://www.oraclescripts.com/tags/routing-diagnostics/</link><description>Recent content in Routing Diagnostics on Oracle Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>OracleScripts.com</copyright><lastBuildDate>Tue, 12 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.oraclescripts.com/tags/routing-diagnostics/index.xml" rel="self" type="application/rss+xml"/><item><title>Diagnose Oracle Net and RAC Interconnect Routing with netstat -r</title><link>https://www.oraclescripts.com/post/netstat-r-oracle-net-routing-diagnostics/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/netstat-r-oracle-net-routing-diagnostics/</guid><description>
&lt;h2 id="diagnose-oracle-net-and-rac-interconnect-routing-with-netstat--r"&gt;Diagnose Oracle Net and RAC Interconnect Routing with netstat -r&lt;/h2&gt;
&lt;h2 id="purpose"&gt;Purpose&lt;/h2&gt;
&lt;p&gt;Oracle Net connections and Oracle RAC private interconnect traffic both depend on correct IP routing. When an Oracle client cannot connect to the listener, when RAC Cache Fusion or heartbeat traffic is routing over the wrong interface, or when &lt;code&gt;sqlnet.ora&lt;/code&gt; logs show unexpected source addresses, the OS routing table is the first place to look. &lt;code&gt;netstat -r&lt;/code&gt; prints the kernel routing table — the same table that determines where every TCP packet on the Oracle server goes.&lt;/p&gt;</description></item></channel></rss>