The DDCMasterTest periodically verifies whether configured ports on the DDC are available or not, and if so how quickly it responds to connection requests. In addition, the test also reports whether the DDC being monitored is the 'master' of a farm. This page depicts the default parameters that need to be configured for the DDCMasterTest and appears on clicking the CONFIGURE DEFAULT button beside this test in the CONFIGURE TESTS page.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed. 

• In the TARGETPORTS text box, specify either a comma-separated list of port numbers that are to be tested (eg., 80,7077,1521), or a comma-separated list of port name:port number pairs that are to be tested (eg., smtp:25,mssql:1433). In the latter case, the port name will be displayed in the monitor interface. Alternatively, this parameter can take a comma-separated list of port name:IP address:port number pairs that are to be tested, so as to enable the test to try and connect to Tcp ports on multiple IP addresses. For example, mysql:192.168.0.102:1433,egwebsite:209.15.165.127:80.

• If the ISPASSIVE flag is set to Yes, then the server under consideration is a passive server in an Oracle cluster. No alerts will be generated if the server is not running. Measures will be reported as "Not applicable' by the agent if the server is not up.

• Specify the duration (in seconds) in the TIMEOUT text box beyond which the this test will time out if a response is not received from the DDC. The default is 60 seconds.

• Once the above value is provided, click on the UPDATE button to register the changes made.

The << button enables the user to go back to the previous screen.