The "Link" LED is an indicator of whether or not the Etherlite has a physical network connection. If the "Link" LED is lit, the unit believes it has a good connection to your network. If this LED is not lit, the best place to check is the cabling between your Etherlite unit and the network. Check to make sure both ends of the cable are securely plugged in. If the cable was plugged in on both ends and the "Link" LED is still not lit, check the Ethernet cable itself by swapping with another.

The "On" LED serves several purposes. If the "On" LED does not light at all, the power supply is likely dead. If the "On" LED is lit solid immediately, this might also be an indicator that the power supply is bad, or that the unit's internal code has been corrupted. Either of these conditions will require that the unit to be sent in for repair.

If the "On" LED has a fast, steady flicker, this indicates that the Etherlite is waiting to be served an IP address. If an IP address is stored on the unit, the "On" LED will flicker briefly and then come on solid. The same behavior will be observed if the Etherlite is getting served an IP address from a bootp or DHCP server, though it may take a bit longer to light solid than a unit which has a stored IP address.

Occasionally the "On" LED will not behave either of the ways described above, but will instead blink a repetitive code. This typically is an indicator that the unit's internal code is corrupted and will need to be sent in for repair. The only user-serviceable codes are 64, which should be resolved when a user upgrades the firmware and driver for the Etherlite; and code 67, which indicates that the Etherlite is being served an IP address that is already in use on the network.

For reference purposes, here is a list of all Etherlite blink codes:

11 - Self test failure (not generated form 'fatal' tho)
12 - Bad blink code passed to 'fatal' itself
13 - Fatal test RAS opcode
14 - Bad flow control mode in 'process_special'
15 - Impossible else clause in 'process_special'
16 - Dma on Null buf in 'dma_out'
17 - Dma length zero in 'dma_out'
21 - 'trap' routine called
22 - Memory sizing error in 'init_bufs'
23 - Not enough bufs in 'init_bufs'
24 - Out of buffers in 'get_buf'
25 - Impossible return point in 'xfer_to_scsi'
26 - Impossible return point in 'xfer_from_scsi'
27 - Buffer timer interrupt SLHdbt_idle handler called unexpectedly
30 - Rom or eprom failure
31 - Baud bank error in 'hwXXXX.c'
32 - Bad register in call to 'wr_scc_reg' in 'hwXXXX.c'
33 - Bad register in call to 'rd_scc_reg' in 'hwXXXX.c'
34 - Xmit incomplete in 'slh.c'
35 - Stuck SCC in slh.c
36 - Unexpected interrupt
37 - Abort got duplicated
41 - Sync free_buf had buffer type or already free
42 - SLMsm bad state transition
43 - Bad sync transmit status
44 - Frame too short
45 - Prep_buf: bad type
46 - Get_mesg: cnt short
47 - get_data: bp NULL or cnt short
51 - Switch default in do_sync
52 - Unit number out of range
53 - Unit not initd
54 - Bad cmd in do_scsi
55 - Bad cmd in proc_sync_buf
56 - Bad cmd in proc_bounced_buf
57 - SLMput_data: cnt too big
61 - SLMtrap
62 - SLMWrapUP: recv_frm NULL
63 - SLCtrap
64 - TXQ Overflow
65 - QUARTs failed init
67 - Duplicate IP Address
68 - Ethernet address not configured