We help IT Professionals succeed at work.

How do I workaround "Authorization Failed" on Cisco 2600 router?

jeffheather
jeffheather asked
on
I have an old 2600 router that has been in service for at least 5 years.  The third party company that installed and deployed is now out of business.  The router works but is a mysterious 'black hole' on our network (I am new to this network).  I need to review the configuration to determine many things (like what is it doing specifically and how?).  I use the rommon mode to get into the router (confreg 2142) but when I issue any command it responds with "Authorization Failed".  We do not have any AAA servers running on our network (TACACS, Radius, etc.) so I am suspicious that the old service provider may have some sort of VPN running or perhaps is using a LOCAL database on the router.  Can anyone suggest a way that I can view this configuration?  THANKS!.
Comment
Watch Question

Top Expert 2010

Commented:

Author

Commented:
Thanks Billy!  That is exactly the procedure I am following.  The problem occurs when I try to enter a command at the Router# prompt.  That's when I get the 'Authorization Failed' error.  So what I would like to know is how can I get around an unknown AAA authentication so that I can simply run a 'show running-configuration' command?
Don JohnstonInstructor
Top Expert 2015

Commented:
At step 10 make a note of the AAA commands and once you're in config mode, reissue the commands with a "no" in front of them.

Author

Commented:
Don--Thanks!  I apologize for not making myself more clear.  Step 10 is exactly where I am having the problem.  When I enter 'sh run' (or any other command) I get the 'authorization failed'.  THAT is my issue.
Thanks again for taking the time to help me out.
Instructor
Top Expert 2015
Commented:
That's right....

What you're going to have to do is after step 8, do a "show start". Paste the output to a text editor. Remove any AAA related commands.

Then get to config mode on the router and copy the text from your text editor to your terminal program.

Exit config mode and set the config-register back to 0x2102 and save your config.


Author

Commented:
Thanks Don!  That worked and was perfectly logical.  I should have been able to think this one through by myself but I'm getting too old!
Don JohnstonInstructor
Top Expert 2015

Commented:
>but I'm getting too old!

Aren't we all. :-)