Dell PERC13 and PERC12 User’s Guide PERC H975 Series and PERC H965 Series cards
- Notes, cautions, and warnings
- Dell PERC13 and PERC12 series cards
- Features of PERC H975i Front
- Features of PERC H965i Adapter
- Features of PERC H965i Front
- Features of PERC H965i Front (supported on 17G)
- Features of PERC H965e Adapter
- Features of PERC H965i MX
- Technical specifications of PERC12 and PERC13 cards
- Operating systems supported by PERC12 Series and PERC13 Series cards
- Applications and User Interfaces supported by PERC13 and PERC12
- PERC features
- Controller features
- PCIe Multi-Function or Multi-Device
- Hardware Root of Trust
- Security Protocol and Data Model (SPDM)
- Device enumeration
- UEFI Secure Boot
- Auto-Configure Behavior (Execute Once)
- Auto-Configure Behavior (Primary and Secondary settings)
- Drive Performance Monitoring (DPM)
- Disk roaming
- Hardware Accelerated I/O
- Non–RAID disks
- Physical disk power management
- Firmware update
- Snapdump
- Physical disk coercion
- PERC H965e support for PowerVault MD24XX enclosure
- Virtual disk features
- Virtual disk initialization
- Background operations
- Drive features
- Fault tolerance
- Controller features
- Install and remove a PERC13 and PERC12 card
- Before working inside your system
- Safety instructions
- Remove the PERC H975i Front card from a PowerEdge R770 (2U) server
- Install the PERC H975i Front card into a PowerEdge R770 (2U) server
- Remove the PERC H975i Front module from a PowerEdge R670 (1U) server
- Install the PERC H975i Front module into a PowerEdge R670 (1U) server
- Remove the PERC H965i Adapter
- Install the PERC H965i Adapter
- Remove the PERC H965i Front card
- Install the PERC H965i Front card
- Remove PERC H965i MX
- Install PERC H965i MX
- Removing the PERC H965e Adapter card
- Installing the PERC H965e Adapter card
- Drivers supported by PERC cards
- Manage the controller firmware
- Manage PERCs using HII Configuration Utility
- Start the PERC HII Configuration Utility
- Exit the PERC HII Configuration Utility
- Navigate to the PERC Configuration Utility
- View the HII Configuration Utility dashboard
- Configuration management
- Controller management
- Save persistent events
- Clear persistent events
- Manage snapdump
- Enable security
- Disable security
- Change security settings
- Restore factory default settings
- Manage the SAS Storage link speed
- Manage the PCIe storage interface
- Auto-Configure Behavior Management
- Advanced controller properties
- Virtual disk management
- Device management
- Hardware components
- Security key management in HII configuration utility
- Security key and RAID management
- Security key implementation
- Local Key Management
- Create a security key
- Change security settings
- Disable security key
- Create a secured virtual disk
- Secure a non-RAID disk
- Secure a pre-existing virtual disk
- Import a secured non-RAID disk
- Import a secured virtual disk
- Dell Technologies OpenManage Secure Enterprise Key Manager (SEKM)
- Supported controllers for OpenManage Secure Enterprise Key Manager (SEKM)
- Manage the Server Enterprise Key Manager (SEKM) feature
- Disable the Secure Enterprise Key Manager (SEKM) feature
- Manage virtual disks in the SEKM mode
- Manage non–RAID disks in the SEKM mode
- Transition of drives from Local Key Management to Secure Enterprise Key Management
- Troubleshoot PERC issues
- Unable to import the VD for 120 s after recently removing the VD
- Observed a controller fault while updating the controller firmware when using Linux operating system
- Virtual drive Blink and Unblink operations are unavailable in iDRAC UI and HII
- Samsung PM893 and Samsung PM897 SATA SSDs are not supported on PERC12 firmware versions earlier than 8.8.0.0.18-26
- The SMART data of SATA SSDs is unavailable from iDRAC
- The default HDD cache policy is not updated to support the read-ahead operation
- Firmware downgrade operation may fail if the firmware version downgraded to does not have the supported feature set
- Unable to downgrade the firmware version of PERC12 to an older revision
- When secured drives are hot-removed or hot-inserted in the server, iDRAC doesn't generate the PD Unlock event
- During a Key Exchange Failure scenario in SEKM mode, native locked drives are Identified as "Locked with Foreign Key" in all interfaces
- After importing the foreign configuration of the associated global hot spare drive on a PERC12 series controller, the drive is still reported as both Online and global hot spare
- LED Operations using ESXCLI Commands for H965 Series controller is unavailable using VMware ESXi operating system
- Backplane slot count may be reported as 32 if there is an error with the backplane during discovery or runtime
- Single virtual disk performance or latency in hypervisor configurations
- Unable to discover or detect a PERC card
- Unable to install the Microsoft Windows operating system
- Only UEFI is supported and not BIOS
- A fault firmware state is detected
- Foreign configuration not found in HII
- Degraded state of virtual disks
- Boot-time errors
- Event log errors
- Application issues
- Memory errors
- Preserved Cache state
- Security key errors
- General issues
- PERC goes into Safe and Unresponsive state
- Enclosure state is indicated as faulty instead of need attention
- perccli2 commands and OS DUPs must have the controller host driver 8.0.0.69.0 for proper functioning
- PERC card has yellow bang in Windows operating system device manager
- PERC card not seen in operating systems
- Unlocked drives if not imported appear as locked
- Physical disk issues
- Lifecycle log indicates drive number as unknown
- An NVMe drive is not indicated as unsupported when EEDP is enabled
- Unexpected generation of incorrect physical AEN
- Unconfigured drives are not listed in the OS or Hardware Diagnostics
- Physical disk in failed state
- The PDR6 Error and Event message is saved in the log data when a new drive is inserted
- Unable to rebuild a fault tolerant virtual disk
- An NVMe drive is indicated as faulty when moving the drive to new backplane using hot-insertion
- Fatal error or data corruption reported
- Multiple disks are inaccessible
- Rebuilding data for a failed physical disk
- Virtual disk fails during rebuild using a global hot-spare
- Dedicated hot-spare disk fails during rebuild
- Virtual disk fails rebuild using a dedicated hot spare
- Physical disk takes a long time to rebuild
- Drive removal and insertion in the same slot generates a foreign configuration event
- SMART errors
- Replace member errors
- Linux operating system errors
- Drive indicator codes
- The Auto-Secure feature is not supported
- HII error messages
- Appendix—RAID description
- Getting help
- Documentation resources
Loading, Please wait
Hardware Root of Trust
Hardware Root of Trust (RoT) builds a chain of trust by authenticating all the firmware components prior to its execution and permits only the authenticated firmware to be installed and upgraded. The controller boots from an Internal Boot ROM (IBR) that establishes the initial RoT and this process authenticates and builds a chain of trust with succeeding software using this RoT.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\