Dmitry,

By disabling "parser config cache interface", you lose the enhancement it
introduces into NVGEN. If your config is large, you may want to add more
memory and re-enable this command to enhance NVGEN.

my 2 c
/eninja


On Mon, Feb 18, 2008 at 1:20 AM, Dmitry Kiselev <[EMAIL PROTECTED]> wrote:

> Hello!
>
> On Mon, Feb 18, 2008 at 11:13:35AM +0200, Dmitry Kiselev wrote:
>
> In few minutes I fix problem by myself by disabling IOS parser
> interfaces cache. Sorry for my noise in the list. :(
>
> Router#conf t
> Enter configuration commands, one per line.  End with CNTL/Z.
> Router(config)#no parser config cache interface
> Router(config)#end
> Router#clear parser cache
> Clearing parser cache...
>
> Router#sh run interface GigabitEthernet0/1.101
> Building configuration...
>
> Current configuration : 2101 bytes
> !
> interface GigabitEthernet0/1.101
>  encapsulation dot1Q 101
>  ip address X.X.X.1 255.255.255.0
> ...
>
>
>
> > Hello!
> >
> > Does anybody see such problems with running configuration building?
> > Subject router is 7200-NPE-G1 under 12.2(25)S14, uptime about 17 weeks.
> > Contact TAC? No other solutions?
> >
> >
> > Router#sh run
> > % String too long to write to nvram (2098):
> > Current configuration : 124735 bytes
> > !
> > ! Last configuration change at 01:08:53 EET Mon Feb 18 2008
> > ! NVRAM config last updated at 01:08:53 EET Mon Feb 18 2008
> > !
> > version 12.2
> > parser config cache interface
> > ...
> >
> > Router#sh run interface GigabitEthernet0/1.101
> > Building configuration...
> >
> > % String too long to write to nvram (2098):
> > Current configuration : 5 bytes
> > end
> >
> > Router#
> > Router#sh startup-config | beg interface_GigabitEthernet0/1.101
> > interface GigabitEthernet0/1.101
> >  encapsulation dot1Q 101
> >  ip address X.X.X.1 255.255.255.0
> > ...
> >
> > Router#copy run start
> > Building configuration...
> >
> > % String too long to write to nvram (2098):[OK]
> > Router#sh startup-config | beg interface_GigabitEthernet0/1.101
> > Router#
>
>
> --
> Dmitry Kiselev
> _______________________________________________
> cisco-nsp mailing list  [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to