Mailing List Archive

OK, I am testing the new version and have a couple of problems with it. I am
working on trying to figure out why "show config" on Extreme doesn't seem to
complete sometimes and I will probably have some time to look into this
tomorrow.

The other issue is "show diagnostics" on Extreme. Apparently this command
does not exist on Alpines or pre-6.1.7 BDs. It does exist on all Extreme
devices supported in 6.2.0 and pre-inferno devices. So, it works with non-I
Summits and current rev BDs. John, how do you want to handle this?

Alex Bochannek
Senior Unix/Network Engineer
Yipes ... that's fast!
(415) 901-2000
(415) 901-2090 (direct)
www.yipes.com


-----Original Message-----
From: 'john heasley' [mailto:heas@shrubbery.net]
Sent: Monday, October 15, 2001 8:25 PM
To: Alex Bochannek
Cc: rancid-discuss at guelah.shrubbery.net
Subject: Re: Proposed Extreme changes.

Mon, Oct 15, 2001 at 03:58:12PM -0700, Alex Bochannek:
> Did you update the image on your server with this new clogin?

i just have, 2.2b8. i know that collection of extreme fails if the
config has been changed but not saved. have not worked that out yet.

CHANGES:

2.2b8
add PAR_COUNT variable to bin/env for adjusting the number of
simultaneous collections. see bin/env (or bin/env.new for those
with
previous installation) and the env(5) manpage.

more work on extreme switch bits + fixes from Alex Bochannek.

jlogin: add 1s sleeps to avoid passwords being echo'd before tty
noecho
is set. richard doty

few looking glass fixes

brancid: filter uptime and add -all option to config for bayrs
version
14. from mordechai abzug

jrancid: m160 measured chassis clock MHz fluctuates, trim the
decimal places. from Mark A Gebert.

par: -x fix for log file monitoring killing xterms. from rdrake.

Wed, Oct 17, 2001 at 02:31:25PM -0700, Alex Bochannek:
> OK, I am testing the new version and have a couple of problems with it. I am
> working on trying to figure out why "show config" on Extreme doesn't seem to
> complete sometimes and I will probably have some time to look into this
> tomorrow.
>
> The other issue is "show diagnostics" on Extreme. Apparently this command
> does not exist on Alpines or pre-6.1.7 BDs. It does exist on all Extreme
> devices supported in 6.2.0 and pre-inferno devices. So, it works with non-I
> Summits and current rev BDs. John, how do you want to handle this?

this shouldnt cause a problem, though some of the useful data may be
missing. why is it a problem? for example

#RANCID-CONTENT-TYPE: extreme
#
#Chassis type: Alpine3804
#
#System Serial Number: 802009-01 0022X-00030
#CPU Serial Number: 702001-05 0021S-01000 CPLD Rev 03
#Baseboard Serial Number: 702008-03 0025B-00022 CPLD Rev 03
#
#Memory: 268435456 (256MB)
#
#Power: Upper (PSU-A) 45012 4300-00007 03 0022J-01355
#Power: Lower (PSU-B)
#
#Image: Extremeware Version 6.2.0 (Build 60)
#Image: License: Full L3 + Security.
#Image: selected: secondary
#Image: booted: secondary
#Image: Primary Software version: x.x
#Image: Secondary software version: x.x
#
#Bootrom: 7.2
#
#
#
#Slot 1: type GM4SX, GM4X/GM4SX
#Slot 1: serial 702005-06-0025S00877
#Slot 1: state Operational
#
#Slot 2: type GM4SX, GM4X/GM4SX
#Slot 2: serial 702005-06-0021S00131
#Slot 2: state Operational
#
#Slot 3: type FM32, FM32
#Slot 3: serial 702009-06-0024S00170
#Slot 3: state Operational
#
#Slot 4: type FM32, FM32
#Slot 4: serial 702009-06-0024S00319
#Slot 4: state Operational
#
configure slot 1 module gm4x
configure slot 2 module gm4x
configure slot 3 module fm32t
configure slot 4 module fm32t
#

It's not causing any problems (that I know of), but I just don't like
sending invalid commands to devices :)

Alex Bochannek
Senior Unix/Network Engineer
Yipes ... that's fast!
(415) 901-2000
(415) 901-2090 (direct)
www.yipes.com


-----Original Message-----
From: 'john heasley' [mailto:heas@shrubbery.net]
Sent: Wednesday, October 17, 2001 7:19 PM
To: Alex Bochannek
Cc: 'john heasley'; rancid-discuss at guelah.shrubbery.net
Subject: Re: Proposed Extreme changes.

Wed, Oct 17, 2001 at 02:31:25PM -0700, Alex Bochannek:
> OK, I am testing the new version and have a couple of problems with it. I
am
> working on trying to figure out why "show config" on Extreme doesn't seem
to
> complete sometimes and I will probably have some time to look into this
> tomorrow.
>
> The other issue is "show diagnostics" on Extreme. Apparently this command
> does not exist on Alpines or pre-6.1.7 BDs. It does exist on all Extreme
> devices supported in 6.2.0 and pre-inferno devices. So, it works with
non-I
> Summits and current rev BDs. John, how do you want to handle this?

this shouldnt cause a problem, though some of the useful data may be
missing. why is it a problem? for example

#RANCID-CONTENT-TYPE: extreme
#
#Chassis type: Alpine3804
#
#System Serial Number: 802009-01 0022X-00030
#CPU Serial Number: 702001-05 0021S-01000 CPLD Rev 03
#Baseboard Serial Number: 702008-03 0025B-00022 CPLD Rev 03
#
#Memory: 268435456 (256MB)
#
#Power: Upper (PSU-A) 45012 4300-00007 03 0022J-01355
#Power: Lower (PSU-B)
#
#Image: Extremeware Version 6.2.0 (Build 60)
#Image: License: Full L3 + Security.
#Image: selected: secondary
#Image: booted: secondary
#Image: Primary Software version: x.x
#Image: Secondary software version: x.x
#
#Bootrom: 7.2
#
#
#
#Slot 1: type GM4SX, GM4X/GM4SX
#Slot 1: serial 702005-06-0025S00877
#Slot 1: state Operational
#
#Slot 2: type GM4SX, GM4X/GM4SX
#Slot 2: serial 702005-06-0021S00131
#Slot 2: state Operational
#
#Slot 3: type FM32, FM32
#Slot 3: serial 702009-06-0024S00170
#Slot 3: state Operational
#
#Slot 4: type FM32, FM32
#Slot 4: serial 702009-06-0024S00319
#Slot 4: state Operational
#
configure slot 1 module gm4x
configure slot 2 module gm4x
configure slot 3 module fm32t
configure slot 4 module fm32t
#

Thu, Oct 18, 2001 at 02:19:02PM -0700, Alex Bochannek:
> It's not causing any problems (that I know of), but I just don't like
> sending invalid commands to devices :)

i dont believe this is problematic, though we should recognize the
"bad cmd" response which i believe is:

/^Syntax error at token/

if they've managed to keep at least that much consistent. without
doing such commands, we'd need sparate scripts for every family and
each OS revision just to collect the info; eg: for cisco we'd need
cat 5000, cat 4000, gsr, 7200, 36xx, 7[05]xx, ....

> Alex Bochannek
> Senior Unix/Network Engineer
> Yipes ... that's fast!
> (415) 901-2000
> (415) 901-2090 (direct)
> www.yipes.com
>
>
> -----Original Message-----
> From: 'john heasley' [mailto:heas at shrubbery.net]
> Sent: Wednesday, October 17, 2001 7:19 PM
> To: Alex Bochannek
> Cc: 'john heasley'; rancid-discuss at guelah.shrubbery.net
> Subject: Re: Proposed Extreme changes.
>
> Wed, Oct 17, 2001 at 02:31:25PM -0700, Alex Bochannek:
> > OK, I am testing the new version and have a couple of problems with it. I
> am
> > working on trying to figure out why "show config" on Extreme doesn't seem
> to
> > complete sometimes and I will probably have some time to look into this
> > tomorrow.
> >
> > The other issue is "show diagnostics" on Extreme. Apparently this command
> > does not exist on Alpines or pre-6.1.7 BDs. It does exist on all Extreme
> > devices supported in 6.2.0 and pre-inferno devices. So, it works with
> non-I
> > Summits and current rev BDs. John, how do you want to handle this?
>
> this shouldnt cause a problem, though some of the useful data may be
> missing. why is it a problem? for example
>
> #RANCID-CONTENT-TYPE: extreme
> #
> #Chassis type: Alpine3804
> #
> #System Serial Number: 802009-01 0022X-00030
> #CPU Serial Number: 702001-05 0021S-01000 CPLD Rev 03
> #Baseboard Serial Number: 702008-03 0025B-00022 CPLD Rev 03
> #
> #Memory: 268435456 (256MB)
> #
> #Power: Upper (PSU-A) 45012 4300-00007 03 0022J-01355
> #Power: Lower (PSU-B)
> #
> #Image: Extremeware Version 6.2.0 (Build 60)
> #Image: License: Full L3 + Security.
> #Image: selected: secondary
> #Image: booted: secondary
> #Image: Primary Software version: x.x
> #Image: Secondary software version: x.x
> #
> #Bootrom: 7.2
> #
> #
> #
> #Slot 1: type GM4SX, GM4X/GM4SX
> #Slot 1: serial 702005-06-0025S00877
> #Slot 1: state Operational
> #
> #Slot 2: type GM4SX, GM4X/GM4SX
> #Slot 2: serial 702005-06-0021S00131
> #Slot 2: state Operational
> #
> #Slot 3: type FM32, FM32
> #Slot 3: serial 702009-06-0024S00170
> #Slot 3: state Operational
> #
> #Slot 4: type FM32, FM32
> #Slot 4: serial 702009-06-0024S00319
> #Slot 4: state Operational
> #
> configure slot 1 module gm4x
> configure slot 2 module gm4x
> configure slot 3 module fm32t
> configure slot 4 module fm32t
> #

Yes, it does still say that:

Syntax error at token diagnostics

I am just a bit worried that in future versions the expected behavior may
change. A mapping table of commands to hardware/software revs would be nice,
but since this particular command doesn't cause any harm, I am happy to live
with the way it is.

Alex Bochannek
Senior Unix/Network Engineer
Yipes ... that's fast!
(415) 901-2000
(415) 901-2090 (direct)
www.yipes.com


-----Original Message-----
From: 'john heasley' [mailto:heas@shrubbery.net]
Sent: Thursday, October 18, 2001 2:43 PM
To: Alex Bochannek
Cc: 'john heasley'; rancid-discuss at guelah.shrubbery.net
Subject: Re: Proposed Extreme changes.

Thu, Oct 18, 2001 at 02:19:02PM -0700, Alex Bochannek:
> It's not causing any problems (that I know of), but I just don't like
> sending invalid commands to devices :)

i dont believe this is problematic, though we should recognize the
"bad cmd" response which i believe is:

/^Syntax error at token/

if they've managed to keep at least that much consistent. without
doing such commands, we'd need sparate scripts for every family and
each OS revision just to collect the info; eg: for cisco we'd need
cat 5000, cat 4000, gsr, 7200, 36xx, 7[05]xx, ....

> Alex Bochannek
> Senior Unix/Network Engineer
> Yipes ... that's fast!
> (415) 901-2000
> (415) 901-2090 (direct)
> www.yipes.com
>
>
> -----Original Message-----
> From: 'john heasley' [mailto:heas at shrubbery.net]
> Sent: Wednesday, October 17, 2001 7:19 PM
> To: Alex Bochannek
> Cc: 'john heasley'; rancid-discuss at guelah.shrubbery.net
> Subject: Re: Proposed Extreme changes.
>
> Wed, Oct 17, 2001 at 02:31:25PM -0700, Alex Bochannek:
> > OK, I am testing the new version and have a couple of problems with it.
I
> am
> > working on trying to figure out why "show config" on Extreme doesn't
seem
> to
> > complete sometimes and I will probably have some time to look into this
> > tomorrow.
> >
> > The other issue is "show diagnostics" on Extreme. Apparently this
command
> > does not exist on Alpines or pre-6.1.7 BDs. It does exist on all Extreme
> > devices supported in 6.2.0 and pre-inferno devices. So, it works with
> non-I
> > Summits and current rev BDs. John, how do you want to handle this?
>
> this shouldnt cause a problem, though some of the useful data may be
> missing. why is it a problem? for example
>
> #RANCID-CONTENT-TYPE: extreme
> #
> #Chassis type: Alpine3804
> #
> #System Serial Number: 802009-01 0022X-00030
> #CPU Serial Number: 702001-05 0021S-01000 CPLD Rev 03
> #Baseboard Serial Number: 702008-03 0025B-00022 CPLD Rev 03
> #
> #Memory: 268435456 (256MB)
> #
> #Power: Upper (PSU-A) 45012 4300-00007 03 0022J-01355
> #Power: Lower (PSU-B)
> #
> #Image: Extremeware Version 6.2.0 (Build 60)
> #Image: License: Full L3 + Security.
> #Image: selected: secondary
> #Image: booted: secondary
> #Image: Primary Software version: x.x
> #Image: Secondary software version: x.x
> #
> #Bootrom: 7.2
> #
> #
> #
> #Slot 1: type GM4SX, GM4X/GM4SX
> #Slot 1: serial 702005-06-0025S00877
> #Slot 1: state Operational
> #
> #Slot 2: type GM4SX, GM4X/GM4SX
> #Slot 2: serial 702005-06-0021S00131
> #Slot 2: state Operational
> #
> #Slot 3: type FM32, FM32
> #Slot 3: serial 702009-06-0024S00170
> #Slot 3: state Operational
> #
> #Slot 4: type FM32, FM32
> #Slot 4: serial 702009-06-0024S00319
> #Slot 4: state Operational
> #
> configure slot 1 module gm4x
> configure slot 2 module gm4x
> configure slot 3 module fm32t
> configure slot 4 module fm32t
> #

One more diff:

bash-2.03$ diff -c clogin clogin.new
*** clogin Fri Oct 19 10:20:07 2001
--- clogin.new Fri Oct 19 10:21:21 2001
***************
*** 491,497 ****
exp_continue }
-re "\[^\r\n]*Press <SPACE> to cont\[^\r\n]*" { send " "
expect {
! -re "\[\r\n]*\r\r"
{}
}
exp_continue
}
--- 491,499 ----
exp_continue }
-re "\[^\r\n]*Press <SPACE> to cont\[^\r\n]*" { send " "
expect {
! # gag, 2 more
prompts
! -re "\[\r\n]*\r" {}
! -re "\[^\r\n]*Press
<SPACE> to cont\[^\r\n]*" { send " "; exp_continue }
}
exp_continue
}

Also, has anybody seen the problem where an Extreme pauses in the middle of
the banner when doing a show config? I rather would not have to undo
expect_after to get timeout to match in run_commands.

Alex Bochannek
Senior Unix/Network Engineer
Yipes ... that's fast!
(415) 901-2000
(415) 901-2090 (direct)
www.yipes.com

This turns out to be a bug with Extreme and SSH only (telnet just briefly
pauses). I reported it to Exreme and it's fairly low on their priority list.
I may have to change expect_after unless someone has a better idea.

Alex.

> Also, has anybody seen the problem where an Extreme pauses in the middle
of
> the banner when doing a show config? I rather would not have to undo
> expect_after to get timeout to match in run_commands.