https://docs.oracle.com/en/engineered-systems/exadata-database-machine/dbmmn/maintaining-exadata-database-servers.html According to Oracle's documentation1, one of the utilities for diagnostics and repair of Oracle Exadata Storage Server is ExaWatcher, which collects operating system and network metrics on database servers and storage servers. The utility is located in the /opt/oracle.ExaWatcher directory1.
To investigate why an Exadata Database Server stopped communicating on the client network for 10 minutes over the past weekend, you can use the GetExaWatcherResults.sh script to collect and analyze ExaWatcher data for a specified time range1.
Therefore, the command that you should use to investigate this is:
/opt/oracle.ExaWatcher/GetExaWatcherResults.sh -from <Fridays_Date>_17:00:00 -to <Sundays_Date>_23:59:00

The CELLCLI utility is a command line interface to Exadata that enables the execution of commands across multiple storage servers in parallel. It also has command-line history, so users can easily recall previously entered commands. Furthermore, the CELLCLI utility can be executed using the DCLI utility, which provides a convenient way to execute commands on multiple storage servers simultaneously.
However, CELLCLI does not require root privileges to create CELLDISKS and GRIDDISKS, and it cannot be executed on storage servers. This is because CELLCLI is used to manage the Exadata database machine from the database server [1]. For more information about CELLCLI, refer to the Oracle Exadata Database Machine X9M Implementation Essentials official text book and resources [1][2].

1. Querying VSSYSTEM_EVENTS for the event 'cell physical IO interconnect bytes returned by smart scan' will not be appropriate for monitoring the access on a particular table. The V$SYSTEM_EVENT view is used to monitor system-wide performance statistics, not specific table access. C. Querying v$SYSTAT for the statistic 'cell smart table scan' will not be appropriate for monitoring the access on a particular table as well. The v$SYSTAT view contains system-wide performance statistics, not specific table access.