When it happens, I can ping the remote end from the 7513, but nothing outside of the 7513.
For Example.... SERVER --ethernet--- 7513 ---multilink (2 T1's)--- END USER 1 multilink T1 bounces. After the T1 comes up, the multilink interface and both T1's show as up/up and 7513 can ping END USER, but END USER can't ping 7513 and no connection to/from SERVER to END USER. Hope that makes sense. -----Original Message----- From: Rodney Dunn [mailto:[email protected]] Sent: Tuesday, August 04, 2009 1:24 PM To: Todd Shipway Cc: [email protected] Subject: Re: [c-nsp] 7513 multilink interface issue That should never happen and is possibly a bug. Can you ping directly over the bundle to the ip address on the other side when it's broke? If not, go to the latest code and see if it's fixed...or do some debugging: 'sh ip cef for other side of bundle, debug ip packet, etc... Rodney Todd Shipway wrote: > We have several customers setup with T1's multilinked. We are running into > a problem with a single multilink member bouncing causing routing issues. > When a single T1 member of a multilink group bounces, traffic to the overall > multilink interface stops and we have to manually shut and no shut the > multilink interface to get traffic flowing again. > > Has anyone seen this before and if so, know what the issue may be? > _______________________________________________ > 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/
