Details
-
Type:
Bug
-
Status:
Cancelled
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: Financial
-
Labels:None Labels
-
Customer:Zain Jordan
Description
Customer has reported duplicate Asset name with different serial number issue.
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
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.
Show
Bessem Manita
added a comment - 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.
Issue fixed after new AI patch
Show
Daljeet Singh Virdi
added a comment - Issue fixed after new AI patch
L3 anaylsis by Bessem:
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.