The dbmcli -e "LIST IBPORT DETAIL" command is not valid on Exadata X9M. According to the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book [1][2], this command is only valid on Exadata X3 and X4 models. The other three commands are valid on Exadata X9M.
https://forums.oracle.com/ords/apexds/map/tech/apps-infra/discussion/4342715/monitoring-roce-performance

The two actions that are not appropriate for monitoring how a large production table is accessed in order to leverage the benefits of the Exadata Platform are A) querying VSSYSTEMEVENTS and filtering for the event 'cell physical IO interconnect bytes returned by smart scan', associated to your table; and B) querying v$segmentstatistics and filtering for the Object ID of your table from dbaobjects and the the column STATISTICNAME='optimized physical reads'. Instead, you should query v$SYSTAT and filter for the statistic 'cell smart table scan', associated to your table (C), or run the CellCli-command list activerequest, filtering for the attributes ioReason and objectNumber, that you specify as 'Smart Scan' and the Object ID of your table from DBA_OBJECTS (D). These two methods are outlined in the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book (Chapter 8, Monitoring the Exadata Database Machine).

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].

For setting up Auto Service Request (ASR) monitoring on a standalone server dedicated to ASR Manager:
ASR Manager with SNMP Traps: Configuring ASR Manager to utilize SNMP traps allows it to automatically receive alerts from the Integrated Lights Out Manager (ILOM) on Exadata components. The SNMP traps notify ASR Manager of specific hardware faults or critical system events, which then automatically generate service requests with Oracle Support.
This setup ensures proactive monitoring and allows rapid response to any critical alerts related to the Exadata hardware, leveraging the ILOM's ability to monitor key system health metrics and trigger alerts as necessary.