Saturday, March 28, 2009

EIGRP

Enhanced Interior Gateway Routing Protocol (EIGRP) is a Cisco proprietary classless routing protocol that uses a complex metric based on bandwidth and delay. The following are some features of EIGRP:

Fast convergence
Support for VLSM
Partial updates conserve network bandwidth
Support for IP, AppleTalk, and IPX
Support for all layer 2 (data link layer) protocols and topologies
Sophisticated metric that supports unequal-metric proportional load-balancing
Use of multicasts (and unicasts where appropriate) instead of broadcasts
Support for authentication


EIGRP Overview
EIGRP’s function is controlled by four key technologies:

Neighbor discovery and maintenance—Uses periodic hello messages
The Reliable Transport Protocol (RTP)—Controls sending, tracking, and acknowledging EIGRP messages
Diffusing Update Algorithm (DUAL)—Determines the best loopfree route
Protocol-independent modules (PDM)—Modules are “plug-ins” for IP, IPX, and AppleTalk versions of EIGRP

EIGRP uses three tables:
The neighbor table is built from EIGRP hellos and used for reliable delivery.
The topology table contains EIGRP routing information for best paths and loop-free alternatives.
EIGRP places best routes from its topology table into the common routing table.


Neighbor Discovery and Route Exchange

When EIGRP first starts, it uses hellos to build a neighbor table.
Neighbors are directly attached routers that have a matching AS
number and k values (the timers don’t have to agree). The process of
neighbor discovery and route exchange between two EIGRP routers is
as follows:

Step 1. Router A sends out a hello.
Step 2. Router B sends back a hello and an update. The update
contains routing information.
Step 3. Router A acknowledges the update.
Step 4. Router A sends its update.
Step 5. Router B acknowledges.

Once two routers are EIGRP neighbors, they use hellos between them as keepalives. Additional route information is sent only if a route is lost or a new route is discovered. A neighbor is considered lost if no hello is received within three hello periods (called the hold time). The default
hello/hold timers are as follows:

5 seconds/15 seconds for multipoint circuits with bandwidth greater than T1 and for point-to-point media
60 seconds/180 seconds for multipoint circuits with bandwidth less than or equal to T1

The exchange process can be viewed using debug ip eigrp packets,
and the update process can be seen using debug ip eigrp. The neighbor
table can be seen with the command show ip eigrp neighbors.


Diffusing Update Algorithm (DUAL)

DUAL is the algorithm used by EIGRP to choose best paths by looking at AD and FD. The path with the lowest metric is called the successor path. EIGRP paths with a lower AD than the FD of the successor path are guaranteed loop-free and called feasible successors. If the successor path is lost, the router can use the feasible successor immediately without risk of loops.

After the router has chosen a path to a network, it is passive for that route. If a successor path is lost and no feasible successor is identified, the router sends out queries on all interfaces in an attempt to identify an alternate path. It is active for that route. No successor can be chosen until the router receives a reply to all queries. If a reply is missing for three minutes, the router becomes stuck in active (SIA). In that case, it resets the neighbor relationship with the neighbor that did not reply.


Route Selection Example

The following diagrams show EIGRP advertisements to R3 and R5 about a destination network connected to R1. In Figure 2-3, R5 chooses R4 as the successor path because it offers the lowest feasible distance. The AD from R3 indicates that passing traffic through R3 will not loop, so R3 is a feasible successor.
How does R3 choose its path? Figure 2-4 shows the path selection process for R3.
R1 will be its successor because it has the lowest metric. However, no feasible successor exists because R2’s AD is greater than the successor path metric. If the direct path to R1 is lost, then R3 has to query its neighbors to discover an alternative path. It must wait to hear back from R2 and R5, and will ultimately decide that R2 is the new successor.

Basic EIGRP Configuration

When setting up EIGRP, an autonomous system number must be used (7 is used in the example). Autonomous system numbers must agree for two routers to form a neighbor relationship and to exchange routes.

Router(config)#router eigrp 7
Router(config-router)#network 192.168.1.0

The wildcard mask option can be used with the network command to more precisely identify EIGRP interfaces. For instance, if a router has two interfaces—fa0/0 (192.168.1.1/27) and fa0/1 (192.168.1.33/27)—and
needs to run only EIGRP on fa0/0, the following command can be used:

Router(config-router)#network 192.168.1.0 0.0.0.1

In this command, a wildcard mask of 0.0.0.1 matches only two IP addresses in network 192.168.1.0–192.168.1.0 and 192.168.1.1. Therefore, only interface fa0/0 is included in EIGRP routing.


Creating an EIGRP Default Route
Figure 2-5 shows a simple two-router network. You can configure EIGRP on R1 to advertise a default route to R3 in three ways:

R1 can specify a default network:

R1(config)#ip default-network 10.0.0.0

R3 now sees a default network with a next hop of R1.



Produce a summary route:

R1(config)#interface s0/0/0
R1(config-if)#ip summary-address eigrp 7 0.0.0.0 0.0.0.0

This passes a default route from R1 out its serial0 interface toward
R3.


Create a static default route and then include network 0.0.0.0 in EIGRP:
R1(config)#ip route 0.0.0.0 0.0.0.0 10.1.1.2
R1(config)#router eigrp 7
R1(config-router)#network 0.0.0.0


Troubleshooting EIGRP

The most straightforward way to troubleshoot EIGRP is to inspect the routing table—show ip route. To filter the routing table and show only the routes learned from EIGRP, use the show ip route eigrp command. The show ip protocols command verifies autonomous system, timer values, identified networks, and EIGRP neighbors (routing information
sources).

The command show ip eigrp topology shows the EIGRP topology table and identifies successors and feasible successors. Use show ip eigrp neighbors to verify that the correct routers are neighbors, and use show ip eigrp traffic to show the amount and types of EIGRP messages.

Tuesday, March 24, 2009

IP Routing Protocols

Routing protocols are used to pass information about the structure of the network between routers. Cisco routers support the following IP routing protocols RIP (versions 1 and 2), IGRP, EIGRP, IS-IS, OSPF, and BGP. This section compares routing protocols and calls out key
differences between them.

Administrative Distance
Cisco routers are capable of supporting several IP routing protocols concurrently. When identical prefixes are discovered from two or more separate sources, Administrative Distance (AD) is used to discriminate between the paths. AD is a poor choice of words; trustworthiness is a better name. Routers use paths with the lower AD. The following figure lists the default values for various routing protocols. Of course, there are several ways to change AD for a routing protocol or for a specific route.


Building the Routing Table

The router builds a routing table by ruling out invalid routes and considering the remaining advertisements. The procedure is:

1. For each route received, verify the next hop. If invalid, discard the route.
2. If multiple, valid routes are advertised by a routing protocol, choose the lowest metric.
3. Routes are identical if they advertise the same prefix and mask, so 192.168.0.0/16 and 192.168.0.0/24 are separate paths and are each placed into the routing table.
4. If more than one specific valid route is advertised by different routing protocols, choose the path with the lowest AD.

Comparing Routing Protocols
Two things should always be considered in choosing a routing protocol: fast convergence speed and support for VLSM. EIGRP, OSPF, and IS-IS meet these criteria. Although all three meet the minimum, there are still important distinctions, as described below:

EIGRP is proprietary, but it is simple to configure and support.
OSPF is an open standard, but it is difficult to implement and support.
There are few books on IS-IS and even fewer engineers with experience who use it. IS-IS is therefore uncommon.

Enterprise Composite Network Model

The Enterprise Composite Model (see Figure 1-3) is broken into three large sections:
Enterprise Campus—Switches that make up a LAN
Enterprise Edge—The portion of the enterprise network connected to the larger world.
Service Provider Edge—The different public networks that are attached

The Enterprise Composite Model

The Enterprise Edge, shown in the following figure, details the connections from the campus to the WAN and includes:
E-commerce
Internet connectivity
Remote access
WAN

The Service Provider Edge is just a list of the public networks that facilitate wide-area connectivity and include:
Internet service provider (ISP)
Public switched telephone network (PSTN)
Frame Relay, ATM, and PPP

The Evolving Network Model


Hierarchical Design Model

Three-Layer Network Design
The layers break a network in the following way:
Access layer—End stations attach to the network using low-cost devices.
Distribution layer—Intermediate devices apply policies.
Route summarization
Policies applied, such as:
Route selection
Access lists
Quality of Service (QoS)

Core layer—The backbone that provides a high-speed path between distribution elements.
Distribution devices are interconnected.
High speed (there is a lot of traffic).
No policies (it is tough enough to keep up).

Problems with the Hierarchical Design Model:
Where do wireless devices fit in?
How should Internet access and security be provisioned?
How do you account for remote access, such as dial-up or VPN?
Where should workgroup and enterprise services be located?