<?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 flaky virtual IP for MC/Service guard in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506351#M716902</link>
    <description>We run a cluster using MC/Service Guard. The cluster is composed of two nodes .2 and .3 with virtual IP .1 &lt;BR /&gt;On a local lan all interfaces respond to PING, from two routers away only .2 and .3 respond, .1 does not answer. We are using Cisco routers and when we clear the ARP cache on the router local to the cluster all works for a few minutes (from seconds to 25 minutes) then the virtual IP refused to respond. Other machines local to the MC/Service Guard cluster respond to PING from two routers away as well as the physical IPs .2 and .3 The virtual IP .1 is the only problem. &lt;BR /&gt;&lt;BR /&gt;In the configuration of MC/Service Guard, should a virtual MAC address be defined? Has anyone else crossed this problem? This is the only problem on our network and it is only the virtual IP that refuses to respond, though the problem does not occur if the virtual IP is PINGed from the local lan to the clsuer.&lt;BR /&gt;&lt;BR /&gt;THanks,&lt;BR /&gt;&lt;BR /&gt;Frank</description>
    <pubDate>Sun, 18 Mar 2001 02:27:43 GMT</pubDate>
    <dc:creator>Frank_9</dc:creator>
    <dc:date>2001-03-18T02:27:43Z</dc:date>
    <item>
      <title>flaky virtual IP for MC/Service guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506351#M716902</link>
      <description>We run a cluster using MC/Service Guard. The cluster is composed of two nodes .2 and .3 with virtual IP .1 &lt;BR /&gt;On a local lan all interfaces respond to PING, from two routers away only .2 and .3 respond, .1 does not answer. We are using Cisco routers and when we clear the ARP cache on the router local to the cluster all works for a few minutes (from seconds to 25 minutes) then the virtual IP refused to respond. Other machines local to the MC/Service Guard cluster respond to PING from two routers away as well as the physical IPs .2 and .3 The virtual IP .1 is the only problem. &lt;BR /&gt;&lt;BR /&gt;In the configuration of MC/Service Guard, should a virtual MAC address be defined? Has anyone else crossed this problem? This is the only problem on our network and it is only the virtual IP that refuses to respond, though the problem does not occur if the virtual IP is PINGed from the local lan to the clsuer.&lt;BR /&gt;&lt;BR /&gt;THanks,&lt;BR /&gt;&lt;BR /&gt;Frank</description>
      <pubDate>Sun, 18 Mar 2001 02:27:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506351#M716902</guid>
      <dc:creator>Frank_9</dc:creator>
      <dc:date>2001-03-18T02:27:43Z</dc:date>
    </item>
    <item>
      <title>Re: flaky virtual IP for MC/Service guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506352#M716903</link>
      <description>Frank,&lt;BR /&gt;&lt;BR /&gt;You don't to set any "virtual MAC" address. The virtual IP should pass the routers without any  problem. As far as I know there's no special setting needed at the UNIX and/or router level. &lt;BR /&gt;&lt;BR /&gt;Make sure &lt;BR /&gt;- you run a HP supported MC Service Guard configuration i.e you have the two systems .1 and .2 on the same subnet and they are not separated by an active networking device(router).&lt;BR /&gt;- you don't have another system with the same IP somewhere in the net (probably behind the router). This can be reason why you can access the addres from inside the cell and for a while from outside too, but as soon as the other system starts sending it's MAC the ARP tables get changed. IF you have a chance have a look at the ARP tables from the router and verify if all network devices support virtual IPs.&lt;BR /&gt;&lt;BR /&gt;Let me know if I'm wrong,&lt;BR /&gt;Ovidiu&lt;BR /&gt;</description>
      <pubDate>Mon, 19 Mar 2001 02:12:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506352#M716903</guid>
      <dc:creator>Ovidiu D. Raita</dc:creator>
      <dc:date>2001-03-19T02:12:53Z</dc:date>
    </item>
    <item>
      <title>Re: flaky virtual IP for MC/Service guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506353#M716904</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;I had once the same problem.  Some subnets could reach the machine, others not.  After weeks of investigations, I suggested to shutdown the switch (we were using ALCATLEL and CISCO).  Problem was solved immediately.  I have the impression that it has to do something with the ARP cache.&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;DD</description>
      <pubDate>Mon, 19 Mar 2001 07:33:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506353#M716904</guid>
      <dc:creator>Dieter Degrendele_1</dc:creator>
      <dc:date>2001-03-19T07:33:15Z</dc:date>
    </item>
    <item>
      <title>Re: flaky virtual IP for MC/Service guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506354#M716905</link>
      <description>Hi,&lt;BR /&gt;Hmmm this sounds familiar...there was a problem reported 2 years ago where the re-arp&lt;BR /&gt;broadcast was broken, but that was fixed in an 11.0 ARPA Transport patch.  Check to see that you have PHNE_17662 or later.  The SR # is 1653282012.&lt;BR /&gt;Hope this helps,&lt;BR /&gt;-&amp;gt; Brian Hackley&lt;BR /&gt;</description>
      <pubDate>Tue, 20 Mar 2001 16:10:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506354#M716905</guid>
      <dc:creator>Brian Hackley</dc:creator>
      <dc:date>2001-03-20T16:10:41Z</dc:date>
    </item>
    <item>
      <title>Re: flaky virtual IP for MC/Service guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506355#M716906</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I have the same sense of Frank. I'm meeting the same problem and I don't know how to solve it.&lt;BR /&gt;&lt;BR /&gt;Is the way of "shutdown switch" the permanent way for solving this problem?&lt;BR /&gt;&lt;BR /&gt;If no, can installation of HP-UX network patch works? and is there any risk for installing the HP-UX network patch?&lt;BR /&gt;&lt;BR /&gt;My enviroment:&lt;BR /&gt;HP-UX 11.0&lt;BR /&gt;MC/ServiceGuard 11.09&lt;BR /&gt;No MC/SG patches installed</description>
      <pubDate>Wed, 21 Mar 2001 10:32:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506355#M716906</guid>
      <dc:creator>Gengwd</dc:creator>
      <dc:date>2001-03-21T10:32:23Z</dc:date>
    </item>
    <item>
      <title>Re: flaky virtual IP for MC/Service guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506356#M716907</link>
      <description>You MUST have all the latest networking patches installed, and the patch for MC/SG 11.09 which is currently PHSS_22876</description>
      <pubDate>Wed, 21 Mar 2001 11:44:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506356#M716907</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2001-03-21T11:44:58Z</dc:date>
    </item>
    <item>
      <title>Re: flaky virtual IP for MC/Service guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506357#M716908</link>
      <description>If I installed MC/SG patch PHSS_22876,is it necessary to install networking patch such as PHNE_22397?&lt;BR /&gt;&lt;BR /&gt;Thanks for melvyn's great help.</description>
      <pubDate>Wed, 21 Mar 2001 19:28:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506357#M716908</guid>
      <dc:creator>Gengwd</dc:creator>
      <dc:date>2001-03-21T19:28:07Z</dc:date>
    </item>
    <item>
      <title>Re: flaky virtual IP for MC/Service guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506358#M716909</link>
      <description>Yes the network patch should be installed.&lt;BR /&gt;Having said that , I guess it is time I posted a list of recommended patches for SG nodes on HP-UX 11.00 :-}&lt;BR /&gt;I will do this as a separate new message&lt;BR /&gt;</description>
      <pubDate>Wed, 21 Mar 2001 22:13:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506358#M716909</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2001-03-21T22:13:38Z</dc:date>
    </item>
    <item>
      <title>Re: flaky virtual IP for MC/Service guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506359#M716910</link>
      <description>Ok, just for the record, here is te RECOMMENDED patch list for SG on 11.00&lt;BR /&gt;&lt;BR /&gt;Please note that any or all of these patches could be superseded, and could have dependencies that you will have to ensure are included.&lt;BR /&gt;Also, various patches will/will not apply depending on the software used on your system.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;PATCH Number Title        &lt;BR /&gt;&lt;BR /&gt;PHCO_21901 s700_800 11.00 fuser(1M) cumulative patch&lt;BR /&gt;PHCO_22733 s700_800 11.00 sar(1M) cumulative patch &lt;BR /&gt;PHCO_22839 s700_800 11.00 LVM commands cumulative patch&lt;BR /&gt;PHKL_13431 s700_800 11.00 bad block msg,panic; data possibly corrupted&lt;BR /&gt;PHKL_18543 s700_800 11.00 PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch&lt;BR /&gt;PHKL_18800 s700_800 11.00 Cumulative JFS patch - panic:dirty inval&lt;BR /&gt;PHKL_21834 s700_800 11.00 Fibre Channel Mass Storage Driver&lt;BR /&gt;PHKL_22494 s700_800 11.00 PCI ExpROM,bridge,BA hints,Lowfat,PIOP,EPIC&lt;BR /&gt;PHKL_22759 s700_800 11.00 SCSI IO Subsystem Cumulative Patch&lt;BR /&gt;PHKL_22986 s700_800 11.00 cumulative pstat patch&lt;BR /&gt;PHKL_23127 s700_800 11.00 LVM Cumulative patch&lt;BR /&gt;PHNE_15537 s700_800 11.00 Fibre Channel cumulative patch&lt;BR /&gt;PHNE_16172 s700_800 11.00 gated (1M) patch&lt;BR /&gt;PHNE_18635 s700_800 11.00 HP Auto-Port Aggregation patch B.11.00.02&lt;BR /&gt;PHNE_19200 s700_800 11.00 EISA 100BT patch&lt;BR /&gt;PHNE_19633 s700_800 11.00 HP-PB FDDI (J2157B) product cumulative patch&lt;BR /&gt;PHNE_20874 s700_800 11.00 PCI FDDI B.11.00.[01-03,05,08,11-13] patch&lt;BR /&gt;PHNE_20949 s700_800 11.00 HyperFabric B.11.00.0[0-8] cumulative patch&lt;BR /&gt;PHNE_21389 s700_800 11.00 EISA FDDI B.11.00.0[0-7] cumulative patch&lt;BR /&gt;PHNE_21390 s700_800 11.00 HSC FDDI B.11.00.0[0-7] cumulative patch&lt;BR /&gt;PHNE_21731 s700_800 11.00 r-commands cumulative mega-patch&lt;BR /&gt;PHNE_22244 s700_800 11.00 Built-in PCI 100BASE-T patch&lt;BR /&gt;PHNE_22245 s700_800 11.00 PCI 100B(Tx/Fx) cumulative patch&lt;BR /&gt;PHNE_22353 s700_800 11.00 LAN product cumulative patch&lt;BR /&gt;PHNE_22397 s700_800 11.00 cumulative ARPA Transport patch&lt;BR /&gt;PHNE_22566 s700_800 11.00 Cumulative STREAMS Patch&lt;BR /&gt;PHNE_22728 s700_800 11.00 4 port PCI 100BASE-T cumulative patch&lt;BR /&gt;PHNE_22930 s700_800 11.00 1000Base-SX/T B.11.00.[02-11] cumul. patch&lt;BR /&gt;PHSS_17496 s700_800 11.00 Predictive C.11.0[0,a-m] cumulative patch&lt;BR /&gt;PHSS_22946 s700_800 11.00 X/Motif 32bit Runtime JAN2001 Periodic Patch</description>
      <pubDate>Wed, 21 Mar 2001 22:55:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/flaky-virtual-ip-for-mc-service-guard/m-p/2506359#M716910</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2001-03-21T22:55:56Z</dc:date>
    </item>
  </channel>
</rss>

