This article describes a potential problem with Juniper Apstra where users may experience deployment failures if they have SSH rate-limiting configured on a device running Junos OS that is managed by Juniper Apstra.

Configuring rate-limiting on the Junos SSH service can cause deployment failures and check job failures.

Example:

services {
    ssh {
        root-login allow;
        rate-limit 10;
    }
    netconf {
        ssh;
    }
}

In AOS, Agent "check" jobs will sometimes or always fail:

Blueprint commits can also fail if they include a configuration change to the device.

1. Increase or remove the rate-limit timer.

Example: set system services ssh rate-limit 100

2. Re-run a check job.

3. Proceed to resolve any deploy failure.