Overview
NMIS provides specialized monitoring for Juniper Networks devices running JUNOS through Common models that collect Class of Service (CoS) and operational statistics.Available Juniper Models
The following Common-Juniper models are available inmodels-default/:
- Common-Juniper-jnxCoS.nmis - Class of Service queue statistics
- Common-Juniper-jnxOperations.nmis - Device operations (CPU, memory, temperature)
Juniper Class of Service (jnxCoS)
Overview
Monitors Juniper CoS queue statistics per interface, tracking traffic forwarding, queuing, and drops across different service classes.Model Structure
Collected jnxCoS Metrics
Queue Statistics:- Transmitted bytes (
jnxCosIfqTxedBytes) - Total bytes transmitted from queue - Queued bytes (
jnxCosIfqQedBytes) - Bytes currently in queue - Queued packets (
jnxCosIfqQedPkts) - Packets currently in queue
- Tail drop packets (
jnxCosIfqTailDropPkts) - Packets dropped due to queue overflow - RED drop packets (
jnxCosIfqTotalRedDropPkts) - Packets dropped by Random Early Detection - RED drop bytes (
jnxCosIfqTotalRedDropBytes) - Bytes dropped by RED
- Interface name - Physical or logical interface
- CoS queue name - Forwarding class (e.g., best-effort, assured-forwarding, expedited-forwarding)
- Reference name - User-defined description
RRD Collection
Understanding Juniper CoS Queues
Understanding Juniper CoS Queues
Juniper devices use forwarding classes to map traffic into queues:Default Forwarding Classes:
- best-effort - Default queue (0)
- assured-forwarding - Medium priority (1, 2, 3)
- expedited-forwarding - High priority, low latency (4)
- network-control - Control plane traffic (7)
- Strict priority
- Weighted round-robin
- Shaped/unshaped
Source/Destination Class Usage
The model also supports tracking traffic by source and destination class:Destination Class Usage
Source Class Usage
Source and Destination Class Usage sections are disabled by default and can be enabled via
model_policy.nmis.Juniper Operations Monitoring
Overview
Monitors Juniper device operational statistics including CPU, memory, temperature, and buffer utilization.Model Structure
Collected Operations Metrics
System Components:- Routing Engine
- Line cards
- Power supplies
- Fan trays
- Temperature - Celsius, per component
- CPU Load - 1 minute and 5 minute averages
- Memory - Total installed RAM in MB
- Buffer Pool - Percentage utilization
- Heap - Percentage utilization
- unknown (1)
- running (2)
- ready (3)
- reset (4)
- runningAtFullSpeed (5)
- down (6)
- standby (7)
Control Statements
The model uses control statements to filter valid data:Including Juniper Models
To enable Juniper-specific monitoring in a custom model:Example: Complete Juniper Model
Juniper models use the JUNIPER-MIB and JUNIPER-COS-MIB. Ensure your NMIS installation has these MIBs loaded for proper OID resolution.
Next Steps
- Cisco Device Models - Compare with Cisco CBQoS
- Huawei Device Models - Similar HQoS monitoring
- Creating Custom Models - Build vendor-specific models