Cisco Cisco Packet Data Interworking Function (PDIF)
AAA Introduction and Overview
▀ Supported Features
▄ AAA Interface Administration and Reference, StarOS Release 18
20
Dynamic Diameter Dictionary Configuration
Apart from the standard and customer-specific dictionaries supported currently in the Diameter application, this feature
allows the dynamic configuration of any new Diameter dictionaries at run time. This feature can be configured using
allows the dynamic configuration of any new Diameter dictionaries at run time. This feature can be configured using
diameter dynamic-dictionary
command in the Global Configuration Mode. For more information on this
command, refer to the Command Line Interface Reference.
Important:
Up to a maximum of 10 dynamic dictionaries can be configured and loaded in to the system.
To perform this configuration, a text file should be created in ABNF format and all the required Diameter AVPs and
command codes should be configured in the file. Then, the file should be saved in flash or some URL that will be
accessible by the system. Now, run the
command codes should be configured in the file. Then, the file should be saved in flash or some URL that will be
accessible by the system. Now, run the
dict_validate.exe
authentication tool on the created dynamic dictionary text
file. This authentication tool does basic syntax checks on the file and prepends the file contents with an MD5 checksum.
This checksum ensures that the dictionary cannot be modified once created. Currently, only Cisco personnel can access
the authentication tool
This checksum ensures that the dictionary cannot be modified once created. Currently, only Cisco personnel can access
the authentication tool
dict_validate.exe
.
Important:
It is highly necessary that you must not create dynamic dictionary for your customization needs.
Contact your Cisco account representative for any new dynamic dictionary creation request.
Now, configure a dynamic dictionary with an unique name and map it to the URL of the file to be loaded dynamically in
to the system at the global configuration level.
to the system at the global configuration level.
When the names of the dynamic dictionaries and their URLs are configured, the corresponding files at the respective
URLs are parsed and populated in all SessMgr and AAAmgr facilities as new dictionaries and kept available to be used
when these dictionary names are configured under any Diameter application level or AAA group.
URLs are parsed and populated in all SessMgr and AAAmgr facilities as new dictionaries and kept available to be used
when these dictionary names are configured under any Diameter application level or AAA group.
When a dynamic dictionary name is configured under an application such as IMS authorization service or in a AAA
group, the corresponding dictionary (which is already loaded in SessMgrs and AAAMgrs) entry will be used.
group, the corresponding dictionary (which is already loaded in SessMgrs and AAAMgrs) entry will be used.
There will be only one instance of a dynamic dictionary loaded in to a task for one dynamic dictionary name even if the
same dictionary name is configured in multiple AAA groups or multiple application configurations. That is, even if the
same dictionary name is configured in several applications or several AAA groups, all these applications and AAA
groups will refer to the same dynamic dictionary instance.
same dictionary name is configured in multiple AAA groups or multiple application configurations. That is, even if the
same dictionary name is configured in several applications or several AAA groups, all these applications and AAA
groups will refer to the same dynamic dictionary instance.
Failure Handling Template Configuration
This feature allows the user to configure Failure Handling template at Global Configuration level. The failure handling
template defines the action to be taken when the Diameter application encounters a failure for example, a result-code
failure, tx-expiry or response-timeout. The application will take the action given by the template. This template can be
configured using
template defines the action to be taken when the Diameter application encounters a failure for example, a result-code
failure, tx-expiry or response-timeout. The application will take the action given by the template. This template can be
configured using
failure-handling-template
command in the Global Configuration Mode.
Important:
A maximum of 64 templates can be configured on the system.
This command specifies the name of a new or existing failure handling template and enters the Failure Handling
Template mode. Lookup is done first to identify if there is an exact match for message-type and failure-type. If not
present, lookup is done for 'any' match for message and failure type.
Template mode. Lookup is done first to identify if there is an exact match for message-type and failure-type. If not
present, lookup is done for 'any' match for message and failure type.
If there are different failure handling configurations present within the template for the same message type, the action is
applied as per the latest error encountered.
applied as per the latest error encountered.