Within the Purity//FA operating system architecture, dedicated NVRAM modules (used heavily in standard non-DFMD arrays to provide non-volatile write caching) are fundamentally treated as specialized drives by the software layer. They are physically installed into specific central chassis bays labeled NVB0, NVB1, NVB2, and NVB3.
Because they are classified as drive components, the primary and most direct command an Implementation Engineer should use to verify their physical installation, health, capacity, and update status is puredrive list. When this command is executed via the CLI, it generates a comprehensive table detailing every DirectFlash Module (DFM) and NVRAM module currently seated in the chassis.
The output explicitly shows the slot location (e.g., CH0.NVB0), the component's operational status (healthy, empty, evacuating, or updating), and its specific firmware version. While the purehw list command is excellent for viewing broader chassis components (like fans, temperature sensors, and controllers), puredrive list is the purpose-built command required to monitor the precise synchronization and firmware update phases of the NVRAM modules, especially crucial during a non-disruptive upgrade (NDU) when ensuring cache mirror integrity is paramount.
