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-infoSlot 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 | 1 | 5 | GREEN | Alarm
ECMP-MEMBER | 32768 | 0 | 0 | 1 | 5 | GREEN | Alarm
EFP | 2048 | 0 | 0 | 1 | 5 | GREEN | Alarm
EGRESS-L3-INTERFACE | 16384 | 13 | 1 | 1 | 5 | YELLOW | Alarm
HOST-IPv4 | 147456 | 44 | 1 | 1 | 5 | YELLOW | Alarm
HOST-IPv6 | 73728 | 7 | 1 | 1 | 5 | YELLOW | Alarm
IFP | 18432 | 234 | 1 | 1 | 5 | YELLOW | Alarm
L3-NEXT-HOP | 65536 | 18 | 1 | 1 | 5 | YELLOW | Alarm
LPM-IPv4 | 24576 | 14 | 1 | 1 | 5 | YELLOW | Alarm
LPM-IPv6-128 | 2048 | 0 | 0 | 1 | 5 | GREEN | Alarm
LPM-IPv6-64 | 12288 | 5 | 1 | 1 | 5 | YELLOW | Alarm
MAC | 163840 | 44 | 1 | 1 | 5 | YELLOW | Alarm
MPLS-INGRESS | 16384 | 8 | 1 | 1 | 5 | YELLOW | Alarm
MPLS-SWAP | 16384 | 0 | 0 | 1 | 5 | GREEN | Alarm
TUNNEL | 4096 | 2 | 1 | 1 | 5 | YELLOW | Alarm
VFP | 1024 | 0 | 0 | 1 | 5 | GREEN | Alarm
VPORT | 16384 | 3 | 1 | 1 | 5 | YELLOW | Alarm
INGRESS-FLEX-COUNTER | 83968 | 249 | 1 | 1 | 5 | YELLOW | Alarm
EGRESS-FLEX-COUNTER | 32768 | 11 | 1 | 1 | 5 | YELLOW | Alarm
INGRESS-VLAN-XLATE | 16384 | 7 | 1 | 1 | 5 | YELLOW | Alarm
EGRESS-VLAN-XLATE | 8192 | 5 | 1 | 1 | 5 | YELLOW | Alarm
IFP-METER-TABLE | 6144 | 0 | 0 | 1 | 5 | GREEN | Alarm
EFP-METER-TABLE | 2048 | 0 | 0 | 1 | 5 | GREEN | Alarm
VLAN | 4096 | 8 | 1 | 1 | 5 | YELLOW | Alarm
VFI | 16384 | 5 | 1 | 1 | 5 | YELLOW | Alarm
EGR-VPLAG-GROUP | 256 | 1 | 1 | 1 | 5 | YELLOW | Alarm
EGR-VPLAG-MEMBER | 4096 | 6 | 1 | 1 | 5 | YELLOW | Alarm
L3-IPMC-IPV4 | 73728 | 1 | 1 | 1 | 5 | YELLOW | Alarm
L3-IPMC-IPV6 | 36864 | 0 | 0 | 1 | 5 | GREEN | Alarm
SOURCE-VP | 16384 | 7 | 1 | 1 | 5 | YELLOW | Alarm
EGRESS-DVP | 16384 | 7 | 1 | 1 | 5 | YELLOW | Alarm
UNDERLAY-MAC | 1024 | 2 | 1 | 1 | 5 | YELLOW | Alarm
OVERLAY-MAC | 1024 | 9 | 1 | 1 | 5 | YELLOW | Alarm
TRUNK-GROUP | 2048 | 1 | 1 | 1 | 5 | YELLOW | Alarm
TRUNK-MEMBER | 4096 | 3 | 1 | 1 | 5 | YELLOW | Alarm
L3-IIF-ATTR | 16384 | 4 | 1 | 1 | 5 | YELLOW | Alarm
MC-Group | 16384 | 8 | 1 | 1 | 5 | YELLOW | Alarm
IFP-DYN-GROUP | 2304 | 221 | 9 | 1 | 5 | RED | Alarm
IFP-VXLAN-GROUP | 6144 | 6 | 1 | 1 | 5 | YELLOW | Alarm
IFP-VXLAN-HIGIG-GROUP | 6144 | 7 | 1 | 1 | 5 | YELLOW | Alarm
{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 | 13 | 1 HOST-IPv4 | 147456 | 44 | 1 HOST-IPv6 | 73728 | 7 | 1 IFP | 18432 | 234 | 1 L3-NEXT-HOP | 65536 | 18 | 1 LPM-IPv4 | 24576 | 14 | 1 LPM-IPv6-128 | 2048 | 0 | 0 LPM-IPv6-64 | 12288 | 5 | 1 MAC | 163840 | 44 | 1 MPLS-INGRESS | 16384 | 8 | 1 MPLS-SWAP | 16384 | 0 | 0 TUNNEL | 4096 | 2 | 1 VFP | 1024 | 0 | 0 VPORT | 16384 | 3 | 1 INGRESS-FLEX-COUNTER | 83968 | 249 | 1 EGRESS-FLEX-COUNTER | 32768 | 11 | 1 INGRESS-VLAN-XLATE | 16384 | 7 | 1 EGRESS-VLAN-XLATE | 8192 | 5 | 1 IFP-METER-TABLE | 6144 | 0 | 0 EFP-METER-TABLE | 2048 | 0 | 0 VLAN | 4096 | 8 | 1 VFI | 16384 | 5 | 1 EGR-VPLAG-GROUP | 256 | 1 | 1 EGR-VPLAG-MEMBER | 4096 | 6 | 1 L3-IPMC-IPV4 | 73728 | 1 | 1 L3-IPMC-IPV6 | 36864 | 0 | 0 SOURCE-VP | 16384 | 7 | 1 EGRESS-DVP | 16384 | 7 | 1 UNDERLAY-MAC | 1024 | 2 | 1 OVERLAY-MAC | 1024 | 9 | 1 TRUNK-GROUP | 2048 | 1 | 1 TRUNK-MEMBER | 4096 | 3 | 1 L3-IIF-ATTR | 16384 | 4 | 1 MC-Group | 16384 | 8 | 1 IFP-DYN-GROUP | 2304 | 221 | 9 IFP-VXLAN-GROUP | 6144 | 6 | 1 IFP-VXLAN-HIGIG-GROUP | 6144 | 7 | 1
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.