E3Switch DS3 Operating information manual - page 23
Chapter 10: Troubleshooting
Event age, most recent first...
days h:m:s event
Age 0d 0:00:02> DS3/E3 Ports OK
Age 0d 0:00:03> PPP is UP - session ID 0xa1b5
Age 0d 0:00:03> Sending PADS session confirmation
Age 0d 0:00:03> PPP PADR msg received from 00:13:46:88:09:3e
Age 0d 0:00:03> Sending PADO offer on 8P8C LAN Port2
Age 0d 0:00:03> PPP PADI msg received from 00:13:46:88:09:3e
Age 0d 0:00:03> SFP LAN Port1: UP
Age 0d 0:00:04> 8P8C LAN Port2: UP
6. Ensure a proper LAN cable is being used. Straight-through or crossover cabling is acceptable. The
LAN light of the converter port to which any LAN is attached should be illuminated and green. If not,
ensure that the attached equipment is set for autonegotiation and can accept 100BaseTX Full-Duplex
links. Refer to front panel section of this document for other LAN light colors.
7. The network equipment attached to the LAN port of the converter should be set for autonegotiation
mode in order to allow the converter to negotiate a 100Mbit full-duplex connection. Forcing either the
converter's or attached equipment's LAN port to 100Mbit full-duplex may not allow the proper
autonegotiation and LAN connection to occur. There are rare cases with older LAN equipment in
which it may be necessary to disable autonegotiation. If crc-errors or short packet errors are seen
in the management statistics of the LAN port, the attached LAN equipment has probably
configured itself to half-duplex mode and colliding packets are being lost. In such a case,
autonegotiation should be disabled on both the converter and the attached LAN equipment with both
forced to 100BaseTX full-duplex. Autonegotiation interoperability and standards were not well
understood by the industry at the inception of 100BaseTX, resulting in some older LAN equipment not
understanding the converter's autonegotiation advertisement of strictly full-duplex capability.
8. If ping is available, ping from the local machine to a machine on the same local LAN. Then ping to the
machine or router, on the same local LAN, that is directly connected to the converter. Then ping to the
machine or router, on the remote LAN, that is directly connected to the remote converter. Then ping to
another machine on the remote LAN. During pinging, attempt to generate high traffic loading on the
network.
9. Try different types of communication with the remote machine. Some examples might be a ping, a file
transfer, a telnet connection if appropriate, a HTTP page viewing if appropriate, a “find” remote
computer if appropriate. If some work and some do not but those that do, work consistently, there is
possibly a network configuration issue.
10. Monitor lights during packet transmission:
·
With LANs attached, verify, perhaps using pings, that data packets generated by a local machine
cause the converter's light of the connected LAN port to blink. If not, determine if there is an
intermediate router or piece of equipment that is not properly forwarding the data packets to the
converter. Examine the Link/Activity light on the source machine and any intermediate machines
to ensure they behave properly (usually flicker) as well.
·
If the local LAN light blinks with each packet, next verify that the packet traverses the link by
monitoring the DS3 Port light at the remote converter. If the remote DS3 Port light does not blink,
there is either a link malfunction or an interface configuration problem or failure between the
converter and the link. Perhaps change 75-ohm cables. Ensure the link is delivering
unchannelized AMI HDB3 or B3ZS data to the converter. Ensure this configuration is proper at
both ends of the link.
·
If the remote DS3 Port light blinks, attempt to locate the Link/Activity light on the destination
machine. Ensure that it flickers. If not, the problem may be with an intermediate router or hub or
converter intercepting the packet.
11. Perform the prior examinations but in the reverse direction – from the remote machine back to the local
machine.
23