Reference:
http://www.cisco.com/en/US/tech/tk713/tk237/tech_configuration_examples_list.html
Objectives:
• To configure Cisco routers to use Frame Relay, and use the W&G analyzers to monitor the Frame Relay links.
Frame Relay
In this part you will re-visit the frame relay configuration done previously. A total of 8 racks are used in the network used in the network as shown in the figure 2. Students are required to configure the frame relay network in two major steps,
1. Configure a frame relay hub and spoke network with in each rack by making R2 as frame switch. Refer to the Figure 1 for the network illustration. Make sure that you have connectivity among all routers in the rack.
2. Configure the inter- rack connectivity using R1 on each rack to connect to frame relay cloud to have inter-rack connectivity as shown in Figure 2. The frame relay cloud (as shown in the figure 2) consists of Cisco 4000 Switch. This switch is already configured with full mesh PVCs. The DLCIs used to identify the PVCs between the eight ports are given on the INWK lab site. As is convention, the 4000 have been configured as the DCE end of each link. To configure your links, specify:
o An IP address (to connect through to each other, all interfaces must be on
the same subnet)
o The LMI type (the switch has been set to run the default LMI type Cisco) o The mapping between each IP address you are trying to reach and the DLCI
associated with the PVC between it and your input link on the switch.
o Ensure that you have connectivity to all of the other routers connected to the
Frame Relay switch.
Note: Please choose appropriate IP addressing scheme and DLCI within each rack.
Use the Domino WAN analyzer to monitor a Frame Relay link. Check the manual to identify the useful functions available for analyzing a Frame Relay link.
Questions:
1. Notice that you cannot ping the any of the local serial interfaces on Frame Relay DTEs. What is the reason for that? How can you make this work?
2. What is the purpose of Frame Relay LMI? Briefly describes the three types commonly used?
3. The frame relay cloud in this lab is actually a single Cisco 4000 router. In order to build the full mesh topology between all racks how many map statements are required?
4. Print the router configuration and attach it to the report. Show output form the important “show command” like “show frame pvc”,“show frame map” etc and highlight the important information.
5. Briefly describe the steps to configure the network.
2XR2 2XR4 S0/0 S1/0 S0/1 2XR1 2XR3 S0/0 S1/0 S1/0 24R2 2XR4 S0/0 S1/0 S0/1 2XR1 2XR3 S0/0 S1/0
S1/0 Frame Relay
Feb 28, 2004 Telcom & WAN
Frame Relay - Figure 1 Lo 0 Lo 0 Lo 0 Lo 0 Lo 0 Lo 0 Sniffer- PC Wan- Analyzer Prepared by: Naman Aslam
FR Cloud Cisco 4000 M Switch
S1/1 21R2 21R4 S1/1 S0/0 S1/0 S0/1 21R1 21R3 S0/0 S1/0 S1/0 22R2 22R4 S1/1 S0/0 S1/0 S0/1 22R1 22R3 S0/0 S1/0 S1/0 25R2 25R4 S1/1 S0/0 S1/0 S0/1 25R1 25R3 S0/0 S1/0 S1/0 24R2 24R4 S0/0 S1/0 S0/1 24R1 24R3 S0/0 S1/0 S1/0 S4 S5 S6 S7
Feb 18, 2005 Telcom & WAN
Lab 4 - Frame Relay Network Performance (OPNET
Simulation)
Reference:
OPNET lab ManualIntroduction:
Frame Relay is a connection-oriented, unreliable technology based on virtual circuits. A virtual circuit must be set up between a source and destination before any data may be exchanged. Most Frame Relay service provider support Permanent Virtual Circuits (PVCs) that are long-lived connections as opposed to the Switched Virtual Circuits (SVCs), which are set up at call time. When PVC is set up, certain parameters govern the behavior of the PVC agreed upon. These include committed information Rate (CIR), committed burst rate (Bc) and the excess burst rate (Bc). The CIR is the rate, which service provider guarantees to the customer. The committed burst rate specifies how quickly data may be sent. For example a customer may contract for CIR of 64 kb/sec and Bc of 32 Kb/sec in any 100 ms period. Frame Relay service providers will accept the additional data over CIR and transmit it if there is excess capacity in the network at that time. The amount of excess data that they will carry is defined by the excess burst rate. Any data frames that are sent in excess of CIR are marked with Discard Eligible Bit set. These frames are discarded in the event of congestion.
OBJECTIVE:
Build the Frame relay simulation model and examine the behavior of PVC as the service contract parameters are varied.
Building the Simulation Model:
Start the OPENT IT GURU Academic Edition
Select the File tab => New Choose Project and click OK
Change the Project Name to xx_WAN_FrameRelay (here xx are you initials). Set the Scenario Name to CIR64 and click OK
In the Initial Topology window, select Create Empty Scenario and click Next In the Choose Network Scale window, choose World and click on Next In the Choose Map window, choose usa and click Next
In the Select Technologies window, scroll down and include frame_relay _advanced model family, and then click on Next
First we will configure a bursty data application to generate traffic over our frame relay network. The File Transfer Protocol will serve our purposes.
Select an Application Config object form the Object Palette and place it in the project workspace. Right click on the object and choose Edit Attributes. Set the name attribute to Bursty Application. Expand the Application Definitions attribute and set the rows to 1. Expand the row 0 attribute and set the Name attribute to FTP_Bursty. Expand the
Select a Profile Config object form the Object Palette and place it in the project
workspace. Right click on the object and choose Edit Attributes. Set the name attribute to Bursty Profile. Expand the Profile Configuration attribute and set the rows to 1. Expand the row 0 attribute and set the Name attribute to FTP_Bursty_Profile. Expand the
Applications attribute and set the rows to 1. Expand row 0 attribute and set the Name to FTP_Bursty. Set the Repeatability attribute to Once at Start Time. Click on OK to close the window.
Select fr_32_cloud object form the object palette and place in the project workspace. Right click on the cloud and choose View Node Description. The cloud represents a WAN that consists of Frame Relay capable switches and that supports up to 32 Frame Relay
connections.
Right click on the cloud and select Set Name to Frame_Relay_Cloud. Click OK to close the window.
Select an fr_wkstn_adv device from the Object Palette and place in the project workspace. Right click on the station and choose View Node Description. Note that the station supports the Frame Relay protocol. Now client should be set up to use the burst FTP application.
Select an fr_server _adv device from the Object Palette and place in the project workspace. Right click on the server and choose View Node Description. Note that the server also supports the Frame Relay protocol. Now server should be set up to support the burst FTP application.
Select two fr8_switch_adv objects form the object palette. Place one next to the client and one next to the server. Right click on one of the switches and choose View Node
Description. Note that the switch takes action when it becomes congested. It will discard the frames marked with Discard Eligible bit first but may even discard the normal frames. Click on close window icon to close the window. Right click on client’s switch name and set its name to Client Switch. Right click on server’s switch name and set its name to Server Switch.
Select FR_T1-int links form the Object palette and use them to connect the client to its switch, server to its switch and two switches to the Frame Relay Cloud. Note that T1 is 1.5 Mbps.
Set up a PVC between the client and the server so that they can communicate. Select FR PVC Config form the object palette and place it in the workspace. Set its Name to the PVC Config. The FR PVC Config onject must be placed in the workspace before any PVCs may be set up. Click Ok to close the window.
Configure and Run Simulation:
Select the Simulation tab => Choose Individual Statistics.
Expand the Global Statistics item and the Frame Relay Item, and select the Delay (sec), Delay (variance) and Residual Error Rate.
Expand the FTP item and select the Download Response Time (sec) and Traffic Received (bytes/sec).
Expand the Node Statistic item and the Frame Relay PVC item and select the BECN Status, DE Status and FECN Status.
Duplicate the scenario by choosing Scenario =>Duplicate Scenario and change its name to CIR128.
Change the contract parameters as, CIR – 128000, Bc – 128000 and leave Be as same. Click OK to close the window.
RUN THE SIMUALTION
Select the Scenarios tab => Manage Scenarios. Edit the Results fields in both scenarios to <collect >
When simulation has completed, click OK to close the window.
Questions:
1. Plot the following results and comment on them.
a. Ftp Download Response Time for both scenarios. b. Ftp Traffic Received for both scenarios
c. Delay and Delay Variance in both Scenarios. d. Frame Relay Residual Error Rate in both scenarios.
2. How much traffic is being produced by the Bursty Server? You can calculate this data rate using Inter-Request Time and File size parameter set in the bursty application.
3. Given the traffic level calculated in the Q2 comment on how this traffic is carried through the network keeping considering Contract Parameters of PVC?
4. Duplicate CIR64 scenario and replace T1 link between client and its switch to FR_DS0_int link. Remember DS0 in 64 Kbps. Rerun the simulation and inspect the BECN and FECN status for both the client and server. How do they compare to the CIR64 scenario results? Explain the usage of BECN and FECN bits in frame relay header? Also inspect the Residual Error Rate? How does it compare to the CIR64 scenario.
