"no exec" command keeps returning, Cisco 1921 universalk9 15.4(3)M5

[robert.germanovich]

We've got this 1921 we're about to deploy into an existing DMVPN setup. We had that issue where the configuration below "line con 0" has "line 2" and had a "no exec" option we did not recall manually configuring. This prevented us from being able to log into the device from the console port when the device was not connected to the tacacs+ server. We removed this command after breaking-in and were able to remove "no exec" from "line 2" and then save and reboot. This seemed to solve the problem. Today, we powered-down the device and removed an old cellular card, then restarted the router. Upon reboot, we had no trouble logging in using TACACS+ credentials as it was connected to our network, but the "no exec" command string below "line 2" has returned.

Does anyone know why this is?

Regards,

Robert G

[Mark Malone]

Hi

When your logged in now and check the start-up config is the command still there under the line in startup ?

could be a bug or it didn't save correctly before it was rebooted

[burleyman · Accepted solution]

You can't delete "Line 2" it is automatically created on ISR G2 platforms and is used to access the embedded service engines. It should have no impact on the Console port as far as I am aware.

Mike

[burleyman]

If you want to disable it you can.

1921Router(config)#line 2

1921Router(config-line)#transport input none

1921Router(config-line)#end

Then save.

Mike

[robert.germanovich]

Thank you to everyone who assisted. It appears to be correct that the Line-2 cannot be removed.