Juniper Network Connect and Crashplan use the same network ports

I actually found this problem months ago. Today I decided I needed to blog it mostly as a reminder to myself.

After upgrading CrashPlan on my computer, I found that the service would not start. The tray icon reported "unable to connect to the backup engine".

CrashPlan has a good article on the problem and how to fix it.

A solution not listed -- uninstall Juniper Network Connect! (I didn't need it any more)

rancid 3.x - juniper display set

I found a lot of directions on the net for how to change rancid 2.x to do "display set" for juniper switches, but none for rancid 3.x (this was tested on rancid 3.1.2 on CentOS 6.6)

It's actually pretty easy:

1. Find your switch type (in this case "juniper") in /etc/rancid/rancid.types.base and copy those lines into /etc/rancid/rancid.types.conf:
   
   juniper;script;rancid -t juniper
   juniper;login;jlogin
   [...]
   juniper;command;junos::ShowConfiguration;show configuration
   
   
2. Now change "juniper" to some unique string that doesn't exist in rancid.types.base, e.g. "juniper-dset"
3. Modify all the "juniper" strings in rancid.types.conf to be "juniper-dset"
   
   juniper-dset;script;rancid -t juniper-dset
   juniper-dset;login;jlogin
   [...]
   juniper-dset;command;junos::ShowConfiguration;show configuration
   
   
4. Add a new line to do the display set:
   
   juniper-dset;command;junos::ShowConfiguration;show configuration | display set | no-more
   
   It's up to you whether you want that before or after the normal multi-line "show configuration".


5. Also, change /var/rancid/router.db to change the "juniper" switch type to "juniper-dset"