Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
It appears you're quite right. Unfortunately I didn't notice the incompatibility with MLPPP since it wasn't clear in the link I had provided, as it is in this link: http://www.cisco.com/en/US/docs/ios/ios_xe/dial/configuration/guide/dia_media-ind_multi_ppp_xe_ps9587_TSD_Products_Configuration_Guide_Chapter.html#wp1001080
Since MLPPP appears not to offer a built-in method to take down a poor bundle member, an alternative might be (on the later IOS platforms) to self monitor the individual links and if a link's CRCs are considered too high to have an automation script on the platform shut the link.
