Is there any place where they list how many routes the ASR9K will handle,
granted most of the current goodness is too rich for my blood, but stuff
like the RSP4G and RSP8G are pretty easy to come by. I thought I saw
something saying they were limited to say 512K routes, but I may be thinking
of
On 5/Jul/16 16:29, Eric Van Tol wrote:
> FYI, we upgraded to this version last week on several of our ASRs. Since
> then, we've had two 'lock-ups'. ISIS, BFD, and LDP all establish (albeit
> inconsistently) and even ISIS database is populated, but no LDP label
> advertisement occurs. Pings to
Hi Everyone,
We (currently) create a new vpdn-group every time a new LAC is enabled(bought
online) by one of our DSL providers - Cumbersome, and if we miss the e-mail
notification from them, any DSL services initiating connections from the new
LAC are rejected by our LNSas the password for
Don't get me started on Cisco versioning. It drives me nuts.
The documentation on the ASR1K seems to be better than the ASR9K.
A lot of the 9K documentation is posting on the support forum by ASR9K team
members.
As for mac accounting on the ASR1K, I haven't had any use for it myself so I
can't s
The spec sheet isn't really clear.
On the 2T it is 1M which is quite constraining.
If it is actually 2M then it would be fine as eventually IPv4 will die and IPv6
is going to have less prefixes.
Mack McBride | Senior Network Architect | ViaWest, Inc.
O: 720.891.2502 | C: 303.720.2711 | mack.mcbr
I found solution to fix timestamp:
I have added following to as per Peter said.
collect timestamp sys-uptime first
collect timestamp sys-uptime last
and change export fron ipfix to v9
Now i can see correct timestamp on Nfsen :)
On Sun, Jul 3, 2016 at 7:16 PM, Peter Rathlev wrote:
> On Fri,
Hi,
On Tue, Jul 05, 2016 at 08:15:41PM +, Mack McBride wrote:
> The Sup6T is still TCAM limited.
> We are moving to ASR9Ks.
This was our plan, but right now the platform annoys me somewhat
(MAC accounting is not reliable, and no MAC addresses in netflow
whatsoever - you want at least one of
Regarding TCAM ... Data sheets are a little confusing in this regard, some
parts indicate "2M FIB TCAM Entries" some imply a 1M FIB limit. If it is a
2M FIB limit, It seems unlikely you would exhaust that limit in the next 10
years.
Peter Kranz
www.UnwiredLtd.com
Desk: 510-868-1614 x100
Mobile: 51
Thanks!! i tried that "collect timestamp sys-uptime first" and "last"
but didn't work,
Now i am trying to enable "NetFlow Version 5" but i am seeing
following in monitor, does v5 supported on ASR1006?
Flow Exporter: netflow-exporter (inactive)
R1#show flow monitor netflow-monitor
Flow Monit
The Sup6T is still TCAM limited.
We are moving to ASR9Ks.
But we have used the ASR1Ks where we need full netflow capture with great
success.
The port density and total throughput is not as high as the 6500 though.
Mack McBride | Senior Network Architect | ViaWest, Inc.
O: 720.891.2502 | C: 303.7
That code is definitely subject to memory leaks.
Specifically if you have a shut down BGP session.
That is also in some revs of SXI.
Later revs tend to have fewer bugs since they are mostly patching bugs.
Mack McBride | Senior Network Architect | ViaWest, Inc.
O: 720.891.2502 | C: 303.720.2711 |
Depending on specific code revision it may require a reboot.
Some code revs are worse than others.
Mack McBride | Senior Network Architect | ViaWest, Inc.
O: 720.891.2502 | C: 303.720.2711 | mack.mcbr...@viawest.com | www.viawest.com
-Original Message-
From: cisco-nsp [mailto:cisco-nsp-b
O'Connor, Michael wrote:
> also i am getting this error when starting nfsen do you have any idea?
>
> Starting nfcapd:(r1)[8882]
> Starting nfsendSubroutine Lookup::pack_sockaddr_in6 redefined at
> /usr/share/perl5/vendor_perl/Exporter.pm line 66.
> at /data/nfsen/libexec/Lookup.pm line 43.
> Su
hi,
On Tue, Jul 05, 2016 at 10:54:47AM -0700, Peter Kranz wrote:
> There is also the option of jumping to a used SUP2T or a SUP6T in your 6500
> chassis. Depending on the line cards you have, you might have to replace
> some of them.
Has anyone tried 6T yet? Does it do useful netflow?
2T had gr
There is also the option of jumping to a used SUP2T or a SUP6T in your 6500
chassis. Depending on the line cards you have, you might have to replace
some of them.
Peter Kranz
www.UnwiredLtd.com
Desk: 510-868-1614 x100
Mobile: 510-207-
pkr...@unwiredltd.com
-Original Message-
From: cis
For a non-cisco option, the new Arista 7280R is somewhat interesting.
Handles BGP full tables, has great port density, relatively affordable.
Peter Kranz
www.UnwiredLtd.com
Desk: 510-868-1614 x100
Mobile: 510-207-
pkr...@unwiredltd.com
-Original Message-
From: cisco-nsp [mailto:cisco-
also i am getting this error when starting nfsen do you have any idea?
Starting nfcapd:(r1)[8882]
Starting nfsendSubroutine Lookup::pack_sockaddr_in6 redefined at
/usr/share/perl5/vendor_perl/Exporter.pm line 66.
at /data/nfsen/libexec/Lookup.pm line 43.
Subroutine Lookup::unpack_sockaddr_in6 re
Hello,
I need to transport some double-tagged customers from SiteA to SiteB
through a GbE link and to rewrite S-VLANs so that those I use on the
aggregation-side interface are different from those I receive on the
customer facing port.
customers aggre
> I'd recommend anyone running an ASR920, particularly one adjacent to a
> Junos-based device, upgrades to this code to avoid pain.
>
FYI, we upgraded to this version last week on several of our ASRs. Since then,
we've had two 'lock-ups'. ISIS, BFD, and LDP all establish (albeit
inconsistently)
On 05/07/16 13:48, Christina Klam wrote:
When we did the tcpdumps, we saw the correct timestamps being sent.
Yet, nfsen was only showing the epoch date. This was on our 4500X & our
N7Ks.
Probably need to post on the nfsen list then. More than likely a bug in
decoding the particular TLV used
>
> I think it's unlikely ASR1k has that issue, but OP could test; capture
> the packets, examine/decode in Wireshark, compare known test traffic w/
> good wall-clock timestamps against the values in the flow. Need to be
> sure you capture the template records too.
>
> If the in-packet flow ti
On 04/07/16 23:00, Mark Tinka wrote:
On 4/Jul/16 15:29, Chris Welti wrote:
I can confirm that the bug has been fixed in 03.18.01.S / 15.6(2)S1 which is
now out on CCO.
Caution, after the first reload when you upgrade from a previous version, there
will be a FPGA upgrade and thus a second (aut
22 matches
Mail list logo
