Re: [c-nsp] ASR1002 -- interface stops passing IPv4 traffic?

I've hit this CSCva35619 so that matches up. Upgraded at the time to 03.16.04a extended support release. Worked perfectly! Forwarding correctly ever since Sent from my portable email sender Please excuse shorter messages > On 19/05/2017, at 21:09, Paul Sherratt wrote: > >

Re: [c-nsp] ASR1002 -- interface stops passing IPv4 traffic?

Thanks Paul -- this appears to be the exact issue. I just didn't have enough experience with the platform to know to look here. John On Fri, May 19, 2017 at 12:09:18PM +0100, Paul Sherratt wrote: > Hi John, > > This sounds like it may be an input queue wedge on the interface, which is

Re: [c-nsp] ASR1002 -- interface stops passing IPv4 traffic?

Hi John, This sounds like it may be an input queue wedge on the interface, which is only fixed with a reload. I've seen CVE-2016-1478 / CSCva35619 hit a few people. If you're running an affected version you'll need to upgrade or workaround. To verify, check queue size in "show interface"

Re: [c-nsp] ASR1002 -- interface stops passing IPv4 traffic?

Hi John, Unfortunately we have seen several examples of this on the ASR9k platform with partial NP microcode lockups. Almost every case relates to us using more than 2 or 3 'features' per physical interface (like Sampled Netflow + Mirror First 64 bytes + Sub Interfaces + CBQoS). These may not