Guest

Preview Tool

Cisco Bug: CSCvu69047 - Doc-Defect - NPI EDCS-1515041 -logs for Scalar Fetch - Trap body won't be present in any of the logs

Last Modified

Jul 07, 2020

Products (1)

  • Cisco Unified SIP Proxy

Known Affected Releases

9.1(8)

Description (partial)

Symptom:
http://frankenberry.cisco.com/ppt_files/converted/1397359443%20(Web)/ 

- Slide 28 , 29 talk about

"No new debugs commands are introduced as part of SNMP feature
?trace snmp all &  trace management all? command will fetch the logs related to SNMP
Logs will be part of atrace.log" 

But in the Slide 29 , when they talk about the SNMP Trace log for Scalar Fetch , the output shown there looks like output from "atrace.log" 

We got confirmation from DE , that 

"Trap body won't be present in any of the logs because that defeats the purpose of having a trap listener configured. For the fetches, one needs to have the snmpclient/NMS where CUSP's IP can be used to fetch the MIB data"

Reference JIRA https://jira-eng-sjc12.cisco.com/jira/browse/CUSP-94 

Need to correct this , or keep this defect so there is a clarity on this for future cases.

Conditions:
http://frankenberry.cisco.com/ppt_files/converted/1397359443%20(Web)/ 

- Slide 28 , 29 talk about

"No new debugs commands are introduced as part of SNMP feature
?trace snmp all &  trace management all? command will fetch the logs related to SNMP
Logs will be part of atrace.log" 

But in the Slide 29 , when they talk about the SNMP Trace log for Scalar Fetch , the output shown there looks like output from "atrace.log" 

We got confirmation from DE , that 

"Trap body won't be present in any of the logs because that defeats the purpose of having a trap listener configured. For the fetches, one needs to have the snmpclient/NMS where CUSP's IP can be used to fetch the MIB data"

Reference JIRA https://jira-eng-sjc12.cisco.com/jira/browse/CUSP-94 

Need to correct this , or keep this defect so there is a clarity on this for future cases.
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.