Probably no traffic is going through OVS. Your vm_x VMs have two interfaces. The first one (in bridged mode) connects them directly to some other network. They seem to be getting IP addresses, probably form a DHCP server, and the default route probably goes through these interfaces and not through the second (internal network mode) interface.
So... disable the bridged mode interfaces on vm_1/vm_2/vm_3 or do something else to force traffic to go through the intnet interface. -- Murphy On Apr 9, 2013, at 8:42 PM, Karthik Sharma wrote: > Hi, > > But my problem is that I don't seem other mac addresses in the log at all.I > have run this for around 5 mins.I just see one mac adddress which belongs to > the bridge lan0. > Is there some way to see more detailed output as > > mac addr a is connected to lan0 port N etc..... > > > I have also attached the trace of the output of > > ./pox.py log.level --DEBUG forwarding.l2_learning > > with this e-mail > > > Regards, > Karthik. > > > > the ifconfig output of the Virtual machines are shown below > > ifconfig for vm_switch > ------------------------------- > > eth1 Link encap:Ethernet HWaddr 08:00:27:e1:e3:fd > inet6 addr: fe80::a00:27ff:fee1:e3fd/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:37 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:7909 (7.9 KB) > > eth3 Link encap:Ethernet HWaddr 08:00:27:be:d4:7c > inet addr:192.168.129.124 Bcast:192.168.129.255 Mask:255.255.254.0 > inet6 addr: fe80::a00:27ff:febe:d47c/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:904 errors:0 dropped:32 overruns:0 frame:0 > TX packets:130 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:101694 (101.6 KB) TX bytes:16081 (16.0 KB) > > eth4 Link encap:Ethernet HWaddr 08:00:27:80:e2:be > inet6 addr: fe80::a00:27ff:fe80:e2be/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:44 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:8538 (8.5 KB) > > eth5 Link encap:Ethernet HWaddr 08:00:27:1a:f8:a5 > inet6 addr: fe80::a00:27ff:fe1a:f8a5/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:37 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:7565 (7.5 KB) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:66 errors:0 dropped:0 overruns:0 frame:0 > TX packets:66 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:5737 (5.7 KB) TX bytes:5737 (5.7 KB) > > > ifconfig for vm_1 > ------------------------ > > eth0 Link encap:Ethernet HWaddr 08:00:27:a4:56:89 > inet addr:192.168.129.22 Bcast:192.168.129.255 Mask:255.255.254.0 > inet6 addr: fe80::a00:27ff:fea4:5689/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:759 errors:0 dropped:30 overruns:0 frame:0 > TX packets:119 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:88324 (88.3 KB) TX bytes:14035 (14.0 KB) > > eth1 Link encap:Ethernet HWaddr 08:00:27:f4:78:53 > inet6 addr: fe80::a00:27ff:fef4:7853/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1 errors:0 dropped:0 overruns:0 frame:0 > TX packets:27 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:342 (342.0 B) TX bytes:5802 (5.8 KB) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:50 errors:0 dropped:0 overruns:0 frame:0 > TX packets:50 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:4489 (4.4 KB) TX bytes:4489 (4.4 KB) > > ifconfig for vm_2 > ------------------------- > eth0 Link encap:Ethernet HWaddr 08:00:27:6f:26:bb > inet addr:192.168.129.171 Bcast:192.168.129.255 Mask:255.255.254.0 > inet6 addr: fe80::a00:27ff:fe6f:26bb/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:800 errors:0 dropped:28 overruns:0 frame:0 > TX packets:123 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:93488 (93.4 KB) TX bytes:14834 (14.8 KB) > > eth1 Link encap:Ethernet HWaddr 08:00:27:dc:b6:4b > inet6 addr: fe80::a00:27ff:fedc:b64b/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:27 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:5901 (5.9 KB) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:52 errors:0 dropped:0 overruns:0 frame:0 > TX packets:52 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:4645 (4.6 KB) TX bytes:4645 (4.6 KB) > > > ifconfig for vm_3 > ------------------------ > eth0 Link encap:Ethernet HWaddr 08:00:27:57:9e:03 > inet addr:192.168.129.174 Bcast:192.168.129.255 Mask:255.255.254.0 > inet6 addr: fe80::a00:27ff:fe57:9e03/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:677 errors:0 dropped:28 overruns:0 frame:0 > TX packets:120 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:79799 (79.7 KB) TX bytes:14448 (14.4 KB) > > eth1 Link encap:Ethernet HWaddr 08:00:27:ae:a6:62 > inet6 addr: fe80::a00:27ff:feae:a662/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:5437 (5.4 KB) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:52 errors:0 dropped:0 overruns:0 frame:0 > TX packets:52 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:4645 (4.6 KB) TX bytes:4645 (4.6 KB) > > > > > > > On 10 April 2013 15:25, Murphy McCauley <[email protected]> wrote: > By default, switches usually send incomplete packets to the switch in case of > a table miss. For many protocols (including TCP), the incomplete packet is > usually enough to parse all the headers and it's just payload that gets > chopped off. In the case of DHCP, it often means that the DHCP packet can't > be entirely parsed, and this message indicates that this has occurred. > > In general, these messages aren't problematic, which is why they're at info > level and not warn. It's possible it'd be preferable if they were at debug > level, but they are actually informational -- they are about an event that > has actually occurred, not hints that are meant to be useful for debugging > (something like this is the rationale for why they are at info). If they > bother you, just turn them off with log.level --packet=WARN. > > (Or you can have the switches send full packets by running the > misc.full_payload component, but that seems sort of silly.) > > -- Murphy > > On Apr 9, 2013, at 8:06 PM, Karthik Sharma wrote: > >> I have 4 virtual Machine (Ubuntu 12.04) running on a host that is also >> running Ubuntu 12.04 >> The Virtual Machines are named as >> >> vm-1 >> vm-2 >> vm-3 >> switch-vm >> >> Below are the network settings on switch-vm >> >> >> Adapter 1: >> >> Intel PRO/1000 MT Desktop (Bridged adapter, eth0) >> Adapter 2: >> >> Intel PRO/1000 MT Desktop (Internal network, 'intnet-1') >> Adapter 3: >> >> Intel PRO/1000 MT Desktop (Internal network, 'intnet-2') >> Adapter 4: >> >> Intel PRO/1000 MT Desktop (Internal network, 'intnet-3') >> >> >> Network settings on vm-1 >> >> >> >> Adapter 1: >> >> Intel PRO/1000 MT Desktop (Bridged adapter, eth0) >> Adapter 2: >> >> Intel PRO/1000 MT Desktop (Internal network, 'intnet-1') >> >> Network settings on vm-2 >> >> Adapter 1: >> >> Intel PRO/1000 MT Desktop (Bridged adapter, eth0) >> Adapter 2: >> >> Intel PRO/1000 MT Desktop (Internal network, 'intnet-2') >> >> >> Network settings on vm >> >> Adapter 1: >> >> Intel PRO/1000 MT Desktop (Bridged adapter, eth0) >> Adapter 2: >> >> Intel PRO/1000 MT Desktop (Internal network, 'intnet-3') >> >> >> I have installed ovs and pox controller on switch-vm >> >> sudo ovs-vsctl show >> sudo ovs-vsctl add-br lan0 >> sudo ovs-vsctl add-port lan0 eth1 >> sudo ovs-vsctl add-port lan0 eth4 >> sudo ovs-vsctl add-port lan0 eth5 >> >> sudo ovs-vsctl set-controller lan0 tcp:127.0.0.1:6633 >> >> ./pox.py log.level --DEBUG forwarding.l2_learning >> >> >> The output is as follows >> >> POX 0.1.0 (betta) / Copyright 2011-2013 James McCauley, et al. >> DEBUG:core:POX 0.1.0 (betta) going up... >> DEBUG:core:Running on CPython (2.7.3/Aug 1 2012 05:14:39) >> DEBUG:core:Platform is >> Linux-3.5.0-23-generic-x86_64-with-Ubuntu-12.04-precise >> INFO:core:POX 0.1.0 (betta) is up. >> DEBUG:openflow.of_01:Listening on 0.0.0.0:6633 >> INFO:openflow.of_01:[08-00-27-1a-f8-a5 1] connected >> DEBUG:forwarding.l2_learning:Connection [08-00-27-1a-f8-a5 1] >> INFO:packet:(dhcp parse) warning DHCP packet data too short to parse >> header: data len 86 >> INFO:packet:(dhcp parse) warning DHCP packet data too short to parse >> header: data len 86 >> INFO:packet:(dhcp parse) warning DHCP packet data too short to parse >> header: data len 86 >> INFO:packet:(dhcp parse) warning DHCP packet data too short to parse >> header: data len 86 >> INFO:packet:(dhcp parse) warning DHCP packet data too short to parse >> header: data len 86 >> >> Why is this error coming? >> >> Regards, >> Karthik. > > > <trace1.txt>
