Troubleshooting guide
Local Area Network
173
LAN Troubleshooting Tips
For IP Phone and physical network connectivity problems:
Verify that the device has power.
Verify the status of the port link integrity LEDs at each end of the cable.
Verify that each device transmits a link integrity pulse (LINK LED on).
If the link is down, try with another port. Verify that proper cabling is installed between
the end devices.
Verify that a crossover cable was not installed instead of a straight-though cable, and
vice-versa.
For network media problems:
If there is excessive noise, check for cabling problems.
If there are excessive collisions, check for duplex mismatch problems.
For Cyclic Redundancy Check (CRC) errors, check if there is a faulty NIC or flow-control.
If there are excessive runt frames, check for bad cables, duplex mismatches or a bad
PC NIC.
For network connectivity problems, identify the path between two end devices by doing
the following PING test (in order):
Local
Local gateway
Remote gateway
Remote IP.
There are several L2 maintenance commands that are useful for collecting details: L2 poestatus;
L2 stat maclist; L2 stat port (port summary); L2 stat port <portnum> (specific port info); L2 stat
spanning-tree; L2 stat switch. For more information, see “Using Layer 2 Statistics” on page 175.
Maintenance and troubleshooting of your LAN/WAN network is the responsibility of your
network provider. Mitel Technical Support can help you isolate minor network problems;
Technical Support will escalate complex network problem to Professional Services, a
billable service.
Before contacting Mitel Technical Support with a LAN issue, ensure that you have
the following information ready:
network diagram
“routeShow” command results
results of PING test between controller and IP Phone
“rness verify” command results
“state xnet all” command results










