Thank you for the link David, before I set it up there is no mention in the document of enabling TLS in the secondary hub install so I assume it is just a matter of copying the .jks file to this secondary hub and adding it during the installation phase.
Also on my new primary hub, everything looks good when logged into Infrastructure Manager but in the hub log I am seeing these errors, any ideas on these please?;
Jan 20 14:31:44:896 [1604] 0 hub: Disconnecting queue route 'alarm_enrichment' after failed attempt to send heartbeat
Jan 20 14:31:45:883 [2440] 0 hub: Disconnecting queue route 'probeDiscovery' after failed attempt to send heartbeat
Jan 20 14:31:45:883 [13020] 0 hub: Disconnecting queue route 'udm_inventory' after failed attempt to send heartbeat
Jan 20 14:31:47:866 [14260] 0 hub: Disconnecting queue route 'action_manager' after failed attempt to send heartbeat
Jan 20 14:31:47:866 [14940] 0 hub: Disconnecting queue route 'legacy_alarm_manager' after failed attempt to send heartbeat
Jan 20 14:31:47:866 [4612] 0 hub: Disconnecting queue route 'event_manager' after failed attempt to send heartbeat
Jan 20 14:31:47:866 [6624] 0 hub: Disconnecting queue route 'alarm_manager' after failed attempt to send heartbeat
Jan 20 14:31:47:866 [14972] 0 hub: Disconnecting queue route 'qos_processor_qos_baseline' after failed attempt to send heartbeat
Jan 20 14:31:48:851 [11996] 0 hub: Disconnecting queue route 't_3' after failed attempt to send heartbeat
Jan 20 14:36:19:328 [10904] 0 hub: login [NimBUS] - wrong password user=administrator ip=xx.x.xx.xxx
Jan 20 14:36:19:328 [10904] 0 hub: Login: failed for administrator, ip = xx.x.xx.xxx
Jan 20 14:36:19:338 [10904] 0 hub: login [NimBUS] - wrong password user=administrator ip=xx.x.xx.xxx
Jan 20 14:36:19:339 [10904] 0 hub: Login: failed for administrator, ip = xx.x.xx.xxx
Jan 20 17:04:38:202 [10904] 0 hub: sec_bfa_locked_user: user cannot be empty
Jan 20 17:04:38:202 [10904] 0 hub: login - denied; user has too many login failures, try again in -1 seconds
Jan 20 17:04:38:202 [10904] 0 hub: Login: failed for , ip = xx.x.xx.xxx
Jan 20 17:04:38:212 [10904] 0 hub: sec_bfa_locked_user: user cannot be empty
Jan 20 17:04:38:212 [10904] 0 hub: login - denied; user has too many login failures, try again in -1 seconds
Jan 20 17:04:38:212 [10904] 0 hub: Login: failed for , ip = xx.x.xx.xxx
Jan 21 10:55:00:061 [10904] 0 hub: login [NimBUS] - wrong password user=administrator ip=xx.x.xx.xxx
Jan 21 10:55:00:062 [10904] 0 hub: Login: failed for administrator, ip = xx.x.xx.xxx
Jan 21 10:55:00:072 [10904] 0 hub: login [NimBUS] - wrong password user=administrator ip=xx.x.xx.xxx
Jan 21 10:55:00:072 [10904] 0 hub: Login: failed for administrator, ip = xx.x.xx.xxx
Original Message:
Sent: Jan 19, 2022 12:18 PM
From: David Michel
Subject: HA Probe
Check out:
Article Id: 10784
AIOps - DX Infrastructure Manager - High Availability (HA) Guide (CA UIM)
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=10784
Original Message:
Sent: Jan 19, 2022 12:13 PM
From: Kevin Nelson
Subject: HA Probe
I am planning to have a secondary hub set up with the HA probe to go with my primary hub. I could not see anything in the documentation that defines what needs to be configured on the secondary hub with HA for it to communicate to the DB with the data_engine probe.
Is it just a matter of importing the DB certificate onto the second hub?
Thank you