Capgemini Solves Multi-Tenancy, Load Balancing and Virtual Context Problems with Thunder Series from A10 Networks
Company Size
1,000+
Region
- America
- Europe
Country
- France
- Netherlands
- United States
Product
- A10 Thunder Series
- A10 Virtual Chassis System (aVCS)
- A10 Thunder Threat Protection System (TPS)
- aGalaxy
Tech Stack
- Layer 3 Virtualization (L3V)
- Virtual Router Redundancy Protocol (VRRP)
- 64-bit Advanced Core Operating System (ACOS)
- Global Server Load Balancing (GSLB)
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Cost Savings
- Customer Satisfaction
- Productivity Improvements
Technology Category
- Application Infrastructure & Middleware - Data Exchange & Integration
- Application Infrastructure & Middleware - Database Management & Storage
- Networks & Connectivity - Network Management & Analysis Software
- Networks & Connectivity - Routers & Bridges
Applicable Functions
- Business Operation
- Facility Management
Services
- Software Design & Engineering Services
- System Integration
- Training
About The Customer
Capgemini The Netherlands is one of the world’s foremost providers of consulting, technology, outsourcing services and local professional services, operating in over 40 countries. Over 130,000 Capgemini employees help clients transform their businesses in order to improve their performance and competitive positioning. Capgemini offers integrated services that help organizations identify, build and execute programs to sharpen their competitive edge.
The Challenge
Capgemini had built out a multi-tenant data center to serve its customers. Using VLANs, Virtual Routing and Forwarding (VRF), firewall rules and application delivery controller (ADC) partitions, Capgemini ensures that each customer’s environment is secure and isolated. Capgemini had deployed Cisco ACE load balancers to load balance web, mail and other applications in the multi-tenant data center. However, the existing Cisco ACE load balancer hardware was running out of available virtual context, couldn’t be upgraded and was having issues – so another solution was needed fast.
The Solution
Verbeek considered several vendors before choosing A10 Thunder™ Series. He went with A10 because the large number of configurable Layer 3 Virtualization (L3V) partitions makes it very suitable for multi-tenancy, A10 has a positive reputation with virtual applications and he liked the price/performance. The A10 Thunder solution was deployed in two distinct topologies on Capgemini’s network. One is where a partition of the A10 Thunder solution is part of the DMZ; in the other, it is placed in the same VLAN as where the real servers are located. When it’s placed in the same VLAN as the real servers, it is only used to load balance traffic that is destined for these real servers. Connectivity to other VLANs from a real server VLAN is not allowed. Since it provides the most flexibility, deploying the A10 Thunder solution in the DMZ is the default deployment. In this scenario, a single partition is allowed to reach multiple real server VLANs. When the A10 Thunder solution is deployed in front of a web-based application, source NAT and client IP header insertion are used to transport the traffic to the real servers. This is to make sure that the return traffic passes back to the A10 Thunder solution, since the default gateway usually points to the firewall.
Operational Impact
Quantitative Benefit
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
