Chapter 10: Troubleshooting
5. 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.
6. 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.
7. 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.
8. Perform the prior examinations but in the reverse direction – from the remote machine back to the local
machine.
9. Enlist the aid of a sniffer program to view at the source and destination machines exactly what data
packets are being sent and received. Free public-domain programs such as Wireshark are readily
available.
Chapter 11: Third Party Copyright Notices
E3Switch is grateful for and contributes to open source software development which may be protected by
the following copyright notices and license terms:
eCos License
E3Switch gratefully acknowledges the contributions of the eCos developers and community. Current eCos source files are available at
http://ecos.sourceware.org/
E3Switch
implementation-specific modifications to those files are available by contacting E3Switch LLC.
The FreeBSD Copyright
Copyright 1994-2006 The FreeBSD Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE FREEBSD PROJECT ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD
PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or
implied, of the FreeBSD Project.
25
