Forum Discussion
Allanwynn_16283
Jan 22, 2015Nimbostratus
High Availability configsync error
install_authority_trust: Exception caught in Management::urn:iControl:Management/Trust::install_authority_trust()
Exception: Common::OperationFailed
primary_error_code : 16908289 (0x01020001)
seconda...
Kash_118367
Mar 09, 2016Nimbostratus
What code version are your F5s running on?
- Rodrigo_Mori_13Mar 10, 2016Cirrus11.6
- Kash_118367Mar 14, 2016NimbostratusI would try to re-create the self-ip for that you can follow these steps: 1. On GUI: Device Management --> Devices --> Cick on "Self" device --> Device Connectivity --> Network Failover --> Delete the unicast address (1.1.1.1 in your case). 2. Delete Self IP 1.1.1.1 from GUI: Network --> Self IP --> Select 1.1.1.1 --> Delete. 3. Re-create Self IP 1.1.1.1 fro GUI (make sure you are in "Common" partition --> Network --> Self IP --> Create 4. On GUI: Device Management --> Devices --> Cick on "Self" device --> Device Connectivity --> Network Failover --> Create the unicast address. Follow same steps on F502.
- Rodrigo_Mori_13Mar 14, 2016CirrusI am creating a step by step how I'm doing the HA to see where the error may be
- Kash_118367Mar 16, 2016NimbostratusRodrigo - is your issue been resolved?
- Rodrigo_Mori_13Mar 16, 2016CirrusGood Morning, Not yet
- Kash_118367Mar 16, 2016NimbostratusI would advise you to open up F5 ticket too.
- Rodrigo_Mori_13Mar 16, 2016CirrusGood afternoon I am posting the step as step'm doing the HA in the BIG IP 4000. At the moment, I'm doing this procedure only with the cable connected NOC network, other cables from the internal network and external station disconnected. I do not know if for these cables not be connected is giving this problem. If anyone can help me. OS Version - 11.6 Link Step by step - https://www.dropbox.com/s/ga5kf75oa3718qe/HA%20-%20F5.pdf?dl=0 My Skype - rodrigosellis1
- Kash_118367Mar 16, 2016NimbostratusRodrigo - looking at your HA self IP seems like you using management IP for HA_SYNC, right? If so, you will need management route on both F5s. If not, then you want to use different IP. Also, are you able to ping self IP from F501 to F502??
- Rodrigo_Mori_13Mar 17, 2016CirrusCurrently, only 1.4 interface is connected, which is the VLAN that will be HA. I took a picture of the appliance and ping https://www.dropbox.com/s/nwwxc45y9oie8gw/Foto-ip.pdf?dl=0
- Kash_118367Mar 18, 2016NimbostratusOkay, so you have directly connected both F5s. Also, looking at your previous pdf, one thing i noticed is you have marked your interface 1.4 as untagged" while you giving the tag value "4091". Move the interface 1.4 to Tagged on both F5s and try again.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects