Preview Tool

Cisco Bug: CSCus78854 - Intracer not able to parse 3gpp xml files form user defined trace folder

Last Modified

Dec 25, 2016

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases


Description (partial)

On Intracer GUI user has option to configure FTP Path under "	Trace Profile Configuration" section but if operator mentions the "FTP Path" other then "tracedata" directory path (i.e. [R-TCE server home path]//data/TCE/[R-TCE Server name]/events/tracedata/) R-TCE is not able to process those 3gpp xml files received from Gateways.

Reproduce Step:
1: Login to Intracer and navigate to Configure > R-TCE > New.
2: Configure all mandatory fields. Make sure you disable "Profile for 7600 Platform ". While configuring "Profile for ASR5000 Platform" section put a different path other then "tracedata" directory path in "FTP Path" field. For example say "/manas/events".
3:Save TCE configuration by clicking the save button.
4: Activate a management trace for a subscriber. (trace > 3gpp trace > Active Traces > New Activation)
5: Create a session for the subscriber.
6:On Gateway side see if the session created successfully and xml files are transferred to the mentioned FTP Path.
7:Now check if the xml are pushed to the FTP Path of the R-TCE server.
8: Verify if the XMLs are processed and deleted successfully.

Test Result:
XML are not processed and kept as it is in that configured FTP Path.
drwxrwxrwx 3 manas manas 4096 Feb  4 15:34 events
[manas@appsucs210-07 ~]$ ls -l /manas/events/
total 8
drwxrwxr-x 2 manas manas 4096 Feb  4 15:35 tce_0
[manas@appsucs210-07 ~]$ ls -l /manas/events/tce_0
total 40
-rw-r--r-- 1 manas manas 1868 Feb  4 15:35 A20150204.1533+0530-PGW.nc11.234156000237.1
-rw-r--r-- 1 manas manas 5583 Feb  4 15:34 A20150204.1533+0530-PGW.nc11.234156000237.1-1
-rw-r--r-- 1 manas manas 2109 Feb  4 15:34 A20150204.1533+0530-PGW.nc11.234156000237.1-2
-rw-r--r-- 1 manas manas 4775 Feb  4 15:35 A20150204.1534+0530-PGW.nc11.234156000237.1
[manas@appsucs210-07 ~]$
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.