Thu, Jan 17, 2019 at 06:44:03PM +0000, heasley:
> Thu, Jan 17, 2019 at 08:07:02AM +0100, Remko Lodder:
> > Hi,
> >
> > I also have “3.99.99” on the system to compare the output. The regular
> > version on the system is 3.6 it seems.
> > But, the noklogin works after modifying the u_prompt and p_prompt. When
> > running rancid -d -t sros <devicename>
> > it wants to execute commands that are not available at all on the Alcatel.
> >
> > The ones that I use from Burgalio’s :
> >
> > {'show chassis' => 'ShowChassis'},
> > {'show system' => 'ShowSystem'},
> > {'show module' => 'ShowModule'},
> > {'show stack topology' => 'ShowStackTopolgy'},
> > {'show lanpower 1' => 'ShowLanPower'},
> > {'show lanpower 2' => 'ShowLanPower'},
> > {'show user' => 'ShowUser'},
> > {'ls' => 'GenericParse'},
> > {'ls certified/' => 'GenericParse'},
> > {'ls working/' => 'GenericParse'},
> > {'ls switch/' => 'GenericParse'},
> > {'ls network/' => 'GenericParse'},
> > {'show vlan' => 'ShowVLAN'},
> > {'show interfaces status' => 'ShowInterfaces'},
> > {'show running' => 'ShowConf'},
> > {'show configuration snapshot' => 'ShowConf’},
> >
> > which does not match:
> >
> > xecuting noklogin -t 90 -c"show system information;file type
> > bootlog.txt;show redundancy synchronization;show chassis;show chassis
> > environment;show chassis power-supply;show chassis power-management;show
> > card state;show card detail;show debug;show bof;admin display-config
> > index;admin display-config” <devicename>
> >
> > Do note that it seems that the SROS is on a very different architecture
> > based then what my Omniswitches use. So it seems incompatible to start
> > with, where the alu* scripts might not entirely work with every command on
> > the OS6000 that I have, but most of them are accepted in older (legacy)
> > components but also on the newer
> > versions.
>
> testing & dev was done with 7750. I will enquire with my nokia contact
> about the omniswitch.
I'm told that these are totally separate from the Nokia systems I know and
will never converge. so, they should be handled separately, but I have
none to poke for debugging/testing.
> > Thanks
> > Remko
> >
> > > On 16 Jan 2019, at 18:39, heasley <h...@shrubbery.net> wrote:
> > >
> > > Wed, Jan 16, 2019 at 12:02:14PM +0100, Remko Lodder:
> > >> Hi all,
> > >>
> > >> First of all, thank you for Rancid, it’s a great tool to monitor
> > >> configuration changes and pushing back changes.
> > >>
> > >> Having Said that;
> > >>
> > >> I fetched some alcatel switches which I modified a little to work on
> > >> various types . These changes are trivial
> > >> changes from upstream so no real changes there actually.
> > >>
> > >> It seems that most switches work just fine, but that one particular
> > >> switch is not able to keep up with the
> > >> requests. It seems that this specific switch misses commands (like ls
> > >> and show interface status).
> > >> If I look back in the raw output it appears to miss characters:
> > >>
> > >> # how interfaces status
> > >> ^
> > >> ERROR: Invalid entry: “how”
I suspect that the login script it out of sync (ahead of) the cli. possibly
due to incorrectly matching a rogue prompt in some output or banner.
> > >> The same goes for ls, where ’s' is the command being send. Or for exit
> > >> at the end which is send as “xit”.
> > >>
> > >> The scripts are from: https://github.com/buraglio/alurancid (Thanks
> > >> buraglio) and apart from one switch work
> > >> fine it seems.
> > >>
> > >> Switching from SSH to Telnet does not make a difference.
> > >> Does someone have an suggestion on where to look?
> > >
> > > can you try the sros support that is in rancid 3.8 or the current alpha?
> >
>
_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@shrubbery.net
http://www.shrubbery.net/mailman/listinfo/rancid-discuss
