[c-nsp] ASR920 is a ticking timebomb (CSCvk35460)

[Giles Coochey]

On 23/01/2019 16:59, David White, Jr. (dwhitejr) via cisco-nsp wrote:
> Hi All,
>
> Sorry to hear you are being impacted by this issue.  I took a look at 
> the bug, and it is in a holding pattern, waiting until we can get some 
> logs from an impacted device - in order to root cause it.  Can I ask 
> that anyone impacted please open a TAC case so they can assist with 
> getting the necessary logs to make forward progress?
>
> Thanks much,
>
> David White
> Cisco TAC 


So part of the nature of the issue, is it is unlikely that anyone will 
have logs to the severity level needed running (out-of-hand) after 880 
days or so of uptime. You might be better assured of getting further 
information asking existing customers with uptimes of 880+ days plus to 
enable debug logging to a remote syslog host for a time.

Perhaps consider gathering further info - e.g. what counter values have 
been reached, any value correlations between customers etc...

I think the tack the OP was meant to imply that Cisco Bughunt for issues 
leaves a lot to be desired, with terse messages attached to bugs, 
incomplete versions affected, etc...