CCNA 640-802 Lab - Configure and verify Frame Relay on Cisco routers

Exam: 640-802

Exam Objective: Configure and verify Frame Relay on Cisco routers

---

Contents

• Introduction
• Technology Background
• Lab Scenario
• Lab Objectives
• Lab Solution

---

Introduction

Frame Relay is a high-performance WAN protocol that operates at the physical and data link layers of the OSI reference model. Frame Relay originally was designed for use across Integrated Services Digital Network (ISDN) interfaces. Today, it is used over a variety of other network interfaces as well. This chapter focuses on Frame Relay's specifications and applications in the context of WAN services.
Frame Relay is an example of a packet-switched technology. Packet-switched networks enable end stations to dynamically share the network medium and the available bandwidth. Frame Relay often is described as a streamlined version of X.25, offering fewer of the robust capabilities, such as windowing and retransmission of last data that are offered in X.25. Frame Relay is a layer 2 technology.

Technology Background

The default encapsulation on a Cisco Router's serial interface is HDLC. To use Frame-Relay on them, the encapsulation needs to be changed using the "encapsulation frame-relay" command. With Frame Relay, there are further two encapsulation types - Cisco and IETF. Cisco is the default type and you will need to manually change it to IETF if you are connecting to a non-Cisco device. The command to do this is:
Router(config)#interface s0/0
Router(config-if)#encapsulation frame-relay ietf
Frame Relay operates using virtual circuits. These virtual circuits are what link together the devices connected to the provider's network. Frame Relay provides a virtual circuit between your two DTE devices, making them appear to be connected via a circuit when they are actually sending devices through a shared medium. There are two types of Virtual Circuits - Permanent virtual circuit (PVC) and Switched Virtual Circuit (SVCs). PVCs will always remain in place but SVCs are setup and torn down as and when data needs to be sent.
Frame Relay PVCs use Data Link Connection Identifiers (DLCIs). A Frame Relay service provider assigns DLCI values, which are used on Frame Relay interfaces to distinguish between different virtual circuits.
A DLCI can be assigned to an interface using the following command
Router(config)#interface s0/0
Router(config-if)#frame-relay interface-dlci <dlci>
The DLCI value can be anything between 16 and 1007.
Local Management Interface (LMI) is a signaling standard used between your router and the first Frame Relay switch it's connected to. It allows for sharing information about the operation and status of the virtual circuit between the provider's network and your router. The following information is shared using LMI:
Keepalives: These verify that data is flowing.
Global addressing: This provides global significance to DLCIs, allowing the Frame Relay
cloud to work exactly like a LAN.
Status of virtual circuits: This provides DLCI status. The status inquiries and messages are
used as keepalives when there is no regular LMI traffic to send.
There are three different types of LMI message formats: Cisco, ANSI, and Q.933A. The different
kinds in use depend on both the type and configuration of the telco's switching gear, so it's important the router is configured to use the LMI type configured at the telco's end. Cisco is default LMI type.
LMI type can be configured using the following command:
Router(config-if)#frame-relay lmi-type <cisco|ansi|q933a>
LMI is autosensed in routers running IOS version 11.2 and above.
Let's see the configuration of a PVC on a Serial Interface:
Router(config)#interface s0/0
Router(config-if)#encapsulation frame-relay ietf
Router(config-if)#ip address 192.168.1.1 255.255.255.0
Router(config-if)#frame-relay interface-dlci 101
The above example will configure a serial interface to use frame relay IETF encapsulation and DLCI 101. The router at the other end can use a DLCI provided by the ISP and 192.168.1.1 IP Address to reach us.
We can have multiple virtual circuits on a single Physical interface and each circuit can be treated as a different network/interface. This can be achieved using sub-interfaces. Frame Relay sub-interfaces can be point-to-point or multipoint. Point-to-Point sub-interfaces treat each DLCI as a different network. Multipoint interfaces will treat a group of DLCI as single network. Frame relay can be configured on sub-interfaces using the following commands:
Router(config)#interface s0/0
Router(config-if)#encapsulation frame-relay ietf
Router(config-if)#exit
Router(config)#interface s0/0.1 point-to-point
Router(config-subif)#ip address 192.168.1.1 255.255.255.0
Router(config-subif)#frame-relay interface-dlci 101
The following commands can be used to verify frame relay configuration:

• show frame-relay pvc
• show frame-relay lmi
• show interfaces

Lab Scenario

We have purchased Frame Relay links between our Head Office and Branch Offices. Your task is to configure the Routers as shown in Figure 1. Ensure that IETF frame-relay encapsulation is used.

Figure 1

Lab Objectives

• Configure Frame Relay using sub-interfaces on RouterA using DLCI 102 and 103
• Configure Frame Relay using the physical interface of Router B and DLCI 201
• Configure Frame Relay using the physical interface of Router C and DLCI 301

Lab Solution

Before we configure Frame-relay, it should be noted that a Frame Relay switch is required between the devices for the link to work. A Cisco router can be configured as a Frame Relay Switch. See the References section for the URL to the document explaining the Frame Relay switch configuration:
Let's configure RouterA first:
RouterA(config)#interface s0/0
RouterA(config-if)#encapsulation frame-relay ietf
RouterA(config-if)#no shut
RouterA(config-if)#exit
RouterA(config)#interface s0/0.1 point-to-point
RouterA(config-subif)#frame-relay interface-dlci 102
RouterA(config-fr-dlci)#exit
RouterA(config-subif)#ip address 192.168.1.1 255.255.255.0
RouterA(config-subif)#exit
RouterA(config)#interface s0/0.2 point-to-point
RouterA(config-subif)#frame-relay interface-dlci 103
RouterA(config-fr-dlci)#exit
RouterA(config-subif)#ip address 192.168.2.1 255.255.255.0

Configuration on RouterB:

RouterB(config)#interface s0/0
RouterB(config-if)#encapsulation frame-relay ietf
RouterB(config-if)#frame-relay interface-dlci 201
RouterB(config-fr-dlci)#exit
RouterB(config-if)#ip address 192.168.1.2 255.255.255.0
RouterB(config-if)#no shut
Configuration on RouterC:
RouterC(config)#interface s0/0
RouterC(config-if)#encapsulation frame-relay ietf
RouterC(config-if)#frame-relay interface-dlci 301
RouterC(config-fr-dlci)#exit
RouterC(config-if)#ip address 192.168.2.2 255.255.255.0
RouterC(config-if)#no shut

Let's verify connectivity from RouterA:
RouterA#ping 192.168.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/22/32 ms
RouterA#ping 192.168.2.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/17/64 ms

PVC status on RouterA:
RouterA#show frame-relay pvc

PVC Statistics for interface Serial0/0 (Frame Relay DTE)
              Active     Inactive      Deleted       Static
  Local          2            0            0            0
  Switched       0            0            0            0
  Unused         0            0            0            0
DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0.1
  input pkts 7             output pkts 18           in bytes 610       
  out bytes 3502           dropped pkts 0           in pkts dropped 0         
  out pkts dropped 0                out bytes dropped 0         
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0         
  out BECN pkts 0          in DE pkts 0             out DE pkts 0         
  out bcast pkts 7         out bcast bytes 2358      
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
  pvc create time 00:04:33, last time pvc status changed 00:04:13
          
DLCI = 103, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0.2
  input pkts 8             output pkts 16           in bytes 758       
  out bytes 2378           dropped pkts 0           in pkts dropped 0         
  out pkts dropped 0                out bytes dropped 0         
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0         
  out BECN pkts 0          in DE pkts 0             out DE pkts 0         
  out bcast pkts 3         out bcast bytes 1026      
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
  pvc create time 00:04:34, last time pvc status changed 00:04:14

PVC status on RouterB:
RouterB#show frame-relay pvc
PVC Statistics for interface Serial0/0 (Frame Relay DTE)
              Active     Inactive      Deleted       Static
  Local          1            0            0            0
  Switched       0            0            0            0
  Unused         0            0            0            0
DLCI = 201, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
  input pkts 16            output pkts 7            in bytes 2542      
  out bytes 610            dropped pkts 0           in pkts dropped 0         
  out pkts dropped 0                out bytes dropped 0         
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0         
  out BECN pkts 0          in DE pkts 0             out DE pkts 0         
  out bcast pkts 1         out bcast bytes 30        
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
  pvc create time 00:03:34, last time pvc status changed 00:02:23

PVC status on RouterC

RouterC#show frame-relay pvc
PVC Statistics for interface Serial0/0 (Frame Relay DTE)
              Active     Inactive      Deleted       Static
  Local          1            0            0            0
  Switched       0            0            0            0
  Unused         0            0            0            0
DLCI = 301, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
  input pkts 18            output pkts 8            in bytes 2750      
  out bytes 758            dropped pkts 0           in pkts dropped 0         
  out pkts dropped 0                out bytes dropped 0         
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0         
  out BECN pkts 0          in DE pkts 0             out DE pkts 0         
  out bcast pkts 1         out bcast bytes 30        
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
  pvc create time 00:03:53, last time pvc status changed 00:02:39


References:

Configuring Frame Relay Switching
http://www.cisco.com/en/US/tech/tk713/tk237/technologies_tech_note09186a008014f8a7.shtml#topic7
Frame Relay
http://www.cisco.com/en/US/docs/internetworking/technology/handbook/Frame-Relay.html
Comprehensive Guide to Configuring and Troubleshooting Frame Relay
http://www.cisco.com/en/US/tech/tk713/tk237/technologies_tech_note09186a008014f8a7.shtml

CCNA 640-802 Lab - Configure verify and troubleshoot EIGRP

Exam: 640-802

Exam Objective: Configure, verify, and troubleshoot EIGRP

---

Contents

• Introduction
• Technology Background
• Lab Scenario
• Lab Objectives
• Lab Solution

---

Introduction

EIGRP is a Cisco proprietary enhanced distance vector (hybrid) routing protocol. It is a classless protocol which sends output updates at startup and when there is a change in the network. The maximum hop count for EIGRP is 255. It supports various Routed protocols such as IPv4, IPv6, Appletalk, etc. It uses proprietary Reliable Transport Protocol (RTP) to send updates and Diffusing Update Algorithm (DUAL) to find the best path.

Technology Background

EIGRP is started on a router using the "router eigrp <as>" command. AS stands for Autonomous system.AS defines an EIGRP network. Routers belonging to different Autonomous Systems do not share routing information.
Once EIGRP has been started, network can be defined using the "network <address> <wildcard mask>". Wildcard mask is optional if you are using default subnet mask for the address class.
As soon as the network statement is added, EIGRP will start on interface which belongs to the Network configured with the network command. EIGRP will start sending out Hello packets to multicast address 224.0.0.10 to discover neighboring routers running EIGRP.
If it receives an ACK or Hello from another router in the same EIGRP AS then it will form an adjacency with it and the routers will exchange their full routing table.
EIGRP maintains a table of all its neighbors. This table can be viewed using the "show ip eigrp neighbor" command.
Routes received from neighbors are stored in a local topology table.
The route received from the neighbor will have a metric attached to it. This is the metric that is applicable on the advertising router. This is called the Reported Distance (RD). The receiving route will need to add the metric of the link between itself and the advertising router. If multiple paths are learned to a remote network then the path with best metric (RD + metric to the advertising router) is selected. This metric is the Feasible Distance (FD).
The path with the best metric is called the Successor. This is the route which will be presented to the router for the routing table. All other route to the same remote network will be kept as Feasible Successors as long as their RD is lower than the FD. Feasible successor is the route which will be used when the Successor is lost. EIGRP will keep upto 6 successors in the topology table.
EIGRP uses a combination of Bandwidth, Delay, Load and Reliability to calculate the metric of a route. Metric is the cost of using that route.
EIGRP topology table can be viewed using "show ip eigrp topology" command.
An important thing to note about EIGRP communication between two routers is that it is done using a Multicast to 224.0.0.10 IP address. If a route does not get Hellos from an adjacent router for a configured period then it will remove it from its neighbor table and also remove all routes learned from it.
Similarly if an EIGRP update is not acknowledged by an adjacent neighbor then update will be resent using a unicast packet up to 16 times. If the adjacent router still fails to acknowledge the update then the adjacency will be torn down and all routes learned from that neighbor will be flushed.
We learned previously that EIGRP will select the route with the best metric. What if there are multiple routes to the same destination with the same metric? EIGRP can load-balance over a maximum of 6 such equal cost paths. By default it is configured to load balance between 4 paths. This can be changed using the following command:
Router(config)#router eigrp 1
Router(config-router)#maximum-paths 6

As mentioned earlier EIGRP has a maximum hop count of 255 but the default maximum hop count is 100. This can be changed using the following command:
Router(config)#router eigrp 1
Router(config-router)#metric maximum-hops 255
The number 255 can be anything from 1 to 255.
EIGRP can be disabled on an interface using the "passive-interface <interface>" command in the EIGRP configuration mode. This will stop EIGRP from sending and receiving Hello packets on an interface. This means that EIGRP will not for adjacency on that interface and hence will not send or receive routes.

Lab Scenario

We want to use EIGRP in the network shown in Figure 2. Your task is to configure EIGRP on all routers such that:

• Traffic from 192.168.1.0/24 never goes through RouterC to reach 192.168.7.0/24
• RouterB never load-balances between the two paths to 192.168.7.0/24
• RouterA should not form adjacency if Hello packets are received on its fa0/1 interface
• RouterC and RouterD should not form adjacency if Hello packets are received on their fa0/2 interfaces.

Apart from the restrictions above, all routers should know about all the networks. AS 100 should be used across the network.

Figure 2

Lab Objectives

• Configure EIGRP is AS 100 on all routers and advertise all connected routes
• Set maximum hop to 2 on RouterA
• Set maximum-paths to 1 on RouterB
• Configure fa0/1 as passive on RouterA
• Configure fa0/2 as passive on RouterC and RouterD

Lab Solution

First we need to enable EIGRP on all routers and advertise their connected routes:
RouterA(config)#router eigrp 100
RouterA(config-router)#network 192.168.1.0
RouterA(config-router)#network 192.168.2.0

RouterB(config)#router eigrp 100
RouterB(config-router)#network 192.168.2.0
RouterB(config-router)#network 192.168.3.0
RouterB(config-router)#network 192.168.5.0

RouterC(config)#router eigrp 100
RouterC(config-router)#network 192.168.3.0
RouterC(config-router)#network 192.168.4.0
RouterC(config-router)#network 192.168.6.0
RouterD(config)#router eigrp 100
RouterD(config-router)#network 192.168.5.0
RouterD(config-router)#network 192.168.6.0
RouterD(config-router)#network 192.168.7.0
We need to ensure that traffic from 192.168.1.0/24 never cross RouterC on the way to 192.168.7.0/24. RouterB will have the path form RouterC as a feasible successor to 192.168.7.0/24. This path will be advertised to RouterA if RouterB's fa0/2 link goes down.
The difference between the two paths for RouterA is the hop count. If we restrict the hop count to 2 on RouterA then the path to 192.168.7.0/24 from RouterC will never be used because its hop count is higher.
RouterA(config)#router eigrp 100
RouterA(config-router)#metric maximum-hops 2
We can stop RouterB from load-balancing by setting maximum-paths to 1 instead of default 4 :
RouterB(config)#router eigrp 100
RouterB(config-router)#maximum-paths 1
Finally we can make the given interfaces passive by using the following commands:
RouterA(config)#router eigrp 100
RouterA(config-router)#passive-interface fa0/1
RouterC(config)#router eigrp 100
RouterC(config-router)#passive-interface fa0/2
RouterD(config)#router eigrp 100
RouterD(config-router)#passive-interface fa0/2

Let's verify configuration by looking at the routing table of each router:
RouterA#show ip route
--output truncated--
Gateway of last resort is not set
D    192.168.4.0/24 [90/309760] via 192.168.2.2, 00:01:59, FastEthernet0/0
D    192.168.5.0/24 [90/284160] via 192.168.2.2, 00:01:59, FastEthernet0/0
D    192.168.6.0/24 [90/309760] via 192.168.2.2, 00:01:59, FastEthernet0/0
D    192.168.7.0/24 [90/286720] via 192.168.2.2, 00:01:59, FastEthernet0/0
C    192.168.1.0/24 is directly connected, FastEthernet0/1
C    192.168.2.0/24 is directly connected, FastEthernet0/0
D    192.168.3.0/24 [90/307200] via 192.168.2.2, 00:01:59, FastEthernet0/0
RouterB#show ip route
--output truncated--
Gateway of last resort is not set
D    192.168.4.0/24 [90/284160] via 192.168.3.2, 00:02:12, FastEthernet0/1
C    192.168.5.0/24 is directly connected, FastEthernet0/2
D    192.168.6.0/24 [90/284160] via 192.168.5.2, 00:02:12, FastEthernet0/2
D    192.168.7.0/24 [90/30720] via 192.168.5.2, 00:02:12, FastEthernet0/2
D    192.168.1.0/24 [90/307200] via 192.168.2.1, 00:02:12, FastEthernet0/0
C    192.168.2.0/24 is directly connected, FastEthernet0/0
C    192.168.3.0/24 is directly connected, FastEthernet0/1
RouterC#show ip route
--output truncated--
Gateway of last resort is not set
C    192.168.4.0/24 is directly connected, FastEthernet0/2
D    192.168.5.0/24 [90/284160] via 192.168.3.1, 00:03:22, FastEthernet0/1
C    192.168.6.0/24 is directly connected, FastEthernet0/0
D    192.168.7.0/24 [90/284160] via 192.168.6.2, 00:03:21, FastEthernet0/0
D    192.168.1.0/24 [90/332800] via 192.168.3.1, 00:02:49, FastEthernet0/1
D    192.168.2.0/24 [90/307200] via 192.168.3.1, 00:03:22, FastEthernet0/1
C    192.168.3.0/24 is directly connected, FastEthernet0/1
RouterD#show ip route
--output truncated--
Gateway of last resort is not set
D    192.168.4.0/24 [90/284160] via 192.168.6.1, 00:03:35, FastEthernet0/0
C    192.168.5.0/24 is directly connected, FastEthernet0/1
C    192.168.6.0/24 is directly connected, FastEthernet0/0
C    192.168.7.0/24 is directly connected, FastEthernet0/2
D    192.168.1.0/24 [90/332800] via 192.168.5.1, 00:02:59, FastEthernet0/1
D    192.168.2.0/24 [90/307200] via 192.168.5.1, 00:03:35, FastEthernet0/1
D    192.168.3.0/24 [90/307200] via 192.168.6.1, 00:03:35, FastEthernet0/0
                    [90/307200] via 192.168.5.1, 00:03:35, FastEthernet0/1
We can further verify the configuration using "show ip protocols" command:
RouterA#sh ip protocols
Routing Protocol is "eigrp 100"
  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 2
  EIGRP maximum metric variance 1
  Redistributing: eigrp 100
  EIGRP NSF-aware route hold timer is 240s
  Automatic network summarization is in effect
  Automatic address summarization:
    192.168.1.0/24 for FastEthernet0/0
  Maximum path: 4
  Routing for Networks:
    192.168.1.0
    192.168.2.0
  Passive Interface(s):
    FastEthernet0/1
  Routing Information Sources:
    Gateway         Distance      Last Update
    192.168.2.2           90      00:06:31
  Distance: internal 90 external 170
RouterB#sh ip protocols
Routing Protocol is "eigrp 100"
  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 100
  EIGRP NSF-aware route hold timer is 240s
  Automatic network summarization is in effect
  Automatic address summarization:
    192.168.5.0/24 for FastEthernet0/0, FastEthernet0/1
    192.168.3.0/24 for FastEthernet0/0, FastEthernet0/2
    192.168.2.0/24 for FastEthernet0/1, FastEthernet0/2
  Maximum path: 1
  Routing for Networks:
    192.168.2.0
    192.168.3.0
    192.168.5.0
  Routing Information Sources:
    Gateway         Distance      Last Update
    192.168.3.2           90      00:07:25
    192.168.2.1           90      00:07:26
    192.168.5.2           90      00:07:26
  Distance: internal 90 external 170
RouterC#show ip protocols
Routing Protocol is "eigrp 100"
  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 100
  EIGRP NSF-aware route hold timer is 240s
  Automatic network summarization is in effect
  Automatic address summarization:
    192.168.6.0/24 for FastEthernet0/1
    192.168.4.0/24 for FastEthernet0/0, FastEthernet0/1
    192.168.3.0/24 for FastEthernet0/0
  Maximum path: 4
  Routing for Networks:
    192.168.3.0
    192.168.4.0
    192.168.6.0
  Passive Interface(s):
    FastEthernet0/2
  Routing Information Sources:
    Gateway         Distance      Last Update
    192.168.3.1           90      00:09:16
    192.168.6.2           90      00:09:16
  Distance: internal 90 external 170
RouterD#show ip protocols
Routing Protocol is "eigrp 100"
  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 100
  EIGRP NSF-aware route hold timer is 240s
  Automatic network summarization is in effect
  Automatic address summarization:
    192.168.7.0/24 for FastEthernet0/0, FastEthernet0/1
    192.168.6.0/24 for FastEthernet0/1
    192.168.5.0/24 for FastEthernet0/0
  Maximum path: 4
  Routing for Networks:
    192.168.5.0
    192.168.6.0
    192.168.7.0
  Passive Interface(s):
    FastEthernet0/2
  Routing Information Sources:
    Gateway         Distance      Last Update
    192.168.5.1           90      00:10:08
    192.168.6.1           90      00:10:08
  Distance: internal 90 external 170
References:

Enhanced Interior Gateway Routing Protocol
http://www.cisco.com/en/US/tech/tk365/technologies_white_paper09186a0080094cb7.shtml
Configuring EIGRP
http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfeigrp.html

Cisco Carrier Routing System X (CRS-X) Core Router

Cisco duplica velocidad de Internet

La tecnológica presentó su ‘router’ de núcleo que ofrecerá velocidades de hasta 1 petabit/segundo; clientes como Verizon ya se han mostrado interesados en el sistema que saldrá al mercado en otoño.

 

Cisco Systems dice que está mejorando sus routers de núcleo para Internet con un sistema de mayor capacidad llamado CRS-X, que dijo ayudará a los proveedores de servicios para satisfacer la demanda de 10G, aplicaciones Ethernet de 40G y 100G sin tener que cambiar de nuevo hardware.

NUEVA YORK — Si el tráfico de Internet se triplica en los próximos cinco años, como predice Cisco, necesitaremos un barco más grande.
Este miércoles Cisco dio a conocer su más reciente solución para ayudar a los operadores inalámbricos y proveedores de servicios de Internet a gestionar la insaciable demanda de sus clientes por más videos en streaming, descargas de aplicaciones y redes sociales.
La nueva tecnología de router de núcleo, conocida como "CRS-X", ofrecerá velocidades de 400 gigabits por segundo; y eso es sólo por una ranura en el anaquel del router (o enrutador de tráfico). Cada anaquel es escalable a hasta 6.4 terabits por segundo, y el sistema CRS-X completo tiene una capacidad de casi 1 petabit por segundo si varios anaqueles se colocan en tándem.
Es increíblemente rápido, el doble de todo lo que existe actualmente en el mercado.
Un solo anaquel CRS-X será capaz de ofrecer streaming de video HD a todos los neoyorquinos a la vez, afirma Cisco. Una instalación completa multichasis es capaz de descargar toda la colección impresa de la Biblioteca del Congreso en una fracción de segundo y puede transmitir todas las películas que jamás se hayan creado en un minuto.
Los routers principales o de núcleo se ubican en el epicentro de Internet, actuando como policías de tránsito en las principales intersecciones de las autopistas de datos más transitadas. Conectan peticiones de los visitantes a sitios como Netflix, Google y Facebook, y también envían los datos al lugar correcto de vuelta.
Son una parte crucial de la red troncal de Internet, y Cisco tiene una cómoda ventaja en ese ámbito. Cisco cuenta con 750 clientes CRS, ha vendido 10,000 sistemas hasta la fecha y cuenta con una participación de aproximadamente 65% en el mercado de enrutamiento de núcleo. Eso es más del doble de la participación del número dos, Juniper.
Cisco dice que su solución es más barata que las ofrecidas por Juniper. Por ejemplo, los clientes que instalaron el router de núcleo anterior de Cisco, denominado CRS-3, en 2010, pueden actualizarse al CRS-X simplemente intercambiando sus tarjetas CRS-3 por las nuevas. En las actualizaciones anteriores, Juniper ha requerido a los clientes que compren instalaciones completamente nuevas de router para actualizar sus sistemas.
"Es tan fácil como colocar nuevas tarjetas de línea", dijo, el director de mercadotecnia de proveeduría de servicios de Cisco, Stephen Liu. "Entonces, para efectos prácticos, será un CRS-X -a excepción de lo que indique la pintura en el exterior".
Cisco dice que el CRS-X ayudará a los clientes a prepararse para el 'Internet de las cosas', un muy debatido (pero aún inexistente) mundo en el que los artículos para el hogar, automóviles e incluso la ropa estaría conectada a Internet. En lugar de conectar cuatro millones de dispositivos al mismo tiempo, los operadores y proveedores de Internet podrían tener que conectar 40 millones de artículos al mismo tiempo.
Es por eso que los modernos routers de núcleo como el CRS-X gestionan distintos tipos de tráfico en vías separadas. Tendrías una experiencia miserable si tu streaming de video en Netflix se interrumpe todo el tiempo, pero es probable que no te des cuenta si una página web toma una fracción de segundo más en cargarse.
"La innovación que nuestros clientes recibirán no se trata únicamente de una mayor velocidad y de más carriles en la autopista", dijo Liu. "Es más como un sistema GPS que te ayuda a encontrar la mejor ruta con base en las congestiones de tráfico".
Aunque el CRS-X no saldrá a la venta sino hasta el otoño y sus envíos no comenzarán sino hasta finales de 2013, los clientes ya están diciendo que están impresionados. El vicepresidente de operaciones de red de Verizon Wireless, Mike Haberman, dijo que el nuevo sistema de CRS ayudará al proveedor de telefonía móvil más grande de Estados Unidos a cumplir con las demandas en su servicio "muy en el futuro".

 Fuente:
http://www.cnnexpansion.com/tecnologia/2013/06/13/internet-mas-rapido-con-router-de-cisco

CCNA 640-802 Lab - Configure, verify and troubleshoot DHCP and DNS operation on a router.(including: CLI/SDM)

Exam: 640-802

Exam Objective: Configure, verify and troubleshoot DHCP and DNS operation on a router.(including: CLI/SDM)

---

Contents

• Introduction
• Technology Background
• Lab Scenario
• Lab Objectives
• Lab Solution

---

Introduction

This lab will cover the configuration and verification of DHCP and DNS in a Cisco network. This is an advanced lab for a CCNA student, as there is now walkthrough and you are on your own to configure the network according to the objectives using only the comments and tips for help. At the end of the lab the completed configurations and verifications "show" commands are provided. Again, this is a somewhat complex lab for a CCNA student but try to complete the tasks shown on your own using your own lab.
Lab Topics Covered:

• Frame Relay
• Frame Relay Multipoint
• DHCP server
• DHCP pool
• DHCP Exclude
• DHCP DNS server
• DHCP Lease
• DCHP Database storage
• DCHP Client
• OSPF
• OSPF multipoint

Technology Background

DHCP is build upon BootP, and BootP remains an internal part of DHCP. Both protocols have been created to provide IP addresses to clients when needed. The difference between them is that while BootP provides an IP address to a client according to the client's hardware address on the BootP server table, DHCP by default provides an IP address automatically to the client from a pool of IP addresses.
Besides an IP address, the DHCP server can provide the client a lot of information, such as DNS server IP address, Default gateway IP address, Domain name and much more.
A Cisco IOS device can be configured to act as:

• a DHCP server - by providing IP addresses when requested to do so

• a DHCP client - when it requests an IP address

• a DHCP relay agent - when it captures IP requests from clients, adds extra information to the request for user identification purposes, and forwards the request to the DHCP server

Cisco IOS devices can be configured to act as all of the above and even in combinations of two or three of roles. The Cisco IOS DHCP Server feature is a full DHCP Server implementation that assigns and manages IP addresses from specified address pools within the router to DHCP clients. If the Cisco IOS DHCP Server cannot satisfy a DHCP request from its own database, it can forward the request to one or more secondary DHCP Servers defined by the network administrator.

Lab Scenario

For this lab, the following network topology will be used.

Lab Objectives

Lab Configuration Tasks:

• Set up the network as shown in the diagram using the IP addresses specified. Configure the frame relay network so that TK3 is the hub using DLCI 311, 322, and 344 going to routers TK1, TK2, and TK4. Use subinterfaces on TK1, TK2, TK3, and TK4. Use IP subnet 172.16.123.0/24 with the router number used as the 4th octet. Ensure that only the DLCI's specified here are used.
• Configure router TK4 as a DHCP server. Create a pool for the 172.16.136.0/25 subnet. Allow the entire subnet but exclude IP addresses 1-10 and 15. Configure it so that hosts use the DNS servers at 10.2.6.253 and 10.2.6.254 and with a DHCP lease time of 8 hours.
• Configure TK4 to send the DHCP database information via TFTP to 10.2.6.264, while delaying the writing of records for 10 minutes.
• Configure OSPF in the network in any manner as you wish, as long as all networks are reachable. For the frame relay cloud, do not use the broadcast network type on any of the frame relay interfaces.
• Configure the Catalyst switch so that it gets it's IP address from the DHCP server. Ensure that this switch always gets the IP address 172.16.136.15 and supply the switch with the DNS server and default gateway information specified in task 2.

Comments and Tips:

Task 1: Not Applicable
Task 2: Routers can be configured to forward DHCP broadcasts (via the IP helper-address command) or to respond to these requests as a DHCP server.
Task 3: A DHCP database agent should be configured for this, or the DHCP conflict resolution should be disabled.
Task 4: The network type will need to be changed on each of the frame relay interfaces of the routers.
Task 5: The Catalyst switch will first broadcast for a DHCP server and then it will RARP. If nothing is received after 10 minutes the switch will retain the 0.0.0.0 IP address. Remember, by default UDP broadcasts are not forwarded by routers. Once the switch receives an IP address it will be written into the configuration.

Lab Solution

Technical Verification For Task 1:

TK1#sho frame map
Serial1/0.1(up): point-to-point dlci, dlci 113(0*71,0*1C10), broadcast
Status defined, active

TK2#sho frame map Serial 1/0.1 (up): point-to-point dlci, dlci 223(0*DF, 0*34F0), broadcast
Status defined, active

TK3#sho frame map
Serial1/0.1(up): ip 172.16.123.1 dlci 311(0*137, 0*4C70), static,
broadcast,
CISCO, status defined, active
Serial1/0(up): ip 172.16.123.1 dlci 322(0*124, 0*5020), static,
broadcast,
CISCO, status defined, active
Serial1/0(up): ip 172.16.123.4 dlci 344(0*158, 0*5480), static,
broadcast,
CISCO, status defined, active

TK4#sho frame map
Serial0/0.1(up): point-to-point dlci, dlci 443(0*1BB, 0*6CB0), broadcast
Status defined, active

Technical Verification For Task 2:

(Note: This show command was issued after completion of exercise E.)
TK4#sho ip dhcp server st
Memory usage 15644
Address pools 2
Database agents 1
Automatic bindings 0
Manual bindings 1
Expired bindings 0
Malformed messages 0
Message Received
BOOTREQUEST 0
DHCPDISCOVER 1
DHCPREQUEST 1
DHCPDECLINE 0
DHCPRELEASE 0
DHCPINFORM 0
Message Sent
BOOTRELAY 0
DHCPOFFER 1
DHCPACK 1
DHCPNAK 0

Technical Verification for Task 3:

TK4#sho ip dhcp database
URL:tftp://10.2.6.254
Read: Never
Written: Never
Status: Nothing to report.
Delay: 600 seconds
Timeout: 300 seconds
Failures: 0
Successes: 0

Technical Verification For Task 4:

TK1#sho ip ospf interface
Loopback0 is up, line protocol is up
Internet address 192.168.1.1/24, area 1
Process ID 1, Router ID 192.168.1.1, Network type LOOPBACK, Cost: 1
Loopback interface is treated as a stub Host
Serial1/0.1 is up, line protocol is up
Internet address 172.16.123.1/24, Area 0
Process ID 1, Router ID 192.168.1.1, Network Type POINT_TO_MULTIPOINT, Cost: 48
Transmit delay is 1 sec, State POINT_TO_MULTIPOINT,
Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5
Hello due in 00:00:17
Index 1/5, flood queue length 0
Next 0*0(0)/0*0(0)
Last flood scan length is 1, maximum is 5
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 192.168.3.3
Suppress hello for 0 neighbor(s)

TK2#sho ip ospf interface
Loopback0 is up, line protocol is up
Internet address 192.168.2.2/24, Area 2
Process ID, Router ID 192.168.2.2, Network Type LOOPBACK, Cost: 1
Loopback interface is treated as a stub Host
Serail1/0.1 up, line protocol is up
Internet address 172.16.123.2/24, area 0
Process ID 1, Router ID 192.168.2.2, Network Type POINT_TO_MULTIPOINT, Cost: 48
Transmit Delay is 1 sec, State POINT_TO_MULTIPOINT,
Timer intervals configured, Hello 30, Dead 120, wait 120, Retransmit 5
Hello due in 00:00:29
Index , flood length 0
Next 0*0(0)/0*0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor 192.168.3.3
Suppress hello for 0 neighbor(s)

TK3#sho ip ospf interface
Ethernet0/0 is up, line protocol is up
Internet address 172.16.136.3/26, Area 0
Internet ID 1, Router ID 192.168.3.3, Network Type BROADCAST, Cost: 10
Transmit Delay is 1 sec, State DR, Priority 1
Designation router (ID) 192.168.1.1, Interface address 172.16.136.1
Backup designation router (ID) 192.168.3.3, Interface address 172.16.136.3
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:07
Index1/1, flood queue length 0
Next 0*0(0)/0*0(0)
Last flood scan length is1, maximum is 5
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor count is 3, Adjacent neighbor count is 3
Adjacent with neighbor 192.168.6.6
Adjacent with neighbor 192.168.5.5
Adjacent with neighbor 192.168.1.1 (Designation Router)
Suppress hello for 0 neighbor(s)
Loopback0 is up, line protocol is up
Internet address 192.168.1.1/24, Area 1
Process ID 1, Router ID 192.168.3.3, Network type LOOPBACK, Cost: 1
Loopback interface is treated as a stub Host
Serial1/0.1 is up, line protocol is up
Internet address 172.16.123.3/24, Area 0
Process ID 1, Router ID 192.168.3.3, Network Type POINT_TO_MULTIPOINT, Cost: 781
Transmit delay is 1 sec, State POINT_TO_MULTIPOINT,
Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5
Hello due in 00:00:04
Next 0*0(0)/0*0(0)
Index 1/5, flood queue length 0
Last flood scan length is 1, maximum is 5
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 3
Adjacent with neighbor 192.168.4.4
Adjacent with neighbor 192.168.1.1
Adjacent with neighbor 192.168.2.2
Suppress hello for 0 neighbor(s)

TK4#sho ip ospf interface
Loopback0 is up, line protocol is up
Internet address 192.168.4.4/24, Area 4
Process ID 1, Router ID 192.168.4.4, Network type LOOPBACK, Cost: 1
Loopback interface is treated as a stub Host
Serail1/0.1 up, line protocol is up
Internet address 172.16.123.4/24, Area 0
Process ID 1, Router ID 192.168.4.4, Network Type POINT_TO_MULTIPOINT, Cost: 64
Transmit Delay is 1 sec, State POINT_TO_MULTIPOINT,
Timer intervals configured, Hello 30, Dead 120, wait 120, Retransmit 5
Hello due in 00:00:17
Index , flood length 0
Next 0*0(0)/0*0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor 192.168.3.3
Suppress hello for 0 neighbor(s)
TK4#


Technical Verification For Task 5:

Console>(enable)set interface sc0 dhcp renew
Renewing IP address...
Console>(enable) sending RARP request with 00:09:2b:a3:bf:ff
Sending DHCP packet with address: 00:09:2b:a3:bf:ff
Sending DHCP packet with address: 00:09:2b:a3:bf:ff
10.2.6.254 added to DNS server table as primary server.
10.2.6.253 added to DNS server table as backup server.
System name set.
Default DNS domain name set to Test1.net
2002 Mar 06: 20:32:05%MGMT-5-DHCP_S:Assigned IP address 172.16.136.15 from DHCP
Server 172.16.123.4
TKCAT>(enable) sho interf
s10: flags=51<UP, POINTOPOINT, RUNNING>
Slip 0.0.0.0dest 0.0.0.0
sc0: flags=63<UP, POINTOPOINT, RUNNING>
vlan 1 inet 172.16.136.15 network 255.255.255.128 broadcast 172.16.136.127
dhcp server: 172.16.123.4
TKCAT>(enable)
Configuration Verification:

Note: Only the relevant portions of the configuration have been included.
Router 1:

TK1#sho run
!
hostname TK1
!
!
interface Loopback0
ip address 192.168.1.1 255.255.255.0
!
interface Ethernet0/0
ip address 172.16.15.1 255.255.255.192
half-duplex
!
interface Serial1/0
no ip address
encapsulation fram-relay
no frame-relay inverse-arp
!
interface Serial1/0.1 point-to-point
ip address 172.16.123.1 255.255.255.0
ip ospf network point-to- multipoint
frame-relay interface-dlci 113
!
router ospf 1
log-adjacency-changes
network 172.16.0.0.0.0.255.255 area 0
network 192.168.1.0.0.0.0.255 area 1
!
!
end

Router 2:

TK2#sho run
!
hostname TK2
!
!
interface Loopback0
ip address 192.168.2.2 255.255.255.0
!
interface Serial1/0
encapsulation frame-relay
no frame-relay inverse-arp
!
interface Serial1/0.1 point-to-point
ip address 172.16.123.2 255.255.255.0
ip ospf network point-to- multipoint
frame-relay interface-dlci 223
!
router ospf 1
log-adjacency-changes
network 172.16.123.0.0.0.0.255 area 0
network 192.168.2.0.0.0.0.255 area 2
!
!
end

Router 3:

TK3#sho run
hostname TK3
!
!
interface Loopback0
ip address 192.168.3.3 255.255.255.0
!
interface Ethernet0/0
ip address 172.16.136.3 255.255.255.192
ip helper-address 172.16.123.4
!
interface Serial1/0
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
!
interface serial1/0.1 multipoint
ip address 172.16.123.3 255.255.255.0
frame-relay interface-dlci 311
frame-relay interface-dlci 322
frame-relay interface-dlci 344
!
router ospf 1
log-adjacency-changes
network 172.16.136.0.0.0.0.255 area 0
network 192.168.3.0.0.0.0.255 area 3
!
!
end

Router 4:

TK4#sho run
!
hostname TK4
!
ip dhcp database tftp://10.2.6.254 write-delay 600
ip dhcp excluded-address 172.16.136.10
ip dhcp excluded-address 172.16.136.15
ip shcp ping packet 4
!
ip shcp pool Test1
network 172.16.136.0 255.255.255.128
domain-name Test1.net
default-router 172.16.136.3
option 66 ip 10.2.6.136.3
netbios-node-type-h-hode
dns-server 10.2.6.254 10.2.6.254
lease 0 8
!
ip dhcp pool cat
!
!
!
!
interface Loopback0
ip address 192.168.4.4 255.255.255.0
!
interface Ethernet0/0
ip address 10.1.4.4 255.255.252.0
!
interface Serial0/0
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
!
interface Serial0/0.1 point-to-point
ip address 172.16.123.4 255.255.255.0
ip ospf network point-to- multipoint
frame-relay interface-dlci 443
!
!
router ospf 1
log-adjacency-changes
network 172.16.123.0.0.0.0.255 area 0
network 192.168.4.0.0.0.0.255 area 4
network 10.1.4.0 0.0.0.255 area 44
!
!
end

Catalyst:

TKCAT>(enable) sho run
!
#ip
#learn from dhcp server 172.16.123.4
interface sc0 1 172.16.136.15 255.255.255.192
set ip route 0.0.0.0/0.0.0.0 172.16.136.3
!
#dns
set ip dns server 10.2.6.254 primary
set dns server 10.2.6.253
set ip dns domain Testking.com
!

References:
Understanding DHCP And DNS
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6554/ps6600/ps6641/prod_presentation0900aecd803116a7.pdf
Configuring DHCP
http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfdhcp.html

CCNA Lab Exam: 640-802 Objective: Configure, verify, and troubleshoot RIPv2

Exam: 640-802

Exam Objective: Configure, verify, and troubleshoot RIPv2

---

Contents

• Introduction
• Technology Background
• Lab Scenario
• Lab Objectives
• Lab Solution

---

Introduction

There are three types of routing Protocols - Distance Vector, Link-State and Hybrid. The distance-vector routing algorithm sends complete routing table information to neighboring
Routers at periodic intervals, which then combine the received routing information with their own routing tables to create the routing table.
RIP is a distance vector protocol and has two version - 1 and 2.

Technology Background

RIPv2 multicasts its entire routing table every 30 seconds to the multicast address 224.0.0.9. It uses hop counts to determine the best path to a destination network but it has a limit of 15 hops. Which means if a network is found to be more than 15 hops away then that route will be discarded as unreachable.
RIPv2 support classless routing updates (sends subnet mask information in routing updates) unlike RIPv1.
RIP uses many timers to maintain its routing table and interact with its neighbors. There are:
Route Update Timer: The routing-update timer clocks the interval between periodic routing updates. Generally, it is set to 30 seconds, with a small random amount of time added whenever the timer is reset.
Route invalid timer: It is the length of time that must elapse (180 seconds by default) before a
router determines that a route has become invalid. This means if a Router hasn't heard about a route for 180 seconds (by default) then it will assume that the route has been lost. When that happens, the router will send out updates to all its neighbors letting them know that the route is invalid.
Holddown timer: This sets the amount of time during which routing information is suppressed.
Routes will enter into the holddown state when an update packet is received which indicates that the route is unreachable. This continues either until an update packet is received with a
better metric or until the holddown timer expires. The default is 180 seconds.
Route flush timer: Sets the time between a route becoming invalid and its removal from the
routing table (240 seconds). Before it's removed from the table, the router notifies its neighbors
that route has been lost. The value of the route invalid timer must be less than that of the route flush timer.
The following steps are required to enable RIP:

• Enable the RIP process using the following command:

Router(config)#router rip

• Set the version to 2:

Router(config-router)#version 2

• Specify the networks to be advertised:

Router(config-router)#network <network>

It should be noted that the networks can be added in their classful form only. RIP will advertised any networks connected the router which fall under the classful boundary but will add the subnet mask configure on the interfaces.

For Example, let's look at the configuration below:

interface FastEthernet0/0

ip address 192.168.1.1 255.255.255.128

!

Interface FastEthernet0/1

ip address 192.168.1.129 255.255.255.128

!

router rip

version 2

network 192.168.1.0

!

This router will advertise both the networks with a /25 mask and will also enable the RIP process on both the interfaces. Which means it will receive and send routing updates through fa0/0 and fa0/1

RIP can be configure not to send updates out on a interface using the passive-interface <interface>command under the routing process. An interface configured as passive under RIP will continue receiving updates though.
A few commands which can be used to verify and troubleshoot RIP are:

• show ip route - Shows the routing table of the router
• show ip protocol - Shows all Routing protocols running and their parameters
• sh ip rip database - Shows the RIP database
• debug ip rip - Shows debugs of rip process

Lab Scenario

Your task is to configure the network shown in Figure 1, such that:

• RouterA and RouterB know all the 192.168.x.0 networks
• RouterC does not know the 192.168.1.0/24, 192.168.2.0/24 and 192.168.3.0/24
• RouterC should be configured with a default route to reach the networks it does not know

Figure 1

Lab Objectives

• Enable RIP on all routers and advertise all networks
• Make the fa0/1 interfce of RouterB a passive interface
• Add a default route on RouterC pointing to 192.168.4.1 (RouterB's fa0/1 interface)

Lab Solution

First we need to enable RIP and advertise all networks on all Routers:
RouterA(config)#router rip
RouterA(config-router)#network 192.168.1.0
RouterA(config-router)#network 192.168.2.0
RouterB(config)#router rip
RouterB(config-router)#network 192.168.2.0
RouterB(config-router)#network 192.168.3.0
RouterB(config-router)#network 192.168.4.0
RouterC(config)#router rip
RouterC(config-router)#network 192.168.4.0
RouterC(config-router)#network 192.168.5.0
Now we need to ensure that RouterC does not get routes from RouterA and RouterB but sends routes to them. So we need to make the fa0/1 interface on RouterB passive. This will ensure that it gets routes from RouterC but does not send any:
RouterB(config-router)#passive-interface fa0/1
Finally we add a default route on RouterC to ensure that it can get to all the networks:
RouterC(config)#ip route 0.0.0.0 0.0.0.0 192.168.4.1

Let's verify the configuration:
RouterA#show ip route
--output truncated--
Gateway of last resort is not set
R    192.168.4.0/24 [120/1] via 192.168.2.2, 00:00:06, FastEthernet0/0
R    192.168.5.0/24 [120/1] via 192.168.2.2, 00:00:04, FastEthernet0/0
C    192.168.1.0/24 is directly connected, FastEthernet0/1
C    192.168.2.0/24 is directly connected, FastEthernet0/0
R    192.168.3.0/24 [120/1] via 192.168.2.2, 00:00:06, FastEthernet0/0

RouterB#show ip route
--output truncated--
Gateway of last resort is not set
C    192.168.4.0/24 is directly connected, FastEthernet0/1
R    192.168.5.0/24 [120/1] via 192.168.4.2, 00:00:01, FastEthernet0/1
R    192.168.1.0/24 [120/1] via 192.168.2.1, 00:00:15, FastEthernet0/0
C    192.168.2.0/24 is directly connected, FastEthernet0/0
C    192.168.3.0/24 is directly connected, FastEthernet0/2

RouterC#show ip route
--output truncated--

Gateway of last resort is 192.168.4.1 to network 0.0.0.0
C    192.168.4.0/24 is directly connected, FastEthernet0/1
C    192.168.5.0/24 is directly connected, FastEthernet0/0
S*   0.0.0.0/0 [1/0] via 192.168.4.1

RouterA#show ip protocols
Routing Protocol is "rip"
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Sending updates every 30 seconds, next due in 8 seconds
  Invalid after 180 seconds, hold down 180, flushed after 240
  Redistributing: rip
  Default version control: send version 2, receive version 2
    Interface             Send Recv Triggered RIP Key-chain
    FastEthernet0/0       2     2                                    
    FastEthernet0/1       2     2                                    
  Automatic network summarization is in effect
  Maximum path: 4
  Routing for Networks:
    192.168.1.0
    192.168.2.0
  Routing Information Sources:
    Gateway         Distance      Last Update
    192.168.2.2          120      00:00:10
  Distance: (default is 120)



References:

Network Protocols Configuration Guide, Part 1 - Configuring RIP:
http://www.cisco.com/en/US/docs/ios/11_3/np1/configuration/guide/1crip.html

Internetworking Technology Handbook - Routing Information Protocol (RIP)
http://www.cisco.com/en/US/docs/internetworking/technology/handbook/RIP.html

CCNA 640-802 Lab - Configure, verify, and troubleshoot OSPF

Exam: 640-802

Exam Objective: Configure, verify, and troubleshoot OSPF

---

Contents

• Introduction
• Technology Background
• Lab Scenario
• Lab Objectives
• Lab Solution

---

Introduction

In this lab you will have to perform configuration tasks in relation to OSPF areas, as well as some redistribution of routes between RIPv2 and OSPF. To complete this lab you will need access to either lab consisting of four Cisco routers or a router simulation program. There are a number of free router simulators available for download from the Internet. As with any other program you download from the Internet make sure you scan it for viruses

Technology Background

When OSPF special areas are implemented the result the ability to support more scalability in networks and increased network stability. The memory of the routers within these areas is not used as much because the LSA messages that are sent are decreased. How much LSA traffic is decreased depends on the area that is implemented. The OSPF areas are stand area, backbone area, stub area, totally area, and NSSA.

OSPF standard areas are the default OPSF area type which accept the following LSA message types: route summary, link updates, and route summaries.

OSPF backbone areas are the area type that all other areas connect to. It also accepts the following LSA message types: route summary, link updates, and route summaries.

Stub areas do not accept any external routes into the area (LSA type 5). These areas cannot contain Autonomous System Boundary Routers (ASBRs) unless the ASBR is also an Area Border Router (ABR). To send packets outside the area a default route is used.

Totally stubby areas do not accept external routes or summary routes from external areas. These areas cannot contain Autonomous System Boundary Routers (ASBRs) unless the ASBR is also an Area Border Router (ABR). To send packets outside the area a default route is used.

NSSA has the same benefits of stub and totally stubby areas, plus also accepts type 7 LSAs and ASBRs
. In order for an area to be a stub or a totally stub area, there are a number of criteria that must be met:

All routers within the area must be configured as stub router prior to forming a neighbor relationship.

There must be only one exit (ABR) from the area. If it is acceptable for packets to not take the optimal route to a destination, then this rule can be avoided if the ABRs both interject default routes into the area.

The area cannot be a backbone area.

The area cannot have virtual links traveling through it.

Routers configured as just ASBR are not permitted within the area.

The remainder of this tutorial and lab will focus on stub areas, totally stub areas, and NSSA.

Stub Areas:

After OSPF is configured, if an OSPF area is to be made a stub area this must be complete. For an area to be considered a stub area all routers need to be defined as stub routers. Stub areas are typically used in a hub and spoke topology. A common example would be a head office and remote office. The head office network would be the hub and the routers in the remote office would be considered the spoke routers. An example of this can be found in the diagram below:

In the diagram above RouterA is in the branch office stub area and RouterB's S0/0/0 interface is also in this area. RouterB's other interface is within the company's head office backbone (transit) area as is one of the interfaces of RouterC.

Once OSPF is properly enabled on RouterA and RouterB then these routers must be configured as stub routers. After this is done, the cost of the default router can be changed. The following commands are required to configure the router as a stub and to change the default cost:

areaarea-id stub [no summary]

The area-id parameter is used to identify the area and can either be a decimal number or a dotted decimal number.

The optional [no summary] parameter is what is used to ensure the ABR does not send summary LSAs into the area. This optional parameter will be discussed more in the next section of this tutorial.

area area-id default-cost cost

The area-id parameter is used to identify the area and can either be a decimal number or a dotted decimal number.

The cost parameter is used to change the default cost (1) of the summary route. The cost can be in the range of 0 to 16777215.

In the above figure RouterB is the ABR. To properly configure RouterA and RouterB the following commands will be required: (Based on the assumption that the interfaces have been properly configured.)

RouterA

router ospf 23
network 172.17.0.0 0.0.255.255 area 5
area 5 stub

RouterB

router ospf 23
network 172.18.0.0 0.0.255.255 area 0
network 172.17.0.0 0.0.255.255 area 5
area 5 stub

Totally Stubby Areas:

Totally stubby areas are a Cisco proprietary implementation. These areas block external router (LSA type 5), summary router (LSA type 3), and interarea routes (LSA type 4). The end result is even more memory saving.

To configure a totally stubby area, after OSPF has been configured, all routers within the area must be configured as stub routers with the area stub command. Then on the ABR the area stub command the no summary parameter must be issued. In the previous example, RouterB's configuration would be as follows:

router ospf 55
network 172.18.0.0 0.0.255.255 area 0
network 172.17.0.0 0.0.255.255 area 5
area 5 stub no-summary

NSSA:

NSSA (not so stubby area) was first introduced in RFC 3101 (supported by Cisco IOS 11.2) to allow the some external routes into the stubby area. This is achieved with a special LSA type (7). The NSSA ASBR creates this LSA and the ABR takes this LSA and make it into a type 5 LSA (default route) and passes this into the rest of the area. The steps to configuring NSSA is the same as stub area except instead of issuing the stub area command on all routers the following command needs to be issued on all routers:

area area-id nsaa [no-resdistribution] [default-information-originate [metric metric-value] [metric-type type-value]] [no-summary]

The area-id parameter is used to identify the NSSA and can be either a decimal number or a dotted decimal number.

The optional [no-resdistribution] parameter is an NSSA ABR and the redistribution routes are only to go into the standard area and not the NSSA area.

The optional default-information-originate parameter is what is used to generate type 7 LSAs.

The optional metric parameter sets the metric for default area. This value can be in the range of 0 to 16777214.

The optional metric-type parameter sets the metric type of default routes. Type 1 external routes and Type 2 external routes.

The no-summary parameter sets the area as an NSSA but without summary routes can be interjected into it.

Stub Area Verification:

To ascertain LSA details the show ip ospf database command is used.
To ascertain all routes the show ip route command is used.
To ascertain the OSPF area types the show ip ospf command is used.
To ascertain details of all type 7 LSA the show ip ospf database nssa-external command.

Lab Scenario

For this OSPF lab consider the following network:

Connect you lab as shown using the labeled IP addresses.

Lab Objectives

You are tasked to configure OSPF on Routers Beta and Charlie. The criterion that is to be met is the following:

• Configure RIPv2 on Alspha using your own IP addressing sceme. Area 49 is to only accept inter-area routes and a default route from RIP. RIP is to use a metric of 10. There are to be no external routes from the backbone. The OSPF process ID for router Beta is 13.

• Area 49 is to be configured as a Not so Stubby Area (NSSA). Charlie is to have a process-id of 25.

Lab Solution

Beta:

router ospf 13
redistribution rip metric 10
network 172.20.19.0 0.0.0.255 area 49
area 49 nssa


Charlie:

router ospf 25
network 172.21.0.0 0.0.255.255 area 0
network 172.20.19.0 0.0.0.255 area 49
area 49 nssa no-summary

Laboratorio CCNA exam 640-802 -configuracion basica-

Laboratorio CCNA: Realizar y verificar tareas de configuración inicial de switch, incluyendo la gestión de acceso remoto.

Exam: 640-802

Exam Objective: Perform and verify initial switch configuration tasks including remote access management

---

Contents

• Introduction
• Technology Background
• Lab Scenario
• Lab Objectives
• Lab Solution

---

Introduction

Like any IOS device, Cisco Switches allow some basic configuration for administrative ease and security etc. The commands are similar to those of a router but there are some basic differences due to the fact that Switch is a Layer 2 device.

Technology Background

For the CCNA the following basic configuration on Cisco Switches should be known:
Hostname: This name identifies the switch. You see this name on the command prompt, on cdp neighbors etc. Every device should have a unique name for the basic fact that you would want to ensure that you are making changes to the correct device. The global configuration command hostname <name> can be used for this.
Enable password/secret: The privilege mode of IOS is the most powerful mode. This mode provides access to all the commands on the device along with access to the configuration mode. Access to this mode should be secured using a password to prevent unauthorized changes to the device. There are two methods to secure this access - enable password and enable secret. Password is the old method which configures a password which can be seen in clear text when the configuration is viewed. Secret is the new method which configured an encrypted password so that the password cannot be seen in the configuration. The command to configure enable password is enable password <password>. The command to configure the enable secret is enable secret <password>. Both of these commands are global configuration mode command.
Banner: Banner is a text message displayed to anyone who logins or tries to login to the device. The following type of banners can be configured:

• exec : This banner is displayed after login
• login : This banner is displayed before the username and/or password prompt
• motd : Message of The Day. This is displayed before the login banner.

Banner can be configured using the banner <type> <delimiting character> <message> <delimiting characted> command. Example :
banner login # Unauthorized Access Prohibited #
Description: This is a text which can be added to an interface so that the administrator can identify the connection when looking at the configuration. This can be done using the description <text> interface command
Remote Access Management: There are three basic ways to connect to a Switch to manage the device - console, vty (telnet) and auxillary. Console is a special interface on the device which can be connected to using a Rollover cable and a terminal emulator such as hyperterminal. You need to be physically close to the device to use the console port. To remotely manage the device either IP based telnet can be used or a modem can be attached to the auxillary port. All the three methods can be secure using a password or even allow unauthenticated access.
To do this the respective lines (console, vty and auxillary) need to be configured with password and login needs to be enabled on them. Example :
line vty 0 4
password cisco
login
It should be noted here that there are 5 telnet lines available in most IOS devices - 0 to 4. This means that only 5 simultaneous connections are allowed to the Switch at any time.
Since the switches are layer 2 devices, their interfaces cannot have IP address. Switches have VLAN. Each VLAN has a Switch Virtual Interface (SVI) which is a layer 3 logical interface having the same identification number as the VLAN. These interfaces can have IP address and hosts belonging to that VLAN can connect to the switch using this IP address. SVIs are configured as shown below:
Switch(config)#interface vlan 1
Switch(config-if)#ip address <address> <mask>

Lab Scenario

For this lab you will need 3 Cisco switches. Your task is to configure the following:

• Hostnames as shown in Figure 1.
• Encrypted password for secure access to the privilege mode
• A message asking unauthorized access to the device before the login prompt
• ‘switchlab' as password for telnet connections to the device

Additionally, configure the switches such that users in VLAN 1 can telnet to the devices using 192.168.1.1-3/24 IP addresses.

Figure 1

Lab Objectives

• Configure Hostname, enable secret and banner login on all devices
• Configure line vty 0 4 with password
• Configure Interface Vlan 1 with IP Address

Lab Solution

Let's configure the switches with hostname, enable secret and banner login:
Switch(config)#hostname SwitchA
SwitchA(config)#enable secret switchlab
SwitchA(config)#banner login # Unauthorized access to this device is prohibited #

Switch(config)#hostname SwitchB
SwitchB(config)#enable secret switchlab
SwitchB(config)#banner login # Unauthorized access to this device is prohibited #

Switch(config)#hostname SwitchC
SwitchC(config)#enable secret switchlab
SwitchC(config)#banner login # Unauthorized access to this device is prohibited #
The vty lines need to be configured with a password and to allow login:
SwitchA(config)#line vty 0 4
SwitchA(config-line)#password switchlab
SwitchA(config-line)#login
SwitchB(config)#line vty 0 4
SwitchB(config-line)#password switchlab
SwitchB(config-line)#login
SwitchC(config)#line vty 0 4
SwitchC(config-line)#password switchlab
SwitchC(config-line)#login
Finally the SVI needs to be configured with an IP Address to allow users in VLAN 1 to telnet to the switch:
SwitchA(config)#interface vlan 1
SwitchA(config-if)#ip address 192.168.1.1 255.255.255.0
SwitchA(config-if)#no shut
SwitchB(config)#interface vlan 1
SwitchB(config-if)#ip address 192.168.1.2 255.255.255.0
SwitchB(config-if)#no shut
SwitchC(config)#interface vlan 1
SwitchC(config-if)#ip address 192.168.1.3 255.255.255.0
SwitchC(config-if)#no shut
The configuration can be verified by initiating a telnet to the Switch. The output will be similar to the following:
Unauthorized access to this device is prohibited
User Access Verification
Password:
References:
Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide - Administering the Switch
http://www.cisco.com/en/US/docs/switches/lan/catalyst2950/software/release/12.1_22_ea5/configuration/guide/swadmin.html

Avaya PA IP Office

Les recomiendo el producto de Avaya IP Office en cualquiera de sus modalidades, ya que lo he manejado y es un producto estrella de Avaya diseñado para la Pequeña-Mediana empresa.

Desarrollado desde la base específicamente para las pequeñas y medianas empresas, IP Office provee las capacidades de comunicaciones a las que están acostumbradas las grandes empresas —con la elegante simplicidad y la facilidad de uso que las pequeñas empresas consideran un "componente fundamental".

Esta solución, lo mejor de ambos mundos, ayuda a las empresas en crecimiento a diferenciarse de la competencia a través de una mayor productividad de los empleados, más bajos costos y un óptimo servicio al cliente.

Ademas de contar con entrenamiento especializado para su linea de productos IP; del cual cuento con las siguientes credenciales:

Datos clave

Avaya

es reconocida constantemente como un líder mundial

por expertos de tecnología y de la industria, y ha logrado

posiciones de liderazgo a nivel mundial en los campos:

• No. 1del mundo en Telefonía Empresarial

• No. 1 del mundo en Telefonía IP

• No. 1 en Telefonía en Europa, Medio Oriente y

África

• No. 1 del mundo en Centrales telefónicas

• No. 1 del mundo en Comunicaciones Unificadas

• No. 1 de los EE.UU en Servicios de Mantenimiento de CPE

• Situado en el Cuadrante de los Líderes dentro del

Cuadrante Mágico de la Telefonía

norteamericana

• Situado en el Cuadrante de los Líderes dentro del

Cuadrante Mágico de la Telefonía Corporativa para

Europa, Medio Oriente y África

•Situado en el Cuadrante de los Líderes dentro del

Cuadrante Mágico de la Infraestructura de Centros de

Contacto Norteamericana