<?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: Failover IP addresses in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571006#M49558</link>
    <description>Volker,&lt;BR /&gt;&lt;BR /&gt;that was it ! Thanks for your assistance.&lt;BR /&gt;&lt;BR /&gt;Robert, I'll check the console level stuff next time the system is rebooted. (Production server, could be 6-12 months !)&lt;BR /&gt;&lt;BR /&gt;Matt</description>
    <pubDate>Mon, 27 Jun 2005 16:32:25 GMT</pubDate>
    <dc:creator>matthew robey</dc:creator>
    <dc:date>2005-06-27T16:32:25Z</dc:date>
    <item>
      <title>Failover IP addresses</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571000#M49552</link>
      <description>OVms V7.3-2 Tcpip V5.4 Eco 4&lt;BR /&gt;Two node ES47 Cluster.&lt;BR /&gt;&lt;BR /&gt;I have configured IP failover for two nics on each node of the cluster.&lt;BR /&gt;All works well, however when rebooting the cluster, one node displays the following error message:&lt;BR /&gt;&lt;BR /&gt;%TCPIP-E-INVINTER, error defining interface: WEA1&lt;BR /&gt;-TCPIP-I-DRIVERQIO, interface operation from internet driver QIO failed&lt;BR /&gt;-SYSTEM-F-DUPLNAM, duplicate name&lt;BR /&gt;%TCPIP-E-INVINTER, error defining interface: IEB1&lt;BR /&gt;-TCPIP-I-DRIVERQIO, interface operation from internet driver QIO failed&lt;BR /&gt;&lt;BR /&gt;The other cluster node displays no such error.&lt;BR /&gt;&lt;BR /&gt;On checking the config all appears to be ok.&lt;BR /&gt;&lt;BR /&gt;$ifconfig -a&lt;BR /&gt;&lt;BR /&gt;IE1: flags=c43&lt;UP&gt;&lt;BR /&gt;     failSAFE IP Addresses:&lt;BR /&gt;        inet xxx.xxx.xxx.157 netmask ffffff00 broadcast xxx.xxx.xxx.255 (on FIRE7 WE0)&lt;BR /&gt;    *inet xxx.xxx.xxx.167 netmask ffffff00 broadcast xxx.xxx.xxx.255 ipmtu 1500&lt;BR /&gt;&lt;BR /&gt;LO0: flags=100c89&lt;UP&gt;&lt;BR /&gt;     inet 127.0.0.1 netmask ff000000 ipmtu 4096&lt;BR /&gt;&lt;BR /&gt;TN0: flags=80&lt;NOARP&gt;&lt;BR /&gt;&lt;BR /&gt;TN1: flags=80&lt;NOARP&gt;&lt;BR /&gt;&lt;BR /&gt;WE0: flags=c43&lt;UP&gt;&lt;BR /&gt;     failSAFE IP Addresses:&lt;BR /&gt;        inet xxx.xxx.xxx.167 netmask ffffff00 broadcast xxx.xxx.xxx.255 (on FIRE7 IE1)&lt;BR /&gt;    *inet xxx.xxx.xxx.157 netmask ffffff00 broadcast xxx.xxx.xxx.255 ipmtu 1500&lt;BR /&gt;                                                                                            &lt;BR /&gt;&lt;BR /&gt;Network appears to be ok, any ideas ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Matt&lt;/UP&gt;&lt;/NOARP&gt;&lt;/NOARP&gt;&lt;/UP&gt;&lt;/UP&gt;</description>
      <pubDate>Sun, 26 Jun 2005 17:24:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571000#M49552</guid>
      <dc:creator>matthew robey</dc:creator>
      <dc:date>2005-06-26T17:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: Failover IP addresses</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571001#M49553</link>
      <description>Matt is the tertiary message for IEB1 also DUPLNAM? Or is it really missing as posted?&lt;BR /&gt;&lt;BR /&gt;What does SHOW DEV/FULL WEA and IEB show? How many other protocols are running on the devices?</description>
      <pubDate>Sun, 26 Jun 2005 17:41:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571001#M49553</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2005-06-26T17:41:02Z</dc:date>
    </item>
    <item>
      <title>Re: Failover IP addresses</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571002#M49554</link>
      <description>If that doesn't help, please log a case with your local customer support centre.</description>
      <pubDate>Sun, 26 Jun 2005 17:41:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571002#M49554</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2005-06-26T17:41:53Z</dc:date>
    </item>
    <item>
      <title>Re: Failover IP addresses</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571003#M49555</link>
      <description>Hi John,&lt;BR /&gt;&lt;BR /&gt;yes, sorry the "duplicate name" for IEB1 is also displayed. (my cut and paste is not what it should be!)&lt;BR /&gt;&lt;BR /&gt;These nics are only running ip and decnet over ip.&lt;BR /&gt;&lt;BR /&gt;Matt</description>
      <pubDate>Sun, 26 Jun 2005 21:46:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571003#M49555</guid>
      <dc:creator>matthew robey</dc:creator>
      <dc:date>2005-06-26T21:46:24Z</dc:date>
    </item>
    <item>
      <title>Re: Failover IP addresses</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571004#M49556</link>
      <description>Matt,&lt;BR /&gt;&lt;BR /&gt;is it possible, that you have (still) defined pseudo interfaces with TCPIP - in addition to failSAFE IP - on that one node ?&lt;BR /&gt;&lt;BR /&gt;Check with TCPIP SHOW CONF INTERFACES&lt;BR /&gt;&lt;BR /&gt;Maybe those definitions conflict with the failSAFE ip config ?&lt;BR /&gt;&lt;BR /&gt;By just defining failSAFE IP, you don't get pseudo interfaces definitions (i.e. weA1).&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Mon, 27 Jun 2005 00:28:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571004#M49556</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-06-27T00:28:31Z</dc:date>
    </item>
    <item>
      <title>Re: Failover IP addresses</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571005#M49557</link>
      <description>In addition to checking the TCPIP interface config info, verify that VMS and LAN databases are in agreement:&lt;BR /&gt;&lt;BR /&gt;$ show dev ie0&lt;BR /&gt;$ show dev ew0&lt;BR /&gt;$ mcr lancp &lt;BR /&gt;lancp&amp;gt; list dev/char&lt;BR /&gt;lancp&amp;gt; show dev/char&lt;BR /&gt;&lt;BR /&gt;Also at the console level, verify the device configuration with commands like&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt; show dev i&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt; show dev ew&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt; show *mode&lt;BR /&gt;&lt;BR /&gt;Make sure that there is consistency between the various addresses/settings for the interfaces.&lt;BR /&gt;&lt;BR /&gt;Robert</description>
      <pubDate>Mon, 27 Jun 2005 09:41:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571005#M49557</guid>
      <dc:creator>Robert_Boyd</dc:creator>
      <dc:date>2005-06-27T09:41:51Z</dc:date>
    </item>
    <item>
      <title>Re: Failover IP addresses</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571006#M49558</link>
      <description>Volker,&lt;BR /&gt;&lt;BR /&gt;that was it ! Thanks for your assistance.&lt;BR /&gt;&lt;BR /&gt;Robert, I'll check the console level stuff next time the system is rebooted. (Production server, could be 6-12 months !)&lt;BR /&gt;&lt;BR /&gt;Matt</description>
      <pubDate>Mon, 27 Jun 2005 16:32:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/failover-ip-addresses/m-p/3571006#M49558</guid>
      <dc:creator>matthew robey</dc:creator>
      <dc:date>2005-06-27T16:32:25Z</dc:date>
    </item>
  </channel>
</rss>

