Frame relay map ip x.x.x.x vs Frame relay route dlci command.

[ejeangilles]

I have a question that's driving me crazy and can't seem to get an understanding around it and that's the difference between the frame relay map ip x.x.x.x and frame relay route interface dlci commands. Do they both accomplish the same thing? Would you say its easier to configure a frame relay switch with the frame-relay route interface dlci commands because it seems that you configure that on the frame switch and your good to go. Oppose to the frame relay map ip x.x.x.x commands because it looks like you configure them on all the routers. Thought you guys can shed some light or point me in the right direction or am understandng it wrong.

 

[burtsbees]

One has to do with a point to multipoint config (hub and spoke), with or without subinterfaces, and the other would be a mesh...now you're going to make me dig out the books...lol

Burt

 

[ejeangilles]

That's how I feel. I've been digging around and see different scenarios. Regardless of the protocol RIP, EIGRP, OSPS, etc shouldn't the routing be the same regardless of which frame relay command is used?

 

[Lemon13]

dlci is layer 2 addressing (instead of mac addresses) and map ip is layer 3 addressing (needed for roting protocol broadcast/multicast)
try it, just define the dlci, disable reverse arp and then ping trough the fr-cloud

 

[jeter]

I guess the question here is what are you trying to accomplish?

I perfer setting up sub interfaces on frame-relay circuits my self but as with Cisco there is more than one way to skin a cat......


Go Army!
Tek-TIP Member 19,650

 

[ejeangilles]

Thanks for the info. It's becoming a little clearer for me. Here's another way to explain my question. Here are 2 configs...do they both accomplish the same thing

This would be a Hub and Spoke using the frame-relay route (dlci) interface port (dlci) command. Where R1 is the Hub and R2 and R3 is the spoke.

frame-relay switching
!

interface Serial1
no ip address
no ip directed-broadcast
encapsulation frame-relay
logging event subif-link-status
logging event dlci-status-change
clockrate 56000
no frame-relay inverse-arp
frame-relay intf-type dce
frame-relay route 122 interface Serial2 221
frame-relay route 123 interface Serial3 321
!
interface Serial2
no ip address
no ip directed-broadcast
encapsulation frame-relay
logging event subif-link-status
logging event dlci-status-change
clockrate 56000
no frame-relay inverse-arp
frame-relay intf-type dce
frame-relay route 221 interface Serial1 122

interface Serial3
no ip address
no ip directed-broadcast
encapsulation frame-relay
logging event subif-link-status
logging event dlci-status-change
clockrate 56000
no frame-relay inverse-arp
frame-relay intf-type dce
frame-relay route 321 interface Serial1 123



And I believe this would be static mappings to achieve the same thing

R1
interface serial 0
no frame-relay inverse-arp
frame-relay map ip 10.0.0.2 122 broadcast
frame-relay map ip 10.0.0.3 123 broadcast

R2
interface serial 0
no frame-relay inverse-arp
frame-relay map ip 10.0.0.1 122 broadcast

R3
interface serial 0
no frame-relay inverse-arp
frame-relay map ip 10.0.0.1 122 broadcast

And in the second example if I do use these static maps for my R1, R2 and R3 router they would be connected to the frame relay switch. Am I on the right track or am I getting ahead of myself..

 

[Belushi]

The frame relay route command is used to have a router emulate a frame relay switch. Yes, you could also use it on a router performing frame-relay switching as well as standard IP routing but the general use would be to emulate.

The frame-relay map ip command as explained earlier is to statically map a layer 3 address to a layer 2 address (DLCI). This can be done dynamically with inverse-arp or statically as you already know.