04-22-2009 05:37 AM - edited 03-04-2019 04:28 AM
All,
I've been playing around with FR mappings and noticed that the mappings require the address and LOCAL dlci, not the remote.
frame-relay map ip 192.168.1.1 201
The 192.x.x.x address is the remote router, but the 201 is the local router's dlci. Why is this? Am I mapping a way for 192.168.1.1 to get back to me through my dlci?
Thanks,
John
Solved! Go to Solution.
04-22-2009 05:50 AM
John
Think of it like this. Frame Relay like ATM can multiplex many different virtual circuits on the same physical link. With frame-relay the virtual circuits (vc) are identified with DLCIs.
So if the physical interface has many vc's using the frame-relay map ip command allows you to tell the router that to get to a specific remote address the data needs to be sent over specific vc and that vc has to be significant to the local router. That vc is a connection between the local router and the Frame switch. And you tell the Frame switch that data arriving on that vc is switched to the remote destination.
Hope this makes sense.
Jon
04-22-2009 10:23 AM
*EDIT* I went back and looked, and when configuring the router as a FRSW, you don't even need addresses on the FRSW interfaces, which makes my question even more confusing.
Why? It actually answers your question. You keep mixing IPs with DLCI.
The FRSW swaps|switches DLCI from incoming to outgoing. The CE routers will map a DLCI to an IP and send the packet out towards the FRSW. The FRSW does not care about the IP address information, just the DLCI.
And you want me to post more complicated FR configs? LOL
__
Edison.
04-22-2009 10:43 AM
Bingo!
That's the reason your mappings didn't work yesterday.
If you see my GNS3 FRSW mappings, it should make sense to you. You had fewer mappings than mine. Check both .NET files and compare.
__
Edison.
04-22-2009 10:46 AM
John
What you are suggesting here is exactly correct if the network is to be full mesh. In full mesh each router needs a unique DLCI for every peer in the Frame Relay network.
HTH
Rick
04-22-2009 05:50 AM
At the Frame-Relay switch, on the interface facing your router, there is a group of commands that instruct the switch what to do in terms of DLCI switching.
The FRSW sends LMI with DLCI 201 to your router and any packets coming from your router towards DLCI 201 will be switched to another DLCI that corresponds the 192.168.1.1 device.
To recap, the DLCIs are locally significant between the FRSW and the router connected to it.
HTH,
__
Edison.
04-22-2009 07:04 AM
Edison,
So the only DLCI the router will ever know about is the local one that was assigned by the switch?
I know that a FR switch can route packets from one to another dlci like:
frame-relay route 150 inter s0/0 140
I believe this is saying that a router assigned dlci 150 gets routed out of s0/0 to dlci 140. Does this complete one pvc?
If it does, then take the following on the same switch:
frame route 130 inter s0/1 120
This does this same thing for incoming 130 to outgoing 120? Now if I had another router at dlci 110, and I mapped:
frame map ip 192.168.1.2 110 broadcast
Let's assume that 192.168.1.2 is out s0/0. How does the switch know to route out of that interface instead of s0/1? Is it based off of the ip address that's assigned to that interface?
Thanks,
John
04-22-2009 08:24 AM
So the only DLCI the router will ever know about is the local one that was assigned by the switch?
It can be multiple DLCIs advertised by the FRSW switch towards your router but each DLCI is switched to a different destination.
I believe this is saying that a router assigned dlci 150 gets routed out of s0/0 to dlci 140. Does this complete one pvc?
Not always, your local FRSW will be accepting your incoming flow but it can route within the frame-relay network to other FRSWs, if necessary. Once it reaches the final destination, then you can define a complete PVC.
frame map ip 192.168.1.2 110 broadcast
Let's assume that 192.168.1.2 is out s0/0. How does the switch know to route out of that interface instead of s0/1?
The command above is done at the router, not the FRSW. The FRSW needs the frame-relay route command, not the frame map ip command.
__
Edison.
04-22-2009 09:15 AM
Edison,
Warning: May get confusing.
I think my main question is that if a router is configured as a FRSW, and it knows to route:
RTR A is configured as a FRSW:
192.168.1.1 (dlci 110) --> 210
192.168.1.3 (dlci 120) --> 220
192.168.1.5 (dlci 130 --> 230
RTR B 192.168.1.2 is 210
RTR C 192.168.1.4 is 220
RTR D 192.168.1.6 is 230
Rtr B, if inverse arp is enabled, will have a mapping like:
serial0/0: 192.168.1.1, 210, broadcast
Right?
For me to get to 192.168.1.6, on Router B I would need to create a static mapping like:
int s0/0
frame-relay map ip 192.168.1.6 210 broadcast
I *should* be able to ping 192.168.1.6, but how does the switch know to go out the 192.168.1.5 address to get to .6 if it's only caring about the L2 mapping? I think that's the question I'm trying to ask. Thank you for your patience :)
*EDIT* I went back and looked, and when configuring the router as a FRSW, you don't even need addresses on the FRSW interfaces, which makes my question even more confusing.
If RTR B is trying to get to RTR C, and RTR B has the same mapping, how does the switch know to go out RTR C's serial interface if there's no address assigned to it? Does the switch keep a table also?
John
04-22-2009 09:47 AM
John
I must admit that I am a bit confused in your question. I get RTRA as the Frame Relay switch. But I am confused about 192.168.1.1 (dlci 110) --> 210. Clearly it says that it receives DLCI 110 but on what interface? And who is 192.168.1.1? And similar confusions for the other two lines:
192.168.1.3 (dlci 120) --> 220
192.168.1.5 (dlci 130 --> 230
Perhaps one thing that may help is to clarify that Frame Relay switching operates only at layer 2. So the configuration of the Frame Relay switch says to expect DLCI x incoming on interface A and it should be switched as outgoing DLCI y on interface B. All of the Frame Relay switching has no knowledge of the IP addressing and operates independently of the IP addressing.
[edit] I just reread your post and would like to make an additional point. You say:"if a router is configured as a FRSW, and it knows to route: ". This seems to imply that you see routing and Frame Relay switching as related. They are not related. Frame Relay switching is just creating virtual circuits, so an incoming virtual circuit has a DLCI from RTRA and it is switched to an outgoing DLCI to RTRB (for example). It does all the Frame Relay switching without any reference to what IP addresses are being used.
HTH
Rick
04-22-2009 10:10 AM
John
I believe that it might be helpful to rethink the example that you propose. You suggest 3 routers and a router/Frame Relay switch. First lets be clear that the Frame Relay switch might route IP, but that is not common and it complicates the discussion. So let us assume that the Frame Relay switch will switch Frame Relay and not route.
So there are RTRA, RTRB, and RTRC which are the Frame Relay network. Will this network operate as a full mesh network where each router has a connection to each other router? If so how many DLCIs would each router have?
Or will the network operate as a hub and spoke network? If so which router is the hub? How many DLCIs will the hub router have? How many DLCIs will each spoke router have?
After you think through these things, then think about what IP addressing you would use on each router for its Frame Relay interface. Is it all in the same subnet or are there multiple subnets involved?
HTH
Rick
04-22-2009 10:27 AM
04-22-2009 10:36 AM
John
I have looked at your drawing and believe that it does much of what I was asking in my previous post.
The biggest conceptual difficulty with your drawing (and perhaps this explains the difficulty you are having explaining your question) is that it shows each router with a single DLCI to the Frame Relay switch. At least one of the routers must have 2 DLCIs.
Perhaps we should clarify in your drawing and in your question whether you intend the Frame Relay network to operate as a full mesh network or as a hub and spoke network.
If it is to be a full mesh then each router needs 2 DLCIs (a DLCI for each peer to whom it communicates). Or if it is hub and spoke then the hub router needs 2 DLCIs and the spokes need a single DLCI. (and bear in mind that for hub and spoke when a spoke wants to communicate with the other spoke it must send to the hub and the hub must forward to the other spoke).
If you can clarify the nature of the network we may be closer to getting explanations that work.
HTH
Rick
04-22-2009 10:43 AM
Rick,
There's not really a problem. I'm just trying to get a grasp on the FR concept because I'm studying for BSCI and ran across it with the way OSPF interacts. I set up a lab in gns3, and I realized that true frame is something that I don't think I've ever worked with.
Thanks!
John
04-22-2009 10:50 AM
John
It is good to have a grasp on the FR concept - especially the concept that a DLCI represents a connection to a single Frame Relay peer. and that Frame Relay switching is a layer 2 process and is separate from the layer 3 IP addressing.
And to have a good grasp of FR it is also helpful to understand the differences in Frame Relay between full mesh networks and hub and spoke networks.
HTH
Rick
04-22-2009 10:36 AM
Based on your diagram, the mappings are incorrect. For instance, Router B has 2 FR mappings but they are both pointing to the same DLCI.
The FRSW will switch any packets coming from 202 out to the same egress interface.
If you want the FRSW to switch packets intended for 192.168.1.1 to go up to Router A, then within the FRSW, it will have a FR route from 202 to 201 but you can't reuse 202 for Router C so you need something like 302 to 203, thus your Layer3 mappings in router B would look like:
frame map ip 192.168.1.1 202 bro
frame map ip 192.168.1.3 302 bro
04-22-2009 10:42 AM
AH!!!! That's what I'm NOT understanding! So, there needs to be a one-to-one mapping for EVERY incoming/outgoing interface? So, for this to work, I would need two mappings per router? And because it sees what interface the incoming is coming in on, the switch knows what interface to go out on?
04-22-2009 10:43 AM
Bingo!
That's the reason your mappings didn't work yesterday.
If you see my GNS3 FRSW mappings, it should make sense to you. You had fewer mappings than mine. Check both .NET files and compare.
__
Edison.
04-22-2009 10:50 AM
Well, I want to thank ALL of you for sticking with me on this! I understand the concept now:
If I have a mapping on my router to two other routers:
My local dlci's are 201 and 202:
frame map ip 192.168.1.1 201
frame map ip 192.168.1.2 202
The switch is then mapped from:
(incoming) 201 --> 101
(incoming) 202 --> 102
Two other routers:
Router A has ip 192.168.1.1 and it's local dlci is 101
Router B has ip 192.168.1.2 and it's local dlci is 102.
The switch changes the dlci from 201 to 101 and 202 to 102 in order for the two devices to talk.
Does that sound right?? (Please say yes!)
John
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: