On 04/23/2013 02:20 PM, Greg Woods wrote: ... The two nodes are connected by a crossover > cable, and that is the link used for DRBD replication. So it seems as > though the only possibilities are a flaky NIC or a flaky cable, but in > that case, wouldn't I see some sort of hardware error logged? Anybody > else ever seen something like this?
If you pull the cable, you may get 'eth1 link down' somewhere (console, /var/log/messages), or not. If you have a hardware error on the NIC something should crash I think, though I don't remember ever seeing that. I've heartbeat (as in 3.0.4 w/ haresources) pings going over the crossover cable as well, so I don't specifically monitor that link or drbd status. I do monitor eth0 (for 'link detected' in the output of ethtool). I also have nagios checking drbd for UpToDate/UpToDate, but that's not part of the cluster. HTH -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
