1. ASR can upload configuration metadata to support problem resolution1.
2. ASR Manager opens a service request (SR) automatically after sensors detect hardware faults1
https://docs.oracle.com/cd/E37710_01/doc.41/e23333/toc.htm

1. OEDA deployment steps include calibrate cells, create cell disks, and resecure machine2.
2. OEDA sets up key-based authentication for the root user by using the setuprootssh.sh utility included with OEDA2.

According to Oracle's documentation1, the Cell Control Command-Line Interface (CellCLI) utility is the command-line administration tool for Oracle Exadata System Software. It can be used to perform various tasks on Exadata Storage Servers, such as creating and managing objects, monitoring performance, and configuring alerts.
To run CELLCLI commands on multiple cells simultaneously, you can use the Distributed Command-Line Interface (dcli) utility2. The dcli utility allows you to execute commands or scripts on a group of cells or hosts in parallel. You can use the dcli utility to copy files from one cell or host to multiple cells or hosts using the -f option3. You can also use the dcli utility to execute commands or scripts on multiple cells or hosts using the -l option to specify a user name and the -g option to specify a file containing a list of cells or hosts3.
Therefore, to achieve your requirement of running a script with several CELLCLI commands on each cell in your Exadata full rack simultaneously, you must:
Copy and execute the script on all storage servers using the dcli command.

This command will display the name, deviceName, diskType and physicalFirmware attributes of the physicaldisks in a storage server, as explained in the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book (page 85).
https://docs.oracle.com/en/engineered-systems/exadata-database-machine/sagug/exadata-storage-server-cellcli.html

According to Oracle's documentation12, some of the statements that are true about applying updates on Exadata systems are:
Failed storage server updates are automatically rolled back to a previous release1.
When running a "yum update" for a new Exadata release, all other repositories should be disabled1.