RE: frame-relay between directly connected serial interfaces..

From: Kenneth Wygand (KWygand@customonline.com)
Date: Mon Jul 12 2004 - 17:31:04 GMT-3


Group,
 
Is this more of a "can it be done"-type scenario, or is there any reasonable consideration that something like this can be on the lab? I think that would be kind've cruel... ;-)
 
Thoughts?
Ken

________________________________

From: nobody@groupstudy.com on behalf of Tom Martin
Sent: Mon 7/12/2004 3:59 PM
To: ccielab@groupstudy.com
Subject: RE: frame-relay between directly connected serial interfaces..

Hello,

A router interface can act as DCE and be a L3 endpoint without problems. Being configured as Frame Relay DCE is layer 2 and only affects Frame Relay keepalives, LMI generation, etc. This is no different than having a back-to-back cable connecting two router interfaces with one acting as DCE and providing clock.

The only time that a Frame Relay DCE interface can't be an L3 endpoint is when it's switching Frame-Relay between interfaces (via frame-relay route commands). For a back-to-back configuration, all that's required is one side provide clock (L1 DCE), one side be Frame Relay DCE (it doesn't have to be the same router that's providing clock) and that they use a common DLCI.

The following is a valid Frame Relay back-to-back configuration taken out of my lab using Frame Relay inverse ARP. Also notice that you don't have to disable LMI keepalive:

r1

---
hostname r1
interface Serial0
  encapsulation frame-relay
  ip address 192.168.12.1 255.255.255.0
!

r2 --- hostname r2 frame-relay switching interface Serial0/2 ip address 192.168.12.2 255.255.255.0 encapsulation frame-relay clockrate 57600 frame-relay interface-dlci 100 frame-relay intf-type dce !

r1#show frame-relay map Serial0 (up): ip 192.168.12.2 dlci 100(0x64,0x1840), dynamic, broadcast,, status defined, active

r1#ping 192.168.12.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.24.4, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 32/32/32 ms

r1#show frame-relay lmi 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 32 Num Status msgs Rcvd 32 Num Update Status Rcvd 0 Num Status Timeouts 0

-- Tom

-----Original Message----- From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Koen Peetermans Sent: Monday, July 12, 2004 3:38 PM To: 'Scott Morris'; 'Richard Dumoulin'; 'Wang Dehong-DWANG1'; ccielab@groupstudy.com Subject: RE: frame-relay between directly connected serial interfaces..

Scott, I think there is a way around, create a subinterface on the router acting as DCE: This way you can do both switching and being a L3 endpoint at the same time.

R3 interface Serial0/0 no ip address encapsulation frame-relay clockrate 2000000 frame-relay intf-type dce interface Serial0/0.1 point-to-point ip address 174.1.13.3 255.255.255.0 frame-relay interface-dlci 103

R1 interface Serial1 ip address 174.1.13.1 255.255.255.0 encapsulation frame-relay end

R1#sh frame map Serial1 (up): ip 174.1.13.3 dlci 103(0x67,0x1870), dynamic, broadcast,, status defined, active R3#ping 174.1.13.1

Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 174.1.13.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms R3#sh ip eigrp neighbors IP-EIGRP neighbors for process 1024 H Address Interface Hold Uptime SRTT RTO Q Seq Type (sec) (ms) Cnt Num 0 174.1.13.1 Se0/0.1 156 00:01:15 217 1302 0 47 Rack1R3#

-----Original Message----- From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Scott Morris Sent: maandag 12 juli 2004 21:03 To: 'Richard Dumoulin'; 'Wang Dehong-DWANG1'; ccielab@groupstudy.com Subject: RE: frame-relay between directly connected serial interfaces..

If you use no keepalive, this is what actually avoids using LMI. Don't forget to use the same DLCI on each end. DCE/DTE doesn't matter without LMI (other than clockrate things).

If you use frame-relay switching, then you also have to consider that the interface with the "frame relay route" is NOT participating as an actual reeachable L3 interface. It's in an L2 switching mode per your commands. So consider that and the effects it will have on your topology. (e.g. making things not usable!)

Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, CISSP, JNCIP, et al. IPExpert CCIE Program Manager IPExpert Sr. Technical Instructor swm@emanon.com/smorris@ipexpert.net http://www.ipexpert.net

-----Original Message----- From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Richard Dumoulin Sent: Monday, July 12, 2004 2:48 PM To: Wang Dehong-DWANG1; ccielab@groupstudy.com Subject: RE: frame-relay between directly connected serial interfaces..

So this is a back to back connection ? If yes then I see two way you can do this.

First, no keepalive at both ends

Second, Configure one end with frame-relay switching (global conf) and frame-relay intf-type dce (interface conf)

--Richard

-----Original Message----- From: Wang Dehong-DWANG1 [mailto:Dehong.Wang@motorola.com] Sent: lunes, 12 de julio de 2004 19:34 To: ccielab@groupstudy.com Subject: frame-relay between directly connected serial interfaces..

I have another question and need some helps.. R5 and R3 are connected with a serial connection(the connection is good, ppp works fine). I want to have frame-relay running between them but with no luck so far. The interfaces were up on both ends, but both routers never learned /32 host route from other ends, so I can not ping other end at all.

Did I miss anything or did something wrong?? thanks.

- Dehong

========= R5 ===========

frame-relay switching

interface Serial0/1 no ip address encapsulation frame-relay IETF clockrate 72000 frame-relay intf-type dce

interface Serial0/1.1 point-to-point ip unnumbered Loopback0 frame-relay interface-dlci 503

interface Loopback0 ip address 172.16.105.1 255.255.255.0

R5#sh frame-relay map Serial0/1.1 (up): point-to-point dlci, dlci 503(0x1F7,0x7C70), broadcast status defined, active

R5#sh frame-relay pvc

PVC Statistics for interface Serial0/0 (Frame Relay DTE)

PVC Statistics for interface Serial0/1 (Frame Relay DCE)

Active Inactive Deleted Static Local 1 0 0 0 Switched 0 0 0 0 Unused 0 0 0 0

DLCI = 503, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/1.1

input pkts 37 output pkts 34 in bytes 13393 out bytes 11699 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 33 out bcast bytes 11685 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec pvc create time 00:53:29, last time pvc status changed 00:11:10 R5#

R5#sh ip route Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route

Gateway of last resort is not set

172.16.0.0/24 is subnetted, 1 subnets C 172.16.105.0 is directly connected, Loopback0 10.0.0.0/24 is subnetted, 1 subnets C 10.10.10.0 is directly connected, Loopback1 R5#

===== R3 ========

interface Serial0/1 no ip address encapsulation frame-relay IETF

interface Serial0/1.1 point-to-point ip unnumbered Loopback0 frame-relay interface-dlci 503

interface Loopback0 ip address 172.16.103.1 255.255.255.0

R3# sh 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 2 0 0 0

DLCI = 301, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = Serial0/0

input pkts 0 output pkts 0 in bytes 0 out bytes 0 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 0 out bcast bytes 0 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec switched pkts 0 Detailed packet drop counters: no out intf 0 out intf down 0 no out PVC 0 in PVC down 0 out PVC down 0 pkt too big 0 shaping Q full 0 pkt above DE 0 policing drop 0 pvc create time 02:13:34, last time pvc status changed 02:13:04

DLCI = 302, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = Serial0/0

input pkts 0 output pkts 0 in bytes 0 out bytes 0 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 0 out bcast bytes 0 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec switched pkts 0 Detailed packet drop counters: no out intf 0 out intf down 0 no out PVC 0 in PVC down 0 out PVC down 0 pkt too big 0 shaping Q full 0 pkt above DE 0 policing drop 0 pvc create time 02:13:35, last time pvc status changed 02:13:05

DLCI = 304, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0.1

input pkts 1697 output pkts 2488 in bytes 75314 out bytes 91710 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 137 out bcast bytes 49428 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec pvc create time 02:14:16, last time pvc status changed 02:13:07 Bound to Virtual-Access1 (up, cloned from Virtual-Template1)

PVC Statistics for interface Serial0/1 (Frame Relay DTE)

Active Inactive Deleted Static Local 1 0 0 0 Switched 0 0 0 0 Unused 0 0 0 0

DLCI = 503, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/1.1

input pkts 38 output pkts 43 in bytes 13480 out bytes 15242 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 43 out bcast bytes 15242 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec pvc create time 00:58:49, last time pvc status changed 00:15:50

R3# sh ver Cisco Internetwork Operating System Software IOS (tm) C2600 Software (C2600-JK9O3S-M), Version 12.2(15)T12, RELEASE SOFTWARE (fc1)

R3#sh ip route Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route

Gateway of last resort is not set

172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks C 172.16.34.4/32 is directly connected, Virtual-Access1 C 172.16.34.0/24 is directly connected, Virtual-Access1 C 172.16.103.0/24 is directly connected, Loopback0

Serial0/0.1 (up): point-to-point dlci, dlci 304(0x130,0x4C00), broadcast status defined, active Serial0/1.1 (up): point-to-point dlci, dlci 503(0x1F7,0x7C70), broadcast status defined, active



This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:53 GMT-3