How to use migration tool from Radware AppDirector to BIG-IP LTM
Hi everyone!! Please show me how to perform Radware AppDirector to BIG-IP LTM migration tool. I'm going to migrate configuration from Radware AppDirector device to BIG-IP LTM device. I read below DevCentral article and performed migration tool. But no configu setting was migrated. https://devcentral.f5.com/wiki/advdesignconfig.radware.ashx I performed downloading config file on AppDirector device and got a config file below. download configuration file format is like --> ------------------------------------------------------------------------- Format: ASCII-1.0 Date: DD-MM-2016 HH:MM:SS System: AppDirector with Cookie Persistency Software Version: 1.02.04 Base Mac Address: xx:xx:xx:xx:xx:xx Set //1 { rsIpAdEntIfIndex.192.168.1.1 = 17 ------------------------------------------------------------------------- (<-- omitting after setting) Operation on AppDirector device was File -> Configuration Recieve from Device Type is ASCII Isn't it correct format? Radware AppDirector v1.02 BIG-IP LTM v11.4.1481Views0likes1CommentF5 equivalent of Alteon's buddy helthchecks
Hi all, I'm in the process of migrating old Radware Alteon load balancers onto F5 kit. On the Alteons they have what's known as a "buddy health check". Basically what it does is monitor a second node, and if that goes down then the first node is marked as down too. For example, Server A is configured to have Server B as its buddy. If the health check for Server B fails, the load balancer will mark Server A as down. I'm aware this could be done using Priority Group Activation, however in this case Server A is being health checked on port 3000 whilst Server B is health checked on port 3001. Data for both is on port 7021. Is this setup achievable on an F5? Thanks!451Views0likes1Comment