Re: [rancid] Help Using git with RANCID

[Ryan Melville]

Thank you for the advice, which got me on the right track.  I think those 
commands probably would have worked as-is, but my ideal state was having 
RANCID's local git workspace wire directly back to my git server *only* and not 
also push to the local ($CVSROOT) git repo.

So my steps were the following, picking up after the "sudo -H -u rancid 
/mnt/rancid/rancid/bin/rancid-cvs" command:

1) Create new empty 'rancid-' repository on my (external) master git 
server (Atlassian Bitbucket, in my case).

2) Create 'rancid' user on my master git server, and give it read/write 
permission to the new repo.

3) Store 'rancid' user git credentials on my RANCID server, which requires a 
temporary clone that is then immediately deleted.

sudo -H -u rancid git config --global user.name "rancid"
sudo -H -u rancid git config --global user.email "rancid@"
sudo -H -u rancid git config --global credential.helper store
sudo -H -u rancid git clone 
https://rancid@/scm/rancid-.git
(enter 'rancid' user passwords when prompted)
sudo -H -u rancid rm -rf rancid-all

4) Re-wire RANCID's git workspace to the master git server, instead of its 
local git server/repo.  Uses my particular RANCID installation path and group 
name ("all").

cd /mnt/rancid/rancid/var/all
sudo -H -u rancid git remote set-url origin 
https://rancid@/scm/rancid-all.git
sudo -H -u rancid git push -u origin --all
sudo -H -u rancid git push origin --tags


At this point, I made a change to a network device, waited for my next cron 
execution of rancid-run, and then observed the changes in my master git repo, 
so I believe it was all working well.

Regards,

Ryan Melville

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

Re: [rancid] Login to Dell N3048p switch

[heasley]

Tue, Aug 21, 2018 at 12:26:23PM -0400, Technology Support:
> I got Rancid 3.8 up and running and I am able to get email alerts. It works
> well with Cisco switch.
> However, our core switches are Dell N3048p.
> I tried many combinations in the router.db file like the below
> 
> *192.168.1.1;dell;up*
> *192.168.1.1;dlink;up*
> *192.168.1.1;smc;up*
> *192.168.1.1;force10;up*
> 
> This is based on what I was reading in several support forums.
> When I am running
> 
> */usr/local/rancid/bin/dllogin 192.168.1.1*
> OR
> 
> */usr/local/rancid/bin/clogin 192.168.1.1 *
> OR
> */usr/local/rancid/bin/hlogin 192.168.1.1*
> 
> 
> They are all able to login to the switch with no issue.

Section 3 Q 2 of the FAQ has basic testing procedure.  Please follow
this to narrow the problem.

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