This is the modern Python re-implementation of the battle-proven Zino network state monitor, first implemented in Tcl/Scotty at Uninett in the 1990s.

An incomplete list of features that have yet to be ported from legacy Zino:

• No support for reading trap messages from a trap multiplexer like straps/nmtrapd. This type of functionality may potentially be achieved by employing general packet multiplexers. See issue #362 for more details.

Development of Zino 2.0 is fully sponsored by NORDUnet, on behalf of the nordic NRENs.

• What is Zino?
• Installing
• Configuring
• Using
• Upgrade from Zino 1
• Contributing

Zino Is Not OpenView.

Zino is an SNMP network monitor that began its life at Uninett in the mid 1990s. It was a homegrown system written in Tcl, specifically to monitor the routers of the Norwegian national research network (NREN), a large backbone network that connects the widely geographically dispersed higher education and research institutions of Norway. Uninett was also part of NORDUnet, the collaboration that interconnects the NRENs of the Nordic countries, and Zino is also utilized to monitor the NORDUnet backbone.

Here's a quote about its features from the README file of the original Tcl codebase:

 o Trap-driven polling; receives and interprets traps.
 o Periodic status polling (by default low frequency).
 o A simplistic event handling system.
 o A simple SMTP-like client/server protocol.
 o A TK-based user interface.

all in a little under 5000 lines of Tcl.

This project aims to port all this to Python, except for the TK-based user interface. The Python implementation keeps backwards compatibility with the "simple SMTP-like client/server protocol", so that the existing user interface clients can be re-used (such as Ritz and cuRitz).

Zino is essentially a small program that can run in the background, monitoring your router network for:

• Link state
• BGP session state
• BFD session state
• Juniper chassis alarms

All changes will result in an "event" (aka a "case"), in which Zino will log all further related changes until the case is manually closed by a human operator via the server protocol on port 8001 (essentially through some user interface).

Notifications are typically achieved by having a client program to fetch active events from the Zino server and decide from that which notifications need to be sent.

Zino has very few dependencies, other than the Python packages required to run it. Zino serializes its running state to a JSON file on disk, and can resume its work from this file when restarted.

Redundancy can thus be achieved by running two or more Zino servers in parallel. A typical solution is for one server to be the "master", and the other to be a "hot standby". To ensure the master and the standby are mostly in sync, a typical solution is to transfer the state dump from the master to the standby every 24 hours and then restarting the standby from the master's state dump. Zino clients can be typically be configured to automatically switch to using a standby server if the master is unavailable.

You need a supported Python version, and these days a virtualenv for dependencies. You also need to choose one of two supported SNMP libraries, by default it is backed by a C-library, Net-SNMP.

We recommend you create a user to own zino's files instead of having everything be owned by root

See Installation for the full details.

Zino must have at minimum one configuration file: polldevs.cf, which keeps track of at least one SNMP-enabled router to monitor. See Configuring for the details.

This package only represents the Zino server backend. In order to meaningfully interface with Zino as a user, you will want a remote interface to Zino. Several remote interfaces exist.

• curitz is a curses-based terminal application to interface with Zino. It is currently the best client for day-to-day use.

• Ritz is the original Remote Interface To Zino. It is an X11 desktop application written in Tcl/Tk. Unfortunately, the source code isn't currently available.

• Howitz is a web-based remote interface to Zino that was originally written as part of the Zino 2.0 project. However, it has since been discontinued in favor of integration with Argus using the zino-argus glue service.

Contributions are welcome, at this point especially bug reports (patches welcome), missing documentation, how to's and usage tips!

See Developing Zino for tips, expectations and assumptions.