projects / mirror_iproute2.git / blame
| Commit | Line | Data |
|---|---|---|
| dcd8d142 RA |
1 | .TH TIPC-NAMETABLE 8 "02 Jun 2015" "iproute2" "Linux" |
| 2 | ||
| 85e3c87c VS |
3 | .\" For consistency, please keep padding right aligned. |
| 4 | .\" For example '.B "foo " bar' and not '.B foo " bar"' | |
| dcd8d142 RA |
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 | .SH DESCRIPTION | |
| 28 | The nametable shows TIPC publication information. | |
| 29 | ||
| 30 | .SS Nametable format | |
| 31 | ||
| 32 | .TP | |
| 33 | .B Type | |
| 34 | .br | |
| 35 | The 32-bit type field of the port name. The type field often indicates the class of service | |
| 36 | provided by a port. | |
| 37 | ||
| 38 | .TP | |
| 39 | .B Lower | |
| 40 | .br | |
| 41 | The lower bound of the 32-bit instance field of the port name. | |
| 42 | The instance field is often used as as a sub-class indicator. | |
| 43 | ||
| 44 | .TP | |
| 45 | .B Upper | |
| 46 | .br | |
| 47 | The upper bound of the 32-bit instance field of the port name. | |
| 48 | The instance field is often used as as a sub-class indicator. | |
| 49 | A difference in | |
| 50 | .BR "lower " "and " upper | |
| 51 | means the socket is bound to the port name range [lower,upper] | |
| 52 | ||
| 53 | .TP | |
| 54 | .B Port Identity | |
| 55 | .br | |
| 56 | The unique socket (port) identifier within the TIPC cluster. The | |
| 57 | .B port identity | |
| 58 | consists of a node identity followed by a socket reference number. | |
| 59 | ||
| 60 | .TP | |
| 61 | .B Publication | |
| 62 | .br | |
| 63 | The | |
| 64 | .B publication | |
| 65 | ID is a random number used internally to represent a publication. | |
| 66 | ||
| 67 | .TP | |
| 68 | .B Scope | |
| 69 | .br | |
| 70 | The publication | |
| 71 | .B scope | |
| 72 | specifies the visibility of a bound port name. | |
| 73 | The | |
| 74 | .B scope | |
| 75 | can be specified to comprise three different domains: | |
| 76 | .BR node ", " "cluster " "and " zone. | |
| 77 | Applications residing within the specified | |
| 78 | .B scope | |
| 79 | can see and access the port using the displayed port name. | |
| 80 | ||
| 81 | .SH EXIT STATUS | |
| 82 | Exit status is 0 if command was successful or a positive integer upon failure. | |
| 83 | ||
| 84 | .SH SEE ALSO | |
| 85 | .BR tipc (8), | |
| 86 | .BR tipc-bearer (8), | |
| 87 | .BR tipc-link (8), | |
| 88 | .BR tipc-media (8), | |
| 89 | .BR tipc-node (8), | |
| 90 | .BR tipc-socket (8) | |
| 91 | .br | |
| 92 | .SH REPORTING BUGS | |
| 93 | Report any bugs to the Network Developers mailing list | |
| 94 | .B <netdev@vger.kernel.org> | |
| 95 | where the development and maintenance is primarily done. | |
| 96 | You do not have to be subscribed to the list to send a message there. | |
| 97 | ||
| 98 | .SH AUTHOR | |
| 99 | Richard Alpe <richard.alpe@ericsson.com> |