Cisco Bug: CSCus80831 - Profile on gateway in not being deleted after deleting a R-TCE server.
Dec 26, 2016
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: While configuring R-TCE one profile is being created on the respective Gateways. This profile on GW should be deleted after successful deletion of this R-TCE server OR if the operator remove the respective gateway from the R-TCE server. Currently after deleting the R-TCE server respective profile is not deleted from GW and this issue is happening only after re-login. Impact: Operator can't add R-TCE as the entries on GW side is there and GUI will show error while adding R-TCE server. (Error: Cannot modify existing trace configuration (error 2) for NE <NE name>) Conditions: Reproduce Steps : 1. Login to InTracer UI and navigate to Configure -->R-TCE --> New 2. Fill all mandatory fields and add the R-TCE server by clicking the save button. 3. Verify if the details are saved successfully on InTracer GUI as well as on postgress database.i.e. see "from lte_traceprofileinfo" table Ex. ipmsdb=# select * from lte_traceprofileinfo; 4. Verify on gateway side if the profile is created or not. Ex: [local]nc11# show config | grep tce session trace network-element pgw tce-mode push transport sftp path /manas/ username manas encrypted password +A2cx2dhvzmdh6p1frp7oxxac5ez3enwuauvo17z60rh2pzvyzsh9e collection-timer 30 5. Logout and re-login to Intracer GUI and navigate to Configure -->R-TCE. 6. Select the R-TCE and click on delete button. 7. Verify GUI , Postgress DB and GW config if the profile is deleted successfully or not.
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