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

[Martin Robinson]

Hello Mark,

 

Probably like teaching your grandmother to sucks egg's, but had a quick
look and I'm sure you've already seen it, but though I would drop this
over to you just incase you hadn't.

 

%PARSER-4-BADCFG (x1): Unexpected end of configuration file. 
 
Explanation: A configuration has been read from the TFTP server or
NVRAM, and
the end of the file  has been encountered before the end statement. The
configuration
may be corrupted or incomplete.  What was read is in effect.
 
Recommended Action: Ensure that the configuration is correct. After the
configuration
is verified,  enter either the copy running-config startup-config
command to write
the good configuration to  NVRAM, or the copy running-config tftp
command to write

to a network TFTP server.

 

 

Martin.

 

- - - - - - - - - - - - -

Martin Robinson

Product Manager

www.hardware.com

+44 (0)1285 771 621

AIM : MartinHardware

________________________________

From: cisco-bba-bounces at puck.nether.net
[mailto:cisco-bba-bounces at puck.nether.net] On Behalf Of Mark Tohill
Sent: 01 September 2006 09:15
To: cisco-bba at puck.nether.net; cisco-nsp at puck.nether.net
Subject: [cisco-bba] 7204VXR(NPE-G1) running c7200-jk9s-mz.123-14.T3.bin

 

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

 


________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________


________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-bba/attachments/20060901/3668d1eb/attachment-0001.html