About jasbro

jasbro · ‎07-18-2017

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

jasbro · ‎07-18-2017

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 · ‎06-20-2017

That makes sense. In this case it is a pool of SMTP servers in our warm-standby DR environment...so there very little traffic there (a few messages from a daily cron really). Sounds like I need to disable the passive monitoring.

jasbro · ‎06-20-2017

Two of three nodes failed in a pool overnight with messages like: Node 123.123.123.123 has failed - Timeout while establishing connection (the machine may be down, or the network congested; increasing the 'max_connect_time' on the pool's 'Connection Management' page may help) When I came in this morning, I was able to verify the ip/port was available and functioning on both nodes, but the pool still had them marked as failed. I stopped the virtual server and started it back up and the pool connected to all three nodes and has been happy for the last hour. It seems like it just didn't try to reconnect to those nodes. I'm new to Stingray load balancers, having only worked with F5 in the past. Is this normal? Do I really need to manually intervene to fix this? Am I missing some obvious config? One attached screenshot is the health monitor config (listed in the catalog as Connect, I'm not sure if that is a standard monitor or was created by my predecessor). The pool also has passive monitoring turned on. The second screen shot shows the connection management settings: Is something in those configs causing the LB to give up on my nodes after some outage and require me to manually intervene?

Re: Broken Pipe errors on traffic going through lo...

Broken Pipe errors on traffic going through load b...

Re: pool won't reconnect to failed node after it r...

pool won't reconnect to failed node after it recov...