Network troubleshooting tools
Over the years, thousands of tools have been developed for debugging TCP/IP networks. They range from very specialized tools that do one particular task, to generalized suites that do just about everything except replace bad Ethernet cables. Even better, many of them are absolutely free. There'...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Beijing ; Sebastopol, California :
O'Reilly
2001.
|
| Edición: | First edition |
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627190206719 |
Tabla de Contenidos:
- Network Troubleshooting Tools; Organization; Conventions; Acknowledgments; 1. Network Management and Troubleshooting; 1.2. Need for Troubleshooting Tools; 1.3. Troubleshooting and Management; 1.3.2. Management Practices; 1.3.2.2. Ego management; 1.3.2.3. Legal and ethical considerations; 1.3.2.4. Economic considerations; 2. Host Configurations; 2.1.2. top; 2.1.3. netstat; 2.1.4. lsof; 2.1.5. ifconfig; 2.1.6. arp; 2.1.7. Scanning Tools; 2.2. System Configuration Files; 2.2.2. Configuration Programs; 2.2.3. Kernel; 2.2.4. Startup Files and Scripts; 2.2.5. Other Files; 2.2.5.2. Security files
- 2.2.5.3. Log files2.3. Microsoft Windows; 3. Connectivity Testing; 3.1.2. Maintaining Existing Cabling; 3.1.3. Testing Cabling; 3.1.3.2. Cable testers; 3.1.3.3. Other cable tests; 3.2. Testing Adapters; 3.3. Software Testing with ping; 3.3.2. How ping Works; 3.3.2.2. Interpreting results; 3.3.2.3. Options; 3.3.2.4. Using ping; 3.3.3. Problems with ping; 3.3.3.2. Smurf Attacks; 3.3.3.3. Ping of Death; 3.3.3.4. Other problems; 3.3.4. Alternatives to ping; 3.3.4.2. echoping; 3.3.4.3. arping; 3.3.4.4. Other programs; 3.4. Microsoft Windows; 4. Path Characteristics
- 4.1.2. Complications with traceroute4.2. Path Performance; 4.2.2. Bandwidth Measurements; 4.2.2.2. pathchar; 4.2.2.3. bing; 4.2.2.4. Packet pair software; 4.2.3. Throughput Measurements; 4.2.3.2. netperf; 4.2.3.3. iperf; 4.2.3.4. Other related tools; 4.2.4. Traffic Measurements with netstat; 4.3. Microsoft Windows; 5. Packet Capture; 5.2. Access to Traffic; 5.3. Capturing Data; 5.4. tcpdump; 5.4.2. tcpdump Options; 5.4.2.2. Controlling how information is displayed; 5.4.2.3. Controlling what&s displayed; 5.4.2.4. Filtering; 5.4.2.4.2. Protocol and port filtering.
- 5.4.2.4.3. Packet characteristics.5.4.2.4.4. Compound filters.; 5.5. Analysis Tools; 5.5.2. tcpdpriv; 5.5.3. tcpflow; 5.5.4. tcp-reduce; 5.5.5. tcpshow; 5.5.6. tcpslice; 5.5.7. tcptrace; 5.5.8. trafshow; 5.5.9. xplot; 5.5.10. Other Packet Capture Programs; 5.6. Packet Analyzers; 5.6.1.2. Display filters; 5.7. Dark Side of Packet Capture; 5.7.2. Protecting Yourself; 5.8. Microsoft Windows; 6. Device Discovery and Mapping; 6.1.2. Discovery and Mapping Tools; 6.1.3. Selecting a Product; 6.2. Device Discovery; 6.2.2. nmap; 6.2.3. arpwatch; 6.3. Device Identification; 6.3.2. queso
- 6.3.3. nmap Revisited6.4. Scripts; 6.5. Mapping or Diagramming; 6.5.1.2. Autodiscovery with tkined; 6.6. Politics and Security; 6.7. Microsoft Windows; 6.7.2. Other Tools for Windows; 7. Device Monitoring with SNMP; 7.2. SNMP-Based Management Tools; 7.2.1.2. Configuration and options; 7.2.1.3. snmpgetnext, snmpwalk, and snmptable; 7.2.1.4. snmpset; 7.2.1.5. snmptranslate; 7.2.1.6. snmpnetstat; 7.2.1.7. snmpstatus; 7.2.1.8. Agents and traps; 7.2.2. scotty; 7.2.3. tkined; 7.2.3.2. SNMP traps; 7.2.3.3. Examining MIBs; 7.2.3.4. Monitoring SNMP objects; 7.2.3.5. Other commands; 7.2.3.6. Caveats
- 7.3. Non-SNMP Approaches
