Symptom
SDWAN ACLs not matching correct sequences due to TCAM misprograming, we hit incorrect sequences due to TCAM not in sync with ACL configurations,
We see CPP errors in show logging:
router#sh log | in CPP
*Nov 1 00:11:01.196: %CPPOSLIB-3-ERROR_NOTIFY: F0/0: cpp_sp_svr: cpp_sp encountered an error -Traceback=
*Nov 1 00:11:01.232: %CPPOSLIB-3-ERROR_NOTIFY: F0/0: cpp_cp_svr: cpp_cp encountered an error -Traceback=
*Nov 1 00:12:00.001: %CPP_FM-3-CPP_FM_CLIENT_WARNING: F0/0: cpp_sp_svr: Client Is Invalid: Client sdwan is editing CG without releasing previous resources. Going to ignore all requests from this client!!!
*Nov 1 00:57:33.601: %CPP_FM-3-CPP_FM_CLIENT_WARNING: F0/0: cpp_sp_svr: Client Is Invalid: Client sdwan is editing CG without releasing previous resources. Going to ignore all requests from this client!!!
Conditions
SDWAN ACL multiple changes in sequences lead to CPP tracebacks causing sequences to be misprogramed