frame relay question!!

[tshekediwalker]

hello everyone,

I've been looking everywhere but can't seem to find the answer.

I am taking my ccna exams in a month's time and I am currently learning about frame-relay.

I have been looking everywhere but how do I know the DLCI that has been assigned to my local router? I know about using several show command e.g. show frame map, show fram lmi, show frame pvc , show run etc. but these only show the DLCI of the REMOTE routers.

I guess my question stems from if there is already a preconfigured and fully operating frame-relay router being used and I as a new engineer wants to know the DLCI that is assigned to it, how do I know. I mean are there some other show commands that I have missed or is it a case of me contacting my service provider to know?

Thanks.

[burleyman]

Rick,

I see what you mean.

Thanks

[John Blakley]

According to the configs, this is the way that the drawing should look:

[tshekediwalker]

ahhh j.blakely I see what you mean. thanks

[tshekediwalker]

i had forgotten one of the config photos from my post at 08:10. I have now edited and attached the photo.

[John Blakley]

That config is fine. The remote sites can use the same dlci....

[paulstone80]

I have that book and used it for my CCNA exams. The content IS correct.

What it tells you is that the DLCI values shown are the Global DLCIs, what you need to configure Frame Relay are the Local DLCIs.

Global DLCIs are a bit misleading, but basically all you need to know is:

If a Global DLCI is shown, the router on the other end of that PVC use that Global DLCI as its Local DLCI.

From Mr Wendell himself: http://www.ccnaskills.com/2011/05/23/fr-answer-iii-global-dlcis/

And a pretty picture to illustrate the point!

[burleyman]

Great explainations.... 5's for all.

I don't work with Frame relay at all and it has been awhile when I did them in my studies. All this information was great. I might just do some lab work to get this drilled in.

Mike

[John Blakley]

Thanks Mike...I had to lab this up because I was curious

Okay..I started think about how the image is presented. I believe what they've done in the book is show the OPPOSITE DLCI. In other words, your Atlanta router will send to DLCI 51, but that's not the local dlci. The local dlci for that circuit is 54. I labbed this up above and it does work...with almost the same configurations as what's in your book:

R1:

interface Serial0/0

no ip address

encapsulation frame-relay

clock rate 2000000

!

interface Serial0/0.52 point-to-point

ip address 192.168.13.1 255.255.255.0

frame-relay interface-dlci 52

!

interface Serial0/0.53 point-to-point

ip address 192.168.14.1 255.255.255.0

frame-relay interface-dlci 53

!

interface Serial0/0.54 point-to-point

ip address 192.168.15.1 255.255.255.0

frame-relay interface-dlci 54

!

--- R2 is the FR Switch ---

R3:

interface Serial0/0

ip address 192.168.13.3 255.255.255.0

encapsulation frame-relay

clock rate 2000000

frame-relay interface-dlci 51

end

R4:

interface Serial0/0

ip address 192.168.14.4 255.255.255.0

encapsulation frame-relay

clock rate 2000000

frame-relay interface-dlci 51

end

R5:

interface Serial0/0

ip address 192.168.15.5 255.255.255.0

encapsulation frame-relay

clock rate 2000000

frame-relay interface-dlci 51

end

However, to your original question of getting the local DLCI, our other answers still stand:

On R4:

R4#sh frame-relay map

Serial0/0 (up): ip 192.168.14.1 dlci 51(0x33,0xC30), dynamic,

              broadcast,, status defined, active

R4#

R4#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         0            0            0            0

DLCI = 51, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0

On R1, this is what you'll see:

R1#sh frame-relay pvc | inc DLCI

DLCI = 52, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0.52

DLCI = 53, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0.53

DLCI = 54, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0.54

R1#

HTH,

John

[anthony.kellar]

This one bugged me too...look at it this way...you will never see the remote dlci on your router...they are always local.

Sent from Cisco Technical Support iPad App

[tshekediwalker]

thanks for all the answer guys. really appreciate it!

[burleyman]

What if you tried running the command...

show frame-relay route

That should show the Input DLCI and the output DLCI

Mike

[tshekediwalker]

Oh my word. Think this is what I am looking for all along! I am using packet-tracer  and the show frame relay command only gives you lmi, pvc and map.!!!

thanks burleyman

[cadet alain]

Hi,

Don't forget this command only works on the router acting as Frame-relay switch not on the DTE devices( end routers).

Regards.

Alain.

[tbogie_gvds]

Folks,

This is the most illuminating article I have ever read as I too have struggled for a long time to understand why diagrams are drawn one way, the show commands say another and the command reference says something that whilst true (one would hope!) didn't match what I was seeing in the books compared to what I was seeing on the CLI.  So Thankfully you guys have put it all in such a way that I for the first time trully understand how to interpret the whole show.

Wow, Thanks!

I do need to also say that technically Odom is correct in his books.  One thing he does write about is the kind of addressing that is used in diagrams - local versus global - so we shouldn't be to hasty in selling him short.  The issue is that it could have been explained better in the book, which unfortunately took an article on a website to explain a little more thoroughly but still not that great in my opinion, but in reality for me it took j.blakley and paulstone80 for me to see the light.

Thanks Guys.

Timothy