Lab 15a: Configuring Voice over Frame Relay-Part II

Lab 14: Configuring Frame Relay Networks, Traffic Shaping, OSPF, & DLSw/LLC2 ”Part I

Practical Scenario

Most networks don't grow at an even, incremental basis. Some portions of the network might have faster newer links, while other parts of it could be older and slower. Oversubscription of links can be a common problem in Frame Relay networks. Traffic shaping helps address this problem. Enabling traffic shaping allows greater control over bursty traffic and the amount of data sent out an interface at any given time. This greatly helps the problem of high-speed links pushing too much data toward lower-speed links. This practice lab challenges you to configure traffic shaping in a multipoint Frame Relay network.

Lab Exercise

The Jet Propulsion Laboratory (JPL) receives large graphic images from several telescopes. When the JPL receives these images, it immediately downloads them to Cape Canaveral in Florida and Houston , Texas. These images can be large at times and quickly saturate the links of the two NASA sites. To control these sudden bursts of large data, the JPL wants to deploy Frame Relay traffic shaping (FRTS). Use the following guidelines for your design and FRTS configuration:

• Use the IP network of 128.10.0.0 for all your addressing.

• Allow for only 14 host addresses on the JPL LAN.

• Use a 29-bit subnet mask on the WAN.

• Use 24-bit addressing on the remaining LANs.

• Use OSPF as the routing protocol for IP. Assign the areas as depicted in Figure 5-8.

  Figure 5-8. NASA Frame Relay Network

  

• Configure Frame Relay traffic shaping using the following guidelines: The local port speed of JPL router is 1.544 Mbps. The CIR on the PVC to nasa_houston is 32 kbps. The local port speed of nasa_houston is 64 kbps. Configure FRTS to optimize for the slowest link or the nasa_houston pvc.

• (Optional): Configure DLSw lite between the two NASA routers' Ethernet segments, and use LLC2 as the encapsulation type.

Lab Objectives

• Configure the network as depicted in Figure 5-8. Configure IP by using the previously stated guidelines.

• Use Frame Relay as data link layer protocol on the WAN.

• Configure Frame Relay traffic shaping on the JPL router by using the previously stated guidelines.

• Optional: Configure DLSw between the two NASA routers; use Frame Relay as the peer type.

Equipment Needed

• Four Cisco routers, connected through V.35 back-to-back cable or in a similar manner. One router will serve as a frame switch and require three serial ports.

• Three LAN segments, provided through hubs or switches.

Physical Layout and Prestaging

• Configure a frame switch to provide the PVCs as listed in Figure 5-8. See Chapter 1 if you need assistance in configuring a Frame Relay switch. Example 5-31 provides a sample frame switch configuration.

• Connect the hubs and serial cables to the routers, as shown in Figure 5-8.

• Connect three Ethernet hubs form three LAN segments, as shown in Figure 5-8.

Example 5-31 Frame Relay Switch Configuration

  hostname frame_switch   !   frame-relay switching   !   <<<text omitted>>>   !   interface Serial0   no ip address   encapsulation frame-relay   no fair-queue   clockrate 148000   frame-relay lmi-type cisco   frame-relay intf-type dce   frame-relay route 121 interface Serial1 120   frame-relay route 165 interface Serial3 166   !   interface Serial1   no ip address   encapsulation frame-relay   clockrate 148000   frame-relay lmi-type ansi   frame-relay intf-type dce   frame-relay route 120 interface Serial0 121   frame-relay route 130 interface Serial3 131   !   <<<text omitted>>>   !   interface Serial3   no ip address   encapsulation frame-relay   clockrate 64000   frame-relay lmi-type ansi   frame-relay intf-type dce   frame-relay route 131 interface Serial1 130   frame-relay route 166 interface Serial0 165