Lab - 09 - Ethernet Switch Troubleshooting

http://www.4shared.com/rar/DTnVAaXA/Lab-09-Ethernet_Switch_Trouble.html 1) Configure the topology 2) Verifying the Network Topology 3) Examining Layer 1 & 2 Problems on Interfaces

1. Configure the topology

Design and configure the topology as shown below.

i.

Configure SW1.

Ping SW1.

www.asghars.blogspot.com

ii.

Configure SW2.

Ping SW2.

iii.

Configure SW3.

Ping SW3.

www.asghars.blogspot.com

2. Verify the Network Topology

Cisco switches & routers send CDP messages out of each of their interfaces. CDP can be used to confirm or fix the documentation shown in a network diagram & discover the devices and interfaces used in a network. The interfaces that need to use CDP are interfaces connected to routers, switches and IP Phones. To check global Cisco Discovery Protocol information.

Displays information about the interfaces on which Cisco Discovery Protocol is enabled.

Using CDP you can learn about the neighboring devices. From which you can draw a basic diagram.

www.asghars.blogspot.com

Check detailed information about a neighbor(s).

3. Examining Layer 1 and Layer 2 Problems on Interfaces

www.asghars.blogspot.com

i.

An interface status codes are used to determine whether the interface is working or not. The following commands shows the two status codes i.e the status of L1 (Interface Status) and L2 (Line Protocol Status).

In this case the both the L1 and L2 are working. The single status code be found as:

ii.

Switch keeps various interface counters. These interface counters can help to identify problems that can occur even though the interface is in a connect state. These counters include CRC/FCS, Collision Counter, Late Collision Counter (Collision occurred when switch sent out 64 bytes of a frame). These counters are used by three LAN problems. Excessive Interface on the Cable: It causes the problem of interference on the cable. It can be identified with CRC counter. Duplex Mismatch: Identified by Collision or Late Collision Counter. Jabber: Jabber refers to cases in which NIC ignores Ethernet rules & sends frame after frame without break. Identified by Collision or Late Collision Counter.

www.asghars.blogspot.com

www.asghars.blogspot.com