Non-Standard Port is not working for Icontrol & F5 Editor

There are 2 parts to this.

1) Change the port the management interface runs on on the BIG-IP 2) Change the client tools to point to the non-default port.

Are you saying you changed the value on the BIG-IP? I'm going to have to look back in the iRule Editor code to see but I believe you can specify a port number in there.

After changing port to 8443 as per Azure F5 documentation, I change port information on login prompt of F5 editor. I am getting "invalid connection" Error.

When I ran Initialize-, I am getting error with connectivity issue.

Can you post a screenshot or text dump of the specific error message that you are receiving?

Well, I ran into a similar issue. I was trying to create a HA pair (Split-brain with a NLB on top). The devices just refused to form a cluster. Upon troubleshooting, could find that the iControl was trying to reach out on 443 for certificate exchange and getting the VS certificate instead of device certificate. Any way to force the iControl handshake on non-standard port ?

The problem is that the iControl library uses https in the protocol for only 443 ports. For anything else, it defaults to http. I've been working on support for non-443 https ports in the library but haven't had time to thoroughly test it. Then we'll have to republish the iRule Editor using the new iControl.dll.

Likely won't get to this until May though. All source is on github so if anyone else want's to contribute, I'll accept the patches! B-)

-Joe

I ran into the same issue after booting an Azure instance as well. From documentation, it looks that all BIG-IP VE v12.1.0+ use the 8443 port by default. As of this post, the version on Azure is BIG-IP 13.0.0 Build 3.0.1679 Hotfix HF3. In my case when using the iControl.jar, I was seeing a

java.lang.NumberFormatException: For input string: "version="1.0""

interfaces.getSystemSystemInfo().get_version()

I was able to resolve this in two different ways:

1. Follow the "Change the Configuration utility port" section of this documentation page. The main command from the documentation that I needed to run was

   modify sys httpd ssl-port 443

   . I cannot say what other repercussions this may have for your environment. I assume if you don't have anything else running on 443, you should be fine.
2. The Interfaces buildURL() method needs to be updated to accept a 8443 port as

   https

   . A simple

   if ( 443 == m_port || 8443 == m_port ) {...}

   update and rebuild looks to suffice for my scripts. I hope to make a pull request with this update, but I am not sure how the F5 devs would prefer to see it implemented or if there are other issues that I do not see.