No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

There is 3 minutes r**ing interruption of VCN3000

Publication Date:  2019-07-30  |   Views:  313  |   Downloads:  0  |   Author:  y00199335  |   Document ID:  EKB1000125600


Issue Description

There is 3 minutes r**ing interruption of VCN3000 in a project.

Version: VCN3000 V100R001C02SPC131

Handling Process

1. Analyze the logs and backup logs of MU, confirmed that there is MU initialization, which means MU restart.

2. Analyze the operation logs of OMU Portal, confirmed that MU was restarted from the IP

2016-06-20 09:11:41.897+00:00|   Info|TID:0x7F04B3A00700|insert ip to list|ip is, time is 1466413901 

2016-06-20 09:12:14.472+00:00|   Info|TID:0x7F04B3A21700|tcp link open, turn to open|linkid=MPSwLr6vkKGAjQr+h3gD0GO-y76qHnumKsnt+Ap7, peer=, socketfd=24 
2016-06-20 09:12:14.472+00:00|   Info|TID:0x7F04B3A21700|nss server opened|nss=server, linkid=MPSwLr6vkKGAjQr+h3gD0GO-y76qHnumKsnt+Ap7 
2016-06-20 09:12:14.472+00:00|   Info|TID:0x7F04B3A21700|NetElement Add Linkid|MPSwLr6vkKGAjQr+h3gD0GO-y76qHnumKsnt+Ap7 
2016-06-20 09:12:14.473+00:00|   Info|TID:0x7F04B3A21700|NetElement Rmv Linkid|MPSwLr6vkKGAjQr+h3gD0GO-y76qHnumKsnt+Ap7 
2016-06-20 09:12:14.473+00:00|   Info|TID:0x7F04B3A21700|NetElement Add Linkid|OMU_Portal#2016-06-20 09:12:14_3_38703 
2016-06-20 09:12:14.473+00:00|   Info|TID:0x7F04B3A21700|in server, process nss client login success| peer LinkId = OMU_Portal#2016-06-20 09:12:14_3_38703. 
2016-06-20 09:12:14.473+00:00|   Info|TID:0x7F04B3A79700|report link status|ReqID=[0x8001],Thread=[0xb3a79700],ServerID=0,CmdType=2 
2016-06-20 09:12:14.478+00:00|   Info|TID:0x7F04B3A00700|DevMgrService HandleCmd|ReqID[0x1002],linkId[OMU_Portal#2016-06-20 09:12:14_3_38703] 
2016-06-20 09:12:14.478+00:00|   Info|TID:0x7F04B3A00700|Reboot System|[action=Restart,nodecode=cfe436810afe4bb0a5d8c92c4253d962] 
2016-06-20 09:12:14.498+00:00|   Info|TID:0x7F04B3A00700|Reboot Module|[action=Restart,module=MU#cfe436810afe4bb0a5d8c92c4253d962,nodecode=cfe436810afe4bb0a5d8c92c4253d962

Root Cause

Man-made restart of MU which caused this issue.


Give a training to the maintenance engineers about the high-risk operation.


Not only need to analyze the system logs, but aslo the operation logs.