Re: 'show run' on causes 7200 to lock up

On Sep 28, 10:05 am, Bo...@xxxxxxxxxxxxx wrote:
On 28 Sep, 14:50, Doug McIntyre <mer...@xxxxxxxxx> wrote:



txqzr4 <txq...@xxxxxxxxx> writes:
On Sep 28, 8:17 am, Christophe Fillot <c...@xxxxxx> wrote:
txqzr4 a =E9crit :

We have 7200 routers being used for DSL aggregation. We terminate
about 4000 subs on each using RBE, so the configs are quite large.
When we do a 'show run' the routers basically freeze up for several
minutes until the config is shown. Is this normal? My presumption is
that it is because of the extreme size of our configs, but maybe there
is something I can do to allow 'show config' to work without locking
up the router for several minutes?

Is it better if you add "parser config cache interface" in config mode?

Hope this helps.
Thanks for the suggestion. I found a command "parser cache" which I
ran, but I don't see much of an improvement. I guess my big issue is
that when I issue a 'show run' the whole router basically freezes up
and stops passing traffic for the most part. I wouldn't mind the wait
if it didn't interrupt service for 4,000 users.

Is the CPU highly loaded? What kind of NPE is in the boxes?

I've only seen that when the box was running way beyond what the CPU
should be doing.- Hide quoted text -

I have never dealt with huge configs so I have not seen that.

Post sh proc cpu during and not during the sh run.

sh buff might be worth seeing too.

It is possible to adjust the CPU scheduling with the scheduler
allocate
and scheduler interval commands.

Reduce the time spent on any task and .do something sensible with
the other one.

Also post your scheduler configuration if not default

sh run | inc scheduler

If you are really loading up the router maybe you can keep a copy of
the config
off line (tftp, ftp, whatever) and only refer to the on-line one when
you must.

You are not doing this on the console are you? Telnet would be better
for sure.

Possibly you are forcing your traffic to be process switched. If so
changing to the fast path may allow user traffic to be switched in
interrupt
mode and of the sh run to be scheduled. Not all traffic can be
switched in the fast path.

I am doing this via telnet, our routers typically run at below 50% CPU
usage with NPE-200s. I will have to see if I can do a 'sh proc cpu'
from the console as I cannot re-telnet in once I have issued 'sh run'.

.

Relevant Pages

  • Re: show run on causes 7200 to lock up
    ... about 4000 subs on each using RBE, so the configs are quite large. ... When we do a 'show run' the routers basically freeze up for ... Post sh proc cpu during and not during the sh run. ... It is possible to adjust the CPU scheduling with the scheduler ...
    (comp.dcom.sys.cisco)
  • Re: show run on causes 7200 to lock up
    ... about 4000 subs on each using RBE, so the configs are quite large. ... When we do a 'show run' the routers basically freeze up for several ... I've only seen that when the box was running way beyond what the CPU ... It is possible to adjust the CPU scheduling with the scheduler ...
    (comp.dcom.sys.cisco)
  • Re: show run on causes 7200 to lock up
    ... about 4000 subs on each using RBE, so the configs are quite large. ... When we do a 'show run' the routers basically freeze up for several ... It is possible to adjust the CPU scheduling with the scheduler ... switched in the fast path. ...
    (comp.dcom.sys.cisco)
  • Re: show run on causes 7200 to lock up
    ... about 4000 subs on each using RBE, so the configs are quite large. ... When we do a 'show run' the routers basically freeze up for several ...
    (comp.dcom.sys.cisco)