Last Modified: Apr 28, 2025
                                            Affected Product(s):
                                            BIG-IP LTM
                                        
                                            Known Affected Versions:
                                            11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4
                                        
                                            Fixed In:
                                            12.0.0, 11.6.0 HF5
                                        
                                Opened: Oct 09, 2014 Severity: 3-Major Related Article: 
K16729                                        
                                
                                    
If the primary blade of a chassis is reset, once it rejoins the cluster as a secondary its configuration may fail to load with errors that look like this: 01070088:3: The requested object name (/Common/default-eviction-policy) is invalid. 01070935:3: Unexpected exception caught in MCPProcessor::rm_DBLowHighWide(). 01070734:3: Configuration error: MCPProcessor::check_initialization: 01070734:3: Configuration error: URL category (/Common/Abortion) cannot be deleted. It is being used by a URL filter.
The impact of this issue is that mcpd will not finish startup unless the workaround steps are performed.
This only affects chassis.
Log in to the affected blade, remove the binary database (/bin/rm -v /var/db/mcp*), and restart all services on the blade (bigstart restart).
Formerly, the primary blade of a chassis is reset, once it rejoins the cluster as a secondary its configuration may fail to load with errors that look like this: 01070088:3: The requested object name (/Common/default-eviction-policy) is invalid. 01070935:3: Unexpected exception caught in MCPProcessor::rm_DBLowHighWide(). 01070734:3: Configuration error: MCPProcessor::check_initialization: 01070734:3: Configuration error: URL category (/Common/Abortion) cannot be deleted. It is being used by a URL filter. The system will now load successfully and not hit this error.