Cisco Bug: CSCuw24274 - Compressed CDR's written with wrong timestamp in HDD during PSC Migration
May 21, 2018
- Cisco ASR 5000 Series
- Cisco ASR 5500
Known Affected Releases
18.0.0.private 18.4.M0.61271 19.4.M0.63997 19.4.M0.64002 21.4.2 21.5.0 21.6.0
Compressed CDR's written with wrong timestamp in HDD during PSC Migration Symptom: 1. 2 CDR files are generated during the PSC Migration, one without compression and one with compression. 2. On Every Subsequent PSC Migration Timestamp of the already existing compressed file in HDD is updated to the latest timestamp value. Timestamp will be updated only for the compressed CDR Files for which uncompressed version is also present in HDD. Conditions: 1. Configure GTPP group with following configuration having local storage mode and file rotation based on time interval: gtpp group gtpp_pgw gtpp attribute node-id-suffix PGW_NH-SAE-01 gtpp attribute served-pdp-pdn-address-extension gtpp dictionary custom24 gtpp egcdr service-idle-timeout 86400 gtpp storage-server mode local gtpp storage-server local file purge-processed-files gtpp storage-server local file compression gzip gtpp storage-server local file format custom5 gtpp storage-server local file rotation time-interval 120 gtpp storage-server local file name prefix PGW_NH-SAE-01 gtpp storage-server local file name format %Y%m%d%H%M%S_%6N_%6Q 2. Bring up calls so that CDR generation happens at regular time intervals 3. Perform PSC Migration when the CDR rotation happens due to time-interval. 4. Both Compressed and uncompressed files will be generated in HDD ,during PSC Migration. 5. On subsequent Migration, Timestamp of compressed CDR Files will be updated since uncompressed version of the CDR File is also present in HDD.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases