This needs to go into the FAQ around cluster/ or in the cluster config section. See https://bugzilla.redhat.com/show_bug.cgi?id=468173 for details
Due to be written Mon 3 Nov and will be available for technical review ~ 5 Nov LKB
Hi Alan, Sorry to leave this so late, but I've just read through the bug you linked to and I'm still clueless as to what this is about. I'm going to go ahead and release this book for tech review without this bug for now, BUT if you can get some info (or a draft version of the type of thing you're looking for here) to me in the next couple of days (say by the end of this week), then we still might be able to sneak it in. Thanks, LKB
From Mick Goulish: Redundant-ring mode in OpenAIS is a redundancy mechanism at the level of the network interface. Here are instructions for setting it up. 1. Find a machine with two network interfaces as reported by "/sbin/ifconfig -a". One such machine is MRG7. ( It has eth0 and eth1. ) 2. Also, the machine should be RHEL 5.X. Ideally 5.2, since the current customer for this functionality requires 5.2. This functionality is not available for RHEL 4.*. 3. Make sure openais and openais-devel packages are installed on the machine. 4. As root: "service openais stop" 5. Use something very much like this example as your /etc/ais/openais.conf file: ------------------ start openais.conf ----------------- # Please read the openais.conf.5 manual page totem { version: 2 secauth: off threads: 0 rrp_mode: passive # ------------ eth1 ----------------- interface { ringnumber: 0 bindnetaddr: 20.0.10.0 mcastaddr: 226.94.1.1 mcastport: 5405 } # ------------ eth0 ----------------- interface { ringnumber: 1 bindnetaddr: 10.16.40.0 mcastaddr: 226.94.1.1 mcastport: 5405 } } logging { debug: off timestamp: on # added these lines: to_stderr: yes to_syslog: yes logger { ident: CPG debug: off } } amf { mode: disabled } ------------------- end openais.conf ------------------ 6. Use the above example for the file /etc/ais/openais.conf Except edit it to get the correct addresses in the two bindnetaddr fields. Here's how to get the correct address: 6.1 For each active interface, the command "/sbin/ifconfig -a" will report an address and a mask. 6.2 Bitwise-AND the two together to find the correct value for the bindnetaddr field. 7. After editing the /etc/ais/openais.conf file, become root and do this: "service openais start". 7. Run any (or all) cluster tests -- "make check" or standalone. They should behave as usual. You are now running the cluster against a two-ring openais set-up.
(In reply to comment #3) > From Mick Goulish: <snip> > > > 6. Use the above example for the file /etc/ais/openais.conf > Except edit it to get the correct addresses in the two bindnetaddr fields. > Here's how to get the correct address: > > 6.1 For each active interface, the command "/sbin/ifconfig -a" > will report an address and a mask. > > 6.2 Bitwise-AND the two together to find the correct value for > the bindnetaddr field. How can I do this from the shell prompt? $((192.168.0.1 & 255.255.255.0)) doesn't seem to work for me :( L
Here's a cool way that you can do a binary AND of two such addresses -- one component at a time. ( Thanks mattf! ) For example, to do 148 & 250, do this: python -c "print 148&250" ( It's not good to use as example where the mask is all 255s and 0s, since 255 & X == X and 0 & X == 0 )
Thanks Mick! This information is now in, and will be available for review shortly. LKB
Updated. Now available for further review. LKB