List
Sent: Sunday, October 30, 2016 4:31 PM
To: Joseph Mays ; Chris Boyd ; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Router memory problem
Very bleary eyed - but shouldnt this:
ip prefix-list max23 seq 5 permit 0.0.0.0/0 ge 8 le 16
be:
ip prefix-list max16 seq 5 permit 0.0.0.0/0 ge 8
: cisco-nsp on behalf of Joseph Mays
Sent: Thursday, 27 October 2016 7:06 AM
To: Chris Boyd; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Router memory problem
> On the plus side, if you screw up routing with a mistake, you'll free a lot
> of memory :-/
See, there could be a si
Justin Krejci wrote:
> We use prefix-lists (not ACL) in our route-maps, BGP filtering, etc
> but I am curious what is wrong with distribute-lists specifically. Is
> it just that they are old and less efficient CPU-wise or something?
> Are there known bugs in certain use cases?
distribute lists are
On 27/Oct/16 21:54, Justin Krejci wrote:
> We use prefix-lists (not ACL) in our route-maps, BGP filtering, etc but I am
> curious what is wrong with distribute-lists specifically.
> Is it just that they are old and less efficient CPU-wise or something? Are
> there known bugs in certain use cas
: Nick Cutting [ncutt...@edgetg.com]
Sent: Thursday, October 27, 2016 1:54 PM
To: Jared Mauch; Justin Krejci
Cc: cisco-nsp@puck.nether.net
Subject: RE: [c-nsp] Router memory problem
We had a case where we used distribute lists matching prefix lists, but some
engineers were forgetting the keyword
o-nsp-boun...@puck.nether.net] On Behalf Of Jared
Mauch
Sent: Thursday, October 27, 2016 2:46 PM
To: Justin Krejci
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Router memory problem
On Thu, Oct 27, 2016 at 05:37:35PM +, Justin Krejci wrote:
> What is wrong with distribute-lists?
You sh
On Thu, Oct 27, 2016 at 05:37:35PM +, Justin Krejci wrote:
> What is wrong with distribute-lists?
You should be using a prefix-list,
as it was designed for this type of function.
distribute-lists (and a bunch of other IOS
crutches) should go away as part of the legacy.
] Router memory problem
On 26/Oct/16 22:06, Joseph Mays wrote:
>
> router bgp
> distribute-list prefix max16 in
You really shouldn't be using distribute lists.
Mark.
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://p
On 26/Oct/16 22:06, Joseph Mays wrote:
>
> router bgp
> distribute-list prefix max16 in
You really shouldn't be using distribute lists.
Mark.
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-
could clear the bgp tables, but I'm hesitant to
do that. Maybe better to just let it drop over time.
-Original Message-
From: Chris Boyd
Sent: Wednesday, October 26, 2016 3:57 PM
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Router memory problem
> On Oct 26, 2016,
> On Oct 26, 2016, at 2:19 PM, Joseph Mays wrote:
>
> I was thinking about using a prefix list to limit the size of the BGP routing
> table.
Hard to do if you can’t see the config, but I suppose if you are careful you
could tftp it in, since you mentioned that’s still working. On the plus si
: [c-nsp] Router memory problem
Perhaps. Looks like, but I don't know if it's TOO low.
core-gw1.noc#show mem
HeadTotal(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 6381CC60 78368 438972176 5506192 945056 898812
I/O
I was thinking about using a prefix list to limit the size of the BGP
routing table.
-Original Message-
From: Chris Boyd
Sent: Wednesday, October 26, 2016 2:59 PM
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Router memory problem
On Oct 26, 2016, at 1:51 PM, Chuck Church
226055602228776022426364
Maybe if I reduce the size of the bgp tables.
-Original Message-
From: Chuck Church
Sent: Wednesday, October 26, 2016 2:51 PM
To: 'Joseph Mays' ; cisco-nsp@puck.nether.net
Subject: RE: [c-nsp] Router memory problem
Is the router out o
> On Oct 26, 2016, at 1:51 PM, Chuck Church wrote:
>
> Is the router out of RAM? A really low memory condition might cause this.
> 'show mem' or 'show log' (if configured) might show some malloc errors if
> that is the issue.
+1 I had a similar issue a while back with a 7206VXR that was get
Of Joseph
Mays
Sent: Wednesday, October 26, 2016 2:28 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] Router memory problem
I’m dealing with a serious problem on a router I can only connect to remotely.
Show run on the router returns nothing.
core-gw1.noc#show run
core-gw1.noc#
The running
y, October 26, 2016 2:28 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] Router memory problem
I’m dealing with a serious problem on a router I can only connect to remotely.
Show run on the router returns nothing.
core-gw1.noc#show run
core-gw1.noc#
The running config is definitely there, though
cisco-nsp@puck.nether.net
Subject: [c-nsp] Router memory problem
I’m dealing with a serious problem on a router I can only connect to remotely.
Show run on the router returns nothing.
core-gw1.noc#show run
core-gw1.noc#
The running config is definitely there, though and the router is operati
I’m dealing with a serious problem on a router I can only connect to remotely.
Show run on the router returns nothing.
core-gw1.noc#show run
core-gw1.noc#
The running config is definitely there, though and the router is operational.
And interestingly the system that copies the router’s config e
19 matches
Mail list logo
