Task 1
| R1#show ip interface brief Interface IP-Address OK? Method Status Protocol FastEthernet0/0 10.1.0.1 YES manual up up Serial0/1 10.0.0.5 YES NVRAM up up |
| R2#show ip interface brief Interface IP-Address OK? Method Status Protocol Ethernet0/0 10.1.0.2 YES manual up up Serial0/0 10.0.0.9 YES manual up up |
| R3#show ip interface brief Interface IP-Address OK? Method Status Protocol Ethernet0/0 10.3.3.3 YES manual up up Serial0/1 10.0.0.6 YES NVRAM up up Serial1/1 10.0.0.10 YES NVRAM up up |
Task 2
| R3(config)#ip sla monitor 1 R3(config-sla-monitor)#type echo protocol ipIcmpEcho 10.0.0.5 R3(config-sla-monitor-echo)#frequency 5 R3(config-sla-monitor-echo)#exit R3(config)#ip sla monitor 2 R3(config-sla-monitor)#type echo protocol ipIcmpEcho 10.0.0.9 R3(config-sla-monitor-echo)#frequency 5 R3(config-sla-monitor-echo)#exit R3(config)#ip sla monitor schedule 1 start-time now life forever R3(config)#ip sla monitor schedule 2 start-time now life forever |
Following this configuration, verify your implementation using the show ip sla monitor configuration command as follows:
| R3#show ip sla monitor configuration SA Agent, Infrastructure Engine-II Entry number: 1 Owner: Tag: Type of operation to perform: echo Target address: 10.0.0.5 Request size (ARR data portion): 28 Operation timeout (milliseconds): 5000 Type Of Service parameters: 0x0 Verify data: No Operation frequency (seconds): 5 Next Scheduled Start Time: Start Time already passed Group Scheduled : FALSE Life (seconds): Forever Entry Ageout (seconds): never Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): Active Threshold (milliseconds): 5000 Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Number of history Lives kept: 0 Number of history Buckets kept: 15 History Filter Type: None Enhanced History: Entry number: 2 |
Additionally, use the show ip sla monitor statistics command to view the current status (statistics) of the operation as follows:
| R3#show ip sla monitor statistics Round trip time (RTT) Index 1 Latest RTT: 1 ms Latest operation start time: *13:22:45.631 UTC Fri Mar 1 2002 Latest operation return code: OK Number of successes: 53 Number of failures: 0 Operation time to live: Forever Round trip time (RTT) Index 2 |
Task 3
| R1(config)#ip route 0.0.0.0 0.0.0.0 serial 0/1 |
| R2(config)#ip route 0.0.0.0 0.0.0.0 serial 0/1 |
Task 4
| R3(config)#track 1 rtr 1 R3(config-track)#exit R3(config)#track 2 rtr 2 R3(config-track)#exit R3(config)#ip route 0.0.0.0 0.0.0.0 10.0.0.5 track 1 R3(config)#ip route 0.0.0.0 0.0.0.0 10.0.0.9 2 track 2 |
Verify your tracking configuration using the show track command as follows:
| R3#show track Track 1 Response Time Reporter 1 state State is Up 1 change, last change 00:00:27 Latest operation return code: OK Latest RTT (millisecs) 1 Tracked by: STATIC-IP-ROUTING 0 Track 2 Response Time Reporter 2 state State is Up 1 change, last change 00:00:19 Latest operation return code: OK Latest RTT (millisecs) 1 Tracked by: STATIC-IP-ROUTING 0 |
Additionally, also verify the tracked static routes using the show ip route track-table command as follows:
| R3#show ip route track-table ip route 0.0.0.0 0.0.0.0 10.0.0.5 track 1 state is [up] ip route 0.0.0.0 0.0.0.0 10.0.0.9 2 track 2 state is [up] |
Because both routes are up, only the primary route should be installed in the RIB:
| R3#show ip route Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2 E1 – OSPF external type 1, E2 – OSPF external type 2 i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2 ia – IS-IS inter area, * – candidate default, U – per-user static route o – ODR, P – periodic downloaded static route Gateway of last resort is 10.0.0.5 to network 0.0.0.0 10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks |
To verify the dynamic redundancy, simply shut the Serial0/1 interface on R3:
| R3(config)#interface serial 0/1 R3(config-if)#shutdown R3(config-if)#end |
Following this change, R3 shows the following RIB entry for the default route:
| R3#show ip route Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2 E1 – OSPF external type 1, E2 – OSPF external type 2 i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2 ia – IS-IS inter area, * – candidate default, U – per-user static route o – ODR, P – periodic downloaded static route Gateway of last resort is 10.0.0.9 to network 0.0.0.0 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks |
Again, you can use the show ip route track-table command to validate as follows:
| R3#show ip route track-table ip route 0.0.0.0 0.0.0.0 10.0.0.5 track 1 state is [down] ip route 0.0.0.0 0.0.0.0 10.0.0.9 2 track 2 state is [up] |
Task 5
When implementing PBR, keep in mind that the same ACL can be referenced in multiple route map match statements, or even in multiple route maps as follows:
| R3(config)#access-list 100 permit ip 10.3.3.0 0.0.0.127 10.1.0.0 0.0.255.255 R3(config)#route-map ROUTE-PBR permit 10 R3(config-route-map)#match ip address 100 R3(config-route-map)#match length 100 100 R3(config-route-map)#set ip next-hop 10.0.0.5 R3(config-route-map)#exit R3(config)#route-map ROUTE-PBR permit 20 R3(config-route-map)#match ip address 100 R3(config-route-map)#match length 200 200 R3(config-route-map)#set ip next-hop 10.0.0.9 R3(config-route-map)#exit R3(config)#interface ethernet 0/0 R3(config-if)#ip policy route-map ROUTE-PBR R3(config-if)#end |
Following this configuration, verify your PBR configuration using the show route-map command as illustrated below:
| R3#show route-map route-map ROUTE-PBR, permit, sequence 10 Match clauses: ip address (access-lists): 100 length 100 100 Set clauses: ip next-hop 10.0.0.5 Policy routing matches: 0 packets, 0 bytes route-map ROUTE-PBR, permit, sequence 20 Match clauses: ip address (access-lists): 100 length 200 200 Set clauses: ip next-hop 10.0.0.9 Policy routing matches: 0 packets, 0 bytes |
For further validation, use the ping command to send traffic to the 10.1.0.0/16 subnet using 100-bye (default) pings and then 200-byte pings. Enable PBR debugging using the debug ip policy command while doing so.
Task 6
| R3(config)#access-list 101 permit tcp any any eq telnet R3(config)#route-map TELNET-POLICY permit 10 R3(config-route-map)#match ip address 101 R3(config-route-map)#set ip next-hop verify-availability 10.0.0.9 1 track 2 R3(config-route-map)#set ip next-hop verify-availability 10.0.0.5 2 track 1 R3(config-route-map)#exit R3(config)#ip local policy route-map TELNET-POLICY R3(config)#end |
Next, use the show route-map command to verify your configuration as follows:
| R3#show route-map route-map TELNET-POLICY, permit, sequence 10 Match clauses: ip address (access-lists): 101 Set clauses: ip next-hop verify-availability 10.0.0.9 1 track 2 [up] ip next-hop verify-availability 10.0.0.5 2 track 1 [up] Policy routing matches: 22 packets, 1268 bytes |
And finally, for further validation, you can enable PBR debugging via the debug ip policy command and then initiating a Telnet session from R3 to either R1 or R2 as follows:
| R3#debug ip policy Policy routing debugging is on R3# R3# R3#telnet 10.1.0.1 Trying 10.1.0.1 … *Mar 1 13:58:02.903: IP: s=10.0.0.6 (local), d=10.1.0.1, len 44, policy match *Mar 1 13:58:02.907: IP: route map TELNET-POLICY, item 10, permit *Mar 1 13:58:02.907: IP: s=10.0.0.6 (local), d=10.1.0.1 (Serial1/1), len 44, policy routed *Mar 1 13:58:02.907: IP: local to Serial1/1 10.0.0.9
|