[c-nsp] [cisco-bba] 7204VXR(NPE-G1) running c7200-jk9s-mz.123-14.T3.bin

[Saku Ytti]

On (2006-09-01 09:53 +0100), Mark Tohill wrote:
 
> Oliver, regarding the 'trigger', I was trying to figure this out myself.
> These boxes were behaving perfectly for six or seven months and then
> this, all of a sudden.

My experience is, that Oliver is right and indeed this happens on
newish software when they run out of memory, I don't think there
is bug-id, but I've seen it myself too in 12.2S.
But just run 12.4 and monitor your largest continuous free space
in memory (show memory free, under Largest(b)).

So really it's side affect of memory leaking bug, and as far as I
know there isn't yet bug-id for the config corruption.
My experience was on 3-4 boxes and all of them lost loopback0 
config.

> There have been no configuration changes, of note, since then. The only
> thing I can think of is I am now logging a suspected spammer on an
> extended inbound ACL on our internet-facing interface.
> 
> I get entries in logging buffer for this user. Possibly connected to
> this is the mention of 'Virtual Exec' messages we got along with the
> tracebacks. It's maybe nothing.
> 
> Thanks again,
> Mark
> 
> 
> -----Original Message-----
> From: Oliver Boehmer (oboehmer) [mailto:oboehmer at cisco.com] 
> Sent: 01 September 2006 09:40
> To: Mark Tohill; cisco-bba at puck.nether.net; cisco-nsp at puck.nether.net
> Subject: RE: [cisco-bba] 7204VXR(NPE-G1) running
> c7200-jk9s-mz.123-14.T3.bin
> 
> Mark,
> 
> to me, this looks like side-effects of the memory leak, i.e. you're
> running out of memory causing all kinds of things. Do you get malloc
> failures in the logs? What is the TAC case# so I can take a look?
> 
> I do wonder about the PARSER-4-BADCFG message. What is the trigger for
> them? Do you do some config via tftp or similar (copy tftp
> running-config)?
> 
> 	oli
> 
> Mark Tohill <> wrote on Friday, September 01, 2006 10:15 AM:
> 
> > Hello,
> > 
> > We have 7204-NPEG1s x 2 running c7200-jk9s-mz.123-14.T3.bin. These
> > boxes are running BGP(default only), and terminating DSL L2TP VPDN's. 
> > 
> > We're having a few issues with that image, one involving 'VTemplate
> > Manager' tracebacks. According to TAC, this is bugid: 
> > 
> > CSCeh90534
> > Externally found severe defect: Duplicate (D)
> > memory leak with micro_block_alloc calling VTEMPLATE Backgr
> > 
> > Duplicate of :  CSCeg81196, fixed in 12.3(14)T4 and later
> > 
> > On same boxes, we get the following:
> > 
> > Aug 31 13:38:15.293: %PARSER-4-BADCFG: Unexpected end of
> > configuration file. 
> > Aug 31 13:38:15.297: %PARSER-4-BADCFG: Unexpected end of
> > configuration file. 
> > 
> > This is having the interesting side effect of not 'saving' a Loopback
> > and GRE Tunnel interface to the running config file. When we show
> > specific interface configurations, it's fine. See below:  
> > 
> > #sh run int tunnel 0
> > Building configuration...
> > Current configuration : 136 bytes
> > !
> > interface Tunnel0
> >  ip address 192.168.200.2 255.255.255.252
> >  tunnel source GigabitEthernet0/2.200
> >  tunnel destination a.b.c.d
> > end
> > 
> > #sh run int loopback 0
> > Building configuration...
> > Current configuration : 111 bytes
> > !
> > interface Loopback0
> >  description VPDN Tunnel Endpoint
> >  ip address a.b.c.d 255.255.255.255
> > end
> > 
> > So we know the interfaces are there, being routed over, but we you do
> > an ordinary 'show run', they're configs are not complete..IP
> > addressing gone.  
> > 
> > #sh running-config | begin Tunnel0
> > interface Tunnel0
> >  !
> >  interface Loopback0
> >  description VPDN Tunnel Endpoint
> > !
> > 
> > Therefore we can't make any changes to the config, we'll loose them
> > when we save to startup!! The loopback is fairly critical, it
> > terminates the L2TP tunnel, an on reboot, the VPDN sessions will not
> > come up since there are no tunnels to carry them.   
> > 
> > Has anyone encounterd this problem? We have been advised by TAC to
> > upgrade to 12.4 mainline, which is fine, but I cannot get info
> > regarding the config file corruption.  
> > 
> > Any experiences/ideas appreciated.
> > 
> > Mark
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

-- 
  ++ytti