3.1.2 Using the lspv
CommandWhen you add a new device to your system, or you need to configure devices that were not detected as available during the boot process, the system must have a way of configuring these devices. The cfgmgr command is used to configure devices and, optionally, install device software into the system. The devices to be configured are controlled by the Configuration Rules object class, which is part of the Device Configuration database. Each configuration rule specifies three items:
During system boot, the cfgmgr command configures all the devices that are necessary to use the system.
The cfgmgr command recognizes three phases of configuration rules:
During Phase 1, the cfgmgr command is invoked specifying this as Phase 1 by using the -f flag. The cfgmgr command runs all of the Phase 1 configuration rules, which results in the base devices being configured. After this, Phase 2 execution begins, and the cfgmgr command is called with the -s flag.
Normally, the cfgmgr command runs all the rules for the phase specified during invocation (Phase 1 rules for the -f flag). However, if the -l flag is used, the cfgmgr command configures only the named device and its children.
If the cfgmgr command is invoked without a phase option (for example, without the -f,-s, or -p flags), then the command runs the Phase 2 rules. The only way to run the Phase 3 rules is with the -p flag.
The configuration rules for each phase are ordered based on the values specified in the seq field. This field is an integer that specifies the priority in which to execute this rule relative to the other rules for this phase. The higher the number specified by the seq field, the lower the priority; for example, a value of 1 specified in the seq field is run before a rule with a value of 10. There is one exception: A seq field value of 0 implies a don't care condition, and any seq field value of 0 is executed last.
Therefore, a seq field value of 1 is the highest priority (first to run).
If there are any devices detected that have no device software installed when configuring devices, the cfgmgr command returns a warning message with the name or a list of possible names for the device package that must be installed. If the specific name of the device package is determined, it is displayed as the only package name on a line below the warning message. If the specific name cannot be determined, a colon-separated list of possible package names is displayed on a single line. A package name or list of possible package names is displayed for each of the devices if more than one device is detected without its device software.
An example is as follows:
cfgmgr: 0514-621 WARNING: The following device packages are
required for device support but are not currently
installed.
devices.pci.22100020
devices.pci.14101800
devices.pci.scsi:devices.pci.00100300:devices.pci.NCR.53C825
In this example, two devices were found whose software is missing, and the cfgmgr command displayed the names of the device packages that must be installed. A third device whose software is missing was also found but in this case, the cfgmgr command displays several possible device package names.
When more than one possible package name is identified for a device, typically only one of the names will actually correspond to a device package on the installation medium. This is the package to install. However, in some cases, more than one of the names will correspond to actual device packages on the installation medium. In this case, the first package name in the list, for which there is an actual device package on the installation medium, is the package that must be installed. If the cfgmgr command is used with the -i flag, then the correct packages will be installed.
If you invoke the cfgmgr command with the -i flag, the command
attempts to install device software automatically for each newly detected
device. The device variable of the -i flag specifies where to find the
installation medium. The installation medium can be a hardware device (such as
a tape or diskette drive), a directory that contains installation images, or
the installation image file itself. Some of the common flags used with the
cfgmgr command are provided in Table 11.
Table 11: cfgmgr Command Flags
The configuration rules used by the cfgmgr command are provided in
Table 12.
Table 12: cfgmgr Configuration Rules
The following examples are based on the configuration rules containing the following information:
phase seq rule 1 1 /usr/lib/methods/defsys 1 10 /usr/lib/methods/deflvm 2 1 /usr/lib/methods/defsys 2 5 /usr/lib/methods/ptynode 2 10 /usr/lib/methods/startlft 2 15 /usr/lib/methods/starttty 3 1 /usr/lib/methods/defsys 3 5 /usr/lib/methods/ptynode 3 10 /usr/lib/methods/startlft 3 15 /usr/lib/methods/starttty
When the cfgmgr command is invoked with the -f flag, the command gets all of the configuration rules with phase = 1 and runs them in the following order:
/usr/lib/methods/defsys /usr/lib/methods/deflvm
| Note |
|---|
When the cfgmgr command is run with the -s flag, the command gets all of the configuration rules with phase = 2 and runs them in the following order:
/usr/lib/methods/defsys /usr/lib/methods/ptynode /usr/lib/methods/startlft /usr/lib/methods/starttty
When the cfgmgr command is run with the -p 3 flag, the command gets all of the configuration rules with phase = 3 and runs them in the following order:
/usr/lib/methods/defsys /usr/lib/methods/ptynode /usr/lib/methods/startlft /usr/lib/methods/starttty
If the cfgmgr command is run without a flag, the command functions the same as when used with the -s flag. In order to configure detected devices attached to the SCSI0 adapter, use the cfgmgr command as follows:
cfgmgr -l scsi0
In order to install device software automatically during configuration (with the software contained in a directory), use the cfgmgr command as follows:
cfgmgr -i /usr/sys/inst.images
3.3 System Management
Services