It might be difficult to trace whether LACP PDU tx (as in
response) was successful when the pdu was not transmitted by
egress slave for various reasons (including resource contention
within NIC) and only way to trace its fate is by looking at
ofproto->stats.tx_[packets/bytes] and slave port stats.
Adding a warning when there is tx failure could help user
debug at the root of this problem.
Signed-off-by: Gowrishankar Muthukrishnan <gmuth...@redhat.com>
---
ofproto/ofproto-dpif.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/ofproto/ofproto-dpif.c b/ofproto/ofproto-dpif.c
index 496a16c8a..4af771585 100644
--- a/ofproto/ofproto-dpif.c
+++ b/ofproto/ofproto-dpif.c
@@ -3405,7 +3405,11 @@ send_pdu_cb(void *port_, const void *pdu, size_t
pdu_size)
pdu_size);
memcpy(packet_pdu, pdu, pdu_size);
- ofproto_dpif_send_packet(port, false, &packet);
+ error = ofproto_dpif_send_packet(port, false, &packet);
+ if (error) {
+ VLOG_WARN_RL(&rl, "port %s: cannot transmit LACP PDU (%s).",
+ port->bundle->name, ovs_strerror(error));
+ }
dp_packet_uninit(&packet);
} else {
static struct vlog_rate_limit rll = VLOG_RATE_LIMIT_INIT(1, 10);
--
2.17.2
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
