We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 644 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

460 Sign Ups in the last 30 days

satisfaction-guaranteed
100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags: , ,


Forum Replies

  1. many thanks for the article; however the spoke-spoke mappings at the end of the article are not correct and we need a new DLCI mapping other than the one already used

    If I use the mappings defined here, when pinging from Spoke1-Spoke2 (and vice verca) I get UUUUU. Changing the mappings to 2:221-3:321 on the switch and the spoke configs solved the problem

    Spoke1 - frame-relay map ip 192.168.123.3 221
    Spoke 2 - frame-relay map ip 192.168.123.2 321

  2. Hello Rene,

    If a pvc has been created between hub-spoke1 and hub-spoke2, how is the traffic from spoke2 to spoke1 going to get to spoke1 by just creating mappings between spoke2 and spoke1?? Should the route table for spoke2 point to 192.168.123.1 as the route to reach 2.2.2.2 on spoke1 via the pvc since this is the next hop in its path? Then should Hub route the traffic via its pvc to reach 2.2.2.2 on spoke1?

    If not, how does the Frame Relay switch know to pass data between spoke2 and spoke1 if a pvc has not been created between a dlci on spoke2 and dlci on spoke1?

     

     

     

  3. Hi,

    Here is my configuration

    **R2-spoke2**
    -----
    interface Serial2/2
    ip address 192.168.123.2 255.255.255.0
    encapsulation frame-relay
    serial restart-delay 0

    **R1-hub**

    interface Serial2/1
     ip address 192.168.123.1 255.255.255.0
     encapsulation frame-relay
     serial restart-delay 0
    

    ---

    **R3-SPOKE2**

    interface Serial2/3
     ip address 192.168.123.3 255.255.255.0
     encapsulation frame-relay
     serial restart-delay 0
    !
    

    **FR-switch**
    -----
    interface Serial2/1
    description R1
    no ip address
    encapsulation frame-relay
    serial restart-delay 0
    frame-relay intf-type dce
    frame-relay

    ... Continue reading in our forum

  4. Hello Sergei

    There are several ways to get a Frame Relay PVC working correctly. One is to use the frame-relay interface-dlci 102 command. However, this would not apply here as it is only used on subinterfaces. It is not common to use, although it does have its uses. When applied, it will assign a DLCI to the subinterface. When the subinterface already has a DLCI assigned and an IP address has been configured on it, Inverse-ARP requests can now be sent to acquire the IP addresses of the neighbor devices.

    Alternatively, the command used on the subinterfaces i

    ... Continue reading in our forum

  5. Hello Sergei

    Sorry Sergei, what I mentioned in the previous post was not entirely correct. Let me clarify:

    When configuring point to point Frame Relay with subinterfaces, you can use the following command:

    frame-relay interface-dlci XXX

    This command configures the DLCI of the subinterface. It also keeps Inverse ARP active to be able to find the DLCI of the other end of the circuit, assuming the IP address has also been configured on the subinterface. Now this command is typically used for subinterfaces, but can also be applied to the main physical interfaces

    ... Continue reading in our forum

31 more replies! Ask a question or join the discussion by visiting our Community Forum