RANCID with Juniper logical-systems: Difference between revisions
From falz.net
Created page with "RANCID 3.x is nice in that it made some usable configuration files to define your own device types. If you happen to be in a scenario where you only have admin access to a log..." |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Network]] | |||
RANCID 3.x is nice in that it made some usable configuration files to define your own device types. If you happen to be in a scenario where you only have admin access to a logical-system in a Juniper device, you can't get "show chassis" or "show system" as that user. Workaround would be to define a new device type without those commands. | RANCID 3.x is nice in that it made some usable configuration files to define your own device types. If you happen to be in a scenario where you only have admin access to a logical-system in a Juniper device, you can't get "show chassis" or "show system" as that user. Workaround would be to define a new device type without those commands. | ||
Latest revision as of 09:37, 11 March 2018
RANCID 3.x is nice in that it made some usable configuration files to define your own device types. If you happen to be in a scenario where you only have admin access to a logical-system in a Juniper device, you can't get "show chassis" or "show system" as that user. Workaround would be to define a new device type without those commands.
- Added to rancid.types.conf:
# juniper logical system (cant show chassis stuff) juniper-ls;script;rancid -t juniper-ls juniper-ls;login;jlogin juniper-ls;module;junos juniper-ls;inloop;junos::inloop juniper-ls;command;junos::ShowVersion;show version detail juniper-ls;command;junos::ShowConfiguration;show configuration
- edit router.db to set the type from juniper to juniper-ls on that device.