ngdr(7d) (man pages section 7: Device and Network Interfaces)

man pages section 7: Device and Network Interfaces

ngdr(7d)

NAME | SYNOPSIS | DESCRIPTION | SEE ALSO

NAME

dr, drmach, ngdr, ngdrmach– Sun Enterprise 10000 and Sun Fire high-end server dynamic reconfiguration driver

SYNOPSIS

dr

drmach

ngdr

ngdrmach

DESCRIPTION

The dynamic reconfiguration (DR) driver consists of a platform-independent driver and a platform-specific module. The DR driver uses standard features of the Solaris operating environment whenever possible to control DR operations and calls the platform specific module as needed. The DR driver creates minor nodes in the file system that serve as attachment points for DR operations.

The DR driver provides a pseudo-driver interface to sequence attach and detach operations on system boards using file system entry points referred to as ”attachment points.” The form of the attachment point depends on the platform.

Sun Enterprise 10000 Server

On the Sun Enterprise 10000 server, the DR driver consists of a platform-independent driver (ngdr) and a platform-specific module (ngdrmach).

The domain configuration server (DCS) accepts DR requests from the system services processor (SSP) and uses the libcfgadm(3LIB) interface to initiate the DR operation. After the operation is performed, the results are returned to the SSP. For more information about the DCS on the Sun Enterprise 10000, refer to the dcs(1M) man page and the Sun Enterprise 10000 Dynamic Reconfiguration User Guide.

The DR driver creates physical attachment points for system board slots that takes the following form:

/devices/pseudo/ngdr@0:SBx

Where x represents the slot number (0 to 15) for a particular board.

The cfgadm_sbd(1M) plugin creates dynamic attachment points that refer to components on system boards, including CPUs, memory, or I/O devices. Refer to the cfgadm_sbd(1M) man page for more details.

Sun Fire High-End Systems

On Sun Fire high-end systems, the DR driver consists of a platform-independent driver (dr) and a platform-specific module (drmach).

The domain configuration server (DCS) accepts DR requests from the domain configuration agent (DCA) that runs on the Sun Fire high-end system controller. After the DCS accepts a DR request, it uses the libcfgadm(3LIB) interface to initiate the DR operation. After the operation is performed, the results are returned to the DCA. For more information about the DCS, refer to the dcs(1M) man page and the Sun Fire High End Systems Dynamic Reconfiguration User Guide. For more information about the DCA, refer to the System Management Services (SMS) Dynamic Reconfiguration User Guide.

The DR driver creates physical attachment points for system board slots that take one of the following forms:

/devices/pseudo/dr@0:SBx

/devices/pseudo/dr@0:IOx

Where x represents the expander number (0 to 17) for a particular board.

The cfgadm_sbd(1M) plugin creates dynamic attachment points. These attachment points refer to components on system boards, including CPUs, memory, or I/O devices. Refer to the cfgadm_sbd(1M) man page for more details.