Forum Discussion
O2_Support_6853
Nimbostratus
NimbostratusNon-standard port for iControl Interfaces.Initialize
We would like to access BIG-IPs which have had their management interfaces translated via PAT to a new TCP port by a jump host between iControl and the BIG-IP. For example the HTTPS service on in the...
O2_Support_6853Nimbostratus
NimbostratusThank you very much for your response. We can continue to use the WSDL definition files directly but it would be great if we could shift to this type of framework in the future.
Can we speed things up by raising a support ticket?
- Since the iControl Libraries are released as source code on DevCentral, they aren't currently handled under out support framework so if you submitted a support ticket, they would likely point you to DevCentral. It was never our original intention to support client libraries as we provided the WSDL to integrate into client toolkits. But, years ago, I found there was some value to wrapping the WSDL generated proxy code into a package object and ended up passing them as open source projects on DC. I make it a goal to release new builds each time we get a major iControl update on the products, but can't guarantee fixes in between those releases. The source is always available if you want to make changes between our release cycle. -Joe
Desai_124243Hi Jeo,
is new feature released for Icontrol which can run on non-standard port instead of port 443?
We need this because Azure Big-IP requirement to change 443 port to different port for management IP. Otherwise we can't use 443 port for application.
Regards
