Once I made a template in Zabbix for Juniper MX204 and I will post some SNMP OIDs in this article.
How to take statistics of traffic and other packets from ports, see my articles:
SNMP OID and MIB for interfaces
Zabbix. Dynamic Indexes
I will describe briefly, first we look at the description of interfaces, vlan, etc.:
snmpwalk -v2c -c public ixnfo.com ifDescr
It is better to take statistics in zabbix not by snmp indexes, but by description, since indexes can change, I will give examples of SNMP data elements (we multiply the result by 8, and also indicate the type: simple change):
ifHCInOctets["index","ifDescr","lo0"]
ifHCOutOctets["index","ifDescr","lo0"]
ifHCInOctets["index","ifDescr","et-0/0/2"]
ifHCOutOctets["index","ifDescr","et-0/0/2"]
ifHCInOctets["index","ifDescr","et-0/0/2.501"]
ifHCOutOctets["index","ifDescr","et-0/0/2.501"]
It doesn’t hurt to watch for errors on interfaces:
ifInErrors["index","ifDescr","et-0/0/2"]
ifOutErrors["index","ifDescr","et-0/0/2"]
Let’s see the filling of Juniper:
1.3.6.1.4.1.2636.3.1.13.1.5 (jnxOperatingDescr)
For example, I got:
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.2.1.0.0 = STRING: "PEM 0"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.2.2.0.0 = STRING: "PEM 1"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.4.1.1.0 = STRING: "Fan Tray 0 Fan 0"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.4.1.2.0 = STRING: "Fan Tray 0 Fan 1"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.4.2.1.0 = STRING: "Fan Tray 1 Fan 0"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.4.2.2.0 = STRING: "Fan Tray 1 Fan 1"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.4.3.1.0 = STRING: "Fan Tray 2 Fan 0"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.4.3.2.0 = STRING: "Fan Tray 2 Fan 1"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.7.1.0.0 = STRING: "FPC: MPC @ 0/*/*"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.8.1.1.0 = STRING: "PIC: 4XQSFP28 PIC @ 0/0/*"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.8.1.2.0 = STRING: "PIC: 8XSFPP PIC @ 0/1/*"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.9.1.0.0 = STRING: "Routing Engine"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.12.1.0.0 = STRING: "CB 0"
Now you can find the temperature:
1.3.6.1.4.1.2636.3.1.13.1.7.2.1.0.0 (PEM 0)
1.3.6.1.4.1.2636.3.1.13.1.7.2.2.0.0 (PEM 1)
1.3.6.1.4.1.2636.3.1.13.1.7.9.1.0.0 (Routing Engine)
1.3.6.1.4.1.2636.3.1.13.1.7.12.1.0.0 (CB 0)
The last digits of the SNMP OID show where the temperature is read from.
Now let’s look at the CPU and memory usage:
1.3.6.1.4.1.2636.3.1.13.1.8.7.1.0.0 (FPC CPU)
1.3.6.1.4.1.2636.3.1.13.1.8.9.1.0.0 (RoutingEngineCPU)
1.3.6.1.4.1.2636.3.1.13.1.11.7.1.0.0 (FPC MemoryUtilization %)
1.3.6.1.4.1.2636.3.1.13.1.11.9.1.0.0 (RoutingEngineMemoryUtilization %)
1.3.6.1.4.1.2636.3.1.13.1.15.7.1.0.0 (jnxOperatingMemory.7.1.0.0)
1.3.6.1.4.1.2636.3.1.13.1.15.9.1.0.0 (jnxOperatingMemory.9.1.0.0)
1.3.6.1.4.1.2636.3.1.13.1.10 (jnxOperatingDRAMSize)
1.3.6.1.4.1.2636.3.1.13.1.11 (jnxOperatingBuffer)
Load Average (must be multiplied by 0.01):
.1.3.6.1.4.1.2636.3.1.13.1.20.9.1.0.0 (jnxOperating1MinLoadAvg.9.1.0.0)
.1.3.6.1.4.1.2636.3.1.13.1.21.9.1.0.0 (jnxOperating5MinLoadAvg.9.1.0.0)
.1.3.6.1.4.1.2636.3.1.13.1.22.9.1.0.0 (jnxOperating15MinLoadAvg.9.1.0.0)
Also, some SNMP mibs can be viewed by running commands on Juniper:
show snmp mib walk jnxOperatingEntry | match LoadAvg.9.1.0.0
show chassis routing-engine
show snmp mib walk jnxOperatingEntry | match Temp
show chassis environment
show snmp mib walk system
Subscriber counter:
1.3.6.1.4.1.2636.3.64.1.1.1.1.0 (jnxSubscriberTotalCount)
1.3.6.1.4.1.2636.3.64.1.1.1.2.0 (jnxSubscriberActiveCount)
1.3.6.1.4.1.2636.3.64.1.1.1.7.0 (jnxSubscriberAccountingTotalCount)
https://www.juniper.net/documentation/en_US/junos/topics/reference/mibs/mib-jnx-subscriber.txt
Power supply status (unknown(1),running(2),ready(3),reset(4),runningAtFullSpeed(5),down(6),standby(7)):
1.3.6.1.4.1.2636.3.1.13.1.6.2 (jnxOperatingEntry)
1.3.6.1.4.1.2636.3.1.13.1.6.2.1.0.0 (PEM0)
1.3.6.1.4.1.2636.3.1.13.1.6.2.2.0.0 (PEM1)
Similarly, we determine the status of all fans:
1.3.6.1.4.1.2636.3.1.13.1.6.4
.1.3.6.1.4.1.2636.3.60.1.2.1.1.6 (jnxDomCurrentLaneRxLaserPower)
.1.3.6.1.4.1.2636.3.60.1.2.1.1.7 (jnxDomCurrentLaneTxLaserBiasCurrent)
.1.3.6.1.4.1.2636.3.60.1.2.1.1.8 (jnxDomCurrentLaneTxLaserOutputPower)
.1.3.6.1.4.1.2636.3.60.1.2.1.1.9 (jnxDomCurrentLaneLaserTemperature)
https://oidref.com/1.3.6.1.4.1.2636.3.1.13.1.21
To monitor BGP peers, prefix statistics, etc. I used a ready-made script and template
https://github.com/Prototype-X/Zabbix-Template-Juniper-MX-BGP4-ipv4-ipv6
From this template I imported only the discovery rule for BGP, it works well on Zabbix 6.4, I also attached the script and template here.
See also my articles:
Configuring SNMP on Juniper MX
SNMP OID for Juniper QFX