<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:lxnf98mm@comcast.net">lxnf98mm@comcast.net</a> wrote:
<blockquote
cite="mid:alpine.LRH.2.00.1008261255020.23046@rray.drdc.mstc.ms.gov"
type="cite">On Thu, 26 Aug 2010, <a class="moz-txt-link-abbreviated" href="mailto:lxnf98mm@comcast.net">lxnf98mm@comcast.net</a> wrote:
<br>
<br>
<blockquote type="cite">On Thu, 26 Aug 2010, Dan Frincu wrote:
<br>
<br>
<blockquote type="cite"> In OpenAIS for example, in
/etc/ais/openais.conf you have a directive
<br>
called interface. In this directive you specify a ringnumber,
bindnetaddr,
<br>
mcastaddr and mcastport. Configuring 2 communication channels means
using
<br>
adding rrp_mode: passive, ringnumber 0 and ringnumber 1, two interface
<br>
directives in which you use different bindnetaddr IP addresses (ex:
<br>
10.0.0.1 and 10.0.0.2, or whatever IP's you use, but preferably each
IP
<br>
address should be assigned to a different network interface), two
<br>
different mcastaddr multicast groups (or mcastport, but I'd recommed
<br>
different mcastaddr's in the range of 239.x.x.x).
<br>
<br>
The principle behind it is if one communication channel (network card,
IP
<br>
address connectivity, multicast group/port) fails, the other one is
still
<br>
there for redundancy. I see this similar to the way ring network
<br>
topologies work, without the token.
<br>
<br>
Regards,
<br>
Dan.
<br>
<br>
p.s.: Andrew, nice to have you back, to paraphrase a famous quote "Mr.
<br>
Anderson. Welcome back, we missed you."
<br>
<br>
</blockquote>
<br>
Thanks that helps a lot
<br>
Just one more thing
<br>
If two interfaces are configured are they both used equally
<br>
<br>
Richard
<br>
<br>
</blockquote>
<br>
I believe I can answer my own question
<br>
<a class="moz-txt-link-freetext" href="http://www.novell.com/documentation/sle_ha/book_sleha/?page=/documentation/sle_ha/book_sleha/data/sec_ha_installation_setup.html">http://www.novell.com/documentation/sle_ha/book_sleha/?page=/documentation/sle_ha/book_sleha/data/sec_ha_installation_setup.html</a>
<br>
<br>
Use the Redundant Ring Protocol (RRP) to tell the cluster how to use
these interfaces. RRP can have three modes (rrp_mode): if set to
active, Corosync uses all interfaces actively. If set to passive,
Corosync uses the second interface only if the first ring fails.
<br>
<br>
Richard
<br>
<br>
</blockquote>
Also see
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<a href="http://linux.die.net/man/5/openais.conf">http://linux.die.net/man/5/openais.conf</a><br>
<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<span class="Apple-style-span"
style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; font-size: medium;"><span
class="Apple-style-span"
style="font-family: arial,sans-serif; font-size: 13px;"><dt>rrp_mode</dt>
<dd>This specifies the mode of redundant ring, which may be none,
active, or passive. Active replication offers slightly lower latency
from transmit to delivery in faulty network environments but with less
performance. Passive replication may nearly double the speed of the
totem protocol if the protocol doesn't become cpu bound. The final
option is none, in which case only one network interface will be used
to operate the totem protocol.
<p>If only one interface directive is specified, none is
automatically chosen. If multiple interface directives are specified,
only active or passive may be chosen.</p>
</dd>
</span></span><br>
<blockquote
cite="mid:alpine.LRH.2.00.1008261255020.23046@rray.drdc.mstc.ms.gov"
type="cite">
<blockquote type="cite">
<blockquote type="cite"> <a class="moz-txt-link-abbreviated" href="mailto:lxnf98mm@comcast.net">lxnf98mm@comcast.net</a> wrote:
<br>
> The DRBD manual says
<br>
> > It is absolutely vital to configure at least two
independent OpenAIS
<br>
> communication channels for this functionality to work correctly.
<br>
> > My Google'n has not yielded any results in the how to do
this > department
<br>
> I have DRBD configured and working properly with one channel
<br>
> Where can I find info to add a second channel
<br>
> > Richard
<br>
> > _______________________________________________
<br>
> Pacemaker mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>
<br>
> <a class="moz-txt-link-freetext" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
<br>
> > Project Home: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
<br>
> Getting started: >
<a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
<br>
> Bugs:
<br>
>
<a class="moz-txt-link-freetext" href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a>
<br>
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Dan FRINCU
Systems Engineer
CCNA, RHCE
Streamwide Romania
</pre>
</body>
</html>