Loss of PWE3 Service Running Status After the PTN NE Explorer Process Is Restart
Loss of PWE3 Service Running Status After the PTN NE Explorer Process Is RestartedKeywordsRunning status, process restart, PTN NE Explorer process Applicable version
SymptomA frontline engineer restarted the PTN NE Explorer process during routine U2000 maintenance and then synchronized all data in the Manage PWE3 Service window. After synchronization, the running status of all PWE3 services on a PTN network was displayed as —. Problem IdentificationØ The running status of services is saved to a PTN NE memory in real time. After the PTN NE Explorer process is restarted, the running status of all services is initialized and becomes invalid (void). In this case, synchronizing PWE3 services will cause invalid values to be refreshed to the Manage PWE3 Service window. As a result, the running status of all PWE3 services is displayed as —. Ø VPLS and static tunnel services also encounter the same fault. Ø This problem is caused by special implementation of the PTN NE Explorer process rather than a bug. To prevent this problem, running status of services has to be manually refreshed. Problem LocatingStep 1 Checked the NML_IP log and found that service running status, reported by the PTN NE Explorer process to E2E, was void (invalid) during PWE3 service synchronization. Step 2 Checked the PTN NE Explorer process log and found that the process has been restarted. Then checked the code and found that the running status has been read from the PTN NE memory and lost after memory data was synchronized to the U2000. SolutionPerform the following operations after restarting the PTN NE Explorer process: Step 3 Synchronize PWE3 services in the Manage PWE3 Service window.
Step 4 Right-click a desired PWE3 service, right-click, and choose Refresh Running Status from the shortcut menu to manually refresh service running status.
|

Favorite (0)