[rancid] Re: [PATCH] Add support for the Cisco WLC

[Ryan West]

Michael,

> -----Original Message-----
> From: Michael Stefaniuc [mailto:mstefani at redhat.com]
> Sent: Wednesday, April 28, 2010 6:11 PM
> To: Ryan West
> Cc: rancid-discuss at shrubbery.net
> Subject: Re: [rancid] [PATCH] Add support for the Cisco WLC
> 
> On 04/28/2010 01:46 AM, Ryan West wrote:
> Hello Ryan,
> 
> >> -----Original Message-----
> >> From: rancid-discuss-bounces at shrubbery.net [mailto:rancid-discuss-
> >> bounces at shrubbery.net] On Behalf Of Michael Stefaniuc
> >> Sent: Tuesday, April 27, 2010 4:04 PM
> >> To: rancid-discuss at shrubbery.net
> >> Subject: [rancid] [PATCH] Add support for the Cisco WLC
> >>
> >> Hello guys,
> >>
> >> I hoped that somebody would beat me to add the Cisco WLC upstream...
> >> Though there was a lot of interest in testing such a patch so here it is.
> >> Especially testing on versions 4.x is needed as I could test it only
> >> on 5.2.x and 6.0.x.
> >
> > It's much cleaner with this version, but it's still failing on the pager or
> an expect loop.  I would move over to version 6 assurewave but I think I would
> hit some of the bugs, so I'm holding on to 4.2.207 for a bit longer.
> >
> > Here is what's happening:
> thanks for the detailed report; it made it easy to figure out what goes wrong.
> The 4.x versions seem to use this pager prompt too:
> Press Enter to continue Or<Ctl Z>  to abort
> 
> The fix was easy aka accept both "or" and "Or" and don't send a CTRL-Z but an
> ENTER. It still worked just fine on my 6.0.x boxes but the 5.2.x box begged to
> differ... There is one place in the "show running-config" where the pager "--
> More-- or (q)uit" clobbers a previous line.
> 
> Can you please give the attached patch a whirl? It applies on top of my
> previous patch. I have added also an unrelated change for wlcrancid where the
> "External Temperature" is filtered out too.
> 

I worked through the pager issues earlier as well, I used ^.*--More--.* to match on the unclean line.  The problem still exists though, the output from 'show run-config commands' is very detailed and will change a lot over time.  Some logic would need to be added to determine the major code version before issuing the commandtable.

Here's some output:

Radio Type..................................... RADIO_TYPE_80211b/g
  Noise Information
    Noise Profile................................ PASSED
    Channel 1.................................... -103 dBm
    Channel 2....................................  -98 dBm
    Channel 3....................................  -93 dBm
    Channel 4....................................  -97 dBm
    Channel 5.................................... -100 dBm
    Channel 6.................................... -102 dBm
    Channel 7....................................  -99 dBm
    Channel 8....................................  -95 dBm
    Channel 9....................................  -94 dBm
    Channel 10................................... -102 dBm
    Channel 11................................... -101 dBm
  Interference Information
    Interference Profile......................... PASSED
    Channel 1....................................  -80 dBm @  5 % busy
    Channel 2.................................... -128 dBm @  0 % busy
............................. -128 dBm @  0 % busy
    Channel 4.................................... -128 dBm @  0 % busy
    Channel 5.................................... -128 dBm @  0 % busy
    Channel 6....................................  -78 dBm @  5 % busy
    Channel 7.................................... -128 dBm @  0 % busy
    Channel 8.................................... -128 dBm @  0 % busy
    Channel 9.................................... -128 dBm @  0 % busy
    Channel 10...................................  -86 dBm @  1 % busy
    Channel 11...................................  -75 dBm @  4 % busy

Thanks,

-ryan