<?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: SG Heartbeat Subnet in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-heartbeat-subnet/m-p/3246858#M706271</link>
    <description>This document talks about multiple heartbeats in Serviceguard:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www1.itrc.hp.com/service/cki/search.do?category=c0&amp;amp;mode=id&amp;amp;searchString=UXSGKBAN00000164&amp;amp;searchCrit=allwords&amp;amp;docType=EngineerNotes&amp;amp;search.x=22&amp;amp;search.y=10" target="_blank"&gt;http://www1.itrc.hp.com/service/cki/search.do?category=c0&amp;amp;mode=id&amp;amp;searchString=UXSGKBAN00000164&amp;amp;searchCrit=allwords&amp;amp;docType=EngineerNotes&amp;amp;search.x=22&amp;amp;search.y=10&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;&lt;BR /&gt;Kent M. Ostby&lt;BR /&gt;</description>
    <pubDate>Tue, 13 Apr 2004 14:53:34 GMT</pubDate>
    <dc:creator>Kent Ostby</dc:creator>
    <dc:date>2004-04-13T14:53:34Z</dc:date>
    <item>
      <title>SG Heartbeat Subnet</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-heartbeat-subnet/m-p/3246855#M706268</link>
      <description>&lt;BR /&gt;I'm about to cluster 2 rp84x0's each fitted with 2 (A5506B) 4 port 100TX NIC's.&lt;BR /&gt;&lt;BR /&gt;I have 1 port on each NIC used as a primary and standby data LAN ( i.e a single bridged SUBNET)&lt;BR /&gt;&lt;BR /&gt;Could I use 1 port on each NIC as a primary and standby heartbeat LAN. If so then I assume I would bridge this SUBNET as normal - or is there no such concept as a 'standby heartbeat' ?&lt;BR /&gt;&lt;BR /&gt;Obviously I would also be using the data LAN as a secondary heartbeat path but I have concerns about the network latency and would like some redundency on the primary heartbeat should I lose it!!.&lt;BR /&gt;&lt;BR /&gt;I have no intention of using crossover cables.&lt;BR /&gt;&lt;BR /&gt;I'd rather not use the other ports on the NIC to create further heartbeat SUBNETs as these may be used for other future data and backup networks. &lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;JJ</description>
      <pubDate>Tue, 13 Apr 2004 12:33:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-heartbeat-subnet/m-p/3246855#M706268</guid>
      <dc:creator>JJ_23</dc:creator>
      <dc:date>2004-04-13T12:33:45Z</dc:date>
    </item>
    <item>
      <title>Re: SG Heartbeat Subnet</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-heartbeat-subnet/m-p/3246856#M706269</link>
      <description>I don't think so there is a stanby heartbeat ting .&lt;BR /&gt;&lt;BR /&gt;THe heartbeat traffic goes on all specified lans . As long as there is path for the nodes to send and recieve heartbeat traffic , there will not be cluster reformation .&lt;BR /&gt;&lt;BR /&gt;You are better off having two dedicated heratbeat subnets .</description>
      <pubDate>Tue, 13 Apr 2004 12:53:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-heartbeat-subnet/m-p/3246856#M706269</guid>
      <dc:creator>Ashwani Kashyap</dc:creator>
      <dc:date>2004-04-13T12:53:14Z</dc:date>
    </item>
    <item>
      <title>Re: SG Heartbeat Subnet</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-heartbeat-subnet/m-p/3246857#M706270</link>
      <description>Hi JJ,&lt;BR /&gt;&lt;BR /&gt;Try this link and see if it helps.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/T1453-90001/T1453-90001_top.html&amp;amp;con=/hpux/onlinedocs/T1453-90001/00/00/20-con.html&amp;amp;toc=/hpux/onlinedocs/T1453-90001/00/00/20-toc.html&amp;amp;searchterms=with%7cMC/ServiceGuard%7cVLANs&amp;amp;queryid=20040413-121146" target="_blank"&gt;http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/T1453-90001/T1453-90001_top.html&amp;amp;con=/hpux/onlinedocs/T1453-90001/00/00/20-con.html&amp;amp;toc=/hpux/onlinedocs/T1453-90001/00/00/20-toc.html&amp;amp;searchterms=with%7cMC/ServiceGuard%7cVLANs&amp;amp;queryid=20040413-121146&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I had a similar situation once where is sperated the two networks using vlan.&lt;BR /&gt;&lt;BR /&gt;lan0 failvoer to lan3 &lt;BR /&gt;lan1 failover to lan2&lt;BR /&gt;&lt;BR /&gt;Also note that the use of a private heartbeat network is not advisable. Check out this link.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B3936-90065/B3936-90065_top.html&amp;amp;con=/hpux/onlinedocs/B3936-90065/00/00/30-con.html&amp;amp;toc=/hpux/onlinedocs/B3936-90065/00/00/30-toc.html&amp;amp;searchterms=Configuration%7cPlanning%7cCluster&amp;amp;queryid=20040413-121539" target="_blank"&gt;http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B3936-90065/B3936-90065_top.html&amp;amp;con=/hpux/onlinedocs/B3936-90065/00/00/30-con.html&amp;amp;toc=/hpux/onlinedocs/B3936-90065/00/00/30-toc.html&amp;amp;searchterms=Configuration%7cPlanning%7cCluster&amp;amp;queryid=20040413-121539&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Apr 2004 13:16:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-heartbeat-subnet/m-p/3246857#M706270</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2004-04-13T13:16:58Z</dc:date>
    </item>
    <item>
      <title>Re: SG Heartbeat Subnet</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-heartbeat-subnet/m-p/3246858#M706271</link>
      <description>This document talks about multiple heartbeats in Serviceguard:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www1.itrc.hp.com/service/cki/search.do?category=c0&amp;amp;mode=id&amp;amp;searchString=UXSGKBAN00000164&amp;amp;searchCrit=allwords&amp;amp;docType=EngineerNotes&amp;amp;search.x=22&amp;amp;search.y=10" target="_blank"&gt;http://www1.itrc.hp.com/service/cki/search.do?category=c0&amp;amp;mode=id&amp;amp;searchString=UXSGKBAN00000164&amp;amp;searchCrit=allwords&amp;amp;docType=EngineerNotes&amp;amp;search.x=22&amp;amp;search.y=10&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;&lt;BR /&gt;Kent M. Ostby&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Apr 2004 14:53:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-heartbeat-subnet/m-p/3246858#M706271</guid>
      <dc:creator>Kent Ostby</dc:creator>
      <dc:date>2004-04-13T14:53:34Z</dc:date>
    </item>
    <item>
      <title>Re: SG Heartbeat Subnet</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-heartbeat-subnet/m-p/3246859#M706272</link>
      <description>So if I read your question correctly, you wish to have (let us say) portA/nic1 &amp;amp; portA /nic2 on each node set as a bridged network for your data lan? The also put the heartbeat acoss this? Yes this is fine.&lt;BR /&gt;You then are looking at doing portC/nic1 and portC/nic2 on each node, setting them up as a bridged network, and using this as a dedicated heartbeat network? Also good, go ahead and do this.&lt;BR /&gt;This still leaves you 2 ports per nic free, gives you a heartbeat lan with a standby, and a data/heartbeat lan also with a standby.&lt;BR /&gt;&lt;BR /&gt;Good design I think ;-]&lt;BR /&gt;</description>
      <pubDate>Wed, 14 Apr 2004 02:20:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-heartbeat-subnet/m-p/3246859#M706272</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2004-04-14T02:20:09Z</dc:date>
    </item>
  </channel>
</rss>

