| blob | b9744b74e2d3264db4da218316a5e1638fb689a9 |
1 '\" te
2 .\" Copyright (c) 2004, Sun Microsystems, Inc. All Rights Reserved.
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH CFGADM_IB 1M "Jul 2, 2008"
7 .SH NAME
8 cfgadm_ib \- InfiniBand hardware specific commands for cfgadm
9 .SH SYNOPSIS
10 .LP
11 .nf
12 \fB/usr/sbin/cfgadm\fR \fB-f\fR [\fB-y\fR | \fB-n\fR] [\fB-v\fR] \fB-c\fR \fIfunction\fR \fIap_id\fR...
13 .fi
15 .LP
16 .nf
17 \fB/usr/sbin/cfgadm\fR [\fB-f\fR] [\fB-y\fR | \fB-n\fR] [\fB-v\fR] [\fB-o\fR \fIhardware_options\fR]
18 \fB-x\fR \fIhardware_function\fR \fIap_id\fR...
19 .fi
21 .LP
22 .nf
23 \fB/usr/sbin/cfgadm\fR \fB-v\fR [\fB-a\fR] [\fB-s\fR \fIlisting_option\fR] [-] [\fIap_id\fR | \fIap_type...\fR]
24 .fi
26 .LP
27 .nf
28 \fB/usr/sbin/cfgadm\fR \fB-v\fR \fB-h\fR [\fIap_id\fR]...
29 .fi
31 .SH DESCRIPTION
32 .sp
33 .LP
34 The InfiniBand hardware specific library \fB/usr/lib/cfgadm/ib.so.1\fR provides
35 the functionality for administering its fabric through the \fBcfgadm\fR(1M)
36 utility. \fBcfgadm\fR operates on attachment points. See \fBcfgadm\fR(1M).
37 .sp
38 .LP
39 An InfiniBand (\fBIB\fR) device is enumerated by the IB nexus driver,
40 \fBib\fR(7D), based on the services from the IB Device Manager (IBDM).
41 .sp
42 .LP
43 The IB nexus driver creates and initializes five types of child device nodes:
44 .RS +4
45 .TP
46 .ie t \(bu
47 .el o
48 IB Port devices
49 .RE
50 .RS +4
51 .TP
52 .ie t \(bu
53 .el o
54 IB HCA service (HCA_SVC) devices
55 .RE
56 .RS +4
57 .TP
58 .ie t \(bu
59 .el o
60 IB Virtual Physical Point of Attachment (VPPA) devices
61 .RE
62 .RS +4
63 .TP
64 .ie t \(bu
65 .el o
66 I/O Controller (IOC)
67 .RE
68 .RS +4
69 .TP
70 .ie t \(bu
71 .el o
72 IB Pseudo devices
73 .RE
74 .sp
75 .LP
76 See \fBib\fR(7D) for details on enumeration of IB Port, IB VPPA, and IB HCA_SVC
77 devices. For additional information on IBDM, see \fBibdm\fR(7D). See
78 \fBib\fR(4) for details on IB Pseudo devices.
79 .sp
80 .LP
81 For IB administration, two types of static attachment point are created for the
82 fabric administration as seen by the given host. There is one static attachment
83 point \fBib\fR and all IB devices (either an IOC, Port, VPPA, HCA_SVC, or a
84 Pseudo device) in the fabric are represented as dynamic attachment points based
85 off of it. There is another static attachment point for each Host Channel
86 Adapter (HCA) in the host based on its node Globally Unique Identifier (GUID)
87 value.
88 .sp
89 .LP
90 Attachment points are named through ap_ids. There are two types of ap_ids:
91 logical and physical. The physical ap_id is based on the physical path name.
92 For the IB fabric it is \fB/devices/ib:fabric\fR. The logical ap_id is a
93 shorter, and has a more user friendly name.
94 .sp
95 .LP
96 The static ap_id for the IB fabric is \fBib\fR. The IB devices are dynamic
97 attachment points and have no physical ap_id. The logical ap_id of an IOC
98 contains its GUID, \fBib::\fR\fIIOC-GUID\fR. An example of an IOC ap_id is
99 \fBib::80020123456789a\fR. The logical ap_id of a Pseudo device, see ib(4) for
100 details, is of the format \fBib::\fR\fIdriver_name\fR\fB,\fR\fIunit-address\fR.
101 An example of a pseudo ap_id would be \fBib::sdp,0\fR where "\fBsdp\fR" is the
102 driver name and "\fB0\fR" is its \fIunit-address\fR property. The logical ap_id
103 of Port, VPPA and HCA_SVC device contains its Partition Key (\fIP_Key\fR),
104 \fIPort GUID\fR / \fINode GUID\fR and a communication service-name. The format
105 of ap_id is as below:
106 .sp
107 .ne 2
108 .na
109 \fBPort device\fR
110 .ad
111 .sp .6
112 .RS 4n
113 \fBib::\fR\fIPORT_GUID\fR\fB,\fR\fI0\fR\fB,\fR\fIservice-name\fR
114 .RE
116 .sp
117 .ne 2
118 .na
119 \fBVPPA device\fR
120 .ad
121 .sp .6
122 .RS 4n
123 \fBib::\fR\fIPORT_GUID\fR\fB,\fR\fIP_Key\fR\fB,\fR\fIservice-name\fR
124 .RE
126 .sp
127 .ne 2
128 .na
129 \fBHCA_SVC device\fR
130 .ad
131 .sp .6
132 .RS 4n
133 \fBib::\fR\fIHCA_GUID\fR\fB,\fR0\fB,\fR\fIservicename\fR
134 .RE
136 .sp
137 .LP
138 The Partition Key (\fIP_Key\fR) is \fB0\fR for Port and HCA_SVC devices. The
139 \fIP_Key\fR helps determine the partition to which this port belongs for a VPPA
140 device node. A port might have more than one \fIP_Key\fR. An example of a VPPA
141 device logical ap_id point is \fBib::80245678,ffff,ipib\fR. The
142 \fIport-GUID\fR is \fB80245678\fR, the \fIP_Key\fR is \fB0xffff\fR, and the
143 service name is \fBipib\fR. The service-name information is obtained from the
144 file \fB/kernel/drv/ib.conf\fR which contains service-name strings. The HCA's
145 logical ap_id contains its node GUID value, hca:HCA-GUID. An example is
146 \fBhca:21346543210a987\fR.
147 .sp
148 .LP
149 A listing of the IB attachment points includes information on all IB devices
150 (IOC, VPPA, HCA_SVC, Pseudo, and Port devices seen by the IBDM and the IB nexus
151 driver) in the fabric even if they are not seen by the host and configured for
152 use.
153 .sp
154 .LP
155 The following shows a listing of five IB devices (two IOC, one VPPA, one Port,
156 one HCA_SVC) and one HCA:
157 .sp
158 .in +2
159 .nf
160 example# cfgadm -al
161 Ap_Id Type Receptacle Occupant Condition
162 hca:21346543210a987 IB-HCA connected configured ok
163 ib IB-FABRIC connected configured ok
164 ib::80020123456789a IB-IOC connected configured ok
165 ib::802abc9876543 IB-IOC connected unconfigured unknown
166 ib::80245678,ffff,ipib IB-VPPA connected configured ok
167 ib::12245678,0,nfs IB-PORT connected configured ok
168 ib::21346543,0,hnfs IB-HCA_SVC connected configured ok
169 ib::sdp,0 IB-PSEUDO connected configured ok
170 .fi
171 .in -2
172 .sp
174 .sp
175 .LP
176 The ap_id \fBib::802abc9876543\fR shows an IOC device that is not yet
177 configured by the host for use or had been previously offlined by an explicit
178 .sp
179 .in +2
180 .nf
181 cfgadm \fB-c\fR unconfigure
182 .fi
183 .in -2
184 .sp
186 .sp
187 .LP
188 operation. The distinction was made by the information displayed under the
189 \fBCondition\fR column. The IB device with a zero P_Key and HCA GUID is a
190 HCA_SVC device. Refer to \fBcfgadm\fR(1M) for more information regarding
191 listing attachment points.
192 .sp
193 .LP
194 The receptacle state for attachment points have the following meanings:
195 .sp
196 .ne 2
197 .na
198 \fBconnected\fR
199 .ad
200 .sp .6
201 .RS 4n
202 For an IOC/VPPA/Port/Pseudo/HCA_SVC device, \fBconnected\fR implies that it has
203 been seen by the host. The device might not have been configured for use by
204 Solaris.
205 .sp
206 For a HCA attachment point, \fBconnected\fR implies that it has been configured
207 and is in use.
208 .sp
209 All IB ap_ids are always shown as connected.
210 .RE
212 .sp
213 .LP
214 The occupant state for attachment points have the following meanings:
215 .sp
216 .ne 2
217 .na
218 \fBconfigured\fR
219 .ad
220 .sp .6
221 .RS 4n
222 The IB device, and the HCA ap_id, are configured and usable by Solaris.
223 .RE
225 .sp
226 .ne 2
227 .na
228 \fBunconfigured\fR
229 .ad
230 .sp .6
231 .RS 4n
232 The IB device at the ap_id was explicitly offlined using \fBcfgadm\fR \fB-c\fR
233 \fBunconfigure\fR, was not successfully configured. This could be because it
234 wasn not successfully configuref for use with Solaris (no driver, or a device
235 problem), or because it was never configured for use by the IB nexus driver.
236 .sp
237 The \fBunconfigured\fR operation is not supported for the HCA attachment point.
238 The IB static apid, \fBib\fR, is shown unconfigured if the system has no IB
239 hardware.
240 .RE
242 .sp
243 .LP
244 The attachment point conditions are:
245 .sp
246 .ne 2
247 .na
248 \fBfailed\fR
249 .ad
250 .sp .6
251 .RS 4n
252 Not used.
253 .RE
255 .sp
256 .ne 2
257 .na
258 \fBfailing\fR
259 .ad
260 .sp .6
261 .RS 4n
262 Not used.
263 .RE
265 .sp
266 .ne 2
267 .na
268 \fBok\fR
269 .ad
270 .sp .6
271 .RS 4n
272 Normal state. Ready for use.
273 .RE
275 .sp
276 .ne 2
277 .na
278 \fBunknown\fR
279 .ad
280 .sp .6
281 .RS 4n
282 This state is only valid for IB device that have been probed by IBDM but not
283 yet configured for use by Solaris. It is also shown for devices that have been
284 explicitly offlined by a \fBcfgadm\fR \fB-c\fR \fBunconfigure\fR operation.
285 This condition does not apply to a HCA attachment point.
286 .RE
288 .sp
289 .ne 2
290 .na
291 \fBunusable\fR
292 .ad
293 .sp .6
294 .RS 4n
295 Not used.
296 .RE
298 .SH OPTIONS
299 .sp
300 .LP
301 The following options are supported:
302 .sp
303 .ne 2
304 .na
305 \fB\fB-c\fR \fIfunction\fR\fR
306 .ad
307 .sp .6
308 .RS 4n
309 The IB hardware specific library supports two generic commands
310 (\fIfunction\fRs). These commands are not supported on the static attachment
311 points (that is, the HCA ap_ids and the IB static \fBib\fR ap_id).
312 .sp
313 The following generic commands are supported:
314 .sp
315 .ne 2
316 .na
317 \fBconfigure\fR
318 .ad
319 .sp .6
320 .RS 4n
321 Configure the IB device to be used by Solaris.
322 .RE
324 .sp
325 .ne 2
326 .na
327 \fBunconfigure\fR
328 .ad
329 .sp .6
330 .RS 4n
331 Unconfigure the IB device. If successful, \fBcfgadm\fR reports the
332 \fBcondition\fR of this \fBap_id\fR as \fBunknown\fR.
333 .RE
335 .RE
337 .sp
338 .ne 2
339 .na
340 \fB\fB-f\fR\fR
341 .ad
342 .sp .6
343 .RS 4n
344 Not supported.
345 .RE
347 .sp
348 .ne 2
349 .na
350 \fB\fB-h\fR \fIap_id\fR\fR
351 .ad
352 .sp .6
353 .RS 4n
354 Obtain IB specific help for an IB attachment point.
355 .RE
357 .sp
358 .ne 2
359 .na
360 \fB\fB-l\fR\fR
361 .ad
362 .sp .6
363 .RS 4n
364 List the state and condition of IB attachment points. The \fB-l\fR option works
365 as described in \fBcfgadm\fR(1M).
366 .sp
367 When paired with the \fB-a\fR option, displays the dynamic attachment points as
368 well (IOC, VPPA, Port, Pseudo, and HCA_SVC devices).
369 .sp
370 When paired with \fB-v\fR option, displays verbose data about the ap_ids. For
371 an IOC, the \fBInfo\fR field in the
372 .sp
373 .in +2
374 .nf
375 cfgadm \fB-avl\fR
376 .fi
377 .in -2
378 .sp
380 output displays the following information: VendorID, IOCDeviceID,
381 DeviceVersion, SubsystemVendorID, SubsystemID, Class, Subclass, Protocol,
382 ProtocolVersion and IDString from the IOCControllerProfile. If the ID string
383 isn't provided then nothing is displayed in its place. These fields are defined
384 in the InfiniBand Specification Volume 1 (http://www.infinibandta.org).
385 .sp
386 For a VPPA, Port, or HCA_SVC device the \fBInfo\fR field in the \fBcfgadm
387 -lav\fR display shows the service name information to which this device is
388 bound. If no such information exists, nothing is displayed.
389 .sp
390 For a Pseudo device \fBcfgadm -alv\fR displays the driver name and its
391 \fBunit-address\fR information. For a HCA the verbose listing displays the
392 VendorID, ProductID of the HCA, number of ports it has, and the PortGUID value
393 of its ports. See \fBEXAMPLES\fR.
394 .RE
396 .sp
397 .ne 2
398 .na
399 \fB\fB-o\fR \fIhardware_option\fR\fR
400 .ad
401 .sp .6
402 .RS 4n
403 This option is not currently defined.
404 .RE
406 .sp
407 .ne 2
408 .na
409 \fB\fB-s\fR \fIlisting_option\fR\fR
410 .ad
411 .sp .6
412 .RS 4n
413 Attachment points of class ib can be listed by using the select sub-option.
414 Refer to the \fBcfgadm\fR(1M) man page for more information.
415 .RE
417 .sp
418 .ne 2
419 .na
420 \fB\fB-x\fR \fIhardware_function\fR\fR
421 .ad
422 .sp .6
423 .RS 4n
424 Perform a hardware specific function. Note that the \fIname\fR can not be more
425 than 4 characters long.
426 .sp
427 The following hardware specific functions are supported:
428 .sp
429 .ne 2
430 .na
431 \fB\fBadd_service\fR
432 \fB-ocomm\fR\fB=[port|vppa|hca_svc],service=\fR\fIname\fR\fR
433 .ad
434 .sp .6
435 .RS 4n
436 This hardware specific function is supported on the static \fBIB\fR attachment
437 point. It can be used to add a new service to \fB/kernel/drv/ib.conf\fR file
438 and to update the \fBib\fR(7D) driver.
439 .sp
440 You must use the \fBservice=\fR\fIname\fR option to indicate the new service to
441 be added. You must use the option \fBcomm=[port|vppa|hca_svc]\fR option to add
442 the \fBname\fR service to either \fBport-svc-list\fR or to the
443 \fBhca-svc-list\fR in the \fB/kernel/drv/ib.conf\fR file. See \fBEXAMPLES\fR.
444 .RE
446 .sp
447 .ne 2
448 .na
449 \fB\fBdelete_service\fR
450 \fB-ocomm\fR\fB=[port|vppa|hca_svc],service=\fR\fIname\fR\fR
451 .ad
452 .sp .6
453 .RS 4n
454 This hardware specific function is supported on the static \fBIB\fR attachment
455 point only. It can be used to delete an existing service from the
456 \fB/kernel/drv/ib.conf\fR file and also from the \fBib\fR(7D) driver's data
457 base. You must use the \fBservice=name\fR option to indicate which service to
458 delete. You must use the \fBcomm=[port|vppa|hca_svc]\fR option to delete this
459 service from the \fBport-svc-list\fR, \fBvppa-svc-list\fR, or
460 \fBvppa-svc-list\fR of the \fB/kernel/drv/ib.conf\fR file. See \fBEXAMPLES\fR.
461 .RE
463 .sp
464 .ne 2
465 .na
466 \fB\fBlist_clients\fR\fR
467 .ad
468 .sp .6
469 .RS 4n
470 Supported on \fBHCA\fR attachment points. Displays all the kernel IB clients
471 using this \fBHCA\fR. It also displays the respective ap_ids of these kernel IB
472 clients and if they have opened an alternate \fBHCA\fR device. See
473 \fBEXAMPLES\fR.
474 .sp
475 \&.
476 .sp
477 If a given kernel IB client does not have a valid ap_id then a \fB-\fR is
478 displayed in that column.
479 .RE
481 .sp
482 .ne 2
483 .na
484 \fB\fBlist_services\fR\fR
485 .ad
486 .sp .6
487 .RS 4n
488 This hardware specific function is supported on the static \fBIB\fR attachment
489 point only. It lists all the Port and VPPA services as read from the
490 \fB/kernel/drv/ib.conf\fR file. See \fBEXAMPLES\fR.
491 .RE
493 .sp
494 .ne 2
495 .na
496 \fB\fBunconfig_clients\fR\fR
497 .ad
498 .sp .6
499 .RS 4n
500 This hardware specific function is supported on the static HCA attachment point
501 only. It can be used to unconfigure all IB kernel clients of this given HCA.
502 Only IB kernel clients that do not have an alternate HCA are unconfigured. See
503 \fBEXAMPLES\fR.
504 .RE
506 .sp
507 .ne 2
508 .na
509 \fB\fBupdate_ioc_config\fR\fR
510 .ad
511 .sp .6
512 .RS 4n
513 This hardware specific function is supported on static ib attachment point and
514 the IOC attachment points. For the \fBib\fR APID, this function updates
515 properties of all the IOC device nodes. For the IOC APID, this function updates
516 the properties of specified IOC device node. This command updates the
517 \fBport-list\fR, \fBport-entries\fR, \fBservice-id\fR, and \fBservice-name\fR
518 IOC node properties .
519 .sp
520 See \fBib\fR(7D).
521 .RE
523 .sp
524 .ne 2
525 .na
526 \fB\fBupdate_pkey_tbls\fR\fR
527 .ad
528 .sp .6
529 .RS 4n
530 Supported on the static \fBib\fR attachment point. Updates the \fBPKEY\fR
531 information inside \fBIBTL\fR. \fBIBTL\fR re-reads the \fBP_Key\fR tables for
532 all the ports on each \fBHCA\fR present on the host.
533 .sp
534 See \fBibtl\fR(7D).
535 .RE
537 .RE
539 .SH EXAMPLES
540 .LP
541 \fBExample 1 \fRListing the State and Condition of IB Devices
542 .sp
543 .LP
544 The following command lists the state and condition of IB devices on the
545 system. It only shows the static attachment points.
547 .sp
548 .in +2
549 .nf
550 example# cfgadm
551 hca:21346543210a987 IB-HCA connected configured ok
552 ib IB-FABRIC connected configured ok
553 .fi
554 .in -2
555 .sp
557 .sp
558 .LP
559 The \fB-a\fR option lists all attachment points. The following example uses the
560 \fB-a\fR option and lists all attachment points:
562 .sp
563 .in +2
564 .nf
565 example# cfgadm -a
566 hca:21346543210a987 IB-HCA connected configured ok
567 ib IB-FABRIC connected configured ok
568 ib::80020123456789a IB-IOC connected unconfigured ok
569 ib::80245678,ffff,ipib IB-VPPA connected configured ok
570 ib::21346543,0,hnfs IB-HCA_SVC connected configured ok
571 ib::12245678,0,nfs IB-PORT connected configured ok
572 ib::sdp,0 IB-PSEUDO connected configured ok
573 .fi
574 .in -2
575 .sp
577 .LP
578 \fBExample 2 \fRListing the Verbose Status of a IB VPPA Device
579 .sp
580 .LP
581 The following command lists the verbose status of a IB VPPA device:
583 .sp
584 .in +2
585 .nf
586 example# cfgadm -alv ib::80245678,ffff,ipib
587 Ap_Id Receptacle Occupant Condition Information
588 When Type Busy Phys_Id
589 ib::80245678,ffff,ipib connected configured ok ipib
590 unavailable IB-VPPA n /devices/ib:fabric::80245678,ffff,ipib
591 .fi
592 .in -2
593 .sp
595 .sp
596 .LP
597 A verbose listing of an IOC shows additional information. The following command
598 shows a verbose listing:
600 .sp
601 .in +2
602 .nf
603 example# cfgadm -alv ib::80020123456789a
604 Ap_Id Receptacle Occupant Condition Information
605 When Type Busy Phys_Id
606 ib::80020123456789a connected configured ok VID: 0xeaea
607 DEVID: 0xeaea VER: 0x5 SUBSYS_VID: 0x0 SUBSYS_ID: 0x0 CLASS: 0xffff
608 SUBCLASS: 0xff PROTO: 0xff PROTOVER: 0x1 ID_STRING: Sample Host Adapter
609 unavailable IB-IOC n /devices/ib:fabric::80020123456789a
610 .fi
611 .in -2
612 .sp
614 .sp
615 .LP
616 A verbose listing of a Pseudo device shows:
618 .sp
619 .in +2
620 .nf
621 example# cfgadm -alv ib::sdp,0
622 Ap_Id Receptacle Occupant Condition Information
623 When Type Busy Phys_Id
624 ib::sdp,0 connected configured ok Driver = "sd
625 p" Unit-address = "0"
626 unavailable IB-PSEUDO n /devices/ib:fabric::sdp,0
627 .fi
628 .in -2
629 .sp
631 .sp
632 .LP
633 A verbose listing of a HCA shows:
635 .sp
636 .in +2
637 .nf
638 example# cfgadm -alv hca:21346543210a987
639 Ap_Id Receptacle Occupant Condition Information
640 When Type Busy Phys_Id
641 hca:21346543210a987 connected configured ok VID: 0x15b3,
642 PID: 0x5a44, #ports: 0x2, port1 GUID: 0x80245678, port2 GUID: 0x80245679
643 unavailable IB-HCA n /devices/ib:21346543210a987
644 .fi
645 .in -2
646 .sp
648 .sp
649 .LP
650 You can obtain more user-friendly output if you specify these following
651 \fBcfgadm\fR class and field selection options: \fB\fR\fB-s\fR
652 \fB"select=class(ib),cols=ap_id:info"\fR
654 .sp
655 .LP
656 The following command displays only IB ap_ids. The output only includes the
657 \fBap_id\fR and \fBInformation\fR fields.
659 .sp
660 .in +2
661 .nf
663 # cfgadm -al -s "cols=ap_id:info" ib::80245678,ffff,ipib
664 Ap_Id Information
665 ib::80245678,ffff,ipib ipib
666 .fi
667 .in -2
668 .sp
670 .LP
671 \fBExample 3 \fRUnconfiguring an Existing IB IOC
672 .sp
673 .LP
674 The following command unconfigures the IB IOC attached to
675 \fBib::80020123456789a\fR, then displays the status of the \fBap_id\fR:
677 .sp
678 .in +2
679 .nf
680 # cfgadm -c unconfigure ib::80020123456789a
681 Unconfigure the device: /devices/ib:fabric::80020123456789a
682 This operation will suspend activity on the IB device
683 Continue (yes/no)?
684 .fi
685 .in -2
686 .sp
688 .sp
689 .LP
690 Enter: \fBy\fR
692 .sp
693 .in +2
694 .nf
695 IB device unconfigured successfully.
696 # cfgadm -al ib::80020123456789a
697 Ap_Id Type Receptacle Occupant Condition
698 ib::80020123456789 IB-IOC connected unconfigured unknown
699 #
700 .fi
701 .in -2
702 .sp
704 .sp
705 .LP
706 The condition unknown implies that the device node doesn't exist anymore and
707 this IB device's existence is known only to the IB Device Manager.
709 .LP
710 \fBExample 4 \fRConfiguring an IB IOC
711 .sp
712 .LP
713 The following series of commands configures an IB device attached to
714 \fBib::80020123456789a\fR:
716 .sp
717 .in +2
718 .nf
719 # cfgadm -yc configure ib::80020123456789a
720 # cfgadm -al ib::80020123456789a
721 Ap_Id Type Receptacle Occupant Condition
722 ib::80020123456789a IB-IOC connected configured ok
723 .fi
724 .in -2
725 .sp
727 .LP
728 \fBExample 5 \fRListing All Kernel IB Clients of a HCA
729 .sp
730 .LP
731 The following command lists all kernel IB clients of an HCA attached to
732 \fBhca:21346543210a987\fR:
734 .sp
735 .in +2
736 .nf
737 # cfgadm -x list_clients hca:21346543210a987
738 Attachment Point Clients Alternate HCA
739 ib::80020123456789a ioc1 Yes
740 ib::80245678,ffff,ipib ipib No
741 ib::21346543,0,hnfs hnfs No
742 - ibdm No
743 - ibmf No
744 .fi
745 .in -2
746 .sp
748 .LP
749 \fBExample 6 \fRAdding a Port Service
750 .sp
751 .LP
752 The following command adds a new Port service called \fBsrp\fR:
754 .sp
755 .in +2
756 .nf
757 # cfgadm -o comm=port,service=srp -x add_service ib
758 .fi
759 .in -2
760 .sp
762 .LP
763 \fBExample 7 \fRDeleting a VPPA Service
764 .sp
765 .LP
766 The following command deletes the \fBibd\fR VPPA service \fBibd\fR:
768 .sp
769 .in +2
770 .nf
771 # cfgadm -o comm=vppa,service=ipib -x delete_service ib
772 .fi
773 .in -2
774 .sp
776 .LP
777 \fBExample 8 \fRListing Port, VPPA, HCA_SVC Services
778 .sp
779 .LP
780 The following command lists all Port, VPPA, and HCA_SVC services:
782 .sp
783 .in +2
784 .nf
785 # cfgadm -x list_services ib
786 Port communication services:
787 srp
789 VPPA communication services:
790 ipib
791 nfs
793 HCA_SVC communication services:
794 hnfs
795 .fi
796 .in -2
797 .sp
799 .LP
800 \fBExample 9 \fRReprobing IOC Devices
801 .sp
802 .LP
803 The following command reprobes all IOC device nodes.
805 .sp
806 .in +2
807 .nf
808 # cfgadm -x update_ioc_config ib
809 This operation can update properties of IOC devices.
810 Continue (yes/no)?
812 Enter: y
814 #
815 .fi
816 .in -2
817 .sp
819 .LP
820 \fBExample 10 \fRUnconfiguring All Kernel Clients of a HCA
821 .sp
822 .LP
823 The following command unconfigures all kernel clients of a HCA
825 .sp
826 .in +2
827 .nf
828 # cfgadm -x unconfig_clients hca:21346543
829 This operation will unconfigure clients of this HCA.
830 Continue (yes/no)?
832 Enter: y
833 .fi
834 .in -2
835 .sp
837 .SH FILES
838 .sp
839 .ne 2
840 .na
841 \fB\fB/usr/lib/cfgadm/ib.so.1\fR\fR
842 .ad
843 .sp .6
844 .RS 4n
845 Hardware-specific library for generic InfiniBand device administration
846 .RE
848 .SH SEE ALSO
849 .sp
850 .LP
851 \fBcfgadm\fR(1M), \fBconfig_admin\fR(3CFGADM), \fBlibcfgadm\fR(3LIB),
852 \fBib\fR(4), \fBattributes\fR(5), \fBib\fR(7D), \fBibdm\fR(7D), \fBibtl\fR(7D)
853 .sp
854 .LP
855 InfiniBand Specification Volume 1 (http://www.infinibandta.org)
856 .SH NOTES
857 .sp
858 .LP
859 Apart from the listing (\fBcfgadm\fR \fB-l\fR or \fBcfgadm\fR \fB-x\fR
860 \fBlist_clients\fR), only the superuser can execute any functions on an
861 attachment point.