Config Museum: Frame Relay Configuration

certskills
By certskills April 26, 2012 12:24

This blog post is the first of a couple of related Config Museum pieces. As with all Config Museum pieces, this post plainly states some requirements that lead you to then create a configuration. The matching answers post will then list the configuration. Today’s post shows a figure of a Frame Relay design, using global Frame Relay addressing, and asks you to configure the Frame Relay part, ignoring IP addressing. (I’ll likely add the IP addressing for the next Config Museum piece.)

Also note that this is the first post in the CCNA Skills blog since I migrated to a self-hosted wordpress site. So, if you see any formatting weirdness here or on any of the earlier posts, feel free to post, and I’ll look at it. Thanks!

Problem: Configure Frame Relay

The figure shown here shows a small internetwork with three routers connected to the same Frame Relay network. The figure shows the Frame Relay global DLCIs used by each router, and the fact that PVCs exist between two pair of the routers, but not between R2 and R3. The figure purposefully does not show an IP addressing details, mainly to let you think about those concepts separately from the Frame Relay parts of the configuration.

Figure 1 – Frame Relay Configuration Details

 

 

The following list details your rules for what to configure.

  1. Configure all *required* parameters to get the Frame Relay connection working, but do not configure IP addresses.
    1. “Working” means that both routers, once configured with IP addresses, could successfully ping each others’ Frame Relay IP addresses
    2. “Working” means that both routers on the ends of each PVC show the PVC in an “Active” state at the end of the config you build for today’s exercise.
  2. Configure so that the IP addresses, once added later, can be easily added to point-to-point subinterfaces, using the numbers listed in the figure.
  3. The figure shows global DLCIs (not local)
  4. Do not configure IP addresses or routing protocols.
  5. Do not configure the LAN interfaces.
  6. Use defaults if possible
  7. Assume the topology is built with gear in a single lab, with no Telco; however, you do not have to build the Frame Relay cloud

 

That’s it! Enjoy!

 

Answer, Config Museum: Frame Relay
Answers, Config VM: IPv6 Static Routes
certskills
By certskills April 26, 2012 12:24
Write a comment

3 Comments

  1. Faizan April 27, 03:03

    Wendell,

    Thanks for the practice lab scenario you posted on Frame Relay topic. For the last requirement, you asked us to assume the topology was built using lab gears. If my understanding is correct, the connection with the remote router will be provided with the back-to-back serial cable. And clocking will be provided from the DCE end. I can understand that this can work with physical interfaces, but when subinterfaces, how will that work? Some food for thought will be appreciated.

    Reply to this comment
    • certskills Author April 27, 06:38

      Faizan,
      Sure thing. It’s actually the one point that I didn’t force you to a single choice through the wording. I agree with what you wrote, so for this config, let’s say you also had one extra router that you used to create the Frame Relay cloud. That is, the three routers actually connected to three different ports on a single overhead “Frame Relay” router. Then, you pick one convention for your cabling, so that either all the DCE ends connect to the normal routers, or all connect to the Frame Relay router. I’ll stop the food for thought there, and leave the rest for the answer. Thanks for the note…
      Wendell

      Reply to this comment
View comments

Write a comment

Comment; Identify w/ Social Media or Email

Subscribe

Subscribe to our mailing list and get interesting stuff and updates to your email inbox.

Thank you for subscribing.

Something went wrong.

Search

Categories