<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Oddities with TCPIP$ROUTE (error accessing routes database) in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/oddities-with-tcpip-route-error-accessing-routes-database/m-p/5934601#M45941</link>
    <description>&lt;P&gt;Hello folks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a dual node RX2800 cluster (OpenVMS 8-4 Update 7, TCPIP 5-7 ECO 3). One of our customers has a small numbe of PCs etc. located in another building connected via some 3rd party comms produc (pair of routes over some kind of ADSL link).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is a single address alias allocated to the cluster which can be seen via the routers, this alias will move from node to node following the software which talks to the remote equipment. The problem I have is that information in the permanent routes database does not seem to be used, access to the remote equipment is only possible once a dynanic route has been entered.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example the&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The command TCPIP SHO ROUTER/PERM&amp;nbsp; shows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="terminal,monaco"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PERMANENT&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;Type&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Destination&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Gateway&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;PH&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.1.1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 193.116.105.248&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;PH&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.1.2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 193.116.105.248&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;But neither address (192.168.1.1) can be pinged (no route), although the gateway address can. Doing a show route on one of the individual addresses gives:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="terminal,monaco"&gt;tcpip sho route 192.168.1.1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;%TCPIP-E-ROUTEERROR, error accessing routes database (TCPIP$ROUTE)&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;-TCPIP-W-NORECORD, information not found&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Logicals such as the TCPIP$INET_HOST etc. are all populated, the routes file is as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="terminal,monaco"&gt;dir tcpip$route/sec&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;Directory SYS$COMMON:[SYSEXE]&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;TCPIP$ROUTE.DAT;1&amp;nbsp;&amp;nbsp;&amp;nbsp; [1,1]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (RWED,RWED,RE,RE)&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As soon as a dynamic route is entered full connectivity is restored.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The hosts in the cluster have their own system disks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any thoughts? In the past I've seen a number of posts regarding these kind of issues but the fixes seem to be unclear.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Brian&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 17 Jan 2013 08:52:14 GMT</pubDate>
    <dc:creator>Brian Reiter</dc:creator>
    <dc:date>2013-01-17T08:52:14Z</dc:date>
    <item>
      <title>Oddities with TCPIP$ROUTE (error accessing routes database)</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/oddities-with-tcpip-route-error-accessing-routes-database/m-p/5934601#M45941</link>
      <description>&lt;P&gt;Hello folks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a dual node RX2800 cluster (OpenVMS 8-4 Update 7, TCPIP 5-7 ECO 3). One of our customers has a small numbe of PCs etc. located in another building connected via some 3rd party comms produc (pair of routes over some kind of ADSL link).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is a single address alias allocated to the cluster which can be seen via the routers, this alias will move from node to node following the software which talks to the remote equipment. The problem I have is that information in the permanent routes database does not seem to be used, access to the remote equipment is only possible once a dynanic route has been entered.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example the&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The command TCPIP SHO ROUTER/PERM&amp;nbsp; shows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="terminal,monaco"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PERMANENT&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;Type&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Destination&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Gateway&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;PH&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.1.1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 193.116.105.248&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;PH&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.1.2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 193.116.105.248&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;But neither address (192.168.1.1) can be pinged (no route), although the gateway address can. Doing a show route on one of the individual addresses gives:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="terminal,monaco"&gt;tcpip sho route 192.168.1.1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;%TCPIP-E-ROUTEERROR, error accessing routes database (TCPIP$ROUTE)&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;-TCPIP-W-NORECORD, information not found&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Logicals such as the TCPIP$INET_HOST etc. are all populated, the routes file is as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="terminal,monaco"&gt;dir tcpip$route/sec&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;Directory SYS$COMMON:[SYSEXE]&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco"&gt;TCPIP$ROUTE.DAT;1&amp;nbsp;&amp;nbsp;&amp;nbsp; [1,1]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (RWED,RWED,RE,RE)&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As soon as a dynamic route is entered full connectivity is restored.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The hosts in the cluster have their own system disks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any thoughts? In the past I've seen a number of posts regarding these kind of issues but the fixes seem to be unclear.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Brian&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jan 2013 08:52:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/oddities-with-tcpip-route-error-accessing-routes-database/m-p/5934601#M45941</guid>
      <dc:creator>Brian Reiter</dc:creator>
      <dc:date>2013-01-17T08:52:14Z</dc:date>
    </item>
  </channel>
</rss>

