Hi, I install ovs and ovn for version of 2.11.4. and use geneve protocol for overlay communication. and found some log info in ovs-vswitch.log, like bellow:
2019-10-18T02:39:39.162Z|00001|vlog|INFO|opened log file /var/log/openvswitch/ovs-vswitchd.log 2019-10-18T02:39:39.166Z|00002|ovs_numa|INFO|Discovered 16 CPU cores on NUMA node 0 2019-10-18T02:39:39.166Z|00003|ovs_numa|INFO|Discovered 16 CPU cores on NUMA node 1 2019-10-18T02:39:39.166Z|00004|ovs_numa|INFO|Discovered 2 NUMA nodes and 32 CPU cores 2019-10-18T02:39:39.166Z|00005|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting... 2019-10-18T02:39:39.166Z|00006|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected 2019-10-18T02:39:39.254Z|00007|dpif_netlink|INFO|The kernel module does not support meters. 2019-10-18T02:39:39.282Z|00008|ofproto_dpif|INFO|system@ovs-system: Datapath supports recirculation 2019-10-18T02:39:39.282Z|00009|ofproto_dpif|INFO|system@ovs-system: VLAN header stack length probed as 2 2019-10-18T02:39:39.282Z|00010|ofproto_dpif|INFO|system@ovs-system: MPLS label stack length probed as 1 2019-10-18T02:39:39.282Z|00011|ofproto_dpif|INFO|system@ovs-system: Datapath supports truncate action 2019-10-18T02:39:39.282Z|00012|ofproto_dpif|INFO|system@ovs-system: Datapath supports unique flow ids 2019-10-18T02:39:39.282Z|00013|ofproto_dpif|INFO|system@ovs-system: Datapath does not support clone action 2019-10-18T02:39:39.283Z|00014|ofproto_dpif|INFO|system@ovs-system: Max sample nesting level probed as 3 2019-10-18T02:39:39.283Z|00015|ofproto_dpif|INFO|system@ovs-system: Datapath does not support eventmask in conntrack action 2019-10-18T02:39:39.283Z|00016|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_clear action 2019-10-18T02:39:39.283Z|00017|ofproto_dpif|INFO|system@ovs-system: Max dp_hash algorithm probed to be 0 2019-10-18T02:39:39.283Z|00018|ofproto_dpif|INFO|system@ovs-system: Datapath supports ct_state 2019-10-18T02:39:39.283Z|00019|ofproto_dpif|INFO|system@ovs-system: Datapath supports ct_zone 2019-10-18T02:39:39.283Z|00020|ofproto_dpif|INFO|system@ovs-system: Datapath supports ct_mark 2019-10-18T02:39:39.283Z|00021|ofproto_dpif|INFO|system@ovs-system: Datapath supports ct_label 2019-10-18T02:39:39.283Z|00022|ofproto_dpif|INFO|system@ovs-system: Datapath supports ct_state_nat 2019-10-18T02:39:39.283Z|00023|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_orig_tuple 2019-10-18T02:39:39.283Z|00024|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_orig_tuple6 2019-10-18T02:39:39.283Z|00025|dpif_netlink|INFO|dpif_netlink_meter_transact OVS_METER_CMD_SET failed 2019-10-18T02:39:39.283Z|00026|dpif_netlink|INFO|dpif_netlink_meter_transact OVS_METER_CMD_SET failed 2019-10-18T02:39:39.283Z|00027|dpif_netlink|INFO|dpif_netlink_meter_transact get failed 2019-10-18T02:39:39.283Z|00028|dpif_netlink|INFO|The kernel module has a broken meter implementation. with the log info it tell me my kernel doesn't support several modules, what can i do to let the kernel support them. also i found some warn message like below: 2019-10-18T02:39:52.861Z|00002|dpif(handler5)|WARN|Dropped 4 log messages in last 8 seconds (most recently, 8 seconds ago) due to excessive rate 2019-10-18T02:39:52.861Z|00003|dpif(handler2)|WARN|system@ovs-system: execute ct(commit,zone=8,label=0/0x1),set(eth(src=00:00:00:2f:11:2c,dst=0a:00:00:14:00:0a)), set(ipv4(src=172.20.0.6,dst=172.20.0.9,ttl=63)),ct(zone=10),recirc(0x1b) failed (Invalid argument) on packet udp,vlan_tci=0x0000,dl_src=0a:00:00:14:00:07,dl_dst=0 0:00:00:2f:11:2c,nw_src=172.20.0.6,nw_dst=172.20.0.9,nw_tos=0,nw_ecn=0,nw_ttl=64,tp_src=53929,tp_dst=53 udp_csum:ebcf with metadata skb_priority(0),skb_mark(0),ct_state(0x21),ct_zone(0x8),in_port(4) mtu 0 2019-10-18T02:39:52.861Z|00003|dpif(handler5)|WARN|system@ovs-system: execute ct(commit,zone=8,label=0/0x1),set(eth(src=00:00:00:2f:11:2c,dst=0a:00:00:14:00:0a)), set(ipv4(src=172.20.0.6,dst=172.20.0.9,ttl=63)),ct(zone=10),recirc(0x1a) failed (Invalid argument) on packet udp,vlan_tci=0x0000,dl_src=0a:00:00:14:00:07,dl_dst=0 0:00:00:2f:11:2c,nw_src=172.20.0.6,nw_dst=172.20.0.9,nw_tos=0,nw_ecn=0,nw_ttl=64,tp_src=57585,tp_dst=53 udp_csum:9f77 with metadata skb_priority(0),skb_mark(0),ct_state(0x21),ct_zone(0x8),in_port(4) mtu 0 anyone can give me some suggestions how to resole this unnormal log messages. thank you very much.
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
