07-18-2004 02:39 PM - edited 03-02-2019 05:09 PM
When issuing a "wr m" on the active (designated) MSFC (Sup1A/MSFC1) an error on the non-designated MSFC is observed: "%PARSER-4-BADCFG: Unexpected end of configuration file", and any configuration changes are not replicated on the non-designated MSFC.
However, if the non-designated MSFC is reloaded, it syncs a correct copy of the configuration on the active (designated) MSFC. All MSFCs are running 12.1(22)E1; CatOS 6.4(3) is also in use on the Sup1As. I can't find any bugs relating to similar issues.
07-18-2004 03:23 PM
On further investigation, it appears that the startup-config of the non-designated MSFC is being updated, whilst the running-config isn't (which explain why a reload of the non-designated MSFC results in an apparent synchronisation).
07-19-2004 04:56 PM
The error message %PARSER-4-BADCFG: Unexpected end of configuration file.\n
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:
(1) 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.
(2) Reset the Non-Designated MSFC.
(3) The config file may be corrupted. You can copy run startup. If this doesn't fix the problem. Then you can format the NVRAM by "wr erase" and then reload the router.
Thanks,
Parag.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide