Common Error Messages in Device-Related Operations
From Release 17.2R1 onward, Junos Space Network Management Platform provides descriptive error messages that explain the reasons for common errors in device-related operations. The error message is recorded in the job details of the corresponding job on Job Management page.
The error messages and suggested resolutions are listed in Table 1.
Error Message |
Suggested Solution |
|---|---|
Unable to establish connection with the device (Device Id: device_id). Device is down, not reachable, or unable to accept requests. |
If the device is in UP state, retry the operation. If the device is in DOWN state, wait for the device to be in UP state and retry the operation. |
Unable to establish connection with the device (Device Id: device_id) because all channels are busy. |
Retry the operation. |
Unable to establish connection with the device (Device Id: device_id). <execution message thrown from J2SSH library> |
Retry the operation. If the issue persists, download troubleshooting logs and please contact the Juniper Technical Assistance Center. |
Unable to close the channel with the device (Device Id: device_id). Channel might be closed already. |
This error can be ignored if it occurs intermittently. If the issue persists, download troubleshooting logs and please contact the Juniper Technical Assistance Center. |
Unable to apply configuration changes on the device because the device configuration is being modified by another user and is locked. Commit or rollback the pending configuration changes. |
Roll back uncommitted changes from the device. |
Unable to get configuration or apply configuration changes on the device because the device returns an unknown error. Error Message from device: <RPC error message from device> |
Retry the operation. If the issue persists, download troubleshooting logs and please contact the Juniper Technical Assistance Center. |
Unable to apply configuration changes to the device as the configuration being pushed has invalid value. This could be due to an invalid reference to a non-existent key. If the configuration is generated by Junos Space, make sure that the configuration in Junos Space is in sync with that of the device. |
If the configuration is generated by Junos Space, resynchronize the device and retry the operation. If the configuration is manually generated, review the configuration for invalid parameters and retry the operation with the corrected configuration. |