Maintaining Config on Load Balancers in Multiple Locations
For those that have systems in multiple locations how do you handle config synchronization? So say you have: Location1: Load Balancer1 VIP www.mydomain.com web1 web2 web3 Location2: Load Balancer 2 VIP www.mydomain.com web4 web5 web6 You can't keep the two LTMs in sync because location1 and 2 have different backend nodes unless you had multiple VIPs like: . Then one of the VIPs in each location just isn't used. That seems a little messy and error prone though? You end up with double the VIPs, if you point to the wrong VIP at the wrong location traffic either might not pass or might be very slow. If you don't do that though what's the alternative? Maintaining each load balancer as stand alone devices? So every time you need to change an irule or SSL certificate you have to do it on multiple devices? That seems like it would have issues too. Is there a better way of approaching this? Thanks Brad
How can code share external monitor scripts be used?
I work for a vendor that distributes F5 LTMs as part of a system (software and hardware). I need to solve a specific problem with the built in health monitors and so have taken an (EAV) external monitor script from the advanced design & config code share examples. I've got the problem solved using the script I have written (derived from one I took from the code share page), but the license stated in all these "code share" sample EAV scripts give me pause as to whether I can simply now distribute my derived script with our system. You can see an example of the license if you look at one of the sample EAV scripts. A snippet of the license that gives me pause for example: ...It is against the law to copy the software. No part of the software may be reproduced, transmitted, or distributed in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose without the express written permission of F5 Networks, Inc. ... Can anyone point me to a "plain text" description that might explain to me in plain text and hopefully show me my misinterpretation and tell I'm allowed to use and distribute my derived EAV script? Or will I actually need to get involved with F5 lawyers/business-people to give me legal permission from F5 to use the script? (it seems odd to have these scripts on the "code share" page with licenses that imply the scripts can't be used). I have searched, but the term "license" overwhelmingly returns topics on F5 system licenses rather than the "legal license" meaning I need. Thanks for your help!