Student Name _________________________________ Date _____________

SEC450 Database Traffic Load iLab

Objectives
In this lab, the students will examine the following objectives.

• Creating Database traffic using the traffic generator
• Specifying link statistics to monitor traffic flow
• Running discrete event simulation (DES)
• Adjusting link speeds to handle Database traffic.

Scenario
A small company is using the topology shown below. The Public Server is actually an offsite Database Server that contains company records. Assume that the 200.100.0.0/16 network represents the Internet. The Dallas and Chicago Servers and Hosts need to access the database server. Only users in the Dallas and Chicago LANs should be able to access the database server.

Topology

The last page of the lab assignment document contains a full page Topology. Remove this page and use it for reference to the topology and the IP addresses. Initial OpNet Preparation

The Week 5 iLab is entitled Database Traffic Load. The following steps show how to create the project required for the Week 5 iLab.

• Log into the Citrix iLab Environment (lab.devry.edu).

• Click on the OpNet 17 icon.

• Click the Accept button to Open OpNet 17.

• Click File/Open and navigate to the F:\op_models\SEC450\SEC450.project\SEC450 file and click Open.

• In OpNet 17 with the SEC450 project open, click File/Save As.

• Save the project in the F:\op_models\SEC450 directory as DB_TrafficLoad.

You are now ready to begin the Database Traffic Load iLab with a project called DB_TrafficLoad.

Initial Configuration
The Dallas, Chicago, and ISP Routers’ FastEthernet and Serial interfaces used for the lab have been correctly configured and enabled. Unused interfaces have been shut down. The RIP routing tables are complete for all routers and hosts. No ACLs have been applied to any of the routers.

Lab Data Collection and Submission
Download and open the lab document file: SEC450_W5_DBTrafficLoad_Report.docx. Enter your name and date at the top of the lab report document. As you complete each task of the lab assignment, copy all relevant configuration information, web reports, tables, answered questions, and or captured screen shots (as specified in the iLab assignment) into this lab document. You will submit the completed SEC450_W5_DBTrafficLoad_Report.docx file into this week’s eCollege iLab Dropbox.

Note: RED text indicates the required capture of commands or windows from the OpNet program into your lab document. All completed tables and answered questions in the lab assignment must be transferred to your submitted lab document.

Task 1—Verify Initial Connectivity Between Router and Hosts

• We need to verify that there are no ACLs active in the network topology, Open the View menu and select Visualize Protocol Configuration -> IP Security Configuration. An Information box should appear indicating no packet filtering on the routers. If you see any evidence of ACLs, delete the access list and remove the ACL from the interface.

• To verify that Interfaces are active, open the View menu. Select Visualize Protocol Configuration -> IP Interface Status. Green arrows will indicate active interfaces. If you have any interface problems, try to correct the problem using the router's VirtualCLI. Use C to clear the icons from the topology.

• Run a Flow Analysis to update the topology. Open the Visual CLI on the ISP router and ping all of the Servers and Host PCs including the Attack PC Use the IP addresses indicated on the network topology page. Select the commands you entered in the Virtual CLI using the mouse and click on the Copy button. Use V to paste the commands into your lab document.

Task 2—Set Up Database Traffic Flows

• In this task, we will set up traffic parameters for the public database server to all Dallas and Chicago Servers and Hosts. The first thing we will do is set the link speed of the serial links from the ISP Router to the Dallas and Chicago Routers to 64,000 bps. Many WAN providers offer link speeds as multiple of 64,000 bps which also referred to as DS0.

• Right-click on the ISP -> Dallas serial link and select Edit Similar Links. In the dialog that follows, set the link speed to 64,000 for both serial links. Click OK.

• Click on the Dallas Server and while holding down the key, select the Dallas Host, Public Server, Chicago Server, and the Chicago Host. Your topology should look like the one on the right.

• From the main menu, select Traffic -> Create Traffic Flows -> IP Unicast. In the dialog box that appears, click the radio button To other selected node from: and select Public Server. For Intensity, enter 50 Packets/sec and 60000 bits/sec.

For socket information, the protocol will be TCP and the Source port will be set to sqlnet – Oracle. When you have completed the traffic configuration, capture the Traffic Generator window () as shown below and paste (V) it into your lab document. After the copy and paste operation, click the Create button.

Task 3—Discrete Event Simulation (DES)

• Right-click on an empty area of the topology and select Choose Individual DES Statistics. Expand the Link Statistics tree item and under point-to-point, check throughput (packets/sec) -->, throughput (packets/sec) and utilization Dallas serial link and select View Results. Expand the Object Statistics tree item and check Throughput –(packets/sec) -> and Utilization-->. You will see two graphs. Change the Stacked Statistics option to Overlaid Statistics so we can see the results in one graph.

• Note that the Utilization is 100% and the Throughput is truncated at less than 50 packets per second. This indicates total saturation of the serial link. Capture this DES Graphs window () and paste it (V) into your lab document.

• Right-click on the Chicago->ISP serial link and select View Results. Expand the Object Statistics tree item and check throughput –(packets/sec) (Report Utilization). This should show a Utilization value less than 50%. Click the Show button. This will display just the graph. Capture the DES Graph window () and paste it into your lab document. Save the project with all the changes we have made.