3 ms·
the first and most important thing is to have the correct network architecture and engineering to make effective use of the tools, and not have a network that n
by walrus01 6y ago
the first and most important thing is to have the correct network architecture and engineering to make effective use of the tools, and not have a network that needs a lot of babysitting in the first place. after that's taken care of as an over-arching and continual business process:
there is no one single god box piece of software that is the be-all and do-all of network management/monitoring for an ISP. Some things come close, such as LibreNMS when used as the sole tool for a small ISP. But most often it is a patchwork quilt of many different things, each used for a discrete purpose.
in no particular order:
opennms
a combination of (influxdb + telegraf + grafana)
librenms
provisioning and automation tools like ansible
various in house things built on traditional RRA files and rrdtool
tools like netbox for keeping track of datacenter customers/hosting environments
phpipam or nipap for IP address management
various self-hostable wiki software packages for internal documentation
various types of self-hostable ticketing systems, monitoring systems that integrate with a customized asterisk system for NOC phone workflow
4 or 5 different tools that fill the same role as smokeping
wireshark
lots of different things for analyzing netflow data (Elastiflow or other)
ELK stack stuff, elasticsearch/logstash/kibana, customized as needed.
in house setups for openstreetmap tile servers and map presentation, to pull data from back-end mariadb databases and present them on monitoring displays.
GIS software like QGIS and a PostGIS backend
lots of different possible things done with custom code and postgresql, mysql/mariadb, or similar
if you go through the PDF slideshows for the powerpoint decks at the last 4-5 years of the NANOG, RIPE and APNIC conferences you'll see discussion of some of the most popular network automation and monitoring tools.