[LS-925] Zain JD | Duplicate Node name with different SN Created: 10/Feb/26 Updated: 10/Mar/26 Due: 12/Feb/26 Resolved: 26/Feb/26 |
|
| Status: | Cancelled |
| Project: | L3 Support |
| Component/s: | Financial |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Normal |
| Reporter: | Daljeet Singh Virdi | Assignee: | Daljeet Singh Virdi |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 5 hours | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
d0fb4212-2430-4cbd-a739-2486170b0f4e.png
duplicate assset name with different sn.png
|
| Customer: |
Zain Jordan
|
| Planned Start: | |
| Planned End: | |
| Actual Start: | |
| Date of Baselining: |
| Description |
|
Customer has reported duplicate Asset name with different serial number issue. |
| Comments |
| Comment by Daljeet Singh Virdi [ 10/Feb/26 ] |
|
L3 anaylsis by Bessem: These two board are related to different node types (eNodeB and RAN BS), and in general this can be acceptable. |
| Comment by Bessem Manita [ 13/Feb/26 ] |
|
Dear Daljeet, These two board are related to different node types (eNodeB and RAN BS), and in general this can be acceptable. However, in this specific case we are getting Role4G and eNodeB with the same name(52954-ULN-Naaimeh-North-PE-TASC-O). Kindly check the XML to confirm whether this information is valid, as we should not have Role4G and eNodeB defined with the same name. |
| Comment by Daljeet Singh Virdi [ 26/Feb/26 ] |
|
Issue fixed after new AI patch |