The corosync configuration is default, except for a minor change I made to the 
interface section:interface {
                # The following values need to be set based on your environment
                ringnumber: 0
                #bindnetaddr: 127.0.0.1
                bindnetaddr: 192.168.10.0
                mcastaddr: 226.94.1.1
                mcastport: 5405
  } Notice that it doesn't have any hostnames included at all, so no carbon or 
carbon.domain.com.I got this from some basic tutorial, probably not what it 
should be. As for DRBD:
global {
        usage-count no;
}
common {
        syncer {
                rate 30M;
        }
}
resource disk0 {
        protocol C;
        startup {
                wfc-timeout 20;
                outdated-wfc-timeout 15;
                degr-wfc-timeout 15;
                become-primary-on carbon;
        }
        disk {
                fencing resource-only;
        }
        net {
                cram-hmac-alg sha1;
                shared-secret "ElementSessions";
        }
        handlers {
                fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
                after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
        }
        on carbon {
                device /dev/drbd0;
                disk /dev/sda4;
                address 10.128.1.1:7788;
                meta-disk internal;
        }
        on oxygen {
                device /dev/drbd0;
                disk /dev/sda4;
                address 10.128.1.2:7788;        }
}
 I did comment out the 127.0.1.1 section of /etc/hosts on both 
machines."carbon" now points to 10.128.1.1 while "carbon.domain.com" still 
points to 192.168.10.151.Tried the following (from your tutorial), but didn't 
work out:ipmitool -I lan -U admin -P secret -H 192.168.10.151 chassis 
statusError: Unable to establish LAN session
Error sending Chassis Status command                                            
          
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to