Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Is it routing issue or acl issue?

TpacB---TpacA------XOA----XOB

This is what's happening:

TpacA can't ping XOA, but when I do extended ping with UUnetA's ip, which is on TpacA, it pings fine.

XOA can ping TpacA, but XOB and anything beyond can't ping TpacA but traffic goes across.

TpacB can ping XOA

To make matters more interesting. eBGP works fine between TpacA and XOA and traffic passes across no problem also. Traceroute works fine as well. I took out the acl on TpacA router on XO's interface and XO says they do not have one either. I did a shut and no shut last night and that seem to have fixed the problem but it started doing it again this morning.

Any help will be greatly appreciated as I've been working on this for a week with XO whom by the way suck. Their engineers won't even talk to me directly.

1 REPLY
Gold

Re: Is it routing issue or acl issue?

Is the address you are pinging from on TpacA from RFC1918 (private space). If so, the problem is that XOA and XOB probably don't have a route back to that private address space. If you are using a nat in the middle, it might not be catching the ping packets, or some such.

Without more information, it's hard to guess beyond this.

Russ

209
Views
0
Helpful
1
Replies
CreatePlease to create content