| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-05-11 | |||
| 15:52:32 | sean-k-mooney | if you log into the souce node and check the name of the tap device you can set up a watch command that will try do start dumping the packets | |
| 15:52:32 | sean-k-mooney | if you log into the souce node and check the name of the tap device you can set up a watch command that will try do start dumping the packets | |
| 15:52:50 | ignaziocassano | ok | |
| 15:52:50 | ignaziocassano | ok | |
| 15:52:57 | sean-k-mooney | e.g. watch -n1 " tcpudump -i tap..." | |
| 15:52:58 | sean-k-mooney | e.g. watch -n1 " tcpudump -i tap..." | |
| 15:53:40 | sean-k-mooney | basicaly what im wondering is will you see the RARP packets form qemu and will they be recived before ovs is configured | |
| 15:53:40 | sean-k-mooney | basicaly what im wondering is will you see the RARP packets form qemu and will they be recived before ovs is configured | |
| 15:54:04 | sean-k-mooney | you coudl similarly check on teh br-ex/phsyical interface connected to ovs | |
| 15:54:04 | sean-k-mooney | you coudl similarly check on teh br-ex/phsyical interface connected to ovs | |
| 15:54:19 | sean-k-mooney | to see if they are sent onto the physical network | |
| 15:54:19 | sean-k-mooney | to see if they are sent onto the physical network | |
| 15:57:09 | ignaziocassano | on the source node the interfcace is tap11fdfb84-4a | |
| 15:57:09 | ignaziocassano | on the source node the interfcace is tap11fdfb84-4a | |
| 15:58:28 | ignaziocassano | so I must run watch -n1 " tcpudump -i tap11fdfb84-4a" on the destination node ? | |
| 15:58:28 | ignaziocassano | so I must run watch -n1 " tcpudump -i tap11fdfb84-4a" on the destination node ? | |
| 16:01:31 | ignaziocassano | tcpdump: verbose output suppressed, use -v or -vv for full protocol decode | |
| 16:01:31 | ignaziocassano | tcpdump: verbose output suppressed, use -v or -vv for full protocol decode | |
| 16:01:32 | ignaziocassano | listening on tap11fdfb84-4a, link-type EN10MB (Ethernet), capture size 262144 bytes | |
| 16:01:32 | ignaziocassano | 18:00:49.552314 ARP, Request who-has 10.138.209.47 (Broadcast) tell 10.138.209.1, length 46 | |
| 16:01:32 | ignaziocassano | listening on tap11fdfb84-4a, link-type EN10MB (Ethernet), capture size 262144 bytes | |
| 16:01:32 | ignaziocassano | 18:00:49.552314 ARP, Request who-has 10.138.209.47 (Broadcast) tell 10.138.209.1, length 46 | |
| 16:01:33 | ignaziocassano | 18:00:49.552325 ARP, Request who-has 10.138.209.47 (Broadcast) tell 10.138.209.1, length 46 | |
| 16:01:33 | ignaziocassano | 18:00:49.556221 ARP, Request who-has 10.138.209.48 (Broadcast) tell 10.138.209.1, length 46 | |
| 16:01:33 | ignaziocassano | 18:00:49.552325 ARP, Request who-has 10.138.209.47 (Broadcast) tell 10.138.209.1, length 46 | |
| 16:01:33 | ignaziocassano | 18:00:49.556221 ARP, Request who-has 10.138.209.48 (Broadcast) tell 10.138.209.1, length 46 | |
| 16:01:34 | ignaziocassano | 18:00:49.556230 ARP, Request who-has 10.138.209.48 (Broadcast) tell 10.138.209.1, length 46 | |
| 16:01:34 | ignaziocassano | 18:00:49.855902 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 | |
| 16:01:34 | ignaziocassano | 18:00:49.556230 ARP, Request who-has 10.138.209.48 (Broadcast) tell 10.138.209.1, length 46 | |
| 16:01:34 | ignaziocassano | 18:00:49.855902 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 | |
| 16:01:35 | ignaziocassano | 18:00:50.009075 IP6 fe80::fc16:3eff:fe6b:8bee > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 | |
| 16:01:35 | ignaziocassano | 18:00:50.009117 IP6 fe80::fc16:3eff:fe6b:8bee > ff02::2: ICMP6, router solicitation, length 16 | |
| 16:01:35 | ignaziocassano | 18:00:50.009075 IP6 fe80::fc16:3eff:fe6b:8bee > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 | |
| 16:01:35 | ignaziocassano | 18:00:50.009117 IP6 fe80::fc16:3eff:fe6b:8bee > ff02::2: ICMP6, router solicitation, length 16 | |
| 16:01:36 | ignaziocassano | 18:00:50.265259 ARP, Reverse Request who-is fa:16:3e:6b:8b:ee (oui Unknown) tell fa:16:3e:6b:8b:ee (oui Unknown), length 46 | |
| 16:01:36 | ignaziocassano | 18:00:50.285607 ARP, Reverse Request who-is fa:16:3e:6b:8b:ee (oui Unknown) tell fa:16:3e:6b:8b:ee (oui Unknown), length 46 | |
| 16:01:36 | ignaziocassano | 18:00:50.265259 ARP, Reverse Request who-is fa:16:3e:6b:8b:ee (oui Unknown) tell fa:16:3e:6b:8b:ee (oui Unknown), length 46 | |
| 16:01:36 | ignaziocassano | 18:00:50.285607 ARP, Reverse Request who-is fa:16:3e:6b:8b:ee (oui Unknown) tell fa:16:3e:6b:8b:ee (oui Unknown), length 46 | |
| 16:01:37 | ignaziocassano | 18:00:50.293932 ARP, Request who-has 10.138.248.68 tell 10.138.248.68, length 28 | |
| 16:01:37 | ignaziocassano | 18:00:50.294153 IP6 fe80::f816:3eff:fe6b:8bee > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::f816:3eff:fe6b:8bee, length 32 | |
| 16:01:37 | ignaziocassano | 18:00:50.293932 ARP, Request who-has 10.138.248.68 tell 10.138.248.68, length 28 | |
| 16:01:37 | ignaziocassano | 18:00:50.294153 IP6 fe80::f816:3eff:fe6b:8bee > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::f816:3eff:fe6b:8bee, length 32 | |
| 16:01:38 | ignaziocassano | 18:00:50.344367 ARP, Request who-has 10.138.248.68 tell 10.138.248.68, length 28 | |
| 16:01:38 | ignaziocassano | 18:00:50.344397 IP6 fe80::f816:3eff:fe6b:8bee > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::f816:3eff:fe6b:8bee, length 32 | |
| 16:01:38 | ignaziocassano | 18:00:50.344367 ARP, Request who-has 10.138.248.68 tell 10.138.248.68, length 28 | |
| 16:01:38 | ignaziocassano | 18:00:50.344397 IP6 fe80::f816:3eff:fe6b:8bee > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::f816:3eff:fe6b:8bee, length 32 | |
| 16:01:39 | ignaziocassano | 18:00:50.435854 ARP, Reverse Request who-is fa:16:3e:6b:8b:ee (oui Unknown) tell fa:16:3e:6b:8b:ee (oui Unknown), length 46 | |
| 16:01:39 | ignaziocassano | 18:00:50.494425 ARP, Request who-has 10.138.248.68 tell 10.138.248.68, length 28 | |
| 16:01:39 | ignaziocassano | 18:00:50.435854 ARP, Reverse Request who-is fa:16:3e:6b:8b:ee (oui Unknown) tell fa:16:3e:6b:8b:ee (oui Unknown), length 46 | |
| 16:01:39 | ignaziocassano | 18:00:50.494425 ARP, Request who-has 10.138.248.68 tell 10.138.248.68, length 28 | |
| 16:01:40 | ignaziocassano | 18:00:50.494456 IP6 fe80::f816:3eff:fe6b:8bee > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::f816:3eff:fe6b:8bee, length 32 | |
| 16:01:40 | ignaziocassano | 18:00:50.494456 IP6 fe80::f816:3eff:fe6b:8bee > ff02::1: ICMP6, neighbor advertisement, tgt is fe80::f816:3eff:fe6b:8bee, length 32 | |
| 16:02:13 | ignaziocassano | the above is on destination node | |
| 16:02:13 | ignaziocassano | the above is on destination node | |
| 16:02:59 | sean-k-mooney | so the Reverse Request who-is fa:16:3e:6b:8b:ee (oui Unknown) tell fa:16:3e:6b:8b:ee | |
| 16:02:59 | sean-k-mooney | so the Reverse Request who-is fa:16:3e:6b:8b:ee (oui Unknown) tell fa:16:3e:6b:8b:ee | |
| 16:03:07 | sean-k-mooney | i think was the RARP packet | |
| 16:03:07 | sean-k-mooney | i think was the RARP packet | |
| 16:04:00 | sean-k-mooney | so the question is has the ovs agent finished installing the openflow rules wehn that was sent and did tha tpacket also get sent on the physical network correnctly encapsulated | |
| 16:04:00 | sean-k-mooney | so the question is has the ovs agent finished installing the openflow rules wehn that was sent and did tha tpacket also get sent on the physical network correnctly encapsulated | |
| 16:05:04 | sean-k-mooney | ignaziocassano: can you confirm that fa:16:3e:6b:8b:ee is the vms mac address | |
| 16:05:04 | sean-k-mooney | ignaziocassano: can you confirm that fa:16:3e:6b:8b:ee is the vms mac address | |
| 16:06:00 | ignaziocassano | fa:16:3e:6b:8b:ee ues | |
| 16:06:04 | ignaziocassano | fa:16:3e:6b:8b:ee ues | |
| 16:06:04 | ignaziocassano | fa:16:3e:6b:8b:ee ues | |
| 16:06:09 | sean-k-mooney | ignaziocassano: by the way longer message like logs are best shared using http://paste.openstack.org/ | |
| 16:06:09 | sean-k-mooney | ignaziocassano: by the way longer message like logs are best shared using http://paste.openstack.org/ | |
| 16:06:11 | ignaziocassano | fa:16:3e:6b:8b:ee yes it is | |
| 16:06:11 | ignaziocassano | fa:16:3e:6b:8b:ee yes it is | |
| 16:06:15 | sean-k-mooney | :) | |
| 16:06:45 | sean-k-mooney | cool so we can see that the RARP packets are sent but we need to look at the timestamp and compore that to the neutron agent logs | |
| 16:06:45 | sean-k-mooney | cool so we can see that the RARP packets are sent but we need to look at the timestamp and compore that to the neutron agent logs | |
| 16:07:38 | ignaziocassano | do you want I send on paste.openstack.org the openvswitch agent log related to destination node ? | |
| 16:07:38 | ignaziocassano | do you want I send on paste.openstack.org the openvswitch agent log related to destination node ? | |
| 16:11:14 | ignaziocassano | sean-k-mooney which logs do you need ? | |
| 16:11:14 | ignaziocassano | sean-k-mooney which logs do you need ? | |
| 16:11:30 | ignaziocassano | I have 3 controllers and 2 compute nodes | |
| 16:11:30 | ignaziocassano | I have 3 controllers and 2 compute nodes | |
| 16:14:52 | sean-k-mooney | ignaziocassano: if you have a subset of the log for the time perod whne it booted say a 2-5 minute span around 18:00:49 | |
| 16:14:52 | sean-k-mooney | ignaziocassano: if you have a subset of the log for the time perod whne it booted say a 2-5 minute span around 18:00:49 | |
| 16:15:07 | sean-k-mooney | the we coudl take a look | |
| 16:15:07 | sean-k-mooney | the we coudl take a look | |
| 16:17:02 | ignaziocassano | Paste #52iiZxCu2PRtXAhf318N | |
| 16:17:02 | ignaziocassano | Paste #52iiZxCu2PRtXAhf318N | |
| 16:17:33 | ignaziocassano | is the dhacpagent log | |
| 16:17:33 | ignaziocassano | is the dhacpagent log | |
| 16:18:41 | ignaziocassano | sorry | |
| 16:18:41 | ignaziocassano | sorry | |
| 16:18:46 | ignaziocassano | http://paste.openstack.org/show/52iiZxCu2PRtXAhf318N/ | |
| 16:18:46 | ignaziocassano | http://paste.openstack.org/show/52iiZxCu2PRtXAhf318N/ | |
| 16:19:51 | sean-k-mooney | can you do the same thing for the ovs l2 agent log, actully it might be better to grep by the port uuid or tap name | |
| 16:19:51 | sean-k-mooney | can you do the same thing for the ovs l2 agent log, actully it might be better to grep by the port uuid or tap name | |
| 16:20:30 | sean-k-mooney | e.g. grep -i -E "tap11fdfb84-4a|fa:16:3e:6b:8b:ee|<port uuid>" | |
| 16:20:30 | sean-k-mooney | e.g. grep -i -E "tap11fdfb84-4a|fa:16:3e:6b:8b:ee|<port uuid>" | |
| 16:21:29 | sean-k-mooney | what im looking for specificly is the l2 agent in debug mode logs when ports are added to ovs and when the prot is "treated" | |
| 16:21:29 | sean-k-mooney | what im looking for specificly is the l2 agent in debug mode logs when ports are added to ovs and when the prot is "treated" | |
| 16:21:54 | sean-k-mooney | which means it has configured ovs to handel data form the port | |
| 16:21:54 | sean-k-mooney | which means it has configured ovs to handel data form the port | |
| 16:22:14 | ignaziocassano | http://paste.openstack.org/show/805250/ | |
| 16:22:14 | ignaziocassano | http://paste.openstack.org/show/805250/ | |