From: Tom Ammon <tom.ammon-wbocuHtxKic@public.gmane.org>
To: "Woodruff,
Robert J"
<robert.j.woodruff-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Pradeep Satyanarayana
<pradeeps-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
EWG <Openfabrics-ewg-0P3JtQMG0aQdnm+yROfE0A@public.gmane.org>
Subject: Re: [ewg] How to monitor traffic with IBoE/RoCEE?
Date: Fri, 26 Mar 2010 11:43:02 -0600 [thread overview]
Message-ID: <4BACF226.6030201@utah.edu> (raw)
In-Reply-To: <382A478CAD40FA4FB46605CF81FE39F455FF9847-osO9UTpF0URzLByeVOV5+bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
A widely-supported method for collecting statistics from ethernet
switching devices is SNMP. As Woody said, you wouldn't manage your
ethernet network any differently than you do now. In addition many many
tools have been written to make use of SNMP counters, so you won't have
a hard time finding tools, both commercial and open source.
Tom
On 03/26/2010 11:29 AM, Woodruff, Robert J wrote:
> Pradeep wrote,
>
>
>> With IBoE/RoCEE, the traditional SM in IB clusters is not needed. Most of the current
>> IB tools rely on the SM and PM to get packet and error statistics and so on. These
>> won't be applicable with IBoE/RoCEE. netstat will have no value since the kernel
>> has been bypassed. So, how does one monitor traffic in such a cluster?
>>
> Some managed Ethernet switches have the ability to log into them and get information
> on packets transmited/received on each port and errors that are detected. However,
> these are typically proprietary. I am not sure about the Mellanox card.
>
> So I guess the answer is that you manage RoCCE and iWarp clusters just like
> you would any Ethernet cluster, with existing management tools that are available
> for managing Ethernet.
>
> woody
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
--------------------------------------------------------------------
Tom Ammon
Network Engineer
Office: 801.587.0976
Mobile: 801.674.9273
Center for High Performance Computing
University of Utah
http://www.chpc.utah.edu
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-26 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 0:18 How to monitor traffic with IBoE/RoCEE? Pradeep Satyanarayana
[not found] ` <4BABFD62.70608-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2010-03-26 17:29 ` [ewg] " Woodruff, Robert J
[not found] ` <382A478CAD40FA4FB46605CF81FE39F455FF9847-osO9UTpF0URzLByeVOV5+bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-03-26 17:43 ` Tom Ammon [this message]
[not found] ` <4BACF226.6030201-wbocuHtxKic@public.gmane.org>
2010-03-26 20:47 ` Pradeep Satyanarayana
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=4BACF226.6030201@utah.edu \
--to=tom.ammon-wbocuhtxkic@public.gmane.org \
--cc=Openfabrics-ewg-0P3JtQMG0aQdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pradeeps-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=robert.j.woodruff-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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