02-10-2009 09:32 AM - edited 03-06-2019 03:57 AM
hi, gang,
Is it a good practice to put 450 static routes on a layer 3 switch? just because there are 2 ISP's to connect. I wonder how the performance is.
Thanks,
Jon
02-10-2009 10:08 AM
The performance will be fine since what is worng with this is the amount of static route you will need to manage manually. But the performance should be okay if not better since there is no routing table that needs to be updated and populated dynamically.
02-10-2009 10:13 AM
Hello Jon,
it can be done but I would move to eBGP connections where you receive just a few routes from one ISP and only a default route from the other one.
(other arrangaments are possible like receiving few specific routes and a default route from each provider)
This allows also for a better behaviour during faults: failure detection is far better.
Static routes if an intermediate device is on the middle become a problem
I would recommend to ask the providers about a BGP session where you put a filter and accepts only some routes (the ones you want) from each.
otherwise reliable static routing but 450 routes are difficult to manage
http://www.cisco.com/en/US/docs/ios/12_3/12_3x/12_3xe/feature/guide/dbackupx.html
Hope to help
Giuseppe
02-10-2009 11:10 AM
The (SDM prefer routing) provides a config template for a switch database Managment for Resource allocation.
It's also rely on the Type of Switches Models & series..
HTH
Mohamed
02-10-2009 11:21 AM
Thanks guys. The bunch of static routes are just for routing optimization. the redundancy is achieved by 2 default routes. The difficulty to manage hundreds of static routes manually is anticipated. As long as the switch can handle such a big routing table, it's fine.
Mohamed, not sure what you're referring to, can you pls elaborate a little bit? thx.
Jon
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