[ZBXNEXT-5926] Template for Juniper Networks Created: 2020 Apr 30  Updated: 2025 Feb 07  Resolved: 2025 Feb 07

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Templates (T)
Affects Version/s: 4.4.7
Fix Version/s: 7.0.10rc1

Type: Change Request Priority: Medium
Reporter: kader Assignee: Aleksandre Sebiskveradze
Resolution: Fixed Votes: 0
Labels: templates
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS 7 with Docker


Team: Team INT

 Description   

I need template for Juniper router (MX series) for MPLS LSP (Label Switched Path), I need to monitoring this lsp in my network.



 Comments   
Comment by Alex King [ 2020 Aug 06 ]

if you are trying to monitor the juniper via snmp you can/should try to create your own template via using mib2zabbix. I've used it for some switches a couple years ago and it worked well. Its worthwhile to note however that while this works well it will create specific zabbix items for oids and not use zabbix snmp style LLD to walk through snmp tables and discover all the values. This can mean depending on the model of switch you may need to add additional items for additional interfaces from one model switch to the other. https://sbcode.net/zabbix/mib-to-zabbix-template/

You could also try adding your snmp lld discovery rule as described in the official manual, it works very well as well https://www.zabbix.com/documentation/4.2/manual/discovery/low_level_discovery/snmp_oids. The benefit here is you can have one SNMP LLD per snmp Table provided by the mib tree/oid instead of a 1-to-1 for every individual oid. In practice this means for example ALL your switch/router interfaces from 1 to 54 or 52 or 100 or N get discovered.

If you haven't custom LLDs yet, you will soon likely realize how powerful LLDs are in zabbix.

Comment by Aleksandre Sebiskveradze [ 2025 Feb 07 ]

Hello, integration was created juniper_mx_snmp here.

Also you might be interested in Juniper MX Series by NETCONF 

Closing this ticket.

BR

Generated at Wed Apr 30 07:10:06 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.