CCNA 1. Networking Basics v3.1.1 Student Lab Manual (796248), страница 20
Текст из файла (страница 20)
Note the Problems tab and thechoices for focusing the investigation.On the Notification, notice that e-mail notifications can be sent out. To use this feature, the studentwould need the same information as that required to set up an Internet e-mail account or Outlook email account.11 - 12CCNA 1: Networking Basics v 3.1 - Lab 7.1.9aCopyright 2003, Cisco Systems, Inc.If the student starts the Agent again, it may take a few minutes to detect any changes that occurredwhile the agent was off.Step 10 Experiment with NIExperiment with the NI tool by looking at the different devices.If NI is installed on the classroom computers, investigate the devices on that larger network.ReflectionHow might this information be used in troubleshooting?__________________________________________________________________________What advantages over HyperTerminal might it have for troubleshooting documentation?__________________________________________________________________________12 - 12CCNA 1: Networking Basics v 3.1 - Lab 7.1.9aCopyright 2003, Cisco Systems, Inc.Lab 7.1.9b Introduction to Fluke Protocol InspectorObjectiveThis lab is a tutorial demonstrating how to use the Fluke Networks Protocol Inspector to analyzenetwork traffic and data frames.
This lab will demonstrate key features of the tool that can beincorporated into various troubleshooting efforts in the remaining labs.Background / PreparationThe output in this lab is representative only. Output will vary depending on the number of devicesadded, device MAC addresses, device hostnames, which LAN is joined, and so on.This lab introducing Protocol Inspector will be useful in later troubleshooting labs as well as in thefield.
While the Protocol Inspector (PI) software is a valuable part of the Academy program, it is alsorepresentative of features available on other products in the market.Options for conducting this lab.1) Use Protocol Inspector or Protocol Expert in a small controlled LAN that is configured by theinstructor in a closed lab environment as shown in the figure above. The minimumequipment should include a workstation, a switch, and a router.2) Perform the steps in a larger environment such as the classroom or the school network tosee more variety. Before attempting to run PI or PE on the school LAN, check with theinstructor and the network administrator.At least one of the hosts must have the Protocol Inspector software installed. If the lab is done inpairs, having the software installed on both machines means that each person can run the lab steps.However, each host may display slightly different results.1 - 18CCNA 1: Networking Basics v 3.1 - Lab 7.1.9bCopyright 2003, Cisco Systems, Inc.Step 1 Configure the lab or attach a workstation to the school LANOption 1.
If the closed lab environment is selected, cable the equipment as shown above and loadthe configuration files into the appropriate routers. These files might be preloaded. If not,obtain them from the instructor. These files should support the IP addressing scheme asshown in the figure above and the table below.Configure the workstations according to the specifications as in the figure shown above and tablebelow.Host #1Host #2IP Address: 192.168.1.20IP Address: 192.168.2.10Subnet mask: 255.255.255.0Subnet mask: 255.255.255.0Default Gateway: 192.168.1.1Default Gateway: 192.168.2.1Option 2. If option 2, connect to school LAN, is selected, simply connect the workstation, with PI orPE installed, directly to a classroom switch or to a data jack connected to the school LAN.Step 2 Start Protocol Inspector EDV programFrom the Start menu, launch the Fluke Protocol Inspector EDV program.Note: The first time the program isrun, a message will appear that asks,“Do you have any Fluke analyzercards or Fluke taps in your localsystem?”If using the educational version, clickon No.
If answering yes or if thefollowing screen appears, just clickon OK without selecting any ports.There are four main Protocol Inspector views, which include the following:•Summary View•Detail View•Capture View of Capture Buffers•Capture View of Capture FilesThe program opens in the Summary View. This view shows several windows used by the tool.
TheResource Browser window in the upper left corner shows the only monitoring device that is2 - 18CCNA 1: Networking Basics v 3.1 - Lab 7.1.9bCopyright 2003, Cisco Systems, Inc.available, which is the NDIS 802.3 Module (NIC) of the host. If there were Protocol Media Monitors,they would be displayed with the associated host devices. The Alarm Browser on the left side andMessage Area at the bottom will be covered later.The Monitor View, which is in the main window on the upper right, monitors one resource perwindow in a variety of viewing options.
The example below and probably the startup screen show noinformation in the Monitor View window. The Stop in the upper-left corner of the Monitor Viewwindow confirms that no monitoring is occurring.NICMonitor ViewResource BrowserMessage AreaStep 3 Start the Monitor / Capture processTo start the monitoring/capturing process, use the Startbutton or Module | Start from the menusystem. The Utilization chart should start showing activity like the graphic below:3 - 18CCNA 1: Networking Basics v 3.1 - Lab 7.1.9bCopyright 2003, Cisco Systems, Inc.The word Arm should appear where Stop had been before.
If opening the Module menu, notice thatStop is now an option while Start is muted. Do not stop the process yet. Restart it again if it isstopped.The tabs at the bottom of the window show the resulting data in a variety of forms. Click on each andnote the result. Transmit (Tx), Alarms, and Alarm Log will be blank. The following is the Received(Rx) frames, which indicates that Broadcast and Multicast frames are being received, but they maynot show any Unicasts.Using the console connection to the router, ping the monitoring host (192.168.1.20 or 192.168.2.10),and notice that Unicast frames appear. Unfortunately, the errors shown in the third column will notappear in the lab exercise unless a traffic generator like the Fluke Networks OptiView product hasbeen added.4 - 18CCNA 1: Networking Basics v 3.1 - Lab 7.1.9bCopyright 2003, Cisco Systems, Inc.The Description tabreveals the MAC address,manufacturer, and modelof the NIC.
It also showswhich Error Counters areon.Take a few minutes tobecome familiar with thetabs and the scrollfeatures of the window.Step 4 View DetailsTo go to the Detail View window click on the Detail Viewbutton in the toolbar or double clickanywhere on the Monitor View chart. This will open a second window that should look something likethe following, after maximizing the Utilization / Errors Strip Chart (RX) window.Note: If necessary, activate all toolbars on the View menu.5 - 18CCNA 1: Networking Basics v 3.1 - Lab 7.1.9bCopyright 2003, Cisco Systems, Inc.Initially, the chart output is the same as before.
However, there are many more toolbar and menuoptions than in the Summary View. Before looking at these features, confirm that the Chart andTable tabs show the same information that was seen earlier.Like all Windows compliant programs, placing the mouse over a button brings up a screen tip brieflyidentifying the purpose of the button. As the mouse moves over the buttons, notice that some aremuted. This means that the feature is not appropriate under the current circumstances.
In somecases, it is not supported in the educational version.Note: There is a complete display of the toolbars and what they do in the Appendix at the end ofthis lab.Click on the Mac Statisticsbutton to see the Rx frame table data displayed in another format.The result should be obvious. Maximize the resulting window. The one piece of new information isthe Speed, which shows the NIC transmission rate.button to see a distribution of the size frames beingClick on the Frame Size Distributionreceived by the NIC. Placing the mouse over any bar will display a small summary like the oneshown below.
Maximize the resulting window.Try the Pie, Bar, and Pausebuttons in the upper-left corner. Note that the Pause stops thecapture, so click on it again to resume the capture. Look at both the Table and Chart tab displays aswell.With the sample configurations, the student should be getting mainly small frames, because the onlything happening is routing updates. Try using the extended Ping feature from the router Consoleconnection, and specify 100 pings with a larger packet size.If maximizing each new display, return to any previous view by using the Window menu. The studentcan also Tile the windows.
Experiment with the Window menu features and then close any unwantedviews.Click on the Protocol Distributionbutton to see a distribution of the protocols being receivedby the NIC. Placing the mouse over any bar will display a small summary panel. Maximize theresulting window.6 - 18CCNA 1: Networking Basics v 3.1 - Lab 7.1.9bCopyright 2003, Cisco Systems, Inc.Try each of the buttons and tabs to see the results. The Net button shows only network protocols.The 323 button refers to the H323 Voiceover IP protocols. Depending on the version of ProtocolExpert or Inspector that is being used, this button may be called VoIP.
Look at the Frm (frame) andthe Abs Bts (absolute bytes) and Rel Bts (relative bytes) to see the results. Remember that thePause button stops the capture.Click on the Host Tablebutton to see the MAC stations and related traffic.Notice the Spanning Tree, AppleTalk, and OSPF traffic. Be sure to look at the Table tab to see theactual values.Click on the Network Layer Host Tablerelated traffic.7 - 18CCNA 1: Networking Basics v 3.1 - Lab 7.1.9bbutton to see the network (IP/IPX) stations andCopyright 2003, Cisco Systems, Inc.Any pings and any additional hosts that might have added to the configuration will impact the actualaddresses that appear on the right.Click on the Application Layer Host Tableapplication.button to see the network station traffic bybuttons.
They create host-to-host matrices for MAC,Experiment with the next threeNetwork, and Application layer conversations. The following is an example of the Network Layer(IP/IPX) conversations.8 - 18CCNA 1: Networking Basics v 3.1 - Lab 7.1.9bCopyright 2003, Cisco Systems, Inc.buttons, the first is the VLAN button that shows network traffic on VLANs.Of the next twoThis sample does not use VLANs. Remember this button when troubleshooting VLANs later.The second button creates a matrix comparing MAC and Network station addresses to names. In thefollowing example the second row is a Novell station.The Name Tablebutton opens the current name table for viewing or editing.button shows the expert symptoms discovered.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
