Network Warrior
Gary A. Donahue
Language: English
Pages: 788
ISBN: 1449387861
Format: PDF / Kindle (mobi) / ePub
Pick up where certification exams leave off. With this practical, in-depth guide to the entire network infrastructure, you’ll learn how to deal with real Cisco networks, rather than the hypothetical situations presented on exams like the CCNA. Network Warrior takes you step by step through the world of routers, switches, firewalls, and other technologies based on the author's extensive field experience. You'll find new content for MPLS, IPv6, VoIP, and wireless in this completely revised second edition, along with examples of Cisco Nexus 5000 and 7000 switches throughout.
Topics include:
- An in-depth view of routers and routing
- Switching, using Cisco Catalyst and Nexus switches as examples
- SOHO VoIP and SOHO wireless access point design and configuration
- Introduction to IPv6 with configuration examples
- Telecom technologies in the data-networking world, including T1, DS3, frame relay, and MPLS
- Security, firewall theory, and configuration, as well as ACL and authentication
- Quality of Service (QoS), with an emphasis on low-latency queuing (LLQ)
- IP address allocation, Network Time Protocol (NTP), and device failures
octet separated by a colon or hyphen (CatOS uses a hyphen as the delimiter when displaying MAC addresses in hexadecimal). Some systems may also display MAC addresses in decimal, while others use hexadecimal. The output from the preceding command shows that port Gi3/22 is where our server is connected. In NX-OS, the command is the same as IOS, though the interface names reflect the Nexus hardware (in this case, a 5010 with a 2148T configured as FEX100): NX-5K-1(config-if)# sho mac-address-table
to communicate with each neighbor manually. The Internet Assigned Numbers Authority (IANA) shows all multicast addresses in use at http://www.iana.org/assignments/multicast-addresses. Some of the more common multicast addresses include: 224.0.0.0 Base Address (Reserved) 224.0.0.1 All Systems on this Subnet 224.0.0.2 All Routers on this Subnet 224.0.0.4 DVMRP Routers 224.0.0.5 OSPFIGP OSPFIGP All Routers 224.0.0.6 OSPFIGP OSPFIGP Designated Routers 224.0.0.9 RIP2 Routers 224.0.0.10 IGRP Routers
RIP, but not EIGRP. To dynamically route between an EIGRP router and a RIP-only firewall, you must redistribute between RIP and EIGRP on the router. The best rule to remember when redistributing is to keep it simple. It’s easy to get confused when routes are being sent back and forth between routing protocols. Keeping the design as simple as possible will help keep the network manageable. You can create some pretty interesting problems when redistribution isn’t working properly. The simpler the
about your probable mistake: R3(config-router)#redistribute eigrp 100 metric 100 % Only classful networks will be redistributed Mutual Redistribution The term mutual redistribution refers to when a router redistributes between two routing protocols in both directions instead of just one. Often, we redistribute because there is a device or entity we wish to connect with that doesn’t support the routing protocol we have chosen to use. We need to share routes between protocols, but, if you will,
broader areas, and are usually used to connect LANs. WANs can span the globe, and there’s nothing that says they couldn’t go farther. MANs are common in areas where technology like Metropolitan Area Ethernet is possible; they typically connect LANs within a given geographical region such as a city or town. A CAN is similar to a MAN, but is limited to a campus (a campus is usually defined as a group of buildings under the control of one entity, such as a college or a single company). One could