<?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: Multicast MAC address in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691896#M712801</link>
    <description>James,&lt;BR /&gt;&lt;BR /&gt; No, we are a large ATM/SONET  based site &amp;amp; we were having poblems with the 12000 series switches.  &lt;BR /&gt;These are our main switches. &lt;BR /&gt;But then again we had trouble from the get-go w/these switches as not all vendors are on the same page when it comes to ATM standards &amp;amp; we had to have a senior Cisco engineer come in &amp;amp; rewrite the firmware at install. So we were not sure from where our problem stemmed. This is probably why the net group was reluctant to remain current - we finally forced them to come up when the problem became untenable&lt;BR /&gt;We are a mixed host (SUN &amp;amp; HP) shop &amp;amp; this problem was only in our larger HP (V &amp;amp; K-class) &amp;amp; only affected the floater. This problem did not affect SUN's HA product, though - just HP MC/SG.&lt;BR /&gt;We always also had problems with situations when the switches would lock up or go 100% CPU such that no traffic would move. If this occurred &amp;amp; lasted longer that 30-45 minutes then we would HAVE to reboot the HPs &amp;amp; SUNs (ATM only) to clear the problem. Thank god we were a testing lab &amp;amp; not production....&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Jeff</description>
    <pubDate>Thu, 28 Mar 2002 19:05:30 GMT</pubDate>
    <dc:creator>Jeff Schussele</dc:creator>
    <dc:date>2002-03-28T19:05:30Z</dc:date>
    <item>
      <title>Multicast MAC address</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691890#M712795</link>
      <description>Does MC/ServiceGuard 11.13 multicast MAC addresses across the networks?</description>
      <pubDate>Wed, 27 Mar 2002 14:37:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691890#M712795</guid>
      <dc:creator>Jim Carter</dc:creator>
      <dc:date>2002-03-27T14:37:09Z</dc:date>
    </item>
    <item>
      <title>Re: Multicast MAC address</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691891#M712796</link>
      <description>Could you elaborate a bit more on the question?&lt;BR /&gt;SG (all versions) will re-arp the MAC address of the card which the relocatable ip address moves to, but I am not sure thaht is what you are asking</description>
      <pubDate>Wed, 27 Mar 2002 17:40:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691891#M712796</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2002-03-27T17:40:55Z</dc:date>
    </item>
    <item>
      <title>Re: Multicast MAC address</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691892#M712797</link>
      <description>The real issue deals with CampusCluster. When a package fails from one data center to another, the switches in the new data center need to learn the new IP/MAC relationship. The network manager wants to know how the switches perform this function in a &amp;lt; 5 minute timeframe.</description>
      <pubDate>Wed, 27 Mar 2002 18:15:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691892#M712797</guid>
      <dc:creator>Jim Carter</dc:creator>
      <dc:date>2002-03-27T18:15:41Z</dc:date>
    </item>
    <item>
      <title>Re: Multicast MAC address</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691893#M712798</link>
      <description>This is what I thought you might be asking :-}&lt;BR /&gt;When the package ip gets added to a new LAN card, there is an automatic arp rebroadcast to set up the MAC/IP address relationship on network devices. This happens as the IP address is added to the network card, so virtually no delay. Wher ewe have seen problems is wher eolder net devices do NOT accept arp rebroadcasts and only refresh their arp cache after a set period of something like 10 nminutes.&lt;BR /&gt;HTH</description>
      <pubDate>Wed, 27 Mar 2002 18:50:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691893#M712798</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2002-03-27T18:50:28Z</dc:date>
    </item>
    <item>
      <title>Re: Multicast MAC address</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691894#M712799</link>
      <description>James,&lt;BR /&gt;&lt;BR /&gt; I've seen the exact problem Melvyn describes on older Ciscos with outdated firmware. We've even experienced a greater level of frustration with these units ie they will even literally "lose" the floater IP from their ARP table altogether for periods FAR greater than 10 minutes - sometimes until you reassert the IP.&lt;BR /&gt;Only solution was to upgrade the Ciscos.&lt;BR /&gt;&lt;BR /&gt;RGds,&lt;BR /&gt;Jeff</description>
      <pubDate>Wed, 27 Mar 2002 19:16:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691894#M712799</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2002-03-27T19:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: Multicast MAC address</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691895#M712800</link>
      <description>Jeff,&lt;BR /&gt;     Can you tell me if you experienced this issue with the Cisco 6900 series?</description>
      <pubDate>Thu, 28 Mar 2002 14:38:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691895#M712800</guid>
      <dc:creator>Jim Carter</dc:creator>
      <dc:date>2002-03-28T14:38:51Z</dc:date>
    </item>
    <item>
      <title>Re: Multicast MAC address</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691896#M712801</link>
      <description>James,&lt;BR /&gt;&lt;BR /&gt; No, we are a large ATM/SONET  based site &amp;amp; we were having poblems with the 12000 series switches.  &lt;BR /&gt;These are our main switches. &lt;BR /&gt;But then again we had trouble from the get-go w/these switches as not all vendors are on the same page when it comes to ATM standards &amp;amp; we had to have a senior Cisco engineer come in &amp;amp; rewrite the firmware at install. So we were not sure from where our problem stemmed. This is probably why the net group was reluctant to remain current - we finally forced them to come up when the problem became untenable&lt;BR /&gt;We are a mixed host (SUN &amp;amp; HP) shop &amp;amp; this problem was only in our larger HP (V &amp;amp; K-class) &amp;amp; only affected the floater. This problem did not affect SUN's HA product, though - just HP MC/SG.&lt;BR /&gt;We always also had problems with situations when the switches would lock up or go 100% CPU such that no traffic would move. If this occurred &amp;amp; lasted longer that 30-45 minutes then we would HAVE to reboot the HPs &amp;amp; SUNs (ATM only) to clear the problem. Thank god we were a testing lab &amp;amp; not production....&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Jeff</description>
      <pubDate>Thu, 28 Mar 2002 19:05:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/multicast-mac-address/m-p/2691896#M712801</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2002-03-28T19:05:30Z</dc:date>
    </item>
  </channel>
</rss>

