<?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: Dual NIC configuration in UCX in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922742#M49901</link>
    <description>Two different network cards must belong to two different subnets - else, the routing layer does not work (properly) - data can be sent through the 'wrong' interface.</description>
    <pubDate>Thu, 01 Sep 2005 04:18:29 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2005-09-01T04:18:29Z</dc:date>
    <item>
      <title>Dual NIC configuration in UCX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922741#M49900</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;AS1200 running OpenVMS V7.1-1H2 / UCX Version V4.2 - ECO 1 (yes, I know, old stuff, but upgrade is not an option) with 2 DE500 nic's.&lt;BR /&gt;The second nic was recently configured in UCX, same subnet, etc. as first one, only new hostname and new IP-address (in the same range as the first one). The purpose of the second nic is for the central backup-system (lan-based connections to vms-clients) to connect to the new nic, freeing the main nic from all that bu traffic.&lt;BR /&gt;&lt;BR /&gt;Everything seems to work OK, only when I disconnect a network cable, outgoing traffic (ping) seems to stop. Incoming ping's only fail on the disconnected nic.&lt;BR /&gt;&lt;BR /&gt;Is all outgoing IP traffic stopped or was it just my session working through the disconnected nic that got stuck ? Any hint on how to monitor in detail traffic on each of the nic's ? Any suggestions to improve my dual nic config (with this OS-version; I know recent VMS/TCPIP has a lot more to offer) ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Dirk</description>
      <pubDate>Thu, 01 Sep 2005 04:06:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922741#M49900</guid>
      <dc:creator>Dirk Bogaerts</dc:creator>
      <dc:date>2005-09-01T04:06:21Z</dc:date>
    </item>
    <item>
      <title>Re: Dual NIC configuration in UCX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922742#M49901</link>
      <description>Two different network cards must belong to two different subnets - else, the routing layer does not work (properly) - data can be sent through the 'wrong' interface.</description>
      <pubDate>Thu, 01 Sep 2005 04:18:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922742#M49901</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-09-01T04:18:29Z</dc:date>
    </item>
    <item>
      <title>Re: Dual NIC configuration in UCX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922743#M49902</link>
      <description>As Uwe said,&lt;BR /&gt;there is no way to choic outgoing device in same netmask.&lt;BR /&gt; &lt;BR /&gt;Antonio Vigliotti&lt;BR /&gt;</description>
      <pubDate>Thu, 01 Sep 2005 04:32:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922743#M49902</guid>
      <dc:creator>Antoniov.</dc:creator>
      <dc:date>2005-09-01T04:32:52Z</dc:date>
    </item>
    <item>
      <title>Re: Dual NIC configuration in UCX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922744#M49903</link>
      <description>As you said current VMS versions have more facilities to do this. Parhaps you need to revisit the reasons about why you can not upgrade. Its often that people have not actually thought what is involved.&lt;BR /&gt;&lt;BR /&gt;As has been said, the 2nd network card has to have a different IP network address.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 01 Sep 2005 05:13:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922744#M49903</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-09-01T05:13:07Z</dc:date>
    </item>
    <item>
      <title>Re: Dual NIC configuration in UCX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922745#M49904</link>
      <description>Dirk,&lt;BR /&gt;&lt;BR /&gt;All routing is done based upon ucx sho rout.&lt;BR /&gt;&lt;BR /&gt;If the second card only communicates with a certain backup node, make sure that after ucx startup the route to the backup node goes via the 2nd card. &lt;BR /&gt;&lt;BR /&gt;It becomes more difficult if routers are between them ...&lt;BR /&gt;&lt;BR /&gt;Wim@home (no vms, so untested)</description>
      <pubDate>Thu, 01 Sep 2005 14:02:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922745#M49904</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2005-09-01T14:02:06Z</dc:date>
    </item>
    <item>
      <title>Re: Dual NIC configuration in UCX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922746#M49905</link>
      <description>For your purpose here you need to have each adapter in a different subnet. That's the only way to ensure that the traffic is separated. So, the "backup LAN" must use a different IP address range and subnet mask to your "public LAN". You will need to ensure that the static routes are correctly configured so that the default gateway is via the "public LAN".&lt;BR /&gt;&lt;BR /&gt;VMS / TCPIP Services will handle multiple adapters in the same subnet, but there's no way to force specific outbound sessions over a specific adapter. VMS V7.3-2 and TCPIP V5.4 (and later) do all sorts of good failover things with multiple adapters (both outbound and inbound), but that's not what you're looking for. All you need is basic traffic separation - so it's back to a simple configuration with different IP addresses and different subnets for each adapter.&lt;BR /&gt;&lt;BR /&gt;Traffic monitoring is probably best done at NIC level by looking at the NIC counters with SDA - or use an external LAN analyser. Later versions of TCPIP Services have facilities to look at the BG devices - I can't remember what was in UCX V4.2.&lt;BR /&gt;&lt;BR /&gt;As has been mentioned - consider upgrading to current versions if you can.&lt;BR /&gt;&lt;BR /&gt;Assuming that you also run DECnet then you might want to ensure that you don't have Phase IV addressing enabled on both adapters - if so then they will both run with the same MAC address. That's OK if they're totally separate LANs (or VLANs through the same switch). It's dfinitely not OK if they're both connected to the same LAN or VLAN. I assume that you won't need DECnet on the "backup LAN" - which will be fine.&lt;BR /&gt;&lt;BR /&gt;Check for other protocols too and disable them on the relevant adapter too if appropriate (eg: clustering traffic, LAT etc.).&lt;BR /&gt;&lt;BR /&gt;Cheers, Colin.</description>
      <pubDate>Thu, 01 Sep 2005 23:23:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922746#M49905</guid>
      <dc:creator>Colin Butcher</dc:creator>
      <dc:date>2005-09-01T23:23:45Z</dc:date>
    </item>
    <item>
      <title>Re: Dual NIC configuration in UCX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922747#M49906</link>
      <description>Thanks all for the quick responses.&lt;BR /&gt;Special thanks to Colin for the comprehensive reply.&lt;BR /&gt;&lt;BR /&gt;For the moment have to keep the 2 nic's in the same subnet (more company rules&amp;amp;restrictions than available subnets..). &lt;BR /&gt;100% separation of traffic is not an absolute must, I'll try to use SET SERVICE &lt;BU service=""&gt; /ADDRESS=&lt;BU nic="" ip=""&gt; to force all 'backup' IP traffic to the 2nd nic; hopefully most of the 'general' IP will stay on the main nic (is UCX smart enough to avoid the congested nic when another nic is available ?). &lt;BR /&gt;During daytime, having both nic's in the same subnet might well improve performance of the 'general' IP traffic. And my initial fears that disconnecting/failing 1 nic would block all IP traffic, seems unfounded (at least on a more recent VMS 7.2/TCPIP5.1 test system)&lt;BR /&gt;&lt;BR /&gt;And as to why VMS upgrade is not an option...sad story... application software not supported on more recent VMS; the future releases of the application will mean being forced to throw the Alphaserver out of the window and the application into the Windows of master Bill&lt;/BU&gt;&lt;/BU&gt;</description>
      <pubDate>Fri, 02 Sep 2005 17:39:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922747#M49906</guid>
      <dc:creator>Dirk Bogaerts</dc:creator>
      <dc:date>2005-09-02T17:39:49Z</dc:date>
    </item>
    <item>
      <title>Re: Dual NIC configuration in UCX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922748#M49907</link>
      <description>just for info : SET SERVICE &lt;BU service=""&gt; /ADDRESS=&lt;BU nic="" ip=""&gt; seems to work fine&lt;BR /&gt;&lt;/BU&gt;&lt;/BU&gt;</description>
      <pubDate>Tue, 13 Sep 2005 04:59:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dual-nic-configuration-in-ucx/m-p/4922748#M49907</guid>
      <dc:creator>Dirk Bogaerts</dc:creator>
      <dc:date>2005-09-13T04:59:39Z</dc:date>
    </item>
  </channel>
</rss>

