Thu, Oct 18, 2018 at 03:17:56AM +, Piegorsch, Weylin William:
> Thanks. I just tried, and got the same "end of run not found." Then I
> realized I wasn’t merely cutting/pasting from one location to another, but
> also the specific logout text test changed; once I updated to what you
> show
+;
[rancid@nsgv-prod-59 ~]$
-Original Message-
From: heasley
Date: Friday, October 12, 2018 at 8:38 PM
To: Weylin Piegorsch
Cc: "rancid-discuss@shrubbery.net"
Subject: Re: [rancid] Unable to Conduct Cisco Wireless Controller Backup
Fri, Oct 12, 2018 at 03:36:
"
Subject: Re: [rancid] Unable to Conduct Cisco Wireless Controller Backup
Fri, Oct 12, 2018 at 03:36:20PM +, Piegorsch, Weylin William:
> send -h "exit\r"
>
> I changed that line to ' send -h "logout\r" ', and now I'm
Fri, Oct 12, 2018 at 03:36:20PM +, Piegorsch, Weylin William:
> ...with the exception of “if (!$clean_run || !$found_end)”. For some reason
> I don’t understand, I keep getting “End of run not found”. I’ve attached .raw
> and .new files following an execution of “NOPIPE=YES rancid -d -t cisc
Fri, Oct 12, 2018 at 03:36:20PM +, Piegorsch, Weylin William:
> send -h "exit\r"
>
> I changed that line to ' send -h "logout\r" ', and now I'm getting a
> clean logout. Wlogin from 3.8 seems to fix this from reading through
> wlogin.in (I couldn't fudge things to get wlogin-3.8 to
Tue, Jul 31, 2018 at 12:13:48PM +, Piegorsch, Weylin William:
> > this is a(nother) design flaw in the o/s, imiho.
>
> FULLY AGREE! "config pager disable" is a per-session setting, and has no
> permanence. I tried setting it, and it lasted the duration of my session,
> but once I logge
e.
Thanks for the help through this process.
weylin
-Original Message-
From: heasley
Date: Monday, July 30, 2018 at 8:45 PM
To: Weylin Piegorsch
Cc: heasley , Daniel Schmidt ,
"rancid-discuss@shrubbery.net"
Subject: Re: [rancid] Unable to Conduct Cisco Wireless Controller Ba
Mon, Jul 30, 2018 at 10:59:39AM +, Piegorsch, Weylin William:
> Hi John,
>
> I'm still playing around with AAA. What I'm finding, is that the f*&^% WLC
> CLI authorization mechanism is all bork bork bork. I can set a read-only
> role, but that disables the ability to issue the "config page
Hi John,
I'm still playing around with AAA. What I'm finding, is that the f*&^% WLC CLI
authorization mechanism is all bork bork bork. I can set a read-only role, but
that disables the ability to issue the "config pager disable" command since the
entire "config *" command tree is not availabl
This might be a tacacs issue. When I log in as a normal user, the config
paging disable command appears when I type "?". I'll play around with that
over the weekend.
Weylin
(cumm111-wism-aca05) >?
debug Manages system debug options.
exit
grep P
Ah; thanks, I see it there. Something is amiss with that. "eval... ; cat -v"
output below.
Weylin
[rancid@nsgv-prod-59 ~]$ eval `rancid -t cisco-wlc5 -C
cumm111-wism-aca05.bu.edu` &> output
[rancid@nsgv-prod-59 ~]$ cat -v output
cumm111-wism-aca05.bu.edu
spawn ssh -2 -c
aes128-ctr,aes192-
Fri, Jul 27, 2018 at 12:08:37PM +, Piegorsch, Weylin William:
> I did some experimenting, issuing the "config paging disable" CLI command on
> initial login seems to eliminate the paging issue, similar to the ASA
> "terminal pager 0" or the IOS "terminal length 0".
> weylin
wlogin should hav
When I login as myself and run the "show sysinfo" command, I get the below
output. I notice that rancid (wlogin) gets stuck on the prompt at the end
there. When expect sees the prompt, a would be the appropriate
response. I'm not sure how to disable paging, unfortunately.
Weylin
(cumm111-
I did some experimenting, issuing the "config paging disable" CLI command on
initial login seems to eliminate the paging issue, similar to the ASA "terminal
pager 0" or the IOS "terminal length 0".
weylin
On 7/27/18, 8:01 AM, "Piegorsch, Weylin William" wrote:
When I login as myself and r
Thu, Jul 26, 2018 at 09:20:42PM +, Piegorsch, Weylin William:
> I should note that using the NOPIPE=yes thing causes the "controller wlogin
> error: Error: Connection closed (ssh): controller" message that I show below.
> If I omit the NOPIPE environment variable on the CLI, I get the output
ancid-discuss@shrubbery.net"
Subject: Re: [rancid] Unable to Conduct Cisco Wireless Controller Backup
Sun, Jan 21, 2018 at 05:43:23AM +, Piegorsch, Weylin William:
> I’m running rancid v3.4.1. I have a number of Cisco WISM2
controller running 8
Original Message-
From: heasley
Date: Monday, January 22, 2018 at 10:17
To: Weylin Piegorsch
Cc: Daniel Schmidt , "rancid-discuss@shrubbery.net"
Subject: Re: [rancid] Unable to Conduct Cisco Wireless Controller Backup
Sun, Jan 21, 2018 at 05:43
gorsch
Cc: Daniel Schmidt , "rancid-discuss@shrubbery.net"
Subject: Re: [rancid] Unable to Conduct Cisco Wireless Controller Backup
Sun, Jan 21, 2018 at 05:43:23AM +, Piegorsch, Weylin William:
> I’m running rancid v3.4.1. I have a number of Cisco WISM2 controller
runnin
Sun, Jan 21, 2018 at 05:43:23AM +, Piegorsch, Weylin William:
> I’m running rancid v3.4.1. I have a number of Cisco WISM2 controller running
> 8.2.166.0. rancid is not able to acquire any of their configs. I’ve tried
> various types in router.db: cisco-wlc4, cisco-wlc5, and cisco, none of
I just tried five times on three different controllers; I got 100% success.
weylin
From: Daniel Schmidt
Date: Sunday, January 21, 2018 at 00:17
To: Weylin Piegorsch
Cc: "rancid-discuss@shrubbery.net"
Subject: Re: [rancid] Unable to Conduct Cisco Wireless Controller Backup
Can you
Can you login with wlogin?
On Fri, Jan 19, 2018 at 8:33 PM, Piegorsch, Weylin William
wrote:
> Hello,
>
>
>
> I’m running rancid v3.4.1. I have a number of Cisco WISM2 controller
> running 8.2.166.0. rancid is not able to acquire any of their configs.
> I’ve tried various types in router.db: c
Hello,
I’m running rancid v3.4.1. I have a number of Cisco WISM2 controller running
8.2.166.0. rancid is not able to acquire any of their configs. I’ve tried
various types in router.db: cisco-wlc4, cisco-wlc5, and cisco, none of them
work. The logs, copied below, show the results of cisco-wl
22 matches
Mail list logo
