05-05-2021 10:55 AM
Hi,
My trace is not working in one direction.
Ping for Site A to Site B and vice versa works (PING's are from CE TO CE and CPE)
SITEA#ping vrf DDDDD-DDDD x.x.228.57 source x.x.228.65
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to x.x.228.57, timeout is 2 seconds:
Packet sent with a source address of x.x.228.65
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/8 ms
SITEA#ping vrf DDDDD-DDDD x.x.228.58 source x.x.228.65
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to x.x.228.58, timeout is 2 seconds:
Packet sent with a source address of x.x.228.65
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/8 m
=====================================================================================
SITEB#ping vrf DDDDD-DDDD x.x.228.65 source x.x.228.57
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to x.x.228.65, timeout is 2 seconds:
Packet sent with a source address of x.x.228.57
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 7/7/8 ms
SITEB#ping vrf DDDDD-DDDD x.x.228.66 source x.x.228.57
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to x.x.228.66, timeout is 2 seconds:
Packet sent with a source address of x.x.228.57
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 6/6/7 ms
========================================================================================
Trace works from SITE A to SITE B (FROM CE to CE and CPE)
SITEA#trace vrf DDDDD-DDDD x.x..228.57 source x.x.228.65
Type escape sequence to abort.
Tracing the route to 172.25.228.57
VRF info: (vrf in name/id, vrf out name/id)
1 x.x.54.198 4 msec 0 msec 0 msec
2 x.x.43.150 4 msec 4 msec 4 msec
3 x.x.43.149 8 msec * 8 msec
SITEA#trace vrf DDDDD-DDDD x.x..228.58 source x.x.228.65
Type escape sequence to abort.
Tracing the route to 172.25.228.58
VRF info: (vrf in name/id, vrf out name/id)
1 x.x.54.198 4 msec 0 msec 0 msec
2 x.x.43.150 4 msec 4 msec 4 msec
3 x.x.43.149 8 msec 8 msec 8 msec
4 x.x.228.58 8 msec * 8 msec
=====================================================================
Trace from SITEB to SITEA only works till CE interface (.228.65) but does work for CPE (.228.66)
SITEB#trace vrf DDDDD-DDDD x.x.228.65 source x.x.228.57
Type escape sequence to abort.
Tracing the route to x.x.228.65
VRF info: (vrf in name/id, vrf out name/id)
1 x.x.43.150 3 msec 3 msec 2 msec
2 x.x.54.198 6 msec 7 msec 6 msec
3 x.x.54.197 7 msec * 7 msec
SITEB#trace vrf DDDDD-DDDD x.x.228.66 source x.x.228.57
Type escape sequence to abort.
Tracing the route to x.x.228.66
VRF info: (vrf in name/id, vrf out name/id)
1 x.x.43.150 3 msec 3 msec 3 msec
2 x.x.54.198 5 msec 6 msec 6 msec
3 x.x.54.197 7 msec 7 msec 7 msec
4 * * *
5 * * *
(edited OUTPUT)
29 * * *
30 * * *
05-05-2021 12:36 PM
Ping works from x.x.228.57 to x.x.228.66, but traceroute from x.x.228.57 to x.x.228.66 don't. So it looks like routing is fine.
ping uses ICMP and traceroute uses UDP, so It could be due to an ACL on Site A CPE that does not allow UDP traffic in or out.
Regards,
05-06-2021 04:53 AM
I double checked all the CE's and CPE's. There are no ACL's for UDP.
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