external FTP monitor via explicit FTP proxy
Dear all, I have a couple of forward proxy servers load balanced behind the F5 and we are wondering how to monitor the FTP proxy services, so basically we are looking for a way to send a FTP command via an external explicit FTP proxy just like we do with http curl command for web services (see below). Does someone have a solution to monitor FTP via explicit proxy? curl -k -v ${URI} --proxy ${IP}:${PORT} --http1.1 2>&1 | grep -i "${RECV}"External monitor Realsec Cryptosec HSM
Hi all, I am trying to monitor a HSM appliance using the external monitor template provided on this link: link text I modified this part in the template so it should send CCCCNC and the response 00000000, I really am not sure if this is the correct line. I uploaded the script and attached it to the pool and it is available and actively sending monitor request towards the pool members, however looking at the payload in wireshark there is no data being send. I verify it in wireshark (Follow TCP stream). Send the request request and check the response echo -n 'CCCCNC' | nc $IP $PORT | grep "00000000" 2>&1 > /dev/null Someone over here with some bash scripting experience? Thanks in advance.
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!
External Passive FTP Health Monitor
Hi Guys, I need help In writing a scripted FTP Health Monitor, due to the Upgrade of our F5 from 11.53. to 12.1.2, there are some changes In The way a standard FTP Works, It now request a 'File Size', (The BIG-IP system requests binary mode and the file size_ ref: https://support.f5.com/csp/article/K11481312) The proxies, which have the FTP Server within, are now generating an error and cant be changed "Response sent to user keepalive: 502 Command SIZE not implemented" I need to create an EAV Health Monitor which simulate the same as before but without the FTP File size option:Help constructing a gtm monitor with a working curl statement
Hi, First, thank you in advance for any assistance with this. This is my first post to DevCentral. I should add we are running 11.5.3 HF2. I am trying to figure out how to use a gtm monitor for the following curl statement against an https URL. curl-apd -k -v --resolve webmail.corp.com:443:10.1.1.1 "https://webmail.corp.com/CookieAuth.dll?GetLogon?curl=Z2F&reason=0&formdir=1" The issue that we have is resolution for host webmail.corp.com returns an external IP, but we want to monitor the above url using an internal IP, reachable from the gtm. Thus the --resolve parameter on the curl statement. I figured once I got a working curl statement the rest would be easy but that has not been the case with this particular monitor. Cheers! Don