<?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: IPfailsafe Continually Moving NIC's in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/ipfailsafe-continually-moving-nic-s/m-p/5209153#M58810</link>
    <description>FailSAFE IP has become FlailSAFE IP?  Whoops.  :-)&lt;BR /&gt;&lt;BR /&gt;Without intending any snark here, what makes you believe that there is nothing wrong with the hardware or the LAN here?  What evidence do you have (LANCP device counters, other LAN traffic, previous experience with these NICs, etc) that the LAN here is correctly configured and is stable and working? &lt;BR /&gt;&lt;BR /&gt;General sequence: verify that the current TCP/IP Services patches are loaded, skim through the details at:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/83final/6526/6526pro_006.html" target="_blank"&gt;http://h71000.www7.hp.com/doc/83final/6526/6526pro_006.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;and do verify that the network LANs have some on-going traffic (as a very quiet LAN is indistinguishable from a failed LAN), and then ring up HP for assistance.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 12 Nov 2009 16:29:56 GMT</pubDate>
    <dc:creator>Hoff</dc:creator>
    <dc:date>2009-11-12T16:29:56Z</dc:date>
    <item>
      <title>IPfailsafe Continually Moving NIC's</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ipfailsafe-continually-moving-nic-s/m-p/5209151#M58808</link>
      <description>I installed IPfailsafe on a test node a few days ago. It went in remarkably easily (which should have been my first warning light).&lt;BR /&gt;&lt;BR /&gt;Having signed it off, I let our Developers loose on the node a day or two later. They came back saying that they kept getting logged out.&lt;BR /&gt;&lt;BR /&gt;I checked and found the following :-&lt;BR /&gt;&lt;BR /&gt;10:17:01  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:16:30.87  %%%%%%%%%%%&lt;BR /&gt;10:17:01 Message from user TCPIP$FSAFE on DELTA&lt;BR /&gt;10:17:01 TCPIP-I-FAILSAFE, WE3 - ifconfig WE3 fail&lt;BR /&gt;10:17:01 &lt;BR /&gt;10:17:01  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:16:30.89  %%%%%%%%%%%&lt;BR /&gt;10:17:01 Message from user INTERnet on DELTA&lt;BR /&gt;10:17:01 %TCPIP-W-FSINTUNAVL, WE3 interface unavailable&lt;BR /&gt;10:17:01 &lt;BR /&gt;10:17:01  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:16:30.89  %%%%%%%%%%%&lt;BR /&gt;10:17:01 Message from user INTERnet on DELTA&lt;BR /&gt;10:17:01 %TCPIP-I-FSIPADDRUP, WE1 192.168.243.240 alias active on node DELTA, interface W&lt;BR /&gt;10:17:01 E1&lt;BR /&gt;10:17:01 &lt;BR /&gt;10:17:31  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:00.82  %%%%%%%%%%%&lt;BR /&gt;10:17:31 Message from user TCPIP$FSAFE on DELTA&lt;BR /&gt;10:17:31 TCPIP-I-FAILSAFE, WE3 - ifconfig WE3 -fail&lt;BR /&gt;10:17:31 &lt;BR /&gt;10:17:31  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:00.86  %%%%%%%%%%%&lt;BR /&gt;10:17:31 Message from user INTERnet on DELTA&lt;BR /&gt;10:17:31 %TCPIP-I-FSINTAVAIL, WE3 interface available&lt;BR /&gt;10:17:31 &lt;BR /&gt;10:17:31  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:00.86  %%%%%%%%%%%&lt;BR /&gt;10:17:31 Message from user INTERnet on DELTA&lt;BR /&gt;10:17:31 %TCPIP-I-FSIPADDRUP, WE3 192.168.243.240 primary active on node DELTA, interface&lt;BR /&gt;10:17:31  WE3&lt;BR /&gt;10:17:31 &lt;BR /&gt;10:17:31  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:00.89  %%%%%%%%%%%&lt;BR /&gt;10:17:31 Message from user TCPIP$FSAFE on DELTA&lt;BR /&gt;10:17:31 TCPIP-I-FAILSAFE, WE3 - route add -net -inet default 192.168.243.254 -dev WE3&lt;BR /&gt;10:17:31 &lt;BR /&gt;10:17:31  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:00.89  %%%%%%%%%%%&lt;BR /&gt;10:17:31 Message from user TCPIP$FSAFE on DELTA&lt;BR /&gt;10:17:31 TCPIP-I-FAILSAFE, WE3 - interface has become functional&lt;BR /&gt;10:17:31 &lt;BR /&gt;10:17:39  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:08.85  %%%%%%%%%%%&lt;BR /&gt;10:17:39 Message from user TCPIP$FSAFE on DELTA&lt;BR /&gt;10:17:39 TCPIP-I-FAILSAFE, WE3 - ifconfig WE3 fail&lt;BR /&gt;10:17:39 &lt;BR /&gt;10:17:39  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:08.87  %%%%%%%%%%%&lt;BR /&gt;10:17:39 Message from user INTERnet on DELTA&lt;BR /&gt;10:17:39 %TCPIP-W-FSINTUNAVL, WE3 interface unavailable&lt;BR /&gt;10:17:39 &lt;BR /&gt;10:17:39  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:08.87  %%%%%%%%%%%&lt;BR /&gt;10:17:39 Message from user INTERnet on DELTA&lt;BR /&gt;10:17:39 %TCPIP-I-FSIPADDRUP, WE1 192.168.243.240 alias active on node DELTA, interface W&lt;BR /&gt;10:17:39 E1&lt;BR /&gt;10:17:39 &lt;BR /&gt;10:18:09  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:38.81  %%%%%%%%%%%&lt;BR /&gt;10:18:09 Message from user TCPIP$FSAFE on DELTA&lt;BR /&gt;10:18:09 TCPIP-I-FAILSAFE, WE3 - ifconfig WE3 -fail&lt;BR /&gt;10:18:09 &lt;BR /&gt;10:18:09  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:38.85  %%%%%%%%%%%&lt;BR /&gt;10:18:09 Message from user INTERnet on DELTA&lt;BR /&gt;10:18:09 %TCPIP-I-FSINTAVAIL, WE3 interface available&lt;BR /&gt;10:18:09 &lt;BR /&gt;10:18:09  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:38.85  %%%%%%%%%%%&lt;BR /&gt;10:18:09 Message from user INTERnet on DELTA&lt;BR /&gt;10:18:09 %TCPIP-I-FSIPADDRUP, WE3 192.168.243.240 primary active on node DELTA, interface&lt;BR /&gt;10:18:09  WE3&lt;BR /&gt;10:18:09 &lt;BR /&gt;10:18:09  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:38.88  %%%%%%%%%%%&lt;BR /&gt;10:18:09 Message from user TCPIP$FSAFE on DELTA&lt;BR /&gt;10:18:09 TCPIP-I-FAILSAFE, WE3 - route add -net -inet default 192.168.243.254 -dev WE3&lt;BR /&gt;10:18:09 &lt;BR /&gt;10:18:09  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:38.89  %%%%%%%%%%%&lt;BR /&gt;10:18:09 Message from user TCPIP$FSAFE on DELTA&lt;BR /&gt;10:18:09 TCPIP-I-FAILSAFE, WE3 - interface has become functional&lt;BR /&gt;10:18:09 &lt;BR /&gt;10:18:17  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:46.86  %%%%%%%%%%%&lt;BR /&gt;10:18:17 Message from user TCPIP$FSAFE on DELTA&lt;BR /&gt;10:18:17 TCPIP-I-FAILSAFE, WE3 - ifconfig WE3 fail&lt;BR /&gt;10:18:18 &lt;BR /&gt;10:18:18  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:46.88  %%%%%%%%%%%&lt;BR /&gt;10:18:18 Message from user INTERnet on DELTA&lt;BR /&gt;10:18:18 %TCPIP-W-FSINTUNAVL, WE3 interface unavailable&lt;BR /&gt;10:18:18 &lt;BR /&gt;10:18:18  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:17:46.88  %%%%%%%%%%%&lt;BR /&gt;10:18:18 Message from user INTERnet on DELTA&lt;BR /&gt;10:18:18 %TCPIP-I-FSIPADDRUP, WE1 192.168.243.240 alias active on node DELTA, interface W&lt;BR /&gt;10:18:18 E1&lt;BR /&gt;10:18:18 &lt;BR /&gt;10:18:47  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:18:16.81  %%%%%%%%%%%&lt;BR /&gt;10:18:47 Message from user TCPIP$FSAFE on DELTA&lt;BR /&gt;10:18:47 TCPIP-I-FAILSAFE, WE3 - ifconfig WE3 -fail&lt;BR /&gt;10:18:47 &lt;BR /&gt;10:18:47  %%%%%%%%%%%  OPCOM  10-NOV-2009 10:18:16.84  %%%%%%%%%%%&lt;BR /&gt;10:18:47 Message from user INTERnet on DELTA&lt;BR /&gt;10:18:47 %TCPIP-I-FSINTAVAIL, WE3 interface available&lt;BR /&gt;10:18:47 &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;As you can see, it continually jumps backwards and forwards. As soon as I disabled IPfailsafe, it remained on WE3 and is quite happy.&lt;BR /&gt;&lt;BR /&gt;As far as I can see, there's nothing wrong with the hardware, so any ideas why it keeps hopping about?&lt;BR /&gt;&lt;BR /&gt;Rob.&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Nov 2009 15:36:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ipfailsafe-continually-moving-nic-s/m-p/5209151#M58808</guid>
      <dc:creator>Robert Atkinson</dc:creator>
      <dc:date>2009-11-12T15:36:26Z</dc:date>
    </item>
    <item>
      <title>Re: IPfailsafe Continually Moving NIC's</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ipfailsafe-continually-moving-nic-s/m-p/5209152#M58809</link>
      <description>Umm, really weird. I've rebooted and it's OK again.&lt;BR /&gt;&lt;BR /&gt;I've found some more info on the IPfailsafe internals (&lt;A href="http://h71000.www7.hp.com/openvms/journal/v2/articles/tcpip.html)" target="_blank"&gt;http://h71000.www7.hp.com/openvms/journal/v2/articles/tcpip.html)&lt;/A&gt; so I'll see if it happens again, and do some more checking.&lt;BR /&gt;&lt;BR /&gt;Rob.</description>
      <pubDate>Thu, 12 Nov 2009 16:16:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ipfailsafe-continually-moving-nic-s/m-p/5209152#M58809</guid>
      <dc:creator>Robert Atkinson</dc:creator>
      <dc:date>2009-11-12T16:16:32Z</dc:date>
    </item>
    <item>
      <title>Re: IPfailsafe Continually Moving NIC's</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ipfailsafe-continually-moving-nic-s/m-p/5209153#M58810</link>
      <description>FailSAFE IP has become FlailSAFE IP?  Whoops.  :-)&lt;BR /&gt;&lt;BR /&gt;Without intending any snark here, what makes you believe that there is nothing wrong with the hardware or the LAN here?  What evidence do you have (LANCP device counters, other LAN traffic, previous experience with these NICs, etc) that the LAN here is correctly configured and is stable and working? &lt;BR /&gt;&lt;BR /&gt;General sequence: verify that the current TCP/IP Services patches are loaded, skim through the details at:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/83final/6526/6526pro_006.html" target="_blank"&gt;http://h71000.www7.hp.com/doc/83final/6526/6526pro_006.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;and do verify that the network LANs have some on-going traffic (as a very quiet LAN is indistinguishable from a failed LAN), and then ring up HP for assistance.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Nov 2009 16:29:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ipfailsafe-continually-moving-nic-s/m-p/5209153#M58810</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-11-12T16:29:56Z</dc:date>
    </item>
    <item>
      <title>Re: IPfailsafe Continually Moving NIC's</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ipfailsafe-continually-moving-nic-s/m-p/5209154#M58811</link>
      <description>How many NICs do you have on the box(es) Rob?  You need at least three really for failsafe IP to work properly.  Otherwise, when one interface goes off the other one thinks that it's lost connectivity and moves the interface.&lt;BR /&gt;It's one of those documented items that you forget about until it hits you (or at least that was the way it was with me!)&lt;BR /&gt;&lt;BR /&gt;Steev</description>
      <pubDate>Fri, 13 Nov 2009 21:02:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ipfailsafe-continually-moving-nic-s/m-p/5209154#M58811</guid>
      <dc:creator>Steve Reece_3</dc:creator>
      <dc:date>2009-11-13T21:02:09Z</dc:date>
    </item>
  </channel>
</rss>

