Module 55
description
Transcript of Module 55
-
ICND1 v1.01-1http://vnexperts.net
LAN Extension into a WAN
Establishing a WAN Connection with Frame Relay
-
ICND1 v1.01-2http://vnexperts.net
Frame Relay Overview
Connections made by virtual circuits Connection-oriented service
-
ICND1 v1.01-3http://vnexperts.net
Frame Relay Terminology
-
ICND1 v1.01-4http://vnexperts.net
Frame Relay default: NBMA
Selecting a Frame Relay Topology
-
ICND1 v1.01-5http://vnexperts.net
Resolving NBMA Reachability Issues
Split horizon can cause problems in NBMA environments. Solution: subinterfaces A single physical interface simulates multiple logical interfaces.
-
ICND1 v1.01-6http://vnexperts.net
LMI receives locally significant DLCI from the Frame Relay switch. Inverse ARP maps the local DLCI to the remote router network
layer address.
Frame Relay Address Mapping
-
ICND1 v1.01-7http://vnexperts.net
Frame Relay Signaling
Cisco supports three LMI standards: Cisco ANSI T1.617 Annex D ITU-T Q.933 Annex A
-
ICND1 v1.01-8http://vnexperts.net
Stages of Inverse ARP and LMI Operation
-
ICND1 v1.01-9http://vnexperts.net
Stages of Inverse ARP and LMI Operation (Cont.)
-
ICND1 v1.01-10http://vnexperts.net
Configuring Basic Frame Relay
-
ICND1 v1.01-11http://vnexperts.net
Configuring a Static Frame Relay Map
Configure a static Frame Relay map when: A Frame Relay peer does not support Inverse ARP You want to control broadcast traffic across a PVC You want to have different Frame Relay encapsulations across
PVCs
-
ICND1 v1.01-12http://vnexperts.net
Configuring Frame Relay Subinterfaces
Point-to-point Subinterfaces act like leased lines. Each point-to-point subinterface requires its own subnet. Point-to-point is applicable to hub-and-spoke topologies.
Multipoint Subinterfaces act like NBMA networks, so they do not resolve
the split-horizon issues. Multipoint can save address space because it uses a single
subnet. Multipoint is applicable to partial-mesh and full-mesh
topologies.
-
ICND1 v1.01-13http://vnexperts.net
Configuring Frame Relay Point-to-Point Subinterfaces
-
ICND1 v1.01-14http://vnexperts.net
Configuring Frame Relay Multipoint Subinterfaces
-
ICND1 v1.01-15http://vnexperts.net
Verifying Frame Relay Operation
RouterX# show interfaces type number Displays information about Frame Relay DLCIs and the LMI
RouterX# show interfaces s0Serial0 is up, line protocol is upHardware is HD64570Internet address is 10.140.1.2/24MTU 1500 bytes, BW 1544 Kbit, DLY 20000 useEncapsulation FRAME-RELAY, loopback not sLMI enq sent 19, LMI stat recvd 20, LMI upd reLMI enq recvd 0, LMI stat sent 0, LMI upd sentLMI DLCI 1023 LMI type is CISCO frame relay
-
ICND1 v1.01-16http://vnexperts.net
Verifying Frame Relay Operation (Cont.)
RouterX# show frame-relay lmi [type number] Displays LMI statistics
RouterX# show frame-relay lmi
LMI Statistics for interface Serial0 (Frame RelaInvalid Unnumbered info 0 Invalid Prot Disc 0Invalid dummy Call Ref 0 Invalid Msg Type 0Invalid Status Message 0 Invalid Lock Shift 0Invalid Information ID 0 Invalid Report IE Len 0Invalid Report Request 0 Invalid Keep IE Len 0
-
ICND1 v1.01-17http://vnexperts.net
Displays LMI debug information
Verifying Frame Relay Operation (Cont.)
RouterX# debug frame-relay lmiFrame Relay LMI debugging is onDisplaying all Frame Relay LMI dataRouterX#1w2d: Serial0(out): StEnq, myseq 140, your1w2d: datagramstart = 0xE008EC, datagram1w2d: FR encap = 0xFCF103091w2d: 00 75 01 01 01 03 02 8C 8B1w2d:1w2d: Serial0(in): Status, myseq 1401w2d: RT IE 1, length 1, type 11w2d: KA IE 3, length 2, yourseq 140, myse
-
ICND1 v1.01-18http://vnexperts.net
Verifying Frame Relay Operation (Cont.)
RouterX# show frame-relay pvc [type number [ Displays PVC statistics
RouterX# show frame-relay pvc 100
PVC Statistics for interface Serial0 (Frame Rela
DLCI = 100, DLCI USAGE = LOCAL, PVC STATU
input pkts 28 output pkts 10 in byout bytes 1198 dropped pkts 0 in in BECN pkts 0 out FECN pkts 0 ou
-
ICND1 v1.01-19http://vnexperts.net
Verifying Frame Relay Operation (Cont.)
RouterX# clear frame-relay-inarp
RouterX# show frame-relay map
Clears dynamically created Frame Relay maps, created by using Inverse ARP
Displays the current Frame Relay map entries
RouterX# show frame-relay mapSerial0 (up): ip 10.140.1.1 dlci 100(0x64,0x1840
broadcast,, status defined, activeRouterX# clear frame-relay-inarpRouterX# show frame mapRouterX#
-
ICND1 v1.01-20http://vnexperts.net
Visual Objective 8-1: Establishing a Frame Relay WAN
WG Router s0/0
A 10.140.1.2B 10.140.2.2C 10.140.3.2D 10.140.4.2E 10.140.5.2F 10.140.6.2G 10.140H 10.140.8.2
-
ICND1 v1.01-21http://vnexperts.net
Summary
Frame Relay PVCs are identified with DLCIs, and the status of the PVCs are reported via the LMI protocol. Frame Relay point-to-point subinterfaces require a separate
subnet for each PVC, and multipoint subinterfaces share a single subnet with frame relay peers. To display connectivity with the Frame Relay provider, use the
show frame-relay lmi command. To display connectivity with the Frame Relay peer, use the show frame-relay pvc and show frame-relay map commands.
LAN Extension into a WANFrame Relay OverviewFrame Relay TerminologySelecting a Frame Relay TopologyResolving NBMA Reachability IssuesFrame Relay Address MappingFrame Relay SignalingStages of Inverse ARP and LMI OperationStages of Inverse ARP and LMI Operation (Cont.)Configuring Basic Frame RelayConfiguring a Static Frame Relay MapConfiguring Frame Relay SubinterfacesConfiguring Frame Relay Point-to-Point SubinterfacesConfiguring Frame Relay Multipoint SubinterfacesVerifying Frame Relay OperationVerifying Frame Relay Operation (Cont.)Verifying Frame Relay Operation (Cont.)Verifying Frame Relay Operation (Cont.)Verifying Frame Relay Operation (Cont.)Visual Objective 8-1: Establishing a Frame Relay WANSummary