Ineffective alias service port in HTTP or TCP Monitors

Hey nathan, thanks a lot for getting back to me. I left out a detail in my post. Currently, our f5 configuration is automated and that includes the monitor creation and assocation with pool. However, if I create a second monitor (exact replica) and manually associate it with the pools, the alias service port will function properly and override the default ports from the pool members. So this could be an issue in automation/iControl. Can you suggest some examples on monitor creation or port assocations with pools? Thanks again!