The purpose for such a configuration is that if one
connection fails, it has an alternative route it can take. Cost metrics are then associated
with each of these lines so that the router can make intelligent decisions around which
path to use for traffic. You can configure load balancing for traffic across both lines or
configure one line as the primary that can switch over to the other line if the primary is
unavailable.
Figure 11-1 shows two networks separated by two routers that are directly connected.
The best way to understand this concept is to illustrate the process of how the packets
get from one host to another. Use Figure 11-1 to follow along.
If Client A with the IP address 192.168.10.10/24 wants to send a packet to Client B with
IP address 192.168.10.15/24, it first determines that they are both on the same network??”
namely 192.168.10.0. In this case, Client A puts the packet ???on the wire??? for Client B to pick
up. Now change that scenario a bit, and say that Client A needs to send a packet to Server A
Figure 11-1. Two networks separated by two routers that are directly connected
192.168.100.1/24
192.168.100.10/24
Server A Router B Router A
192.168.15.5/24 192.168.10.1/24
192.168.10.15/24
192.168.10.10/24
192.168.15.1/24
Client B
Client A
356 Microsoft Windows Server 2008 Administration
with the IP address 192.168.100.10/24. The server is on the network 192.
Pages:
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397