Intermittent disconnections with peer
Good morning I have a small problem with my devices, and I cannot find the cause or origin. The problem is that intermittently in the Device management --> Overview, we view on each node that the peer appears as disconnected for a few seconds, and then immediately returns to the in sync state. This does not affect the operation at any time. Our equipment is an F5 virtual edition on HyperV. We have performed tests, traffic captures and reviewed configurations, without finding any errors. Best regards
BIG-IP Sync-Failover - Sync Failed
Hi, In a project we're running a device-group in Sync-Failover* mode with Manual Sync type. After a change on the Active unit trying to sync from the Active unit to the device-group, Sync Failed with the information below: Sync Summary Status Sync Failed Summary A validation error occurred while syncing to a remote device Details Sync error on 2nd-unit: Load failed from 1st-unit 01070110:3: Node address 'node' is referenced by a member of pool 'pool'. Recommended action: Review the error message and determine corrective action on the device We're totally sure that nothing had been changed manually on the 2nd node, and both nodes were in sync before the change on 1st node. The Last Sync Type field for both nodes shows Manual Full Node. I couldn't find anything on this case; is it safe to just manipulate the configuration on the 2nd node and then sync from 2nd node to the device-group? Many thanks in advance!
BIG-IP : iControl sync operation executed against non-sync'd cluster
F5 BIG-IP LTM VE v11.4.0 on ESXi I am working with a 2-node BIG-IP cluster. I am using iControl API ( .NET/C code ) to manipulate a 2-node BIG-IP cluster. All operations are directed to the floating-VIP and so arrive at the cluster's primary node. First, I update a data-group-file, next I re-cache the data-group, and finally I issue a sync command : SystemConfigSync.synchronize_to_group() I am wondering what is the expected result for a cluster that was already in a non-synchronized state before I initiated any of my iControl operations ? By "non-synchronized state" I mean that the primary node sync status is green, and the secondary node sync status is yellow "Changes Pending". The iControl sync operation returns an error with little detail, but potentially could it fail to sync because the secondary is in a more current state than the primary ?
How to get sync information with .Net API
I apologize if this question doesn't make sense or if I'm not posting in the correct location. I am a .Net developer and never even heard of F5 until I was tasked with developing a web interface for controlling our devices. From what I was told, we have a device group of two devices that are set up as a failover. I need to determine if the devices are in sync. I have the name of the device group and the names of both devices. Determine if devices are in sync: This code works, but I'm not sure it makes sense because I would expect to be connecting to the device group, not one of the devices. However, this is the only way I could find to get the sync state. This code returns iControl.ManagementDeviceGroupMemberState.MEMBER_STATE_IN_SYNC. The reason it doesn't make sense to me is because what if the device I'm connecting to is down and the other device is now the active one? In that case, I would not be able to connect, right? Interfaces m_interfaces = new Interfaces(); m_interfaces.initialize("Device1Name", 443, userName, password); dg.SyncStatus = m_interfaces.ManagementDeviceGroup.get_sync_status_overview().member_state;
Sync config in an Active/Active cluster.
Hi, I've an Active/Active cluster and for an unknown reason, I can't Sync the config. When I do a change on one of the LTM , nothing happen. I've created the "Device Group" and added the two device in, I've set it to "Manual with Full Sync". Even after a change, the device status stay "In Sync".BIGIP DNS - What configuration get replicated by Sync group
Can anyone point me at some resources that explain what is replicated among devices by configuration sync on BIG-IP DNS? It seems that things like listeners and DNS profiles aren't synced so just want to understand what is and what isn't replicated. thanks Paul
Standby shows as offline in HA pair in version 12.1.2
Hello all, I know this topic has been discussed before but for older code versions and none of the solutions worked for me and I tried pretty much all of them. I have 2 3900 series boxes in HA pair. Network failover, port lockdown set to "allow all", boxes directly connected in HA vlan, no device in between. Upgraded from 12.0.0 to 12.1.2 and in the "Overview" page on the active box it shows the standby peer as "offline". If I failover to the other box it will again show the standby peer as "offline" from the new active box. Everything looks fine from the standby box "Overview". Both failover group and trust group show full sync, HA status on both boxes shows "in sync", no issues there. I tried multiple failovers, reboots from CLI, power cycles, changing port lockdown, even tried the process of forcing the configuration reload to no avail, still the same. Does anybody experience the same behaviour? I suspect this is a bug in the 12.1.2 code version.Cluster Cross subnet
Hi, We currently have two independent clusters of F5 in separate subnets (sites) and require a method for synchronizing the configuration between them. There is a restriction on the deployment where they must be in separate subnets. The two sites run active-active. The obvious issue for this is that the gateways are separate and when we attempt to synchronize the configuration, the gateway address is clobbered, resulting in the routing breaking. We've tried a few things including: sync only; doesn't synchronize everything ip gw pool w/ sync fail-over; server split routing looking at the files manually and syncing them with external script Does anybody have advice on how they would handle this situation? Thanks.
GTM Sync and a Sync-Failover Group
I have two data centers, and each of them have two BIG-IP devices. In data center A, they are in a active/standby group running AFM. In data center B, those two are also in an active/standby group running AFM as well. These devices are in-line from the Internet to the data center at both data centers. I am also going turn on GTM on each cluster in both data centers. My question is around syncing GTM information, but not syncing AFM policies. As expected, each data center has AFM policies that are specific to that data center. So, if I do gtm_add and join the GTMs to a GTM-sync-group, will the two separate clusters keep their data center specific AFM policies? I basically need to keep the two clusters separate from each other, but still allow GTM to remain in sync. Will this work as I expect it to? I just don't want to inadvertently overwrite data center A's AFM policies with data center B's. That would be bad. Thanks!
