Use the DCCA Server Nodal test case to test one or more DCCA servers. The test system emulates the mobile nodes (MN) from the aspect of creating unique identifiers for each MN. It also emulates a Diameter client, generating traffic from the client towards the server, and listening for and responding to messages from the server.
The test case can be configured for dedicated mode, where the client generates Diameter Credit Control traffic towards a primary server SUT as shown in the diagram below. You can also define a secondary SUT. If the primary SUT is not responsive, the test directs traffic towards the secondary SUT. Both primary and secondary proxies are also supported.
In round-robin mode, you can test up to 10 SUTs. All traffic for the first MN is directed towards the first SUT, the second SUT is used for the second MN, and so on.
In addition to the SUT configuration, you define:
The transaction volume and rates, and an optional rate distribution model.
Mandatory and optional Diameter Base and application-specific AVPs
The amount and type of credit unit usage reported to the server in CCR messages
Default failure handling and failover behaviors
Encrypt Diameter traffic with the optional Dynamic IPSec feature.
Use the SUT Query option to monitor the CPU utilization of an SUT, and determine the amount of activity that the SUT can handle within a given CPU threshold.
Measurements collected for the basic DCCA Server Nodal test case are reported on the following tabs. Additional measurements may be available depending on the test activity and options executed with the test case.