Retrying resource allocation
On some platforms, if the system is initially unable to program specific resources because of a node running out of resources condition, the system attempts to reprogram them when resources become available. This applies to the following resources on the following platforms:
On 7220 IXR platforms:
- ARP/ND
- Including IRB subinterfaces
On 7250 IXR Gen 2c+ and 7250 IXR Gen 3 platforms:
- ARP/ND
- Including IRB subinterfaces
- L1/L2/L3 ECMP Group FECs
- Member FECs
- L1/L2/L3 non-ECMP FECs
- LIF
- NHLFEs, tunnelsNHLFE resources are retried but tunnel indexes are not.
- MPLS, IPnIP, GRE, VXLAN, UDP tunnel-type options to the same destination are not re-attempted.
- NHLFEs via the same tunnel are retried.
- NHLFEs, tunnels
- Multicast S, G
- The multicast routes are retried if programming fails.
- OIFs that exceed the system scale limit are retried when resources become available.
Configuring thresholds for system resources
To configure monitoring for system resources, use the platform resource-monitoring command to set values for the rising-threshold-log and falling-threshold-log parameters for the resource you want to monitor.
Set thresholds for disk utilization
The following example sets thresholds for resource usage for disk utilization.
--{ * candidate shared default }--[ ]--
# info with-context platform resource-monitoring
platform {
resource-monitoring {
disk {
partition {
resource percent-used {
rising-threshold-log 90
falling-threshold-log 70
}
}
}
}
}