Monitoring Performance Statistics Derived from MIB Objects
Junos Space Release 13.1P1 enables you to collect and display performance data derived from MIB objects. The instructions for deriving the MIB data are contained in a Stylesheet Language Alternative Syntax (SLAX) script. The Network Activate application automatically edits a predefined SLAX script to detect policies that are specific to different point-to-point pseudowire or VPLS services.
To configure Junos Space to monitor service performance based on an SLAX script, you perform tasks in both the Network Management Platform application and Network Activate application.
Before you can view performance statistics collected according to SLAX scripts, you must complete some preparatory tasks. On the server on which you are running the Junos Space software, modify files in the existing directories as described in the following list:
In the directory /home/admin/opennmspatch, copy the file collectd-configuration.xml and replace the existing version of the file in the directory /opt/opennms/etc/.
In the directory /home/admin/opennmspatch, copy the file datacollection-config.xml and replace the existing version of the file in the directory /opt/opennms/etc/.
In the directory /home/admin/opennmspatch, copy the file JNX-Util.xml and add it to the directory /opt/opennms/etc/datacollection/.
In the directory /home/admin/opennmspatch, copy the file jnxutil-graph.properties and replace the existing version of the file in the directory /opt/opennms/etc/snmp-graph.properties.d/.
In the directory /home/admin/opennmspatch, copy the file eventconf.xml and replace the existing version of the file in the directory /opt/opennms/etc/.
In the directory /home/admin/opennmspatch, copy the file JNX-Util-TCA.xml and add it to the directory /opt/opennms/etc/events/JuniperEvents/.
In the directory /home/admin/opennmspatch, copy the file threshd-configuration.xml and replace the existing version of the file in the directory /opt/opennms/etc/.
In the directory /home/admin/opennmspatch, copy the file thresholds.xml and replace the existing version of the file in the directory /opt/opennms/etc/.
To collect performance data based on an SLAX script:
- In the Network Management Platform task pane, select Images and Scripts > Scripts.
- In the Scripts window, click the Import Script icon in the command bar.
- In the Import Script window, click the + button.
- In the Add Device Scripts window, browse your
local file system for the SLAX script PM.slax.
Note If you access the server on which the Junos Space software is installed as a remote client, you must copy the PM.slax script from the directory /home/admin/opennmspatch/ to your local client file system. That is, when you click on Browse to select the PM.slax script, which you want to import, Junos Space opens the local client file system, not the file system of the server on which Junos Space is installed.
- When the script is added successfully, in the Scripts window, right-click the script and select Stage Scripts on Devices.
- In the Stage Scripts on Devices window, select the device on which you want the script to manage the collection of performance data.
- Click the Enable Scripts on Device check box.
- When you complete staging scripts, in the Network Management Platform task pane, select Administration.
- In the Administration window, right-click Network Activate and select Modify Application Settings.
- In the Modify Application Settings panel, select Performance Monitoring.
In the Performance Monitoring window, the Enable performance monitoring through scripts check box should be enabled.
Note By default, the Enable performance monitoring through scripts check box is disabled.
When the check box is enabled, the performance data is collected according to the SLAX scripts. If the check box is disabled, the performance data is collected according to the Y.1731 OAM method.
After you configure Junos Space to collect performance data according to SLAX scripts:
- In the Network Activate application, create a point-to-point or VPLS service on which you attach a CFM profile.
- Perform a Functional Audit on the service.
- After the Functional Audit completes successfully, select PM statistics > Start.
At this point, the system checks to determine whether the statistics will be collected according to scripts or by the Y.1731 OAM method.
If data collection by script is enabled, the system pushes a policy to the device upon which the performance will be monitored. The script runs every 5 minutes to collect data from updated MIB objects. To see graphs for the collected performance data, to see graphs select Network Management Platform > Network Monitoring > Reports and select the node.
If data collection by script is disabled, to see graphs for the collected performance data, see Viewing Performance Management Statistics.