Dual-Egress configuration instance for Policy Routing (2)

Previous Article: Dual-Egress configuration instance for Policy Routing 1)

Configure and debug Policy Routing dual-egress

 
 

  
  
R2 # sh ip policy // display the application policy
  
  
 
  
  
Interface Route map
  
  
 
  
  
Fa0/0 isp-acc
  
  
 
  
  
R2 # sh route-map isp-test // display the configured route map
  
  
 
  
  
Route-map isp-test, permit, sequence 10
  
  
 
  
  
Match clses:
  
  
 
  
  
Ip address (access-lists): 101
  
  
 
  
  
Set clses: feedom.net
  
  
 
  
  
Ip default next-hop 123.0.0.3
  
  
 
  
  
Policy routing matches: 0 packets, 0 bytes
  
  
 
  
  
Route-map isp-test, permit, sequence 20
  
  
 
  
  
Match clses:
  
  
 
  
  
Bitscn.com
  
  
 
  
  
Ip address (access-lists): 102
  
  
 
  
  
Set clses:
  
  
 
  
  
Ip default next-hop 223.0.0.3
  
  
 
  
  
Policy routing matches: 0 packets, 0 bytes
  
  
 
  
  
Route-map isp-test, permit, sequence 30 feedom.net
  
  
 
  
  
Match clses:
  
  
 
  
  
Set clses:
  
  
 
  
  
Default interface Null0
  
  
 
  
  
Policy routing matches: 0 packets, 0 bytes
 
 

 
 

  
  
R1 # traceroute // route tracking
  
  
 
  
  
Protocol [ip]: // ip traffic
  
  
 
  
  
Target IP address: 100.100.100.100 // Target location
  
  
 
  
  
Source address: 192.168.1.1 // the Source address is the first host of subnet 1.
  
  
 
  
  
Numeric display [n]: bitscn.com
  
  
 
  
  
Timeout in seconds [3]:
  
  
 
  
  
Probe count [3]:
  
  
 
  
  
Minimum Time to Live [1]:
  
  
 
  
  
Maximum Time to Live [30]:
  
  
 
  
  
Port Number [33434]:
  
  
 
  
  
Loose, Strict, Record, Timestamp, Verbose [none]:
  
  
 
  
  
Type escape sequence to abort.
  
  
 
  
  
Tracing the route to 100.100.100.100
  
  
 
  
  
1 12.0.0.2 72 msec 216 msec 276 msec
  
  
 
  
  
2 123.0.0.3 288 msec 360 msec * // ISP1 entry
  
  
 
  
  
-------------------------------------------------------------------------------
 
 

 
 

  
  
R1 # traceroute
  
  
 
  
  
Protocol [ip]:
  
  
 
  
  
Target IP address: 100.100.100.100
  
  
 
  
  
Source address: 192.168.1.2 // the Source address is the second host of subnet 1.
  
  
 
  
  
Numeric display [n]:
  
  
 
  
  
Timeout in seconds [3]:
  
  
 
  
  
Probe count [3]:
  
  
 
  
  
Minimum Time to Live [1]:
  
  
 
  
  
Maximum Time to Live [30]:
  
  
 
  
  
Port Number [33434]:
  
  
 
  
  
Loose, Strict, Record, Timestamp, Verbose [none]:
  
  
 
  
  
Type escape sequence to abort.
  
  
 
  
  
Tracing the route to 100.100.100.100
  
  
 
  
  
1 12.0.0.2 92 msec 188 msec 52 msec
  
  
 
  
  
2 123.0.0.3 416 msec 436 msec * // ISP1 entry
  
  
 
  
  
----------------------------------------------------------------------------------
 
 

 
 

  
  
R1 # traceroute
  
  
 
  
  
Protocol [ip]:
  
  
 
  
  
Target IP address: 100.100.100.100
  
  
 
  
  
Source address: 192.168.2.1 // the Source address is the first host in subnet 2.
  
  
 
  
  
Numeric display [n]:
  
  
 
  
  
Timeout in seconds [3]:
  
  
 
  
  
Probe count [3]:
  
  
 
  
  
Minimum Time to Live [1]:
  
  
 
  
  
Maximum Time to Live [30]:
  
  
 
  
  
Port Number [33434]:
  
  
 
  
  
Loose, Strict, Record, Timestamp, Verbose [none]:
  
  
 
  
  
Type escape sequence to abort.
  
  
 
  
  
Tracing the route to 100.100.100.100
  
  
 
  
  
Bitscn.com
  
  
 
  
  
1 12.0.0.2 136 msec 40 msec 144 msec
  
  
 
  
  
2 223.0.0.3 356 msec * 132 msec // ISP2 entry
  
  
 
  
  
---------------------------------------------------------
 
 

 
 

  
  
R1 # traceroute
  
  
 
  
  
Protocol [ip]:
  
  
 
  
  
Target IP address: 100.100.100.100 bitscn.com
  
  
 
  
  
Source address: 192.168.2.2 // the Source address is the second host in subnet 2.
  
  
 
  
  
Numeric display [n]:
  
  
 
  
  
Timeout in seconds [3]:
  
  
 
  
  
Probe count [3]:
  
  
 
  
  
Minimum Time to Live [1]:
  
  
 
  
  
Maximum Time to Live [30]:
  
  
 
  
  
Port Number [33434]:
  
  
 
  
  
Loose, Strict, Record, Timestamp, Verbose [none]:
  
  
 
  
  
Type escape sequence to abort.
  
  
 
  
  
Tracing the route to 100.100.100.100
  
  
 
  
  
1 12.0.0.2 28 msec 104 msec 200 msec
  
  
 
  
  
2 223.0.0.3 300 msec * 196 msec // ISP2 entry
  
  
 
  
  
-----------------------------------------------------
 
 

 

Summary of Policy Routing dual-Egress Configuration

Policy Routing dual-exit configuration experiment is introduced for everyone, through the above experiment, we can see that a sub-network 192.168.1.0/24) traffic through the previous link of the R2-R3 selected ISP1 link, subnet 2 192.168.2.0/24) traffic is selected through the next link of the R2-R3 ISP2 link. Therefore, policy routing is used to achieve source-based supplier selection and network load balancing.

1. Basic configurations of Cisco Routers
2. Dynamic Routing Protocol for routing in WINDOWS
3. The concept of routing in WINDOWS