Destination Node & Destination GW are not collocated.jpg
OMAN-Tel
[LS-507] Destination Node and Destination GW are not collocated Created: 18/Jul/25 Updated: 17/Sep/25 Due: 22/Jul/25 Resolved: 17/Sep/25 |
|
| Status: | Closed |
| Project: | L3 Support |
| Component/s: | NEP |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Normal |
| Reporter: | Aurobinda Panda | Assignee: | Aurobinda Panda |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | MS_OT, Service_routing | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 1 hour | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
Destination Node & Destination GW are not collocated.jpg
|
| Customer: |
OMAN-Tel
|
| Planned Start: | |
| Planned End: | |
| Severity: | Major |
| Product: | NEP |
| REQUESTER: | INTERNAL |
| Actual Start: | |
| Date of Baselining: |
| Description |
|
I have checked the implementation. It is implemented in RB report. But still showing error which is not relevant. In the above SS, the destination node is collocated with Destination GW, but Still error message showing as “Destination Node TCC-SHLR and Destination GW NGN-TCC-SX-EXT-LSW-1 are not collocated” & “Destination Node Sohar_SHLR and Destination GW NGN-SOH-SX-EXT-LSW-0 are not collocated”. |
| Comments |
| Comment by Bessem Manita [ 21/Jul/25 ] |
|
Dear Aurobinda, Issue fixed. will be released in patch 3.7.0.1325. BR, |
| Comment by Aurobinda Panda [ 17/Sep/25 ] |
|
Issue fixed. Ticket closed. |