Beruflich Dokumente
Kultur Dokumente
TRANSMISIÓN DE DATOS
Laboratorio Nº 3
1 Requisitos previos
• Haber revisado material de modelos OSI, presentaciones de clase y lectura de separata de
cableado estructurado.
• PCs o portátiles con tarjeta de red (de preferencia Ethernet e inalámbrica)
• Cables estructurados Cat-5E y/o Cat 6.
• Herramientas de corte, tijeras, crimper tool y otros de acuerdo a los requerido en la
separata
2 Topología
PC Internet
Win
IP1 Router
Red LAN
PC
Linux
IP2
PC's de Laboratorio
En este laboratorio Ud revisará los estándares de cableado T568A y T568B para RJ- 45.,
así como sus las terminaciones para un cable Categoría 5e .
Notice that only pins 1, 2, 3, and 6 are used. Just connect 1 to 1, 2 to 2, 3 to 3, and 6 to 6.
Realizar:
• Investigue el uso e importancia de cada uno de los cables indicados anteriormente.
• Realizar una comparación entre las diversas normas de cableado estructurado indicados
en la lectura de Panduit
4 Verificación de conectividad
Realice los procedimientos indicados en 4.1.1 para verificar la correcta conectividad de sus
computador bajo estos dos escenarios:
D:\>ipconfig
Configuración IP de Windows
Adaptador Ethernet Conexión de área local 1 :
Sufijo de conexión específica DNS :
Dirección IP. . . . . . . . . . . : 10.0.0.5
Máscara de subred . . . . . . . . : 255.255.255.0
Puerta de enlace predeterminada : …...
4.2.1 Verificación
D:\>ping 10.0.0.10
Pinging 10.0.0.2 with 32 bytes of data:
Reply from 10.0.0.2: bytes=32 time<10ms TTL=128
Reply from 10.0.0.2: bytes=32 time<10ms TTL=128
En esta parte del laboratorio Ud usará algunas herramientas y comandos (ping y trace
route) para realizar troubleshooting (layer 3 commands). Inicie abriendo una ventana DOS
(windows) ó consola (linux) y visualice las opciones disponibles para ping.
Windows
Linux
lab@pe-n190:~$ ping
Usage: ping [-LRUbdfnqrvVaA] [-c count] [-i interval] [-w deadline]
[-p pattern] [-s packetsize] [-t ttl] [-I interface or address]
[-M mtu discovery hint] [-S sndbuf]
[ -T timestamp option ] [ -Q tos ] [hop1 ...] destination
lab@pe-n190:~$
1. The first step in troubleshooting is testing layer 1 and working our way up the OSI model.
Check the cabling. Be certain the LED on the NIC’s is lit up. You can also do a visual
verification on the cable to be certain you are using the correct one. Just because the light
is lit does not mean the cable is working or is the proper cable. Be careful!
2. First we can test the functionality of the NIC (layers 1-2) and the computer for its ability to
communicate with networking. We can do this by using ping to any address on the
127.0.0.1-127.255.255.254 network. This is called the “loopback adapter network.” So I
pick an IP address from the 127 network and ping it. You should see something like this if
everything is fine:
3. Next we can test our basic network connection between the two computers using ping
(layer 3). If my workstation used 192.168.1.1 and the other one used 192.168.1.2 then I
would ping 192.168.1.2 to test connectivity. If you cannot ping the other workstation then
check the IP addresses and masks on each workstation. When all else fails reboot the
workstations too.
4. Let’s see what some options are for ping and what they do. First adding the –t option will
cause multiple pings UNTIL YOU STOP IT by using the break sequence in DOS
(control+C)...this is technically illegal because it creates a very, very small denial of service
attack:
Why do this? Let’s just say we start it up on one machine and it is telling us that it is not
replying...by using the constant ping we can “see” the instant the other computer or
interface comes on-line.
5. Ok...lets try another one. Adding the –n will let us specify how many packets to send.
Sometimes waiting for four packets can be problematic, so we just want to send one.
6. adding the –l will let us change the size of our packet from 32 bytes to whatever we want it
to...sometimes during labs you may want to see how much it would take to “choke” out the
performance of an interface or to test some traffic balancing and this would work for it.
7. When you have more than two computers in a network you can also use another layer 3
tool: trace route. Let’s start by looking at our options with tracert in DOS:
If you are having difficulty connecting to another device several hops away trace route will
show you exactly which device “looses” your communication. For example, if I had a
network with several routers and was trying to get to www.spjc.edu I could find the faulty
device. First, since it helps to have a baseline before something goes bad let’s look at a
good trace route to our destination: