Frame Relay - Basic Configurations Hub and Spoke - Part 2

Frame Relay - Basic Configurations Hub and Spoke - Part 2 of 4

Frame Relay is well-suited for a hub and spoke design. We can take advantage of Frame Relay's ability to assign more than one virtual circuit (VC) to a single physical access circuit and design a hub and spoke network that gives us connectivity between all endpoints with a minimum of circuit and equipment cost.

We'll revisit Frame Relay point to point connections in more detail in a future lesson, but the steps for configuring a serial interface for a Frame Relay point to point connection are pretty simple:

- Set the interface encapsulation to Frame Relay
- Set LMI type, if necessary
- Disable Frame Relay Inverse-ARP, if necessary
- Configure Layer 3 address on interface
- Manually configure Frame Relay IP to DLCI mapping including spoke to spoke mappings

Category:

Science & Technology

Tags:

• packetlab
• Packet Lab
• Frame Relay
• DLCI
• LMI
• GNS3
• hub and spoke
• split horizon
• frame-relay map ip
• CCNA
• CCNP
• CCIP
• Cisco
• Cisco certification
• Free Cisco video lessons

[MrFaisalMmirza]

Love u man, you solved one of my biggest problem

[Xaeravoq]

@Xaeravoq If both R2 and R3 have 192.168.x.x networks attached to them and one network is trying to talk to the other the traffic will be destined for a 192.168.x.x network and when R2 gets the traffic the router will say I don't a Frame Relay map for the 192.168.x.x network I only have 10.x.x.x.

[Xaeravoq]

I guess i don't fully understand Frame Relay. You say that when R2 gets a packet destined for R3's IP address then it needs a static map to that IP. But my question is when would R2 ever need to send a packet directly to R3's serial interface? I mean a ping i guess but how would real traffic get from R2's LAN to R3's LAN since the destination IP address never changes in a packet.