Mailing List Archive

Hello Everyone,

I was trying to do a google search for anyone using rancid with FS switches. It basically came up with nothing. So I thought I would post here. We are looking to add some FS S5500 switches to rancid. Has anyone written a plugin for these switches?

Best,

-Troy
_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net
https://www.shrubbery.net/mailman/listinfo/rancid-discuss

On Thu, May 7, 2020 at 10:54 PM Troy Beisigl <troy@i2bnetworks.com> wrote:
>
> I was trying to do a google search for anyone using rancid with FS switches. It basically came up with nothing. So I thought I would post here. We are looking to add some FS S5500 switches to rancid. Has anyone written a plugin for these switches?

Hi,
replying to an old message, but just chipping in to see if you got any
further with FS switches and rancid? We just got in a bunch of FS
S3900-48T4S and are looking to add them to rancid.

BR
Bjørn

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net
https://www.shrubbery.net/mailman/listinfo/rancid-discuss

Sun, Aug 08, 2021 at 02:11:22PM +0200, Bj?rn Skobba:
> On Thu, May 7, 2020 at 10:54 PM Troy Beisigl <troy@i2bnetworks.com> wrote:
> >
> > I was trying to do a google search for anyone using rancid with FS switches. It basically came up with nothing. So I thought I would post here. We are looking to add some FS S5500 switches to rancid. Has anyone written a plugin for these switches?
>
> Hi,
> replying to an old message, but just chipping in to see if you got any
> further with FS switches and rancid? We just got in a bunch of FS
> S3900-48T4S and are looking to add them to rancid.

In general, if it smells like an already supported device, that rancid
device type might work or at the least be a good starting point. Try
it; if it does not work, lmk and I'll help.

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net
https://www.shrubbery.net/mailman/listinfo/rancid-discuss

Hello Bjørn,

We looked at this for s short amount of time and got it put on the back burner as several other projects came up. I don’t recall exactly what I was able to figure out before that happened, but will see if I can take a look this week and see what I can dig up.

Best,

-Troy

> On Aug 8, 2021, at 5:11 AM, Bjørn Skobba <bjorn@basis-consulting.com> wrote:
>
> On Thu, May 7, 2020 at 10:54 PM Troy Beisigl <troy@i2bnetworks.com> wrote:
>>
>> I was trying to do a google search for anyone using rancid with FS switches. It basically came up with nothing. So I thought I would post here. We are looking to add some FS S5500 switches to rancid. Has anyone written a plugin for these switches?
>
> Hi,
> replying to an old message, but just chipping in to see if you got any
> further with FS switches and rancid? We just got in a bunch of FS
> S3900-48T4S and are looking to add them to rancid.
>
> BR
> Bjørn

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net
https://www.shrubbery.net/mailman/listinfo/rancid-discuss

On Sun, Aug 8, 2021 at 5:45 PM heasley <heas@shrubbery.net> wrote:
>
> Sun, Aug 08, 2021 at 02:11:22PM +0200, Bjørn Skobba:
> > On Thu, May 7, 2020 at 10:54 PM Troy Beisigl <troy@i2bnetworks.com> wrote:
> > >
> > > I was trying to do a google search for anyone using rancid with FS switches. It basically came up with nothing. So I thought I would post here. We are looking to add some FS S5500 switches to rancid. Has anyone written a plugin for these switches?
> >
> > Hi,
> > replying to an old message, but just chipping in to see if you got any
> > further with FS switches and rancid? We just got in a bunch of FS
> > S3900-48T4S and are looking to add them to rancid.
>
> In general, if it smells like an already supported device, that rancid
> device type might work or at the least be a good starting point. Try
> it; if it does not work, lmk and I'll help.

Thanks! :) I tested a few device types and it seems like I can use
dnos9. I added this to rancid.types.conf:
dnos9fs;script;rancid -t dnos9fs
dnos9fs;login;clogin
dnos9fs;module;dnos9
dnos9fs;inloop;dnos9::inloop
dnos9fs;command;dnos9::ShowVersion;show version
dnos9fs;command;dnos9::ShowBoot;show boot
dnos9bc;command;dnos9::DirSlotN;dir
dnos9fs;command;dnos9::ShowChassis;show system
dnos9fs;command;dnos9::ShowVLAN;show vlan all
dnos9fs;command;dnos9::WriteTerm;show running-config

Seems to give me what I need. The output is quite "airy"(as in lots of
empty lines ), but so is the output from show running-config on the
actual switch.

/bjørn

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net
https://www.shrubbery.net/mailman/listinfo/rancid-discuss

Wed, Aug 11, 2021 at 01:48:06PM +0200, Bj?rn Skobba:
> On Sun, Aug 8, 2021 at 5:45 PM heasley <heas@shrubbery.net> wrote:
> >
> > Sun, Aug 08, 2021 at 02:11:22PM +0200, Bj?rn Skobba:
> > > On Thu, May 7, 2020 at 10:54 PM Troy Beisigl <troy@i2bnetworks.com> wrote:
> > > >
> > > > I was trying to do a google search for anyone using rancid with FS switches. It basically came up with nothing. So I thought I would post here. We are looking to add some FS S5500 switches to rancid. Has anyone written a plugin for these switches?
> > >
> > > Hi,
> > > replying to an old message, but just chipping in to see if you got any
> > > further with FS switches and rancid? We just got in a bunch of FS
> > > S3900-48T4S and are looking to add them to rancid.
> >
> > In general, if it smells like an already supported device, that rancid
> > device type might work or at the least be a good starting point. Try
> > it; if it does not work, lmk and I'll help.
>
> Thanks! :) I tested a few device types and it seems like I can use
> dnos9. I added this to rancid.types.conf:
> dnos9fs;script;rancid -t dnos9fs
> dnos9fs;login;clogin
> dnos9fs;module;dnos9
> dnos9fs;inloop;dnos9::inloop
> dnos9fs;command;dnos9::ShowVersion;show version
> dnos9fs;command;dnos9::ShowBoot;show boot
> dnos9bc;command;dnos9::DirSlotN;dir
^^ typo? that will not be included in the collect, obviously.
> dnos9fs;command;dnos9::ShowChassis;show system
> dnos9fs;command;dnos9::ShowVLAN;show vlan all
> dnos9fs;command;dnos9::WriteTerm;show running-config

Does their O/S have a name?

> Seems to give me what I need. The output is quite "airy"(as in lots of
> empty lines ), but so is the output from show running-config on the
> actual switch.
>
> /bj?rn

This would trim all the blank lines in the config. dell nos does not appear
to output blank lines.

diff --git a/lib/dnos9.pm.in b/lib/dnos9.pm.in
index 1bb52dde..b6950202 100644
--- a/lib/dnos9.pm.in
+++ b/lib/dnos9.pm.in
@@ -363,7 +363,8 @@ sub WriteTerm {
# skip crap
/^Current Configuration/ && next;
/^! (version|last configuration|startup-config last)/i && next;
-
+ # skip empty lines at the beginning
+ next if (/^\s*$/);

# Dog gone Cool matches to process the rest of the config
/^tftp-server flash / && next; # kill any tftp remains

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net
https://www.shrubbery.net/mailman/listinfo/rancid-discuss

It's not the same as the Dell NOS, but I recall hearing that it shares some lineage in the distant, dusty past. (Well, as dusty as something that's only existed for <10yrs can be, anyway.) So it makes sense it would be quite similar. I've installed them for customers, but don't have any here to test with.

NOTE: different FS.com switch product lines use different OSes. Not sure how different, but definitely not a unified software for all products. (Again, this makes sense, it's all just vendor reference designs with the FS.com logo slapped onto it.)

-Adam

Adam Thompson
Consultant, Infrastructure Services
[1593169877849]
100 - 135 Innovation Drive
Winnipeg, MB, R3T 6A8
(204) 977-6824 or 1-800-430-6404 (MB only)
athompson@merlin.mb.ca<mailto:athompson@merlin.mb.ca>
www.merlin.mb.ca<http://www.merlin.mb.ca/>
________________________________
From: Rancid-discuss <rancid-discuss-bounces@www.shrubbery.net> on behalf of heasley <heas@shrubbery.net>
Sent: August 11, 2021 10:03
To: Bj?rn Skobba <bjorn@basis-consulting.com>
Cc: Troy Beisigl <troy@i2bnetworks.com>; rancid-discuss@shrubbery.net <rancid-discuss@shrubbery.net>
Subject: Re: [rancid] FS switches

Wed, Aug 11, 2021 at 01:48:06PM +0200, Bj?rn Skobba:
> On Sun, Aug 8, 2021 at 5:45 PM heasley <heas@shrubbery.net> wrote:
> >
> > Sun, Aug 08, 2021 at 02:11:22PM +0200, Bj?rn Skobba:
> > > On Thu, May 7, 2020 at 10:54 PM Troy Beisigl <troy@i2bnetworks.com> wrote:
> > > >
> > > > I was trying to do a google search for anyone using rancid with FS switches. It basically came up with nothing. So I thought I would post here. We are looking to add some FS S5500 switches to rancid. Has anyone written a plugin for these switches?
> > >
> > > Hi,
> > > replying to an old message, but just chipping in to see if you got any
> > > further with FS switches and rancid? We just got in a bunch of FS
> > > S3900-48T4S and are looking to add them to rancid.
> >
> > In general, if it smells like an already supported device, that rancid
> > device type might work or at the least be a good starting point. Try
> > it; if it does not work, lmk and I'll help.
>
> Thanks! :) I tested a few device types and it seems like I can use
> dnos9. I added this to rancid.types.conf:
> dnos9fs;script;rancid -t dnos9fs
> dnos9fs;login;clogin
> dnos9fs;module;dnos9
> dnos9fs;inloop;dnos9::inloop
> dnos9fs;command;dnos9::ShowVersion;show version
> dnos9fs;command;dnos9::ShowBoot;show boot
> dnos9bc;command;dnos9::DirSlotN;dir
^^ typo? that will not be included in the collect, obviously.
> dnos9fs;command;dnos9::ShowChassis;show system
> dnos9fs;command;dnos9::ShowVLAN;show vlan all
> dnos9fs;command;dnos9::WriteTerm;show running-config

Does their O/S have a name?

> Seems to give me what I need. The output is quite "airy"(as in lots of
> empty lines ), but so is the output from show running-config on the
> actual switch.
>
> /bj?rn

This would trim all the blank lines in the config. dell nos does not appear
to output blank lines.

diff --git a/lib/dnos9.pm.in b/lib/dnos9.pm.in
index 1bb52dde..b6950202 100644
--- a/lib/dnos9.pm.in
+++ b/lib/dnos9.pm.in
@@ -363,7 +363,8 @@ sub WriteTerm {
# skip crap
/^Current Configuration/ && next;
/^! (version|last configuration|startup-config last)/i && next;
-
+ # skip empty lines at the beginning
+ next if (/^\s*$/);

# Dog gone Cool matches to process the rest of the config
/^tftp-server flash / && next; # kill any tftp remains

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net
https://www.shrubbery.net/mailman/listinfo/rancid-discuss

On Wed, Aug 11, 2021 at 5:03 PM heasley <heas@shrubbery.net> wrote:
>
> Wed, Aug 11, 2021 at 01:48:06PM +0200, Bjørn Skobba:

> > dnos9bc;command;dnos9::DirSlotN;dir
> ^^ typo? that will not be included in the collect, obviously.

Thanks for pointing that out. Indeed a typo.

> Does their O/S have a name?

I am not sure to be honest, it seems to be called fsos in some cases,
but there might also be variations between the different switch models
as pointed out by Adam in this thread. We only have the S3900 series,
so I cannot verify it.

However, our Layer2 dude pointed out the os also was a bit cisco-ish,
so I tried the cisco device type (ios module) and that worked fine as
well . To make it more tailored to these switches I fiddled a bit with
stuff I'm not really able to do (I'm not a (perl) programmer...):
The ios module didn't have a ShowChassis routine, so I copied the ios
module to a new one and added the ShowChassis routine from the dnos9
module and added this to rancid.types.conf:

fscom;script;rancid -t fscom
fscom;login;clogin
fscom;module;fscom
fscom;inloop;fscom::inloop
fscom;command;fscom::ShowChassis;show system
fscom;command;fscom::ShowVersion;show version
fscom;command;fscom::ShowBoot;show boot
fscom;command;fscom::DirSlotN;dir
fscom;command;fscom::ShowDot1x;show dot1x
fscom;command;fscom::ShowVLAN;show vlan all
fscom;command;fscom::ShowDebug;show debug
fscom;command;fscom::WriteTerm;show running-config

So just another way to achieve more or less the same.

/bjørn

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net
https://www.shrubbery.net/mailman/listinfo/rancid-discuss

I would suggest providing a show version, listing from a boot sequence
or similar might be helpful.
Focus on the ones you want first and expand from there.

On Thu, Aug 12, 2021 at 10:14 AM Bjørn Skobba
<bjorn@basis-consulting.com> wrote:
>
> On Wed, Aug 11, 2021 at 5:03 PM heasley <heas@shrubbery.net> wrote:
> >
> > Wed, Aug 11, 2021 at 01:48:06PM +0200, Bjørn Skobba:
>
> > > dnos9bc;command;dnos9::DirSlotN;dir
> > ^^ typo? that will not be included in the collect, obviously.
>
> Thanks for pointing that out. Indeed a typo.
>
> > Does their O/S have a name?
>
> I am not sure to be honest, it seems to be called fsos in some cases,
> but there might also be variations between the different switch models
> as pointed out by Adam in this thread. We only have the S3900 series,
> so I cannot verify it.
>
> However, our Layer2 dude pointed out the os also was a bit cisco-ish,
> so I tried the cisco device type (ios module) and that worked fine as
> well . To make it more tailored to these switches I fiddled a bit with
> stuff I'm not really able to do (I'm not a (perl) programmer...):
> The ios module didn't have a ShowChassis routine, so I copied the ios
> module to a new one and added the ShowChassis routine from the dnos9
> module and added this to rancid.types.conf:
>
> fscom;script;rancid -t fscom
> fscom;login;clogin
> fscom;module;fscom
> fscom;inloop;fscom::inloop
> fscom;command;fscom::ShowChassis;show system
> fscom;command;fscom::ShowVersion;show version
> fscom;command;fscom::ShowBoot;show boot
> fscom;command;fscom::DirSlotN;dir
> fscom;command;fscom::ShowDot1x;show dot1x
> fscom;command;fscom::ShowVLAN;show vlan all
> fscom;command;fscom::ShowDebug;show debug
> fscom;command;fscom::WriteTerm;show running-config
>
> So just another way to achieve more or less the same.
>
> /bjørn
>
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss@www.shrubbery.net
> https://www.shrubbery.net/mailman/listinfo/rancid-discuss

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net
https://www.shrubbery.net/mailman/listinfo/rancid-discuss

Thu, Aug 12, 2021 at 04:14:21PM +0200, Bj?rn Skobba:
> However, our Layer2 dude pointed out the os also was a bit cisco-ish,
> so I tried the cisco device type (ios module) and that worked fine as
> well . To make it more tailored to these switches I fiddled a bit with
> stuff I'm not really able to do (I'm not a (perl) programmer...):
> The ios module didn't have a ShowChassis routine, so I copied the ios
> module to a new one and added the ShowChassis routine from the dnos9
> module and added this to rancid.types.conf:
>
> fscom;script;rancid -t fscom
> fscom;login;clogin
> fscom;module;fscom
> fscom;inloop;fscom::inloop
> fscom;command;fscom::ShowChassis;show system
> fscom;command;fscom::ShowVersion;show version
> fscom;command;fscom::ShowBoot;show boot
> fscom;command;fscom::DirSlotN;dir
> fscom;command;fscom::ShowDot1x;show dot1x
> fscom;command;fscom::ShowVLAN;show vlan all
> fscom;command;fscom::ShowDebug;show debug
> fscom;command;fscom::WriteTerm;show running-config
>
> So just another way to achieve more or less the same.

fwiw, it is possible include multiple modules with more recent rancid
versions, like:

foo;module;ios
foo;module;fscom
foo;command;fscom::ShowChassis;show system
foo;command;ios::ShowVersion;show version

and more recent still, a type name can aliased:

fscom;alias;dnos9

if any of that helps.

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net
https://www.shrubbery.net/mailman/listinfo/rancid-discuss

On Fri, Aug 13, 2021 at 8:56 PM heasley <heas@shrubbery.net> wrote:
>
> Thu, Aug 12, 2021 at 04:14:21PM +0200, Bjørn Skobba:
> > However, our Layer2 dude pointed out the os also was a bit cisco-ish,
> > so I tried the cisco device type (ios module) and that worked fine as
> > well . To make it more tailored to these switches I fiddled a bit with
> > stuff I'm not really able to do (I'm not a (perl) programmer...):
> > The ios module didn't have a ShowChassis routine, so I copied the ios
> > module to a new one and added the ShowChassis routine from the dnos9
> > module and added this to rancid.types.conf:
>
> fwiw, it is possible include multiple modules with more recent rancid
> versions, like:
>
> foo;module;ios
> foo;module;fscom
> foo;command;fscom::ShowChassis;show system
> foo;command;ios::ShowVersion;show version
>
> and more recent still, a type name can aliased:
>
> fscom;alias;dnos9
>
> if any of that helps.

Ahh, brilliant. I had forgotten about the aliasing, and didn't know
about the multiple modules. Will look into that at some stage - our
rancid installation could do with some TLC anyway ;)

Thanks for kind help and pointers as always.

/bjørn

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net
https://www.shrubbery.net/mailman/listinfo/rancid-discuss