FEC Onlineservices
Checklist router hardware
Advices for the systematic verification of the router hardware

1. Preliminary note
Before replacing the router because of a possible hardware defect you should exclude potential errors in the routers periphery with the aid of this check list.

2. Delete configuration
To exclude a faulty configuration of the router you should save your configuration file on your PC and choose "Delete Configuration" in the Bootmonitor Menu to check the functions with a basic configuration.

3. Power-LED (PWR)
Symptom: PWR (green) not on permanently.

After the power on the PWR led should be constantly on.

In case of an error:
  • verify the power supply.
  • verify cabling.
  • verify the provided power supply is in use.
  • verify the provided power supply is working properly or try to test another power supply of the same type.

4. Error-LED (ERR)
Symptom: ERR (red) is on constantly.

Normaly the ERR led must not be constantly on, but a short term flash up is possible because of e. g. LAN collisions

In case of an error:
  • verify the cabling.
  • verify the cabling for ISDN and Ethernet is not inverted.

5. Serial interface (RS-232)
Symptom: The serial connection between PC and Router can not be established.

In case of an error:
  • Verify the correct settings of your terminal programm:
    Bitrate 9600 Bit/s, 8 Databits, no Parity, 1 Stopbit, no Handshake.
  • Verify the used COM port is activated at your PC.
  • Verify the serial cabel is connected properly.
  • Verify an intended cabel ('null modem-cabel') is used.
  • Verify the cable is not faulty.

6. LAN-interface
Symptom: LAN connection is not working.

Test the LAN-interfcae with a ping-command on the shell:

x1200II:> ping -c5 <IP Adresse Ihres PCs>
PING x.x.x.x: 64 data bytes
64 bytes from x.x.x.x: icmp_seq=0. time=1. ms
64 bytes from x.x.x.x.67: icmp_seq=1. time=1. ms
64 bytes from x.x.x.x.67: icmp_seq=2. time=1. ms
---- x.x.x.x PING Statistics----
5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 1/1/1
In case of a fault:

  • Check cabling:
    • Verify LAN cable is connected properly.
    • Verify an intended LAN cable is used.
    • Verify the cable is not faulty.
    • If necessary verify the switch/hub.
    • When the LAN-connection is established between the router and a PC directly (without hub/switch) it might be possible that a cross-cable or an adapter is required .

  • Check configuration
    • Verify IP-address and netmask of the LAN-interface.
    • Verify the mode of the LAN-interface in the Setup-Tool -> LAN:
      The default setting is Mode 'Auto'. If applicable adjust the mode manually according to the mode of your switch/hub.
    • Verify the state of the LAN-interface is 'up'. Use the command 'ifstat' (e.g. for en1):

x1200II:> ifstat
Index  Descr        Type Mtu  Speed St Ipkts   Ies Opkts   Oes PhyAddr/ChgTime
000000 REFUSE       othr 8192     0 up 0       0   0       0     0 00:00:00
000001 LOCAL        othr 8192     0 up 0       0   0       0     0 00:00:00
000002 IGNORE       othr 8192     0 up 0       0   0       0     0 00:00:00
001000 en1-0        eth  1500  100M up 6784    0   302     0   00:a0:f9:06:20:90
001001 en1-0-llc    eth  1496  100M up 0       0   0       0   00:a0:f9:06:20:90


7. '@'-interface (xDSL-interface)
For the @-interface (xDSL-interface, e.g. en3) please act according to the above description of the LAN-interface.


8. ISDN-interface
Symptom: The ISDN-connection doesn´t work.

To test the outgoing direction of the ISDN-interface please call a phone with your router using the "isdnlogin" command.

x1200_II:> isdnlogin <number of your phone>  telephony
The Telephone should ring now (disconnect command: Ctrl.-C).
Afterwards check the Setup-Tool -> Monitoring and Debugging -> ISDN Monitor -> (h)istory, if an outgoing call was logged with the correct dialed number.

To test the ISDN-interface for incoming calls call the router with a Telephone and verify in parallel in the Setup-Tool -> Monitoring and Debugging -> ISDN Monitor -> (c)alls, if an incoming is logged at least for a short time.

In case of an error:
  • Check cabling

    • Verify the ISDN cable is connected correctly. 
    • Verify an intended ISDN cable is used.
    • Verify the cable is not faulty.
    • Verify the correct function of the 'NTBA' or the 'NTPM'.

  • Check configuration

    • If necessary verify all BRI and PRI licences are entered correctly.
    • Verify the PBX is configured correctly.
    • Verify that the router is adjusted correctly to the requirements of the PBX (e.g. dialing-prefix, ISDN-type).
    • Verify that the correct D-channel-protocol is set. Check in the Setup-Tool -> WAN, if 'Result of autoconfiguration' is conforming to your ISDN-terminal point (e.g. 'Euro ISDN point to multipoint' for S0). Otherwise choose the suitable value at 'ISDN Switch Type'.  At ISDN-point-to-point connections the 'ISDN Switch Type' has to be set manually.
    • Verify that all three channels are set to "dialup" at ISDN Bri interfaces.

9. ADSL-/SHDSL-interfaces of the X2300/X2400 Family
Symptom: The xDSL-connection is not working.

After the syncronisation the ADSL- respectively the SHDSL-LED is active permanently (a new syncronisation may last up to 10 minutes).

In case of an error:
  • Check Cabling

    • Verify the xDSL-cable is connected correctly.
    • Verify the intended cable is used.
    • Verify the cable is not faulty.
    • Verify the Splitter is working fine.

  • Checking the router software

    • Verify the router has an actual boot image. To check the version please type 'swversion' or "show rev" at the router shell.
    • If necessary verify the ADSLi logic is up-to-date (current Version 4.10.09).  Type 'update -i'  on the shell and afterwards 'ls -l'.
    • Current software with release notes can be found in the download area at  www.funkwerk-ec.com.

  • Check of the DSL provider access

    • Request a check of the access through the provider.
    • Verify with help of your provider if  the xDSL-access has the required specification (e.g. 'U-R2' Norm at ADSL).
    • Verify with help of your provider that the 'DSLAM' in the local exchange has an actual software version.
    • The Provider should do a line reset on the DSLAM, particularly after changing the  ADSL-Modem it may be necessary to reset the DSLAM itself.

© 2013 bintec elmeg GmbH