Prompt issues on Bay routers.

[john heasley]

Mon, Sep 15, 2003 at 07:00:43PM -0500, stefmit:
> See comments inline:
> 
> On Monday 15 September 2003 05:52 pm, you wrote:
> > Fri, Sep 12, 2003 at 07:58:16AM -0500, 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
> >
> >   ^^^^^^^^^^^^^^
> > where did this prompt come from? ie: what does "us-head-bcn" mean?
> > is it always within []s (square brackets)?  always end with $ (dollar
> > sign)?
> 
> I apologize - the name in between [] is the sysID associated with SNMP, that 
> the system reads (for example we named our router us (location) - head 
> (headquarters) - bcn (model). The important part is $ only, I think.

so, this may contain spaces and puctuation?  sorry, dont have the mib handy.

as for '$' only, no.  looking for lone characters or english phrases that
can not be anchored has a tendency to match random characters appearing in
the normal output.  something more like

	^\[[^][]+\]\$

> >
> > no prompt for a password, because it is the "manager" account.  right?
> 
> Right!
> 
> >
> > btw, when i say "always", I mean at that privilege level and with all
> > bay devices capable of cmd-line...or at least those we hope to collect.
> >
> > >      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#
> >
> > the prompt is "box"?  not us-head-bcn# or bcc#?
> 
> Right! it is box# - but - yet again - the point here is to pay attention to 
> the # only (I think).
> 
> >
> > I should have asked explicity; what does the exit from 'box#' back to your
> > host look like?
> >
> > > ... that's all that is to it.
> > >
> > > Thank you, John!
> > >
> > > Stef
> 
> In my opinion, the sequence would be:
> 
> $ 	prompt for TI
> > 	prompt for bcc as command interface
> # 	prompt for bcc as "enable"
> 
> The rest being more or less variable (for example, after getting into box#, 
> then every "move" is similar to "enable" in Cisco, i.e. changing the string 
> before # into whatever interface/entity is being processed.
> 
> Thx,
> Stef

> Forgot to answer your last question - will let the previously recorded session 
> do it for me:
> 
> <snip>
> 
> > > >      Welcome to the Bay Command Console!
> > > >
> > > >      * To enter configuration mode, type config
> > > >
> > > >      * To list all system commands, type ?
> > > >
> > > >      * To exit the BCC, type exit
> 
> <snip>
> 
> > > I should have asked explicity; what does the exit from 'box#' back to
> > > your host look like?
> 
> i.e. same as the "exit" from bcc ... "exit"

so,

box# exit
unix_host% blogin host
	...

not,
box# exit
bcc> exit
[foo]$ exit
unix_host%