Signed-off-by: Parthasarathy Bhuvaragan <parthasarathy.bhuvara...@ericsson.com>
---
man/man8/tipc-link.8 | 101 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 101 insertions(+)
diff --git a/man/man8/tipc-link.8 b/man/man8/tipc-link.8
index 3be8c9ad4b16..f023b095a01a 100644
--- a/man/man8/tipc-link.8
+++ b/man/man8/tipc-link.8
@@ -39,6 +39,32 @@ tipc-link \- show links or modify link properties
.B tipc link list
.br
+.ti -8
+.B tipc link monitor set
+.RB "{ " "threshold" " } "
+
+.ti -8
+.B tipc link monitor get
+.RB "{ " "threshold" " } "
+
+.ti -8
+.B tipc link monitor summary
+.br
+
+.ti -8
+.B tipc link monitor list media
+.br
+.RB "{ { " eth " | " ib " } " device
+.IR "DEVICE" " }"
+.RB "|"
+.br
+.RB "{ " udp
+.B name
+.IR NAME
+.B localip
+.IR LOCALIP " } }"
+.br
+
.SH OPTIONS
Options (flags) that can be passed anywhere in the command chain.
.TP
@@ -204,6 +230,81 @@ The link window controls how many unacknowledged messages
a link endpoint can
have in its transmit queue before TIPC's congestion control mechanism is
activated.
+.SS Monitor properties
+
+.TP
+.B threshold
+.br
+The threshold specifies the cluster size exceeding which the link monitoring
+algorithm will switch from "full mesh" to "overlapping ring". The default value
+is 32. Threshold value of 0, implies that ring monitoring is always on.
+
+.SS Monitor information
+
+.TP
+.B table
+.br
+Represents the event count in a node's local monitoring list. It steps every
+time something changes in the local monitor list, including changes in the
+local domain.
+
+.TP
+.B members
+.br
+Represents the total count of nodes which are cluster members.
+
+.TP
+.B state
+.br
+The current state of "overlapping ring" supervision algorithm for the bearer.
+The value active implies that the overlapping ring supervision algorithm is
+currently being used by the bearer.
+
+.TP
+.B S - Current Node Status
+.br
+The Node status derived by the local node. Possible values are:
+U-Up, D-Down.
+
+.TP
+.B D - Directly monitored
+.br
+Is the Node actively monitored from the local node. Possible values are:
+Y-Yes, N-No.
+
+.TP
+.B Dom - Domain Generation
+.br
+Represents the event count in a node's local domain. It steps every time
+something changes (peer add/remove/up/down). This helps the receiver of
+a domain record to know if it should ignore or process the record.
+
+.TP
+.B Applied Node Status
+.br
+The Node status reported by the peer node for the preceeding peers in
+the Node list. The Node list is a circular list of ascending addresses
+begining with the local node. Possible values are: U-Up, D-Down.
+
+.TP
+.B [Non-Applied Node:Status]
+.br
+Represents the Nodes which cannot be applied to the monitoring list
+for this peer node. These are usually transient node states during
+the cluster startup phase or network partition.
+
+.SH EXAMPLES
+.PP
+tipc link monitor list media eth dev data0
+.RS 4
+Shows the link monitoring information for cluster members on device data0.
+.RE
+.PP
+tipc link monitor summary
+.RS 4
+The monitor summary command prints the basic attributes.
+.RE
+
.SH EXIT STATUS
Exit status is 0 if command was successful or a positive integer upon failure.
--
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. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion
