Juniper Networks

Learn how to monitor Junos OS devices using the Juniper ActiveGate extension.

Getting started

To get started, just click the chat button in the upper-right corner of the Dynatrace menu bar to contact a Dynatrace ONE Product Specialist. Dynatrace ONE will make sure you have what you need to monitor Junos OS devices.

Prerequisites

  • Juniper Network devices running Junos OS, version 12.1+
  • An Environment ActiveGate that has the ActiveGate plugin module installed and isn't used for synthetic or mainframe monitoring.
    • ActiveGate version 1.175+ is ready to accept and run extensions. If you are running an earlier version of ActiveGate, see Install ActiveGate plugin module for instructions on installing the plugin module.
    • For Environment ActiveGate installation instructions, see Dynatrace ActiveGate.
    • One Environment ActiveGate can typically support 30-50 Juniper devices.

Permissions

The Junos OS user needs to have VIEW permissions for the following commands:

  • show system memory
  • show system processes brief
  • show interfaces
  • show system statistics

Extension installation

  1. Get the install file (custom.remote.python.juniper.zip) from your Dynatrace ONE Product Specialist via live chat. Don't rename the file.

  2. Unzip custom.remote.python.juniper.zip to the plugin_deployment directory of your ActiveGate host.

  3. If the resulting directory structure isn't .\plugin_deployment\custom.remote.python.juniper\, please make the necessary changes.

  4. Restart the Dynatrace Remote Plugin Module service.

    • On Linux, restart the service using the following commands with admin rights:
      systemctl restart remotepluginmodule.service  
      
    • On Windows, run these two commands in a Command Prompt launched as Admin:
      sc stop "Dynatrace Remote Plugin Module"  
      sc start "Dynatrace Remote Plugin Module"  
      
  5. In Dynatrace, selectk Settings, Add new technology monitoring, and Add ActiveGate extension.

  6. Select Upload extension and upload custom.remote.python.juniper.zip.

  7. Enter the endpoint information requested for connecting to the Juniper device:

    Setting Details
    Endpoint name Enter a meaningful endpoint name.
    Username The username for connecting to the Junos OS API.
    Password The user password.
    SSH Key File Address of SSH private key to be used instead of a password.
    Device Address The hostname/IP of the device.
    Device Port SSH port of the device.
    Device Alias Optional alias or the device name.
    Name of the group If the device is part of a cluster, enter the name here to group the devices in the GUI.
    Optional list of interfaces to ignore Allows for filtering which interfaces should not be monitored.
    • Enter a comma-separated list to ignore more than one interface
    • You can use a regex expression
    Optional list of interfaces to include Allows for filtering which interfaces should be monitored.
    Ignore interfaces that do not have an IP address Select to ignore interfaces that do not have an IP address.
    Enable debug logging Select this only if Dynatrace ONE requests it so they can investigate an issue.

Troubleshoot ActiveGate extensions

See Troubleshoot ActiveGate extensions.

Metrics

The IP address of all network interfaces and the ports used by the services are automatically captured, as are the following metrics:

Device

  • Availability
  • Wired memory used
  • Active memory used
  • CPU load

Network interface (split by interface)

  • Input bytes
  • Output bytes
  • Input errors
  • Output errors
  • Framing errors
  • Input discards
  • Input drops
  • Output collisions
  • Output drops
  • Flow input policy bytes
  • Flow output policy bytes

Network interface queue (split by interface)

  • Best effort queue - queued packets
  • Best effort queue - transmitted packets
  • Best effort queue - dropped packets
  • Expedited forwarding queue - queued packets
  • Expedited forwarding queue - transmitted packets
  • Expedited forwarding queue - dropped packets
  • Assured forwarding queue - queued packets
  • Assured forwarding queue - transmitted packets
  • Assured forwarding queue - dropped packets
  • Network control queue - queued packets
  • Network control queue - transmitted packets
  • Network control queue - dropped packets

Network protocols

  • Packets sent
  • Packets received
  • Connections requested
  • Connections closed
  • Connections accepted
  • Connections established
  • Datagrams received
  • Datagrams delivered