Hi Mikael, For active/passive bonds, it is currently not possible to explicitly choose which slave will be the active/primary slave and which ones are the used for backup.
However, I believe that the following guidelines apply: * If one of the PIFs that your are bonding together has an IP address in dom0 (e.g. the management interface), then that PIF will become the primary slave. * If not, then the first PIF that you mention in the 'xe bond-create' call will become the primary slave. Let me know if that works for you (or not). Cheers, Rob > -----Original Message----- > From: [email protected] [mailto:xen-api- > [email protected]] On Behalf Of Mikael Hugo > Sent: 01 March 2013 9:26 AM > To: Mike McClurg > Cc: [email protected] > Subject: Re: [Xen-API] Active-Passive Fast/Slow path > > Hi, > > >Are you talking about setting openvswitch's lacp-time parameter to either > fast or slow? This feature doesn't exist yet, but it should >be in a > soon-to-be > released version of xenserver. I'm not sure when it will trickle down into > XCP, though. > > I want my servers to have a secondary passive connection to one router for > backup, but I want it to fall back to the primary when up. > > So I would like to make one primary slave and one secondary slave with > automatic fallback. > > /Mikael > > _______________________________________________ > Xen-api mailing list > [email protected] > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list [email protected] http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
