I did add the relevance and it did register that change on the client. However, when I placed the device in the opposite state, it did not change the download limit to what I have called out in the relevance. (perhaps because the IP address is being returned as ‘multiple results’? Perhaps a conflict?)
Also, when the change was made, it removes my relevance lanquage, and entered a 0 (which is what the setting should have been at that IP state).
I was reading about the relevance statement (addresses of adapters whose (cidr string of it = wake on lan subnet cidr string) of network) which might help me, but unsure how to implement this into my dynamic property, how to write the langeage.
Ok, I think i have this, but looking for input. I run this in the API tester, and it seems to take a lot fof time to evaluate, which concerns me in the real work applications.
if exists ((addresses of adapters whose (cidr string of it = wake on lan subnet cidr string) of network) as string as version) whose (it >= “10.71.0.0” as version and it <= “10.71.255.254” as version) OR exists((addresses whose (it as string != “0.0.0.0”) of ip interfaces whose (loopback of it = false) of network) as string as version) whose (it >= “10.60.0.0” as version and it <= “10.60.255.254” as version)OR exists((addresses whose (it as string != “0.0.0.0”) of ip interfaces whose (loopback of it = false) of network) as string as version) whose (it >= “10.242.116.0” as version and it <= “10.242.116.254” as version) then “2000” else “0”
The Client Tester API will always be slowish because the agent only will periodically respond to it… I think this will be a pretty fast expression so I don’t think you need to worry too much about the speed of it from a CPU or resourcing perspective…
In the case of the dynamic setting, the agent will not switch over instantaneously… Depending on the circumstance, it might be a bit of time (measured in seconds and minutes) for the agent to double-check this setting. Setting actions run with higher priority than other actions so it should be pretty fast (but you do need to wait at least a little while… I would say 3 minutes if I had to guess on average, but you will need to try it out in your deployment to know for sure…)