Note: The information contained in this article is structured as help information for the System Management Interface Tool (SMIT) and is not intended for general reading.
Select the desired type of device from the list of predefined device types. Information about the device is presented in three columns: device type, device subclass or interface, and device description.
Select the desired device from the list. Information about the device is presented in four columns: device name, device state, device location code, and device description.
When adding a device, the device is defined and configured in the Customized database. You can also set attributes when adding a device.
When adding a device, the device is defined and configured in the Customized database. You can also set attributes when adding a device.
When adding a device, the device is defined and configured in the Customized database. You can also set attributes when adding a device.
When adding a device, the device is defined and configured in the Customized database. You can also set attributes when adding a device.
When adding a device, the device is defined and configured in the Customized database. You can also set attributes when adding a device.
When adding a device, the device is defined and configured in the Customized database. You can also set attributes when adding a device.
When adding a device, the device is defined and configured in the Customized database. You can also set attributes when adding a device.
When adding a device, the device is defined and configured in the Customized database. You can also set attributes when adding a device.
Change one or more attributes for a specific device.
When deleting a device, you can make the device unavailable, but still defined, or remove the device definition from the Customized database.
When deleting a device, you can make the device unavailable, but still defined, or remove the device definition from the Customized database.
You can move a device. When you move a device, the device retains its characteristics in the Customized database.
You can move a device. When you move a device, the device retains its characteristics in the Customized database.
You can move a device. When you move a device, the device retains its characteristics in the Customized database.
Select the adapter to which the desired device is attached or will be attached. The possible adapters are presented in a list with four columns of information: adapter device name, adapter state, adapter location code, and adapter description.
Select the parent device to which the new device it to be attached.
Select the desired mode of operation for which the selected 5085/86/88 Attachment adapter is to be configured. There are two choices: gsw, indicating 5085/86 mode, or hia, indicating System/370 Host Interface Adapter (5088).
Selects the device class that includes the device for which characteristics are to be displayed.
Selects the desired device interface. This is the same as the device subclass in the device configuration database. Only the interfaces supported within the previously selected device class are displayed.
Selects the desired device type. Only the types within the previously selected device class and interface are displayed.
Lists supported devices, defined devices, or the characteristics of a particular device.
When a device is defined, the device instance is recorded in the Customized Configuration Database. All of the device's attributes, plus connection and location information, are known and recorded, but the device cannot be used by the operating system. After you configure a device, the device is said to be available. When listing defined devices, the information is presented in four columns: device name, status (indicating whether a device is available or just defined), location code, and device description.
When a device is defined, the device instance is recorded in the Customized Configuration Database. All of the device's attributes, plus connection and location information, are known and recorded, but the device cannot be used by the operating system. After you configure a device, the device is said to be available. When listing defined devices, the information is presented in four columns: device name, status (indicating whether a device is available or just defined), location code, and device description.
When a device is defined, the device instance is recorded in the Customized Configuration Database. All of the device's attributes, plus connection and location information, are known and recorded, but the device cannot be used by the operating system. After you configure a device, the device is said to be available. When listing defined devices, the information is presented in four columns: device name, status (indicating whether a device is available or just defined), location code, and device description.
When a device is defined, the device instance is recorded in the Customized Configuration Database. All of the device's attributes, plus connection and location information, are known and recorded, but the device cannot be used by the operating system. After you configure a device, the device is said to be available. When listing defined devices, the information is presented in four columns: device name, status (indicating whether a device is available or just defined), location code, and device description.
When a device is defined, the device instance is recorded in the Customized Configuration Database. All of the device's attributes, plus connection and location information, are known and recorded, but the device cannot be used by the operating system. After you configure a device, the device is said to be available. When listing defined devices, the information is presented in four columns: device name, status (indicating whether a device is available or just defined), location code, and device description.
When a device is defined, the device instance is recorded in the Customized Configuration Database. All of the device's attributes, plus connection and location information, are known and recorded, but the device cannot be used by the operating system. After you configure a device, the device is said to be available. When listing defined devices, the information is presented in four columns: device name, status (indicating whether a device is available or just defined), location code, and device description.
When a device is defined, the device instance is recorded in the Customized Configuration Database. All of the device's attributes, plus connection and location information, are known and recorded, but the device cannot be used by the operating system. After you configure a device, the device is said to be available. When listing defined devices, the information is presented in four columns: device name, status (indicating whether a device is available or just defined), location code, and device description.
When a device is defined, the device instance is recorded in the Customized Configuration Database. All of the device's attributes, plus connection and location information, are known and recorded, but the device cannot be used by the operating system. After you configure a device, the device is said to be available. When listing defined devices, the information is presented in four columns: device name, status (indicating whether a device is available or just defined), location code, and device description.
Defined devices are recorded in the Customized Configuration Database. All of the device's attributes, connection, and location information are known and recorded. When displaying characteristics, a list including device name, device description, status, and location code is displayed. If the defined device has attributes, two columns are displayed. The first column shows the attribute description and the second shows the current attribute values.
Supported devices are listed in the Predefined Configuration Database. These devices cannot be used by the operating system until they are defined and configured in the Customized Configuration Database. When listing supported devices, the information is presented in columns consisting of device class, device type, device subclass or interface, and device description. Device class is not shown when listing the supported devices for a specific class.
Supported devices are listed in the Predefined Configuration Database. These devices cannot be used by the operating system until they are defined and configured in the Customized Configuration Database. When listing supported devices, the information is presented in columns consisting of device class, device type, device subclass or interface, and device description. Device class is not shown when listing the supported devices for a specific class.
Supported devices are listed in the Predefined Configuration Database. These devices cannot be used by the operating system until they are defined and configured in the Customized Configuration Database. When listing supported devices, the information is presented in columns consisting of device class, device type, device subclass or interface, and device description. Device class is not shown when listing the supported devices for a specific class.
Supported devices are listed in the Predefined Configuration Database. These devices cannot be used by the operating system until they are defined and configured in the Customized Configuration Database. When listing supported devices, the information is presented in columns consisting of device class, device type, device subclass or interface, and device description. Device class is not shown when listing the supported devices for a specific class.
Supported devices are listed in the Predefined Configuration Database. These devices cannot be used by the operating system until they are defined and configured in the Customized Configuration Database. When listing supported devices, the information is presented in columns consisting of device class, device type, device subclass or interface, and device description. Device class is not shown when listing the supported devices for a specific class.
Supported devices are listed in the Predefined Configuration Database. These devices are not usable by the operating system until they are defined and configured in the Customized Configuration Database. When listing supported devices, the information is presented in columns consisting of device class, device type, device subclass or interface, and device description. Device class is not shown when listing the supported devices for a specific class.
Configures devices added to the system or powered on after the last system boot by running the configuration manager (cfgmgr). This option should be used when devices are added to the system or external devices are powered on after the system is booted. Such devices are not usable by the operating system until they are defined and configured in the Customized Devices Configuration database.
Some devices, such as printers, are not software detectable and must be configured using the devices specific SMIT options.
Note: If you unplug a mouse, tablet, or keyboard, the device becomes inactive. If the mouse, tablet, or keyboard is reconnected, it will remain inactive until the next system reboot. Configure Devices Added after IPL will not make these devices available.
This option can also be used for the installation of device software for new devices added to the system (either before or after the last system reboot). In this case, the device will be configured after the software is installed.
Configures devices added to the system or powered on after the last system boot by running the configuration manager (cfgmgr). This option should be used when devices are added to the system or external devices are powered on after the system is booted. Such devices are not usable by the operating system until they are defined and configured in the Customized Devices Configuration database.
Some devices, such as printers, are not software detectable and must be configured using the devices specific SMIT options.
Note: If you unplug a mouse, tablet, or keyboard, the device becomes inactive. If the mouse, tablet, or keyboard is reconnected, it will remain inactive until the next system reboot. Configure Devices Added after IPL will not make these devices available.
This option can also be used for the installation of device software for new devices added to the system (either before or after the last system reboot). In this case, the device will be configured after the software is installed.
Specifies the input device or directory that is the source of the software you are installing. The input device can be a tape drive, diskette drive, or a directory. Selecting none configures devices added after IPL without the installation of software.
Supported devices are listed in the Predefined Configuration Database. These devices are not usable by the operating system until they are defined and configured in the Customized Configuration Database. When displaying characteristics, a device description is listed. If the supported device has attributes, two columns are displayed. The first column shows the attribute description and the second shows the attribute default value.
Indicates whether the configuration changes being made should be applied only to the database or to both the database and the current device operation. For devices that are in use and cannot be changed, this option allows the database to be changed for the device so that the changes take effect the next time the system is started.
Indicates whether a device's definition is to be retained in the Configuration Database. Setting this field to yes makes the device unavailable and, therefore, unusable, but the device remains defined. This option allows the device to be made available again with the same attributes it had before. Setting this field to no makes the device unavailable and deletes the device definition from the database.
Indicates whether a device's definition is to be retained in the Configuration Database. Setting this field to yes makes the device unavailable and, therefore, unusable, but the device remains defined. This option allows the device to be made available again with the same attributes it had before. Setting this field to no makes the device unavailable and deletes the device definition from the database.
Makes a defined device available for use by the operating system.
Makes a defined device available for use by the operating system.
Makes a defined device available for use by the operating system.
Makes a defined device available for use by the operating system.
Makes a defined device available for use by the operating system.
Makes a defined device available for use by the operating system.
Makes a defined device available for use by the operating system.
Makes a defined device available for use by the operating system.
Makes a defined device available for use by the operating system.
Makes a defined device available for use by the operating system.
Configures devices by running the programs specified in the Configuration Rules Object Class.
Suppose you have both a tty device and a printer and each alternately uses the same tty connector. In your device configuration database, you have both a tty device and printer defined on the same parent and port. However, you can only configure one at a time. When you unconfigure the printer, the specific setup information would be retained until the next time you configure it, because the device was not removed, but was merely brought from the available state down to the defined state.
Suppose you have both a tty device and a printer and each alternately uses the same tty connector. In your device configuration database, you have both a tty device and printer defined on the same parent and port. However, you can only configure one at a time. When you unconfigure the printer, the specific setup information would be retained until the next time you configure it, because the device was not removed, but was merely brought from the available state down to the defined state.
Suppose you have both a tty device and a printer and each alternately uses the same tty connector. In your device configuration database, you have both a tty device and printer defined on the same parent and port. However, you can only configure one at a time. When you unconfigure the printer, the specific setup information would be retained until the next time you configure it, because the device was not removed, but was merely brought from the available state down to the defined state.
Suppose you have both a tty device and a printer and each alternately uses the same tty connector. In your device configuration database, you have both a tty device and printer defined on the same parent and port. However, you can only configure one at a time. When you unconfigure the printer, the specific setup information would be retained until the next time you configure it, because the device was not removed, but was merely brought from the available state down to the defined state.
Suppose you have both a tty device and a printer and each alternately uses the same tty connector. In your device configuration database, you have both a tty device and printer defined on the same parent and port. However, you can only configure one at a time. When you unconfigure the printer, the specific setup information would be retained until the next time you configure it, because the device was not removed, but was merely brought from the available state down to the defined state.
Suppose you have both a tty device and a printer and each alternately uses the same tty connector. In your device configuration database, you have both a tty device and printer defined on the same parent and port. However, you can only configure one at a time. When you unconfigure the printer, the specific setup information would be retained until the next time you configure it, because the device was not removed, but was merely brought from the available state down to the defined state.
Allows you to selectively install some or all of the individual device software packages that exist on the installation media (or directory).
Specifies the software option you want to install.
To view a list of the software from the selected input device, press F4. The list displays the software available for installation. You then select the software option you want to install from the list.
On the software name list, use the following keys to select software to install. Use the arrow cursor keys to scroll through the list one line at a time. Use the Page Up or Page Down keys to view the list one page at a time. Use F7 to select an option for installation. Once an option has been selected, you can use F7 to deselect it.
Click the Need to add device software before adding device button if you want the system to install the necessary device software before adding the device to the system. Specify the source of the software in the Install media directory field.
If this option is not selected, the system will configure devices added after IPL without installing the device software.
Specifies the input device or directory that is the source of the software you are installing. The input device can be a tape drive, diskette drive, CD-ROM drive or a directory.
Specifies which SCSI bus modes will restrict data transfers to narrow width (8-bit) if both an internal and external cable are attached to the same SCSI bus.
Devices are usually allowed to attempt wide data (16-bit) transfers. However, there is a problem with a 16-bit device terminating one side of the bus and an 8-bit device terminating the other side. The adapter cannot sense the width of the cable, so the full 16-bits are not terminated on the 8-bit end. To resolve this problem, data transfers will be limited to only 8-bits when both an internal and external cable are attached to the same SCSI bus.
You can choose one of the following bus modes to enforce this restriction:
| None | Always allow 16-bit transfers |
| SE | Restrict the transfers when running in single-ended mode and both an internal and external cable are attached to the same SCSI bus. Low voltage differential is not restricted. |
| LVD/SE | Always restrict the data transfer width if both an internal and external cable are attached to the same SCSI bus. It does not matter if the bus is operating in low voltage differential or single-ended mode. |
The device driver supports a transmit queue that you configure. You can configure it with values of 16, 32, 64, 128, and 256. The default is 256.
The device driver supports a receive queue that you configure. You can configure it with values of 16, 32, 64, 128, and 256. The default is 256.
The device driver supports a receive buffer pool size that you configure. The buffer is the number of preallocated mbufs for receiving packets. The minimum size of the buffer is the receive queue size and the maximum size is 2K, with a default value of 384.
You can add, to the adapter, the MPQP COMIO interface emulation that is compatible with the Multiprotocol Quad Port (MPQP) device. You must configure emulation of the COMIO interface for each port of the adapter.
Adds a device driver to work with one of the available ports.
Type the port number.
Manages the MPQP Emulation Device Driver that operates on the IBM ARTIC960HX PCI adapter.
Type the logical name of the MPQP Emulation Device Driver.
Indicates the on-card CBMS pool size for the device driver (kn Kbytes).
Type the logical name of the port.
Configures and unconfigures specific devices defined in the Customized Devices Configuration database.
Unconfigures specific devices defined in the Customized Devices Configuration database. You can also unconfigure child devices and remove their device definitions from the database.
Configures specific devices defined in the Customized Devices Configuration database.
Identifies the logical name of the device you are unconfiguring.
Indicates that child devices are to be unconfigured prior to unconfiguring the selected device. Setting this field to yes makes all child devices, if any, unavailable along with the selected device. Setting this field to no applies the action only to the selected device. In this case, if the selected device has configured or available child devices, the unconfigure action will fail.
Indicates whether a device's definition is to be retained in the Configuration Database. Setting this field to yes makes the device unavailable and, therefore, unusable, but the device remains defined. This option allows the device to be made available again with the same attributes it had before. Setting this field to no makes the device unavailable and deletes the device definition from the database.
Identifies the logical name of the device you are configuring.
Use the options on this menu to list and identify PCI slots that support hot plug operations and to perform specific hot plug operations such add, remove, or replace a PCI hot plug adapter.
Lists all the PCI slots that support hot plug operations on this system and displays information about each slot such as whether the slot contains an adapter or is empty.
Allows you to physically replace or remove a PCI adapter from a PCI slot that supports hot plug operations. If you press a key other than Enter at the prompt, this operation is terminated and the state of the slot and connected devices remains unchanged.
Lists all the occupied hot plug slots and displays information about each slot. This allows you to determine where a specific PCI slot that supports hot plug operations is located.
Allows you to physically add a PCI adapter to a PCI slot that supports hot plug operations. If you press a key other than Enter at the prompt, this operation is terminated.
Select the PCI slot containing the PCI adapter that you want to remove or replace.
Indicates whether a replace or a remove hot plug operation is to be performed.
Select the PCI slot that you want to identify or locate.
Select the PCI slot to which you want to add a PCI adapter.
The unique ID associated with the VLAN driver. You can specify from 0 to 4094.
The priority of the packets associated with the VLAN driver. You can specify a value from 0-7, where 0 is the default priority. Priority 1 is the highest, followed by 2, followed by the default 0, and then in decreasing numerical order from 3 through 7.
The network adapter to which the VLAN device driver is connected. This adapter connects to the network.
Connects multiple physical LANs and segment physical LANs into different virtual LANs. Supports the IEEE 802.1Q standard. Implements the multiple VLAN ID capability outlined by the IEEE 802.1Q standard for Ethernet. You can enable VLAN for the Fast Ethernet and Gigabit Ethernet adapters.
The maximum number of LUNs (Logical Unit Numbers) at the SCSI ID of this device. This attribute should be set only for the device at LUN 0. Adjust the number to reflect the actual number of LUNs available at this SCSI ID. The maximum number of LUNs supported by SCSI-3 devices is 64 LUNs.
Some SCSI devices support a smaller number of LUNs. Setting the maximum number of LUNs to a value that is too large for some of these SCSI devices could result in multiple instances of a device being configured. Do not change this value without understanding the SCSI behavior of this device.
Limits the maximum speed in megabytes per second (MB/s) that the adapter SCSI bus can use. Speed is negotiated between the adapter and SCSI devices. The maximum negotiated speed cannot be greater than the maximum bus speed value. The values you can specify are 5, 10, 20, 40, 80, 160, and 320. The default value is 320.
To allow quick arbitration capability, select "Enable". All devices on the SCSI bus must support QAS or starvation can occur. The default is "Disable".
The size, in bytes, of the pool needed to map control structures and long term mapped buffers. The default value of 0x800000 is typically sufficient for I/O. You can increase the size if a large number of FCP (Fiber Channel Protocol) targets are attached or if the adapter is communicating with a high volume of IP addresses.
Enables or disables dynamic tracking. Select "yes" to enable dynamic tracking. Select "no", which is the default, to disable it.
When dynamic tracking of FC Devices is enabled, the FC adapter driver can detect when the Fiber Channel N_Port ID of a device changes and re-route traffic destined for that device to the new address while the devices are still online. Examples of events that can cause an N_Port ID to change are moving a cable between a switch and storage device from one switch port to another, connecting two separate switches via an Inter-Switch Link (ISL), and possibly rebooting a switch.
Select the error recovery method for FC fabric event errors:
If dynamic tracking is set to "no" and an RSCN for a remote device is received, the FC drivers will not recover if the SCSI ID of a device changes, and I/Os will take longer to fail when a link loss occurs between a remote storage port and switch. This situation only occurs on machines running earlier versions of AIX. However, this may be desirable in single-path situations if dynamic tracking support is not a requirement.
Enables FARP (Fiber Channel Address Resolution Protocol) to be used by the Fiber Channel TCP/IP protocol driver for address resolution. To enable FARP, select "yes". This is the default. To disable FARP, select "no". If FARP is disabled, ARP (Address Resolution Protocol) will be used.
The maximum number of receive buffers queued in the Fiber Channel adapter for the incoming TCP/IP networking packets. The default is 75. You can increase this number for better performance during heavy network traffic. However, having a large number of buffers reserved for IP over FC will limit the memory resources available for other operating system functions, which may negatively impact the system's performance.
When Data Verify is enabled, the IDE optical device driver will implement a read back and compare operation. For those IDE Controllers that have Data Verify as changeable, the default value is required to ensure data integrity across the path to the optical device.
In order to enable or disable Data Verify, the ODM Attribute data_verify of the IDE optical device's IDE controller must be changed. The data_verify ODM Attribute of the IDE controller will determine the Data Verify value for all IDE optical devices connected to it. The IDE optical device driver will retrieve the IDE controller's data_verify attribute when it is configured. In order to change Data verify for a IDE optical device, you must first change the data_verify attribute of it's IDE controller, and then reconfigure the IDE optical device.
PCI Bus Memory address mapping to adapter registers.
Enables or disables data transfers through Direct Memory Access (DMA).
Interrupt Priority for adapter.
PCI Bus Interrupt level for adapter.
PCI Bus I/O address mapping to adapter registers.
Indicates the type of I/O processor associated with this device.
Identifies the location of the adapter. The location code format is AA-BB-CC, where AA-BB is the location of the IDE Controller and CC is the specific IDE Channel.
Indicates whether CD-DA (CD-Digital Audio)format media is supported by this device.
Device index of this device, which, in IDE, is either 0 (Master) or 1 (Slave).
Indicates whether this drive supports IDE Self-Monitoring Analysis and Reporting Technology (SMART), which is a status-checking tool that monitors various attributes on the device for errors.
Indicates whether this device can use diagnostic commands to download new firmware (microcode) to this device.
Displays the storage capacity in megabytes of this device.
When data verify is enabled, the IDE optical device driver implements a read back and compare operation. For those IDE Controllers that have data verify as changeable, the default value is required to ensure data integrity across the path to the optical device. In order to change data verify for an IDE optical device, first change the data_verify attribute of it's IDE Controller, and then reconfigure the IDE optical device.
Used to determine when a VSCSI server adapter is no longer responding to I/O requests. You should enable this feature only if the devices on this client adapter are also available to this partition from another VSCSI client adapter. That is, if the "lspath" command shows multiple paths to these devices.
If no I/O requests have been serviced after VSCSI Path Timeout seconds, one more attempt will be made to contact the VSCSI server adapter, and if the VSCSI server adapter does not respond within 60 seconds, all outstanding I/O to the VIOS server adapter will be failed. If your VSCSI client adapter devices are configured with multiple paths, the I/Os should be resent down an alternative good path. If the device is not configured with multiple paths, the I/Os will be returned with errors to the application. If the device contains the "rootvg" for this partition and another path is not available, the partition may crash.
Careful consideration should be given when setting this value, keeping in mind when the VSCSI server adapter is servicing the I/O request, the storage the request is being sent to may be either local to the VIO Server or on a SAN.
This field should be set to 0, the default value, to disable the timeout feature, or to the time, in seconds, to wait before checking if the path to the server adapter has failed.
If the feature is enabled, a minimum setting of 30 seconds is required. If a value between 0 and 30 is entered, the field defaults to 30 upon the next adapter reconfiguation or reboot.
The new setting will not take affect until the adapter is reconfigured or the machine is rebooted.
The Link Initialization protocol is used the first time this FC adapter is opened. There are two settings for this attribute: Arbitrated Loop and Switch (al) and point-to-point only (pt2pt).
When set to Arbitrated Loop and Switch (al), this adapter first attempts to connect in switch/point-to-point mode. If the initialization attempt is unsuccessful, the adapter falls back and attempts to connect in Arbitrated Loop mode. If that fails then the link remains down.
When set to point-to-point only (pt2pt), this adapter first attempts to connect in switch/point-to-point mode, also known as Old Port mode. If the initialization attempt fails, then the link remains down.
Note that "pt2pt" mode will never succeed in a case where "al" mode fails.
Do not change this attribute unless directed by IBM support.
Specifies the desired link speed, in gigabytes per second, for data transmission to and from the device.
Some devices operate at specific link speeds only, in which case it is best to leave this field at its default setting, "auto", to allow the firmware to auto-negotiate a link speed that is acceptable to both the adapter and the device. If the attached device lacks the ability to auto-negotiate link speed, set this field to a specific link speed based on the device's documentation.