sending an email through gmail using python

Guide to Enterprise Network Planning

Enterprise Network Planning is divided into 2 parts:

  1. Data Center Planning (DC)
  2. Data/ Disaster Recovery Site Planning (DR)

Data Center Planning:

The organization’s core Network, Application, Data, Server, etc. is implemented on the DC site. The complete Enterprise Network Plan must possess Fault Tolerance, High Availability, Reliability, Scalability, and Quality of Services. An Enterprise might require a converged network with an Internet facility so it is required to send/ receive all traffic through a single FTTH line.

Requirements:

  1. 2 different ISPs to maintain Internet fault tolerance (Primary and Secondary). Recommended Primary ISP with higher bandwidth than Secondary ISP. Each ISP having primary and secondary links.
  2. 2 Identical Manageable Routers (optional if your Service provider provides you a Router that matches your specification) or at least 1 SFP port with PoE compatible, console port, Stacking possible. No. of ethernet port (4/8) estimation as per the requirement. Also, you can find more information about Hardware specifications in Device Catalogs.
  3. 2 Identical Firewalls with basic protection licensure activated. IPS/ IDS, Antimalware, Antivirus, Website filtering features.
  4. 2 Identical Manageable core Switches at least 2 SFP ports with POE/ POE+ compactible, console port, stacking possible. No. of eth port (8/24/48) estimation as per the requirement.
  5. 1 DMZ Switch to divert traffic to public servers.
  6. 2 Identical Server farm Switch must be manageable having all specifications mentioned above switch.
  7. 2 Identical Manageable Router for site-to-site and Remote access VPN configuration against DR site.

Data Recovery Site Planning

You require your data to be in a safe place even if a natural disaster takes away your Data Center. And operate enterprise applications without knowing if your DC has failed due to various reasons like, Power system failure, Server Failure, Network Failure and so on. You require a different geographical location far away from your data center. It is recommended that you choose your DR site to be different seismic plate than that of your DC site. E.g., Data Center at Kathmandu and Data Recovery Center at Hetauda.

The Network Equipment requirement is also the same for the Data Recovery Site as of the Data Center. If you have a lower budget for the DR site, you can use a single ISP, ROUTER, FIREWALL, and SWITCH. But if you are a critical customer service provider (Banks and Financial Institutions) and you require your system to be High Available you should not compromise for Fault Tolerance in DR Site too.

Additionally,

  1. 2 different NSPs to route traffic from DC via Intranet connectivity to connect to other Remote Sites. The NSP is connected to both DC and DR sites. It is best to have Identical NSPs that has its connectivity on both DC and DR sites so that it might be more helpful whenever you require other Data Connectivity in your DC site in the future.
  2. Dark core connectivity Most of the ISPs have already created FDDI Ring for you to connect your different sites within Nepal via Dark Core dedicated fiber cables. You need not to worry about installing a leased line to connect DC with DR site. SFP port of DC site is connected to SFP port of DR site which can be useful to access server in failure of Primary DC site, helps in transferring Realtime data backup to DC site and many more.

This fulfills the requirement for DC-DR planning. The network is the backbone of every organization and the device installation cost is just one time. If you require any consultation for your organization, I am grateful to help you with procurement, installation, commissioning, deployment, and documentation. Feel free to email us at: info@infogramtechnologies.com

Leave a Reply