Cabling for Frame-Relay

In simple Frame-Relay configurations using an AdTran as a FR "cloud," I'm connecting two routers to the AdTran, with one host to each router. I've done the written labs and such, but now I'm doing the hands-on. With ISDN we connected a straight-through cable from the router to the ISDN port on the AdTran. But with FR, the lab says to use a serial cable. So I'll need, say, a smart-cable serial-cable to connect the router to the AdTran and not use a straight-through or the ISDN port? I feel like an idiot asking this, but I need to know. There's also two port one cable ports on the back and two port two cable ports. Which do I use coming from the router? Thanks.

Find more posts tagged with

SAVE $250 on Your CISCO Boot Camp — Use Code "EXAM26"

Exclusively for TechExams members for Infosec Boot Camps starting before April 30, 2026

View CISCO Boot Camps

Comments

Netstudent

IS this an adtran switch or router? What model number? Are you postitive that this adtran can do frame-relay encapsulation?

Tricon7

Netstudent wrote:

IS this an adtran switch or router? What model number? Are you postitive that this adtran can do frame-relay encapsulation?

Pretty sure. It's an Atlas AdTran 550.

I've input what I thought were all the pertinent commands, but I still can't get one router to talk to the other through the AdTran. The routers can talk to the hosts, and vice versa, no problem.

Here's my input:

R1

(config)#int fa 0/0
(config-if)#ip address 192.168.13.2 255.255.255.0
(config-if)#no shut

(config-if)#int s 0/0
(config-if)#encapsulation frame-relay ieft
(config-if)#frame-relay lmi-type ansi
(config-if)#frame-relay interface-dlci 102
(config-if)#frame-relay map ip 192.168.12.2 102 ietf broadcast

(config-if)#ip address 192.168.12.1 255.255.255.0
(config-if)#clock rate 56000
(config-if)#no shut
(config)#ip route 0.0.0.0 0.0.0.0 192.168.12.2

R2

(config)#int fa 0/0
(config-if)#ip address 192.168.14.2 255.255.255.0
(config-if)#no shut

(config-if)#int s 0/0
(config-if)#encapsulation frame-relay ieft
(config-if)#frame-relay interface-dlci 102
(config-if)#frame-relay lmi-type ansi
(config-if)#frame-relay map ip 192.168.12.1 102 ieft broadcast

(config-if#ip address 192.168.12.2 255.255.255.0
(config-if)#clock rate 56000
(config-if)#no shut

(config)#ip route 0.0.0.0 0.0.0.0 192.168.12.1

Netstudent

You don;t need clock rate on a DTE interface. Also you need a different DLCI on each end on the PVC so that the DLCI's can be switched at the destination frame-relay switch. This is done for return traffic so that the return traffic knows which DLCI to use to go back in the direction in came.

Lets say R1 uses 102 to get to R2. So 102 is R1's local DLCI.
Then lets say thay R2 uses DLCI 201 to get to R1. So 201 is R2;s local DLCI.

R1(102)

cloud

R2(201)

When a frame leaves R1 it will have a DLCI102 in the frame, this frame will traverse the cloud untill it gets to the destination frame-relay switch. Before the destination switch fwd's the frame to R2, the DLCI gets changed to 201. So the return traffic can be sent back to 201.

And we need the configs for that adtran. I'm about to read about that model because I have no idea what that is.

r_durant

I dont know how the Adtran works, but I'm curious...

I know you use the physical interface s0, s1, s0/0, etc when you do a back to back connection to simulate a WAN, with the Adtran is this the same principle?

The reason I asked is because i realized that you have the frame-relay configs under the physical interface and not a sub-interface?

Or is the sub-interface line missing from the config?

Netstudent

a subinterface isn't necesarily required here. Okay it is modular, do you know what cards are in that thing? I read that it can automatically negotiate LMI, but like cisco, it can't automatically negotiate encapsulation. So my guess is, log into the adtran and setup frame-relay encapsulation on the connected interfaces along with clocking.

r_durant

Ok cool, was just checking...

Netstudent

OKay I think I found what you need here.

http://images.google.com/imgres?imgurl=http://www.adtran.com/adtranpx/Doc/0/05OT6SQTE7OKTF5I0QF7FTUDE8/fig1.jpg&imgrefurl=http://www.adtran.com/adtranpx/Doc/0/GPTFE2KD3EVK7FJA71RES6CK7E/CU-11a5e4a2f29d4828bb6fd9ef90479cd.html&h=310&w=545&sz=43&hl=en&start=38&tbnid=4rPrel9UlNHCzM:&tbnh=76&tbnw=133&prev=/images%3Fq%3DAdtran%2Batlas%2B550%26start%3D20%26gbv%3D2%26ndsp%3D20%26svnum%3D10%26hl%3Den%26sa%3DN

This is for an 800. Not sure if the software is the same in these devices. Worth a look though.

Tricon7

Netstudent wrote:

a subinterface isn't necesarily required here. Okay it is modular, do you know what cards are in that thing? I read that it can automatically negotiate LMI, but like cisco, it can't automatically negotiate encapsulation. So my guess is, log into the adtran and setup frame-relay encapsulation on the connected interfaces along with clocking.

No AdTran configurations required for this exercise. We only input info on each router while connected to the AdTran.

My DLCI #s are different on each serial interface, so I know that's right.