Forum Discussion
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 interface is accessed via say TCP port 10,717 from an iControl perspective.
When we use this port as part of the C SDK Interfaces Initialize method we get a protocol error. We assume that the SDK thinks that since port 443 is not specified it will not negotiate SSL on the connection.
Is there a way to use the SDK so that the Initialize method knows to use SSL even when a non-standard port is used?
7 Replies
This is the first time this has been requested since I wrote the first iControl .Net wrapper over 10 years ago. Hadn't thought of the use case where a user would need HTTPS over an alternate port. Right now it's hard coded to https for port 443 only. I'll look into adding an additional initialize method in the next release to allow for https over alternate ports. Unfortunately it isn't in there now...
-Joe
O2_Support_6853Thank 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
- Desai_124243
Hi 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
As far as I know, the only way to change the port that the BIG-IP management is run on is to manually configure the httpd.conf file on the BIG-IP which most likely is not a supported option.
- Desai_124243
As per below F5 link, we must have to change management port to non-standard port on Azure BIG-IP. So 443 port can use on users application
So how can we use iControl on Azure BIG-IP if non-standard port required to change?
