[rancid] The new "alias" option in rancid.types.base does not seem to be working

[Bjørn Skobba]

On 18 Feb 2020, at 15:07, Vlad Olariu <florinvlad.olariu at gmail.com> wrote:
> 
> I recently upgrade to v3.10 and it seems force10 is an alias now. The problem is that my old force10 devices (since before the upgrade) now no longer work, with rancid throwing a "device type not recognised" error in the logs. I don't think this is force10-exclusive.
> 
> Could somebody be so kind to check this out? I don't have the option of upgrading, so I'd need to hack away at my local version of the file if a fix is released.


The force10 alias is pointing to dnos9, which is the new module for older Force10 switches running FTOS/OS9 or whatever it is called. Newer “Force10” switches (or “Dell EMC Powerswitch” as it has been rebranded to after Dell took over) will in many cases not be running FTOS/OS9, but for example OS10. The rancid module for this type is dnos10.

We do have both; 
- Switches running FTOS/OS9 and using the dnos9 type in rancid
- Switches running OS10 and using the dnos10 type in rancid.

Both working very well.

rancid at rancid:~/etc$ grep dnos *
rancid.types.base:dnos9;script;rancid -t dnos9
rancid.types.base:dnos9;login;clogin
rancid.types.base:dnos9;module;dnos9
rancid.types.base:dnos9;inloop;dnos9::inloop
rancid.types.base:dnos9;command;dnos9::ShowVersion;show version
rancid.types.base:dnos9;command;dnos9::ShowBoot;show bootvar
rancid.types.base:dnos9;command;dnos9::DirSlotN;dir flash:
rancid.types.base:dnos9;command;dnos9::DirSlotN;dir slot0:
rancid.types.base:dnos9;command;dnos9::ShowChassis;show chassis
rancid.types.base:dnos9;command;dnos9::ShowChassis;show system
rancid.types.base:dnos9;command;dnos9::ShowInventory;show inventory
rancid.types.base:dnos9;command;dnos9::ShowVLAN;show vlan
rancid.types.base:dnos9;command;dnos9::WriteTerm;show running
rancid.types.base:dnos10;script;rancid -t dnos10
rancid.types.base:dnos10;login;hlogin
rancid.types.base:dnos10;module;dnos10
rancid.types.base:dnos10;inloop;dnos10::inloop
rancid.types.base:dnos10;command;rancid::RunCommand;terminal length 0
rancid.types.base:dnos10;command;dnos10::ShowSys;show system
rancid.types.base:dnos10;command;dnos10::ShowVer;show version
rancid.types.base:dnos10;command;dnos10::ShowVlan;show vlan
rancid.types.base:dnos10;command;dnos10::WriteTerm;show running-configuration
rancid.types.base:force10;alias;dnos9
rancid.types.conf:dnos9bc;script;rancid -t dnos9
rancid.types.conf:dnos9bc;login;clogin
rancid.types.conf:dnos9bc;module;dnos9
rancid.types.conf:dnos9bc;inloop;dnos9::inloop
rancid.types.conf:dnos9bc;command;dnos9::ShowVersion;show version
rancid.types.conf:dnos9bc;command;dnos9::ShowBoot;show bootvar
rancid.types.conf:#dnos9bc;command;dnos9::DirSlotN;dir flash:
rancid.types.conf:#dnos9bc;command;dnos9::DirSlotN;dir slot0:
rancid.types.conf:dnos9bc;command;dnos9::ShowChassis;show chassis
rancid.types.conf:dnos9bc;command;dnos9::ShowChassis;show system
rancid.types.conf:dnos9bc;command;dnos9::ShowInventory;show inventory
rancid.types.conf:dnos9bc;command;dnos9::ShowVLAN;show vlan
rancid.types.conf:dnos9bc;command;dnos9::WriteTerm;show running

And then in router.db, I have:
sw1;dnos9bc;up
sw2;dnos10;up

I am not sure why you get the error you mentioned, others might be able to explain that - but maybe you could  try with “dnos9” as the type and see if that works?

BR
Bjørn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.shrubbery.net/pipermail/rancid-discuss/attachments/20200218/cf2f0677/attachment.htm>