Mpathd errors

From: Hardison Leif (Leif.Hardison@comverse.com)
Date: Mon Mar 20 2006 - 11:16:06 EST


Hi,

I was wondering if someone with more experience regarding mpath could
sheed some light on the following log entries;

Mar 19 23:36:25 myhost in.mpathd[34]: [ID 997829 daemon.info] probe
status 2 Fake probe reply seq 65535 snxt 0 on ce4 from 192.168.99.33
Mar 19 23:36:48 myhost in.mpathd[34]: [ID 438866 daemon.info] probe
status 2 Duplicate probe reply seq 65535 snxt 0 on ce1 from 192.168.30.1
Mar 19 23:36:56 myhost in.mpathd[34]: [ID 438866 daemon.info] probe
status 2 Duplicate probe reply seq 65535 snxt 0 on ce2 from 192.168.30.1
Mar 19 23:37:06 myhost in.mpathd[34]: [ID 997829 daemon.info] probe
status 2 Fake probe reply seq 65535 snxt 0 on ce3 from 192.168.99.37
Mar 20 16:04:52 myhost in.mpathd[34]: [ID 398532 daemon.error] Cannot
meet requested failure detection time of 10000 ms on (inet ce4) new
failure detection time is 24934 ms
Mar 20 16:04:52 myhost in.mpathd[34]: [ID 398532 daemon.error] Cannot
meet requested failure detection time of 10000 ms on (inet ce4) new
failure detection time is 24934 ms
Mar 20 16:06:42 myhost in.mpathd[34]: [ID 398532 daemon.error] Cannot
meet requested failure detection time of 10000 ms on (inet ce4) new
failure detection time is 51422 ms
Mar 20 16:06:42 myhost in.mpathd[34]: [ID 398532 daemon.error] Cannot
meet requested failure detection time of 10000 ms on (inet ce4) new
failure detection time is 51422 ms
Mar 20 16:07:48 myhost in.mpathd[34]: [ID 122137 daemon.error] Improved
failure detection time 25711 ms
Mar 20 16:07:48 myhost in.mpathd[34]: [ID 122137 daemon.error] Improved
failure detection time 25711 ms
Mar 20 16:08:43 myhost in.mpathd[34]: [ID 122137 daemon.error] Improved
failure detection time 12855 ms
Mar 20 16:08:43 myhost in.mpathd[34]: [ID 122137 daemon.error] Improved
failure detection time 12855 ms

What would cause the Fake and Duplicate probes? Are they normal
messages that can be safely ignored?

Why failure detection time spike past 50,000 ms? Would it be due to an
interface running near capacity?

Thanks,

Leif
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:39:20 EDT