On Fri, 2008-12-19 at 12:38 -0500, Peter Memishian wrote: > > bash-3.2# ifconfig redunder0 inet6 > > redunder0: flags=202100841<UP,RUNNING,MULTICAST,ROUTER,IPv6,CoS> mtu 1500 > index 11 > > inet6 fe80::214:4fff:fe8d:ce2e/10 > > groupname red > > bash-3.2# ipmpstat -i > > INTERFACE ACTIVE GROUP FLAGS LINK PROBE STATE > > redunder0 yes red0 --mbM-- up disabled ok > > > > The above doesn't look quite right, however. I have a valid IPv6 > > interface in this group, and it has a link-local address configured on > > the underlying interface. Shouldn't that automatically cause in.mpathd > > to use IPv6 for probing? Meem, am I forgetting to do something to > > enable IPv6 probes? > > Yes, you need to set -failover (this is required even for IPv6 since not > everyone may want to use probes).
Ah, that worked: bash-3.2# ifconfig redunder0 inet6 -failover INTERFACE ACTIVE GROUP FLAGS LINK PROBE STATE redunder0 yes red0 --mbM-- up ok ok bash-3.2# ipmpstat -t INTERFACE MODE TESTADDR TARGETS redunder0 multicast fe80::214:4fff:fe8d:ce2e fe80::203:baff:fe44:3252 fe80::203:baff:fe2a:255c fe80::214:4fff:fe7a:5320 fe80::203:baff:fe94:2f92 fe80::203:baff:fe29:fe84 bash-3.2# ipmpstat -p TIME INTERFACE PROBE NETRTT RTT RTTAVG TARGET 1.46s redunder0 91 0.25ms 0.28ms 0.36ms fe80::214:4fff:fe7a:5320 2.82s redunder0 92 0.43ms 0.46ms 0.59ms fe80::203:baff:fe94:2f92 4.31s redunder0 93 0.44ms 0.46ms 0.56ms fe80::203:baff:fe29:fe84 One thing I noticed before I enabled the IPv6 test address was that "ipmpstat -p" would simply hang there without displaying anything (no header). Would it be simple to have it return and tell me that no interfaces are probing instead of sitting there forever? Thanks, -Seb
