Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
No need for a switch with any modern nic - they had auto mdi-x. Use standard cables and nic will take care of crossing connection as needed.
Jake
----- Reply message -----
From: "Walter Robert Ditzler" <ditwal001 at gmail.com>
To: "Eduardo Diaz - Gmail" <ediazrod at gmail.com>
Cc: "Yount, William D" <Yount.William at menloworldwide.com>, "drbd-user at lists.linbit.com" <drbd-user at lists.linbit.com>
Subject: [DRBD-user] Corosync Configuration
Date: Tue, Jun 12, 2012 10:24 am
hi all,
we use cat6 normal 30cm cable on hp dl320, since 3 years, never ever had any problems. now we even use both hp dl 320 nics with bonding!
cheers walter
On 12.06.2012, at 16:04, Eduardo Diaz - Gmail <ediazrod at gmail.com> wrote:
> Don't use crossover cables.. In my experience use crossover cables for two node cluster make only problems... use a simple switch..
>
> Why don't use a simple configure..http://oss.linbit.com/drbd-mc/
>
> regards!
>
>
> On Thu, Jun 7, 2012 at 7:22 AM, Yount, William D <Yount.William at menloworldwide.com> wrote:
> I am following this guide: http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/txt/Clusters_from_Scratch/Clusters_from_Scratch.txt
>
>
>
> I have two servers with two NICS each:
>
> Server 1:
>
> NIC-A: 10.89.99.31
>
> NIC-B: 192.168.1.5
>
> Server 2:
>
> NIC-A: 10.89.99.32
>
> NIC-B: 192.168.1.10
>
>
>
> I am at the section where I need to configure corosync.conf. I tried doing the command line:
>
> 1. export ais_port=4000
>
> 2. export ais_mcast=226.94.1.1
>
> 3. export ais_addr=`ip addr | grep “inet” | tail –n 1 | awk ‘{print $4}’ | sed s/255/0/
>
> 4. env | grep ais_ais_mcast=226.94.1.1
>
>
>
> The last command doesn’t show anything. I was reading the notes and it said that this was for a simple setup with one NIC. I am editing the corosyn.conf file manually. I was wondering if anyone could look at the attached configuration and let me know if that is suitable or should I be doing something different. The 192.168.1.X addresses are for the cross-over connection that directly links both computers together and which I plan to use for sync/pacemaker traffic.
>
>
>
>
>
>
>
>
>
> Thanks,
>
> William Yount | Systems Analyst | Menlo Worldwide | Cell: 901-654-9933
>
> Safety | Leadership | Integrity | Commitment | Excellence
>
> Please consider the environment before printing this e-mail
>
>
>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20120612/06cfb6c6/attachment.htm>