Re: F5 Load Balancer Configuration for Cloud Foundry Loggregator

Rohit Kumar

Does `cf logs --recent` work for you? The recent logs request goes over
HTTP. If that goes through that means only the websocket requests to
loggregator servers are a problem.


On Tue, Sep 22, 2015 at 8:18 PM, Anthony <lee.apc(a)> wrote:

Thanks Mike! Unfortunately, upgrading is not an option since its a really
loaded enterprise device. The interesting part is that there is a
similarly set up websockets vip (plain old server i think .net) that is
working on the same device.

We'll work with our network folks to find other devices with newer
software we can use.

Would appreciate if anyone has other ideas?


On Sep 22, 2015, at 7:49 PM, Mike Youngstrom <youngm(a)> wrote:

We are running 11.4 and 11.6. I'd give an upgrade a try before digging
too much deeper.

On Sep 22, 2015 6:36 PM, "Anthony" <lee.apc(a)> wrote:

The version we are testing in is 10.4.


On Sep 22, 2015, at 6:41 PM, Mike Youngstrom <youngm(a)> wrote:

What version of F5 software are you running?


On Tue, Sep 22, 2015 at 5:20 PM, Anthony Lee <lee.apc(a)> wrote:

Does any one have any experience configuring F5 load balancers in front
of the CF routers? We have configured F5 and app https and cf push requests
are working fine. However, the connectivity with loggregator is not
working. Taking a look at the documentation, it requires "websocket
support" on the load balancer. We've done the configuration specified here:

With the following irule basically, applying the default TCP profile if
it detects websocket traffic:

if { [string tolower [HTTP::header Upgrade]] contains "websocket" }{

However, we are running into errors. Doing `cf logs myapp1` yields:

Error dialing loggregator server: read tcp <ip redacted>:443: connection
reset by peer.
Please ask your Cloud Foundry Operator to check the platform
configuration (loggregator endpoint is wss://loggregator.<sys domain

Does anyone have a clue?


Join to automatically receive all group messages.