DSR Bulk Export
The DSR Bulk Export operation creates ASCII Comma-Separated Values (CSV) files (.csv) containing Diameter and Diameter Common, IPFE, and DSR Application configuration data. Exported configuration data can be edited and used with the DSR Bulk Import operations to change the configuration data in the local system without the use of GUI pages. The exported files can be transferred to and used to configure another DSR system.
Note:
Exported CSV files are not intended for long-term backup of configuration data. (Use the Database Backup function described in the DSR Administration Guide and DSR Administration Help for long-term backups of configuration data.)Exported CSV Files
Each exported CSV file contains one or more records for the configuration data that was selected for the Export operation. The record formats and contents are described in Diameter and Diameter Common CSV File Formats and Contents.
- Configuration data refers to any data that is
configured for one of the
Export Application types
(Diameter, RADIUS,
FABR,
RBAR,
CPA,
SBR, PCA, GLA, MDIWF and
IPFE).
Note:
GLA requires that Policy DRA Pooling is active. For more information, see Gateway Location Application (GLA) User Guide or PCA User Guide.Exports must be performed on the OAM where the data can be configured - the NOAM for Diameter Topology Hiding, Diameter Common data, network-wide PCA data, and MAP-Interwokring data for MD-IWF ; and the SOAM for the rest of the Diameter data, Diameter Common data, site-specific PCA data, IPFE data, MAP-Diameter Interworking data for DM-IWF, and DSR Application data.
- For the "Diameter"
Export Application type,
configuration data refers to any data that is configured using the GUI pages
that are available from the Diameter Configuration folders and the Diameter
Common folders.
Note:
configuration data cannot be imported using the Bulk Export function.Note:
Diameter Mediation configuration data cannot be exported with DSR Bulk Export; Mediation has its own Import and Export functions.
- All exportable configuration data available on the OAM
- All exportable configuration data from the selected Export Application, on the OAM
- Exportable configuration data from a selected configuration component for the selected Export Application
When ALL is selected, the exported data for each configuration component appears in a separate .csv file.
For data that is exported once immediately, the default
Output File Name has the following format; the name can be changed and is not
required to keep this format:
NE
Name_Timestamp-TimeZone_ApplicationType_DataType.csv.
For data that is scheduled to be exported periodically, the default Task Name is DSR Configuration Export; the name can be changed.
- Software revision used to generate the exported file
- Date and Time file was generated
- Name of each selected Data object exported
- Total number of exported records
##################################################################################
# Oracle Communications DSR Software Revision: <x.x.x-xxx.xx.x>
# Date/Time Generated: <yyyy/mon/dd hh:mm:ss timezone>
# Exported Application: <ApplicationType>
# Exported Object: <ObjectType>
# Number of Records: <nnn>
##################################################################################
Export Operations
Exported files can be written to the File Management Directory in the Status & Manage File Management area (see the
page) or to the Export Server Directory.Files that are created by a DSR Bulk Export operation must be in the local File Management area before they can be used for Bulk Import operations. See DSR Bulk Import.
- The files appear in the File Management area list on the local system (see the page) and in the list on the page.
- These files can be used for Import operations on the local system.
Any .csv files that are exported to the File Management Directory and remain unchanged for more than 14 days will be automatically removed. The task to remove these files runs once a day.
- If a remote Export Server has been configured (see ), the files in the local Export Server Directory are transferred to the configured remote Export Server location and are deleted from the local Export Server Directory. These transferred files do not appear in the File Management area on the local system, and cannot be used for Import operations on the local system.
- If a remote Export Server has not been configured, the files in the local Export Server Directory appear in the list on the page and in the File Management area list on the local system, but not on the page. These files cannot be used for Import operations on the local system.
Export Results
If the export has any failures or is unsuccessful, the results of the export operation are logged to a log file with the same name as the exported file but with a ".log" extension. Successful export operations will not be logged.
The Diameter Common Export page
- Manually export configuration data one time immediately in a CSV file to either the Export Server or the File Management area.
- Schedule periodic automatic exports of configuration data in CSV files to either the Export Server or the File Management area. Scheduled exports are listed on the page.
- Click
Tasks to display the status and
progress of an Export operation.
The progress of the export operation can also be viewed on the
page. - Click
File Management on the
page to open the
page.
On the
page, exported .csv files can be viewed, downloaded to an external location, uploaded from an external location, and deleted. Log files from Export operations can be viewed and deleted.