1TIPC-NAMETABLE(8) Linux TIPC-NAMETABLE(8)
2
3
4
6 tipc-nametable - show TIPC nametable
7
8
10 tipc nametable show
11
12
14 Options (flags) that can be passed anywhere in the command chain.
15
16 -h, --help
17
18
19 -j, -json
20 Output results in JavaScript Object Notation (JSON).
21
22
23 -p, -pretty
24 The default JSON format is compact and more efficient to parse
25 but hard for most users to read. This flag adds indentation for
26 readability.
27
28 Show help about last valid command. For example tipc nametable
29 --help will show nametable help and tipc --help will show gen‐
30 eral help. The position of the option in the string is irrele‐
31 vant.
32
33
35 The nametable shows TIPC publication information.
36
37
38 Nametable format
39 Type
40 The 32-bit type field of the port name. The type field often
41 indicates the class of service provided by a port.
42
43
44 Lower
45 The lower bound of the 32-bit instance field of the port name.
46 The instance field is often used as as a sub-class indicator.
47
48
49 Upper
50 The upper bound of the 32-bit instance field of the port name.
51 The instance field is often used as as a sub-class indicator. A
52 difference in lower and upper means the socket is bound to the
53 port name range [lower,upper]
54
55
56 Port Identity
57 The unique socket (port) identifier within the TIPC cluster. The
58 port identity consists of a node identity followed by a socket
59 reference number.
60
61
62 Publication
63 The publication ID is a random number used internally to repre‐
64 sent a publication.
65
66
67 Scope
68 The publication scope specifies the visibility of a bound port
69 name. The scope can be specified to comprise three different
70 domains: node, cluster and zone. Applications residing within
71 the specified scope can see and access the port using the dis‐
72 played port name.
73
74
76 Exit status is 0 if command was successful or a positive integer upon
77 failure.
78
79
81 tipc(8), tipc-bearer(8), tipc-link(8), tipc-media(8), tipc-node(8),
82 tipc-peer(8), tipc-socket(8)
83
85 Report any bugs to the Network Developers mailing list <net‐
86 dev@vger.kernel.org> where the development and maintenance is primarily
87 done. You do not have to be subscribed to the list to send a message
88 there.
89
90
92 Richard Alpe <richard.alpe@ericsson.com>
93
94
95
96iproute2 02 Jun 2015 TIPC-NAMETABLE(8)