Use the Edit VSA window... or the Edit AVP window... to define the parameters (that can optionally be saved as templates) used to create optional RADIUS or Diameter attributes. They include the information required to provision the attribute fields and a selection of messages in which the attribute will be used.
RADIUS |
Diameter |
See Diameter Result Codes for AVP-related errors that may be returned by a server when AVPs are improperly used or improperly coded.
Vendor |
Select the vendor associated with the attribute. In a vendor-specific attribute, the vendor's ID provisions the Vendor-ID field. Options: All defined vendors are available in the list. You can add a new vendor with the Vendors... button. Default: RADIUS or Diameter |
||
Library | Select from BASIC or GLOBAL library. | ||
Filter |
Use Filter to Compare the Name, Type/Code, and Type/Code-Name fields of Templates. |
||
Type |
Provision either the RADIUS Type or Vendor Type field. The RADIUS Type field is coded differently for RADIUS attributes and VSA extended attributes.
Range: 0 — 255 Default: 0 |
||
Code |
Provision the AVP Code field. This field, in combination with the Vendor ID field, uniquely identifies an AVP. You may also enter the application ID AVP. The Application-Id AVP returned by a server node is provisioned by the value received in requests from a peer. If the you do not enter the Application ID AVP, the default AVP will be used. The IANA manages the official codes allocated to Diameter. Range: N/A (values 1 — 255 are reserved for backward compatibility with RADIUS)
Default: 0 |
||
Name |
Indicates the attribute's display name. This value is not included in any message fields. Range: up to 32 characters Default: N/A |
||
Hashing |
Select the Hashing algorithm to be used (RADIUS only). Choices include MD5, SMD5 (Salt MD5), or None. |
||
Format |
Identifies the Value type and determines how the Value will be formatted in the message. Refer to the attribute definition for the valid format. Auto-Increment feature is supported for all the formats listed below. Options:
Default: UINT32 |
||
Auto Increment |
Provision a serially-incrementing value for every MN. Each MN session will use the same value in all selected messages. The incrementing method varies depending on the value Format — for example, IP addresses increment using valid address values. |
||
AVP Flags |
Set the bits in the AVP Flags field. AVP Flags are used to inform the peer how each attribute must be handled.
|
||
Value |
Provision either the RADIUS String field, the Value portion of a RADIUS vendor-specific attribute, or the Data field of a Diameter attribute. This value should be consistent with the Format selected. If you enter an invalid value for the UINT32 or HEX_STRING formats, you will receive a validation error. Range: N/A (Up to 253 characters for RADIUS attributes or 247 characters for RADIUS vendor-specific attributes) Default: 0 |
||
|
Select to indicate whether you would like the AVP/VSA to be always appended to the message or override built-in AVP/VSA (if not built-in AVP/VSA, to add the AVP/VSA to the message) or Remove Built-in AVP.
Override/Remove Built-in AVP is only available in these Test Cases: AAA Server Node, DRA Nodal, DRA Node (with the exception of User Auth Request Command and Answer), HSS Nodal (S6a Interface), HSS Node, IMS Node (Rx Interface), MME Nodal (S6a Interface), OCS Node (Ro and Sy Interface), PCRF Nodal, PCRF Node (Sy Interface and AGW-Rules-all), SCEF Node (T6x), and SGW Nodal (S6a Interface). See AVP Override/Remove/Append Rule below. |
||
Only in these message instances |
Use Only in these message instances (e.g., 1, 3-4, 8- ) to include different AVPs in each/different instances of the message. This Only in these message instances checkbox and the text input field is available for the DCCA Node test case when you select any one of the following Message types:
This Only in these message instances checkbox and the text input field is available for the Wifi Offload Gateway Nodal test case when you select any one of the following Message types:
|
||
Messages |
Select messages in which the attribute will be used. At least one message must be selected. The selections that you can make are limited to only the messages that can be sent by the test case and are not shaded in the Edit AVP Window / Edit VSA Window.
|
Select to View/Edit criteria based on VSAs on AAA Radius Tab. Define VSA Criteria, that get associated with VSA Criteria measurements which increment when Criterion is not met. To get indication (measurement count > 0) when an AVP value==300, you must setup VSA Criterion to check for AVP!=300 and then it will increment when the value does == 300. The generated measurement will remain 0 by default and will only increment if the VSA Criterion is set to Not Present and a matching VSA type is found or if the VSA Criterion is set to match a condition (operator-format-value) the VSA type is matched and the condition is not met (false). These rules are applied on a per-message basis, use the filter to see the effective rules on a per-message basis. The Vendor and Flags have no impact on the Criterion.
Able to:
Determine if certain VSAs are present, not present or have certain values in specific messages.
Define VSA Criteria, that get associated with VSA Criteria measurements.
Setup Pass/Fail Criteria against these measurements, to tie it into the Pass/Fail Criteria.
Define up to 32 VSA Criteria per test case, which will result in up to 32 simple count measurements that increment each time a criteria is not met. Measurements names are VSA Criterion 1 through VSA Criterion 32.
Measurements are Summarized across all test cases in Summary view, and individual counts for each test case are available in the test case view. (e.g. "The # of VSA that Failed to meet Criteria #N" )
Up to the user to put the VSAs in the same order in each test case to achieve same meaning.
VSA Criteria can be setup easily in one Test Case, then copy/paste to the others via QuickList, to maintain the same exact setup.
Can also be synchronized across test cases using the Cross Reference.
Enter the Match Criteria:
Either select Not Present or Enter Format, Operator , and Value.
Operator Options: ‘==’ (Equal), ‘!=’ (Not Equal) , ‘>’ (Greater than), ‘<’ (Less than), ‘>=’ (Greater than or Equal) and ‘<=’ (Less than or Equal).
NOTE: Not all Operator options are available for all Format Types. For example, If Format type = MAC_ADDRESS then only '==' (Equal) and '!=' (Not Equal) are available Operator Options. When checking against a GROUPED AVP, you must use HEX_STRING set the Value to the Grouped AVP hex stream payload without the grouped AVP vendor field. |
Available Measurements:
Able to track the measurements with Test Session Pass/Fail Criteria.
Select to View/Edit criteria based on AVPs on Diameter Tab. Define AVP Criteria, that get associated with AVP Criteria measurements which increment when Criterion is not met. To get indication (measurement count > 0) when an AVP value==300, you must setup AVP Criterion to check for AVP!=300 and then it will increment when the value does == 300. The generated measurement will remain 0 by default and will only increment if the AVP Criterion is set to Not Present and a matching AVP type is found or if the AVP Criterion is set to match a condition (operator-format-value) the AVP type is matched and the condition is not met (false). These rules are applied on a per-message basis, use the filter to see the effective rules on a per-message basis. The Vendor and Flags have no impact on the Criterion.
Able to:
Determine if certain AVPs are present, not present or have certain values in specific messages.
Define AVP Criteria, that get associated with AVP Criteria measurements.
Setup Pass/Fail Criteria against these measurements, to tie it into the Pass/Fail Criteria.
Define up to 32 AVP Criteria per test case, which will result in up to 32 simple count measurements that increment each time a criteria is not met. Measurements names are AVP Criterion 1 through AVP Criterion 32.
Measurements are Summarized across all test cases in Summary view, and individual counts for each test case are available in the test case view. (e.g. "The # of AVP that Failed to meet Criteria #N" )
Up to the user to put the AVPs in the same order in each test case to achieve same meaning.
AVP Criteria can be setup easily in one Test Case, then copy/paste to the others via QuickList, to maintain the same exact setup.
Can also be synchronized across test cases using the Cross Reference.
Enter the Match Criteria:
Either select Not Present or Enter Format, Operator , and Value.
Operator Options: ‘==’ (Equal), ‘!=’ (Not Equal) , ‘>’ (Greater than), ‘<’ (Less than), ‘>=’ (Greater than or Equal) and ‘<=’ (Less than or Equal).
NOTE: Not all Operator options are available for all Format Types. For example, If Format type = MAC_ADDRESS then only '==' (Equal) and '!=' (Not Equal) are available Operator Options. When checking against a GROUPED AVP, you must use HEX_STRING set the Value to the Grouped AVP hex stream payload without the grouped AVP vendor field. |
Able to track the measurements with Test Session Pass/Fail Criteria.
NOTE: The naming convention for the AVP Criteria is in the DRA Nodal is: Node_Name + "AVP Criteria". Examples: PCRF AVP Criteria, AGW Node AVP Criteria, AF Node AVP Criteria. |
For PCRF Node, only Gx Rule level is supported:
Example, override rule name in “Rule Set 1” in CCR-I to “aaaaaaaa”
Result:
Diameter Protocol
|
| first level
|
|---| second level (group)
|---|
|---|---| third level (sub group)
|---|---|
- Override will override any matched AVP Code at any level, cannot override group.
- Remove will remove any matched AVP Code at any level. To remove group:
For example, remove “Charge-Rule-Install” group with AVP Code 1001 in CCR-I Message:
Append will only append at 1st level and at the end of message.
Use Remove & Append to add an AVP into 2nd, 3rd,… level with this helpful trick:
For example, add “Origin-Realm” AVP code 296 into “Charge-Rule-Install” group.
Can also use this to Override a specific AVP in Specific group.
dcca_config_param.xlsx, dcca_example.xlsx, dcca_avp_config_example.csv
Avp | avp | When you provision AVPs, the value format includes the same settings as a AVP Template: |
<Vendor-ID>/<AvpCode>/<Msg-Mask>/<Format>/<Auto Increment>/<Avp Flags>/<Value> | ||
Where: | ||
<Vendor-ID> = Decimal or hexadecimal Vendor ID | ||
<AvpCode> = Decimal or hexadecimal Avp code | ||
<Msg-Mask> = A bit mask of the messages that will include the attribute (Applies To) | ||
aaReqMsg_c = 0x0001, aaAnsMsg_c = 0x0002, accountStartMsg_c = 0x0004, accountStopMsg_c = 0x0008, accountInterimMsg_c = 0x0010, accountAnsMsg_c = 0x0020, reAuthReqMsg_c = 0x0040, reAuthAnsMsg_c = 0x0080, sessTermReqMsg_c = 0x0100, sessTermAnsMsg_c = 0x0200, abortSessReqMsg_c = 0x0400, abortSessAnsMsg_c = 0x0800, capExchgReqMsg_c = 0x1000, capExchgAnsMsg_c = 0x2000, creditCtrlInitialMsg_c = 0x4000, creditCtrlUpdateMsg_c = 0x8000,//uint16 max creditCtrlTerminateMsg_c = 0x10000, creditCtrlAnsMsg_c = 0x20000, DERMsg_c = 0x40000, DEAMsg_c = 0x80000, //DEA success-obsolete in 6.5 accountEventMsg_c = 0x100000, DEAMultiRoundMsg_c = 0x200000,//DEA multiround Answer new in 6.5 DEASuccessMsg_c = 0x400000,//DEA success Answer new in6.5 TR6052 WHA4AMsg_c = 0x800000,//Wimax HA4 Answer new in6.5 TR5476 WHA4RMsg_c = 0x1000000,//Wimax HA4 Req new in6.5 TR5476 reAuthDERMsg_c = 0x2000000,//TR5281 reAuthAARMsg_c = 0x4000000,//TR5281 |
ccTriggerUpdateMsg_c = 0x8000000,//CR
ccReauthUpdateMsg_c = 0x10000000,
ccAnsMsccFinalMsg_c = 0x20000000,
ccOneEventMsg_c = 0x40000000,
ccAnsMsccFailMsg_c = 0x80000000,//uint32 max|
[<Format> = The attribute's Format|mk:@MSITStore:C:\Documents%20and%20Settings\cludwig.SPIRENTCOM.000\Desktop\Landslide_5.6_Help.spirent.chm::/params/aaa/parmvsas.htm#format] |
#define FMT_UINT32 0 #define FMT_TEXT 1 #define FMT_HEX_STRING 2 #define FMT_SSE_USERNAME 3 #define FMT_IPV4 4 #define FMT_IPV6 5 #define FMT_UINT64 6 #define FMT_GROUPED 7 #define FMT_GROUPED_END 8 |
[<Auto Increment> = 0=no, 1=yes (Auto Increment)|mk:@MSITStore:C:\Documents%20and%20Settings\cludwig.SPIRENTCOM.000\Desktop\Landslide_5.6_Help.spirent.chm::/params/aaa/parmvsas.htm#autoinc] |
<Avp Flags> = 0=none, 1=M flag, 2=P flag |
<Value> = The AVP's Value |
Example: |
0/287/4/1/0/0/12345678 provisions the Diameter (0) Accounting-Sub-Session-ID Avp (287) in all AccountStartMsg messages using a TEXT format (1) and a value of 12345678. |