CCNA 1. Networking Basics v3.1.1 Student Lab Manual (796248), страница 18
Текст из файла (страница 18)
A console session allows the user to check or change theconfiguration of the switch or router and is the simplest method of connecting to one of thesedevices.This lab should be performed twice, once with a router and once with a switch to see the differencesbetween the user interfaces. Start this lab with the equipment turned off and with cablingdisconnected. Work in teams of two with one for the router and one for the switch. The followingresources will be required:1-6•Workstation with a serial interface and HyperTerminal installed•Ethernet 10BASE-T or Fast Ethernet switch•Cisco Router•Rollover or console cable for connecting the workstation to the router or switchCCNA 1: Networking Basics v 3.1 - Lab 5.2.7Copyright 2003, Cisco Systems, Inc.Step 1 Identify the Router/Switch console connectorsa.
Examine the router or switch and locate the RJ-45 connector labeled “Console”.Step 2 Identify the computer serial interface, which is COM 1 or 2a. It should be a 9 or 25-pin male connector labeled serial or COM1. It may or may not beidentified.Step 3 Locate the RJ-45 to DB-9 adapterOne side of the adapter connects to the PCs serial interface and the other to the RJ-45 rollover cableconnector. If the serial interface on the PC or dumb terminal is a DB-25, an RJ-45 to DB-25 adapterwill be needed. Both of these adapters typically come with a Cisco router or switch.Step 4 Locate or build a rollover cableUse a rollover cable. If necessary, make one of adequate length to connect the router or switch to aworkstation.2-6CCNA 1: Networking Basics v 3.1 - Lab 5.2.7Copyright 2003, Cisco Systems, Inc.Step 5 Connect the cabling componentsConnect the rollover cable to the router or switch console port RJ-45 connector.
Next, connect theother end of the rollover cable to the RJ-45 to DB-9 or DB-25 adapter. Finally, attach the adapter to aPC serial port, either DB-9 or DB-25, depending on the computer.Step 6 Start the PC HyperTerminal programa. Turn on the computerb. From the Windows taskbar, locate the HyperTerminal program:Start > Programs > Accessories > Communications > Hyper TerminalStep 7 Name the HyperTerminal SessionAt the “Connection Description” popup enter a name in the connection Name field and select OK.3-6CCNA 1: Networking Basics v 3.1 - Lab 5.2.7Copyright 2003, Cisco Systems, Inc.Step 8 Specify the computer connecting interfaceAt the “Connect To” popup, use the drop down arrow in the Connect using: field to select COM1 andselect OK.Note: Depending on which serial port was used on the PC, it may be necessary to set this toCOM2.Step 9 Specify the interface connection propertiesa.
At the “COM1 Properties” popup use the drop down arrows to select the following:Bits per second = 9600Data bits = 84-6CCNA 1: Networking Basics v 3.1 - Lab 5.2.7Copyright 2003, Cisco Systems, Inc.Parity = NoneStop bits = 1Flow control = Noneb. Then select OK.c.When the HyperTerminal session window comes up, turn on the router or switch. If the router orswitch is already on, press the Enter key. There should be a response from the router or switch.If there is, then the connection has been successfully completed.Step 10 Observe the router or switch user interfacea. Observe the user interface.b. If this is a router, what is the prompt? ________________________c.If this is a switch, what is the prompt? ________________________Step 11 Close the Sessiona.
To end the console session from a HyperTerminal session, select the following:File > Exitb. When the HyperTerminal disconnect warning popup appears, select Yes.5-6CCNA 1: Networking Basics v 3.1 - Lab 5.2.7Copyright 2003, Cisco Systems, Inc.c.The computer will then ask if the session is to be saved. Select No.Step 12 Shut down the router or switch and store the cables6-6CCNA 1: Networking Basics v 3.1 - Lab 5.2.7Copyright 2003, Cisco Systems, Inc.Lab 7.1.2 Waveform DecodingObjectiveThe purpose of this lab is to integrate knowledge of networking media, OSI Layers 1, 2, and 3, andEthernet, by taking a digital waveform of an Ethernet frame and decoding it. Specifically, studentswill do the following:•Review numbering systems, OSI concepts, and encoding methods as background from Module1.•Learn to decode the waveform back into binary, reorder the binary, and identify Ethernet fieldboundaries from Module 2.•Decode the Ethernet Length/Type field, locate and read RFCs, and decode Layer 3 of thewaveform from Module 3.•Use a Protocol Analyzer from Module 4.Background / PreparationAs a student of networking, there are many new concepts to learn:•The OSI model•Networking media and signals•Ethernet•The TCP/IP protocolsNetwork administrators, technicians, and engineers study and troubleshoot a network using ProtocolAnalysis software.
Protocol Analysis software allows the capture and interpretation of frame-leveldata, which is crucial for understanding what is happening on a live and perhaps troublesomenetwork. Hand-decoding the signal gives more insight into what the software is doing automatically.Therefore, this lab provides an important foundation for future learning of network troubleshooting.A Digital Oscilloscope was attached to an Ethernet 10BASE2 coaxial cable to capture actualEthernet waveforms.
Although it is possible to capture waveforms on 10BASE-T and 100BASE-TXtwisted pair media, the coaxial cable gives the cleanest and most readable waveform data. This datais available from the instructor. Decoding the waveform is a crucial step in understanding hownetworks operate.For the first part of the lab, all that is needed is this lab printout and the printout of the waveform forstudents to write on as they decode.
The last task of the lab involves the use of a Protocol Analyzer,which is Fluke Protocol Inspector or the equivalent.Note: This lab is over 20 pages long and includes excellent supplemental sections on thefollowing:1-1•Numbering systems, which include binary, decimal, and hex•The OSI 7-Layer model with real-world examples•Signaling and Encoding methods of Ethernet Waveform and ManchesterCCNA 1: Networking Basics v 3.1 - Lab 7.1.2Copyright 2003, Cisco Systems, Inc.The lab can be downloaded from the local Academy server at the institution with Version 3.0 of thecurriculum or from the Cisco Academy Connection website.
The Ethernet waveform for decoding willalso need to be downloaded. Check with the instructor for help in obtaining the lab and waveform.2-2CCNA 1: Networking Basics v 3.1 - Lab 7.1.2Copyright 2003, Cisco Systems, Inc.Lab 7.1.9a Introduction to Fluke Network InspectorObjectiveThis lab is a tutorial demonstrating how to use the Fluke Networks Network Inspector (NI) to discoverand analyze network devices within a broadcast domain. This lab will demonstrate the key featuresof the tool that can be incorporated into various troubleshooting efforts in the remaining labs.Background / PreparationThe Network Inspector software can distinguish workstations, servers, network printers, switches,and managed hubs, if they have been assigned a network address.Options for conducting this lab.1) Use Network Inspector in a small controlled LAN that is configured by the instructor in aclosed lab environment as shown above.
The minimum equipment should include aworkstation, 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 NI on the school LAN, check with the instructorand the network administrator.The following is a list of points to consider:1. Network Inspector detects the devices within a network subnet or VLAN. It does not searchbeyond a router. It will not inventory the entire network of the school unless it is all on onesubnet.2. Network Inspector is not a Cisco product nor is it limited to detecting just Cisco devices.1 - 12CCNA 1: Networking Basics v 3.1 - Lab 7.1.9aCopyright 2003, Cisco Systems, Inc.3.
Network Inspector is a detection tool, but it is not a configuration tool. It cannot be used toreconfigure any devices.The output in this lab is representative only, and output will vary depending on the number ofdevices, device MAC addresses, device hostnames, and which LAN is joined.This lab introduces the Fluke Networks Network Inspector software, which may be useful in latertroubleshooting labs and in the field. While the Network Inspector software is a valuable part of theAcademy program, it is also representative of features available on other products in the market.At least one host must have the Network Inspector software installed.
If the lab is done in pairs,having the software installed on both machines means that each person can run the lab steps. Besure to select both the Network Inspector and the Network Inspector Agent during installation.The Console can be anywhere that has a valid IP path and security to allow the connection to anAgent. In fact, it might be an interesting exercise to have the Console reach across the serial link toload the database from the other Agent.
The student can have the Console reading from a differentdatabase than the one that is currently in use by the Agent on the same PC.Step 1 Configure the lab or attach the 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 already be preloaded.If not, obtain them from the instructor. These files should support the IP addressingscheme as shown in the figure above and the table below.Configure the workstation according to the specifications in the table below.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.1Since the software discovers devices on the network, the more devices the better the demonstration.If available, add additional hosts to both LANs.Option 2.
If option 2, connect to school LAN, is selected, simply connect the workstation, withNetwork Inspector or Protocol Expert installed, directly to a classroom switch or to a datajack connected to the school LAN.Step 2 Start Network Inspector and the AgentFrom the Start menu, launch the NetworkInspector Console.Click on the Agent button at the left end ofthe toolbar so that the Agent can be started.If necessary, select the Agent tab in the window, then click on the Start button and watch the Statusbox until it shows that the Agent is running as in the figure below. This process may take severalminutes to start.2 - 12CCNA 1: Networking Basics v 3.1 - Lab 7.1.9aCopyright 2003, Cisco Systems, Inc.Notice the Agent status on the bottom of the Console window.
Look closely and notice that the Agenthas been running since 9:57 PM in the second graphic captured below that is in Step 3.Use the Close button in the lower-right corner of the Agent window to send the Agent away. In someversions, this may be a Hide button. Do not use the Stop button or the discovery process will cease.Step 3 Allow network discovery to occurThe Network Inspector software is designed to quietly, both passively and actively, collect networkdata. As such it takes time for devices to appear. This small network should be discovered in aminute or two.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
