4.6 Remote audit

The SDS Maintenance Remote Audit page allows you to access an on-demand ability to initiate an audit of the remote HLR Router provisioning database and flag any differences found between the SDS and the HLR Router databases. This provisioning database audit includes MSISDNs and IMSIs and their associated Network Entity address values, which are extracted from the Destination Map table.

When you submit an audit request on the SDS GUI maintenance page, a PDBI client called pdbaudit connects to the local PDBA and to the remote PDBA running on the HLR Router system. It sends request commands to both PDBAs, compares the response data, and reports any discrepancies between the two databases. Then you can check the status and review the results of the audit on the SDS GUI status page.

SDS supports manual and configurable automated audit runs between the SDS master database instance and the HLR Router database instance. Configurable automated audit runs are those runs that run at configured times to verify the accuracy of SDS master and HLR Router database instances. A manual audit allows specification of audit between SDS master and HLR Router database instances, based on some data range (for example, audit IMSI range) or single MSISDN or IMSI value.

SDS supports an on-demand ability to initiate an audit of the remote HLR Router provisioning database and flag any differences found between the SDS and the HLR Router databases. HLR Router provisioning data to be audited can be specified in one of two ways - by a single range of numbers, or by an input file containing multiple ranges of numbers. Using an input file allows an operator to specify multiple IMSI and MSISDN ranges at one time versus scheduling multiple remote HLR Router audits on a single range.

Use the SDS Maintenance Remote Audit page to:

  • View the status of the database remote audits and to request a site-wide database audit of a specified subset of provisioning data, and/or
  • Request a remote audit between SDS and HLR Router data using a subset of MSISDN or IMSI values.

Since each node is responsible for managing its own resources, some nodes may decide to delay or cancel the requested audit to maintain sufficient resources to process signaling traffic.