d memory is released.
From: Erik Sundberg <esundb...@nitelusa.com>
Sent: Friday, 3 June 2016 5:41 AM
To: CiscoNSP List; Mark Tinka; James Jun
Cc: cisco-nsp@puck.nether.net
Subject: RE: [c-nsp] ASR920 - Any "outstanding" TAC cases people are working
through?
We have been using ASR92
On 2/Jun/16 21:41, Erik Sundberg wrote:
> We have been using ASR920's for a couple months now.
>
> I have an outstanding Memory leak issue in
> asr920-universalk9_npe.03.16.01a.S.155-3.S1a-ext.bin
>
> https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuy87268
>
> The work around doesn't work for
CiscoNSP List
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] ASR920 - Any "outstanding" TAC cases people are working
through?
On 26/May/16 06:23, James Jun wrote:
> I believe there is an mpls label-range bug that Mark noted (CSCuy29638) which
> is outstanding, but that can
cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] ASR920 - Any "outstanding" TAC cases people are working
through?
On 26/May/16 06:23, James Jun wrote:
> I believe there is an mpls label-range bug that Mark noted (CSCuy29638) which
> is outstanding, but that can be worked around
On 26/May/16 06:23, James Jun wrote:
> I believe there is an mpls label-range bug that Mark noted (CSCuy29638) which
> is outstanding, but that can be worked around by staying out of high label
> range.
Actually, Cisco normally allocate low-range labels. So this is fine if
the box adjacent
On Wed, May 25, 2016 at 09:54:11AM +, CiscoNSP List wrote:
>
> Just reading through all the recent threads, and as we are about to deploy a
> number of these boxes in production, wanted to be 100% on any potential
> issues we may face (couple of recent posts, mention ASR920, ISIS stopping
2016 7:24 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] ASR920 - Any "outstanding" TAC cases people are working
through?
Hi Everyone,
Just reading through all the recent threads, and as we are about to deploy a
number of these boxes in production, wanted to be 100% on any potential
Hi Everyone,
Just reading through all the recent threads, and as we are about to deploy a
number of these boxes in production, wanted to be 100% on any potential issues
we may face (couple of recent posts, mention ASR920, ISIS stopping working(And
routing unexpectedly), and reboot "resolves"
