Installing and Running the CI Exerciser Software

This document outlines the procedures for installing and running the CI Exerciser software, an online diagnostic tool designed to detect and isolate errors within a cluster to specific nodes. The software operates with a controller node that sends commands and responder nodes that perform actions and return responses, with all error output appearing at the controller.

Before running the exerciser, several prerequisites must be met:

• Process Quotas and Privileges: Users need specific privileges (e.g., CMKRNL, DIAGNOSE) and increased process quotas (listed in Appendix B), which can be set using the Authorize program.
• System Resources: System parameters such as nonpaged pool, IRP count, SRP count, LRP count, SCSCONNCNT, and SCSBUFFCNT must be increased using the SYSGEN utility. These modifications usually require a system reboot, and the system manager must be notified. Appendix A provides formulas to calculate the necessary increases based on the number of controllers and responders in the cluster. Command files (CIEPARAMS, CIEPARRST) are provided to assist with this, but caution is advised.
• SCS System ID: Each node in the CI cluster must have a unique, non-zero SCSSYSTEMID to ensure the diagnostic runs correctly.
• Polling Interval: The PAPOLLINTERVAL parameter should be kept at 15 seconds or less to prevent excessively long timeouts.

The installation process (Section 3.0) involves logging into a system manager account, inserting the CI Exerciser media (floppy disk for CI780 or CI750), mounting it, and executing the installation command procedure (@CS1:(CIE)CIEINSTAL), which copies necessary files to the SYSSMAINTENANCE area. The Diagnostic Supervisor (EVXCI) media, included in the kit, also needs to be placed in sysmaint.

Loading the CI Exerciser software (Section 4.0) is a separate step required after each system reboot. This involves running the CIELOAD.COM command procedure to load the appropriate class drivers into nonpaged pool. The procedure prompts the user to specify whether the node will act as a controller or a responder; running as a controller causes more significant system performance degradation than running as a responder.

Finally, running the CI Exerciser (Section 5.0) involves issuing specific commands in the Diagnostic Supervisor, including LOAD EVXCI, ATTACH for each port to be tested, and SELECT. Only one controller should run activity generation (test 20) or performance monitoring (test 21) tests at a time in a cluster. A help facility (HELP EVXCI) is available for guidance on various topics.