Sorry, my bad. When I finally used the right binary it worked fine, so forget 
about previous mail.

Tested and acked-by: jon

///jon

PS: net-next is at rc6+ now, so it might close any day.

> -----Original Message-----
> From: Jon Maloy
> Sent: Thursday, 21 July, 2016 13:24
> To: Parthasarathy Bhuvaragan; tipc-discussion@lists.sourceforge.net;
> ma...@donjonn.com; Ying Xue
> Subject: Re: [tipc-discussion] [PATCH iproute2 v5 00/10] tipc: updates for
> neighbour monitor
> 
> root@xenial1:~# tipc l m
> Usage: tipc montior COMMAND [ARGS] ...
> 
> COMMANDS
>  set                    - Set monitor properties
>  get                    - Get monitor properties
>  list                   - List all cluster members
>  summary                - Show local node monitor summary
> root@xenial1:~# tipc l m l
> error, missing bearer media
> root@xenial1:~#
> 
> I thought this was what you had fixed? I must have misunderstood something.
> 
> ///jon
> 
> 
> > -----Original Message-----
> > From: Parthasarathy Bhuvaragan
> > Sent: Tuesday, 19 July, 2016 11:16
> > To: tipc-discussion@lists.sourceforge.net; Jon Maloy; ma...@donjonn.com;
> Ying
> > Xue
> > Subject: [PATCH iproute2 v5 00/10] tipc: updates for neighbour monitor
> >
> > This commit series requires the following kernel patch set:
> > "[PATCH net-next v3 0/5] tipc: netlink updates for neighbour monitor".
> >
> > v5: - Made bearer name optional in monitor list command based on
> >       feedback from Jon.M in patch 9,10.
> >     - fix indentation in patch 5,6.
> >
> > v4: - Declare bname_list as constant in patch#2.
> >     - Declare media_list as global constant in patch#4.
> >     - Updated to address comments from Jon.M in patch 7, 9 & 10.
> >
> > v3: - simplified the header layouts in commit#9.
> >     - updated man pages.
> >
> > v2: - split patches into self-contained complete commits.
> >     - address review comments from richard alpe.
> >     - cleanup of tipc bearer.
> >     - introduce tipc link monitor summary
> >
> > regards
> > Partha
> >
> > Parthasarathy Bhuvaragan (10):
> >   tipc: remove dead code
> >   tipc: introduce cmd_get_unique_bearer_name() function
> >   tipc: validate bearer arguments early
> >   tipc: fix bearer operations with media=ib
> >   tipc: add link monitor set threshold
> >   tipc: add link monitor get threshold
> >   tipc: add link monitor summary
> >   tipc: export some bearer helper functions
> >   tipc: add link monitor list
> >   tipc: update man page for link monitor
> >
> >  include/linux/tipc_netlink.h |  37 ++++
> >  man/man8/tipc-link.8         | 106 ++++++++++++
> >  tipc/bearer.c                | 402 
> > ++++++++++++++++++++++++-------------------
> >  tipc/bearer.h                |   3 +
> >  tipc/link.c                  | 386 
> > ++++++++++++++++++++++++++++++++++++++++-
> >  5 files changed, 749 insertions(+), 185 deletions(-)
> >
> > --
> > 2.1.4
> 
> 
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports.http://sdm.link/zohodev2dev
> _______________________________________________
> tipc-discussion mailing list
> tipc-discussion@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tipc-discussion

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion

Reply via email to