Design approach

Hi ,

We are planning for 100 sites connnecteing  to Central site (datacenter)

1. What is the basic Networking requirements gather at Locations

2.What requirements should at DC (with highavailbility and Loadbalacing)

Regards
Ram
LVL 1
RAMU CHAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Thomas RushCommented:
1) Your networking needs will depend on the bandwidth necessary to support your applications at a reasonable delay.   If you want, you can estimate how much bandwidth a user will require, and then multiply that by the number of users.  Networking between the sites will depend on what's needed to support both communication and replication of storage for high availability.

2) No way to know.  What applications are you running?  How much downtime can you allow for each application?  What's your budget?  What's your HW infrastructure?  What tools do you have already?

Since you have lots of questions and don't seem to know what information we need from you to answer your questions, I'll recommend that the best thing you can do for your business is hire an analyst who can ask all the right questions and put together a plan that will meet your needs.

As it stands, it's like you've asked us these questions:
1) What kind of engine should I get?
2) What kind of tires do I need?
without any information about what you'll be doing with the vehicle.  Is it supposed to be a sports car?  A commute van?  A luxury auto for ferrying around potential real estate buyers?  A long-haul truck?   It's impossible to know -- and designing a network infrastructure for a business with 100 sites is even more difficult than helping someone decide which kind of automobile or truck to buy.
0
btanExec ConsultantCommented:
will be better to explore based on example e.g. looking at some instance such as below.

on Central administration site, Primary site and Secondary site
- Distribution of actual content and network traffic throughput, latency and compression etc
- Discovery services for maintaining resource consistency
- Security policy to enforce data confidentality, integrity, strict access control in tier-ed segmentation, identity and role based administration and workflow approval and machine to machine transaction
- Alerts mechanism for information for operations esp incident handling throughout the hierarchy.
http://technet.microsoft.com/en-sg/library/gg712681.aspx

On the multi data center redundancy, also check out for the pt to pt in distributed fashion
https://blog.serverdensity.com/multi-data-center-redundancy-sysadmin-considerations/

Just to simplify that for the DC site redundancy configuration that will depends on combination option two factors such as below - level of resiliency in ascending order

1- DNS failover e.g. DNS detect and trigger failover among DC1 and DC2
DC1 (pri) <> DNS <> DC2 (sec)

2- Load balancer e.g. physical LB checks on site availability and other resource for load balancing due to apps pooling or systems resource uptime etc

DC1 (pri) <> LB <> DC2 (sec)

3- DNS + LB failover whereby DNS failover to the 2xLB which will decide the best DC to send and this give a higher resiliency level  
 
    |======   LB1 =====|
   ||                 ()              ||
DC1 (pri) <> DNS <>  DC2 (sec)
   ||                 ()              ||
    |======  LB2 ======|

e.g. preferably in different sites, or different providers front them with DNS failover then you can move clients from site to site as soon as a failure is detected.

Upon a load balancer goes down, there can be some switch over. But do note the link resiliency for heartbeat or the swing over as the weakest link is still btw the component.

In case you are interested, there is some beyond load balancer called the application delivery controller (ADC), with leaders such as F5 Networks, Citrix, A10, etc the yfailover support parameters helps to sieve out what the app and system needs to monitor...(not just snmp)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RAMU CHAuthor Commented:
Excellent
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Network Architecture

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.