<?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: Network architecture for the M/C service guard in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/network-architecture-for-the-m-c-service-guard/m-p/2541841#M714976</link>
    <description>When the linkloop command fails it can be two things:&lt;BR /&gt;&lt;BR /&gt;1) physical problem: cable, NIC switch port etc.&lt;BR /&gt;2) logical problem: when the primary and standby lans are not in the same Vlan (subnet) on the switch linkloop will fail.</description>
    <pubDate>Tue, 17 Jul 2001 07:12:55 GMT</pubDate>
    <dc:creator>Mark van Hassel</dc:creator>
    <dc:date>2001-07-17T07:12:55Z</dc:date>
    <item>
      <title>Network architecture for the M/C service guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/network-architecture-for-the-m-c-service-guard/m-p/2541838#M714973</link>
      <description>I am implementing cluster setup for 2 HP L class server . The server has tree lan cards &lt;BR /&gt;one as primary , standby and heartbeat . Primary cards for the both the servers is attaced to a switch and standby cards to another switch . The switch has back to back connectivity so they should act as a bridge in case of lancard failure . &lt;BR /&gt;This setup seems to be not working . &lt;BR /&gt;The linkloop command gives FAILED status when I try to check connectivity from primary to standby network interface . Am I missing somthing ?</description>
      <pubDate>Mon, 18 Jun 2001 17:50:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/network-architecture-for-the-m-c-service-guard/m-p/2541838#M714973</guid>
      <dc:creator>vaibhav_1</dc:creator>
      <dc:date>2001-06-18T17:50:20Z</dc:date>
    </item>
    <item>
      <title>Re: Network architecture for the M/C service guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/network-architecture-for-the-m-c-service-guard/m-p/2541839#M714974</link>
      <description>Your setup sounds good, you probably need to check your switch configuration. linkloop between primary and standby lans must be possible for local lan failover to function (i.e. primary and standby lan must be on the same bridged network).&lt;BR /&gt;&lt;BR /&gt;You might want to refer to the somewhat outdated paper &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/ha/wpnetwork.pdf" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/ha/wpnetwork.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;for reference and you will find your setup on page 5 (figure 6). &lt;BR /&gt;&lt;BR /&gt;Carsten</description>
      <pubDate>Mon, 18 Jun 2001 18:33:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/network-architecture-for-the-m-c-service-guard/m-p/2541839#M714974</guid>
      <dc:creator>Carsten Krege</dc:creator>
      <dc:date>2001-06-18T18:33:59Z</dc:date>
    </item>
    <item>
      <title>Re: Network architecture for the M/C service guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/network-architecture-for-the-m-c-service-guard/m-p/2541840#M714975</link>
      <description>I would hazard a guess that the switch-2-switch connection may not be correct.&lt;BR /&gt;You need to do as Carsten says, and check all the configutrations on the switches.&lt;BR /&gt;It may be a worthwhile test to first check all the lan connections by connecting them all to just one switch to prove at least the cables are ok.</description>
      <pubDate>Tue, 19 Jun 2001 06:31:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/network-architecture-for-the-m-c-service-guard/m-p/2541840#M714975</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2001-06-19T06:31:19Z</dc:date>
    </item>
    <item>
      <title>Re: Network architecture for the M/C service guard</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/network-architecture-for-the-m-c-service-guard/m-p/2541841#M714976</link>
      <description>When the linkloop command fails it can be two things:&lt;BR /&gt;&lt;BR /&gt;1) physical problem: cable, NIC switch port etc.&lt;BR /&gt;2) logical problem: when the primary and standby lans are not in the same Vlan (subnet) on the switch linkloop will fail.</description>
      <pubDate>Tue, 17 Jul 2001 07:12:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/network-architecture-for-the-m-c-service-guard/m-p/2541841#M714976</guid>
      <dc:creator>Mark van Hassel</dc:creator>
      <dc:date>2001-07-17T07:12:55Z</dc:date>
    </item>
  </channel>
</rss>

