Professional Documents
Culture Documents
All rights reserved. No part of this publication and file may be reproduced, stored in a retrieval system,
or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise,
without prior written permission of Professor Jenhui Chen (E-mail: jhchen@mail.cgu.edu.tw).
NDSL, Chang Gung University 1
Outline
DTE
DCE
Service
Provider
EIA/TIA-232 EIA/TIA-449 V.35 X.21 EIA-530
Network connections at the CSU/DSU
NMC in Region II
Centre in other region Moscow 64K Washington
64K
MTN circuit
Regional circuit 14.4-33.6K IMTN-MDCN
Interregional circuit 14.4-33.6K Novosibirsk (V.34) Khabarovsk CIR<32/768K>
Additional circuit (V.34)
NI No implementation Almaty 14.4-33.6K 14.4-33.6K 9.6K
14.4-33.6K (V.34) (V.34)
Non-IP link (V.34) 14.4-33.6K 14.4-33.6K
NI Via Moscow
IP link 14.4-33.6K V.34 Bishkek (V.34) 14.4-33.6K (V.34)
(V.34) PyongYang
Ulaanbaatar Tokyo
Id V.34
Ashgabad Id V.34 Tashkent CMA-VSAT
Offenbach IMTN-MDCN CMA-VSAT IMTN-MDCN
NI Frame Relay 75 Frame Relay
Baghdad CIR<8/8K> 75 CIR<48/48K>
NI
NI Tehran NI Dushanbe IMTN-MDCN
Beijing
IMTN-MDCN NI Frame Relay
Frame Relay 64K CIR<48/48K> Frame Relay
CIR<16/8K> NI Offenbach CIR<32/32K>
75
50 Kabul Frame Relay
Kuwait 9.6K CIR<16/16K>
64K 64K NI Thimpu
NI
Karachi 64K IMTN-MDCN 64K Seoul
64K Bahrain Frame Relay
New Delhi CIR<16/16K>
Jeddah 200 128K Frame Relay
50
Doha 64K CIR<16/16K>
64K
NI Kathmandu Moscow
Internet Hong Kong
50 Internet Abu- CMA-VSAT
Dhabi
64K 2.4K 100 ISDN 128K
Internet 100
64K 50
Hanoi
Algiers Macao
Dhaka Frame Relay
Muscat Cairo Internet CIR<16/16K>
Internet Internet Vientiane 9.6K
50 Frame Relay
Internet Cairo Yangon IMTN-MDCN
Sanaa CIR<16/16K>
64K Colombo 50 1200 CIR<32/32K>
Male 200 64K
Melbourne
Manila
Washington
75
Bangkok NI
Phnom Penh
2.4K Melbourne
Frame Relay
CIR<16/16K>
Regional Meteorological Telecommunication Network for Region II (Asia) Singapore Kuala Lumpur
User data
Layer 3
X.25 packet
header
LAPB LAPB
LAPB frame
header trailer
Implemented by
X.25 packet Implemented by end system but
level end system but not network
not network
Implemented by
end system and LAPF control LAPF control
network LAPB Implemented by
LAPF core LAPF core
Implemented end system and
by end system network
PHY layer and network PHY layer PHY layer
devices is established.
Data transfer—Data is transmitted between the DTE devices
terminated.
CONNECT
RELEASE
RELEASE COMPLETE
CSU/DSU
Presentation
Session
Transport
Network IP/IPX/AppleTalk, etc.
Data Link Frame Relay
EIA/TIA-232,
Physical EIA/TIA-449, V.35,
X.21, EIA/TIA-530
DLCI: 400
Local Access
Local Loop=64 kbps
Access
Loop=T1
PVC
Local Access
Loop=64 kbps
DLCI: 500
Frame Relay
Address Mapping
DLCI: 500 PVC 10.1.1.1
CSU/DSU
Inverse ARP or
Frame Relay map
Frame IP
Relay DLCI (500) (10.1.1.1)
Keepalive
ITU-T Q.933
Frame Relay Inverse ARP and LMI
Operation
1
Frame Relay
DLCI=100 Cloud DLCI=400
172.168.5.5 172.168.5.7
Frame Relay Inverse ARP and LMI
Operation
1
Frame Relay
DLCI=100 Cloud DLCI=400
172.168.5.5 172.168.5.7
172.168.5.5 172.168.5.7
172.168.5.5 172.168.5.7
Hello, I am 172.168.5.5.
4
Frame Relay Inverse ARP and LMI
Operation (cont.)
Frame Relay
DLCI=100 Cloud DLCI=400
172.168.5.5 172.168.5.7
Hello, I am 172.168.5.7.
4
Frame Relay Map
5
172.168.5.7 DLCI 100 Active
Frame Relay Inverse ARP and LMI
Operation (cont.)
Frame Relay
DLCI=100 Cloud DLCI=400
172.168.5.5 172.168.5.7
Hello, I am 172.168.5.7.
4
Frame Relay Map
5
172.168.5.7 DLCI 100 Active
Hello, I am 172.168.5.5.
6
Frame Relay Inverse ARP and LMI
Operation (cont.)
Frame Relay
DLCI=100 Cloud DLCI=400
172.168.5.5 172.168.5.7
Hello, I am 172.168.5.7.
4
Frame Relay Map
5
172.168.5.7 DLCI 100 Active
Hello, I am 172.168.5.5.
6
Keepalives Keepalives
7 7
Configuring Basic Frame Relay
HQ Branch
HQ Branch
Inverse ARP
• Enabled by default
• Does not appear in configuration output
Configuring a Static Frame Relay
Map
DLCI=110
IP address=10.16.0.1/24
p1r1
HQ Branch
DLCI=100
IP address=10.16.0.2/24
interface Serial1
ip address 10.16.0.1 255.255.255.0
encapsulation frame-relay
bandwidth 64
frame-relay map ip 10.16.0.2 110 broadcast
Verifying Frame Relay Operation
Router#show interface 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>
LMI Statistics for interface Serial0 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 113100 Num Status msgs Rcvd 113100
Num Update Status Rcvd 0 Num Status Timeouts 0
DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0
Full Mesh
Partial Mesh
2
AA C
C
3
D
Problem:
Broadcast traffic must be replicated for
each active connection
Resolving Reachability Issues
Subnet C
Solution:
Split horizon can cause problems in NBMA environments
Subinterfaces can resolve split horizon issues
A single physical interface simulates multiple logical interfaces
Configuring Subinterfaces
Point-to-Point
– Subinterfaces act as leased line
– Each point-to-point subinterface requires its own subnet
– Applicable to hub and spoke topologies
• Multipoint
– Subinterfaces act as NBMA network so they do not resolve the split
horizon issue
– Can save address space because uses single subnet
– Applicable to partial-mesh and full-mesh topology
Configuring Point-to-Point
Subinterfaces 10.17.0.1
s0.2 DLCI=110 10.17.0.2
A DL
s0.3 C
10.18.0.1 I=1 B
20
interface Serial0
no ip address
encapsulation frame-relay
! 10.18.0.2
interface Serial0.2 point-to-point
ip address 10.17.0.1 255.255.255.0
bandwidth 64 C
frame-relay interface-dlci 110
!
interface Serial0.3 point-to-point
ip address 10.18.0.1 255.255.255.0
bandwidth 64
frame-relay interface-dlci 120
!
Multipoint Subinterfaces
Configuration Example
= 120 B
DL CI
s2.2=10.17.0.1/24 s2.1=10.17.0.2/24
DLCI=130
RTR1
RTR3
DLCI=
140 s2.1=10.17.0.3/24
interface Serial2
no ip address RTR4
encapsulation frame-relay s2.1=10.17.0.4/24
!
interface Serial2.2 multipoint
ip address 10.17.0.1 255.255.255.0
bandwidth 64
frame-relay map ip 10.17.0.2 120 broadcast
frame-relay map ip 10.17.0.3 130 broadcast
frame-relay map ip 10.17.0.4 140 broadcast
Visual Objective
wg_pc_a
10.2.2.12
pod ro’s s0
e0/1 A 10.140.1.2
e0/2 e0 wg_ro_a B 10.140.2.2
10.2.2.3
s0 C 10.140.3.2
wg_sw_a 10.140.1.2/24
10.2.2.11
D 10.140.4.2
E 10.140.5.2
Frame Relay F 10.140.6.2
wg_pc_l G 10.140.7.2
10.13.13.12 H 10.140.8.2
wg_ro_l I 10.140.9.2
PPP with CHAP
e0/1
e0/2 e0 s0 J 10.140.10.2
FR K 10.140.11.2
10.13.13.3 10.140.12.2/24
wg_sw_l L 10.140.12.2
10.13.13.11
...
1. What is a DLCI?
2. What are two methods to map a network
layer address to a DLCI on a Cisco
router?
3. What are the advantages of configuring
Frame Relay subinterfaces?