← חזרה לרשימה

Draft #8 — ticket #11584

סטטוס: pending · ביטחון: 0.70

הטיקט

נושא: Network latency check

Network latency check

שיחות קודמות

agent: Hi Eitan Calderon, Performance and Reliability Issues Upon reviewing the logs from the past month, we have identified several recurring issues: Packet Loss: Multiple instances of packet loss have been logged, particularly during peak usage hours. This has likely contributed to occasional network slowdowns and reduced overall efficiency. Below are a few notable entries from the logs: 2024-12-07 11:45:52: Packet loss detected on Switch 1, port 1, 8% packets dropped. 2024-12-15 09:32:18: Packet loss detected on Switch 4, port 5, 6.5% packets dropped. 2024-12-20 20:10:34: Packet loss detected on Switch 3, port 13, 9% packets dropped. 2024-12-26 18:12:54: Packet loss detected on Switch 1, port 9, 7.8% packets dropped. 2024-12-29 11:05:20: Packet loss detected on Switch 3, port 6, 9% packets dropped. 2024-12-30 08:17:43: Packet loss detected on Switch 1, port 2, 7% packets dropped. 2025-01-02 10:30:11: Packet loss detected on Switch 4, port 11, 8.5% packets dropped. 2025-01-04 09:50:45: Packet loss detected on Switch 1, port 14, 10% packets dropped. 2025-01-05 16:30:10: Packet loss detected on Switch 3, port 9, 9.5% packets dropped. 2025-01-05 17:40:12: Packet loss detected on Switch 1, port 4, 11% packets dropped. 2025-01-05 19:55:33: Packet loss detected on Switch 4, port 7, 8.2% packets dropped. 2025-01-05 20:25:50: Packet loss detected on Switch 3, port 11, 9.8% packets dropped. 2025-01-05 21:00:45: Packet loss detected on Switch 1, port 10, 7.5% packets dropped. 2025-01-05 22:35:10: Packet loss detected on Switch 4, port 3, 8.9% packets dropped. 2025-01-05 23:10:25: Packet loss detected on Switch 3, port 5, 9.3% packets dropped. Increased Latency: There have been consistent reports of increased latency, especially when handling high-bandwidth applications. The logs indicate several instances where latency exceeded acceptable thresholds: 2024-12-18 10:20:47: Latency spike detected on Switch 3, port 4, average latency 315ms. 2024-12-24 13:12:58: Latency spike detected on Switch 1, port 7, average latency 330ms. 2024-12-27 15:10:33: Latency spike detected on Switch 3, port 8, average latency 340ms. 2024-12-31 17:45:11: Latency spike detected on Switch 4, port 10, average latency 320ms. 2025-01-01 11:25:54: Latency spike detected on Switch 1, port 3, average latency 310ms. 2025-01-03 08:20:25: Latency spike detected on Switch 1, port 12, average latency 345ms. 2025-01-05 14:05:50: Latency spike detected on Switch 3, port 3, average latency 355ms. 2025-01-05 18:42:12: Latency spike detected on Switch 4, port 6, average latency 325ms. 2025-01-05 19:25:14: Latency spike detected on Switch 1, port 2, average latency 350ms. 2025-01-05 20:45:31: Latency spike detected on Switch 3, port 13, average latency 360ms. 2025-01-05 21:50:42: Latency spike detected on Switch 4, port 9, average latency 330ms. 2025-01-05 22:15:55: Latency spike detected on Switch 1, port 8, average latency 370ms. 2025-01-05 23:30:20: Latency spike detected on Switch 3, port 6, average latency 380ms. Port Errors: Numerous port errors have been recorded, including CRC errors and late collisions. These errors point to aging hardware components that may soon lead to critical failures. Examples from the logs include: 2024-12-12 14:50:19: CRC error on Switch 1, port 9, 220 errors recorded. 2024-12-16 19:35:41: Late collision on Switch 3, port 10, 40 collisions recorded. 2024-12-22 08:55:10: CRC error on Switch 4, port 2, 250 errors recorded. 2024-12-28 13:45:23: Late collision on Switch 1, port 5, 55 collisions recorded. 2025-01-01 16:32:49: CRC error on Switch 3, port 14, 230 errors recorded. 2025-01-03 09:18:35: Late collision on Switch 4, port 12, 60 collisions recorded. 2025-01-04 14:45:33: CRC error on Switch 1, port 11, 275 errors recorded. 2025-01-05 09:30:18: Late collision on Switch 3, port 4, 70 collisions recorded. 2025-01-05 10:55:48: CRC error on Switch 4, port 7, 280 errors recorded. 2025-01-05 12:25:42: CRC error on Switch 1, port 8, 290 errors recorded. 2025-01-05 14:45:20: Late collision on Switch 3, port 9, 80 collisions recorded. 2025-01-05 16:15:30: CRC error on Switch 4, port 6, 300 errors recorded. 2025-01-05 18:30:05: Late collision on Switch 1, port 14, 95 collisions recorded. 2025-01-05 20:00:10: CRC error on Switch 3, port 11, 310 errors recorded. 2025-01-05 22:05:45: Late collision on Switch 4, port 10, 100 collisions recorded. Limited Support and Updates: Given the age of the switches, firmware updates and security patches from DELL have either slowed down or ceased entirely. This poses a potential security risk as vulnerabilities may go unaddressed. Age of Current Equipment The DELL switches currently in operation are 12 years old. While they have provided reliable service over the years, their age is now becoming a liability. Networking hardware typically has a lifecycle of 5-7 years, after which performance degradation, increased failure rates, and reduced manufacturer support become significant concerns. Conclusion and Next Steps Given the evidence provided by the logs and the inherent risks of continuing to rely on 12-year-old switches, I strongly recommend proceeding with the replacement of the current equipment. Ticket: https://help.sccn.co.il/helpdesk/tickets/11584 Best Regards Sharon Carciente Chief executive officer at SCCN Ltd. P 08-970-8022 E sharonc@sccn.co.il W www.sccn.co.il   

טיוטת תשובה (ניתן לערוך)

מקורות מה-KB

נימוק של המודל

The ticket provides minimal information - just 'Network latency check' without any details about the issue, affected systems, or symptoms. The KB snippets don't contain relevant information about network latency diagnostics (they mention switch issues, RDP connections, and email setup, but not latency testing). Since there's insufficient information to provide a specific solution, I'm asking for clarification and requesting basic diagnostic information (which computer(s), error messages, timing, connection type) plus a simple ping test that can help initial troubleshooting. This follows the principle of not inventing information and asking for what's missing.