Generic Diameter Interface
DRA Nodal Testing
The DRA Nodal test case emulates the functional requirements of 3GPP Diameter Routing Agent (DRA) and GSM-A Diameter Edge Agent (DEA). The test case also generates and measures diameter messaging traffic sent to or received from DRA/DEA agents.
See DRA Nodal Parameters for details of configuring various test case options and parameters.
Define your own custom (Generic) Diameter Interfaces in DRA Nodal.
Select up to four, and choose to emulate, client, server, or both, and give them names, on the Test configuration tab:
Go to each tab to define the diameter/messages for the interface as a profile:
When creating a profile, add your own Diameter Commands/Messages and fill them with AVPs from the profile’s defined AVP Database.
All commands/messages in the profile must use AVPs defined in this database. DB Size (bytes) has been added to the VSA/AVP configuration window. This is the value the AVP Database estimator calculates that is required for the AVP Database size in tabs such a Diameter, Radius, Etc. It should be used when determining the size of the AVP Database Size in Bytes.
View/edit this database from the “AVP Database” “View/Edit” button:
the database may be updated directly from the Command/Message editor windows:
The left side of the editor is the Command/Message content (black line) and the right side is the AVP Database. Drag and drop AVPs or click the Insert (Left arrow) to add AVPs to command. You can select different commands from the Command Combo Box.
Deleting an AVP from the database will remove it from ALL commands.
Move AVPs up and down in the Command using Up and Down arrows.
Move AVPs up and down in the AVP Database as well, this will result in the AVP-# changing in the Commands, as AVPs are ID’d by their Index in the Command (red – dashes).
Edit individual Commands by editing the AVPs cell:
In this mode, the Combo Box will only have one command in it.
Message Flows have special rules for Generic Interfaces.
Consider two sets of Commands, Generic commands Gen1-Gen4 and Native (named protocol) Commands S6a/Gx/Gxx, etc....
When Native Commands are sent from a Generic Interface, they cannot have ANY Arguments. If arguments are set up, they will fail validation.
Generic Commands have up to 3 arguments. If it is a response, (No R-Flag), it can have either ResultCode or ExperimentalResultCode, not both. All Generic Commands have SessionNumber argument.
The entire Profile tab can be saved as a Template:
Then last saved template name is on profile:
