Applies To:

Show Versions Show Versions

Supplemental Document: Release Information: F5 Application Connector 1.0.1

Original Publication Date: 07/24/2017

Application Connector Release Information

Version: Application Connector-1.0.1
Build: 52.0

Known Issues in Application Connector v1.0.x

Functional Change Fixes

None


Application Connector Fixes

ID Number Severity Solution Article(s) Description
666339 1-Blocking   Restrictions on AWS Node naming for Auto Node Discovery
664993 3-Major   Proxy Node Names with periods are not supported

 

Cumulative fix details for Application Connector v1.0.1 that are included in this release

666339 : Restrictions on AWS Node naming for Auto Node Discovery

Component: Application Connector

Symptoms:
The following restrictions apply to AWS node naming for auto discovered nodes in v1.0.0:

Auto Node discovery extracts AWS Node names from Tag[0] Key: "Name".
      a) All instances must have at least one Tag
      b) If an instance does not have a Tag[0] the proxy process will error and exit (by default all AWS nodes have one tag) But if any nodes do not have a tag - Auto Discovery cannot be enabled.
      b) Names must be unique to be published
      c) Names must be legal BIG-IP names to be published

Conditions:
This occurs when using auto discovery on the F5 Application Connector Proxy in an AWS environment.

Impact:
The proxy will crash during auto-discovery.

Fix:
In version 1.0.1 auto discovery node naming for AWS resources conforms to the following rules:

For an auto discovered node the AC Proxy:
1) searches the resource tags attached to the node and finds the first tag with a key of "name" (case insensitive) and uses the value associated with the key as the node name.
2) The node name is formed from the concatenation of the instance id with the name as - {instanceID,'-',name}
3) If the resource does not have a name tag then the instanceID is used for the name
4) Valid names are defined by the following regex - /^[a-zA-Z_][a-zA-Z0-9-._]*$/ If the name is invalid the node will not be successfully published to BIG-IP


664993 : Proxy Node Names with periods are not supported

Component: Application Connector

Symptoms:
Attempting to add a node to the F5 Application Connector Proxy where the node name contains one or more periods (".") results in an error and a failure of the node being added.

Conditions:
This occurs when adding a node to the proxy, and the node name contains a period.

Impact:
Unable to add the node.

Workaround:
Remove the period from the node name.t

Fix:
F5 Application Connector Proxy now supports "." in the Node Name field provided it is not the first character in the string and also in the instance ID field. The following regular expression is utilized to determine valid instanceID: /^[a-zA-Z0-9-_][a-zA-Z0-9-._]*$/ and valid node names are determined using the following regex - /^[a-zA-Z_][a-zA-Z0-9-._]*$/



Known Issues in Application Connector v1.0.x


Application Connector Issues

ID Number Severity Solution Article(s) Description
647180-1 2-Critical   It is possible to deploy Application Connector Service Center with iRulesLX not provisioned
664968 3-Major   Proxy environment variable proxyName does not support "." in string
653066-1 3-Major   Pool member status is Red on the standby, long failover times
651625 3-Major   Application Connector Service Center requires HTTPS on the Proxy Virtual Server
651108-1 3-Major   Only Round Robin load balancing is supported with Application Connector nodes
650368-1 3-Major   No persistence records for traffic going through Application Connector
647184 3-Major   Application Connector Service Center RPM must be installed on all devices in a device group before configuring it
647157-1 3-Major   Application Connector can be assigned to a traffic group different from the virtual servers it serves
646863 3-Major   Application Connector Proxy does not redirect HTTP to HTTPS
646859-1 3-Major   Online help missing in Application Connector Proxy
662783 4-Minor   Adding redundant nodes to a second proxy with different node name produces confusing error
662641 4-Minor   AVR does not show pool member statistics with Application Connector nodes
656795-1 4-Minor   Source address persistence does not work
649410-1 4-Minor   You can only run one instance of the Application Connector Service Center
646852-1 4-Minor   Adding a node to the Application Connector proxy causes it to re-sort while entering data
646849-1 4-Minor   If the Application Connector Proxy loses connection to the BIG-IP, the GUI does not display the configuration

 

Known Issue details for Application Connector v1.0.x

664968 : Proxy environment variable proxyName does not support "." in string

Component: Application Connector

Symptoms:
If the proxyName environment variable set on the "docker run" command on the Application Connector Proxy contains a period ("."), the Application Connector Service Center generates an error message when a connection from the Proxy is established to the Service Center.

Also if the proxyName contains any characters besides . _ - a-z A-Z or 0-9 it will not properly connect to the service center.

Conditions:
This occurs when starting a proxy using the -e proxyName=<a-string-with-a-period> parameter.

Impact:
The F5 Application Connector Service Center will reject the connection from the Proxy.

Workaround:
Avoid using a period in the proxyName environment variable.


662783 : Adding redundant nodes to a second proxy with different node name produces confusing error

Component: Application Connector

Symptoms:
When you manually add a node with an identical address or name as a node that already exists, you receive a confusing error:

01020036:3: The requested Node (/Common/mynode) was not found.

Conditions:
This occurs when adding a node to the proxy where either the node name or the node address already exists.

For example, if a proxy already has a node with this name and address:
mynode/10.1.20.11

Later if you add a node with the same name but different address:
mynode/10.1.20.12

The error will be generated

Impact:
The error actually means that the node already exists, so is confusing.


662641 : AVR does not show pool member statistics with Application Connector nodes

Component: Application Connector

Symptoms:
When looking at AVR charts, pool members served by Application Connector Service Center do not appear.

Conditions:
This occurs when AVR + Application Connector is provisioned, and you are looking at AVR statistics.

Impact:
Pool member statistics are not available, and the pool members are not displayed.


656795-1 : Source address persistence does not work

Component: Application Connector

Symptoms:
When you configure source address persistence for an Application Connector Virtual Server, persistence does not work.

Conditions:
This occurs with Application Connector on the Application Virtual Servers.

Impact:
Source address persistence does not work. The only persistence method that works in this version is Cookie Persistence, and it requires an iRule in order to work properly.


653066-1 : Pool member status is Red on the standby, long failover times

Component: Application Connector

Symptoms:
When Application Connector is deployed with health monitors, the pool members will appear Red on the standby. When the active traffic-group fails over, it can take several seconds (up to 20) for the pool members to become green.

Conditions:
This occurs when Application Connector Service Center is deployed in a HA environment. The long failover times can occur with or without health monitors.

Impact:
The Application Connector Service Center is not running on the standby traffic-group, so health checks will not be successful on the standby device until it has started and connected to the Proxies. This can cause the failover to take up to 20 seconds to complete.


651625 : Application Connector Service Center requires HTTPS on the Proxy Virtual Server

Component: Application Connector

Symptoms:
When you associate the Service Center's "Proxy Virtual Server" to a Virtual Server configured to listen on HTTP, the connection from the Application Connector Proxy to the Service Center fails.

Conditions:
The Virtual Server associated with the Proxy Virtual Server is not an HTTPS virtual server, or there is no clientssl profile.

Impact:
Connections from the proxy will fail with Error 403: Failed to establish connection to WebSocket Server

Workaround:
Make sure the Proxy Virtual Server is listening on port 443 and has a clientssl profile associated with it.


651108-1 : Only Round Robin load balancing is supported with Application Connector nodes

Component: Application Connector

Symptoms:
When you add cloud nodes provided by Application Connector to a pool using any load balancing algorithm other than Round Robin, load balancing fails and all traffic is directed to the first pool member in the list.

This may also either prevent traffic from going to the cloud nodes , or force 100% of the traffic to the cloud nodes, if the cloud pool members co-exist with local pool members in the pool.

Conditions:
Cloud nodes provided by Application Connector exist in a pool, and the pool's load balancing method is not Round Robin.

Impact:
Since cloud pool members from Application Connector have no pool member statistics, all of the statistical load balancing methods will fail because the stats will read 0. For example if the load balancing method is Least Connections, the first pool member will always have 0 connections associated with it so all traffic will go to the first pool member.

Workaround:
Always use Round Robin load balancing with cloud nodes provided by Application Connector.


650368-1 : No persistence records for traffic going through Application Connector

Component: Application Connector

Symptoms:
When you run tmsh show ltm persistence persist-records, there are no records even though cookie persistence is enabled and working.

Conditions:
This occurs if persistence is configured for the virtual server, such as Cookie Persistence, and you want to see the persistence records.

Impact:
LTM will show no persistence records, and there is no way to see persistence records from LTM. All traffic is going through an iRule and bypassing the persistence tracking in LTM.


649410-1 : You can only run one instance of the Application Connector Service Center

Component: Application Connector

Symptoms:
When you try to launch a second instance of the Application Connector Service Center, the second instance is added but it does not work. The status shows as red and when you click into it, you see the configuration of the first service center.

Conditions:
This occurs when attempting to create more than one Application Connector Service Center using the iAppsLX menu in the GUI.

Impact:
Two service centers appear in the iAppsLX menu but they both are the same service center. All additional service centers appear as red.

Workaround:
Only configure a single Application Connector Service Center per BIG-IP device.


647184 : Application Connector Service Center RPM must be installed on all devices in a device group before configuring it

Component: Application Connector

Symptoms:
After installing Application Connector Service Center on one device in a sync group, after syncing it appears to be installed on the other devices when you look at iApps :: Package Management LX, but you cannot configure it on the other devices.

Conditions:
This occurs when installing the Application Connector Service Center RPM only on one device.

Impact:
The contents of the RPM are not synced to the other devices, and any attempt to configure the Application Connector Service Center on the other devices will fail.

Workaround:
You will need to install the RPM on all of the devices in the sync group before configuring it. This only applies to the initial installation. The configuration only needs to be configured on one device and synced.


647180-1 : It is possible to deploy Application Connector Service Center with iRulesLX not provisioned

Component: Application Connector

Symptoms:
After deploying Application Connector Service center and setting up the proxy virtual server and the app virtual server(s), you notice that the virtual servers do not have the iRules associated with them.

Conditions:
This can occur if you deploy Application Connector Service Center with iRulesLX not provisioned.

Impact:
Application Connector Service Center will not function properly. You will not be able to connect a proxy to the service center without the needed iRule. You will encounter this during initial configuration so there is no impact to network traffic.

Workaround:
Make sure that iRulesLX is provisioned before installing and deploying the RPM for the service center. If you are already in this condition, uninstall the RPM via iApps :: Package Management LX, then provision iRulesLX, then re-install the RPM and proceed from there.


647157-1 : Application Connector can be assigned to a traffic group different from the virtual servers it serves

Component: Application Connector

Symptoms:
In a HA configuration, if Application Connector Service Center's virtual IP is assigned to a different traffic group than the virtual servers it is serving, an outage could occur if the virtuals are active on a different device

Conditions:
This can occur if Application Connector Service Center is configured on one traffic group, while the virtual servers it is tunneling exist on a traffic group. If the application virtusl servers are active on a device where the Service Center is in standby mode, the virtual servers will be unable to pass traffic.

Impact:
When this occurs, a traffic outage will occur.

Workaround:
When configuring Application Connector Service Center, make sure that the Proxy Virtual Server is in the same traffic group as all of the Application Virtual Servers.


646863 : Application Connector Proxy does not redirect HTTP to HTTPS

Component: Application Connector

Symptoms:
When you log into the Application Connector Proxy using a web browser, you must specify https as the protocol or the page will not load, there is no redirect.

Conditions:
Attempting to log into the Application Connector Proxy using http and not https

Impact:
Unable to load the page, in the browser it looks like the proxy is down but it is closing the connection.

Workaround:
Switch to https and the page should load as long as the proxy is running.


646859-1 : Online help missing in Application Connector Proxy

Component: Application Connector

Symptoms:
When you click the online Help button in Application Connector Proxy, there is no help content.

Conditions:
This occurs when looking at the online help.

Impact:
There is currently no online help available for Application Connector Proxy


646852-1 : Adding a node to the Application Connector proxy causes it to re-sort while entering data

Component: Application Connector

Symptoms:
While entering a new node to the Application Connector Proxy, the row you were entering data on suddenly moves to a different part of the list

Conditions:
This can occur when the column you are sorting on gets new data entered into it. Sorting is immediate and the row is moved to where it would be if the row were entered completely.

Impact:
The row you were entering data on will suddenly change. Also if the data you entered would cause the record to be sorted to the top of the list, the sort still happens and you lose input focus on the edit box.

This has no impact to traffic, you just need to click into the fields to finish inputting data for the node.


646849-1 : If the Application Connector Proxy loses connection to the BIG-IP, the GUI does not display the configuration

Component: Application Connector

Symptoms:
If an Application Connector Proxy is connected and authorized with a BIG-IP, a record will show in the "BIG-IPs" table showing that it is connected; however, if the proxy loses connection to the BIG-IP for any reason (network issue, dns issue, BIG-IP restart or reboot), the GUI will stop displaying the BIG-IP.

Conditions:
This will occur if the proxy loses connection to the BIG-IP for any reason.

Impact:
If you look at the proxy GUI it will appear that there are no BIG-IPs configured, nor any nodes, and that you need to configure everything from scratch.

Workaround:
If the BIG-IP was simply rebooting, you may be able to re-add the BIG-IP connection to the proxy, and BIG-IP will automatically re-authorize the proxy. Once this occurs, any pre-existing nodes that were configured on the proxy when the BIG-IP is reconnected.




*********************** NOTICE ***********************

For additional support resources and technical documentation, see:
******************************************************
Generated: Mon Jul 24 10:46:13 2017 PDT
Copyright F5 Networks (2017) - All Rights Reserved

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)