![BinTec NetRACER Getting Started Download Page 34](http://html1.mh-extra.com/html/bintec/netracer/netracer_getting-started_2752955034.webp)
N
ET
RACER
28
For information on configuration management and
the transfer of configuration files to/from remote hosts
via TFTP refer to the NetRACER
User’s Guide.
Testing your Configuration
LAN Test
To test your new configuration try issuing a simple ping
command to a PC on the NetRACER’s LAN to verify the
LAN interface is properly configured. In our example, we
would issue:
ping -c 5 199.1.1.1
If the LAN portion of the configuration was successful
you should receive output similar to the following:
PING 199.1.1.1: 64 date bytes
64 bytes from 199.1.1.1: icmp_seq=0. time=8. ms
64 bytes from 199.1.1.1: icmp_seq=1. time=1. ms
64 bytes from 199.1.1.1: icmp_seq=2. time=1. ms
64 bytes from 199.1.1.1: icmp_seq=3. time=1. ms
64 bytes from 199.1.1.1: icmp_seq=4. time=1. ms
----199.1.1.1 PING Statistics----
5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms) min/avg/max = 1/2/8
ISDN Test
To verify the ISDN portion of the configuration is correct,
try the same command using the IP address of the remote
router (200.1.1.1 in our example) or a host on the remote
LAN.
If the ping command to the remote router is successful,
try issuing another ping command using the IP address
of a computer on the remote partner’s LAN.
Once all ping commands are successful, your config-
uration is complete.
Troubleshooting
If any of the ping commands are unsuccessful, first make
sure that the LAN switch is in the correct position (see