<div>
<div class="content wysiwyg-content">
Greetings,<br />
I have been tasked to design a redundant connection point between my enterprise network and my internet provider. &nbsp;<br />
I have multiple buidlings. &nbsp;Two of them have a direct fiber line from the provider to our buildings. &nbsp;<br />
<br />
The first one has an S4 router that is our single point of contact. In addition, it has the DHCP Server, and a SonicWall Firewall IDS.<br />
<br />
The second has just the incoming cable with no connections.<br />
<br />
What I want to do is build up the second wall for &quot;Cluster&quot; operations (can't find the right word). &nbsp;If building one goes down, then building two can handle the load. &nbsp;We are also considering a second Exchange server there.<br />
<br />
I need a recommendation on how to handle &nbsp;that second point. &nbsp;I want to find a way to create the second &quot;gateway&quot;, IDS, and domain controller.<br />
<br />
The concern I have is what I don't know. &nbsp;my fear is spanning tree issues due to multiple gateways. In addition, I fear competing services, as well as other things I don 't know.<br />
<br />
How do I get started?<br />
Thanks
</div>
</div>


Greetings,
I have been tasked to design a redundant connection point between my enterprise network and my internet provider.  
I have multiple buidlings.  Two of them have a direct fiber line from the provider to our buildings.  

The first one has an S4 router that is our single point of contact. In addition, it has the DHCP Server, and a SonicWall Firewall IDS.

The second has just the incoming cable with no connections.

What I want to do is build up the second wall for "Cluster" operations (can't find the right word).  If building one goes down, then building two can handle the load.  We are also considering a second Exchange server there.

I need a recommendation on how to handle  that second point.  I want to find a way to create the second "gateway", IDS, and domain controller.

The concern I have is what I don't know.  my fear is spanning tree issues due to multiple gateways. In addition, I fear competing services, as well as other things I don 't know.

How do I get started?
Thanks

Request information on how to provide redundancy in outside internet access.

Network design and methodology, also known as network architecture, is the design of a communication network. It is a framework for the specification of a network's physical components and their functional organization and configuration, its operational principles and procedures, as well as data formats used in its operation. In telecommunication, the specification of a network architecture may also include a detailed description of products and services delivered via a communications network, as well as detailed rate and billing structures under which services are compensated.

Network Architecture

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.

Network Management

Network Operations includes asset management, help-desk supervision, security and user policies, infrastructure administration and anything else that affects the operation of your network. Discussions will include those of best practices in platforms, configurations, performance, security and accounting.