<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML DIR=ltr><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"></HEAD><BODY><DIV><FONT face='Arial' color=#000000 size=2>Hello,</FONT></DIV>
<DIV><FONT face=Arial color=#000000 size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#000000 size=2>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.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>We're having a few issues with that image, one
involving 'VTemplate Manager' tracebacks. According to TAC, this is
bugid:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>CSCeh90534<BR>Externally found severe defect:
Duplicate (D)<BR>memory leak with micro_block_alloc calling VTEMPLATE
Backgr<BR><BR>Duplicate of : CSCeg81196, fixed in 12.3(14)T4 and
later</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>On same boxes, we get the following:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>Aug 31 13:38:15.293: %PARSER-4-BADCFG: Unexpected end of configuration
file.
<DIV>Aug 31 13:38:15.297: %PARSER-4-BADCFG: Unexpected end of configuration
file.</DIV>
<DIV> </DIV>
<DIV>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:</DIV>
<DIV> </DIV>
<DIV>
<DIV dir=ltr><FONT face=Arial size=2>#sh run int tunnel 0<BR>Building
configuration...</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Current configuration : 136
bytes<BR>!<BR>interface Tunnel0<BR> ip address 192.168.200.2
255.255.255.252<BR> tunnel source GigabitEthernet0/2.200<BR> tunnel
destination a.b.c.d<BR>end</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>#sh run int loopback 0<BR>Building
configuration...</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Current configuration : 111
bytes<BR>!<BR>interface Loopback0<BR> description VPDN Tunnel
Endpoint<BR> ip address a.b.c.d 255.255.255.255<BR>end</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>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. </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr>#sh running-config | begin Tunnel0<BR>interface
Tunnel0<BR> !<BR> interface Loopback0<BR> description VPDN
Tunnel Endpoint<BR>!<BR></DIV>
<DIV dir=ltr>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.</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>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. </DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Any experiences/ideas appreciated.</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Mark</DIV>
<DIV dir=ltr> </DIV></FONT></DIV></DIV></BODY></HTML>