Welcome to docs.opsview.com

Opsview RANCID Architecture


RANCID consists of two components:

  • RANCID collector - this runs the RANCID application to collect the router configuration information. This would usually be installed on Opsview slaves and Opsview Master
  • RANCID master - this is the central RANCID repository, which holds the configuration information (stored using Subversion). This also includes some integration code with Opsview. This is on the Opsview master

RANCID also depends on activemq for messaging.

In a clustered slave scenario, the hosts for that slave are load balanced between the clustered nodes. If a node fails, there is no takeover because RANCID is not considered a major service.


NetAudit is supported on the same platforms that Opsview is supported on.


This requires Opsview. While RANCID may work with previous versions of Opsview, it is only supported on the version of Opsview that it is shipped with.


There are 3 packages required in addition to Opsview and messaging:

  • Opsview Rancid Collector: opsview-rancid-collector (Debian/Redhat)
  • Opsview Rancid Master: opsview-rancid-master (Debian/Redhat)
  • Opsview Rancid: opsview-rancid (Debian/Redhat)

Opsview Rancid Collector

RANCID core code with some helper scripts. This is installed into /opt/opsview/rancid on Opsview master or slaves.

Opsview Rancid Master

RANCID master, holding the history of all router configuration. This also contains the Web UI to display subversion repositories.

This is installed into /opt/opsview/rancid. This is installed on the Opsview master.

Opsview Rancid

This provides iIntegration with Opsview Core. This is installed on the Opsview master.

Supported Vendors

  • AGM
  • Alteon
  • Baynet
  • Cat5
  • Cisco
  • CSS
  • Ellacoya
  • Enterasys
  • ERX
  • Extreme
  • EZT3
  • Force10
  • Foundry
  • Hitachi
  • HP
  • Juniper
  • MRTD
  • Netscaler
  • Netscreen
  • Procket
  • Redback
  • Riverstone
  • SMC
  • TNT
  • Zebra