Why does my TCP Connect collector generate “No Connection” errors when I use an SA Agent device as the target, with a target port number greater than 1024?
Make sure you configured the target as a Cisco SAA Responder target on the Target Configuration window. If you mistakenly configured it as an IP target, and you specify a Target Port that is not well known (that is, if you specify a port number greater than 1024), IPM considers the target an IP device rather than an SA Agent device and does not enable the SA Agent Control protocol. As a result, the collector cannot connect to the target and no data is collected.
Related Questions
- Why does my TCP Connect collector generate "No Connection" errors when I use an SA Agent device as the target, with a target port number greater than 1024?
- Is the Device Management agent aware that VxWorks 6 core images exist on the target?
- Does a target device need to be a router that supports SA Agent?