Backend nodes goes unreachable from active F5
Hi Team , We are facing node reachability issue from Active f5 on evryweeknd (sunday ) but this happens only from the Active F5 and for few VIP/pools only .. We simply failover the f5 to standby and issue resolves and then failback to standby .. Has anyone faced such issue ? We have virtual appliance configured on the ESXi host . Before opening a TAC case , Can anyone confirm if you have faced similar problem ? I did not find anything on the audit logs which indicates some sceduled jobs running at tht time ..What else can be checked ?
Adding Viprion Blade Management Address in Production
Hi every one. I have 2 Viprion with 2 blade cluster identic on each viprion. i have situation were when i create a new vcmp guest on Viprion02 and assign an ip address, that ip address is unreachable from the network (all other vcmp guest is reachable). When i checked on the bash linux for the mgmt address, there is no ip address were on the system-platform i can see the same ip address for the management. But this issue is not happen on Viprion01. I take a look for the viprion02 cluster blade. Only cluster IP is configured and No blade management ip is configured. Not like in Viprion01, All blade have its own management IP. I would like to add management ip address on Viprion02 blade. 1. Will there is an impact on the production? I have tried read about the viprion and assume it should not give any impact due to management ip is distinct with management blackplane were used for blade inter communication, traffic handling, and sync. 2. Which HA is that doc talking about? Blade HA is active active right? And Guest HA using its own management IP, not the blade management address. Thank You
BIG-IP : configure 2-node pool as simple failover
F5 BIG-IP Virtual Edition v11.4.1 (Build 635.0) LTM on ESXi I have a RESTful service deployed on two servers (with no other sites/services). I've configured BIG-IP as follows : single vip dedicated to service single pool dedicated to service two nodes , one for each server one health monitor which determines health of each node I need to configure this cluster as simple failover where traffic is sent only to primary. So, if node 1 is primary and it fails health monitor, node 2 is promoted to primary and handles all traffic. How to configure BIG-IP ?
BIG-IP : sync-failover device-group sync options
F5 BIG-IP Virtual Edition v11.4.1 (Build 635.0) LTM on ESXi For a device-group of type sync-failover, the admin browser provides these options : Automatic Sync Full Sync Maximum Incremental Sync Size (KB) Could someone please explain these options ? Are syncs on a time-schedule ? Or are syncs triggered by any change to the primary ? Or exactly what types of changes will trigger a sync ? Specifically, will a change to a data-group file ( e.g. add/delete a line ) trigger a sync ?
BIG-IP active-standby configurations failed
We are working on a new proyect about F5 Big IP Link Controler. For this implementation We did the steps-by-step installation describes in the follow document: http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-implementations-11-4-0/2.html Well everything it was fine until the Discovery Peer process; The problem was that the second device not discovered the first device and finally the two devices haven't a trust relationship and the Big IP appliances do not works as an active-standby pair. The messages error is: [CheckHandlers.cpp:83 checkDevic] System time on 192.168.50.100 off by -1800 seconds Hello, We configure an NTP server on both device. Also we used Setup utility to configure the new devices as an active-standby pair on several times. For this step we follow this article –> https://support.f5.com/kb/en-us/solutions/public/10000/200/sol10240.html Besides, We check out the Time zone and Clock on both appliances and everything looks fine. By the way We are on time zone America/Caracas (UTC -4:30). Thanks in advance
iRules LX config sync in cluster with workspaces, how?
Hi all, A customer of us is using with success the iRules LX and he likes it very much to do some REST-API security. Now he has a iRules LX workspace which is located in the path /var/ilx/workspaces. He is using a Big-IP cluster and is doing a config sync to the standby node. Unfortunately the iRules LX workspaces are not synced to the other machine... BigIP Version is v12.1.1. Since I couldn't find any information about iRules LX and clustering I ask it here: How should we proceed when the active cluster member is down and the created iRules LX? Many thanks for an answer. PeterViprion 2400 B2250 run two clusters?
Hello, I have redundant 2400 chassis with a single B2250 blade in each. vCMP guests are configured sync failover between chassis, There is no HA at the Viprion Level. I need to setup two blades for a DR Bubble environment needs to be isolated from the existing blade in the default cluster and the vlans cannot mix between the blades. Is it advisable to run a second cluster for the slot 2 and 3 blades to segment the networks? I dont see much documentation on this so any help is appreciated.
Config sync for ASM module not impacting other modules
Hello experts, Need an advice how to properly sync ASM policy/configuration between different devices. I have an environment with a sync-failover cluster consisting of 2 F5 devices in each data centre so in total - 4 devices. Each cluster runs APM, LTM and ASM. What I want is to configure sync only between clusters for ASM module not impacting other modules. So if I make ASM change on a cluster in 1st DC the change is synced to 2nd DC cluster. All other changes for LTM/APM are synced between devices in the particular DC cluster only - not propagated between clusters in different DCs. Would this be possible? Is there any guide / KB to implement this? Thanks, Roman