[ewg] Can't snoop all kinds of mad packets
Yunzhao li
yzli.ksu at gmail.com
Tue Apr 8 09:54:15 PDT 2014
Sorry for not mentioning the VxWorks environment. I'll retest the snooping
routine after fixing the failure.
Thanks for the help!
On Tue, Apr 8, 2014 at 11:47 AM, Hal Rosenstock <hal at dev.mellanox.co.il>wrote:
> On 4/8/2014 12:41 PM, Yunzhao li wrote:
> > The Connect-IB node is configured by the switch SM, and it can
> > send/receive traffic with other connected Connect-IB nodes. We pulled
> > OFED-2.1 into our VxWorks environment,
>
> You hadn't mentioned you were talking about vxWorks rather than Linux.
>
> > so it's a little difficult to run
> > linux commands for verification. For the Connect-IB port: the port state
> > is "defer" and link state is "active".
>
> LinkActDefer means that the physical layer has indicated a failure in
> the link.
>
> >
> > On Tue, Apr 8, 2014 at 11:25 AM, Hal Rosenstock <hal at dev.mellanox.co.il
> > <mailto:hal at dev.mellanox.co.il>> wrote:
> >
> > On 4/8/2014 12:13 PM, Yunzhao li wrote:
> > > We are working on the newest IB card: Mellanox Connect-IB. We
> pulled
> > > Mellanox OFED-2.1 into our environment. The IB nodes are connected
> > > through Mellanox SX3036 switch. We exactly followed Sean Hefty's
> > madeye
> > > code: using ib_register_mad_snoop() for registration and using
> > > ib_mad_snoop_handler() and ib_mad_recv_handler() to handle the
> > sent and
> > > received MAD packets respectively. However, the most captured SM
> > packets
> > > are DevMgt (0x06), and we haven't received any class 0x81 or class
> > 0x01
> > > MADs.
> > >
> > > Does the snooping mad routine need the support of HCA
> > hardware/firmware?
> > > Or, does it need the support of ibdump package?
> >
> > I don't have access to Connect-IB so don't know for sure but my
> > understanding is that a Connect-IB port can be configured by an
> external
> > SM and that an SM can be run on the Connect-IB port so you should be
> > able to capture send and receive SM class packets.
> >
> > Also, PMA should be supported and you can double check this with
> > perfquery.
> >
> > All of the above involves kernel interaction (for even SMA/PMA) so
> > snooping should work AFAIK.
> >
> > What does ibstat say for your Connect-IB port ?
> >
> > -- Hal
> >
> > >
> > > Thanks!
> > >
> > >
> > > On Mon, Apr 7, 2014 at 7:50 PM, Hal Rosenstock
> > <hal at dev.mellanox.co.il <mailto:hal at dev.mellanox.co.il>
> > > <mailto:hal at dev.mellanox.co.il <mailto:hal at dev.mellanox.co.il>>>
> > wrote:
> > >
> > >
> > > > We try to use IB MAD snoop to capture IB mad packets.
> > >
> > > Note that there is old kernel util module madeye written by
> > Sean which
> > > does this:
> > >
> > >
> >
> http://git.openfabrics.org/?p=ofed_1_5/linux-2.6.git;a=blob;f=drivers/infiniband/util/madeye.c;h=2c650a33a69c56d2b8a3274f63185214904abf3a;hb=967460824529719677d6a1d4600ec3e89a4538ab
> > >
> > > which shows how to properly use the ib_register_mad_snoop API
> > for both
> > > SM and GS class MAD snooping.
> > >
> > > > However, currently
> > > > only the classes of DevMgt (0x06) and ComMgt (0x07) could be
> > > snooped. We
> > > > tried to run tests based on class Perf (0x04) and class Subn
> > > (0x01) mad,
> > > > and neither of them can be captured. Any suggestion?
> > >
> > > In the distant past, I've used madeye and captured SM, SA, and
> > PerfMgt
> > > packets.
> > >
> > > Assuming your snoop registration(s) is/are correct:
> > > Most SM packets are class 0x81 (directed route) and not class
> > 0x01 (LID
> > > routed) but this is SM dependent. Also, it might be that there
> > is no
> > > PerfMgt running to/from your node.
> > >
> > > -- Hal
> > >
> > > >
> > > >
> > > > Thanks in advance!
> > > >
> > > >
> > > >
> > > > Yunzhao
> > >
> > >
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ewg/attachments/20140408/b4680dad/attachment.html>
More information about the ewg
mailing list