So What Are The Steps Required To Build Such A Networlk
Although we work with multiple ISPs in PNG; this article has no affiliation to any ISP in PNG. The content in this document is generic and meant to be used ONLY as a guide for building best practice WAN networks.
Consider The Following Case Study:
Scope Based On Customer Requirements
- Robust and stable using Dynamic Routing
- Use best practise security solutions
- Be able to scale and anticipate growth when new branches are added.
- WAN redundancy using two services providers (example: TPNG and Digicel).
- One service provider should be primary while the other is back up, with Automatic Failover and high availability
- All server connectivity and Internet access will be via the Hub router(s), except for specific servers sitting behind each branch, where optimal routing should be used.
- It has been deduced from the latency reports supplied by the two ISPs, the link at the branch in Lae has better response time over the TPNG transmission, while the link at Wewak has a better response over Digicel. (NOTE: currently TPNG uses satellite links in Wewak and has a latency of approximately 500 milliseconds; this is considerably higher than Digicel). Therefore, it is prudent to use TPNG as the primary link at Lae and Digicel as the back. And, Digicel as the primary supplier in Wewak and TPNG as the backup
- Proactive Network Monitoring and Manage the data network during business hours.
Figure 1: High-Level Design Overview
Figure 2: High-Level Design Traffic Flow
Figure 3: Possible Dot1Q aggregated Link at the hub
- Complete Layer 2 error report for both ISPs (BERT tests) and acceptable threshold
- Static IP allocation on the Client interface on the Digicel PPPoE links (reasons for this will be explained later in the document)
- Throughput tests should be performed by the customer end.
- Latency reports for Satellite links, fibre and radio links.
- Support contact details (this could be obvious but sometimes overlooked)
Here’s a summary of the functions that will be performed at both the hub (HQ) and each branch site for both services providers:
At the Head Office
Installation and configuration of TPNG managed equipment and associated hardware into HQ. (TPNG responsibility)
- Enabling Layer 1/2 connectivity with SW1 and SW2 switches.
- Integrating into OSPF Area 0
- Enabling iBGP peering with the core layer devices at HQ.
- Verifying that BGP route propagation is functioning as expected
At Branch Offices
- Enabling Layer 1/2 connectivity with the branch switch(es).