1isns(1M) System Administration Commands isns(1M)
2
3
4
6 isns - Internet Storage Name Service
7
9 /usr/sbin/isns
10
11
13 The Internet Storage Name Service (iSNS) provides consolidated discov‐
14 ery services for Internet SCSI (iSCSI) and Internet Fibre Channel Pro‐
15 tocol (iFCP) devices in an IP network. iSNS uses a client/server mech‐
16 anism: servers store configuration information for clients, and pro‐
17 vide that information upon a client's request. IETF RFC 4171 describes
18 the protocols between the server and client.
19
20
21 This man page provides a summary of the Solaris iSNS server implementa‐
22 tion. The current implementation does not support iFCP devices.
23
24
25 Solaris iSNS server is implemented as the daemon isns, which binds to
26 the well -known port 3205 to service client requests. The daemon is
27 started by the service management facility (smf(5)), using the fault
28 management resource identifier (FMRI):
29
30 svc:/network/isns_server
31
32
33
34
35 Use svcadm(1M) to enable isns. Enabling the service means that it
36 starts and runs automatically whenever the operating system is booted.
37 The state of service can be displayed with the svcs(1) command.
38
39
40 The service properties listed below can be managed using svccfg(1M).
41 The default value is assigned per RFC 4171 and implementation choice.
42
43 data_store_location
44
45 Configuration data store location. The default location is
46 /etc/isns/isnsdata.xml.
47
48
49 ESI_retry_threshold_count
50
51 Entity Status Inquiry retry threshold counter. The default count is
52 3.
53
54
55 Management_SCNs_Enabled
56
57 Boolean that determines whether Management State Change Notifica‐
58 tion is enabled. The default is yes.
59
60
61 Authorized_Control_Nodes
62
63 Control node names.
64
65
66
67 After changing a property value, you must use svcadm(1M) refresh to
68 enable isns to recognize the new value. If you change the
69 data_store_location property, you must enter a svcadm restart command
70 for the change to take effect.
71
72
73 RFC 4171 defines the default discovery domain, the default domain set,
74 and the "Default DD/DDS" setting with the intent of managing clients
75 that have not been assigned to any user-defined discovery domain. The
76 server adopts the following behaviors with respect to the default dis‐
77 covery domain and domain set:
78
79 o An unassigned client is added to the default discovery
80 domain. A newly registered client or a client that was
81 removed from its last discovery domain membership is consid‐
82 ered to be an unassigned client.
83
84 o When a client gets assigned to a user-defined discovery
85 domain, the server will remove the client from the default
86 discovery domain.
87
88 o The default discovery domain set is allowed to be adminis‐
89 tratively activated or deactivated in order to let the
90 administrator control discovery among clients in the default
91 discovery domain.
92
93 o It is not allowed to administratively add a client to the
94 default discovery domain, nor to administratively add a
95 user-defined discovery domain to the default discovery
96 domain set.
97
98 o The default state of the Default discovery domain set is
99 inactive.
100
101
102 The isns server supports certain rbac(5) authorizations that allow you
103 to administer isns activity. These authorizations include the following
104 auth_attr(4) privileges:
105
106 solaris.isnsmgr.write
107
108 Required to create a discovery domain or domain set, to enable/dis‐
109 able a discovery domain set and to change grouping of iSNS clients
110 in a discovery domain or grouping of discovery domains in a discov‐
111 ery domain set.
112
113
114 solaris.smf.manage.isns
115
116 Required to manage the isns server through the smf(5).
117
118
119 solaris.smf.value.isns
120
121 Required to change the SMF service properties associated with isns.
122
123
124
125 The iSNS Server Management profile (see prof_attr(4)) includes all of
126 the preceding authorizations. See rbac(5) for an overview of roles and
127 authorizations.
128
130 There are no options supported by the isns daemon.
131
133 Example 1 Starting an isns Server
134
135
136 The following command starts the isns server.
137
138
139 # svcadm enable svc:/network/isns_server
140
141
142
143 Example 2 Stopping an isns Server
144
145
146 The following command stops the isns server.
147
148
149 # svcadm disable svc:/network/isns_server
150
151
152
153 Example 3 Changing an isns Property
154
155
156 The following sequence of commands changes the value of the
157 ESI_retry_threshold_count property.
158
159
160 # svccfg -s svc:/network/isns_server setprop \
161 config/ESI_retry_threshold_count = 6
162 # svcadm refresh svc:/network/isns_server
163
164
165
167 /usr/sbin/isns
168
169 iSNS daemon binary.
170
171
173 See attributes(5) for descriptions of the following attributes:
174
175
176
177
178 ┌─────────────────────────────┬─────────────────────────────┐
179 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
180 ├─────────────────────────────┼─────────────────────────────┤
181 │Availability │SUNWisnsr │
182 ├─────────────────────────────┼─────────────────────────────┤
183 │Interface Stability │Standard │
184 └─────────────────────────────┴─────────────────────────────┘
185
187 svcs(1), isnsadm(1M), svcadm(1M), svccfg(1M), auth_attr(4),
188 prof_attr(4), attributes(5), rbac(5), smf(5)
189
191 It is strongly recommended that you restart the server (svcadm restart)
192 after a service property is changed. This allows the server to apply a
193 uniform setting for existing and new clients.
194
195
196 A control node, as described in RFC 4171, is not required to administer
197 the server. Control node operations can be achieved through the
198 isnsadm(1M) command interface on the local host. For example, isnsadm
199 enables you to create a discovery domain and a discovery domain set and
200 to add a member to it, in order to create discovery domain and discov‐
201 ery domain set associations.
202
203
204
205SunOS 5.11 8 Nov 2007 isns(1M)