- Posts: 20
- Thank you received: 0
Frame-Relay Point-to-Point
14 years 9 months ago #33556
by kchong_14
Kenneth Chong
Frame-Relay Point-to-Point was created by kchong_14
Hi,
I have configured a Frame relay scenario in GNS.
It consist of 3 routers (hub and spoke topology). They are all configured as point-to-point.
My hub router is able to ping both spoke routers, and the spoke routers are able to ping the hub router.
But my problem is that the spoke routers are not able to ping each other, is this a characteristic of point-t-point frame relay? Or I should be able to make the 2 spoke routers pingable?
Thanks.
I have configured a Frame relay scenario in GNS.
It consist of 3 routers (hub and spoke topology). They are all configured as point-to-point.
My hub router is able to ping both spoke routers, and the spoke routers are able to ping the hub router.
But my problem is that the spoke routers are not able to ping each other, is this a characteristic of point-t-point frame relay? Or I should be able to make the 2 spoke routers pingable?
Thanks.
Kenneth Chong
- broadcaststorm
- Offline
- Junior Member
Less
More
- Posts: 79
- Thank you received: 0
14 years 9 months ago #33557
by broadcaststorm
Replied by broadcaststorm on topic Re: Frame-Relay Point-to-Point
Presumably the two serial interfaces on the hub router are in separate subnets? If so, then you need either a layer two or a layer three route between the two spokes. A combination of sub-interfaces with the appropriate layer three addresses along with some layer two dlci addresses and mappings should sort it, assuming I remember correctly :oops:
14 years 9 months ago #33583
by kchong_14
Kenneth Chong
Replied by kchong_14 on topic Re: Frame-Relay Point-to-Point
Hey,
I don't really understand what your saying...
Ok, so there are 3 routers ( hub and spoke topolgy ).
And yea they are on different subnets.
R1 = Hub
R2= Spoke
R3= Spoke
I have the basic configuration that R1 is able to ping both R2 and R3.
R2 is able to ping R1
R3 is able to ping R1
The only problem I am having now is that R3 is not able to ping R2, and I have no routing protocols running on non of the routers.
They are configured as point-to-point.
I am wondering if there is a method or command that I can use to make R2 and R3 pingable. I have heard of this frame relay mapping, but I am not sure how this is used, and I can't really find a good documentation on this...
So is this frame-relay mapping command that I have to use ?
Thanks.
I don't really understand what your saying...
Ok, so there are 3 routers ( hub and spoke topolgy ).
And yea they are on different subnets.
R1 = Hub
R2= Spoke
R3= Spoke
I have the basic configuration that R1 is able to ping both R2 and R3.
R2 is able to ping R1
R3 is able to ping R1
The only problem I am having now is that R3 is not able to ping R2, and I have no routing protocols running on non of the routers.
They are configured as point-to-point.
I am wondering if there is a method or command that I can use to make R2 and R3 pingable. I have heard of this frame relay mapping, but I am not sure how this is used, and I can't really find a good documentation on this...
So is this frame-relay mapping command that I have to use ?
Thanks.
Kenneth Chong
- broadcaststorm
- Offline
- Junior Member
Less
More
- Posts: 79
- Thank you received: 0
14 years 9 months ago #33737
by broadcaststorm
Replied by broadcaststorm on topic Re: Frame-Relay Point-to-Point
The issue is getting a layer three route across a layer two hub.
Frame relay mapping is used if you turn off inverse arps, which you can do if you want, but it won't help with your issue.
Your hub router needs to have 4 interfaces, not just the two physical. So you need to create a sub interface on each interface of all 3 routers. Then you can map across the hub with layer 2 to layer 3 map commands on the sib-ifs. Essentially you make the hub transparent at Layer 3 whilst it provides frame relay switching at layer two. With this type of config, the two spokes will be able to ping at layer three
BUT, I need to configure this on my test lab to make 100% sure I'm not talking rubbish. But as I'm away from home right now it'll be next week, unless I can blag some time in the switch room after hours :shock:
Frame relay mapping is used if you turn off inverse arps, which you can do if you want, but it won't help with your issue.
Your hub router needs to have 4 interfaces, not just the two physical. So you need to create a sub interface on each interface of all 3 routers. Then you can map across the hub with layer 2 to layer 3 map commands on the sib-ifs. Essentially you make the hub transparent at Layer 3 whilst it provides frame relay switching at layer two. With this type of config, the two spokes will be able to ping at layer three
BUT, I need to configure this on my test lab to make 100% sure I'm not talking rubbish. But as I'm away from home right now it'll be next week, unless I can blag some time in the switch room after hours :shock:
- broadcaststorm
- Offline
- Junior Member
Less
More
- Posts: 79
- Thank you received: 0
14 years 8 months ago #33841
by broadcaststorm
Replied by broadcaststorm on topic Re: Frame-Relay Point-to-Point
Can you show me the config for the hub, assuming you haven't sorted it already?
Can't think what I'm missing having re-visited this subject :oops:
Can't think what I'm missing having re-visited this subject :oops:
14 years 8 months ago #33873
by Losh
~ Networking :- Just when u think its starting to make sense......... ~
____________________________________________
CCNA, CCNP, CCNA Security, JNCIA, APDS, CISA
Replied by Losh on topic Re: Frame-Relay Point-to-Point
Are you using inverse ARPs or manual ip mapping? it would be better if you posted your configuration so that we can see the problem. the problem might be because of split horizon which doesnt accept sending routing updates out the same interface on which it received another. try disabling split horizon.
~ Networking :- Just when u think its starting to make sense......... ~
____________________________________________
CCNA, CCNP, CCNA Security, JNCIA, APDS, CISA
Time to create page: 0.154 seconds