Problems getting config when not enable mode

[Fred Jordan]

John,
    Thanks for the reply. We do have creative AAA statements that
do allow us to type "show config" and we can see the
startup-config file. Really this is where I am headed. At the
privilege level we log in , which is less than 15; we can do almost
all of the show commands. With that, I was hoping we would be able to
either get the default clogin to work by creating the proper entry in the
.cloginrc file for these hosts; OR would I need to hack a xlogin
and/or xrancid to get this to work. From your email, sounds like
I will have to have a modified xlogin and/or xrancid and I don't know
if I need the first, the second or both.

Again, any help is greatly appreciated.

                                                                        
            Thanks Much,
                                                                        
                        Fred

john heasley wrote:

>Wed, Jul 09, 2003 at 10:36:42AM -0400, Fred Jordan:
>  
>
>>We are collecting cisco router config files from some of our customers.
>>Problems is we do not have enable mode access to the routers.
>>What we have is the ability to do "show config" at the default
>>privledge level that we log in with.
>>
>>I have tried multiple permutations of autoenable/noenable and still
>>cannot get clogin to run the commands to collect the configs.
>>
>>Here are examples of telneting into the router as well as running
>>clogin as user rancid with various .cloginrc permutations.
>>Any help is greatly appreciated.
>>    
>>
>
>w/o creative AAA, you have to have enable to get the config, so
>rancid expects that, ie: a prompt ending in #.  That will be one
>problem, that will need to be (for the moment) hacked in rancid.
>
>there may other cmds run by rancid that also require privs.
>
>  
>
>>==============================================================
>>= First try
>>= .cloginrc parameters
>>=add user     1.2.3.4  ranuser
>>=add password 1.2.3.4   {ranpass} {ranpass}
>>=add noenable 1.2.3.4
>>    
>>
>			 ^ you need a value here for the config parser, 1.
>			   sorry, the manpage is wrong and the code doesnt
>			   handle this well --- added to the todo list.
>  
>