1IPRCONFIG(8) System Manager's Manual IPRCONFIG(8)
2
6 iprconfig - IBM Power RAID storage adapter configuration/recovery util‐
7 ity
8
10 iprconfig [-e editor] [-k dir] [-c command]
11 iprconfig --version --debug --force
13
15 iprconfig is used to configure IBM Power RAID storage adapters, display
16 information about them, and to perform adapter and disk unit recovery.
17 The menu options are:
18 1. Display hardware status.
20 This option can be used to display various information regarding the
21 IBM Power RAID adapters attached to the system and the disk units con‐
22 trolled by them. For each adapter and disk unit, their /dev name, phys‐
23 ical location, description, vendor/product ID, and hardware status will
24 be available. Beside each resource is an OPT field. By entering a 1
25 beside any resource, detailed information about that resource can be
26 obtained. For an adapter resource, this will display the adapter
27 firmware version and the physical location amongst other things.
28 2. Work with Disk Arrays
30 This option will present a second menu containing disk array related
31 commands.
32 Display disk array status is used to display the status of disk arrays
34 on the system.
35 Create a disk array is used to create a disk array.
37 Delete a disk array is used to delete disk arrays. Selecting this
39 option will provide you with a list of disk arrays which can be
40 deleted.
41 Add a device to a disk array is used to include devices of similar
43 capacity into an existing disk array. This function is currently only
44 supported for RAID 5 and RAID 6 disk arrays.
45 Format device for advanced function is used to format disks to 522
47 bytes/sector so that they may be used in a disk array. Only disks which
48 are not formatted for advanced function or are formatted for advanced
49 function but are not known to be zeroed will be available for selection
50 for this function.
51 Format device for JBOD function (512) is used to format disks to 512
53 bytes/sector so that they may be used as standalone disks. Only disks
54 which are not formatted for JBOD function or are formatted for JBOD
55 function and are in the Format Required state will be available for
56 this function.
57 Work with hot spares is used to create a hot spare which designates a
59 device as a dedicated hot spare. It is also used to delete a hot spare
60 which unconfigures a previously configured hot spare.
61 Work with asymmetric access is used to select which path of a disk
63 array will be the primary path in a dual controller environment. Asym‐
64 metric Access must be enabled on the adapter first. Not all adapters
65 support asymmetric access and adapters that do provide support may
66 require updated microcode.
67 Force RAID Consistency Check is used to force a consistency check on a
69 RAID array. All ipr adapters continually perform background consistency
70 checking when idle. This option can be used to force a consistency
71 check to be performed.
72 Migrate disk array protection is used to change the RAID protection
74 level for an array to another supported level. In some cases, this
75 will require adding more disks to the array. In other cases, disks
76 will be freed.
77 3. Work with disk unit recovery is used to perform the following disk
79 unit recovery actions:
80 Concurrent add device is used to concurrently add a new disk to a run‐
82 ning system. This feature is only supported with SES (SCSI Enclosure
83 Services) packaging.
84 Concurrent remove device is used to concurrently remove a disk from a
86 running system. This feature is only supported with SES (SCSI Enclo‐
87 sure Services) packaging.
88 Initialize and format disk unit is used to issue a SCSI format command
90 to attached devices. A format unit command has special meaning to the
91 adapter and is used as a service action for certain error conditions.
92 Formatting a disk unit will lose all data on that drive. If the disk is
93 attached to an ipr adapter that does not support RAID, the drive will
94 be formatted to 512 bytes/sector. If the disk is attached to an ipr
95 RAID adapter, the block size will not be changed. To change the block
96 size, use the format menu options under the disk arrays menu.
97 Reclaim IOA cache storage is used to repair cache error conditions.
99 ATTENTION: Use this option with care. This is used to discard data from
100 the cache and may result in data loss. This option is designed to be
101 used by authorized IBM hardware customer engineers.
102 Rebuild disk unit data is generally used following concurrent mainte‐
104 nance. Select this option after a failing array member device has been
105 replaced to reconstruct the device as an active array member.
106 Work with resources containing cache battery packs is used to display
108 information regarding rechargeable cache battery packs and to force
109 rechargeable cache battery packs into an error state so that they can
110 be replaced prior to failure. ATTENTION: Once an error has been forced
111 on a rechargeable cache battery pack write caching will be disabled
112 until the battery pack is replaced.
113 4. Work with SCSI bus configuration is used to change configurable SCSI
115 bus attributes, such as maximum SCSI bus speed, SCSI initiator ID, etc.
116 5. Work with driver configuration is used to change driver configurable
118 attributes, such as log_level.
119 6. Work with disk configuration is used to change configurable disk
121 attributes, such as queue depth.
122 7. Work with adapter configuration is used to change configurable
124 adapter attributes, such as dual adapter settings. Refer to the fol‐
125 lowing command line options: primary, secondary, query-ha-mode, set-ha-
126 mode, set-ioa-asymmetric-access and set-array-asymmetric-access for
127 more information regarding these settings.
128 8. Download microcode is used to download microcode to ipr adapters and
130 attached SCSI disks.
131 9. Analyze Log is an option available to analyze /var/log/messages*
133 files. By default it will use vi as the editor to open the concatenated
134 error log files. This can be changed by using option 6 on the Kernel
135 Messages Log menu. Selecting option 1 on the Kernel Messages Log menu
136 will display only the most recent errors logged by the ipr device
137 driver and may be useful to filter out some of the clutter. Option 2
138 will display all recorded errors logged by the ipr device driver.
139 Option 3 will display all kernel messages. Option 4 will display errors
140 logged by the iprconfig utility. This may be useful for debugging prob‐
141 lems. Option 5 can be used to change where the tool looks to find the
142 kernel messages files. The default is to look in /var/log.
143
145 -e editor
146 Default editor for viewing error logs. The default editor is vi,
147 but can be changed with this parameter.
148 -k directory
150 Kernel messages root directory. Root directory to look for ker‐
151 nel messages. Default is /var/log.
152 -c command
154 Command line, non-interactive commands. Currently supported com‐
155 mands include:
156 show-config
158 Show ipr configuration.
159 show-alt-config
161 Show alternate ipr configuration information.
162 show-ioas
164 Show all ipr adapters.
165 show-arrays
167 Show all ipr arrays.
168 show-battery-info [IOA]
170 Show cache battery information for specified IOA. Exam‐
171 ple:
172 iprconfig -c show-battery-info sg5
173 show-details [device]
175 Show device details for specified device. Example:
176 iprconfig -c show-details sda
177 show-hot-spares
179 Show all configured hot spares.
180 show-af-disks
182 Show disks formatted for Advanced Function that are not
183 configured in an array or as a hot spare.
184 show-all-af-disks
186 Show all disks formatted for Advanced Function
187 show-jbod-disks
189 Show all disks formatted for JBOD Function.
190 show-slots
192 Show all disks slots available on the system.
193 status [device]
195 Show the status of the specified device. This is the same
196 status as which shows up in the last column of the Dis‐
197 play hardware status menu. Can specify either a /dev/sdX
198 name or a /dev/sgX name. Example:
199 iprconfig -c status /dev/sda
200 alt-status [device]
202 Show the status of the specified device. This is the same
203 status as above with the exception of when a long running
204 command is executing to the device, in which case the
205 percent complete for the long running command is printed.
206 query-raid-create [IOA]
208 Show all devices attached to the specified IOA that are
209 candidates for being used in a RAID array. Example:
210 iprconfig -c query-raid-create sg5
211 query-raid-delete [IOA]
213 Show all RAID arrays attached to the specified IOA that
214 can be deleted.
215 iprconfig -c query-raid-delete sg5
216 query-hot-spare-create [IOA]
218 Show all devices attached to the specified IOA that are
219 candidates for being hot spares.
220 query-hot-spare-delete [IOA]
222 Show all hot spares attached to the specified IOA that
223 can be deleted.
224 query-raid-consistency-check
226 Show all RAID arrays that are candidates for a RAID con‐
227 sistency check.
228 query-format-for-jbod
230 Show all disks that can be reformatted for JBOD function.
231 query-reclaim
233 Show all IOAs that may need a reclaim cache storage.
234 query-arrays-raid-include
236 Show all RAID arrays that can have disks included in them
237 to increase their capacity.
238 query-devices-raid-include [array]
240 Show all disks that can be added to the specified array
241 to increase its capacity.
242 query-supported-raid-levels [IOA]
244 Show all RAID levels supported by the specified adapter.
245 query-include-allowed [IOA] [raid level]
247 Some RAID levels allow for adding additional disks to
248 existing disk arrays to increase their capacity. Prints
249 "yes" to stdout if the specified RAID level supports this
250 function, else prints "no".
251 query-max-devices-in-array [IOA] [raid level]
253 Print the maximum number of devices allowed in a RAID
254 array of the specified RAID level for the specified RAID
255 adapter.
256 query-min-devices-in-array [IOA] [raid level]
258 Print the minimum number of devices allowed in a RAID
259 array of the specified RAID level for the specified RAID
260 adapter.
261 query-min-mult-in-array [IOA] [raid level]
263 Print the minimum multiple of devices required in a RAID
264 array of the specified RAID level for the specified RAID
265 adapter.
266 query-supp-stripe-sizes [IOA] [raid level]
268 Print all supported stripe sizes supported for RAID
269 arrays of the specified RAID level on the specified RAID
270 adapter. Stripe sizes are printed in units of KB.
271 query-recommended-stripe-size [IOA] [raid level]
273 Print the default/recommended stripe size for RAID arrays
274 of the specified RAID level on the specified RAID
275 adapter. Stripe size is in units of KB.
276 query-recovery-format
278 Show all disks that can be formatted for error recovery
279 purposes.
280 query-raid-rebuild
282 Show all disks in RAID arrays that can be rebuilt.
283 query-format-for-raid
285 Show all disks that can be formatted such that they can
286 be used in a RAID array or as a hot spare.
287 query-ucode-level [device]
289 Show the microcode level that is currently loaded on the
290 specified device. Note: The device specified may be the
291 sg device associated with an IOA, in which case the IOA's
292 microcode level will be shown.
293 ssd-report [device]
295 Display information about Read Intensive SSD devices in
296 the system.
297 show-ucode-levels
299 Show the microcode level that is currently loaded for
300 every device and adapter in the system. If newer
301 microcode is available on the filesystem than what is
302 loaded on the device, an * chararacter will be displayed
303 next to the device.
304 query-format-timeout [device]
306 Show the current format timeout to be used when format‐
307 ting the specified disk. This value is only applicable
308 when the device is currently in Advanced Function format.
309 query-qdepth [device]
311 Show the queue depth currently being used for the speci‐
312 fied disk.
313 query-tcq-enable [device]
315 Print 1 to stdout if tagged queuing is enabled for the
316 specified device, else print 0 to stdout.
317 query-log-level [IOA]
319 Print the current log level being used for the specified
320 IOA. Can be a number from 0 to n.
321 query-add-device
323 Show all empty disk slots that can have a disk concur‐
324 rently added.
325 query-remove-device
327 Show all disk slots which are either empty or have disks
328 in them which can be concurrently removed from the run‐
329 ning system.
330 query-initiator-id [IOA] [busno]
332 Show the current SCSI initiator ID used by the IOA for
333 the specified SCSI bus.
334 query-bus-speed [IOA] [busno]
336 Show the current maximum SCSI bus speed allowed on the
337 specified SCSI bus.
338 query-bus-width [IOA] [busno]
340 Show the current SCSI bus width in units of bits for the
341 specified SCSI bus.
342 query-path-status [IOA]
344 Show the current dual path state for the SAS devices
345 attached specified IOA.
346 query-path-details [device]
348 Show the current dual path details for the specified SAS
349 device.
350 query-arrays-raid-migrate
352 Show the arrays that can be migrated to a different pro‐
353 tection level.
354 query-devices-raid-migrate [array]
356 Show the AF disks that are candidates to be used in a
357 migration for a given array.
358 query-raid-levels-raid-migrate [array]
360 Show the protection levels to which the given array can
361 be migrated.
362 query-stripe-sizes-raid-migrate [array] [raid level]
364 Given an array and a protection level, show the valid
365 stripe sizes to which the array can be migrated.
366 query-devices-min-max-raid-migrate [array] [raid level]
368 Show the number of devices that will be removed for a
369 migration to a protection level that requires fewer
370 devices. Or, show the minmum number of devices required,
371 the maximum number of devices allowed and the multiple of
372 the number of devices required for a migration that
373 requires more devices.
374 query-ioas-asymmetric-access
376 Show the IOAs that support asymmetric access.
377 query-arrays-asymmetric-access
379 Show the disk arrays that are candidates for setting
380 their asymmetric access mode to Optimized or Non-Opti‐
381 mized.
382 query-ioa-asymmetric-access-mode [IOA]
384 Show the current asymmetric access mode for the given
385 IOA.
386 query-array-asymmetric-access-mode [array]
388 Show the current asymmetric access mode for the given
389 disk array.
390 query-ioa-caching [IOA]
392 Show whether or not the user requested caching mode for
393 the given IOA is set to default or disabled.
394 query-array-label [label]
396 Show the device name of the array with the specified
397 label. Label must have been specified when creating the
398 RAID array. See raid-create command.
399 query-array-rebuild-rate [IOA]
401 Show the array rebuild rate for the given IOA.
402 query-array-rebuild-verify [IOA]
404 Show whether array rebuild verification is enabled for
405 the given IOA.
406 query-array [location]
408 Show the device name of the array of which one of the
409 disks in the array has the specified platform location
410 code.
411 query-device [location]
413 Show the device name of the disk that has the specified
414 platform location code.
415 query-location [device]
417 The device specified can be either the device name of a
418 disk or the device name of a single disk RAID 0 array. If
419 the specified device name is a disk, the platform loca‐
420 tion code will be displayed. If the specified device name
421 is a single device RAID 0 array, the platform location of
422 the disk which is a member of the specified array will be
423 displayed.
424 query-write-cache-policy [device]
426 Show the current write cache policy for [device].
427 raid-create [-r raid_level] [-s stripe_size_in_kb] [-l label]
429 [--skip-format] [-c cache_policy] [devices...]
430 Create a RAID array. RAID level can be any supported RAID
431 level for the given adapter, such as 0, 10, 5, 6. Cur‐
432 rently supported stripe sizes in kb include 16, 64, and
433 256. If raid_level is not specified, it will default to
434 RAID 5. If stripe size is not specified, it will default
435 to the recommended stripe size for the selected RAID
436 level. Available cache policies are the same that can be
437 passed to set-write-cache-policy command. If none is
438 specified, write back is assumed. Devices are specified
439 with their full name, either the /dev/sd name or the
440 /dev/sg name is acceptable. On some RAID adapters, a
441 label can also be specified. Example array creation:
442 iprconfig -c raid-create -r 5 -s 64 /dev/sda /dev/sdb
443 /dev/sdc
444 This would create a RAID 5 array with a 64k stripe size
445 using the specified devices.
446 raid-delete [RAID device]
448 Delete the specified RAID array. Specify either the
449 /dev/sd name or the /dev/sg name. Only 1 array can be
450 deleted with a single command. Example:
451 iprconfig -c raid-delete /dev/sda
452 This would delete the disk array represented by /dev/sda
453 raid-include [array] [disk] ... [disk]
455 Add the specified devices to the specified disk array to
456 increase its capacity. Example:
457 iprconfig -c raid-include sda sg6 sg7
458 raid-migrate -r raid_level [-s stripe_size_in_kb] array [disk]
460 ... [disk]
461 Migrate an existing RAID array to a new RAID protection
462 level. Optionally, a new stripe size can be given. In
463 some cases one or more new disks must be added for the
464 migration to succeed. Example:
465 iprconfig -c raid-migrate -r 10 -s 64 sda sg5 sg6
466 format-for-raid [disk] ... [disk]
468 Format the specified disks for Advanced Function so they
469 can be used in a RAID array or as a hot spare.
470 format-for-jbod [disk] ... [disk]
472 Format the specified disks for JBOD Function so they can
473 be used as standalone disks.
474 recovery-format [disk] ... [disk]
476 Format the specified disks as directed by the reference
477 guide for error recovery purposes.
478 hot-spare-create [disk]
480 Create a hot spare using the specified Advanced Function
481 disk.
482 hot-spare-delete [disk]
484 Delete the specified hot spare.
485 disrupt-device [disk]
487 Force the specified Advanced Function device failed.
488 reclaim-cache [IOA]
490 Reclaim the specified IOA's write cache. ATTENTION: Use
491 this option with care. This is used to discard data from
492 the cache and may result in data loss. This option is
493 designed to be used by authorized IBM hardware customer
494 engineers.
495 reclaim-unknown-cache [IOA]
497 Reclaim the specified IOA's write cache and allow unknown
498 data loss. ATTENTION: Use this option with care. This is
499 used to discard data from the cache and WILL result in
500 data loss. This option is designed to be used by autho‐
501 rized IBM hardware customer engineers.
502 raid-consistency-check [array]
504 Force a full RAID consistency check on the specified
505 array. This command will return before the RAID consis‐
506 tency check has completed. Use the status command to
507 check the status of the command.
508 raid-rebuild [disk]
510 Following a disk replacement for a failed disk in a RAID
511 array, use this command to rebuild the failed disk's data
512 onto the new disk and return the disk array to the Active
513 state.
514 update-ucode [device] [microcode file]
516 Update the microcode on the specified device (IOA or
517 disk) with the specified microcode file. ATTENTION: Lim‐
518 ited checking of the microcode image is done. Make sure
519 the specified microcode file is the correct file for the
520 specified device.
521 update-all-ucodes
523 Update the microcode of every device with the latest ver‐
524 sion found in the system.
525 set-format-timeout [disk] [timeout in hours]
527 Set the format timeout to be used when formatting the
528 specified disk.
529 set-qdepth [device] [queue depth]
531 Set the queue depth for the specified device or disk
532 array.
533 set-tcq-enable [device] [0 = disable, 1 = enable]
535 Enable/disable tagged command queueing for the specified
536 device.
537 set-log-level [IOA] [log level]
539 Set the error logging verbosity to use for the specified
540 IOA. Default is 2.
541 set-write-cache-policy [device] [writeback|writethrough]
543 Set the write cache policy for [device]. Available poli‐
544 cies are writeback and writethrough. This command sup‐
545 ports JBOD disk (write cache) and Volume Sets (vset write
546 cache). Example:
547 iprconfig -c set-write-cache-policy sdp writeback
548 identify-disk [disk] [0 = turn off identify LED, 1 = turn on
550 identify LED]
551 Turn on/off the disk identify LED for the specified disk.
552 This function may or may not be available depending on
553 the hardware packaging.
554 identify-slot [location] [0 = turn off identify LED, 1 = turn on
556 identify LED]
557 Turn on/off the disk identify LED for the specified loca‐
558 tion. This function may or may not be available depending
559 on the hardware packaging. Example:
560 iprconfig -c identify-slot 0000:d8:01.0/0:1:1: 1
561 remove-disk [disk] [0 = turn off identify LED, 1 = turn on iden‐
563 tify LED]
564 Turn on/off the disk remove identify LED for the speci‐
565 fied device. When 1 is specified as the second argument,
566 the specified disk is set to the remove state. When in
567 this state, the disk may be removed. Once the disk has
568 been physically removed, iprconfig must be invoked again
569 with the second argument set to 0. This turns off the
570 slot identifier light and logically removes the disk from
571 the host operating system.
572 remove-slot [location] [0 = turn off identify LED, 1 = turn on
574 identify LED]
575 Turn on/off the disk remove identify LED for the speci‐
576 fied location. When 1 is specified as the second argu‐
577 ment, the specified location is set to the remove state.
578 When in this state, the disk may be removed. Once the
579 disk has been physically removed, iprconfig must be
580 invoked again with the second argument set to 0. This
581 turns off the slot identifier light and logically removes
582 the disk from the host operating system. Example:
583 iprconfig -c remove-slot 0000:d8:01.0/0:1:1: 1
584 add-slot [location] [0 = turn off identify LED, 1 = turn on
586 identify LED]
587 Turn on/off the disk insert identify LED for the speci‐
588 fied location. When 1 is specified as the second argu‐
589 ment, the specified location is set to the insert state.
590 When in this state, the disk may be inserted. Once the
591 disk has been physically inserted, iprconfig must be
592 invoked again with the second argument set to 0. This
593 turns off the slot identifier light and logically adds
594 the disk to the host operating system. Example:
595 iprconfig -c add-slot 0000:d8:01.0/0:1:1: 1
596 set-initiator-id [IOA] [busno] [initiator id]
598 Set the IOA's SCSI initiator ID for the specified bus.
599 Must be a value between 0 and 7 and must not conflict
600 with any other device on the SCSI bus.
601 set-bus-speed [IOA] [busno] [speed in MB/sec]
603 Set the maximum SCSI bus speed allowed on the specified
604 SCSI bus.
605 set-bus-width [IOA] [busno] [bus width in # bits]
607 Set the SCSI bus width to use for the specified SCSI bus.
608 Example:
609 iprconfig -c set-bus-width sg5 0 16
610 primary [IOA]
612 Set the adapter as the preferred primary adapter. This is
613 used in dual initiator RAID configurations to indicate
614 which adapter should be the primary adapter. The primary
615 adapter should be the adapter receiving the majority of
616 the I/O. Example:
617 iprconfig -c primary sg5
618 secondary [IOA]
620 Set the adapter to indicate it is not the preferred pri‐
621 mary adapter. See the notes for the preferred primary for
622 additional information. Example:
623 iprconfig -c secondary sg5
624 set-all-primary
626 Set all attached ipr adapters as the preferred primary
627 adapter. This can be used when running a dual initiator
628 RAID HA configuration. This command can be run on the
629 primary system to quickly enable the preferred primary
630 mode for all attached adapters. Refer to
631 /etc/ha.d/resource.d/iprha for an example of how this
632 might be used. Example:
633 iprconfig -c set-all-primary
634 set-all-secondary
636 Set all attached ipr adapters to indicate they are not
637 the preferred primary adapter. Example:
638 iprconfig -c set-all-secondary
639 query-ha-mode [IOA]
641 When an adapter is configured in a highly available dual
642 adapter configuration, it may be able to be configured in
643 one of two ways. The default mode is Normal. This mode
644 is used for all SCSI adapters and many SAS adapters.
645 Some SAS adapters also support a JBOD dual adapter con‐
646 figuration. This mode is to be used when the dual adapter
647 configuration is to consist of JBOD disks rather than
648 RAID arrays. If the adapter is NOT going to be used in a
649 dual adapter configuration, this mode MUST be set to Nor‐
650 mal. Example:
651 iprconfig -c query-ha-mode sg5
652 set-ha-mode [IOA] [Normal | RAID]
654 Used to set the high-availability mode of the adapter.
655 Refer to the query-ha-mode command for more information
656 regarding these settings. Example:
657 iprconfig -c set-ha-mode sg5 Normal
658 set-array-asymmetric-access-mode [array] [Optimized | Non-Opti‐
660 mized]
661 Used to set the asymmetric access mode of the disk array.
662 Example:
663 iprconfig -c set-array-asymmetric-access-mode sda Opti‐
664 mized
665 set-ioa-asymmetric-access-mode [IOA] [Enabled | Disabled]
667 Used to set the asymmetric access mode of the IOA.
668 Example:
669 iprconfig -c set-ioa-asymmetric-access-mode sg5 Enabled
670 set-ioa-caching [IOA] [Default | Disabled]
672 Used to set the requested caching mode of the IOA.
673 Example:
674 iprconfig -c set-ioa-caching sg5 Disabled
675 set-array-rebuild-verify [IOA] [enable | disable | default]
677 Used to define whether to perform verification during an
678 array rebuild. Enabling this can affect performance.
679 The default value is disabled.
680 Example:
681 iprconfig -c set-array-rebuild-rate sg5 disable
682 set-array-rebuild-rate [IOA] [Rebuild Rate | default]
684 Used to set the rebuilt rate ratio of the IOA. [Rebuild
685 Rate] must be in range 10..100. If 'default' is used, the
686 IOA will reset to the implementation default rate. The
687 value actually configured may not be the exact rate con‐
688 figured by the user, but an approximation to the closest
689 rate supported by the IOA.
690 Example:
691 iprconfig -c set-array-rebuild-rate sg5 10
692 get-live-dump [IOA]
694 Dump the IOA's implementation unique critical informa‐
695 tion. The dump data will be saved in the /var/log/ direc‐
696 tory with the pattern ipr-CCIN-PCI_ADDRESS-dump-TIME‐
697 STAMP.
698 Example:
699 iprconfig -c get-live-dump sg5
700 dump Display detailed hardware and system information on stan‐
702 dard output. In case a report file is needed, the iprsos
703 command will create one at /var/log/iprsos.log.
704 Example:
705 iprconfig -c dump
706 --version
708 Print version number of iprconfig
709 --debug
711 Enable additional error logging. Enabling this will result in
712 additional errors logging to /var/log/messages.
713 --force
715 Disable safety checks. Use this to disable safety checks in
716 iprconfig. This will allow you to format devices that are not
717 at the appropriate code levels. Only use this option if you
718 really know what you are doing.
719
721 Brian King <brking@us.ibm.com>
722
724 Notes on using under iSeries 5250 telnet
725 Only use this utility across 5250 telnet when there are no other
727 options available to you. Since there may be occasions when 5250 telnet
728 is your only option to access your iSeries Linux console, every attempt
729 has been made to make this utility usable under 5250 telnet. By follow‐
730 ing a few guidelines, you can make your 5250 telnet experience more
731 productive and much less frustrating.
732 1. First of all, it will be helpful to know how the keys are mapped
734 under 5250 telnet. From the 5250 telnet window, hit ESC. This will get
735 you to the Send TELNET Control Functions menu. Take option 6 to display
736 the keyboard map. Take note of how TAB, ESC, CTLC, and SENDWOCR are
737 bound. They will be useful in the future.
738 2. When selecting menu options, enter the menu number, followed by the
740 enter key, same as usual.
741 3. When typing single character commands (eg. r=Refresh), type the sin‐
743 gle character followed by the SENDWOCR key (F11 by default).
744 4. When on a device/array/IOA selection screen (eg. Display Disk Unit
746 Details), do NOT use the arrow keys to navigate. Instead use the TAB
747 key (F7 by default) to navigate these screens.
748 5. Beware of the backspace and delete keys. As a rule do NOT use them.
750 6. When editing the root kernel message log directory or the default
752 editor, you may use the arrow keys, but not the backspace and delete
753 keys. Use the space bar to remove already typed characters.
754 August 2009 IPRCONFIG(8)