<?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 Re: can not route through 2nd nic/interface in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/can-not-route-through-2nd-nic-interface/m-p/2986955#M46476</link>
    <description>I'm guess were static. Here's "show route".&lt;BR /&gt;&lt;BR /&gt;[KILLINGER]&amp;gt; ucx show route&lt;BR /&gt;  &lt;BR /&gt;                             DYNAMIC database&lt;BR /&gt;  &lt;BR /&gt;Type           Destination                           Gateway&lt;BR /&gt;                                         &lt;BR /&gt;AH    127.0.0.1                             127.0.0.1&lt;BR /&gt;AN    0.0.0.0                               144.70.165.126&lt;BR /&gt;AN    144.70.165.0                          144.70.165.115&lt;BR /&gt;AN    144.70.165.0                          144.70.165.74&lt;BR /&gt;[KILLINGER]&amp;gt;</description>
    <pubDate>Tue, 03 Jun 2003 09:01:59 GMT</pubDate>
    <dc:creator>Tim Killinger</dc:creator>
    <dc:date>2003-06-03T09:01:59Z</dc:date>
    <item>
      <title>can not route through 2nd nic/interface</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/can-not-route-through-2nd-nic-interface/m-p/2986953#M46474</link>
      <description>I have configured the second NIC on our VMS 7.1 host. It comes up (we1) and can be used only on the local subnet. I've run ucx$config and swapped ip addresses between we0 and we1 and still can only route through we0. Both NICS are on the same subnet using the same default router. Any idea why the second NIC won't route(we1)???&lt;BR /&gt;&lt;BR /&gt;Thanks!!!</description>
      <pubDate>Tue, 03 Jun 2003 00:29:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/can-not-route-through-2nd-nic-interface/m-p/2986953#M46474</guid>
      <dc:creator>Tim Killinger</dc:creator>
      <dc:date>2003-06-03T00:29:44Z</dc:date>
    </item>
    <item>
      <title>Re: can not route through 2nd nic/interface</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/can-not-route-through-2nd-nic-interface/m-p/2986954#M46475</link>
      <description>are you using static or dynamic routing? Can you post the result of UCX SHOW ROUTE?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 03 Jun 2003 08:37:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/can-not-route-through-2nd-nic-interface/m-p/2986954#M46475</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2003-06-03T08:37:46Z</dc:date>
    </item>
    <item>
      <title>Re: can not route through 2nd nic/interface</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/can-not-route-through-2nd-nic-interface/m-p/2986955#M46476</link>
      <description>I'm guess were static. Here's "show route".&lt;BR /&gt;&lt;BR /&gt;[KILLINGER]&amp;gt; ucx show route&lt;BR /&gt;  &lt;BR /&gt;                             DYNAMIC database&lt;BR /&gt;  &lt;BR /&gt;Type           Destination                           Gateway&lt;BR /&gt;                                         &lt;BR /&gt;AH    127.0.0.1                             127.0.0.1&lt;BR /&gt;AN    0.0.0.0                               144.70.165.126&lt;BR /&gt;AN    144.70.165.0                          144.70.165.115&lt;BR /&gt;AN    144.70.165.0                          144.70.165.74&lt;BR /&gt;[KILLINGER]&amp;gt;</description>
      <pubDate>Tue, 03 Jun 2003 09:01:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/can-not-route-through-2nd-nic-interface/m-p/2986955#M46476</guid>
      <dc:creator>Tim Killinger</dc:creator>
      <dc:date>2003-06-03T09:01:59Z</dc:date>
    </item>
    <item>
      <title>Re: can not route through 2nd nic/interface</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/can-not-route-through-2nd-nic-interface/m-p/2986956#M46477</link>
      <description>Usualy every NIC must be in different subnet.</description>
      <pubDate>Wed, 04 Jun 2003 12:01:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/can-not-route-through-2nd-nic-interface/m-p/2986956#M46477</guid>
      <dc:creator>Gorazd Kikelj</dc:creator>
      <dc:date>2003-06-04T12:01:23Z</dc:date>
    </item>
    <item>
      <title>Re: can not route through 2nd nic/interface</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/can-not-route-through-2nd-nic-interface/m-p/2986957#M46478</link>
      <description>Since TCP/IP for OpenVMS V5.1 it is supported&lt;BR /&gt;to have two NICs in the same subnet.&lt;BR /&gt;&lt;BR /&gt;From the V5.1 Release Notes.&lt;BR /&gt;&lt;BR /&gt;""&lt;BR /&gt;o  Multiple adapters per subnet&lt;BR /&gt;&lt;BR /&gt;You can configure multiple active network adapters in one computer, even if they operate on the same subnetwork. For example, you can configure a WE0 interface at 192.24.156.20 and a WE1 interface at 192.24.156.21 with the same netmask.&lt;BR /&gt;&lt;BR /&gt;When you establish a connection, the kernel routes the connection through the interface that has the smallest number of connections. As a result, connections are load-balanced, leading to greater throughput than on a system with only one adapter per subnetwork.&lt;BR /&gt;""</description>
      <pubDate>Thu, 05 Jun 2003 09:09:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/can-not-route-through-2nd-nic-interface/m-p/2986957#M46478</guid>
      <dc:creator>Pim van Velzen</dc:creator>
      <dc:date>2003-06-05T09:09:55Z</dc:date>
    </item>
  </channel>
</rss>

