Nortel/bay routers and rancid

[stefmit]

Thank you ... didn't work, yet, but you pointed me to the right place, and I
started to play around with it. I need to figure out where you have the "bcc"
part, to see if I can figure it out in conjunction with the "enable" and
prompt sequence.

FYI: the sequence of events (including prompt "history" during the login and
enable processing) is as I explained it in the original message, i.e.:

telnet <my_router> <CR>
prompt is Login: 	--> <my_username> <CR>
prompt is Password:	--> <my_password> <CR>
prompt is $		--> bcc <CR>
prompt is bcc>		--> config <CR>
prompt is bcc#		--> this is what I could probably call "enable" mode, if I
were to compare it - somehow - with Cisco

So - after logging in succesfully, the sequence of prompts is $, >, then #.

Thanks again for all the help,
Stef

On Friday 06 June 2003 03:42 pm, Mark Cooper wrote:
> The "$" prompt ? The bay's I've come across usually have a prompt of ">"
> which is probably the cause of your problem.
>
> Try the following patch..
>
>
> --- blogin.ORIG Fri Jun  6 21:12:57 2003
> +++ blogin      Fri Jun  6 21:13:22 2003
> @@ -483,7 +483,7 @@
>              set prompt "#"
>          } else {
>              set autoenable 0
> -           set prompt ">"
> +           set prompt "$"
>          }
>       }
>
> stefmit wrote:
> > Here is what I have:
> >
> > .cloginrc:
> >
> > add password router password (tried also {password}
> > add user router user (tried alternatively with the above, {user})
> > add userprompt {Login:}
> > # the above is the only one getting me to the $ prompt, all other options
> > # (e.g. {"Login:"}) leaving me at the Login: prompt!
> > add autoenable router 1
> > add userpwassword password
> > # last two lines tried without, with one at a time, with both, etc.
> >
> > With all five lines above, in the form I have them now, get me as far as
> > the $ prompt, which is one step before the bcc.
> >
> > When running the suggested:
> >
> > blogin -c "help" router
> >
> > I still stop at the $ prompt - no "help" and no logout.
> >
> > Any ideas of what could be wrong at this level?
> >
> > Thx,
> > Stefan

<snip>