IIRC, and I may be wrong, either IS-IS or CLNS (can't remember which)
can look at congestion, and EIGRP can look at load if you tweak the K
parameters.
-Ejay
IIRC, and I may be wrong, either IS-IS or CLNS (can't remember which)
can look at congestion, and EIGRP can look at load if you tweak the K
parameters.
-Ejay
Opposite problem -- he wants to delay routing updates if the link is full.
EIGRP by default won't use more than 25/50% (I forget) of link bw, for
instance, but I'm not aware of any intentional features in other IGPs to do
this.
If routing updates constitute enough traffic to disrupt your links, you need
to investigate why you have so many updates instead of putting a band-aid on
the problem.
S
Ejay Hire wrote:
IIRC, and I may be wrong, either IS-IS or CLNS (can't remember which)
can look at congestion, and EIGRP can look at load if you tweak the K
parameters.
Silly redistribution of IGP into BGP leads to flapping.
Flapping leads to dampening.
Dampening leads to suffering.
Alex
Suffering leads to pain
Pain leads to the dark side?
Stephen Sprunk wrote:
Opposite problem -- he wants to delay routing updates if the link is full.
EIGRP by default won't use more than 25/50% (I forget) of link bw, for
instance, but I'm not aware of any intentional features in other IGPs to do
this.
Both OSPF and ISIS in Cisco's have pacing, ie they will not flood LSAs/LSPs
over a certain configurable limit. Not sure about other platforms..
-A
Be mindful of your routes Master Luke!