Symptom
FRR protection not removed after removing path-protection config and replacing it with NCP in the same configuration batch
Conditions
Issue happens when the removal of path-protection and the addition of non-zero max-install-standby-paths is committed together
Workaround
Do not commit these in the same batch. Delete path protection, then configure NCP in a separate configuration action.
Further Problem Description
This is not actually a critical issue as if max-install standby is more than 0 the LSP in question should still remain up. What is unexpected is that the primary LSP has FRR protection, when NCP does not support this feature yet. Behaviour should be normal if max-install is set to 0 and should return to normal with any LSP state change.
