On Fri, Apr 16, 2010 at 04:07:10PM -0500, Patrick Cotner wrote: > > > > On 04/16/2010 07:04 PM, Patrick Cotner wrote: > > > > cl_status hblinkstatus san02 eth2 reports 'dead' from san01.
But later you show > > > > cl_status hblinkstatus san02 eth1 >> dead << this is the problem So which one is it, eth1, eth2? Just to make sure you are tcpdump'ing on the right one. > Here is the output of tcpdump on the suspect ethernet port: > > san01:~# tcpdump -i eth2 > 21:02:42.459569 IP 10.1.10.2.46836 > 10.1.10.15.694: UDP, length 208 > 21:02:42.850461 IP 10.1.10.1.52791 > 10.1.10.15.694: UDP, length 208 > 21:02:43.463612 IP 10.1.10.2.46836 > 10.1.10.15.694: UDP, length 205 > 21:02:43.463619 IP 10.1.10.2.46836 > 10.1.10.15.694: UDP, length 208 > 21:02:43.854462 IP 10.1.10.1.52791 > 10.1.10.15.694: UDP, length 208 for a 10.1.10.0/28 this looks good. > 21:02:44.054676 STP 802.1d, Config, Flags [none], bridge-id > 8001.00:0b:5f:09:55:00.800e, length 43 STP? What exactly is this network, switched, virtual, direct link, ...? -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
