Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Frame Relay es una de conmutacin de paquetes, la conexin orientado a servicios WAN. Se opera en la capa de enlace de datos del modelo OSI modelo de referencia. Frame Relay utiliza un subconjunto de la de alto nivel protocolo de control de enlace de datos (HDLC) llamado Enlace Procedimiento de acceso para Frame Relay (LAPF). Marcos transportan datos entre dispositivos de usuario llamado equipo terminal de datos (DTE), y los datos Rick Graziani graziani@cabrillo.edu
Access circuits
una red especfica y por lo general se encuentran en las instalaciones del cliente. El cliente tambin puede poseer este equipo. Ejemplos de dispositivos DTE son routers y dispositivos de acceso Frame Relay (FRAD). Un FRAD es un dispositivo especializado diseado para proporcionar una conexin entre una LAN y una WAN Frame Relay.
5
10
11
12
DLCI
13
DLCI
Inside the cloud, your Frame Relay provider sets up the DLCI numbers
to be used by the routers for establishing PVCs.
Rick Graziani graziani@cabrillo.edu 14
15
per VC
20
LMI es un estndar de sealizacin entre el DTE y el switch Frame Relay. LMI se encarga de gestionar la conexin y el mantenimiento de el estado entre los dispositivos. LMI incluye: Un mecanismo de keepalive, que verifica que los datos fluyan Un mecanismo de multidifusin, lo que proporciona el servidor de red (enrutador) con su DLCI local. El direccionamiento multicast, que puede dar DLCI globales en lugar de importancia local en las redes Frame Relay (no es comn). Un mecanismo de estado, que proporciona un estado en curso en los DLCI se sabe que el interruptor
21
LMI
LMI
Con el fin de ofrecer los primeros servicios de LMI a los clientes tan
pronto como sea posible, los vendedores y los comits de estndares trabajaron por separado para desarrollar y desplegar LMI en las implementaciones de Frame Relay temprana. El resultado es que hay tres tipos de LMI, ninguno de los cuales es compatible con los otros. Cisco, StrataCom, Northern Telecom y Digital Equipment Corporation (Gang of Four) dio a conocer un tipo de LMI, mientras que el ANSI y UIT-T cada lanzaron sus propias versiones. El tipo de LMI debe coincidir entre el switch Frame Relay proveedor y Rick el Graziani graziani@cabrillo.edu dispositivo DTE cliente.
22
LMI
LMI
In Cisco IOS releases prior to 11.2, the Frame Relay interface must be
manually configured to use the correct LMI type, which is furnished by the service provider. If using Cisco IOS Release 11.2 or later, the router attempts to automatically detect the type of LMI used by the provider switch. This automatic detection process is called LMI autosensing. No matter which LMI type is used, when LMI autosense is active, it sends out a full status request to the provider switch.
23
LMI
The Frame Relay switch uses LMI to report the status of configured
PVCs. The three possible PVC states are as follows: Active state Indicates that the connection is active and that routers can exchange data. Inactive state Indicates that the local connection to the Frame Relay switch is working, but the remote router connection to the Frame Relay switch is not working. Deleted state Indicates that no LMI is being received from the Frame Relay switch, or that there is no service between the CPE router and Frame Relay switch.
Rick Graziani graziani@cabrillo.edu 24
Manual
Manual: Administrators use a frame relay map statement. Dynamic Inverse Address Resolution Protocol (I-ARP) provides a given DLCI and requests next-hop protocol addresses for a specific connection. The router then updates its mapping table and uses the information in the table to forward packets on the correct route.
25
My IP is 1.1.1.2y Una vez que el router aprende del interruptor sobre PVC disponibles sus correspondientes DLCI, el router puede enviar una solicitud ARP inverso al otro extremo del PVC. (a menos mapeado estticamente ms tarde) Para cada protocolo soportado y configurado en la interfaz, el router enva una solicitud ARP inverso para cada DLCI. (a menos que asigna estticamente) En efecto, la solicitud ARP inverso pide a la estacin remota por su direccin de la Capa 3. Al mismo tiempo, proporciona el sistema remoto con la direccin del sistema local Capa 3. La informacin de retorno de la ARP inverso se utiliza entonces para construir el mapa de Frame Relay..
26
27
cisco - Default
29
DLCI 101
HubCity(config)# interface serial 0 HubCity(config-if)# ip address 172.16.1.2 255.255.255.0 HubCity(config-if)# encapsulation frame-relay Spokane(config)# interface serial 0 Spokane(config-if)# ip address 172.16.1.1 255.255.255.0 Spokane(config-if)# encapsulation frame-relay
30
DLCI 101
Cisco Router est listo para actuar como un dispositivo DTE FrameRelay.
El siguiente proceso: 1. La interfaz est activada. 2. El switch Frame-Relay anuncia el DLCI configurado (s) en el
router. 3. ARP inverso se lleva a cabo para asignar direcciones de capa de red remotos para el DLCI (s) local.
31
Inverse ARP
172.16.1.2
DLCI 101
HubCity# show frame-relay map Serial0 (up): ip 172.16.1.1 dlci 101, dynamic, broadcast, status defined, active
dynamic refers to the router learning the IP address via Inverse ARP The DLCI 101 is configured on the Frame Relay Switch by the
DLCI 101
If the environment does not support LMI autosensing and Inverse ARP,
a Frame Relay map must be manually configured. Use the frame-relay map command to configure static address mapping. Once a static map for a given DLCI is configured, Inverse ARP is disabled on that DLCI. The broadcast keyword is commonly used with the frame-relay map command. The broadcast keyword: Forwards broadcasts when multicasting is not enabled.
34
Remote IP Address
Local DLCI
35
encapsulacin y el estado de la Capa 1 y Capa 2. Tambin incluye informacin sobre la multidifusin DLCI, los DLCI utilizado en el marco de la interfaz serial del rel configurado y el DLCI utilizado para la sealizacin de LMI.
37
38
40
41
clear frame-relay-inarp
42
Use the debug frame-relay lmi command to determine whether the router and the Frame Relay switch are sending and receiving LMI packets properly.
Rick Graziani graziani@cabrillo.edu 43
FYI ONLY The possible values of the status field are as follows: 0x0 Added/inactive means that the switch has this DLCI programmed but for some reason it is not usable. The reason could possibly be the other end of the PVC is down. 0x2 Added/active means the Frame Relay switch has the DLCI and everything is operational. 0x4 Deleted means that the Frame Relay switch does not have this DLCI programmed for the router, but that it was programmed at some point in the past. This could also be caused by the DLCIs being reversed on the router, or by the PVC being deleted by the service provider in the Frame Relay cloud.
Rick Graziani graziani@cabrillo.edu 44
45
An NBMA network is the opposite of a broadcast network. On a broadcast network, multiple computers and devices are
attached to a shared network cable or other medium. When one computer transmits frames, all nodes on the network "listen" to the frames, but only the node to which the frames are addressed actually receives the frames. Thus, the frames are broadcast. A nonbroadcast multiple access network is a network to which multiple computers and devices are attached, but data is transmitted directly from one computer to another over a virtual circuit or across a switching fabric. The most common examples of nonbroadcast network media include ATM (Asynchronous Transfer Mode), frame relay, and X.25. http://www.linktionary.com/
46
Star Topology
Full Mesh
Full Mesh Topology Number of Number of Connections PVCs -----------------------------2 1 4 6 6 15 8 28 10 45
In a full mesh topology, all routers have PVCs to all other destinations. This method, although more costly than hub and spoke, provides direct
connections from each site to all other sites and allows for redundancy. For example, when one link goes down, a router at site A can reroute traffic through site C. As the number of nodes in the full mesh topology increases, the topology becomes increasingly more expensive. The formula to calculate the total number of PVCs with a fully meshed WAN is [n(n - 1)]/2, where n is the number of nodes.
48
This is known as a Hub and Spoke Topology, where the Hub router relays information between the Spoke routers. Limits the number of PVCs needed as in a full-mesh topology (coming).
Hub Router
DLCI 101 172.16.1.2 DLCI 112
Spoke Routers
DLCI 112
50
DLCI 112
HubCity# show frame-relay map Serial0 (up): ip 172.16.1.1 dlci 101, dynamic, broadcast, status defined, active Serial0 (up): ip 172.16.1.3 dlci 112, dynamic, broadcast, status defined, active Spokane# show frame-relay map Serial0 (up): ip 172.16.1.2 dlci 102, dynamic, broadcast, status defined, active Spokomo# show frame-relay map Serial0 (up): ip 172.16.1.2 dlci 211, dynamic, broadcast, status defined, active
Rick Graziani graziani@cabrillo.edu 51
DLCI 112
Can HubCity ping both Spokane and Spokomo? Yes! Can Spokane and Spokomo ping HubCity? Yes! Can Spokane and Spokomo ping each other? No! The Spoke
routers serial interfaces (Spokane and Spokomo) drop the ICMP packets because there is no DLCI-to-IP address mapping for the destination address.
Solutions to the limitations of Inverse ARP 1. Add an additional PVC between Spokane and Spokomo (Full Mesh) 2. Configure Frame-Relay Map Statements 3. Configure Point-to-Point Subinterfaces.
Rick Graziani graziani@cabrillo.edu 53
Instead of using additional PVCs, Frame-Relay map statements can be used to: Statically map local DLCIs to an unknown remote network layer addresses. Also used when the remote router does not support Inverse ARP
54
HubCity interface Serial0 ip address 172.16.1.2 255.255.255.0 encapsulation frame-relay (Inverse-ARP still works here) Spokane interface Serial0 ip address 172.16.1.1 255.255.255.0 encapsulation frame-relay frame-relay map ip 172.16.1.3 102 frame-relay map ip 172.16.1.2 102 Spokomo interface Serial0 ip address 172.16.1.3 255.255.255.0 encapsulation frame-relay frame-relay map ip 172.16.1.1 211 frame-relay map ip 172.16.1.2 211
DLCI 112
Notice that the routers are configured to use either IARP or Frame Relay maps. Using both on the same interface will cause problems.
Rick Graziani graziani@cabrillo.edu 55
DLCI 112
The previous configuration works fine and all routers can ping each
other. What if we were to mix IARP and Frame Relay map statements on the same router for the same DLCI? There would be a problem!
56
DLCI 112
Spokane and Spokomo relying on IARP for mapping DLCI to IP address of Hub City.
Rick Graziani graziani@cabrillo.edu 57
58
Good News: Everything looks fine! Now all routers can ping each other! Bad News: Problem when using Frame-Relay map statements AND Inverse ARP. This will only work until the router is reloaded, here is why...
Rick Graziani graziani@cabrillo.edu 59
Frame-Relay Map Statement Rule: When a Frame-Relay map statement is configured for a particular protocol (IP, IPX, ) Inverse-ARP will be disabled for that specific protocol, only for the DLCI referenced in the Frame-Relay map statement.
60
The previous solution worked only because the Inverse ARP had taken place between Spokane and HubCity, and between Spokomo and HubCity, before the Frame-Relay map statements were added. (The Frame-Relay map statement was added after the Inverse ARP took place.) Both the Inverse-ARP and Frame-Relay map statements are in effect. Once the router is reloaded (rebooted) the Inverse-ARP will never occur because of the configured Frame-Relay map statement. (assuming the running-config is copied to the startup-config) Rule: Inverse-ARP will be disabled for that specific protocol, for the DLCI referenced in the Frame-Relay map statement.
61
62
Spokane and Spokomo can no longer ping HubCity because they do not have a dlci-to-IP mapping for the others IP address!
63
HubCity interface Serial0 ip address 172.16.1.2 255.255.255.0 encapsulation frame-relay (Inverse-ARP still works here) Spokane interface Serial0 ip address 172.16.1.1 255.255.255.0 encapsulation frame-relay frame-relay map ip 172.16.1.3 102 frame-relay map ip 172.16.1.2 102 Spokomo interface Serial0 ip address 172.16.1.3 255.255.255.0 encapsulation frame-relay frame-relay map ip 172.16.1.1 211 frame-relay map ip 172.16.1.2 211
DLCI 112
Solution: Do not mix IARP with Frame Relay maps statements. If need be use Frame-Relay map statements instead of IARP.
Rick Graziani graziani@cabrillo.edu 64
The Central router must receive the broadcast from Branch A and then
send its own broadcast to Branch B. In this example, there are problems with routing protocols because of the split horizon rule. A full mesh topology with virtual circuits between every site would solve this problem, but having additional virtual circuits is more costly and does not scale well.
66
Using a hub and spoke topology, the split horizon rule reduces the
chance of a routing loop with distance vector routing protocols. It prevents a routing update received on an interface from being forwarded through the same interface. If the Central router learns about Network X from Branch A, that update is learned via S0/0. According to the split horizon rule, Central could not update Branch B or Branch C about Network X. This is because that update would be sent out the S0/0 interface, which is the same interface that received the update.
67
To remedy this situation, turn off split horizon for IP. Of course, with split horizon disabled, the protection it affords against
routing loops is lost. Split horizon is only an issue with distance vector routing protocols like RIP, IGRP and EIGRP. It has no effect on link state routing protocols like OSPF and IS-IS.
68
Mulitpoint
Point-to-point
Mulitpoint
Point-to-point
71
Router(config-if)#interface serial number subinterface-number {multipoint | point-to-point} Router(config-subif)# frame-relay interface-dlci dlci-number
73
With multipoint subinterfaces, they are listed as an inverse ARP entry, dynamic
Router#show frame-relay map Serial0 (up): ip 172.30.2.1 dlci, 301 (0x12D, 0x48D0), dynamic,, broadcast status defined, active
74
Point-to-point Subinterfaces
Mulitpoint
Point-to-point Point-to-point subinterfaces are like conventional point-to-point interfaces (PPP, ) and have no concept of (do not need): Inverse-ARP mapping of local DLCI address to remote network address (frame-relay map statements) Frame-Relay service supplies multiple PVCs over a single physical interface and point-to-point subinterfaces subdivide each PVC as if it were a physical point-to-point interface. Point-to-point subinterfaces completely bypass the local DLCI to remote network address mapping issue.
Rick Graziani graziani@cabrillo.edu 75
Point-to-point Subinterfaces
Mulitpoint
Point-to-point With point-to-point subinterfaces you: Cannot have multiple DLCIs associated with a single point-to-point subinterface Cannot use frame-relay map statements Cannot use Inverse-ARP
Can use the frame-relay interface dlci statement (for both point-topoint and multipoint)
Rick Graziani graziani@cabrillo.edu 76
Point-to-point Subinterfaces
Each subinterface is on a separate network or subnet with a single remote router at the other end of the PVC.
77
172.30.1.1/24
172.30.2.1/24
172.30.3.1/24
S0
S1
S2
172.30.1.2/24
172.30.2.2/24
172.30.3.2/24
Site A
Site B
Site C
Point-to-point Subinterfaces
Saint Seiya Concierto 25 Aniversario. KANAN Una sola subinterfaz se utilizaGRUPO para establecer una conexin de PVC a otra fsica o subinterfaz Parte 5 en un router remoto. En este caso, las interfaces podran ser: En la misma subred y Cada interfaz tendra un solo DLCI Cada conexin de punto a punto es su propia subred. En este ambiente, las emisiones no son un problema porque los
routers son punto a punto y actan como una lnea arrendada.
Rick Graziani graziani@cabrillo.edu 79
Point-to-point Subinterfaces
Configuracin de subinterfaz punto a punto, mnimo de dos rdenes: Router (config) # interface punto a punto Serial0.1 Router (config-subif) # frame-relay interface-dlci dlci
Reglas: 1. No se realizarn manifestaciones mapa Frame-Relay se pueden utilizar con el punto-a-punto subinterfaces. 2. Uno y slo un DLCI puede estar asociado con una sola subinterfaz punto-a-punto
Por cierto, la encapsulacin se realiza slo en la interfaz fsica: interfaz Serial0 Rick Graziani graziani@cabrillo.edu
80
Each subinterface on Hub router requires a separate subnet (or network) Each subinterface on Hub router is treated like a regular physical point-to-point interface, so split horizon does not need to be disabled.
Interface Serial0 (for all routers) encapsulation frame-relay no ip address HubCity interface Serial0.301 point-to-point ip address 172.16.1.1 255.255.255.0 encapsulation frame-relay frame-relay interface-dlci 301 interface Serial0.302 point-to-point ip address 172.16.2.1 255.255.255.0 encapsulation frame-relay frame-relay interface-dlci 302
DLCI 103
DLCI 203
Spokane interface Serial0.103 point-to-point ip address 172.16.1.2 255.255.255.0 frame-relay interface-dlci 103 Spokomo interface Serial0.203 point-to-point ip address 172.16.2.2 255.255.255.0 frame-relay interface-dlci 203
Rick Graziani graziani@cabrillo.edu
Two subnets
81
Multipoint Subinterfaces
Mulitpoint
Point-to-point
Comparte muchas de las mismas caractersticas que una interfaz Frame-Relay fsica Con subinterfaz multipunto se puede tener: puede tener mltiples DLCI asignados. puede utilizar la interfaz del mapa y frame relay declaraciones DLCI puede utilizar ARP inverso Recuerde que con el punto-a-punto subinterfaces usted: no puede tener mltiples DLCI asociados a una sola subinterfaz punto a punto no puede utilizar frame relay declaraciones del mapa no puede utilizar ARP inverso (se puede utilizar la sentencia dlci interfaz frame relay tanto de punto a punto y multipunto) Rick Graziani graziani@cabrillo.edu
82
Multipoint subinterfaces
Each subinterface is on a separate network or subnet but may have multiple connections, with a different DLCI for each connection.
83
172.30.1.1/24
172.30.2.1/24
172.30.3.1/24
S0
S1
S2
172.30.1.2/24
172.30.3.3/24
Site A1
172.30.1.3/24 172.30.2.2/24 172.30.2.3/24
Site C2
172.30.3.2/24
Site A2
DLCI 302
DLCI 103
DLCI 203
Spokomo interface Serial0.1 point-to-point ip address 172.16.3.2 255.255.255.0 frame-relay interface-dlci 203
Serial 0 172.16.3.1
One subnet
Serial 0 172.16.3.2
85