Prompt issues on Bay routers.

[stefmit]

I have raised this issue before, but I had never dared to go any further, 
knowing how hard it is for someone to create a program, then having to deal 
with all possible questions and issues raised by everyone, about every flavor 
of equipment that could possibly exist ... I have made myself some changes to 
the script, but have failed to properly login all the way into the "bcc". I 
will thus take advantage right now of this kind and direct offer from John, 
to help in resolving the Bays, and prodiving him with the info:

TI = technician interface - a rudimentary management interface into the 
Bay/Nortel routers, with some (limited) capabilities. Unlike a regular CLI 
(command line interface), the TI has some scripting capabilities

BCC = Bay Command Console - next level into the "guts" of the router. This has 
two modes: command mode and configuration mode.

NOTE: before showing you a simple login session through all layers, I feel we 
need to specify something here: the majority of items to be set on Bay 
routers are reachable only via their corresponding MIB entity names/numbers, 
which is a PITA!!!

And now a session - consisting in login to the TI (first level), then issuing 
the bcc command (second level, and first of the bcc, the command mode), then 
typing config (this is probably the equivalent of enable in cisco - second 
level for bcc)

[scm at Crypto]$ telnet x.y.z.w
Trying x.y.w.z...
Connected to bcn (x.y.w.z).
Escape character is '^]'.


Bay Networks, Inc. and its Licensors.
Copyright 1992,1993,1994,1995,1996,1997,1998,1999. All rights reserved.



Login: Manager

Password: [hidden]

Mounting new volume...
Device label:
Directory: 1:
New Present Working Directory: 1:


      Welcome to the Backbone Technician Interface


[us-head-bcn]$bcc

     Welcome to the Bay Command Console!

     * To enter configuration mode, type config

     * To list all system commands, type ?

     * To exit the BCC, type exit

bcc> config

Reading configuration information, please wait . . . done.

box#

... that's all that is to it.

Thank you, John!

Stef

On Thursday 11 September 2003 01:23 pm, john heasley wrote:
> Wed, Sep 03, 2003 at 12:28:41PM -0700, James Kilton:
> > Hi,
> >
> > I'm new to Rancid and not familiar with Tcl, so forgive the newbieness -
> >
> > I'm unable to run commands in BCC on Bay routers and I think it's because
> > of prompt issues.  When you first log in to a Bay router, you're in TI
> > instead of BCC.  The prompt is [1:TN]$.  I can get Rancid to recognize
> > this by doing 'set prompt "TN"' in blogin.  Rancid then executes the
> > 'bcc' command to get into BCC.  BCC uses a totally different prompt,
> > however (bcc>), and I'm wondering how to get Rancid to "switch" to that
> > prompt so that commands can be run in BCC.  I've tried stuff like 'set
> > prompt "TN|bcc"' or 'set prompt (TN|bcc)' all to no avail.
> >
> > If anyone has any ideas I'd appreciate hearing them.
>
> I think that someone explained this to me before, but I must have purged
> it. blogin has a comment which reads:
>
> # Unlike the Cisco's, there is no enable function on the Bay's.
> # Instead there are seperate User and Manager accounts.  A 'system' command
> # exists, which i am told does nothing.
>
> so, what is bcc?  for that matter, what is "TI"?  is the prompt
> configurable?
>
> an example of non-privileged and privileged logins (and perhaps a few
> random commands) performed manually from the bay/nortel would be helpful.