![]() 1 address for tests)Įmulated Branch LAN (Use. Link between Branch and HQ\, where Branch is. Link between HQ and Provider 2, where HQ is. Link between HQ and Provider 1, where HQ is. We must achieve all of that with static routes.Ĭheck out the following table to understand the addressing plan. If that’s the case, it should automatically fall back on the second provider. Moreover, we want to add some redundancy: HQ should connect to the Internet using Provider 1 unless the link is down. ![]() Specifically, Branch must be able to communicate with the Internet and HQ LAN. We will consider that as the office network in Branch and HQ, respectively.Īs a requirement from a routing perspective, everything must be able to communicate with everything. To do that, we leverage interface Loopback 0 on both Branch and HQ routers. To speed things up, we pre-configured IP addresses on the interfaces, so that you’ll need to configure routes only.įor this lab, we are emulating two LANs: Branch LAN and HQ LAN. As a result, you will need to create new static routes on both Branch and HQ routers. However, the customer-side of the network has no routing at all. This lab comes with provider-side routing already configured. In this scenario, we want to establish communication and routing in the best way possible. The branch is connected to HQ only, but HQ has two different Internet providers connected to the Internet. For that, we have a router in the main site – HQ, and a remote route – Branch. The topology for this lab is fairly simple, yet interesting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |