I tested a beta version of the N2000 at strict Layer 4, advanced Layer 4, Layer 7 and finally SSL. Strict layer 4 load balancing does not take advantage of the TideRunner chipset and therefore does not do TCP termination. It allows only for a weighted hash algorithm to be used for load balancing and is used when speed is a necessity and all machines in the pool are equivalent. Sessions are passed through to the appropriate server (chosen by a weighted hash algorithm) and bound directly to that server.
Strict Layer 4 testing under the maximum load we could dish out with our Avalanche-Reflector combination showed TCP session latency of less than 1 ms, with HTTP latency climbing no higher than 25 ms under a load of 27,000 HTTP transactions per second, distributed over four back-end Web servers simulated by the WebReflector. Because the N2000 uses a half-NAT (Network Address Translation) scheme, a virtual service and its supporting back-end servers must be on different subnets. This also means that the N2000 does not support DSR (direct server return). Given the high-volume backplane, this should not be the concern it might be with lower-capacity load balancers. Throughput averages of 750 Mbps were not a problem, and the N2000 appeared limited only by our test equipment.
With advanced Layer 4 testing you can use more varied algorithms because sessions are passed through the TideRunner chip. Running the same tests with a round-robin algorithm showed no increase in TCP session latency, with HTTP latency peaking at 60 ms to 70 ms.
Rules and Routing
The N2000 lets you create content-matching rules, which can be used by any forwarding policy, meaning rules can be configured on virtually any portion of the URI as well as almost all HTTP headers.
Bob Friday, Chief AI Officer for Juniper Networks, explains how the advanced technology is transforming operations.
Contact center leaders from 8x8, Awaken Intelligence, and 360insight discuss the importance of agent experience.
AI may force enterprises to rewire parts of their data centers so they are fully optimized to run such workloads. The question is do you use Ethernet or InfiniBand?
