H_S
March 4, 2026, 10:01am
1
The screenshot above corresponds to a COW site that has recently been relocated and is currently in the integration phase at the new location.
When checking the configuration:
In 2G and 3G, the target site name appears correctly updated according to the new location.
However, in LTE, the system is still displaying the old site name from the previous location.
In addition, the DSP S1 printout is showing abnormal behavior.
This suggests that some configuration element may not have been fully updated or synchronized after the relocation.
So here my questions to the Huawei BSS experts:
What could be causing LTE to still reference the old site name while 2G/3G show the correct one?
Could this be related to S1 configuration, site database synchronization, or incomplete parameter updates during relocation?
What would be the recommended steps to troubleshoot and resolve this issue?
H_S:
When checking the configuration:
In 2G and 3G, the target site name appears correctly updated according to the new location.
However, in LTE, the system is still displaying the old site name from the previous location.
In addition, the DSP S1 printout is showing abnormal behavior.
This suggests that some configuration element may not have been fully updated or synchronized after the relocation.
So here my questions to the Huawei BSS experts:
What could be causing LTE to still reference the old site name while 2G/3G show the correct one?
Could this be related to S1 configuration, site database synchronization, or incomplete parameter updates during relocation?
What would be the recommended steps to troubleshoot and resolve this issue?
Check LTE site name parameters in eNodeB. Verify S1 configuration and MME settings. Confirm database synchronization between BSC/RNC and eNodeB. Review relocation-related scripts and re-run missing updates if needed.
