IS-IS / SPBM / I-SID support for Extreme VOSS/FabricEngine and BOSS/ERS

Hi,

I have prepared a patch that adds IS-IS/SPBM support to Observium, with a focus on Extreme Networks VOSS/FabricEngine and BOSS/ERS platforms.

The main goal is to make SPBM fabrics more visible in Observium in the same way other routing protocols and neighbour protocols are already represented. The patch adds polling, UI pages, graphs, alerting support and I-SID visibility.

Main features included:

• IS-IS discovery and polling using both standard ISIS-MIB and Extreme/Rapid-City RC-ISIS-MIB

• Support for Extreme VOSS/FabricEngine SPBM data

• Support for BOSS/ERS devices where ISIS-MIB is available

• Device-level Routing -> IS-IS page

• Global /routing/protocol=isis/ overview

• Global /isid/ inventory page

• Main menu entries for Network -> IS-IS and Network -> I-SIDs

• IS-IS/SPBM adjacencies shown directly on the port view, similar to LLDP/CDP neighbours

• Fabric node discovery/table

• I-SID discovery including origin information such as manually configured, EAP learned and auto-sense related entries

• RRD graph support for adjacency counts, adjacency state counts, areas, ports and packet counters where available

• Alert Checker support for:

• • IS-IS instances

• • IS-IS adjacencies

• • adjacency count checks

• • adjacency state checks

• Consolidated SQL schema update in a single update/533.sql file

This was tested on Observium Professional 26.6 / SVN rev 14882 with Extreme VOSS/FabricEngine and BOSS/ERS devices. The implementation was intentionally kept aligned with existing Observium concepts: routing protocol pages, entity definitions, Alert Checker integration, graph definitions and port neighbour display.

The feature is especially useful for SPBM environments, because it allows operators to quickly answer questions like:

• Which IS-IS/SPBM adjacencies are currently up or down?

• Which fabric nodes are visible from a given switch?

• Which I-SIDs exist in the fabric?

• Which I-SIDs are locally configured and which were learned dynamically, for example via EAP?

• Has a device lost one or more expected IS-IS adjacencies?

• Which physical port is an IS-IS neighbour connected to?

I think this would be a useful addition to Observium because Extreme FabricEngine/SPBM deployments are common in campus and enterprise networks, but the IS-IS/SPBM visibility is currently quite limited compared to protocols like OSPF, BGP, LLDP or CDP.

The patch is provided as a single consolidated developer patch, with a README and file list included. The SQL update number is only a proposal and can of course be renumbered to the next appropriate Observium update number.