resourcecontent.html

ccna

<p class="smtext">Estimated time: 30 min.</p>
<p align="left">
                                    <span class="resourceSectionTitle">Objectives: </span>
                                </p>
                                <blockquote>
                                    <span class="smtext">
                                        <ul type="disc">
<li>Use Protocol Inspector (or equivalent) software to view dynamic TCP operations</li>
</ul>
                                    </span>
                                </blockquote>
<p align="left">
                                    <span class="resourceSectionTitle">Background: </span>
                                </p>
                                <blockquote>
                                    <p class="smtext">Protocol analysis software has a feature called capture. This feature allows all frames, through an interface, to be captured for analysis. With this feature, you can see how the Transmission Control Protocol (TCP) moves segments filled with user data across the network. You may have found TCP to be a bit abstract, but with the protocol analyzer we can see just how important TCP is to network processes (such as email and web-browsing).</p>
                                </blockquote>
<p align="left">
                                    <span class="resourceSectionTitle">Tools / Preparation:</span>
                                </p>
                                <blockquote>
                                    <p class="smtext">Each PC must be running Windows 95, 98, or NT, Microsoft TCP/IP stack, and Winsock 2.0. Fluke Protocol Inspector ver. 3.0 (or higher) Software (Check the Web for downloadable upgrades) must be installed on each PC. During the installation of the software you must specify which network adapter (NIC, dialup, and so on) you wish to monitor. Then, specify the NIC that attaches the PCs to an Ethernet. The PCs should be on either a 10BASE-T or 100BASE-TX Ethernet network. Preferably, the network includes servers, switches, routers, printers, and a connection to a web server, or preferably the Internet (this will make the protocol analysis more interesting). The following resources will be required:</p>
                                    <span class="smtext">
                                        <ul type="disc">
<li>PC with Windows 95, 98, or NT, Microsoft TCP/IP stack, and Winsock 2.0.</li>
<li>Fluke Protocol Inspector ver. 3.0 (or higher) Software (Check the Web for downloadable upgrades)</li>
<li>Browser and email applications installed and running</li>
</ul>
                                    </span>
                                </blockquote>
<p align="left">
                                    <span class="resourceSectionTitle">Worksheet</span>
                                </p>
                                <blockquote>
                                    <span class="smtext">
                                        <ol>
<li>Open Protocol Inspector and your browser.</li>
<li>Go to detail view.</li>
<li>Start a capture.</li>
<li>Request a Web Page.</li>
<li>Watch the monitor view while the web page is requested and delivered.</li>
<li>Stop the capture.</li>
<li>Study the TCP frames, HTTP frames, and statistics using various views, especially the detail view.</li>
<li>Using the detail view, explain what evidence it provides about a) TCP handshakes b) TCP acknowledgments c) TCP segmentation and segment size d) TCP sequence numbers and e) TCP sliding windows.</li>
</ol>
                                    </span>
                                </blockquote>
<p align="left">
                                    <span class="resourceSectionTitle">Reflection:</span>
                                </p>
                                <blockquote>
                                    <p class="smtext">Did this lab help you to visualize the TCP protocol in action? Why or why not?</p>
                                    <p class="smtext">
                                        <img border="0" src="../../../../../CHAPID=knet-v214aCH47512/RLOID=knet-v214aRLO47839/RIOID=knet-v214aRIO125378/knet/v214aclixsi144/line450.gif" width="450" height="1"></p>
                                    <p class="smtext">
                                        <img border="0" src="../../../../../CHAPID=knet-v214aCH47512/RLOID=knet-v214aRLO47839/RIOID=knet-v214aRIO125378/knet/v214aclixsi144/line450.gif" width="450" height="1"></p>
                                </blockquote>
<p align="left">
                                    <span class="resourceTitle">LAB 12.1.3 PROTOCOL INSPECTOR and TCP - ANSWERS</span>
                                </p>
                                <span class="smtext">
                                    <ol class="resourceAnswer">
<li>Open protocol inspector and your browser.
<p class="resourceAnswer">
                                                <b>
                                                    <u>Students should be familiar with this from earlier labs.</u>
                                                </b>
                                            </p>
                                        </li>
<li>Go to detail view.
<p class="resourceAnswer">
                                                <b>
                                                    <u>Again, students should be familiar with this from earlier labs. By this lab they should have basic proficiency in navigating the Protocol Inspector.</u>
                                                </b>
                                            </p>
                                        </li>
<li>Start a capture.</li>
<li>Request a Web Page:
<p class="resourceAnswer">
                                                <b>
                                                    <u>Using a browser, either go to a www address or enter an IP address.</u>
                                                </b>
                                            </p>
                                        </li>
<li>Watch the monitor view while the web page is requested and delivered.
<p class="resourceAnswer">
                                                <b>
                                                    <u>The monitor view should show bursts of activity corresponding to the Web Page request and reply.</u>
                                                </b>
                                            </p>
                                        </li>
<li>Stop the capture.
<p class="resourceAnswer">
                                                <b>
                                                    <u>Stop the information flowing into the database.</u>
                                                </b>
                                            </p>
                                        </li>
<li>Study the TCP frames, HTTP frames, and statistics using various views, especially the detail view.
<p class="resourceAnswer">
                                                <b>
                                                    <u>Going line by line through the Capture View Database can be intimidating, but this is just an overview look to get a flavor of the information available and the "back and forth" nature of TCP. The curriculum details various TCP characteristics, but without actually acting them out (in class) and seeing them (with a Protocol Analyzer) TCP can be very abstract.</u>
                                                </b>
                                            </p>
                                        </li>
<li>Using the detail view, explain what evidence it provides about a) TCP Handshakes b) TCP acknowledgments c) TCP segmentation and segment size d) TCP sequence numbers and e) TCP sliding windows.
<p class="resourceAnswer">
                                                <b>
                                                    <u>a) look at the beginnings of the TCP sequences</u>
                                                </b>
                                            </p>
<p class="resourceAnswer">
                                                <b>
                                                    <u>b) look at the back and forth nature of the TCP conversation</u>
                                                </b>
                                            </p>
<p class="resourceAnswer">
                                                <b>
                                                    <u>c) look at the byte size of the TCP frames</u>
                                                </b>
                                            </p>
<p class="resourceAnswer">
                                                <b>
                                                    <u>d) look at the sequence numbers for each TCP frame and</u>
                                                </b>
                                            </p>
<p class="resourceAnswer">
                                                <b>
                                                    <u>e) look at the variations in the byte size of the frames (?)</u>
                                                </b>
                                            </p>
                                        </li>
</ol>
                                </span>
                                <p align="left">
                                    <span class="resourceAnswerSectionTitle">Reflection:</span>
                                </p>
                                <blockquote>
                                    <p class="resourceAnswer">Did this lab help you to visualize the reality of the TCP protocol in action? Why or why not?</p>
                                    <p class="resourceAnswer">
                                        <b>
                                            <u>Hopefully the students will associate their HTTP request with the many TCP operations that occurred.</u>
                                        </b>
                                    </p>
                                </blockquote>
</td>
                        </tr>
                    </table>
                </td>
            </tr>
        </table>
    </body>
</html>