My Account|View Cart|Wishlist|Checkout|About Us|Contact Us

Posts Tagged ‘Add new tag’

CCNA Certification: EIGRP 640-802 Concepts

Tuesday, January 19th, 2010 by CiscoKits

EIGRP Concepts

In this lesson, we will introduce you to EIGRP, as requested by the Cisco CCNA certification exam.

Enhanced Interior Gateway Routing Protocol (EIGRP) is a Cisco proprietary, distance vector, classless routing protocol used for routing inside a network (IGP). In addition to other distance vector routing protocol, like RIP and IGRP, EIGRP has some unique features like: Reliable Transport Protocol (RTP), which provides reliable and unreliable delivery of EIGRP packets, Bounded Updates, Diffusing Update Algorithm (DUAL) to guarantee loop-free paths and backup paths, Neighbor and Topology Tables. EIGRP can operate as a classful routing protocol, as well as a classless one.

Unlike other distance vector routing protocols, EIGRP does not send periodic updates, so the route entries to not age out, instead, EIGRP uses a lightweight Hello protocol to monitor connection status with its neighbors.

Every EIGRP packet includes the EIGRP Packet Header. The important fields in this header are the Opcode field and the Autonomous System Number field. The Opcode specifies the packet type, which can be Update, Query, Reply and Hello. The Autonomous System (AS) Number specifies the EIGRP routing process. Unlike RIP, a Cisco router can run multiple instances of EIGRP. The AS number is used to track multiple instances of EIGRP.

Reliable Transport Protocol (RTP) is used by EIGRP for the delivery and reception of EIGRP packets. RTP sends packets to either unicast address or the reserved multicast address 224.0.0.10.

As we already told you, EIGRP uses five different packet types:

·         Hello packets – are used to discover neighbors and form adjacencies with them. These packets are multicast and use unreliable delivery and are sent typically every 5 seconds.

·         Update packets – are used to propagate the routing information. Update packets are sent only when a change in the topology occurs and only to those routers who require them. EIGRP update packets use reliable delivery and are sent to the multicast address when multiple routers require them, and to the unicast address when they are required by a single router.

·         Acknowledgement (ACK) packets – are sent when reliable delivery is used. They contain a nonzero acknowledgement number and are always sent to the unicast address.

·         Query and Replay packets – are used by DUAL when searching for networks and other tasks. Queries are sent to the multicast address and use reliable delivery, while replies are sent as unicast and they are also using reliable delivery.

In EIGRP, the default administrative distance (AD) is 170 when used as an Exterior Gateway Protocol (EGP), 90 when used as an IGP and 5 for EIGRP summary routes.

EIGRP also supports authentication to ensure the information transmitted over the network is authentic and from a trusted source.

To better understand EIGRP, we will use the following topology to configure an EIGRP network.

eigrp 

First, let’s configure the IP addresses on the interfaces of the routers.

R0(config)#int Fa0/0
R0(config-if)#ip addr 172.16.1.1 255.255.255.0
R0(config-if)#no shutdown
R0(config-if)#int Fa0/1
R0(config-if)#ip addr 192.168.1.1 255.255.255.0
R0(config-if)#no shutdown

R1(config)#int Fa0/0
R1(config-if)#ip addr 172.16.1.2 255.255.255.0
R1(config-if)#no shutdown
R1(config-if)#int Fa0/1
R1(config-if)#ip addr 192.168.2.1 255.255.255.0
R1(config-if)#no shutdown

R2(config)#int Fa0/0
R2(config-if)#ip addr 192.168.1.2 255.255.255.0
R2(config-if)#no shutdown

R3(config)#int Fa0/0
R3(config-if)#ip addr 192.168.2.2 255.255.255.0
R3(config-if)#no shutdown

Now, let’s enable EIGRP and specify what networks to advertise to our neighbors. We will use EIGRP autonomous system (AS) 1.

R0(config)#router eigrp 1
R0(config-router)#network 172.16.1.0 0.0.0.255
R0(config-router)#network 192.168.1.0

Optionally, in EIGRP, you can specify the wildcard bits when you chose to advertise a network. By default, when using the network command and a classful network address such as 172.16.1.0, all interfaces will be enabled for EIGRP. Although this is not our case, if you don’t want to enable all of them, you must specify the wildcard mask. To calculate the wildcard mask, you must substract the subnet mask from 255.255.255.255. For example, the wildcard mask for 255.255.255.252 is 255.255.255.255 – 255.255.255.252 = 0.0.0.3.

Let’s continue to configure the other routers now.

R1(config-router)#router eigrp 1
R1(config-router)#network 172.16.1.0
R1(config-router)#
*Mar  1 00:14:27.267: %DUAL-5-NBRCHANG
E: IP-EIGRP(0) 1: Neighbor 172.16.1.1 (FastEthernet0/0) is up: new adjacency
R1(config-router)#network 192.168.2.0

R2(config)#router eigrp 1
R2(config-router)#network 192.168.1.0
R2(config-router)#
*Mar  1 00:16:17.475: %DUAL-5-NBRCHANG
E: IP-EIGRP(0) 1: Neighbor 192.168.1.1 (FastEthernet0/0) is up: new adjacency

R3(config)#router eigrp 1
R3(config-router)#network 192.168.2.0
R3(config-router)#
*Mar  1 00:17:02.279: %DUAL-5-NBRCHANG
E: IP-EIGRP(0) 1: Neighbor 192.168.2.1 (FastEthernet0/0) is up: new adjacency

Now, let’s check the routing table.

R3#show ip route
Codes: C – connected, S – static, R – RIP, M – mobile, B –
BGP
       D –
EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area
       N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2
      
E1 – OSPF external type 1, E2 – OSPF external type 2
       i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2
       ia – IS-IS inter area, * – candidate default, U – per-user static route
       o – ODR, P – periodic downloaded static route

Gateway of last resort is not set


D    172.16.0.0/16 [90/307200] via 192.168.2.1,
00:00:35, FastEthernet0/0
D    192.168.1.0/24 [90/332800] via 192.168.2.1,
00:00:35, FastEthernet0/0
C    192.168.2.0/24 is directly connected, FastEthernet0/0

As you can see, the routing table is already populated with the routes. Let’s check the neighbors.

R0#show ip eigrp neighbors
IP-
EIGRP neighbors for process 1
H   Address                 Interface       Hold Uptime   SR
TT   RTO  Q  Seq
                                            (sec)         (ms)       Cnt Num
1   192.168.1.2             Fa0/1             10
00:04:27    8   200  0  4
0   172.16.1.2              Fa0/0             13
00:06:17    6   300  0  9

The fields of this command show you the following:

·         H column – lists the neighbors in the order they were learned.

·         Address – the IP address of the neighbor.

·         Interface – the local interface on which the Hello packet was received.

·         Hold – the current hold time. Every time a Hello packet is received, this value is reset to the maximum hold time for that interface and then counts down to zero. If zero is reached, the neighbor is considered down.

·         Uptime – amount of time since the neighbor was added to the neighbor table

·         SRTT (Smooth Round Trip Timer) and RT0 (Retransmit Interval ) – used by RTP to manage reliable EIGRP packets.

·         Queue Count – should always be zero, else EIGRP packets are waiting to be sent.

·         Sequence Number – used to track updates, queries and reply packets.

As with the other routing protocols, you can use the show ip protocols command to check detailed information about your routing protocols.

R0#show ip protocols
Routing Protocol is “eigrp 1
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Default networks flagged in outgoing updates
  Default networks accepted from incoming updates
 
EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
 
EIGRP maximum hopcount 100
 
EIGRP maximum metric variance 1
  Redistributing: eigrp 1
 
EIGRP NSF-aware route hold timer is 240s
  Automatic network summarization is in effect
  Automatic address summarization:
    192.168.1.0/24 for Fast
Ethernet0/0
    172.16.0.0/16 for Fast
Ethernet0/1
      Summarizing with metric 281600
  Maximum path: 4
  Routing for Networks:
    172.16.1.0/24
    192.168.1.0
  Routing Information Sources:
    Gateway         Distance      Last Update
    (this router)         90      00:16:06
    172.16.1.2            90      00:11:56
  Distance: internal 90 external 170

When automatic summarization is enabled or at least one subnet was learned via EIGRP, EIGRP includes a summary route. Null0 is the interface used for summary routes. This is a “virtual” interface used only for advertising purposes.

R0#show ip route
Codes: C – connected, S – static, R – RIP, M – mobile, B –
BGP
       D –
EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area
       N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2
      
E1 – OSPF external type 1, E2 – OSPF external type 2
       i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2
       ia – IS-IS inter area, * – candidate default, U – per-user static route
       o – ODR, P – periodic downloaded static route


Gateway of last resort is not set

     172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks
D       172.16.0.0/16 is a summary,
00:37:40, Null0
C       172.16.1.0/24 is directly connected, Fast
Ethernet0/0
C    192.168.1.0/24 is directly connected, Fast
Ethernet0/1
D    192.168.2.0/24 [90/307200] via 172.16.1.2,
00:33:30, FastEthernet0/0

To calculate the preferred path on a network, EIGRP uses the following values in its composite metric:

·         Bandwidth

·         Delay

·         Reliability

·         Load

The default composite formula is: metric = [K1 * bandwidth + K3*delay]

By default, K1 and K3 are set to 1, and K2, K4 and K5 are set to 0. These values can be changed with metric weights tos k1 k2 k3 k4 k5 EIGRP router configuration command.

To find out the values used by EIGRP for the bandwidth, delay, reliability and load use the show interface interface interface-number command.

R0#show interface Fa0/0
Fast
Ethernet0/0 is up, line protocol is up
  Hardware is Gt96k F
E, address is c400.039f.0000 (bia c400.039f.0000)
  Internet address is 172.16.1.1/24
  MTU 1500 bytes, BW 10000 Kbit/sec, DLY 1000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
 
Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Half-duplex, 10Mb/s, 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00

When you use Serial interfaces, the default bandwidth value may not match your real bandwidth which may cause EIGRP to not work properly. In this case, you have to manually configure the bandwidth value for your interface. Although, this is not our case, because we use FastEthernet interface, we will demonstrate you how to accomplish this, with the bandwidth kilobits interface configuration command.

R0(config)#interface Serial 0/0/0
R0(config-if)#bandwidth 1024

EIGRP is one of the most used Interior Gateway Protocols (IGP) used these days. In your preparation for your CCNA exam, you must know the basics of EIGRP and we hope you found this article useful for achieving the basic knowledge required for the CCNA certification exam. Remember that practice is best way to prepare for the CCNA exam, and we can provide you with many training resources, including labs prepared specially for the exam on which you can setup your own EIGRP enabled topologies.

CCNA Certification 640-802: Inter-VLAN Routing

Tuesday, January 5th, 2010 by CiscoKits

Inter-VLAN Routing

Welcome to a new lesson from the Cisco CCNA exam preparation series. In this lesson, we will talk about Inter-VLAN routing and different methods to accomplish this. Inter-VLAN Routing is used to allow devices on separate VLANs communicate with each other.

Inter-VLAN Routing is the process of routing traffic between VLANs in a network. As we explained to you in the previous lesson about VLANs, VLANs are used to create logical networks from a physical network, isolating hosts from one VLAN from the ones in other VLANs. Most of the times, although you want to create different broadcast domain in your network by creating more logical networks, you want the hosts from those networks to communicate with each other, even if they are not belonging to the same VLAN.

A host belonging to a VLAN attached on a specific physical port, for example VLAN 10 in port FastEthernet0/10 is usually not able to communicate to a host attached to another VLAN, for example VLAN11 attached to port FastEthernet0/11. They belong to different networks, different broadcast domains and switches do not know how to forward packets from one network to another. The process of forwarding packets from a network to another is called routing and you must use a router to accomplish this.

In classic networks that are using multiple VLANs, routing is performed by connecting multiple physical interfaces on the router to multiple physical interfaces on the switch. The switch ports are connected to the router in access mode, and a different static VLAN is assigned to every interface. An access mode switch port can belong to only one VLAN and is usually used to connect to an end user device.

Usually, this is not a desired behavior because you end up using too many physical interfaces, and sooner or later you will run out of interfaces. A typical switch can have up to 48 ports. This means, you can use that switch to route traffic between VLANs for up to 48 VLANs. In smaller networks this may be enough, but in larger enterprise networks, 48 VLANs may not be enough.

Router-on-a-stick ” is a type of router configuration in which you are able to use a single physical interface to route traffic between multiple VLANs. The router interface is configured as a trunk link and is connected to a trunk switch port. The router is accepting the tagged traffic on the trunk interface and routes it internally using subinterfaces. Trunk links are able to accept multiple VLANs on one physical interface. Switches are able to recognize the VLAN used for a specific packet through the use of encapsulation protocols that encapsulate or tag the frames. The protocols used are 802.1Q or Cisco’s proprietary Inter-Switch Link (ISL). To find out more about these encapsulation protocols check the Trunking Concepts lessons from our Cisco CCNA exam preparation series.

Subinterfaces are virtual interfaces associated with a single physical interface. These subinterfaces have their own IP address and VLAN assignment to be able to operate on a specific VLAN.

However, if your switch is capable of doing Layer 3 functions, you don’t need a router anymore. The switch will handle the Inter-VLAN routing decisions too. These switches are called multilayer switches .

The router acts as a Gateway for devices on a VLAN. The subinterface configured for a particular VLAN has an IP assigned from the range of IPs used in that VLAN. The other devices on the VLAN are sending packets for devices in other VLANs through the router. The router then, takes the routing decision and sends the packet to the destination.

Usually, when you configure a router, you assign IPs to interfaces, and once the IPs are assigned, the routing table shows how to reach the networks those IPs are part of.

Router(config)#interface Fa0/0
Router(config-if)#ip address 172.16.10.1 255.255.255.0
Router(config-if)#no shutdown
Router(config-if)#interface Fa0/1
Router(config-if)#ip address 172.16.30.1 255.255.255.0
Router(config-if)#no shutdown
Router(config-if)#end
Router#show ip route
Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP
D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area
N1 – OSPF NSSA external type 1, N2 – O
SPF NSSA external type 2
E1 – OSPF external type 1, E2 – OSPF external type 2
i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2
ia – IS-IS inter area, * – candidate default, U – per-user static route
o – ODR, P – periodic downloaded static route

Gateway of last resort is not set

172.16.0.0/24 is subnetted, 2 subnets
C 172.16.10.0/24 is directly connected, FastEthernet0/1
C 172.16.30.0/24 is directly connected, FastEthernet0/1

As you can see, the only chance to route traffic between those two networks is to connect both interfaces to the switch. This could be a solution if you have a small number of VLANs on your network and you are sure your network will never evolve, but if you have for example 120 VLANs what would you do?

The solution is to use subinterfaces. When you use subinterfaces,

Router(config)#interface Fa0/0.10
Router(config-if)#encapsulation dot1q 10
Router(config-if)#ip address 172.16.10.1 255.255.255.0
Router(config-if)#interface Fa0/0.30
Router(config-if)#encapsulation dot1q 30
Router(config-if)#ip address 172.16.30.1 255.255.255.0
Router(config-if)#interface Fa0/0
Router(config-if)#no shutdown
Router(config-if)#end
Router#show ip route
Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP
D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area
N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2
E1 – OSPF external type 1, E2 – OSPF external type 2
i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2
ia – IS-IS inter area, * – candidate default, U – per-user static route
o – ODR, P – periodic downloaded static route

Gateway of last resort is not set

172.16.0.0/24 is subnetted, 2 subnets
C 172.16.10.0/24 is directly connected, FastEthernet0/0.10
C 172.16.30.0/24 is directly connected, FastEthernet0/0.30

As you can see in this example, we use only the FastEthernet 0/0 interface for both VLANs. We have created the Fa0/0.10 and Fa0/0.30 subinterfaces, specified the encapsulation type dot1q which is IEEE’s 802.1Q, and the VLAN they belong to and we assigned an IP address. In this case, the physical interface, FastEthernet 0/0, does not need an IP address configuration, the only thing you must do is to use the no shutdown command so that the interfaces comes up.

If you use a multilayer switch, to enable to routing features you must also enable ip routing .

Switch(config)#ip routing

However, different issue may arise when you use Inter-VLAN Routing. A switch for example can have an incorrect VLAN assigned to a switch port or the switch port may be configured in access mode instead of trunk. A router also, can have the wrong VLAN assigned to an interface or subinterface or the wrong encapsulation type. Assigning an IP address belonging to a class not used in that specific VLAN will also cause Inter-VLAN routing to not function properly. If your network is not working as expected, these are the most common places to look for errors.

This concludes our lesson. When you’ll take your Cisco CCNA certification exam, you must be able to correctly configure and troubleshoot a network using Inter-VLAN Routing. Practicing is the best way to learn how things work and we hope you found our hands-on example a great starting point.