![]() See our KB Unitrends Agent Pairing - Force Pairing Mode ON to resolve that condition as well. If this process fails, it may also be necessary to force the agent into pairing mode. Once this is done, you may attempt to pair by selecting the asset in the UI and selecting " Inventory Sync" from the gear icon menu at the top right. Unitrends Agent Pairing - Force Pairing Mode On To remove existing by ID (node_no): cli_key_manager json_whitelist -action remove -tag key_id -value node_no To find existing by ID (node_no): cli_key_manager json_whitelist -action find -tag key_id -value node_no This command is run in the appliance command line by first logging into your appliance via SSH as the IOS Root user, or via physical or virtual console access. The ID # seen in the ID column for an agent based asset would be required as input to the command below. From the hamburger icon at the right, enable the "ID" column if not already seen. Kafka Broker Failed authentication - SSL handshake failed - Stack Overflow Kafka Broker Failed authentication - SSL handshake failed Ask Question Asked 1 year, 5 months ago Modified 1 year, 5 months ago Viewed 3k times 2 Getting SSL errors in a cluster of three Kafka servers that communicate over SSL (only). The easiest way to locate this value is to go to Configure > Protected Assets in the UI. Removing keys from the appliance requires knowing the client's node ID number. To resolve this condition requires removing the existing keys from the appliance as well, and then ensuring the client is in pairing mode. If an appliance has prior record of an agent based asset being paired, re-pairing cannot be automatically done. This typically happens when manually removing the C:\PCBP directory or it s files in the keystore subfolder. In various circumstances, a client may lose it's keyfiles and require re-pairing with an appliance. Starting with Unitrends release 10.6.6, Secure Agent Pairing features are enabled for Windows which result in secure TLS communication between agent and appliance and prevent unauthorized systems from all communication to the Unitrends Agent. See our KB Unitrends Agent Pairing - Force Pairing Mode ON to resolve that condition as well.Unitrends Agent Pairing - Clearing Appliance Pairing (SSL Handhsake Failed) ![]() From the hamburger icon at the right, enable the "ID" column if not already seen. This only seems to be a problem specifically with Infoblox (that I've found so far). NOTE: Requests to other internal TLS sites using PS 7.1.0 work just fine. ![]() Downgrading PowerShell back to 7.0.3 fixes the problem. This typically happens when manually removing the C:\PCBP directory or it s files in the keystore subfolder. Expanding the inner exception reveals the underlying problem is an SSL handshake failure. ![]() Unitrends Agent Pairing - Clearing Appliance Pairing (SSL Handhsake Failed) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |