RE: Juniper failes to change keys (More MD5 fun: Cisco uses wrong MD5key for old session after key change)

I agree here. If we can roll new md5 keys without session resets I am all
for it. I believe Juniper needs to fix their implementation. Especially
with md5 rolling out network wide for quite a few networks. If an employee
leaves and we have to reset the md5 passwords for the entire network with a
hybrid of Juniper and Ciscos, I would love to not have to bounce all of my
sessions. I think your best bet is to call JTAC and ask for a feature


I'd point out that this headache is likely why MANY networks didn't deploy
md5 before last week, or perhaps haven't even deployed it to date...