Billing Server收不到CDR数据，分几种情况：
Sub未生成CDR数据（Sub：at /var/log/active/cm/cdr ）
Sub未成功向Pub发送CDR数据：/var/log/active/cm/cdr_repository/preserve
Pub和Billing Server传输CDR失败：/var/log/active/cm/cdr_repository/destination [1/2/3]
如果是Sub未向Pub传CDR数据，则在Pub的cdr_repository/preserve/xxxx年xx月xx日文件夹里是没有CDR数据的：
从CUCM CLI里：file list activelog /cm/cdr_repository/preserve/20110106 看不到数据。
这时需要RTMT抓CDR Agent Log，如下是Log里的报错信息：
2017-07-07 11:03:01,065 DEBUG [main] sftpapi.ftpClient (ftpClient.java:193) - connect(): connect for SFTP
2017-07-07 11:03:01,071 DEBUG [main] sftpapi.SFTPConnection (SFTPConnection.java:67) - Inside the SFTPConnection Constructor
2017-07-07 11:03:01,071 DEBUG [main] sftpapi.SFTPConnection (SFTPConnection.java:273) - checkConnection for Publisher using Key Authentication-->
2017-07-07 11:03:01,071 DEBUG [main] sftpapi.SFTPConnection (SFTPConnection.java:274) - checkConnection: UserName : ccmservice
2017-07-07 11:03:01,071 DEBUG [main] sftpapi.SFTPConnection (SFTPConnection.java:275) - checkConnection: hostname : 10.14.149.27
2017-07-07 11:03:01,094 DEBUG [main] sftpapi.SFTPConnection (SFTPConnection.java:288) - Trying to connect to the SFTP server.
2017-07-07 11:03:01,108 ERROR [main] sftpapi.SFTPConnection (SFTPConnection.java:315) - error Making SFTP connectioninvalid privatekey: [B@110ba23
Workaround：
Workaround for Defect
CSCug55011: CDR file transfer fails in FIPS mode The following are the steps for applying a workaround for the defect to each node in a cluster. The workaround needs remote support account to be enabled and needs to be applied as the remote support user. Hence this work around needs to be executed by Cisco TAC only. And the document is intended for Cisco TAC use only. 1.Enable remote support account on the affected nodes. 2.Login as the remote support account into the affected nodes. 3.Edit the fips config file using vi /usr/local/platform/conf/fips.cnf 4.Change the value in the file from 1 to 0. Save file and exit. 5.Convert the SSH private key format for ccmservice user using the command /usr/local/platform/bin/openssl dsa -in /home/ccmservice/.ssh/id_dsa -outform PEM -out /home/ccmservice/.ssh/id_dsa 6. Edit the fips config again to change the value back to 1 from 0 vi /usr/local/platform/conf/fips.cnf save and exit. Steps to verify CDR Agent Service while performing workaround :- 1.Stop CDR Agent Service in subscriber. 2.Check CDR flat file count under /var/log/active/cm/cdr/ location with the following command. ls l | wc l 3.Please check if cdr files older than 30 days are present in the above mentioned location. CDR flat file format is below from which the date of generation of the CDR file can be figured out. cdr_StandaloneCluster_08_YYYYMMDD0343_94657 4.Publisher CDR Repository Manager will keep last 30 days cdr record, so if CDR Agent Service starts to transfer the CDR files to publisher, older than 30 days cdr flat files will be discarded and also the same will be deleted from subscriber. Please check with customer if these old cdr files need to be backed up prior. 5.Once done, please start the CDR Agent service in subscriber. 6.Keep the trace level to DEBUG for this service, so that for any issue further we have the detailed logs which will be present under /var/log/active/cm/trace/cdragent/log4j/ location.
解决方法总结：系统中了一个Bug：
CSCug55011。需要向TAC开Case，申请 CLI root权限，进入底层改FIPS模式。
