Making assumptions relating to power, space, and infrastructure services such as firewall/network, ACL, DNS, NTP, and so on is a common pitfall and poses challenges for ECS installation. Thus, knowledge of requirements and existing infrastructure at the customer site is important to mitigate this issue. There are documentation and tools available to help plan, prepare, and design ECS to fit your requirements and eliminate the guess work.
To review, the following components illustrated in Figure 2 form the basis of an ECS deployment:
A VDC/site is built up of one or more racks where each rack requires a tile space on the data center floor. Racks communicate across the site's Local Area Network (LAN) by means of uplink network connections through a pair of 25GbE switches for EX300, EX500, EX3000 and EXF900. These switches may be purchased with the ECS as part of the solution or may also be customer provided switches. In addition, ECS communicates privately over a closed backend for administrative tasks; no data travels over the backend network except EXF900 which use a dedicated RDMA backend network. The quantity of racks deployed at each site is primarily determined by storage and performance requirements. Floor space and plans for future growth are also considerations.
A multi-site deployment is built by federating two or more sites. ECS enables you to configure replication either within a single site or across multiple sites. This provides flexibility in solution design allowing for data separation, protection against many types of failures, and global access.
After understanding the terminology and components, there are documentation and tools that can help in the planning and deployment which include:
Regarding the ECS Designer, all hardware, software and licensing are associated with a specific and unique site ID. It is critical site information be kept up-to-date and verified for accuracy from the earliest planning stages, through the ordering process, and all the way through provisioning, alerting, and remote access. Support issues are tied to site IDs as well.
Planning documentation and tools best practices