SMS2000 Troubleshooting
TUT Systems, Inc Page 94 of 104 P/N 220-06288-20
Chapter 17 - SMS2000 Troubleshooting SMS2000 Troubleshooting Procedures
Table 17-3 provides valuable information for troubleshooting the SMS2000.
Table 17-3 SMS2000 Troubleshooting Procedures
Problem Area Commands What to Look for
ping router address
Look for any packets
returned.
show status ifconfig Check for non-zero
packets being sent or
received on eth0
(network port).
Verify that physical connectivity is
good
Look for green lights
on intermediate switch.
Swap Ethernet cables
with known good
cable.
ping external address Verify that the routing
table in the router is
good
Network Connection:
If communication problems
exist between SMS2000 and
the outside world (through
the on-site router), verify the
cabling is correct between the
SMS2000 and the router.
Afterwards, diagnose the
physical layer, IP
configuration, and routing
tables.
traceroute external address Determine location of
the bad route
When a subscriber PC
is directly connected
via x-over Ethernet
cable to the subscriber
interface of the
SMS2000, the front
panel LEDs will light
on the Subscriber side
of the LED panel.
Show status ifconfig Check for non-zero
packets being sent or
received on eth1
(subscriber port).
Subscriber Connection:
If subscribers cannot get IP
addresses or Web pages, first
verify a physical connection
exists.
Can any other subscriber get
access?
Is the SMS2000 receiving
packets on the subscriber
port?
Verify that the physical
cabling is correct. Bypass the
wiring system by attaching a
PC directly to the SMS2000
subscriber port (use x-cable)
and seeing if it works
From the PC, type arp a . See if there are any
entries in the ARP
cache for the PC. There
should be “35.x.x.x” if
physical connectivity is
good.