- play_arrow Overview
- play_arrow Operation, Administration, and Management Features
- play_arrow Ethernet OAM and Connectivity Fault Management for Routers
- Introduction to OAM Connectivity Fault Management (CFM)
- Configure Connectivity Fault Management (CFM)
- CFM Action Profile
- Ethernet Local Management Interface
- CFM Support for CCC Encapsulated Packets
- Configure Unified ISSU for 802.1ag CFM
- CFM Monitoring between CE and PE Devices
- Configure Continuity Check Messages
- Example: Configure Ethernet CFM on Physical Interfaces
- Example: Configure Ethernet CFM on Bridge Connections
- Example: Configure Ethernet CFM over VPLS
- play_arrow Link Fault Management for Routers
- play_arrow Ethernet OAM Link Fault Management for Switches
- play_arrow Ethernet OAM Connectivity Fault Management for Switches
- play_arrow Ethernet Frame Delay
- Ethernet Frame Delay Measurements on Switches
- Configure MEP Interfaces on Switches to Support Ethernet Frame Delay Measurements (CLI Procedure)
- Configure One-Way Ethernet Frame Delay Measurements on Switches (CLI Procedure)
- Configure an Iterator Profile on a Switch (CLI Procedure)
- Trigger an Ethernet Frame Delay Measurement Session on a Switch
- Configure Two-Way Ethernet Frame Delay Measurements on Switches (CLI Procedure)
- play_arrow Ethernet Service OAM (ITU-TY.1731) for Routers
- ITU-T Y.1731 Ethernet Service OAM Overview
- Configure Ethernet Frame Delay Measurement Sessions
- Configuring MEP Interfaces to Support Ethernet Frame Delay Measurements
- Configure Ethernet Frame Loss Measurement
- Configure an Iterator Profile
- Configure Ethernet Synthetic Loss Measurements
- Ethernet Alarm Indication
- Inline Transmission Mode
-
- play_arrow Network Monitoring by using SNMP
- SNMP Architecture and SNMP MIBs Overview
- Understand SNMP Implementation in Junos OS
- Configure SNMP in Junos OS
- Configure Options on Managed Devices for Better SNMP Response Time
- Enterprise Specific Utility MIB to Enhance SNMP Coverage
- Optimize the Network Management System Configuration for the Best Results
- Interfaces to Accept SNMP Requests
- Configure SNMP for Routing Instances
- Configure SNMP Remote Operations
- SNMP Traps
- SNMP Traps Supported by Junos OS
- Trace SNMP Activity
- Access Privileges for an SNMP Group
- Configure Local Engine ID on SNMPv3
- Configure SNMPv3
- Configure SNMPv3 Authentication Type and Encryption Type
- SNMPv3 Traps
- SNMPv3 Informs
- SNMP Communities
- MIB Views
- SNMP MIBs Supported by Junos OS and Junos OS Evolved
- Junos OS SNMP FAQs
- play_arrow Remote Network Monitoring (RMON) with SNMP Alarms and Events
- play_arrow Accounting Options
- play_arrow Monitoring Options
- play_arrow Interface Alarms
- play_arrow IP Monitoring
- play_arrow sFlow Monitoring Technology
- play_arrow Adaptive Sampling for Routers and Switches
- play_arrow Packet Flow Accelerator Diagnostics Software
-
- play_arrow Monitoring Common Security Features
- play_arrow Port Mirroring
- play_arrow Port Mirroring and Analyzers
- Port Mirroring and Analyzers
- Configuring Port Mirroring and Analyzers
- Configuring Port Mirroring Instances
- Configuring Port Mirroring on Physical Interfaces
- Configuring Port Mirroring on Logical Interfaces
- Configuring Port Mirroring for Multiple Destinations
- Configuring Port Mirroring for Remote Destinations
- Configuring Port Mirroring Local and Remote Analysis
- 1:N Port Mirroring to Multiple Destinations on Switches
- Example: Configure Port Mirroring with Family any and a Firewall Filter
- Monitoring Port Mirroring
- Configure Packet Mirroring with Layer 2 Headers for Layer 3 Forwarded Traffic
- Troubleshooting Port Mirroring
-
- play_arrow System Log Messages
- play_arrow Network Management and Troubleshooting
- Compressing Troubleshooting Logs from /var/logs to Send to Juniper Networks Technical Support
- Monitoring and Troubleshooting
- Troubleshooting System Performance with Resource Monitoring Methodology
- Configuring Data Path Debugging and Trace Options
- Using MPLS to Diagnose LSPs, VPNs, and Layer 2 Circuits
- Using Packet Capture to Analyze Network Traffic
- On-Box Packet Sniffer Overview
- Troubleshooting Security Devices
- play_arrow Configuration Statements and Operational Commands
Configure Hardware Resource Threshold Monitoring for Capacity Planning
This topic describes hardware resource threshold monitoring, how to configure a resource list, associate a resource list to a monitor profile, how to configure the polling interval, and the operational mode commands to display the hardware resource utilization.
Hardware Resource Threshold Monitoring
To configure hardware resource threshold monitoring, create a resource list and specify which hardware resources to monitor or monitor all your hardware resources. You can choose several options to enhance resource lists. You can also configure a monitor profile with these optional settings that can be applied to your resource lists. You can specify a polling interval for how often hardware resource data is polled. The upper, lower thresholds, and notification type can be configured. Whenever a threshold is breached you receive notification.
Configure a Resource List
Create a resource list to monitor hardware resource utilization.
You can configure multiple resource lists, but the same resource can only be used once and cannot be duplicated on multiple resource lists.
Once configured, hardware resource utilization data is periodically polled. Default polling interval is one second.
To configure a resource list :
Configure the Polling Interval (optional)
You can optionally configure a single polling interval for the all the applicable resources.
To configure the polling interval:
[edit system
packet-forwarding-options hw-resource-monitor]
hierarchy level
and configure the polling interval: set system packet-forwarding-options hw-resource-monitor polling-interval <10-86400000 milliseconds>
Associate a Monitor Profile (optional)
You can optionally map a configured resource list with a monitor profile. A monitor-profile can be mapped to multiple resource-lists, but a single resource-list cannot be mapped to multiple monitor-profiles. A resource-list can be mapped only to a single monitor-profile. Configure a monitor profile before you map it to a resource list.
To associate a monitor profile:
Monitor Utlilization
Use the following operational mode command to display the hardware resources configured under a resource-list. The current resource utilization utilization, upper threshold, lower threshold, health, and notification type values are displayed.
show system
packet-forwarding-options hw-resource-monitor
utilization-info
Slot 0 ***** HW Resource Monitoring Information ***** Polling Interval: 1000 milliseconds (1 seconds) HW Resource Name | Max Capacity | Current Utilization | Current Utilization % | Lower Threshold % | Upper Threshold % | Health | Notification Type --------------------|--------------|---------------------|-----------------------|-------------------|-------------------|--------|------------------ ECMP-GROUP | 4096 | 0 | 0 | 50 | 90 | GREEN | Sylog ECMP-MEMBER | 32768 | 0 | 0 | 50 | 90 | GREEN | Sylog EFP | 2048 | 0 | 0 | 50 | 90 | GREEN | Sylog EGRESS-L3-INTERFACE | 16384 | 7 | 1 | 50 | 90 | GREEN | Sylog HOST-IPv4 | 147456 | 21 | 1 | 50 | 90 | GREEN | Sylog HOST-IPv6 | 73728 | 5 | 1 | 50 | 90 | GREEN | Sylog IFP | 18432 | 182 | 1 | 50 | 90 | GREEN | Sylog L3-NEXT-HOP | 65536 | 10 | 1 | 50 | 90 | GREEN | Sylog LPM-IPv4 | 24576 | 8 | 1 | 50 | 90 | GREEN | Sylog LPM-IPv6-128 | 2048 | 0 | 0 | 50 | 90 | GREEN | Sylog LPM-IPv6-64 | 12288 | 4 | 1 | 50 | 90 | GREEN | Sylog MAC | 163840 | 2 | 1 | 50 | 90 | GREEN | Sylog MPLS-INGRESS | 16384 | 0 | 0 | 50 | 90 | GREEN | Sylog MPLS-SWAP | 16384 | 0 | 0 | 50 | 90 | GREEN | Sylog TUNNEL | 4096 | 0 | 0 | 50 | 90 | GREEN | Sylog VFP | 1024 | 0 | 0 | 50 | 90 | GREEN | Sylog VPORT | 16384 | 0 | 0 | 50 | 90 | GREEN | Sylog IFP-DYN-GROUP | 6144 | 364 | 5 | 50 | 90 | GREEN | Sylog {master:0}
To view the alarms, use the show system alarms
command. To view the log messages, use the show log messages
command.
Whenever there is a change in resource health, notifications are
raised or cleared as required depending upon the notification type
(alarm
or syslog
). Green
indicates that the hardware resource utilization is safely within threshold
boundaries. Yellow
indicates that the hardware resource
utilization is above the lower threshold but within the upper threshold.
Red
indicates that the hardware resource utilization is
above the the upper threshold. When the resource health changes from
Green
to Yellow
or vice-versa, a minor
alarm is raised or cleared (as applicable). When the resource health changes
from Yellow
to Red
or vice-versa, a major
alarm is raised or cleared (applicable only if the notification type is alarm).
When the resource health changes from Green
to
Yellow
, a syslog WARNING is logged (as applicable). When
the resource health changes from Yellow
to
Red
, a syslog CRITICAL is logged (applicable only if the
notification type is syslog).
Enter the show system
packet-forwarding-options hw-resource-utilization-info
command to
display the maximum capacity and current utilization for all the applicable
resources. This command can be used to display the utilization of hardware
resources even if resource lists are not configured.
For example:
Slot 0 ***** HW Resource Maximum Capacity and Current Usage ***** HW Resource Name | Max Capacity | Current Utilization | Current Utilization % --------------------|--------------|---------------------|---------------------- ecmp-group | 4096 | 0 | 0 ecmp-member | 32768 | 0 | 0 efp | 2048 | 0 | 0 egress-l3-interface | 16384 | 7 | 1 host-ipv4 | 147456 | 21 | 1 host-ipv6 | 73728 | 5 | 1 ifp | 18432 | 182 | 1 l3-next-hop | 65536 | 10 | 1 lpm-ipv4 | 24576 | 8 | 1 lpm-ipv6-128 | 2048 | 0 | 0 lpm-ipv6-64 | 12288 | 4 | 1 mac | 163840 | 2 | 1 mpls-ingress | 16384 | 0 | 0 mpls-swap | 16384 | 0 | 0 tunnel | 4096 | 0 | 0 vfp | 1024 | 0 | 0 vport | 16384 | 0 | 0
See Also
HW Resource Monitoring: npu/memory/ sensor (JTI)
View the monitored data using operational mode commands or use Junos Telemetry interface (JTI) to send data from your device to a collector using the resource path /junos/system/linecard/npu/memory/.
Sample output:
kv { key:property[name='mem-util-host-v4-size']/state/value, uint_value:147456 } kv { key:property[name='mem-util-host-v4-allocated']/state/value, uint_value:12 } kv { key:property[name='mem-util-host-v4-utilization']/state/value, int_value:1 } kv { key:property[name='mem-util-host-v4-lower-threshold']/state/value, uint_value:50 } kv { key:property[name='mem-util-host-v4-upper-threshold']/state/value, uint_value:90 } kv { key:property[name='mem-util-host-v4-health']/state/value, uint_value:1 }
If resource lists are not configured, the threshold and health values will be "0" and not displayed in the sensor output because of zero-suppression.