rapid network reconvergence technology?|
|
|
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
||||||||||
|
Posted by Trs80 on August 16, 2009, 5:04 pm
Please log in for more thread options
On a simple routed path with 2 paths, if a path is broken, it takes about 2 seconds for data to be rerouted over the alternate path. Is there technology available that will provide much faster router reconvergence over a simple 2 path network like described above? Nortel has something called SuperMezz but I cant find any information about it or how it works. Does Cisco have something. Any url references or search tips would be appreciated. thank you | ||||||||||
|
Posted by bod43 on August 16, 2009, 7:50 pm
Please log in for more thread options > On a simple routed path with 2 paths, if a path is broken, it takes about=
2
> seconds for data to be rerouted over the alternate path.
ut
> > Is there technology available that will provide much faster router > reconvergence over a simple 2 path network like described above? > > Nortel has something called SuperMezz but I cant find any information abo= > it or how it works. =A0Does Cisco have something. =A0Any url references o=
r
> search tips would be appreciated.
> thank you I have heard that ISIS has the fastest failover of the IGPs. http://www.cisco.com/en/US/technologies/tk869/tk769/technologies_white_pape= r09186a00801dce40.html May get you started. Unless you really, really need fast failover I would not recommend fiddling with the default timers. At the end of the day while some super quick failover sounds quite seductive if you end up creating an unstable network that simply dies when it goes wrong no one will give you any prizes. If you say more about what you are wanting to do then maybe someone can come up with some suggestions. For example - - how many routers/links/user segments are required - what protocols/applications require the quick failover - what bandwidth is the slowest link - probably more questions I have not read this - http://www.networkingunlimited.com/bookpages.html The author is a past poster here and seems pretty sensible. I think the book was out of print but maybe amazon have a used one. It may be a bit out of date regarding timer settings but should have good ideas. You could always hire him. http://www.sun.com/blueprints/1203/817-4683.pdf I bumped into this - not read it either. | ||||||||||
|
Posted by bod43 on August 16, 2009, 8:03 pm
Please log in for more thread options
> I have not read this -http://www.networkingunlimited.com/bookpages.html
High Availability Networking with Cisco (Paperback) by Vincent C. Jones (Author) Seems that someone likes it - =A3169.81 + =A32.75shipping Used - Like New Seller: anybook-uk Bet Vincent wishes he has a few in his retirement fund:-) Other people are asking *much less* by the way. | ||||||||||
|
Posted by Stephen on August 17, 2009, 12:23 pm
Please log in for more thread options
>On a simple routed path with 2 paths, if a path is broken, it takes about 2
a lot depends on what is making the reroute happen.
>seconds for data to be rerouted over the alternate path. > to change to a new path you generally need to 1. detect the fault in a circuit carrying traffic and switch. cisco by default add a delay to this of 5 sec for some types of interface 2. wait for any routing protocol delay 3. wait for any routing updates needed (n/a if you run OSPF or IS-IS, can be avoided with EIGRP with good design - but often isnt). 4. recalc the route 5. update the forwarding table and start using it. note 1 is nothing directly to do with the routing protocol. >Is there technology available that will provide much faster router
yes - and some other things that may help in some setups, such as MPLS
>reconvergence over a simple 2 path network like described above? > fast reroute. >Nortel has something called SuperMezz but I cant find any information about
>it or how it works. Does Cisco have something. Any url references or >search tips would be appreciated. the golden rule is - avoid non standard "stuff" whenever you can as the unpleasant surprise risks go up. cisco has a bunch of best practice docs - unfortunately they just "improved" their web site again to make it more industry specific and so made them much more difficult to find. Talk about shooting yourself in the foot..... this one is about actual convergence in a campus, but the principles and routing protocols are applicable to a WAN. http://www.cisco.com/en/US/docs/solutions/Enterprise/Campus/HA_recovery_DG/campusRecovery.html >thank you
--
> Regards stephen_hope@xyzworld.com - replace xyz with ntl | ||||||||||
|
Posted by John Agosta on August 17, 2009, 6:51 pm
Please log in for more thread options
>
>>On a simple routed path with 2 paths, if a path is broken, it takes about
>>2 >>seconds for data to be rerouted over the alternate path. >> > a lot depends on what is making the reroute happen.
> > to change to a new path you generally need to > > 1. detect the fault in a circuit carrying traffic and switch. > cisco by default add a delay to this of 5 sec for some types of > interface > 2. wait for any routing protocol delay > 3. wait for any routing updates needed (n/a if you run OSPF or IS-IS, > can be avoided with EIGRP with good design - but often isnt). > 4. recalc the route > 5. update the forwarding table and start using it. > > note 1 is nothing directly to do with the routing protocol. > >>Is there technology available that will provide much faster router
>>reconvergence over a simple 2 path network like described above? >> > yes - and some other things that may help in some setups, such as MPLS
> fast reroute. > >>Nortel has something called SuperMezz but I cant find any information
>>about >>it or how it works. Does Cisco have something. Any url references or >>search tips would be appreciated. >
http://www.cisco.com/en/US/docs/solutions/Enterprise/Campus/HA_recovery_DG/campusRecovery.html
> the golden rule is - avoid non standard "stuff" whenever you can as > the unpleasant surprise risks go up. > > cisco has a bunch of best practice docs - unfortunately they just > "improved" their web site again to make it more industry specific and > so made them much more difficult to find. Talk about shooting yourself > in the foot..... > > this one is about actual convergence in a campus, but the principles > and routing protocols are applicable to a WAN. > >
>>thank you
>> > --
> Regards > > stephen_hope@xyzworld.com - replace xyz with ntl You want to look into "Bi-directional Forwarding Detection" (BFD) ((seriously, it's called "BFD") -ja | ||||||||||
|
Home Cabling GuideFinally, an instantly downloadable book that saves you thousands in home improvement dollars! Enjoy living in 21st century technology-advanced home while increasing its selling value and competitive advantage on the real estate market. Whether your cabling is for home office or high-tech leisure, you can wire your home yourself or learn "wirish" to speak with your cabling contractors in their language! Learn More |