03-12-2013 03:43 AM - edited 03-07-2019 12:11 PM
Well i configured VPN between two Gateways (ASA & Router 2900)
Site A Gateway (Cisco ASA) Public IP : 86.xx.XX.XX
Site B Gateway (Cisco Router) Public IP : 196.xx.xx.xx
Site A INternal Lan : 10.4.200.0/24
Site B INternal LAN : 192.168.1.0/24
In Site-A, i have ISP modem connected direct to ASA outside interface which means i have default route to ISP
interface FastEthernet0/0
ip address 86.xx.xx.01 yy.yy.yy.yy
security-level 0
nameif outside
route outside 0.0.0.0 0.0.0.0 86.xx.xx.02
In Site - B , Router has two interface
interface Gi0/0
ip address 196.xx.xx.01 yy.yy.yy.yy
duplex auto
speed auto
!
interface Gi0/1.363
ip address 10.xx.xx.01 yy.yy.yy.yy
duplex auto
speed auto
crypto map CMAP
!
ip route 0.0.0.0 0.0.0.0 10.xx.xx.02
ip route 10.4.200.0 255.255.255.0 196.xx.xx.02
ip route 192.168.1.0 255.255.255.0 196.xx.xx.02
!
On router , if i check ping reach ability from source 10.4.200.250 to destination loopback 192.168.2.1 i got ping output like this "!!!!!!!!!!!!!!!!! "
But if i try to ping testing PC on site-B from site-A i got ping output "!.!.!.!.!.!.!.!.!.!.!.!.!" means 50% traffic drop. and i got the following debugs
As i configured static route on TMG for 10.4.200.0 with next-hop 196.xx.xx.02
Debug on Router
============
What are these messages means
Mar 11 11:33:47.069: ICMP type=8, code=0, IPSec: to crypto engine(70), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:47.069: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, output feature
Mar 11 11:33:47.069: ICMP type=8, code=0, Post-encryption output features(71), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
debu
Router#debug ip pack
Router#debug ip packet 101 de
Router#debug ip packet 101 detail
IP packet debugging is on (detailed) for access list 101
Router#debu
Router#debug
Mar 11 11:33:28.381: IP: s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02, len 29, input feature
Mar 11 11:33:28.381: UDP src=4500, dst=4500, MCI Check(80), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:28.381: FIBipv4-packet-proc: route packet from GigabitEthernet0/1.363 src 86.xx.xx.01 dst 196.xx.xx.02
Mar 11 11:33:28.381: FIBfwd-proc: Default:196.xx.xx.02/32 receive entry
Mar 11 11:33:28.381: FIBipv4-packet-proc: packet routing failed
Mar 11 11:33:28.381: IP: tableid=0, s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02 (GigabitEthernet0/0), routed via RIB
Mar 11 11:33:28.381: IP: s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02, len 29, rcvd 4
Mar 11 11:33:28.381: UDP src=4500, dst=4500
Mar 11 11:33:28.381: IP: s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02, len 29, stop process pak for forus packet
Mar 11 11:33:28.381: UDP src=4500, dst=4500
Mar 11 11:33:28.421: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:28.421: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Router#debug crypto iisa
Mar 11 11:33:28.421: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:28.605: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:28.605: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:28.605: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:29.273: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:29.273: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:29.273: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:29.341: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:29.341: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:29.341: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:29.341: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:29.341: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:29.341: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:29.341: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:29.341: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:29.341: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:29.341: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:29.341: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:29.341: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:29.345: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:29.345: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:29.345: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:29.485: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:29.485: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:29.485: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:29.905: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:29.905: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:29.905: FIBipv4-packet-proc: packet routing succeeded
^
% Invalid input detected at '^' marker.
Router#
Mar 11 11:33:34.353: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:34.353: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:34.353: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:34.353: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:34.353: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:34.353: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:34.353: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:34.353: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:34.353: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:34.569: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:34.569: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:34.569: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:34.901: IP: s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02, len 116, input feature
Mar 11 11:33:34.901: UDP src=4500, dst=4500, MCI Check(80), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:34.901: FIBipv4-packet-proc: route packet from GigabitEthernet0/1.363 src 86.xx.xx.01 dst 196.xx.xx.02
Mar 11 11:33:34.901: FIBfwd-proc: Default:196.xx.xx.02/32 receive entry
Mar 11 11:33:34.901: FIBipv4-packet-proc: packet routing failed
Mar 11 11:33:34.901: IP: tableid=0, s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02 (GigabitEthernet0/0), routed via RIB
Mar 11 11:33:34.901: IP: s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02, len 116, rcvd 4
Mar 11 11:33:34.901: UDP src=4500, dst=4500
Mar 11 11:33:34.901: IP: s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02, len 116, stop process pak for forus packet
Mar 11 11:33:34.901: UDP src=4500, dst=4500
Mar 11 11:33:34.901: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 86.xx.xx.01
Mar 11 11:33:34.901: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:34.901: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:34.901: IP: s=196.xx.xx.02 (local), d=86.xx.xx.01 (GigabitEthernet0/1.363), len 124, sending
Mar 11 11:33:34.901: UDP src=4500, dst=4500
Mar 11 11:33:34.901: IP: s=196.xx.xx.02 (local), d=86.xx.xx.01 (GigabitEthernet0/1.363), len 124, sending full packet
Mar 11 11:33:34.901: UDP src=4500, dst=4500a
Router#debug crypto isakmp
Crypto ISAKMP debugging is on
Router#
Router#
Mar 11 11:33:45.569: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:45.569: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:45.569: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:45.569: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:45.569: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:45.569: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:45.569: IP: s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02, len 116, input feature
Mar 11 11:33:45.569: UDP src=4500, dst=4500, MCI Check(80), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:45.569: FIBipv4-packet-proc: route packet from GigabitEthernet0/1.363 src 86.xx.xx.01 dst 196.xx.xx.02
Mar 11 11:33:45.569: FIBfwd-proc: Default:196.xx.xx.02/32 receive entry
Mar 11 11:33:45.569: FIBipv4-packet-proc: packet routing failed
Mar 11 11:33:45.569: IP: tableid=0, s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02 (GigabitEthernet0/0), routed via RIB
Mar 11 11:33:45.569: IP: s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02, len 116, rcvd 4
Mar 11 11:33:45.569: UDP src=4500, dst=4500
Mar 11 11:33:45.569: IP: s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02, len 116, stop process pak for forus packet
Mar 11 11:33:45.569: UDP src=4500, dst=4500
Mar 11 11:33:45.581: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:45.581: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:45.581: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:45.581: ISAKMP (1016): received packet from 86.xx.xx.01 dport 4500 sport 4500 Global (R) QM_IDLE
Mar 11 11:33:45.581: ISAKMP: set new node -291920883 to QM_IDLE
Mar 11 11:33:45.581: ISAKMP:(1016): processing HASH payload. message ID = 4003046413
Mar 11 11:33:45.581: ISAKMP:(1016): processing NOTIFY DPD/R_U_THERE protocol 1
spi 0, message ID = 4003046413, sa = 0x283EC5C4
Mar 11 11:33:45.581: ISAKMP:(1016):deleting node -291920883 error FALSE reason "Informational (in) state 1"
Mar 11 11:33:45.581: ISAKMP:(1016):Input = IKE_MESG_FROM_PEER, IKE_INFO_NOTIFY
Mar 11 11:33:45.581: ISAKMP:(1016):Old State = IKE_P1_COMPLETE New State = IKE_P1_COMPLETE
Mar 11 11:33:45.581: ISAKMP:(1016):DPD/R_U_THERE received from peer 86.xx.xx.01, sequence 0x676F4C3D
Mar 11 11:33:45.581: ISAKMP: set new node -1324581969 to QM_IDLE
Mar 11 11:33:45.581: ISAKMP:(1016):Sending NOTIFY DPD/R_U_THERE_ACK protocol 1
spi 685439936, message ID = 2970385327
Mar 11 11:33:45.581: ISAKMP:(1016): seq. no 0x676F4C3D
Mar 11 11:33:45.581: ISAKMP:(1016): sending packet to 86.xx.xx.01 my_port 4500 peer_port 4500 (R) QM_IDLE
Mar 11 11:33:45.581: ISAKMP:(1016):Sending an IKE IPv4 Packet.
Mar 11 11:33:45.581: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 86.xx.xx.01
Mar 11 11:33:45.581: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:45.581: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:45.581: IP: s=196.xx.xx.02 (local), d=86.xx.xx.01 (GigabitEthernet0/1.363), len 124, sending
Mar 11 11:33:45.581: UDP src=4500, dst=4500
Mar 11 11:33:45.581: IP: s=196.xx.xx.02 (local), d=86.xx.xx.01 (GigabitEthernet0/1.363), len 124, sending full packet
Mar 11 11:33:45.581: UDP src=4500, dst=4500
Mar 11 11:33:45.581: ISAKMP:(1016):purging node -1324581969
Mar 11 11:33:45.581: ISAKMP:(1016):Input = IKE_MESG_FROM_PEER, IKE_MESG_KEEP_ALIVE
Mar 11 11:33:45.581: ISAKMP:(1016):Old State = IKE_P1_COMPLETE New State = IKE_P1_COMPLETE
Mar 11 11:33:45.581: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:45.585: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:45.585: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:45.585: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:45.585: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:45.585: FIBipv4-packet-proc: packet routing succeeded
Router#
Router#
Mar 11 11:33:46.241: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:46.241: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:46.241: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:46.241: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:46.241: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:46.241: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:47.065: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100, len 100, input feature
Mar 11 11:33:47.069: ICMP type=8, code=0, MCI Check(80), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:47.069: FIBipv4-packet-proc: route packet from GigabitEthernet0/1.363 src 10.4.200.250 dst 192.168.1.100
Mar 11 11:33:47.069: FIBfwd-proc: packet routed by adj to GigabitEthernet0/0 196.xx.xx.01
Mar 11 11:33:47.069: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:47.069: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, output feature
Mar 11 11:33:47.069: ICMP type=8, code=0, IPSec output classification(32), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:47.069: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, output feature
Mar 11 11:33:47.069: ICMP type=8, code=0, IPSec: to crypto engine(70), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:47.069: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, output feature
Mar 11 11:33:47.069: ICMP type=8, code=0, Post-encryption output features(71), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:47.069: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), g=196.xx.xx.01, len 100, forward
Mar 11 11:33:47.069: ICMP type=8, code=0
Mar 11 11:33:47.069: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, post-encap feature
Mar 11 11:33:47.069: ICMP type=8, code=0, (1), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:47.069: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, post-encap feature
Mar 11 11:33:47.069: ICMP type=8, code=0, FastEther Channel(3), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:47.069: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, sending full packet
Mar 11 11:33:47.069: ICMP type=8, code=0
Mar 11 11:33:47.085: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:47.085: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:47.085: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:47.085: IP: s=196.xx.xx.02 (GigabitEthernet0/0), d=86.xx.xx.01 (GigabitEthernet0/1.363), len 160, sending full packet
Mar 11 11:33:47.085: UDP src=4500, dst=4500
Mar 11 11:33:47.609: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:47.609: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:47.609: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:47.609: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:47.609: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:47.609: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:47.609: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100, len 100, input feature
Mar 11 11:33:47.609: ICMP type=8, code=0, MCI Check(80), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:47.609: FIBipv4-packet-proc: route packet from GigabitEthernet0/1.363 src 10.4.200.250 dst 192.168.1.100
Mar 11 11:33:47.609: FIBfwd-proc: packet routed by adj to GigabitEthernet0/0 196.xx.xx.01
Mar 11 11:33:47.609: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:47.609: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, output feature
Mar 11 11:33:47.613: ICMP type=8, code=0, IPSec output classification(32), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:47.613: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, output feature
Mar 11 11:33:47.613: ICMP type=8, code=0, IPSec: to crypto engine(70), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:47.613: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, output feature
Mar 11 11:33:47.613: ICMP type=8, code=0, Post-encryption output features(71), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:47.613: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), g=196.xx.xx.01, len 100, forward
Mar 11 11:33:47.613: ICMP type=8, code=0
Mar 11 11:33:47.613: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, post-encap feature
Mar 11 11:33:47.613: ICMP type=8, code=0, (1), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:47.613: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, post-encap feature
Mar 11 11:33:47.613: ICMP type=8, code=0, FastEther Channel(3), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:47.613: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, sending full packet
Mar 11 11:33:47.613: ICMP type=8, code=0
Mar 11 11:33:47.613: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:47.613: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:47.613: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:47.613: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:47.613: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:47.613: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:47.613: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:47.613: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:47.613: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:47.613: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:47.613: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:47.613: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:48.313: FIBipv4-packet-proc: route packet from (local) src 196.xx.xx.02 dst 188.xx.xx.01
Mar 11 11:33:48.313: FIBfwd-proc: packet routed by adj to GigabitEthernet0/1.363 10.xx.xx.01
Mar 11 11:33:48.313: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:49.169: IP: s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02, len 29, input feature
Mar 11 11:33:49.169: UDP src=4500, dst=4500, MCI Check(80), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:49.169: FIBipv4-packet-proc: route packet from GigabitEthernet0/1.363 src 86.xx.xx.01 dst 196.xx.xx.02
Mar 11 11:33:49.169: FIBfwd-proc: Default:196.xx.xx.02/32 receive entry
Mar 11 11:33:49.169: FIBipv4-packet-proc: packet routing failed
Mar 11 11:33:49.169: IP: tableid=0, s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02 (GigabitEthernet0/0), routed via RIB
Mar 11 11:33:49.169: IP: s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02, len 29, rcvd 4
Mar 11 11:33:49.169: UDP src=4500, dst=4500
Mar 11 11:33:49.169: IP: s=86.xx.xx.01 (GigabitEthernet0/1.363), d=196.xx.xx.02, len 29, stop process pak for forus packet
Mar 11 11:33:49.169: UDP src=4500, dst=4500
Mar 11 11:33:49.929: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100, len 100, input feature
Mar 11 11:33:49.929: ICMP type=8, code=0, MCI Check(80), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:49.929: FIBipv4-packet-proc: route packet from GigabitEthernet0/1.363 src 10.4.200.250 dst 192.168.1.100
Mar 11 11:33:49.929: FIBfwd-proc: packet routed by adj to GigabitEthernet0/0 196.xx.xx.01
Mar 11 11:33:49.929: FIBipv4-packet-proc: packet routing succeeded
Mar 11 11:33:49.929: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, output feature
Mar 11 11:33:49.929: ICMP type=8, code=0, IPSec output classification(32), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:49.929: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, output feature
Mar 11 11:33:49.933: ICMP type=8, code=0, IPSec: to crypto engine(70), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:49.933: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, output feature
Mar 11 11:33:49.933: ICMP type=8, code=0, Post-encryption output features(71), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:49.933: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), g=196.xx.xx.01, len 100, forward
Mar 11 11:33:49.933: ICMP type=8, code=0
Mar 11 11:33:49.933: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, post-encap feature
Mar 11 11:33:49.933: ICMP type=8, code=0, (1), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:49.933: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, post-encap feature
Mar 11 11:33:49.933: ICMP type=8, code=0, FastEther Channel(3), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
Mar 11 11:33:49.933: IP: s=10.4.200.250 (GigabitEthernet0/1.363), d=192.168.1.100 (GigabitEthernet0/0), len 100, sending full packet
Mar 11 11:33:49.933: ICMP type=8, code=0
My contact email : muhammad.uetian.04@gmail.com
03-12-2013 09:39 AM
Problem Solved
On router ,
int gi0/0
no ip route-cache
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide