Details Embedded Collector troubleshooting scenarios, including admin state changes in single-VM deployments and Kafka connection failures for unsecured external destinations, with guidance for diagnosing blocked ports and restoring connectivity.
The troubleshooting section contains information about the possible issues and corrective actions that you may observe with Embedded Collectors.
Troubleshooting the admin state change from DOWN to UP
In a single VM deployment, devices are automatically attached to Embedded Collectors, which causes their Admin State to change from DOWN to UP.
Workaround: If you need to change the Admin State to DOWN, manually update it using the Edit Device page. For detailed steps on editing a device, see the Edit Devices section in the Cisco Crosswork Network Controller 7.2.x Device Lifecycle Management guide.
Kafka connection failure for unsecured external destinations
If a collection job is submitted to an external (unsecured) Kafka destination, the dispatch job may fail to connect to the Kafka server.
Collector error:
org.apache.kafka.common.errors.TimeoutException: Topic cli-job-kafka-unsecure not present in metadata after 60000 ms.
Kafka error:
SSL authentication error "[2021-01-08 22:17:03,049] INFO [SocketServer brokerId=0] Failed authentication with /80.80.80.108 (SSL handshake failed) (org.apache.kafka.common.network.Selector).
These errors appear when the required port on the external Kafka VM is blocked, preventing the collector from connecting.
Workaround:
On the Kafka Docker host or server, run this command to verify whether the Kafka port is listening:
netstat -tulpn-
Unblock or correct the port configuration on the Kafka server. After fixing the issue, restart the Kafka server process to restore connectivity.