Troubleshooting device snapshot issues
This topic includes tips for troubleshooting device low-level interaction-related issues. It explains various exceptions that the system generates when command/response interactions do not behave as expected.
Message: Device Snapshot communication failure. IOException: command failure, caused by: IllegalArgumentException: could not localize property named disc.version.
Explanation: This error occurs because the adapter cannot understand the output of the command because that version of the Device IOS is not supported in BMC Network Automation 5.2.01.
User response: BMC Network Automation version 5.2.01 or earlier is out of support. Upgrade to the latest version of BMC Network Automation. To view the support status for a release, see the BMC Network Automation Support page.
Explanation: This error occurs because the value of a property is being accessed while that property does not exist. For example, using a %myPropertyName% in a test for equality when no logic put a value into such a property generates this error.
User response: Edit the adapter logic to check that the property exists before trying to use its value.
Message: Device Snapshot communication failure. InterruptedIOException: timed out waiting for expected response [CORE-MPLS-7613-1-MRB2#] to command [dir all-filesystems]:
Explanation: This error occurs because the device sends a different prompt or response than the one that the adapter expects. The system might have received a response it does not understand, or it might have received no response at all within the timeout period (usually one minute).
User response: Edit the adapter to capture the correct prompt or response. Or increase the timeoutSeconds to allow the device enough time to run the command and generate an expected response.
Message: Device Snapshot communication failure. ChatException: chat phrase [(Timed out)] found in [ena-135085.tmp ...%Error opening tftp://172.20.6.24/ena-135085.tmp
(Timed out) CORE-MPLS-ASR1006-12OC-1#]
Explanation: This error occurs because an expected <error> has been received as a response. In other words, the system sent the device a command; the adapter logic has coded into it good responses and error responses, and the system has received one of these known errors in response.
User Response: Examine the transcript for the error message the device generated and correct the problem it identified. BMC Network Automation version 5.2.01 or earlier is out of support. Upgrade to the latest version of BMC Network Automation. To view the support status for a release, see the BMC Network Automation Support page.