From: Stephen Hemminger <stephen@networkplumber.org>
To: anuradhak@cumulusnetworks.com
Cc: davem@davemloft.net, sfeldma@gmail.com, netdev@vger.kernel.org,
roopa@cumulusnetworks.com, gospo@cumulusnetworks.com,
wkok@cumulusnetworks.com
Subject: Re: [PATCH iproute2 v7 4/4] ip link: proto_down config and display.
Date: Tue, 28 Jul 2015 16:44:53 -0700 [thread overview]
Message-ID: <20150728164453.07cf0422@urahara> (raw)
In-Reply-To: <1436906602-2958-5-git-send-email-anuradhak@cumulusnetworks.com>
On Tue, 14 Jul 2015 13:43:22 -0700
anuradhak@cumulusnetworks.com wrote:
> From: Anuradha Karuppiah <anuradhak@cumulusnetworks.com>
>
> This patch adds support to set and display protodown on a switch port. The
> switch driver can handle this error state by doing a phys down on the port.
>
> One example user space application setting this flag is a multi-chassis
> LAG application to handle split-brain situation on peer-link failure.
>
> Example:
> root@net-next:~# ip link set eth1 protodown on
> root@net-next:~/iproute2# ip link show eth1
> 4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
> link/ether 52:54:00:12:35:01 brd ff:ff:ff:ff:ff:ff protodown on
> root@net-next:~/iproute2# ip link set eth1 protodown off
> root@net-next:~/iproute2# ip link show eth1
> 4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
> link/ether 52:54:00:12:35:01 brd ff:ff:ff:ff:ff:ff
> root@net-next:~/iproute2#
>
> Signed-off-by: Anuradha Karuppiah <anuradhak@cumulusnetworks.com>
> Signed-off-by: Andy Gospodarek <gospo@cumulusnetworks.com>
> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
> Signed-off-by: Wilson Kok <wkok@cumulusnetworks.com>
Applied to net-next branch.
prev parent reply other threads:[~2015-07-28 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 20:43 [PATCH iproute2 v7 4/4] ip link: proto_down config and display anuradhak
2015-07-28 23:44 ` Stephen Hemminger [this message]
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=20150728164453.07cf0422@urahara \
--to=stephen@networkplumber.org \
--cc=anuradhak@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=gospo@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@gmail.com \
--cc=wkok@cumulusnetworks.com \
/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