Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: NEP
-
Customer:OMAN-Tel
-
Severity:Major
-
Defect Category:Improper Test Plan
-
Product:NEP
Description
Dear dr Khaled and L3 team
As per our troubleshooting with Natnael , the initial view NE_ROUTER_DETAILS is not collecting SDWAN routers and it seems someone made a workaround and collected the data of SDWAN and they were added statically to the table NE_ROUTER_DETAILS_STATIC to be part of the main view used by OT system VD_Integration
It is required to review the main view NE_ROUTER_DETAILS part and adjust it to be able to collect SDWAN routers also not only ( CE,CPE, CORE etc,,,) as shown in attachment and not rely on STATIC table
Thanks
Abir
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
Kindly we need to stop the NE_ROUTER_DEATILS_STATIC and take the value SDWAN under #SNMP_CATEGORY for SDWAN nodes.
Dear @Khaled M Ayoubi,
Regarding the NE_ROUTER_DETAILS view, after reviewing the data, we concluded that there are two filtering rules applied: CPE and MONITORED. These filters are functioning as expected, and we can see that SDWAN entries are already included in the view. However, we need to identify the source of the SNMP data, as observed in the snapshot showing duplicates under SNMP_CATEGORY (SDWAN vs. Router), with the difference mainly in the SNMP_COMMUNITY field:
ss
I have already removed NE_ROUTER_DETAILS_STATIC from the view query, and the resulting data is now clearer, which allows us to better analyze the inconsistencies and isolate potential issues:
ss
In conclusion, there are data issues that must be addressed, particularly with SNMP_COMMUNITY and NE_POSITION, to ensure the integrity and accuracy of the view. These corrections are necessary before finalizing the view for reporting and operational use.
ss
Best Regards,
Marwan Kanaan I Software Developer
if data filled correctly SDWAN router details will be available
Dear @Khaled M Ayoubi,
As discussed, the changes to NE_ROUTER_DETAILS have been applied. SDWAN devices are now displayed correctly for vendors Lanner, Advantec, and VMware Inc.
ss attatched
However, please note that the NEs for vendor VMware Inc are not shown because the corresponding entries in ELEMENTADDITIONALINFO are missing the ATTRIBUTE = 'MONITORED' and VALUE = 'TRUE'.
The new view is attached.
Best Regards,
Marwan Kanaan I Software Developer
New script applied on PROD and validated by Khaled
to prepare the updated script but to apply after adjusting the cities from customer side