Guest

Cisco Billing and Measurements Server

Field Notice: *Expired* FN - 28375 - Billing and Measurements Server (BAMS)- Rollover to January 1, 2004 Generates Errors in Processing Data


Revised May 7, 2008

January 07, 2004


NOTICE:

THIS FIELD NOTICE HAS BEEN EXPIRED AND IS NO LONGER MAINTAINED OR UPDATED BY CISCO.

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE, WARRANTY OR SUPPORT. USE OF THE INFORMATION ON THIS FIELD NOTICE OR MATERIALS LINKED FROM THIS FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Products Affected

BAMS 3.10, 3.13

Problem Description

It has come to our attention that Billing and Measurements Server (BAMS) releases 3.10 and 3.13 will more than likely experience problems in processing data generated since January 1, 2004.

Background

BAMS Engineering has confirmed the problems exist in release 3.10 and 3.13 and have posted the patches on Software Center.

Problem Symptoms

As of the rollover to 2004, the following error messages have commonly been reported in the BAMS logs:

01/06/04 10:53:15 AGB004: Processing file cor_agcdr_20040105210003_008155.bi
01/06/04 10:53:15 AGB004:+n
01/06/04 10:53:15 * AGB202: #2 - Invalid CALL_REFERENCE_ID: 200401052104240000
01/06/04 10:53:15 * AGB202:+000007
01/06/04 10:53:15 * AGB202: #3 - Invalid CALL_REFERENCE_ID: 200401052104340000
01/06/04 10:53:15 * AGB202:+000008
01/06/04 10:53:15 AGB010: Processed cor_agcdr_20040105210003_008155.bin, tot
01/06/04 10:53:15 AGB010:+al:6 good:3 synerr:2 semerr:0 lkuperr:1
01/06/04 10:53:15 AGB236: 2 record(s) default to interlata due to absent NPA
01/06/04 10:53:15 AGB236:+NXX for file cor_agcdr_20040105210003_008155.bin
01/06/04 10:53:15 AGB237: 6 record(s) did not have called and/or calling num
01/06/04 10:53:15 AGB237:+ber for file cor_agcdr_20040105210003_008155.bin
01/06/04 10:53:15 AGB019: No flat files to process. Retry in 60 seconds

Workaround/Solution

Patches that were updated January 10, 2004 are now available. The latest BAMS patches are now available to address the following problems:

  1. An FMT process problem encountered due to new length in tags 4046/4047, DDTS CSCed37233 (registered customers only) BAMS - PGW CDR file caused BAMS to stop processing and dump core fil

  2. An additional problem related to the recent 2004 rollover problem in ASCII output data, DDTS CSCed41193 (registered customers only) CDRs produced after P12 upgrade is ascew by 86400 seconds (one day).

Patches for BAMS are :

BAMS 3.10 (registered customers only) patch.

BAMS 3.13 (registered customers only) patch.

Data can still be polled from the PGW and stored on BAMS for re-processing. Ensure that the cleanup interval (delage) on the BAMS box is as follows (30=30days). This will allow for reprocessing of the Call Detail Records (CDRs) on BAMSs when the patch is available. If this interval has elapsed, CDR data can be lost!

mml:sys>prov-rtrv:MSC-PARMS:
Billing and Measurements Server - BAMS-01 2004-03-31 18:48:06
B RTRV
"MSC-PARMS:active="Y",dir="/opt/CiscoBAMS/data",subdirs="Y",type="baf*bin",polled=2,alarm=5,agealarm=30,agelevel=6,delage=30,delalarm=6"
"MSC-PARMS:active="Y",dir="/opt/CiscoBAMS/data",subdirs="Y",type="acc_h*",polled=1,alarm=5,agealarm=30,agelevel=6,delage=30,delalarm=6"
"MSC-PARMS:active="Y",dir="/opt/CiscoBAMS/data",subdirs="Y",type="acc_d*",polled=1,alarm=5,agealarm=30,agelevel=6,delage=30,delalarm=6"
"MSC-PARMS:active="Y",dir="/opt/CiscoBAMS/data",subdirs="Y",type="acc_r*",polled=1,alarm=5,agealarm=30,agelevel=6,delage=30,delalarm=6"
"MSC-PARMS:active="Y",dir="/opt/CiscoBAMS/data",subdirs="Y",type="cdr*bin",polled=2,alarm=5,agealarm=30,agelevel=6,delage=30,delalarm=6"
"MSC-PARMS:active="Y",dir="/opt/CiscoBAMS/data",subdirs="Y",type="*finished",polled=1,alarm=5,agealarm=30,agelevel=6,delage=30,delalarm=6"
"MSC-PARMS:active="Y",dir="/opt/CiscoBAMS/data",subdirs="Y",type="elkup*",polled=1,alarm=6,agealarm=30,agelevel=6,delage=30,delalarm=6"
"MSC-PARMS:active="Y",dir="/opt/CiscoBAMS/data",subdirs="Y",type="esyn*",polled=1,alarm=6,agealarm=30,agelevel=6,delage=30,delalarm=6"
"MSC-PARMS:active="Y",dir="/opt/CiscoBAMS/data",subdirs="Y",type="esem*",polled=1,alarm=6,agealarm=30,agelevel=6,delage=30,delalarm=6"

RELEASE NOTES:

This applies to BAMS 3.10 patch 12, 3.13 patch 11.

When installing the patch containing the fix for the EMPTY ASCII CDRs and Invalid CALL REFERENCE ID message for the first time, the install script will prompt the user to answer Yes or No to the following questions.

  1. Do you want to re-process billing records using the archived files? [y,n]

    Answering y will initiate re-processing of all 2004 billing records

  2. Do you want to save old billing records generated after New Years Day? [y,n]

The second question is asked only if the user answered yes to the first question.

If the user answers yes to first question , then the CDR files archived since New Years Day Jan 1, 2004 00:00:00 UTC will be re-processed. The user should then wait a few hours or even a few days, depending on the size of archived files.

If the user answer yes to the second question, then the billing files already generated after New Years Day prior to this patch will be saved. The saved directories are /opt/CiscoBAMS/data/s0X/backup_dir_2004 where X is in the range of one to eight, for a total of eight nodes on BAMS.

warning Warning:?Since reprocessing requires a large amount of free disk space in the /opt/CiscoBAMS/data partition, BAMS users should backup all the files in /opt/CiscoBAMS/CDR and /opt/CiscoBAMS/data partitions before the re-processing.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCed38155 (registered customers only)

EMPTY ASCII CDRs and Invalid CALL_REFERENCE_ID messag BAMS-logs

CSCed3723 (registered customers only) 3

BAMS - PGW CDR file caused BAMS to stop processing and dump core fil

CSCed41193 (registered customers only)

CDRs produced after P12 upgrade is ascew by 86400 seconds (one day)

  

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.