From: Chuck Larrieu (chuck@xxxxxxxxxxxxx)
Date: Sun Jan 07 2001 - 11:47:05 GMT-3
In terms of Cisco routers as frame relay switches, the answer is no the
frame switch does not necessarily have to supply clock rate to the line.
However yes the frame switch should be configured with the frame-relay
interface-type DCE
In the Cisco world, the interface connected to the DCE end of the serial
cable should be configured with the clockrate. It matters not which router
this is - frame switch or edge device.
This is the difference between the physical DCE and the logical DCE.
Chuck
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of G F
Marsh
Sent: Sunday, January 07, 2001 1:40 AM
To: Bob Harrison; ccielab@groupstudy.com
Subject: Re: frame relay on lab8 ccbootcamp
Shouldn't the frame switch be supplying the clock and configured as the DCE
and the router should be DTE?
Gary
----- Original Message -----
From: Bob Harrison <bobmon2000@yahoo.com>
To: <ccielab@groupstudy.com>
Sent: Sunday, January 07, 2001 7:36 AM
Subject: frame relay on lab8 ccbootcamp
> Having problems with lab 8. Basically I can bring up
> the two routers connected via point-to-point frame
> relay. However, I can not bring up the multipoint
> connection from r5 to r2 and r3. Can anyone spot the
> issues or at least explain what a looped serial
> interface could imply? Here are my interfaces on the
> fr switch:
>
> interface Serial0 (goes to r2)
> no ip address
> no ip directed-broadcast
> encapsulation frame-relay
> no ip mroute-cache
> no keepalive
> no fair-queue
> frame-relay route 105 interface Serial2 501
>
> interface Serial3 (goes to r3)
> no ip address
> no ip directed-broadcast
> encapsulation frame-relay
> keepalive 20
> cdp enable
> frame-relay lmi-type ansi
> frame-relay route 305 interface Serial2 503
>
> R3 serial int s1
> interface Serial1
> ip address 137.20.100.35 255.255.255.224
> encapsulation frame-relay
> ip ospf network point-to-multipoint
> clockrate 64000
> cdp enable
> frame-relay map ip 137.20.100.34 305 broadcast
> frame-relay lmi-type ansi
> ****** shows as up, down (looped)
> R2 int s0
> interface Serial0
> ip address 137.20.100.33 255.255.255.224
> encapsulation frame-relay
> no fair-queue
> clockrate 64000
> frame-relay map ip 137.20.100.34 105 broadcast
> frame-relay lmi-type ansi
> ***** shows in show int as up, down*******
>
> R5 subinterfaces
> interface Serial1
> no ip address
> encapsulation frame-relay
> bandwidth 2000
> keepalive 15
> no fair-queue
> frame-relay lmi-type ansi
> !
> interface Serial1.1 multipoint
> ip address 137.20.100.34 255.255.255.224
> frame-relay map ip 137.20.100.33 501 broadcast
> frame-relay map ip 137.20.100.35 503 broadcast
> !
> interface Serial1.2 point-to-point
> ip address 137.20.200.17 255.255.255.240
> frame-relay interface-dlci 504
> !
> ***** again point-to-point works fine, but not multi***
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:23 GMT-3