We wish to interrogate our fleet (Several generations of servers and controllers, including R730XDs) for their Storage Read and Write Policies.
We want to be able to change those policies if they do not meet our criteria.
I cannot find the specific RACADM commands to do the above. I have downloaded the paper RAID And Storage Configuration using RACADM Commands in iDRAC7, but cannot see the correct commands to use.
Can someone pls point me to the correct commands, starting with the interrogation command to see the status of the Read and Write Policies?
I need to get the status of the VDisks from the DRAC using putty.
Is there a command to do this?
racadm storage get vdisks -o
or
racadm storage get vdisks -o -p DiskCachePolicy
The -p property subcommand will reduce the amount of information provided and only list the value specified.
The command to change the policy would be something like this:
racadm set Storage.VirtualDisk.DiskCachePolicy.7 disabled
Some of these commands are case sensitive, so it is best practice to use proper case. Virtual disk numbering starts at 0, but the command arguments start at 1. Virtual disk 6 would correlate to 7.
I'm not sure about a RACADM command. If you really need a RACADM let me know and I will see if one exists. You should be able to accomplish this using omreport and omconfig commands. The disk cache policy is set at a virtual disk level on most of our controllers. If you have a controller that allows non-RAID or HBA mode then it will be set at a physical disk level. The command to get the disk information would on vdisks or pdisks would be:
Daniel My
12 Elder
•
6205 Posts
8342
0
Posted August 17th, 2017 16:00
racadm storage get vdisks -o
or
racadm storage get vdisks -o -p DiskCachePolicy
The -p property subcommand will reduce the amount of information provided and only list the value specified.
The command to change the policy would be something like this:
racadm set Storage.VirtualDisk.DiskCachePolicy.7 disabled
Some of these commands are case sensitive, so it is best practice to use proper case. Virtual disk numbering starts at 0, but the command arguments start at 1. Virtual disk 6 would correlate to 7.
Thanks