Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to specify destination port in New-HealthMonitor #149

Open
davidroberts63 opened this issue Dec 20, 2017 · 2 comments
Open

Ability to specify destination port in New-HealthMonitor #149

davidroberts63 opened this issue Dec 20, 2017 · 2 comments

Comments

@davidroberts63
Copy link

I'm not seeing a way to specify the destination port (in the UI the 'Alias Service Port') in the New-HealthMonitor function.

Or is there a way to update the health monitor with that information?

@joel74
Copy link
Owner

joel74 commented Jan 30, 2018

Sorry for the slow reply on this. I believe we'd need to add 'destination' as a param for the New-HealthMonitor function. If we're going to make that change, though, I believe there are other params that should be added as well presumably any param mentioned in https://devcentral.f5.com/Wiki/iControlREST.APIRef_tm_ltm_monitor_tcp.ashx that is included in the supported versions of the PS module (11.5.1 HF8 - 13.1+) I need to figure out what that set of params is and then I can make some progress on this.

@joel74
Copy link
Owner

joel74 commented Feb 4, 2018

The differences in the iControlREST API between pre-v12 and v12 are substantial, and I'm not sure how to make changes that would accommodate both. v12 introduces 20+ types of monitors that one could create and modify. I think I'd need to split/fork the module and have one version continue to support 11.5/11.6 and have another version support 12+.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants