| 1 |
.TH TIPC-NAMETABLE 8 "02 Jun 2015" "iproute2" "Linux" |
| 2 |
|
| 3 |
.\" For consistency, please keep padding right aligned. |
| 4 |
.\" For example '.B "foo " bar' and not '.B foo " bar"' |
| 5 |
|
| 6 |
.SH NAME |
| 7 |
tipc-nametable \- show TIPC nametable |
| 8 |
|
| 9 |
.SH SYNOPSIS |
| 10 |
.ad l |
| 11 |
.in +8 |
| 12 |
|
| 13 |
.ti -8 |
| 14 |
.B tipc nametable show |
| 15 |
.br |
| 16 |
|
| 17 |
.SH OPTIONS |
| 18 |
Options (flags) that can be passed anywhere in the command chain. |
| 19 |
.TP |
| 20 |
.BR "\-h" , " --help" |
| 21 |
Show help about last valid command. For example |
| 22 |
.B tipc nametable --help |
| 23 |
will show nametable help and |
| 24 |
.B tipc --help |
| 25 |
will show general help. The position of the option in the string is irrelevant. |
| 26 |
|
| 27 |
.TP |
| 28 |
.BR "\-j", " \-json" |
| 29 |
Output results in JavaScript Object Notation (JSON). |
| 30 |
|
| 31 |
.TP |
| 32 |
.BR "\-p", " \-pretty" |
| 33 |
The default JSON format is compact and more efficient to parse but hard for most users to read. |
| 34 |
This flag adds indentation for readability. |
| 35 |
|
| 36 |
.SH DESCRIPTION |
| 37 |
The nametable shows TIPC publication information. |
| 38 |
|
| 39 |
.SS Nametable format |
| 40 |
|
| 41 |
.TP |
| 42 |
.B Type |
| 43 |
.br |
| 44 |
The 32-bit type field of the port name. The type field often indicates the class of service |
| 45 |
provided by a port. |
| 46 |
|
| 47 |
.TP |
| 48 |
.B Lower |
| 49 |
.br |
| 50 |
The lower bound of the 32-bit instance field of the port name. |
| 51 |
The instance field is often used as a sub-class indicator. |
| 52 |
|
| 53 |
.TP |
| 54 |
.B Upper |
| 55 |
.br |
| 56 |
The upper bound of the 32-bit instance field of the port name. |
| 57 |
The instance field is often used as a sub-class indicator. |
| 58 |
A difference in |
| 59 |
.BR "lower " "and " upper |
| 60 |
means the socket is bound to the port name range [lower,upper] |
| 61 |
|
| 62 |
.TP |
| 63 |
.B Port Identity |
| 64 |
.br |
| 65 |
The unique socket (port) identifier within the TIPC cluster. The |
| 66 |
.B port identity |
| 67 |
consists of a node identity followed by a socket reference number. |
| 68 |
|
| 69 |
.TP |
| 70 |
.B Publication |
| 71 |
.br |
| 72 |
The |
| 73 |
.B publication |
| 74 |
ID is a random number used internally to represent a publication. |
| 75 |
|
| 76 |
.TP |
| 77 |
.B Scope |
| 78 |
.br |
| 79 |
The publication |
| 80 |
.B scope |
| 81 |
specifies the visibility of a bound port name. |
| 82 |
The |
| 83 |
.B scope |
| 84 |
can be specified to comprise three different domains: |
| 85 |
.BR node ", " "cluster " "and " zone. |
| 86 |
Applications residing within the specified |
| 87 |
.B scope |
| 88 |
can see and access the port using the displayed port name. |
| 89 |
|
| 90 |
.SH EXIT STATUS |
| 91 |
Exit status is 0 if command was successful or a positive integer upon failure. |
| 92 |
|
| 93 |
.SH SEE ALSO |
| 94 |
.BR tipc (8), |
| 95 |
.BR tipc-bearer (8), |
| 96 |
.BR tipc-link (8), |
| 97 |
.BR tipc-media (8), |
| 98 |
.BR tipc-node (8), |
| 99 |
.BR tipc-peer (8), |
| 100 |
.BR tipc-socket (8) |
| 101 |
.br |
| 102 |
.SH REPORTING BUGS |
| 103 |
Report any bugs to the Network Developers mailing list |
| 104 |
.B <[email protected]> |
| 105 |
where the development and maintenance is primarily done. |
| 106 |
You do not have to be subscribed to the list to send a message there. |
| 107 |
|
| 108 |
.SH AUTHOR |
| 109 |
Richard Alpe <[email protected]> |