Attachment point identifier; an ap-id specifies the type and location of the attachment point in the system and is unambiguous. There are two types of identifier: physical and logical. A physical identifier contains a fully specified path name, while a logical identifier contains a shorthand notation.
A collective term for a board and its card cage slot. A physical attachment point describes the software driver and location of the card cage slot. A logical attachment point is an abbreviated name created by the system to reference the physical attachment point.
cfgadm is the primary command for dynamic reconfiguration on the Sun Fire Entry-Level Midrange Systems system. For information about the command and its options, see the cfgadm(1M), cfgadm_sbd(1M), and cfgadm_pci(1M) man pages. For any late-breaking news about this and related commands, see the Solaris 8 section at the DR web site. See Chapter 12.
Capacity on Demand (COD)
Capacity on Demand (COD) is an option that provides additional processing resources (CPUs) when you need them. These additional CPUs are provided on COD CPU/Memory boards that are installed in Sun Fire entry-level midrange systems. You can access the COD CPUs after you purchase the COD right-to-use (RTU) licenses for them.
The operational status of an attachment point.
The operating system assigns functional roles to a board and loads device drivers for the board and for devices attached to the board.
The collection of attached devices known to the system. The system cannot use a physical device until the configuration is updated. The operating system assigns functional roles to a board and loads device drivers for the board and for devices attached to the board.
A board is present in a slot and is electrically connected. The temperature of the slot is monitored by the system.
The device driver supports DDI_DETACH and the device (such as an I/O board or a SCSI chain) is physically arranged so that it can be detached.
The system stops monitoring the board and power to the slot is turned off. A board in this state can be unplugged.
See Dynamic Reconfiguration.
Dynamic Reconfiguration (DR) software allows the administrator to (1) view a system configuration; (2) suspend or restart operations involving a port, storage device, or board; and (3) reconfigure the system (detach or attach hot-swappable devices such as disk drives or interface boards) without the need to power down the system. When DR is used with IPMP or Solstice DiskSuite software (and redundant hardware), the server can continue to communicate with disk drives and networks without interruption while a service provider replaces an existing device or installs a new device. DR supports replacement of a CPU/Memory board, provided the memory on the board is not interleaved with memory on other boards in the system.
Hot-plug boards and modules have special connectors that supply electrical power to the board or module before the data pins make contact. Boards and devices that do not have hot-plug connectors cannot be inserted or removed while the system is running.
A hot-swap device has special DC power connectors and logic circuitry that allow the device to be inserted without the necessity of turning off the system.
instant access CPUs
Unlicensed COD CPUs on COD CPU/Memory boards installed in Sun Fire entry-level midrange systems. You can access up to a maximum of four COD CPUs for immediate use while you are purchasing the COD right-to-use (RTU) licenses for the COD CPUs. Also referred to as headroom.
IP Multipathing (IPMP)
Internet Protocol multipathing. Enables continuous application availability by load balancing failures when multiple network interface cards are attached to a system. If a failure occurs in a network adapter, and if an alternate adapter is connected to the same IP link, the system switches all the network accesses from the failed adapter to the alternate adapter. When multiple network adapters are connected to the same IP link, any increases in network traffic are spread across multiple network adapters, which improves network throughput.
A DR operation in which hardware is not physically added or removed. An example is the deactivation of a failed board that is then left in the slot (to avoid changing the flow of cooling air) until a replacement is available.
Hardware resource such as a system board or a disk drive that occupies a DR receptacle or slot.
A specific Sun Fire system model, such as the Sun Fire entry-level midrange systems.
A DR operation that involves the physical addition or removal of a board. See also "Logical DR."
A brief pause in the operating system to allow an unconfigure and disconnect operation on a system board with non-pageable OpenBoot PROM (OBP) or kernel memory. All operating system and device activity on the backplane must cease for a few seconds during a critical phase of the operation.
A board connector.
A receiver such as a board slot or SCSI chain.
Simple Network Management Protocol. SNMP is any system listening to SNMP events.
The operational status of either a receptacle (slot) or an occupant (board).
To be suitable for DR, a device driver must have the ability to stop user threads, execute the DDI_SUSPEND call, stop the clock, and stop the CPUs.
A suspend-safe device is one that does not access memory or interrupt the system while the operating system is in quiescence. A driver is considered suspend-safe if it supports operating system quiescence (suspend/resume). It also guarantees that when a suspend request is successfully completed, the device that the driver manages will not attempt to access memory, even if the device is open when the suspend request is made.
A suspend-unsafe device is one that allows a memory access or a system interruption while the operating system is in quiescence.
The main application that performs all of the SC hardware management functions.
The system detaches a board logically from the operating system and takes the associated device drivers off-line. Environmental monitoring continues, but any devices on the board are not available for system use.