The DSR Bulk Import operations use configuration data in ASCII Comma-Separated Values (CSV) files (.csv), to insert new data into, update existing data in, or delete existing data from the Diameter Configuration and Diameter Common, IPFE Configuration, or DSR Applications (FABR, RBAR, PCA, GLA, CPA and Charging SBR, MD-IWF, DM-IWF, and RADIUS) configuration data in the system.
Import CSV Files
Import CSV files can be created by using a DSR Bulk Export operation, or can be manually created using a text editor. The CSV file formats are described in Diameter and Diameter Common CSV File Formats and Contents.
Caution:
The format of each Import CSV file record must be compatible with the configuration data in the current DSR release in the system.Note:
configuration data cannot be imported using the Bulk Export function.Note:
Diameter Mediation configuration data cannot be imported with DSR Bulk Import operations; Mediation has its own Import and Export functions.Files that are created using the DSR Bulk Export operation can be exported either to the Status & Manage File Management Directory ( page), or to the local Export Server Directory.
Import Operations
Caution:
Bulk Import can degrade the performance of the DA-MP and should be performed only in the maintenance window.The
page lists all files in the File Management area (on the page) that have the .csv file extension.The File Management button on the page opens the page.
Note:
The Application Type, Keyword, and Key fields in each file record are used to identify the configuration data entry in the system.Only data records that do not currently exist in the system are inserted. Any records in the file that do already exist in the system are treated and logged as failures.
Only data records that currently exist in the system can be updated. Any records in the file that do not already exist in the system, and any records that already exist in the system but are not updated in the file, are treated and logged as failures.
Only data records that currently exist in the system can be deleted. Any records in the file that do not exist in the system, and any records that exist in the system but are not changed in the file, are treated and logged as failures.
Insert from CSV operations - Records need to be added or edited to be able to insert new configuration data entries (such as connections or Route Lists). It is best to remove from the file any records for existing configuration data entries; they will be flagged as errors for an Insert operation. It might be difficult to distinguish between logged errors for existing data and for the records for the new entries.
Update from CSV operations – Records need to be edited to change element values in existing configuration data entries. The Application Type, Keyword, and Key fields are NOT changed in the records, so that the entries can be identified as existing in the system. It is best to remove from the file any records for existing configuration data entries that are NOT being updated; they will be flagged as errors for an Insert operation. It might be difficult to distinguish between logged errors for existing records that are not updated and for the updated records.
Delete from CSV operations – Using an exported file without editing it will remove from the system all of the configuration data entries in the exported records. If you do not want to delete all of the configuration data entries that are in the file records, edit the file and remove the records for the entries that are NOT to be deleted. Records for configuration data entries that do not exist in the system will be flagged as errors for a Delete operation. For example, if you want to delete 20 of 100 configured connections, edit the file and remove the records for the 80 connections that you do not want to delete.
The files can be edited later for use with a different Import operation.
Manually created CSV files are not required to contain a comment header. If a comment header is included in the file, it must be formatted using pound signs (#), as shown in the Export file header that is described in Export Results.
Note:
IPFE supports Import and Delete operations only. Due to the design of the IPFE database, import of a single table is not supported. Importing both IpfeOption and IpListTsa is required. You must import IpfeOption first followed by IpListTsa. IpfeOption defines part of the Target Set data used during validation of the IpListTsa.Import Operation Results
For example, ImportExportStatus/<import file name>.log
Information for records that succeed is not included in the log. The log file contains the Action (Import operation) that was performed; and the number of Successful Operations (records), Failed Operations (records), and Total Operations (records).
The file is a .csv with the same name as the Import file, but contains _Failures in the file name.
For example, if the Import file name is October_2_SO_DSR1_Diameter_CmdCodes.csv
, the Failures file is named October_2_SO_ DSR1_Diameter_CmdCodes_Failures.csv
A Failures file can be downloaded from the local File Management area to a server off the local system, edited to correct each record that failed, uploaded to the local system File Management area, and used again to repeat the Import operation and successfully process the records.
Any Failures .csv files in the File Management Directory that remain unchanged for more than 14 days and any log files older than 14 days will be automatically removed. The task to remove these files runs once a day.
The Diameter Common > Import page
A popup window appears to confirm the selected Import operation.
One import or export task at a time is allowed.
The progress of the import operation can also be viewed on the
page.Exported .csv files can be viewed, downloaded to an external location, uploaded from an external location, and deleted.
Log files from Import operations can be viewed and deleted.
When a check mark appears in the box, only the first record that failed is recorded in the log and the Failures .csv file. The Bulk Import operation stops after the error is detected and logged.
When there is no check mark in the box (the default), all records that failed are recorded in the log and the Failures .csv file.