Cisco 887 VA Router giving -------- control-plane ^ % Invalid input detected at '^' marker. --- on Reload

Hi EE,

When I do a reload on a newly acquired 887VA router it gives the error:

control-plane        ^ % Invalid input detected at '^' marker.

Afterwards it boots fine and I can go into the router an configure but this is a bit annoying. Any help in resolving this issue will be much appreciated.

Below is a snippet of the message output.

Thanks EE.

------------------------------
Cisco 887VA (MPC8300) processor (revision 1.0) with 236544K/25600K bytes of memory.
Processor board ID XXXXXXXX
.
.
.

256K bytes of non-volatile configuration memory.
126000K bytes of ATA CompactFlash (Read/Write)

control-plane
       ^
% Invalid input detected at '^' marker.



Press RETURN to get started!
DaeraAsked:
Who is Participating?
 
avcontrolConnect With a Mentor Commented:
Upgrading IOS should help for sure.
But if error repeats, it can be hardware issue.
0
 
Don JohnstonInstructorCommented:
There's something in the startup-config that the router is unhappy with.

Please the the current startup-config.
0
 
DaeraAuthor Commented:
It is currently empty.

I write erase, then del vlan.dat and reloaded so it is empty.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
DaeraAuthor Commented:
When I do a reload after wr erase, the error dosent come up as it boots a new.

However when I make a config change, ie create a hostname and reload it gives the error. There fore you are right Don that something in the startup config is causing grief to the router.

============== one change====hostname

RTR>en
RTR#sh run
Building configuration...

Current configuration : 873 bytes
!
version 15.1
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname RTR
!
boot-start-marker
boot-end-marker
!
!
!
no aaa new-model
memory-size iomem 10
crypto pki token default removal timeout 0
!
!
ip source-route
!
!
!
!
!
ip cef
no ipv6 cef
!
!
license udi pid CISCO887VA-K9 sn xxxxxxxxxx
!
!
!
!
!
!
controller VDSL 0
!
!
!
!
!
!
!
!
interface Ethernet0
 no ip address
 shutdown
!
interface ATM0
 no ip address
 shutdown
 no atm ilmi-keepalive
!
interface FastEthernet0
!
interface FastEthernet1
!
interface FastEthernet2
!
interface FastEthernet3
!
interface Vlan1
 no ip address
!
ip forward-protocol nd
no ip http server
no ip http secure-server
!
!
logging esm config
!
!
!
!
!
control-plane
!
!
line con 0
 no modem enable
line aux 0
line vty 0 4
 login
 transport input all
!
end

RTR#
0
 
Craig BeckCommented:
It's probably just a command in the IOS that is issued at startup when no startup-config is present.  I wouldn't worry about it.
0
 
Don JohnstonInstructorCommented:
The command "control-plane" in your config is what's causing the error. It's being erroneously placed there either from the IOS or the setup dialog.  I would try removing it from the config. But if it was placed there as a default, you may not be able to remove it.  In which case, just ignore the message when the router boots.
0
 
DaeraAuthor Commented:
I've tried removing it but gave an error instead. The command is not even in IOS help.

Will upgrading the IOS and deleting the current IOS fix it? I might experiment with that instead.
0
 
Don JohnstonConnect With a Mentor InstructorCommented:
You're running v15.1 code so I don't think upgrading will change anything.  More likely downgrading has a better chance of eliminating the issue (but that's not a good solution).

I would just ignore it.
0
 
Craig BeckConnect With a Mentor Commented:
Really, it's of no consequence whatsoever.  There are lots of commands that fail to apply - they are hardware-dependent in some cases.  For example, the 887VA is different to the 881, yet the IOS is exactly the same.  When the 887VA boots the VDSL controller needs to be initialized, yet there isn't one in the 881, so the initialization command would fail upon boot of the 881.  This is essentially the same kind of issue, therefore it's fine to ignore.
0
 
DaeraAuthor Commented:
I havent done any IOS upgrade and leave the router as is. Sometime in the future I will do it. However thanks for the contributions.
0
 
Don JohnstonInstructorCommented:
Please read this before grading your next question.
0
All Courses

From novice to tech pro — start learning today.