Features
- Cover Type: Hard Cover with 608 pages
- Published by: Wiley
- Edition: 1st Edition July 19, 2002
- Written in: English
- ISBN 10 Number: 0471210137
- ISBN 13 Number: 978-0471210139
-
Book Dimensions:
9 x 7.5 x 1.4 inches
- Weighs: 2.2 pounds
Product Description
All network designers and administrators want their campus LANs to run efficiently. This book provides tips and techniques for using protocol analyzers and other tools to recognize problems for both Cisco and multiprotocol traffic patterns.
* Focuses on troubleshooting problems that arise from the Cisco routers inter-operating with many other network protocols
* Covers both legacy and cutting-edge technologies
* Authors are respected in the field for their teaching and training development skills in network troubleshooting
Back Cover Copy
Essential information on the successful troubleshooting of complex campus networks
Just as a used car can seem to be in good condition to an inexperienced consumer, a network can also feign an appearance that all is running smoothly to the unskilled user. Upon closer examination, though, a true expert can discern when a network is a lemon. Network engineers, administrators, and technicians who manage Cisco and multivendor campus networks know how crucial it is to determine when a network has serious problems and what to do about them, particularly when that network spans buildings and consists of wired and wireless technologies. Known as campus networks, these networks connect tens, hundreds, or even thousands of users at businesses, universities, nonprofit organizations, and government agencies. This informative book teaches the use of Cisco and industry-standard trouble-shooting tools to analyze, diagnose, and fix problems on modern switched and routed networks with information that is based on many years of analyzing real-world, diverse, and complex networks. Written by a pair of authors with over forty years of networking experience between them, this book discusses:
* Techniques for using protocol analyzers, such as the WildPackets EtherPeek and AiroPeek products, to recognize and isolate faulty network behavior
* The OSI Reference Model and the Internet Control Message Protocol (ICMP)
* How Ethernet and 802.11 wireless networks work and how to troubleshoot them when they don't
* Spanning Tree Protocol, which is used on bridged and switched networks, and the configuration and troubleshooting of VLANs
* IP addressing, IP routing protocols, TCP, and an overview of upper-layer TCP/IP protocols
* Troubleshooting for Novell NetWare, AppleTalk, and Windows networking
* WAN technology and trouble-shooting from the perspective of the LAN-oriented network engineer
Reader ReviewsI'm sad I waited so long to read this excellent book. "Troubleshooting Campus Networks" (TCN) was published in Jul 2002, and it belongs on every network administrator's shelf -- now! This is the best networking book since Scott Haugdahl's "Network Analysis and Troubleshooting" and Eric Hall's "Internet Core Protocols." TCN will truly test your networking knowledge; you'll quickly validate the truth and discard the fiction. So many books discuss networks, but somehow distort subtle points. Authors Oppenheimer and Bardwell know their material inside-out and explain key points in clear, concise prose. Ever hear of the "37% utilization rule for Ethernet?" It's false. Think that TCP sequence numbers count packets? Wrong -- they count bytes of data. And why are sequence numbers seemingly "off by one?" Look at the difference between ordinal and cardinal numbers, described in ch. 9. TCN displays an uncanny ability to include just the information that is needed. "Reversible half-ASCII," which accounts for odd-looking NetBIOS traces, appears in ch. 12. The sections on Windows networking are first-rate, with helpful comparisons of NetBIOS with IPX, TCP, and NetBEUI. Even theoretical but damaging attack methods, like corrupting Hot Standby Router Protocol messages (ch. 8), are illuminated. I have two complaints. I would have liked more attention paid to the mechanics of analyzing traffic, including the use of taps. Also, the Windows chapter seemed to end abruptly, just when the dynamics of Windows 2000 networking and port 445 should have appeared. TCN is designed to educate protocol analysts. People with this skill set can administer LANs, analyzer network-based IDS traffic, and deploy network infrastructure. I thank the authors for their efforts and look forward to their next endeavor.
Search for books at
