Only explanation I can come up with (and I didn’t want to send this email because it could be wrong) is since it is using VM's Mac address when registering with your switch It might be normal in an active-active bond on public interface, since new VM will have a different MAC, or MAC changes on virtual switch I might be wrong but I know it uses VM's mac address, like I said it is hard to pinpoint the issue but could be the case... When I have time I will trace packets on an active-active bond to better understand what's going on...
-----Original Message----- From: Fedi Ben Ali [mailto:ben.ali.fe...@gmail.com] Sent: Sunday, April 12, 2015 1:59 PM To: users@cloudstack.apache.org Subject: Re: Urgent : Xenserver Bond status change Any idea ??? 2015-04-12 0:13 GMT+01:00 Fedi Ben Ali <ben.ali.fe...@gmail.com>: > I've cheked my xensource.log and i have no trace of the issue(i keep > looking ,my bond is on Active/Active. All my bonds are configured on > two PIF that are connected to two switches thats why we are not using lacp. > > Thx > > 2015-04-11 23:00 GMT+01:00 Sam Ceylani <s...@mistercertified.com>: > >> adding or removing a vm shouldn't affect management bond status >> unless when cloudstack makes an API call to xen toolstack for adding >> or removing vm somehow xenserver's management interface is bounced >> with that API call, I would check xenserver logs under /var/log and >> you can determine the reason, i doubt it is related to cloudstack, >> it could also be a spanning-tree or lacp issue, check switch logs to >> determine if any of those sub systems on the switch causing this >> issue...what kind of bond is this? >> how is it configured on the switch,is it lacp or not basically? >> >> >> Thanks, >> >> Sam Ceylani, MBA >> Computer Engineer >> MisterCertified Inc. >> >> 301 W. Platt St. Suite 447, Tampa, FL >> 33606<x-apple-data-detectors://0/0> >> P 813<tel:813.264.6460>.264.6460<tel:813.264.6460> M >> 813<tel:813.416.7867>.416.7867<tel:813.416.7867> >> F 800<tel:800.553.9520>.553.9520<tel:800.553.9520> E >> sam.ceyl...@mistercertified.com<mailto:sam.ceyl...@mistercertified.co >> m> >> >> On Apr 11, 2015, at 5:52 PM, "Fedi Ben Ali" <ben.ali.fe...@gmail.com >> <mailto:ben.ali.fe...@gmail.com>> wrote: >> >> Hello , >> >> >> I'm working on a platform with many xenservers ,i'm using bonded >> interfaces for all the required cloudstack networks >> (management,guest,storage,public). >> >> All my networks works fine except the public network ,each time i add >> or remove VM from a cluster ,the xenserver log shows" the status of >> the bond has changed ". >> >> Did i miss some configuration ?? >> >> >> i 'll give my log output : >> >> WB5: Bond status has changed,"3","The status of the eth2+eth3+eth4 bond >> changed: 0/3 up (was 3/3)" WB5: Bond status has changed,"3","The status >> of the eth2+eth3+eth4 bond changed: 3/3 up (was 0/3)" >> WB1: Bond status has changed,"3","The status of the eth5+eth6+eth7 >> bond >> changed: 0/3 up (was 3/3)"," >> > >
