cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1426
Views
0
Helpful
21
Replies

Frame Relay connectivity

a.maldonado
Level 1
Level 1

I have two 2500 and one 3600 connected together via Frame Relay. I configured the 3600 to be a FR switch and is providing clocking on each interface to each of the 2500's. The 2500 are the DTE's. The interfaces are X.21 and they are connected back to back with the 3600 using a DCE cable. The interfaces show they are up, the LMI is up at both ends but I cant ping from one 2500 to the other, or to the LAN interface on each of the 2500's. Sh cdp neigh does not show any of the routers, and the ip route command only shows the subnets directly attached to each router.

Does anyone have any idea what I am doing wrong?

Many thanks.

Arturo Maldonado

21 Replies 21

Dennis,

I manage to fix my original problem. The problem was that I had misconfigured the clock rate in both interfaces of the switch. the setting is in bits per second and I assumed that it was in Kbps so I had configured a 1000 bps interface and a 500 bps interface. Instead of the 1Mbps and 500 kbps that I wanted.

Anyway now I have a different problem and I am writing to you becuase you seem to have experimented with Cisco routers as switches. The DCE as I said is a 3600 router, which I labeled as Router 3, and I want to connect it to another router (Router 4) via a Fastethernet in a different subnet to where Routers 1 and 2 are (the FR DTEs). So the question is, how can I do to advertise the subnets configured in Router 4 so Routers 1 and 2 know about them, and viceversa.

EIGRP is configured in four routers and they are all in the same AS.

Many Thanks for your help.

Arturo.

lveraza
Level 1
Level 1

Hi

Arturo,

I have been watching your problem, now i have a problem with frame-relay look like your.

Can you send me a e-mail ?, maybe i can help you.

Best Regards

Luis

luis.veraza@foclan.net

jolly
Level 1
Level 1

you should also be able to do a sh fram pv on the 2500 to see what dlci's the 3600 is advertising to you. you may also need to set clock on the 2500's. here is a full mesh fram config if you want it.

sj

r7# wr t

Building configuration...

Current configuration : 6406 bytes

!

version 12.2

no parser cache

no service single-slot-reload-enable

service timestamps debug uptime

service timestamps log uptime

no service password-encryption

!

hostname r7

!

logging rate-limit console 10 except errors

enable password cisco

!

!

!

ip subnet-zero

!

!

no ip domain-lookup

ip host sw 192.168.255.9

ip host linux 192.168.255.101

ip host switch 172.16.255.2

!

no ip dhcp-client network-discovery

frame-relay switching

call rsvp-sync

!

!

!

!

!

!

!

!

!

interface Serial0/0

description r1

no ip address

encapsulation frame-relay

no ip route-cache

no ip mroute-cache

logging event subif-link-status

logging event dlci-status-change

keepalive 20

no fair-queue

clockrate 72000

frame-relay lmi-type ansi

frame-relay intf-type dce

frame-relay route 102 interface Serial0/1 201

frame-relay route 103 interface Serial0/2 301

frame-relay route 104 interface Serial0/3 401

frame-relay route 105 interface Serial1/0 501

frame-relay route 106 interface Serial1/1 601

frame-relay route 107 interface Serial1/2 701

frame-relay route 108 interface Serial1/3 801

!

interface Serial0/1

description r2

no ip address

encapsulation frame-relay

no ip route-cache

no ip mroute-cache

logging event subif-link-status

logging event dlci-status-change

keepalive 20

no fair-queue

clockrate 72000

frame-relay lmi-type ansi

frame-relay intf-type dce

frame-relay route 201 interface Serial0/0 102

frame-relay route 203 interface Serial0/2 302

frame-relay route 204 interface Serial0/3 402

frame-relay route 205 interface Serial1/0 502

frame-relay route 206 interface Serial1/1 602

frame-relay route 207 interface Serial1/2 702

frame-relay route 208 interface Serial1/3 802

!

interface Serial0/2

description r3

no ip address

encapsulation frame-relay

no ip route-cache

no ip mroute-cache

logging event subif-link-status

logging event dlci-status-change

keepalive 20

no fair-queue

clockrate 2016000

frame-relay lmi-type ansi

frame-relay intf-type dce

frame-relay route 301 interface Serial0/0 103

frame-relay route 302 interface Serial0/1 203

frame-relay route 304 interface Serial0/3 403

frame-relay route 305 interface Serial1/0 503

frame-relay route 306 interface Serial1/1 603

frame-relay route 307 interface Serial1/2 703

frame-relay route 308 interface Serial1/3 803

!

interface Serial0/3

description r4

no ip address

encapsulation frame-relay

no ip route-cache

no ip mroute-cache

logging event subif-link-status

logging event dlci-status-change

keepalive 20

frame-relay lmi-type ansi

frame-relay intf-type dce

frame-relay route 401 interface Serial0/0 104

frame-relay route 402 interface Serial0/1 204

frame-relay route 403 interface Serial0/2 304

frame-relay route 405 interface Serial1/0 504

frame-relay route 406 interface Serial1/1 604

frame-relay route 407 interface Serial1/2 704

frame-relay route 408 interface Serial1/3 804

!

interface Serial1/0

description r5

no ip address

encapsulation frame-relay

no ip route-cache

no ip mroute-cache

logging event subif-link-status

logging event dlci-status-change

keepalive 20

no fair-queue

clockrate 72000

frame-relay lmi-type ansi

frame-relay intf-type dce

frame-relay route 501 interface Serial0/0 105

frame-relay route 502 interface Serial0/1 205

frame-relay route 503 interface Serial0/2 305

frame-relay route 504 interface Serial0/3 405

frame-relay route 506 interface Serial1/1 605

frame-relay route 507 interface Serial1/2 705

frame-relay route 508 interface Serial1/3 805

!

interface Serial1/1

description r6

no ip address

encapsulation frame-relay

no ip route-cache

no ip mroute-cache

logging event subif-link-status

logging event dlci-status-change

keepalive 20

no fair-queue

clockrate 72000

frame-relay lmi-type ansi

frame-relay intf-type dce

frame-relay route 601 interface Serial0/0 106

frame-relay route 602 interface Serial0/1 206

frame-relay route 603 interface Serial0/2 306

frame-relay route 604 interface Serial0/3 406

frame-relay route 605 interface Serial1/0 506

frame-relay route 607 interface Serial1/2 706

frame-relay route 608 interface Serial1/3 806

!

interface Serial1/2

description r7

ip address 30.30.30.1 255.255.255.252

no ip route-cache

no ip mroute-cache

keepalive 20

no fair-queue

clockrate 72000

!

interface Serial1/3

description r8

no ip address

encapsulation frame-relay

no ip route-cache

no ip mroute-cache

logging event subif-link-status

logging event dlci-status-change

keepalive 20

no fair-queue

clockrate 72000

frame-relay lmi-type ansi

frame-relay intf-type dce

frame-relay route 801 interface Serial0/0 108

frame-relay route 802 interface Serial0/1 208

frame-relay route 803 interface Serial0/2 308

frame-relay route 804 interface Serial0/3 408

frame-relay route 805 interface Serial1/0 508

frame-relay route 806 interface Serial1/1 608

frame-relay route 807 interface Serial1/2 708

!

interface FastEthernet2/0

ip address 192.168.255.1 255.255.255.0

duplex auto

speed auto

!

interface Serial2/0

ip address 160.160.1.2 255.255.255.252

clockrate 148000

!

interface FastEthernet2/1

ip address 10.5.0.1 255.255.255.0

duplex auto

speed auto

!

interface Serial2/1

ip address 63.63.1.1 255.255.255.252

!

interface FastEthernet3/0

ip address 10.70.0.2 255.255.255.0

duplex auto

speed auto

!

router eigrp 1

redistribute static route-map default

network 10.0.0.0

no auto-summary

no eigrp log-neighbor-changes

!

router bgp 3

bgp log-neighbor-changes

neighbor 30.30.30.2 remote-as 5

neighbor 63.63.1.2 remote-as 4

neighbor 160.160.1.1 remote-as 2

!

ip classless

ip route 0.0.0.0 0.0.0.0 10.5.0.20

ip route 0.0.0.0 0.0.0.0 10.70.0.3

no ip http server

!

access-list 1 permit 0.0.0.0

!

!

route-map default permit 10

match ip address 1

!

!

dial-peer cor custom

!

!

!

alias exec c configure terminal

alias exec si show ip route

alias exec ci clear ip route *

alias exec oi show ip ospf interface

alias exec ion show ip ospf neighbor

alias exec ib show ip bgp

alias exec cib clear ip bgp *

alias exec ibn show ip bgp neighbor

alias exec wrb sho run | begin

alias exec sib show ip interface brief

!

line con 0

exec-timeout 0 0

privilege level 15

password cisco

logging synchronous

line aux 0

exec-timeout 0 0

privilege level 15

transport input all

line vty 0 4

exec-timeout 0 0

privilege level 15

password cisco

login

!

ntp clock-period 17179817

ntp server 137.20.20.1

!

end

r7#

I could not set the clock rate in the 2500's because they are the DTEs and the IOS complained that this is a feature of a DCE device. However, when trying to setup the clock rate in one of the DTEs I noticed that this setting is in bits per second, and not in kilobits per second as i initially thought. Once I corrected the clock rate value in both FR interfaces of the switch I managed to get pings from one DTE to the other across the DCE.

Many thanks to every one who helped me to sort out this problem.

Now I have a different problem. The DCE as I said is a 3600 router, which I labeld as Router 3, and I want to connect it to another router (Router 4) via a Fastethernet in a different subnet to where Routers 1 and 2 are (the FR DTEs). So the question is, how can I do to advertise the subnets configured in Router 4 so Routers 1 and 2 know abot them, and viceversa.

EIGRP is configured in four routers and they are all in the same AS.

Many Thanks.

Arturo.

Check to see if the segment (fast ethernet) between R3 and R4 are enabled with EIGRP.

Sankar Nair
UC Solutions Architect
Pacific Northwest | CDW
CCIE Collaboration #17135 Emeritus

I suppose it is, as they can see each other with the command sh ip eigrp neighbour.

Router_3 is esentially a FR switch and a Router. So how can we do to advertise the networks configured in the router part of Router_3 to the switch side of the same router? Is it possible at all?

I know I can achieve that by using an additional router configured as a hub router with another FR interface to Router_3 but my problem is that it may be difficult to find the hardware required, cables router, etc. That's is why I want to find an alternative to this problem with what I've got.

Many thanks.

Arturo Maldonado.

The frame switch and router functions are separate. The frame switch is a telco device, not a part of your network. Any interfaces on "the frame switch" router that are not configured for switching can be used for routing so they can be build into lab scenarios but they cannot see the switch ports.

Review Cisco Networking for a $25 gift card