From: Greg O'Rawe <greg.orawe@enea.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Bonded failover does not work with Cisco ENIC driver
Date: Mon, 21 Oct 2019 12:45:44 +0000 [thread overview]
Message-ID: <AM6PR03MB4840E6C0E5F5F63B8C1FC545ED690@AM6PR03MB4840.eurprd03.prod.outlook.com> (raw)
Hi,
I've a Cisco UCS server using the enic driver, and have configured two slave interfaces into a bond (Active-standby mode) with two VLAN sub-interfaces which are managed via DPDK (through VPP).
The system is Red Hat 7.6 running DPDK 17.11.4.
However, failover does not work - when the primary slave interface is taken down the standby does not take over and connectivity is lost. It is eventually restored when the primary interface is brought up again.
Should failover work with this driver, either on this DPDK version or a later one? Is there anything else required to get this to function be default? I didn't see any later changes in the DPDK enic driver code which seemed relevant to this area.
Thanks
Greg O'Rawe
This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks.
reply other threads:[~2019-10-23 21:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM6PR03MB4840E6C0E5F5F63B8C1FC545ED690@AM6PR03MB4840.eurprd03.prod.outlook.com \
--to=greg.orawe@enea.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).