Hello everyone!
Today, I'd like to share a case.
Problem Description
The message information show error when trace signaling U2000-MBB ATAE RHA V200R017C10CP2303+HP000. When upgrade U2000 to V200R017C10CP2303, operation was done successfully and most basic service can run as normally, But when some user trace signaling of SE2900 NE by using U2000 trace management, there is error message when view more information.
Problem Analysis
The problem occurred after upgrade U2000 to new version, meanwhile trace signaling function worked properly before upgrade (V200R015). In order to make sure problem does not came from NE side, then trace both NE in LMT and U2000 in the same time, and the result is tracing in LMT is normal, but U2000 is error. Furthermore, it is normal when export trace from U2000 and reopen in offline mode.
Root Cause
As checked parsing file that had been downloaded to local PC, the field name “Message type” and “Interface type” cannot be parsed and shown N/A. then test imported the trace file “.tmf” to U2000 R16 and R17. It is normal in R16, but error in R17.
Through R&D compare the code of R16 and R17, they found that there is some code bug which is a protection added in R17, when identify the length of a field cannot be greater that the total length of the message, result into error of detailed messages. To solved this R&D release patch version iManagerU2000V200R017C10HP0016 for fix bus issue.
Solution Description
After install new patch package iManagerU2000V200R017C10HP0016, the problem was solved, the trace signaling function work as normal.
Welcome to leave a message below.
We’ll study together.
Thank you!
