Junos Space SDK uses OpenNMS REST APIs to provide fault and performance management capabilities for enterprise networks. OpenNMS is a highly scalable platform that can manage thousands of devices from a single server or from a cluster of servers. It can also configure and manage network devices without direct operator intervention. OpenNMS is an open-source platform written in Java.

The main features of OpenNMS are:

  • Data Collection—Collecting, storing, and reporting of various network available data points using SNMP.
  • Discovery—Finding equipment on your network and adding it to the database.
  • Event Management—Receiving, correlating, and sending notifications, such as alarm reduction and robust notification system with escalations.
  • Service Monitoring—Tracking the status of networked equipment, including monitoring modules and determining if network-based services (such as ICMP, HTTP, or DNS) are available.

Because Junos Space implements a single sign-on authentication scheme, the user name and password credentials you use to log into Junos Space also validate your use of OpenNMS. No separate authentication is needed.

Junos Space SDK and OpenNMS APIs

Junos Space SDK provides OpenNMS API support for network monitoring. You can access a subset of the full set of OpenNMS URLs using REST or by using other northbound interface (NBI) clients. The Junos Space Main UI already provides network monitoring functionality that uses OpenNMS for nodes, alarms, acknowledgement, and similar tasks.

How to Invoke Supported OpenNMS APIs

OpenNMS is automatically configured and started for Bridged-mode JSVA instances. However, it is no longer supported for JSVA running in NAT mode.

To see which specific OpenNMS subservices have started:

service opennms -v status

For more information on OpenNMS configuration, see the OpenNMS Quick Start Guide.

Note: OpenNMS APIs can be accessed via the /api/space/opennms uri, and this is recommended. Alternatively, you can use the /opennms/rest uri to access those APIs not currently available through the /opennms/rest uri. To access this uri, use port http port 8980, instead of 8080 or 443. For example:


When calling OpenNMS APIs from within your application code, you can also use localhost or jmp-CLUSTER for <node-ip>.

Media Types

OpenNMS APIs support the following media types:

  • application/xml
  • application/json

Note: APIs having "count" are exceptions because they return plain text only.

OpenNMS REST API Documentation

For complete information about RESTful interfaces for OpenNMS, see the OpenNMS ReST page at https://wiki.opennms.org/wiki/ReST.

Mapping Space Device IDs to OpenNMS Node IDs

To facilitate integration with other (foreign) sources, OpenNMS includes a mechanism to map its own native node IDs to other source IDs, such as device IDs, from Junos Space. When an OpenNMS node is defined, it specifies its own ID, which is used as an element in other OpenNMS APIs, such as those for acknowledgements or alarms.

In addition, the node definition defines attributes that label an equivalent foreign source and foreign ID. In the case of Junos Space, the foreignSource attribute is always defined with the value space and the foreignID attribute value is set as the Space device ID. For example:

<node type="A" id="4" label="" foreignSource="space" foreignId="229388">
. . .

Use the space:foreignId syntax anywhere an OpenNMS node ID can be used.

Note: A colon separates the two Junos Space ID values. For example, if you are using the API with the example node defined above:


The id value can be the OpenNMS node ID (4) or the Space device ID (space:229388).

In addition, anywhere you use id in an OpenNMS REST API, you can alternatively use the foreign source and foreign ID separated by a colon. For example:

GET /nodes/space:<deviceID>