Quantcast
Channel: IEOC - INE's Online Community
Viewing all articles
Browse latest Browse all 10744

Reliable Static Routing with Enhanced Object Tracking

$
0
0

Hello everyone,

I am just starting to go thought the new v5 lab book and I noticed some of my output is not the same as the verification tasks / screens in the workbook.  I am not sure how important it is to make sure my output matches 100%.  The reason I ask is that in the Reliable Static Routing with Enhanced Object Tracking verfication section is that when I do a traceroute I don't get all the results I expected?

I know it little thing but I thought I would share:

Under the section in which you shutdown the port gi1.146 on R1 so the route changes to go via R5 then to R1 - As shown below

R4#traceroute 150.1.1.1 source 150.1.4.4

 

Type escape sequence to abort.

Tracing the route to 150.1.1.1

 

  1 155.1.0.5 28 msec 28 msec 28 msec

  2 155.1.0.1 56 msec *  56 msec

!

R4#show ip route 150.1.1.1

Routing entry for 150.1.1.1/32

  Known via "static", distance 2, metric 0

  Routing Descriptor Blocks:

  * 155.1.0.1

      Route metric is 0, traffic share count is 1

 

However my results do not show the trace going via R5 but CEF and the RT table does

 

Before the port shut - CEF output

 

R4#sh ip cef 150.1.1.1

150.1.1.1/32

  nexthop 155.1.146.1 GigabitEthernet1.146

R4#

 

After port shut - CEF output

 

R4#sh ip cef 150.1.1.1

150.1.1.1/32

  nexthop 155.1.0.1 Tunnel0

R4#

 

So I can see it is going the right way

      150.1.0.0/32 is subnetted, 2 subnets

S        150.1.1.1 [2/0] via 155.1.0.1

 

However my trace is not the same - This is the workbook version

 

R4#traceroute 150.1.1.1 source 150.1.4.4

 

Type escape sequence to abort.

Tracing the route to 150.1.1.1

 

  1 155.1.0.5 28 msec 28 msec 28 msec

  2 155.1.0.1 56 msec *  56 msec

!

And this is my results - It seems it is dropping the first trace?

 

R4#traceroute 150.1.1.1 so 150.1.4.4

Type escape sequence to abort.

Tracing the route to 150.1.1.1

VRF info: (vrf in name/id, vrf out name/id)

  1  * 

    155.1.0.1 7 msec * 

R4#

 

Everything else works fine - So should I worry about things like this?

Many thanks

 

John Smile


Viewing all articles
Browse latest Browse all 10744

Trending Articles