Hi Saku
Thank you for your support I really appreciate your help, we have solved this issue after we raised it to the remote end looks like they have some qos based on the prefixes and was misconfigured and now the issue is resolved thanks again Nareshchandra Paturi On Thursday, February 27, 2014 1:49 PM, Saku Ytti <[email protected]> wrote: On (2014-02-26 07:27 -0800), naresh reddy wrote: > I did verfy form a couple of lookup websites and the trace goes through the > same path > > but cant verify from the remote end > have raised a issue with the remote end operation waiting for them to get > back to me This would be complicated to debug in own network with 11 hopes, with Internet and no visibility to other side it may not be possible solve. What you could try is add secondary addresses on your 'working' VLAN, like 10 addresses in row. And source ping from each of them. If you observe packet loss on some address in 'working' then we can pretty safely assume it's ECMP/802.1AX issue somewhere in path. -- ++ytti _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
