Forum Discussion
Radius External Monitor (Python)
This is not a non-starter, I got the script up and running as a working monitor. Using the environment variables turns out to be the cleanest way to hand information into the script at run time however I have added the ability to override the environment variables when running from the command line.
- The monitor execution is working, the shebang is fine.
- When the script runs there is super handy environment variable, MON_INST_LOG_NAME, that the F5 supplies at run time that contains the log file for the host and monitor and is the same log file that is used if you enable the Monitor Logging on the pool member.
- I have added two debugging levels that allow for the dumping the environment variables and command line arguments.
- I couldn't figure out why I couldn't write to the ltm log, but with the above log file I felt that it was better suited for debugging so I discarded the want to write to the ltm log file.
The remaining issue with the monitor is that when run as a monitor, valid credentials with a current dynamic token value results in a failed auth while the exact same credentials via command line while the token is still valid results in a successful auth.
This happens whether one uses the Environment Variable or the Arguments field in the monitor. Either way the response is a valid radius response so it marks the pool members up as it should.
I feel that this problem is outside of the scope of this question and is likely due to some idiosyncrasy with the monitor variables/arguments so I'll close this query off, but if you have any comments or solutions feel free to post.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com