Mike Gerdts writes: > bge0 0.0.0.0 RUNNING,NOFAILOVER group native > bge0:1 10.0.0.1 UP,RUNNING > bge1 0.0.0.0 RUNNING,NOFAILOVER group native
Why wouldn't it be more like this? bge0 10.0.0.1 UP,RUNNING group native bge1 0.0.0.0 RUNNING,STANDBY,INACTIVE group native Since you're not using probes here, what do the address zero nofailover interfaces buy? > Now, if I pull bge0 everything fails over to bge1 as expected. > However, when I reconnect the cable to bge0, 10.0.0.1 is on bge0 (not > bge0:1), 10.0.1.1 is on bge1000 (not bge1000:1), and 10.0.2.1 is on > bge2000 (not bge2000:1). I believe IPMP sees all logical interfaces as equivalent, so it doesn't make a distinction between bge0:1 and bge0:0 (aka bge0). It has no reason to avoid bge0:0 that I can see -- well, beyond the zone interfaces, and I'm not actually sure how those will be handled in this case. > Then, if I pull bge1 I notice that the addresses on bge1:1, bge1001:1, > and bge2001:1 do not fail over properly. The interfaces show that > they are FAILED and the RUNNING flag is cleared, but the addresses > stay where they started. That sounds like a bug, but one that's potentially triggered by an unusual starting configuration. Address zero + nofailover is the odd part. > Does this sound like a configuration error or bug? Perhaps a bit of both. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
