Broken Pipe errors on traffic going through load balancer

[jasbro]

We send logs from our applications to a logging server through the load balancer.  The virtual server is set up to use "Generic client first" for the internal protocol (though we've also tried "Generic streaming" without any better luck).  The traffic is a protocol specific to the logging server (LogFaces).  When we send traffic directly to the log server, all messages are received without issue.  When we direct traffic through the load balancer (only one server in the pool), we get Broken Pipe errors in primary application and we lose about 1% of the log messages.  I'm sure this isn't enough information to really diagnose anything, but maybe someone out there has an idea of what I need to look at next?  What else do I need to provide here to figure this out?

[jasbro]

If it makes a difference, we are running Brocade Virtual Traffic Manager Appliance 500 l2 v10.4.

[DeniseK]

@jasbro

Welcome to the Community!

While we still encourage the Community to assist with your post, I wanted to let you know that I have passed your questions on to our TAC Engagement Team. They will be reaching out to you shortly to gather more information regarding your configuration, so we can get you routed to the correct group.

Once your case is closed, if appropriate, we will post the resolution to this thread to help others within the Community; or, if you'd prefer, please come back and post the resolution yourself.

Please let us know if there is anything else we can do to help faciliate your case resolution.

You can find out more about the TAC Engaged Program by clicking on the link below.

Thank you!

Denise K.
Brocade Community Team
@DeniseK

TAC Engaged Program