INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Troubleshooting Callmanager 6.x 7.x CDR / CMR & how to fix error 10021

Troubleshooting Callmanager 6.x 7.x CDR / CMR & how to fix error 10021

Troubleshooting Callmanager 6.x 7.x CDR / CMR & how to fix error 10021

(OP)
How to troubleshoot CallManager 6.x / 7.x CDR/CMR
and how to fix Error code 10021.



Note:


Before making changes to the database or its values, please read this document on its entirety
before proceeding further.


-The "Cisco CDR Agent" service moves the CDR records from the subscribers
servers to the publisher server.
-The "Cisco CDR Repository Manager" service moves the CDR records from the
publisher server to the Billing server.


A few days ago I had an issue with CDR, everytime we were trying to run a query on
an extension we were getting "Error Code 10021 There is no matching records".


Before continuing further I am assuming that the proper CDR/CAR services are running and
that the proper options in the service parameters/Enterprise parameters are selected in your cluster,such as:


CDR File Time Interval = 1
Cluster ID = StandAloneCluster


-Service Parameters (Service: Cisco CallManager):


Configure the following parameters on all the callmanager servers in your
cluster:


CDR Enabled Flag = True
CDR Log Calls with Zero Duration Flag = True Call Diagnostics Enabled =
Enabled Regardless of CDR Enabled Flag



So if all the above options are selected in your cluster and you are still
unable so run a query from the car gui, then the first thing to do is
to restart the following network services in all your nodes, in the following order
before moving to the next steps.


Cisco Database Layer Monitor
Cisco CDR Repository Manager
Cisco CDR Agent
Cisco CAR Scheduler


after restarting the above services I will suggest you to wait at least until the
01:00 hrs to the next day before running a query from the car gui. Now if you still
unable to run a query from the car gui after doing the all of the above steps, its time
for us to find out if CDR is indeed collecting and producing records,to do this go to the CLI
and issue the following commands:


admin:file list activelog cm/cdr_repository/car/


The output of the above command will be the following


admin:file list activelog cm/cdr_repository/car/
<dir> 20081218
<dir> 20081219
<dir> 20081220
<dir> 20081221
<dir> 20081222
<dir> 20081223
<dir> 20081224
<dir> 20081225
<dir> 20081226
<dir> 20081227
<dir> 20081228
<dir> 20081229
<dir> 20081230
<dir> 20081231
<dir> 20090101
<dir> 20090102
<dir> 20090103
<dir> 20090104
<dir> 20090105
<dir> 20090106
<dir> 20090107
<dir> 20090108
<dir> 20090109
<dir> 20090110
<dir> 20090111
<dir> 20090112
<dir> 20090113
<dir> 20090114
<dir> 20090115
<dir> 20090116
<dir> 20090117
<dir> 20090118
dir count = 32, file count = 0
admin:


As we can see above each directory represents a day of collection, now we need to know
if we have files inside each directory, if indeed CDR is collecting information, we should
see files inside each directory, a file inside each folder will represent about 1 or 2 min of collection.
to do this will issue the following command:


For example we will take a look at date 20090117


admin:file list activelog cm/cdr_repository/car/20090117


The output will be the following:


admin:file list activelog cm/cdr_repository/car/20090117
cdr_PUBLISHERNAME-Cluster_01_200901170000_6812
cdr_PUBLISHERNAME-Cluster_01_200901170001_6821
cdr_PUBLISHERNAME-Cluster_01_200901170002_6790
cmr_PUBLISHERNAME-Cluster_01_200901170000_6713
cmr_PUBLISHERNAME-Cluster_01_200901170001_6714
cmr_PUBLISHERNAME-Cluster_01_200901170002_6715
cmr_PUBLISHERNAME-Cluster_01_200901170003_6716
cmr_PUBLISHERNAME-Cluster_01_200901170004_6717
cmr_PUBLISHERNAME-Cluster_01_200901170005_6718
cmr_PUBLISHERNAME-Cluster_01_200901170006_6719




As you can see above, CDR is indeed collecting data starting at 0000 hours on date 20090117
so far we know that data is being collected but we are unable to see it via the car gui,
at this point we could either get a file exported to an sftp server or we can actually see it
raw in the cli, to see the contents of a file we need to use the following command.


For example lets take a look at the following file which represents collection date 20090117 and
time 1333 hours


admin:file view activelog cm/cdr_repository/car/20090117/cmr_PUBLISHERNAME_03_200901171333_4040


The output will be the following:



admin:file view activelog cm/cdr_repository/car/20090117/cmr_PUBLISHERNAME-Cluster_03_200901171333_4040


"cdrRecordType","globalCallID_callManagerId","globalCallID_callId","nodeId","directoryNum","callIdentifier","dateTimeStamp","numberPacketsSent","numberOctetsSent","numberPacketsReceived","numberOctetsReceived","numberPacketsLost","jitter","latency","pkid","directoryNumPartition","globalCallId_ClusterID","deviceName","varVQMetrics"
INTEGER,INTEGER,INTEGER,INTEGER,VARCHAR(50),INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,UNIQUEIDENTIFIER,VARCHAR(50),VARCHAR(50),VARCHAR(129),VARCHAR(600)
2,3,39739,3,"2755",61245505,1232199149,5282,908504,5278,907816,0,1,0,"d371996a-aee3-41f1-9d7a-6574bd7bc4ac","ANY-Internal_PT","PUBLISHERNAME-Cluster","SEP0015FA1CBC12","MLQK=4.5000;MLQKav=4.5000;MLQKmn=4.5000;MLQKmx=4.5000;MLQKvr=0.95;CCR=0.0000;ICR=0.0000;ICRmx=0.0000;CS=0;SCS=0"


end of the file reached
options: q=quit, n=next, p=prev, b=begin, e=end (lines 1 - 3 of 3)
admin:


Ok we have now confirmed that cdr is collecting data as suppose to, next we will check the CAR preferences, and look for
the min date max date, etc


To do this, issue the following command



admin:run sql select * from car:tbl_system_preferences


The output will be the following


admin:run sql select * from car:tbl_system_preferences
param_name param_value
========================= ========================================
MIN_DATE 01/01/1970
MAX_DATE 01/01/1970
CDR_MIN_DATE 01/01/1970
CDR_MAX_DATE 01/01/1970
MAX_CDR_NUMBER 2000000
MAX_ERROR_RECORD_ID 1
COMPANY_NAME YOUR COMPANY NAME
TOLL_FREE 1800,1855,1866,1877,1888
CHARGELIMIT 200.00
GOOD 20.00
POOR 30.00
DEFAULT_CAR_USER _unspecifieduser
LOADER_STATUS 1
CONTINUOUS_LOADING_24_7 1
LOAD_CDR_ONLY 1
MANUAL_PURGE_STATUS 0
LOADER_SCHEDULE_BACKUP DailyCdrLoad,L,1440,-1,00:00:00,0,300,30
PURGE_LOW_WATER_MARK 80
PURGE_HIGH_WATER_MARK 90
MIN_CAR_DATABASE_AGE 30
MAX_CAR_DATABASE_AGE 60
LAST_PROCESSING_DIRECTORY
LAST_PROCESSING_FILE
LAST_PROCESSING_DATA_ROW
UPDATE_STATISTICS_DATE 01/17/2009,0
LOADER_BATCH 600,600,2500,3000
INSTALLATION_DATE 1/16/2009
admin:


As you can see above the MIN_DATE, MAX_DATE, CDR_MIN_DATE, CDR_MAX_DATE are set to 01/01/1970
First and forth most we will change the company name to the name of our company , to do this
we need to issue the following command (changinge the name of the company is not a necessary troubleshooting step
I just wanted to show you that any of the parameters can be modified)



admin:run sql update car:tbl_system_preferences set param_value='COLEMAN TECHNOLOGIES' where param_name='COMPANY_NAME'


the output will be the following


admin:run sql update car:tbl_system_preferences set param_value='COLEMAN TECHNOLOGIES' where param_name='COMPANY_NAME'
Rows: 1
admin:


Now we will issue the following command to verify our changes


admin:run sql select * from car:tbl_system_preferences


The output is the following


admin:run sql select * from car:tbl_system_preferences
param_name param_value
========================= ========================================
MIN_DATE 01/01/1970
MAX_DATE 01/01/1970
CDR_MIN_DATE 01/01/1970
CDR_MAX_DATE 01/01/1970
MAX_CDR_NUMBER 2000000
MAX_ERROR_RECORD_ID 1
COMPANY_NAME COLEMAN TECHNOLOGIES
TOLL_FREE 1800,1855,1866,1877,1888
CHARGELIMIT 200.00
GOOD 20.00
POOR 30.00
DEFAULT_CAR_USER _unspecifieduser
LOADER_STATUS 1
CONTINUOUS_LOADING_24_7 1
LOAD_CDR_ONLY 1
MANUAL_PURGE_STATUS 0
LOADER_SCHEDULE_BACKUP DailyCdrLoad,L,1440,-1,00:00:00,0,300,30
PURGE_LOW_WATER_MARK 80
PURGE_HIGH_WATER_MARK 90
MIN_CAR_DATABASE_AGE 30
MAX_CAR_DATABASE_AGE 60
LAST_PROCESSING_DIRECTORY
LAST_PROCESSING_FILE
LAST_PROCESSING_DATA_ROW
UPDATE_STATISTICS_DATE 01/17/2009,0
LOADER_BATCH 600,600,2500,3000
INSTALLATION_DATE 1/16/2009
admin:


Ok now we need to fix our dates, because otherwise we would never be able to see any cdr data
via the car gui.


We will change the dates in order, starting from MIN_DATE to CDR_MAX_DATE


admin:run sql update car:tbl_system_preferences set param_value='01/01/2009' where param_name='MIN_DATE'
Rows: 1
admin:


To verify our changes we will issue the following command



admin:run sql select * from car:tbl_system_preferences
param_name param_value
========================= ========================================
MIN_DATE 01/01/2009 <--------
MAX_DATE 01/01/1970
CDR_MIN_DATE 01/01/1970
CDR_MAX_DATE 01/01/1970
MAX_CDR_NUMBER 2000000
MAX_ERROR_RECORD_ID 1
COMPANY_NAME COLEMAN TECHNOLOGIES
TOLL_FREE 1800,1855,1866,1877,1888
CHARGELIMIT 200.00
GOOD 20.00
POOR 30.00
DEFAULT_CAR_USER _unspecifieduser
LOADER_STATUS 1
CONTINUOUS_LOADING_24_7 1
LOAD_CDR_ONLY 1
MANUAL_PURGE_STATUS 0
LOADER_SCHEDULE_BACKUP DailyCdrLoad,L,1440,-1,00:00:00,0,300,30
PURGE_LOW_WATER_MARK 80
PURGE_HIGH_WATER_MARK 90
MIN_CAR_DATABASE_AGE 30
MAX_CAR_DATABASE_AGE 60
LAST_PROCESSING_DIRECTORY
LAST_PROCESSING_FILE
LAST_PROCESSING_DATA_ROW
UPDATE_STATISTICS_DATE 01/17/2009,0
LOADER_BATCH 600,600,2500,3000
INSTALLATION_DATE 1/16/2009
admin:


Now we will proceed to change the MAX_DATE,CDR_MIN_DATE, CDR_MAX_DATE respectively


admin:run sql update car:tbl_system_preferences set param_value='01/01/2012' where param_name='MAX_DATE'
Rows: 1
admin:run sql update car:tbl_system_preferences set param_value='01/01/2009' where param_name='CDR_MIN_DATE'
Rows: 1
admin:run sql update car:tbl_system_preferences set param_value='01/01/2012' where param_name='CDR_MAX_DATE'
Rows: 1
admin:


Now we will verify our changes


admin:run sql select * from car:tbl_system_preferences
param_name param_value
========================= ========================================
MIN_DATE 01/01/2009 <---------------
MAX_DATE 01/01/2012 <---------------
CDR_MIN_DATE 01/01/2009 <---------------
CDR_MAX_DATE 01/01/2012 <---------------
MAX_CDR_NUMBER 2000000
MAX_ERROR_RECORD_ID 1
COMPANY_NAME COLEMAN TECHNOLOGIES
TOLL_FREE 1800,1855,1866,1877,1888
CHARGELIMIT 200.00
GOOD 20.00
POOR 30.00
DEFAULT_CAR_USER _unspecifieduser
LOADER_STATUS 1
CONTINUOUS_LOADING_24_7 1
LOAD_CDR_ONLY 1
MANUAL_PURGE_STATUS 0
LOADER_SCHEDULE_BACKUP DailyCdrLoad,L,1440,-1,00:00:00,0,300,30
PURGE_LOW_WATER_MARK 80
PURGE_HIGH_WATER_MARK 90
MIN_CAR_DATABASE_AGE 30
MAX_CAR_DATABASE_AGE 60
LAST_PROCESSING_DIRECTORY
LAST_PROCESSING_FILE
LAST_PROCESSING_DATA_ROW
UPDATE_STATISTICS_DATE 01/17/2009,0
LOADER_BATCH 600,600,2500,3000
INSTALLATION_DATE 1/16/2009
admin:



Before running another query via the car gui, we need to do the following


-Restart the following network services in the following order


-Wait until 01:00hrs the next day.


Cisco Database Layer Monitor
Cisco CDR Repository Manager
Cisco CDR Agent
Cisco CAR Scheduler


This document was created by Cesar Fiestas

 

Cesar Fiestas
Network Engineer

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close