Due to HSRP running on my two 65xx switchs that are trunked together, I now have a whole slough of feasible successor routes that appear in my routing table. Having them in the eigrp topology table is no big deal, but it is really ugly in the routing table. Doing traceroutes can be very confusing to people that are not aware of how things work since whichever vlan is used to route from one switch to the next, it is still always traversing the same physical link. (Once my migration is complete so that all routing is done on one box and the other is just the standby for all vlans, the routing table will still be ugly).
So I'm thinking that if I select one route and alter the weighting so that it is always used for routing, and all my other routes become successors rather than feasible successors, then my routing table will be cleaned up without deteriorating performance.
Any pitfalls, suggestions, or experience with this sort of thing?
Passiving some number of interfaces would clean up the topo table--as long as you don't want user traffic to flow across the vlan (in other words, you only want traffic to and from hosts and servers attached to the vlan itself), go ahead and passive interface it. EIGRP won't build a neighbor adjacency across it at all.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.