Guest

Preview Tool

Cisco Bug: CSCup20324 - Consequences if IDP upload flag set to 0

Last Modified

Sep 04, 2018

Products (1)

  • Network Level Service

Known Affected Releases

2.18(2)

Description (partial)

Symptom:
Fields challenges :
Collector team needs the flag to set to 0 in various field scenarios:
- Changes made in collection during both Deployment/Day-2 need to be tested while on customer call instead of waiting for weeks for the next upload
Support Challenges:
If IDP upload flag set to 0 then it may overload the SNTC backend system .
Id IDP upload flag set to 0 then XPT may get 2 uploads within some  mins gap  will start for   re-trying. due to which   rpt_cir table the data may not get populated and as a result the custom inventory report will not have nay data (please refer CDET-CSCun65259 for more information ).

Conditions:
If IDP upload flag set to 0 then it may overload the SNTC backend system.
Id IDP upload flag set to 0 then XPT may get 2 uploads within some minutes gap  will start for   re-trying. due to which   rpt_cir table the data may not get populated and as a result the custom inventory report will not have any  data (please refer CDET-CSCun65259 for more information ).
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)
  • 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.