Skip to content

eNMS 3.0
Compare
Choose a tag to compare
@afourmy afourmy released this 22 Oct 19:47
v3
88be366

  • Custom services

  • Existing services: the existing "default" services have been enhanced to allow variable substitution and python code execution within the payload fields of each web form. For example, this allows the ReST call service URL to iterate across each {{device.name}} as it is called on a selection of inventory devices.

  • eNMS is now configured to use a PostgreSQL database + a Hashicorp Vault to store sensitive information such as network credentials.

  • Automatic topology import from OpenNMS (REST API) or Netbox (with pynetbox).

  • Web SSH: you can now SSH to your switches/routers directly from the web UI with a web-based SSH solution. For instance, from the geographical view, you can click on a device, then click on "Connect" to open a web SSH terminal. This works even if your network is behind a jumpserver, as long as eNMS is installed on the jumpserver. Optionally, eNMS can automatically authenticate you (credentials are fetched from the Vault)

  • Event-driven automation: Services and workflows can be triggered by an external event in two ways: via a call to the REST API with the name of the service/workflow, or upon receiving a Syslog message that matches a preconfigured rule.

  • There is a dockerfile to start the application as a container, and a docker-compose file to start it with PostgreSQL database and Nginx web server.

Assets 2
Loading