C H A P T E R 3 | Fast Ethernet Modules |
| ||
|
|
| Possible |
|
|
| Symptom | Cause | Course of Action |
|
|
|
|
|
|
| No connectivity | No link. Link on | See “No Link LED” |
|
| with a station on a | 10/100 module is | symptom above. |
|
| switch port. | off. |
|
|
| Test for connectivity with | ||
|
|
|
| |
|
|
|
| the ping command. |
|
|
|
|
|
|
|
| Cable has just | Use the clear fdb |
|
|
| been moved from | command or wait until the |
|
|
| one port to | aging time has expired if |
|
|
| another. | the destination is not |
|
|
|
| generating traffic. The set |
|
|
|
| agingtime command |
|
|
|
| establishes the aging time. |
|
|
|
|
|
|
|
| Spanning Tree | Wait 60 seconds for state |
|
|
| has just been | to change to “forwarding.” |
|
|
| enabled. |
|
|
|
|
|
|
|
| Poor performance | A considerable | Use the show counters |
|
| on a link. | amount of Data | command to display them. |
|
|
| Link errors such | Or, use any |
|
|
| as CRC errors. | network management tool |
|
|
|
| to generate reports based |
|
|
| Too many | on these counters. |
|
|
| collisions. |
|
|
|
|
| Too many stations on the |
|
|
|
| segment. Try moving |
|
|
|
| some to their own |
|
|
|
| segment. |
|
|
|
|
|
|
|
| Late Collisions. | Cables are too long. Use a |
|
|
|
| shorter cable, or add a |
|
|
|
| repeater or bridge. |
|
|
|
|
|
There are too many “hops.” Use fewer devices from end to end.
19
