Reporting Network ProblemsLes Cottrell. Last Update: August 21, 2010SLAC Computer Services (SCS) | Network Group | Computer Networking |
Related sites WAN Case Studies Computing Outages Comp-out mailing list Diagnostic Steps Reporting Problems Request Tracker(RT)* |
For SLAC problems, typically the user will report the problem to their departmental admin. The departmental admin will do triage to gather information and decide who should be contacted. All network problems must report the coordinates (phone and email) of the contacts, the time and date of the start of the problem occurence, the name and IP addresses of the hosts involved (server and client), the user name (need for Visitor subnet registrations), connection kind (wireless, DSL/cable at home, modem, wired connection), if on SLAC wireless where on site the problem occurred, the application that was having problems, the Operating System of the users's computer, ping and traceroute* output from your host to the server, a description of the problem's symptoms, and if possible a Network Diagnostic Tool (NDT) report see here for a web accessible based tool for SLAC only users and here for offsite users. There is also a Linux command line version available from SLAC Linux hosts by running ndt-client -n nettest5. |
30cottrell@pinger:~>traceroute 134.79.112.24 traceroute to 134.79.112.24 (134.79.112.24), 30 hops max, 38 byte packets 1 rtr-iepm-test (134.79.243.1) 0.413 ms 0.552 ms 0.292 ms 2 rtr-core1-p2p-iepm (134.79.252.5) 0.403 ms 0.453 ms 0.431 ms 3 rtr-block-p2p-core1 (134.79.252.30) 1.417 ms 1.457 ms 1.434 ms 4 * * *