Our High Availability Infrastructure
Autonomous system (AS) and PI addresses
NBS System announces its addresses on its AS (Autonomous System) AS51335. Our infrastructure is a member of the DFZ (Default Free Zone) for organisations that do not have a default path as they are directly connected to the internet and participate to its interconnection. Our IP regroups thousands of addresses and one is classified as Provider Independent (IP), as well as many addresses in every country (UK, ES, CH, BE etc.)
Our architecture constantly evolves in order to adapt to the needs of our clients and the growth of our company. Here is an update of our network as of July 19th 2011.
Two Datacenters For A Very High Availability
Our two implementations are 25kms away from each other. As a result, NBS System is one of the few hosting companies who belong to the restricted club of “multihoming” able to provide very high availability. In order to minimize the Single Point of Failure (SPOF) our engineers created a redundant architecture for each level: routers (and routing), switches, load balancer and reverse proxy.
Some of our clients who are engaged in sensitive activities want to possess servers in the two datacenters or even duplicate the number of servers in order to have very high availability.
These datacenters in Saint Denis and Evry are linked to each other through private fibres. This link enables them to use the connection of the other when one of them is down and uses its servers even if the Internet connection is broken. NBS System is now able to provide high-quality Business Continuity Planning (BCP) and a very secured subnet.
External Probes To Watch Over The Whole Structure
In order to follow-up the performances of our links, we keep checking them from ADSL connections that are not hosted in our offices, and from two different Internet Service Providers (ISPs).
It allows us to check in real conditions if the links are available and efficient. We can also check if a server is out of service from the network or not. This matrix of probes gives us precise information for improving our analysis.
A Few Pictures
(The lobby, two Dell PE M1000 with 16 blades for each of them with 384 cores, the back of the chassis is very “clean”)
(Doors of the private room, inside the room with racks, two complete racks full of Dell equipments)
Our backbone Switches come from Cisco (Catalyst) and our inter-servers VLANs Swtiches from Dell, Linksys, HP or Cisco.
Our front routers are Juniper.
NBS System uses its hybridisation technology between its physical infrastructure and the one on-demand (Cloud) also called E.T.C as Extend To Cloud.
Connectivity & Transit
- Two Interlan fibres are available through the company Ielo
- The transit on Equinix PA3 is supplied by Nerim.
- The transit on Evry is supplied by Ielo.
It is important to explicate how the cost of the hosting is composed in order to understand exactly why and what you pay.
In a high-quality infrastructure, the cost of your monthly bill is made of the following:
Equipment and environment: (70%)
- Shared components to the whole infrastructure (switch, routers, mailing servers, DNS, rproxy, etc (30% monthly bill)
- Rental of your dedicated server(s) (40%)
- Bandwidth transit (to internet, 20%) and between the Datacenters (Interlan, 1%)
- Energy, air conditioner and the rental of your rooms (7%)
- Data backup (2%)
Human service: (30 %)
- Setup of the global components (switches, routers, RP, FW, etc)
- Setup of your material
- Maintenance of the shared components
- Update of your architecture (software, security, etc)
- Supervision and 24×7 live support
- Commercial follow-up
- The initial creation and the communication
History of our implementations
|Level 3||Nanterre||Implementation closed end 2008|
|Claranet||Paris VIII°||Implementation closed end 2009|
|NBS System||Haussmann||Emergency Implementation|
|Equinix PA2||Saint Denis||Implementation closed mid 2010|
|Equinix PA3||Saint Denis||Primary implementation – March 2010|
|Cogent||La Garenne Colombes||Implementation closed end september 2010|
|Iliad||Vitry||Primary implementation – July 2010|