![](https://pdfstore-manualsonline.prod.a.ki/pdfasset/0/a5/0a5663ab-15e2-4e2c-926f-076e6f549524/0a5663ab-15e2-4e2c-926f-076e6f549524-bg6e.png)
78 SPARC Enterprise Mx000 Servers Administration Guide • November 2007
These sections provide details:
■ COD Boards
■ COD License Purchase
■ License Installation
■ License Allocation
■ Headroom Management
■ License Violations
COD Boards
A COD board is a system board that has been configured at the factory for COD
capability. COD boards come in the same configurations as standard system boards.
The number of CPUs per COD board depends on the configuration of your server.
COD boards are subject to the same limitations for mixed architectures and CPU
speeds as system boards. Likewise, COD board software requirements, such as the
Solaris OS or OpenBoot PROM version, are the same as those of system boards. Your
server can have any combination of COD and system boards. It can even be
configured entirely with COD boards.
Once a COD board has been licensed, you can configure it into domains in the same
way as a system board. Until it has been activated (using licenses or headroom),
however, you cannot configure it into a domain.
COD boards are identified by a special field-replaceable unit (FRU) ID and by a
COD label. Except for their FRU ID, label, and COD capability, once COD boards are
licensed, they are handled by the rest of the hardware and software in exactly the
same way as system boards. COD boards fully support dynamic reconfiguration
operations.
You can order COD boards either when you order your server, in which case they
arrive already installed, or as an option. The SPARC Enterprise M4000 and M5000
servers cannot add option COD boards after shipment from the factory; COD
capability for these two servers must be ordered with the server.
For more information about COD boards and replacing COD boards (field-
replaceable units, or FRUs) in your server, see the COD User’s Guide and the Service
Manual.