Re: CEF record issue on C1812 IOS Version 12.4(6)T11

hajyoshi00 · ‎11-08-2010

Hi all

I can't ping the ip 192.168.1.3 from the C1812(RT1).
I check to CEF table and the routing table of the C1812(RT1),
I find the the ip 192.168.1.3 record on CEF table(*1).

After a while,
I can ping the ip 192.168.1.3 from the C1812(RT1).
I check to CEF table and the routing table of the C1812(RT1),
I can't find the the ip 192.168.1.3 record on CEF table(*2).

Can anyone help ?

Thanks in advance

Hajime Yoshida

(*1)
===PING NG LOG===
RT1#ping 192.168.1.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.3, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
RT1#
RT1#ping 192.168.62.253

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.62.253, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
RT1#

RT1#sh ip cef detail
-snip-
192.168.1.3/32, version 4904, epoch 0, cached adjacency 192.168.1.3
0 packets, 0 bytes
via 192.168.1.3, Vlan1, 0 dependencies
next hop 192.168.1.3, Vlan1
valid cached adjacency

RT1#sh ip route
-snip-
S 192.168.1.0/24 [1/0] via 192.168.62.253

===PING OK LOG===
RT1#ping 192.168.1.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/21/24 ms
RT1#
RT1#ping 192.168.62.253

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.62.253, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
RT1#

RT1#
RT1#sh ip cef detail
-snip-
Adjacency Table has 105 adjacencies
0.0.0.0/0, version 13, epoch 0, attached, cached adjacency to Dialer2
0 packets, 0 bytes
via Dialer2, 0 dependencies
    valid cached adjacency
0.0.0.0/32, version 1, epoch 0, receive
172.25.178.0/24, version 14, epoch 0, attached, cached adjacency to Dialer1
0 packets, 0 bytes
via Dialer1, 0 dependencies
    valid cached adjacency
172.25.178.1/32, version 4, epoch 0, connected, receive
192.168.1.0/24, version 18, epoch 0, cached adjacency 192.168.62.253
0 packets, 0 bytes
via 192.168.62.253, 0 dependencies, recursive
    next hop 192.168.62.253, Vlan1 via 192.168.62.253/32
    valid cached adjacency
192.168.3.0/24, version 19, epoch 0, cached adjacency 192.168.62.200
0 packets, 0 bytes
via 192.168.62.200, 0 dependencies, recursive
    next hop 192.168.62.200, Vlan1 via 192.168.62.200/32
    valid cached adjacency
192.168.5.0/24, version 20, epoch 0, cached adjacency 192.168.62.253
0 packets, 0 bytes
via 192.168.62.253, 0 dependencies, recursive
    next hop 192.168.62.253, Vlan1 via 192.168.62.253/32
    valid cached adjacency

RT1#sh ip route
-snip-
S 192.168.1.0/24 [1/0] via 192.168.62.253

jorge.calvo · ‎11-08-2010

Hello,

Have you tried the commands "clear adjacency epoch" and "clear adjacency"?

It seems you have an inconsistence:

RT1#sh ip cef detail
-snip-
192.168.1.3/32, version 4904, epoch 0, cached adjacency 192.168.1.3
0 packets, 0 bytes
via 192.168.1.3, Vlan1, 0 dependencies
next hop 192.168.1.3, Vlan1
valid cached adjacency

192.168.1.0/24, version 18, epoch 0, cached adjacency 192.168.62.253
0 packets, 0 bytes
via 192.168.62.253, 0 dependencies, recursive
next hop 192.168.62.253, Vlan1 via 192.168.62.253/32
valid cached adjacency

Hope this helps.

hajyoshi00 · ‎11-09-2010

Two records that you pointed out are not at the same time.

The cef record 192.168.1.3/32 is on the cef table,
I can't ping to the ip 192.168.1.3.

The cef record 192.168.1.3/32 is not on the cef table,
I can ping to the ip 192.168.1.3.

Thanks in advance.

jorge.calvo · ‎11-09-2010

Hi,

What I see is that when you have in CEF the entry pointing to 192.168.1.3/32 with next hop 192.168.1.3 you cannot ping it and you can ping it when the entry is the correct one: 192.168.1.0/24 with next hop 192.168.62.23.

I would try clearing the adjacency table.

Regards.