-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oliver Boehmer (oboehmer) wrote: ...snip...snip... > Bruce: > >> Based on the supported protocols list at: >> > http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft > /120limit/120s/120s22/s_ipevdp.htm >> I would say that MPLS/TE is not supported. I would think there is a >> need for some RSVP hooks in that scenario. > > Not sure there is. If IP event dampening holds the lineprotocol down > (i.e. when the penalty accumulated is too high), ISIS/OSPF will not get > notified, so the headend will not reoptimize (if it is configured to do > so). >
Therein lies the rub. It is not interface dampening but rather IP event dampening. So the line protocol of the interface is not held down but rather the routing protocols are notified so that *they* can consider the interface down for the purposes of adjacency formation, route advertisement, and forwarding. That's why there is a supported protocol list. - -- ========= bep -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGJ83iE1XcgMgrtyYRAluhAKDILr1Jn6KLFmuriqgJIw0wsAqLMwCgwp6j LuHNsORm2NWeuUS6W4TLZ0s= =dQ8M -----END PGP SIGNATURE----- _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
