Re: [ovs-discuss] Port satturation?

2011-10-12 Thread Vladimir Nikolić
ut on OVS? Or to enter static mac addresses into switch mac address table? Thanks for you help. Regards On 12. 10. 2011 02:52, Jesse Gross wrote: > 2011/10/11 Vladimir Nikolić : >> The switch should learn syslog server mac address from the arp response, >> and send traffic only to up

Re: [ovs-discuss] Port satturation?

2011-10-11 Thread Vladimir Nikolić
The switch should learn syslog server mac address from the arp response, and send traffic only to uplink. Regards On 12. 10. 2011 01:19, Jesse Gross wrote: > 2011/10/11 Vladimir Nikolić : >> VM1 does not know MAC address of syslog server. VM1 sends arp message to >> ff:ff:ff:ff:f

Re: [ovs-discuss] Port satturation?

2011-10-11 Thread Vladimir Nikolić
not send broadcast message, it sends only syslog UDP packets to syslog server MAC address. Switch should know that syslog server MAC is not on its ports, and should not send that traffic to port vif2.0 (xapi2). Regards On 12. 10. 2011 00:34, Jesse Gross wrote: > 2011/10/11 Vladimir Niko

Re: [ovs-discuss] Port satturation?

2011-10-11 Thread Vladimir Nikolić
Yes, there are occasionally arp records (showed by tcpdump on VM2), but there is 1000x more records for unicast traffic between VM1 and syslog server. I can see that traffic on VM2 (vif2.0) and xapi2 interface (tcpdump). Regards On 12. 10. 2011 00:12, Jesse Gross wrote: > 2011/10/11 Vladi

[ovs-discuss] Port satturation?

2011-10-11 Thread Vladimir Nikolić
Hi, we are expiriencing some very strange behaviour on our XenServer 6.0 server (openvswitch-1.0.99-104.9871). On fake bridge xapi2 we have 2 VM, each with one interface: # ovs-vsctl list-ports xapi2 vif1.0 (VM1, ip 1.1.1.1) vif2.0 (VM2, ip 1.1.1.2) VM1 is mail server, with traffic peaks at 15Mb