Fixed                
                
            
            
                
                    Created: Sep 17, 2018   
                                            Updated: Dec 3, 2018                                    
                
                    
                                    
             
         
        
            
            
                                    
                        Resolved Date: Oct 15, 2018                    
                
                                    
                        Previous ID: LIN8-9835                    
                
                                    
                        Found In Version: 10.17.41.11                     
                
                                    
                        Fix Version: 10.17.41.12                    
                
                                        
                            Severity: Severe                        
                    
                                        
                            Applicable for: Wind River Linux LTS 17                        
                    
                                    
                        Component/s: Kernel                    
                
                
                             
         
                        
                After set MTU to 9700, can not sync name table between two node, part of them will lost, and show the following error:
/*********************************/
no route to host
/*********************************/
If keep the MTU as default value, will not trigger this issue.
Not sure if this is TIPC limitation or PMTU defect
        
                        
                1, set one of node's MTU to 9700
2, config tipc on two node with tipc-config, such as:
tipc-config -addr=1.1.20552,tipc-config -be=eth:eth2.4901
3, then call tipc related API to try to do communication between two node. 
issue will happen when one node try to send tipc message to another node:
/********************************************************************/
dcal_tipc_sendmsg:829] Send multi msg to 20001f00:40000001 error: No route to host
2016/05/21 17:20:00:884762 trace/3: [dcal_tipc_sendmsg:829] Send multi msg to 2000b800:40000001 error: No route to host
2016/05/21 17:20:01:760497 trace/3: [dcal_tipc_sendmsg:829] Send multi msg to 20002000:40000001 error: No route to host
2016/05/21 17:20:01:822377 trace/3: [dcal_tipc_sendmsg:829] Send multi msg to 20002000:40000001 error: No route to host
2016/05/21 17:20:01:822494 trace/3: [dcal_tipc_sendmsg:829] Send multi msg to 20001f00:40000001 error: No route to host
2016/05/21 17:20:01:822579 trace/3: [dcal_tipc_sendmsg:829] Send multi msg to 2000b800:40000001 error: No route to host
2016/05/21 17:20:01:833981 trace/3: [dcal_tipc_sendmsg:829] Send multi msg to 20001f00:40000001 error: No route to host
2016/05/21 17:20:01:884773 trace/3: [dcal_tipc_sendmsg:829] Send multi msg to 2000b800:40000001 error: No route to host
2016/05/21 17:20:02:759920 trace/3: [dcal_tipc_sendmsg:829] Send multi msg to 20002000:40000001 error: No route to host
2016/05/21 17:20:02:822386 trace/3: [dcal_tipc_sendmsg:829] Send multi msg to 20002000:40000001 error: No route to host
2016/05/21 17:20:02:822506 trace/3: [dcal_tipc_sendmsg:829] Send multi msg to 20001f00:40000001 error: No route to host
2016/05/21 17:20:02:822667 trace/3: [dcal_tipc_sendmsg:829] Send multi msg to 2000b800:40000001 error: No route to host
2016/05/21 17:20:02:833970 trace/3: [dcal_tipc_sendmsg:829] Send multi msg to 20001f00:40000001 error: No route to host
/********************************************************************/