Heck, my 3 different Rogers wavelength services we not impacted at all (although L1 services have other failure modes that take longer to recover from since there is no automatic rerouting as with L2 networks).
Sort of, our wave circuits will automatically reroute but we had to shell out the $$ for protected waves and then explicitly mention they had to be configured to be auto-revertive as that was not the default behavior for that telecom provider. Then L2 and L3 don't notice when it shifts between the working and protect paths, it happens fast enough the only visible change then is the latency difference between the two.
True, our use case is a bit different as the waves go between PoPs/DCs/Offices so the only diversity can be in the path itself. Faster to have the path switch over and have L3 re-converge only when the working and protected path are unavailable.
Sort of, our wave circuits will automatically reroute but we had to shell out the $$ for protected waves and then explicitly mention they had to be configured to be auto-revertive as that was not the default behavior for that telecom provider. Then L2 and L3 don't notice when it shifts between the working and protect paths, it happens fast enough the only visible change then is the latency difference between the two.