1-6 instant Capacity on Demand Notes for Installation and Use
This command untars the kit to a subdirectory (CODBASE520) in the
current directory.
3. Install the iCAP kit using setld(8) with the following command:
# /usr/sbin/setld -l download_directory_name/CODBASE520 CODBASE520
Note that in the previous example, download_directory_name is the path to
the subdirectory where you downloaded the kit and the revision number of
the iCoD software product is 520. This revision number may increase for
later versions.
4.
Verify the iCAP installation with the command:
# /usr/sbin/setld -i | grep COD
3.0 Configuring iCAP
You must include as active CPUs the primary CPU, and either the CPUs
responsible for managing hardware interrupts, or the CPUs being used by one
or more applications, or both when configuring iCAP.
For ES47, ES80 and GS1280, an inactive iCAP CPU cannot be connected to
either internal I/O (ES47 & ES80) or an external I/O Building Block Drawer.
1. ES47 & ES80: One CPU on the iCAP Dual CPU Building Block Module
must remain active, and the active CPU must be the one connected to the
internal I/O. The inactive iCAP CPU cannot be connected to an external I/O
Building Block Drawer.
2. GS1280: Neither CPU on the iCAP Dual CPU Building Block Module can be
connected to an external I/O Building Block Drawer.
Perform these steps to configure iCAP:
1. Display the list of CPUs that must remain on line and the list of available
CPUs before configuring iCAP with the command:
# /usr/sbin/codconfig –show
2. Configure iCAP with the set of active CPUs initially purchased:
# /usr/sbin/codconfig cpu_id_list
Note: CPUs may be started (put on line) and stopped (put off line) as a
Kommentare zu diesen Handbüchern