[rancid] managing supermicro switches.

Discussion:

Jason Welsh

2013-11-07 15:32:36 UTC

Has anyone figured out how to do it? They are quite "IOS" like, but not
exactly..

***@srv01 ~:$ /usr/local/rancid/bin/clogin -c "show clock" backbone
backbone
spawn ssh -c 3des -x -l user backbone
***@backbone's password:

Supermicro Switch

backbone#
backbone# terminal length 0
% Invalid Command
backbone# terminal width 132
% Invalid Command
backbone# show clock

Thu Nov 07 07:48:44 2013
backbone#exit
Received disconnect from 10.11.12.13: 2: Connection Closed
***@srv01 ~:$

suggestions?

Jason

Alan McKinnon

2013-11-07 16:02:40 UTC

Permalink

Post by Jason Welsh
Has anyone figured out how to do it? They are quite "IOS" like, but not
exactly..
backbone
spawn ssh -c 3des -x -l user backbone
Supermicro Switch
backbone#
backbone# terminal length 0
% Invalid Command
backbone# terminal width 132
% Invalid Command
backbone# show clock
Thu Nov 07 07:48:44 2013
backbone#exit
Received disconnect from 10.11.12.13: 2: Connection Closed
suggestions?

This was asked a year ago, this is the entire thread:

http://www.shrubbery.net/pipermail/rancid-discuss/2012-October/006539.html

The original poster didn't answer back with any results.

You might have to implement you own parser script (it's really not that
hard at all). Can you give some idea of just how different they are from
IOS? Is it a few commands that are different, or as much as it works
like IOS but with completely differnt commands?

If this problem is not already solved with code out there, posting a
list of supported commands would be a good start to getting you up and
running.

--
Alan McKinnon
***@gmail.com

Jason Welsh

2013-11-07 16:13:03 UTC

Permalink

well theyre documented at
http://www.supermicro.com/manuals/network/smc_switches_cli_manual.pdf
but it seems the main problem is that the command

"write term" doesnt work, but "show run" does.

regards,
Jason

Post by Alan McKinnon

http://www.shrubbery.net/pipermail/rancid-discuss/2012-October/006539.html
The original poster didn't answer back with any results.
You might have to implement you own parser script (it's really not that
hard at all). Can you give some idea of just how different they are from
IOS? Is it a few commands that are different, or as much as it works
like IOS but with completely differnt commands?
If this problem is not already solved with code out there, posting a
list of supported commands would be a good start to getting you up and
running.

heasley

2013-11-07 16:48:21 UTC

Permalink

Post by Jason Welsh
well theyre documented at
http://www.supermicro.com/manuals/network/smc_switches_cli_manual.pdf
but it seems the main problem is that the command
"write term" doesnt work, but "show run" does.

then use rancid 3.0aN with your own device definition excluding that command.

Post by Jason Welsh
regards,
Jason

Post by Alan McKinnon

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

Jason Welsh

2013-11-07 19:50:41 UTC

Permalink

so im using the rancid-3.0a3 and ive gotten it to run, but it doesnt
seem to be working.. all I see in the logs is

starting: Thu Nov 7 11:27:52 PST 2013

ending: Thu Nov 7 11:27:52 PST 2013

***@srv01 ~:$ bin/clogin -c"sh ver" backbone
backbone
spawn ssh -c 3des -x -l jwelsh backbone
***@backbone's password:

Supermicro Switch

backbone#
backbone# terminal length 0
% Invalid Command
backbone# terminal width 132
% Invalid Command
backbone# sh ver
Switch ID Hardware Version Firmware Version
0 SSE-X24 B (P3-01) 1.0.3-2
backbone#exit
Received disconnect from 10.11.12.13: 2: Connection Closed
***@srv01 ~:$ bin/clogin -V
rancid 3.0a3
***@srv01 ~:$

individual commands seem to run fine, but when i run
bin/rancid-run
it comes back to the prompt quickly and shows the above (nothing) in the
logs

regards,
Jason

Post by heasley

then use rancid 3.0aN with your own device definition excluding that command.

Post by Jason Welsh
regards,
Jason

Post by Alan McKinnon

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

heasley

2013-11-07 20:08:35 UTC

Permalink

Post by Jason Welsh
so im using the rancid-3.0a3 and ive gotten it to run, but it doesnt
seem to be working.. all I see in the logs is
starting: Thu Nov 7 11:27:52 PST 2013
ending: Thu Nov 7 11:27:52 PST 2013

<group>/routers.up is probably empty. check your router.db format. note
that the : separator was changed to ; to accomodate ipv6 addresses.

Jason Welsh

2013-11-08 14:20:30 UTC

Permalink

I forgot to say that using the : as the separator was the issue.. I
changed it to ;
that fixed the issue with the empty log file.

Post by heasley
<group>/routers.up is probably empty. check your router.db format. note
that the : separator was changed to ; to accomodate ipv6 addresses.

regards,

Jason

Jason Welsh

2013-11-08 15:23:55 UTC

Permalink

Post by heasley
<group>/routers.up is probably empty. check your router.db format. note
that the : separator was changed to ; to accomodate ipv6 addresses.

ok, my mistake, editing the etc/rancid.types.base was the right thing
to do.. I cut out all the non-working commands.
It seems to be working now.. The only issue left (i hope) is this in
the logs.

Trying to get all of the configs.
backbone: End of run not found

=====================================
Getting missed routers: round 1.
backbone: End of run not found

=====================================
Getting missed routers: round 2.
backbone: End of run not found

=====================================
Getting missed routers: round 3.
backbone: End of run not found

=====================================
Getting missed routers: round 4.
backbone: End of run not found

I see in the var/networking/configs directory a
backbone.raw and a backbone.new (which seem to have the config info
that rancid is gathering during the run but disappear at the end of the run)
while rancid is running, but when rancid is done, the backbone config
file in this directory is left empty..
Im guessing it should have something in it ?

regards,
Jason

heasley

2013-11-08 16:31:31 UTC

Permalink

Post by Jason Welsh

Post by heasley
<group>/routers.up is probably empty. check your router.db format. note
that the : separator was changed to ; to accomodate ipv6 addresses.

ok, my mistake, editing the etc/rancid.types.base was the right thing
to do.. I cut out all the non-working commands.

actually it is not, as noted at the top of that file. you should copy the
cisco definition to etc/rancid.types.conf, rename it (ciscolocal or similar)
and alter the command list there.

Post by Jason Welsh
It seems to be working now.. The only issue left (i hope) is this in
the logs.
Trying to get all of the configs.
backbone: End of run not found
=====================================
Getting missed routers: round 1.
backbone: End of run not found
=====================================
Getting missed routers: round 2.
backbone: End of run not found
=====================================
Getting missed routers: round 3.
backbone: End of run not found
=====================================
Getting missed routers: round 4.
backbone: End of run not found
I see in the var/networking/configs directory a
backbone.raw and a backbone.new (which seem to have the config info
that rancid is gathering during the run but disappear at the end of the run)
while rancid is running, but when rancid is done, the backbone config
file in this directory is left empty..
Im guessing it should have something in it ?

yes, something is failing during the collection. look at the logs and you
can test with

NOPIPE=YES; export NOPIPE
grancid -t ciscolocal -d devicename

Jason Welsh

2013-11-08 17:35:54 UTC

Permalink

Post by heasley

Post by Jason Welsh

Post by heasley
<group>/routers.up is probably empty. check your router.db format. note
that the : separator was changed to ; to accomodate ipv6 addresses.

ok, my mistake, editing the etc/rancid.types.base was the right thing
to do.. I cut out all the non-working commands.

actually it is not, as noted at the top of that file. you should copy the
cisco definition to etc/rancid.types.conf, rename it (ciscolocal or similar)
and alter the command list there.

yes, something is failing during the collection. look at the logs and you
can test with
NOPIPE=YES; export NOPIPE
grancid -t ciscolocal -d devicename
.

***@srv01 ~:$ NOPIPE=YES; export NOPIPE
***@srv01 ~:$ grancid -t supermicro -d backbone
loadtype: device type supermicro
loadtype: found device type supermicro in
/usr/local/rancid/etc/rancid.types.conf
executing clogin -t 90 -c"show version;show vlan;show running-config"
backbone
PROMPT MATCH: backbone#
HIT COMMAND:backbone# show version
In ShowVersion: backbone# show version
HIT COMMAND:backbone# show vlan
In ShowVLAN: backbone# show vlan
HIT COMMAND:backbone# show running-config
In WriteTerm: backbone# show running-config
backbone: End of run not found
backbone: End of run not found

***@srv01 ~:$

thanks/regards,
Jason

Jason Welsh

2013-11-07 20:41:48 UTC

Permalink

Post by heasley
then use rancid 3.0aN with your own device definition excluding that command.

im guessing "excluding that command" in the device definition means editing
~/etc/rancid.types.base
and commenting out the line
cisco;command;ios::WriteTerm;show run
???
that didnt seem to work.. please clarify.

thanks/regards,
Jason