<?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: Cluster Virtual IP /alias IP in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/cluster-virtual-ip-alias-ip/m-p/5087594#M55873</link>
    <description>Hi Feige&lt;BR /&gt;&lt;BR /&gt;This is the normal behaviour for the IP Cluster Alias. It is bound to the first booting node within a cluster. As long this node is up, all connects to the Tcpip Cluster alias will reach this node.&lt;BR /&gt;&lt;BR /&gt;If you want to change this, then you must introduce FailSafe IP. Together with a DNS Sever which change the order of the two adresses you will have what you are looking for&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Geni</description>
    <pubDate>Fri, 11 Jan 2008 15:18:07 GMT</pubDate>
    <dc:creator>Heinz W Genhart</dc:creator>
    <dc:date>2008-01-11T15:18:07Z</dc:date>
    <item>
      <title>Cluster Virtual IP /alias IP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-virtual-ip-alias-ip/m-p/5087593#M55872</link>
      <description>OpenVMS 8.2 Two nodes cluster.&lt;BR /&gt;Node A we0 IPaddress:100.1.0.221&lt;BR /&gt;Node B we0 IPaddress:100.1.0.222&lt;BR /&gt;Cluster IP: 100.1.0.220&lt;BR /&gt;when I use:&lt;BR /&gt;$UCX&lt;BR /&gt;  TCPIP&amp;gt;telnet 100.1.0.220&lt;BR /&gt;When telnet clusterIP(100.1.0.220&lt;BR /&gt;),I find all clients login the Node A(Node A  first started the tcpip service).&lt;BR /&gt;Can I set connect to 100.1.0.222 when i use 100.1.0.220 IP access?&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Fri, 11 Jan 2008 14:51:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-virtual-ip-alias-ip/m-p/5087593#M55872</guid>
      <dc:creator>Feige</dc:creator>
      <dc:date>2008-01-11T14:51:43Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Virtual IP /alias IP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-virtual-ip-alias-ip/m-p/5087594#M55873</link>
      <description>Hi Feige&lt;BR /&gt;&lt;BR /&gt;This is the normal behaviour for the IP Cluster Alias. It is bound to the first booting node within a cluster. As long this node is up, all connects to the Tcpip Cluster alias will reach this node.&lt;BR /&gt;&lt;BR /&gt;If you want to change this, then you must introduce FailSafe IP. Together with a DNS Sever which change the order of the two adresses you will have what you are looking for&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Geni</description>
      <pubDate>Fri, 11 Jan 2008 15:18:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-virtual-ip-alias-ip/m-p/5087594#M55873</guid>
      <dc:creator>Heinz W Genhart</dc:creator>
      <dc:date>2008-01-11T15:18:07Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Virtual IP /alias IP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-virtual-ip-alias-ip/m-p/5087595#M55874</link>
      <description>Feige,&lt;BR /&gt;&lt;BR /&gt;alas, this is standard TCPIP.&lt;BR /&gt;Never confuse IP workings with Decnet workings, an do NOT confuse similarly-named concepts!&lt;BR /&gt;&lt;BR /&gt;A IP cluster alias is just another address that gets bound to the first network DEVICE that presents it (the "impersonator") and remains so as long as that device is available. Only if the device goes out of functionality (for whatever reason) does another potential cluster alias device become the new impersonator.&lt;BR /&gt;&lt;BR /&gt;If you strive towards some kind of load balancing, then use&lt;BR /&gt;--METRIC - to determine available capacities&lt;BR /&gt;--LOADBROKER - to regularly determine which node (actually, which device) can currently best accept new load&lt;BR /&gt;--allow your BIND server to be updated by the loadbroker&lt;BR /&gt;AND ----  SET ALL IP KEEPALIVE TIMERS in ALL ROUTERS to the order of at most one or two minutes.&lt;BR /&gt;&lt;BR /&gt;----- round-robin answers be the bind server are also a (rather more rude) means of spreading the load. That also required=s short keep-alive times.&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Fri, 11 Jan 2008 15:30:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-virtual-ip-alias-ip/m-p/5087595#M55874</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2008-01-11T15:30:47Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Virtual IP /alias IP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-virtual-ip-alias-ip/m-p/5087596#M55875</link>
      <description>Feige,&lt;BR /&gt;&lt;BR /&gt;I forgot one thing: this works with DNS names, NOT with IP addresses.&lt;BR /&gt;It just regularly changes the IP address for a given DNS name.&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Fri, 11 Jan 2008 15:33:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-virtual-ip-alias-ip/m-p/5087596#M55875</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2008-01-11T15:33:18Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Virtual IP /alias IP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-virtual-ip-alias-ip/m-p/5087597#M55876</link>
      <description>Thanks, I will try</description>
      <pubDate>Tue, 15 Jan 2008 01:00:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-virtual-ip-alias-ip/m-p/5087597#M55876</guid>
      <dc:creator>Feige</dc:creator>
      <dc:date>2008-01-15T01:00:54Z</dc:date>
    </item>
  </channel>
</rss>

