Your SlideShare is downloading. ×
0
Icnd23 s06l02
Icnd23 s06l02
Icnd23 s06l02
Icnd23 s06l02
Icnd23 s06l02
Icnd23 s06l02
Icnd23 s06l02
Icnd23 s06l02
Icnd23 s06l02
Icnd23 s06l02
Icnd23 s06l02
Icnd23 s06l02
Icnd23 s06l02
Icnd23 s06l02
Icnd23 s06l02
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Icnd23 s06l02

72

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
72
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Establishing Serial Point-To-Point Connections Configuring Frame Relay © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-1
  • 2. Outline • • • • • • Overview Basic Frame Relay Network Configuration Static Frame Relay Map Configuration Frame Relay Subinterface Configuration Basic Frame Relay Operation Verification Summary © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-2
  • 3. Configuring Basic Frame Relay © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-3
  • 4. Configuring a Static Frame Relay Map © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-4
  • 5. Configuring 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. © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-5
  • 6. Configuring Point-to-Point Subinterfaces © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-6
  • 7. Multipoint Subinterfaces Configuration Example © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-7
  • 8. Verifying Frame Relay Operation Router# show interfaces type number • Displays information about Frame Relay DLCIs and the LMI Router# show interfaces s0 Serial0 is up, line protocol is up Hardware is HD64570 Internet address is 10.140.1.2/24 MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255 Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec) LMI enq sent 19, LMI stat recvd 20, LMI upd recvd 0, DTE LMI up LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0 LMI DLCI 1023 LMI type is CISCO frame relay DTE FR SVC disabled, LAPF state down Broadcast queue 0/64, broadcasts sent/dropped 8/0, interface broadcasts 5 Last input 00:00:02, output 00:00:02, output hang never Last clearing of "show interface" counters never Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops <Output omitted> © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-8
  • 9. Verifying Frame Relay Operation (Cont.) Router# show frame-relay traffic • Displays Frame Relay traffic statistics Router# show frame-relay traffic Frame Relay statistics: ARP requests sent 14, ARP replies sent 0 ARP request recvd 0, ARP replies recvd 10 © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-9
  • 10. Verifying Frame Relay Operation (Cont.) Router# show frame-relay lmi [type number] • Displays LMI statistics rame-relay lmi for interface Serial0 (Frame Relay DTE) LMI TYPE = CISCO bered info 0 Invalid Prot Disc 0 Call Ref 0 Invalid Msg Type 0 s Message 0 Invalid Lock Shift 0 mation ID 0 Invalid Report IE Len 0 t Request 0 Invalid Keep IE Len 0 q. Sent 113100 Num Status msgs Rcvd 113100 atus Rcvd 0 Num Status Timeouts 0 © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-10
  • 11. Verifying Frame Relay Operation (Cont.) Router# show frame-relay pvc [type number [dlci]] • Displays PVC statistics Router# show frame-relay pvc 100 PVC Statistics for interface Serial0 (Frame Relay DTE) DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0 input pkts 28 output pkts 10 in bytes 8398 out bytes 1198 dropped pkts 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 10 out bcast bytes 1198 pvc create time 00:03:46, last time pvc status changed 00:03:47 © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-11
  • 12. Verifying Frame Relay Operation (Cont.) Router# show frame-relay map • Displays the current Frame Relay map entries Router# clear frame-relay-inarp • Clears dynamically created Frame Relay maps, created by using Inverse ARP Router# show frame-relay map Serial0 (up): ip 10.140.1.1 dlci 100(0x64,0x1840), dynamic, broadcast,, status defined, active Router# clear frame-relay-inarp Router# show frame map Router# © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-12
  • 13. Troubleshooting Basic Frame Relay Operations Router# debug frame-relay lmi Frame Relay LMI debugging is on Displaying all Frame Relay LMI data Router# 1w2d: Serial0(out): StEnq, myseq 140, yourseen 139, DTE up 1w2d: datagramstart = 0xE008EC, datagramsize = 13 1w2d: FR encap = 0xFCF10309 1w2d: 00 75 01 01 01 03 02 8C 8B 1w2d: 1w2d: Serial0(in): Status, myseq 140 1w2d: RT IE 1, length 1, type 1 1w2d: KA IE 3, length 2, yourseq 140, myseq 140 1w2d: Serial0(out): StEnq, myseq 141, yourseen 140, DTE up 1w2d: datagramstart = 0xE008EC, datagramsize = 13 1w2d: FR encap = 0xFCF10309 1w2d: 00 75 01 01 01 03 02 8D 8C 1w2d: 1w2d: Serial0(in): Status, myseq 142 1w2d: RT IE 1, length 1, type 0 1w2d: KA IE 3, length 2, yourseq 142, myseq 142 1w2d: PVC IE 0x7 , length 0x6 , dlci 100, status 0x2 , bw 0 • Displays LMI debug information © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-13
  • 14. Summary • A basic Frame Relay configuration assumes that there are one or more physical interfaces, and that LMI and Inverse ARP are running on the remote routers. In this type of environment, the LMI notifies the router about the available DLCIs. • When the remote router does not support Inverse ARP or when you want to control routed broadcast traffic, you must statically define the address-to-DLCI table. • You can configure Frame Relay subinterfaces in either point-to-point or multipoint mode. • After you configure Frame Relay, you can verify that the connections are active using the available show commands. • The debug frame-relay lmi command can be used to determine whether the router and the Frame Relay switch are sending and receiving LMI packets properly. The show interfaces serial command can be used to troubleshoot some common Frame Relay network problems. © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-14
  • 15. © 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-15

×