On 12/19/20 10:45, Saku Ytti wrote:

I think the community largely got blindsided by this, I suspect
marketability of the whole solution would have been a lot poorer if
this argument was thrown around at standardisation. However, that ship
has sailed, we can implement new cheaper methods, but the damage is
done and it will be there long after we've retired.

I know I got blindsided, and it was so obvious, but not a problem I
was aware until a customer complained about excessive refresh. It
would be funny to analyse how much more wattage is drawn because of
this globally. how many early control-plane upgrades.  Is it
immaterial or material? I don't know. But it does seem to put some
customers control-planes over the edge.

We suffered with this a great deal when we used ASR9001's for peering. A bunch of peers complained about it, to the extent that they had to drop sessions.

Problem was fixed by moving to the MX204. Not elegant, and an unnecessary spend.

Mark.
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to