I just got hit by this also on a 5506-x. I turned off the login history for
now, but I saw back in January a proposed patch, did that work out? (I guess
I could try it, but it's always nice to know if it worked, and if it might be
destined for incorporation?)
Linwood
From: Rancid-discuss [
(Sorry, I replied to this initially with a different account, if that's sitting
in a moderation queue it can be deleted)
>> I just got hit by this also on a 5506-x. I turned off the login history for
>> now, but I saw back in January a proposed patch, did that work out? (I
>> guess I could
I have a bunch of old DLinks and have been working to find a way to monitor
changes. I saw some past mail list notes on DLInk's, and I see the DLLOGIN and
Dell.pm modules, that have some support.
I could not get them to work in any straightforward way, so I spent a bit of
time changing them, e
For a client I suddenly am getting a pile of Netgear switches.
I had previously patched the Dell routines to work with DLink and am starting
to do the same for Netgear (it supports a show running_config), but I did not
see either much discussion (some in 2008) or any built in support (at least
> If you post a snippet of config, somebody might recognise what ODM makes the
> switches.
Sure, thanks. The login is
User:
Password:
The not-enabled prompt is the model in parenthesis
(M4100-26G) >
The enable prompt (no password required, at least as we are set up):
(M4100-26G) #
A "termi
> Looks a lot like a Ubiquiti EdgeMAX so presumably Ubiquiti and Netgear are
> buying the design from the same place.
> You're in luck:
> # edgemax.pm - Ubiquity ("UBNT") EdgeMAX switch rancid procedures
>
Real close but it uses exit not logout. exit won't actually log off, it just
loops fore
OK if the command completes OK.
I think I have it running, I just did a show config, hopefully everything is
really in there.
Appreciate the pointers.
Linwood
-Original Message-
From: heasley [mailto:h...@shrubbery.net]
Sent: Wednesday, May 16, 2018 9:14 PM
To: o...@leferguson.com
Cc
Start by looking in the log file (usually in the rancid directory structure,
try ~/var/rancid/logs (though I think depending on how installed it may be
elsewhere). Find the latest log, look at it, see what is happening.
If it's not there (i.e. no logs) rancid is probably not starting. Restarti
ne listed in the up-to-date error
(e.g. 192.168.215.10) and see if the up-to-date goes away when it can process
the device.
Hopefully someone more CVS knowledgeable can advise on what that actually means.
Linwood
From: Larry Larsen [mailto:llar...@longlines.biz]
Sent: Wednesday, Octo
Yeah, this is something I keep meaning to change as well. I haven't done it,
but I think you can just put something like
next if (^!VLAN:);
in showVLAN in ios.pm. You'll see similar checks. But I also just want to
put a plug in that this is a good candidate for a rancid option. I would t
10 matches
Mail list logo