--- Begin Message ---
On 24/01/2019 6:23 am, Giles Coochey wrote:
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...
The thing that sends me off the deep end with bugs
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
--- Begin Message ---
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
...answering to Lucas and James:
We have EXACTLY the same behavior. And it's worrying that the bug notes
do not include all this info.
We have hundreds of these boxes in our networks but just recently we
approached this time limit.
Until now ALL the boxes that have passed the time limit have
>
> Has anyone been hit by CSCvk35460?
We have definitely been hit by this bug on two ASR920s running 03.16.02aS with
over 2 years of uptime.
The symptoms and effect of the bug from our observation include:
- packets continue to forward, so there is no immediate disruption to traffic
-
Hello,
On Wed, 23 Jan 2019 at 13:37, Tassos Chatzithomaoglou
wrote:
>
>
> Has anyone been hit by CSCvk35460?
>
> Symptom:
> counter not increasing under show interface even though packets are
> being forwarded normally
>
> Conditions:
> ASR920 is running for nearly 889 days
>
> Workaround:
>
Has anyone been hit by CSCvk35460?
Symptom:
counter not increasing under show interface even though packets are
being forwarded normally
Conditions:
ASR920 is running for nearly 889 days
Workaround:
none
It seems strange that Cisco has terminated it as non-reproducible,
unless all customers
