- Notes, cautions, and warnings
- Overview
- Accessing the command prompt
- Working with the PERC Command Line Interface tool
- System commands
- Controller commands
- Drive commands
- Virtual drives commands
- Add virtual drives commands
- Delete virtual drives commands
- Delete Non-RAID disks
- Virtual drive show commands
- Preserved cache commands
- Change virtual drive properties commands
- Virtual drive initialization commands
- Virtual drive erase commands
- Virtual drive migration commands
- Virtual drive consistency check commands
- Background initialization commands
- Virtual drive expansion commands
- Foreign configurations commands
- BIOS-related commands
- Drive group commands
- BBU commands
- Enclosure commands
- PHY commands
- Logging commands
- PERC CLI command examples
- Getting a complete list of CLI commands
- Checking controller availability
- Viewing controllers
- Viewing free space information
- Viewing disk1 information
- Viewing controller, virtual disk, and drivers information
- Checking for preserved cache
- Deleting preserved cache
- Viewing expansion information
- Viewing the foreign configuration
- Importing the foreign configuration
- Viewing BBU information
- Viewing physical drive details for the specified slot in the controller
- Viewing the boot drive for the controller
- Setting virtual drive as boot drive
- Locating a drive
- Stopping a locate operation
- Snapdump commands
- Getting help
Dell EMC PowerEdge RAID Controller CLI Reference Guide
Controller profile commands
The PERC command line tool supports the following profile-related commands:
perccli /cx show profile perccli /cx set profile profileid=<id>
The detailed description for each command follows.
perccli /cx show profile
This command shows current profile and profile properties.
Input example:
perccli /c1 show profileperccli /cx set profile profileid=<id>
This command sets profile ID. The output contains control ID, status, and description attributes.
Input example:
perccli /c1 set profile profileid=<id>NOTE: You must reboot the system for profile changes to take effect.
NOTE: Profile changes fail if:
- The new profile supports fewer drives than the number of drives supported in the current topology.
- Background operations (rebuild, copy back, full initialization, background initialization, patrol read, cc) are active.
- Background operations start after profile change but before you reboot the system.
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: <>()\