Struggling with Node.js API for Searching Profiles Across Multiple F5 Devices
Hey everyone, I’m working on a Node.js API that connects to my frontend and allows users to search for an SSL or LTM profile by name and get back all the relevant details. The twist is that the profile could live on any one of 40+ F5 devices (different mgmt IPs). Here’s what I’ve done so far: I’m using the F5 REST API and creating a session token for each mgmt IP to avoid basic auth on every call. I built a loop to query each device, aggregate results, and return the profile details if it exists. The problem: It’s not consistent. Sometimes the profile is found; other times it’s missed—even though it’s definitely there. I’m getting timeouts pretty frequently, which adds to the frustration. Feels like I’m doing too many sequential calls and maybe hitting performance or token issues. Has anyone tackled something similar? How do you structure your calls to make them reliable across multiple devices? Is there a recommended pattern for handling large-scale F5 REST calls in Node.js (parallelization, rate limits, caching)? Should I stick to session tokens or consider another auth pattern? Any tricks for minimizing timeouts when calling multiple mgmt IPs? Any examples, best practices, or lessons learned would be hugely appreciated. At this point, I’m looking for a clean way to make this work reliably before I refactor again. Thanks
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!