![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
NetportExpress(TM) XL/EL Print Servers: LED Diagnostics Error Codes
Contents:
UNDERSTAND/TROUBLESHOOT THE ACTIVITY LIGHTS
NetportExpress(TM) XL & EL print server uses a 3 color Activity LED:
Red, Amber & Green.
COLOR MEANING
Off NO Power
Red Steady Malfunctioned CPU (RMA)
Red Flashing The XL/EL's self-test failed or COS error
Amber Flashing Self Test in progress
Amber steady Unable to boot the application file stored on
the RBL file server
Green steady Ready to print, RBL boot successful
Green flicker NetportExpress print server is printing
There are 3 conditions involving the Red color that are important to
understand. These are:
1. Red Steady
A red steady Activity LED when power is first engaged to the
NetportExpress server indicates a malfunctioned CPU and that the
unit has failed. A RMA (Return Merchandise Authorization) will be
required. Please contact your vendor or Intel customer support.
2. Red Flashing during POST
Upon power-up, the NetportExpress server goes through a Power-On
Self Test or POST. The unit will flash amber during this POST. If
an error is discovered during the POST, the Activity LED will flash
red in the following pattern:
# of
Flashes Meaning
1 80186 microprocessor failure
2 Flash memory checksum error
3 RAM failure
4 Microprocessor timer failure
5 Serial port failure (not used for EL)
6 Parallel port failure
7 Network interface failure
8 Network interface RAM failure
If the unit has an Activity LED flashing red in the pattern of 5, 6
or 7 flashes, the unit will require some troubleshooting.
* If your NetportExpress server fails with a 5 or 6 blink pattern,
remove all devices from the printer ports and try powering up
again.
* If your NetportExpress server fails with with a 7 blink pattern
you may have a bad connection to your network. Move the unit to
a different network connection that is known to be good. Make
sure the cabling is within specifications. A 10baseT
NetportExpress server must be within 100 meters of the Hub. For
thin wire BNC, make sure the segment does not exceed 200 meters.
Any other red flashing pattern (1,2,3,4,8) indicates a failed unit.
You should contact your vendor or Intel Customer support for a
RMA.
3. Red Flashing after POST
A red flashing pattern during normal operation indicates a fatal
COS (Client Operating System) error has been detected. The
flashing pattern is different from the "during post" flash in that
the flashing is in a 3 digit pattern: If the error is #364, the
unit will flash 3 flashes, short pause, 6 flashes, short pause, and
4 flashes, long pause and then repeat this pattern. (If it blinks
10 times, this is equal to a 0) If this rare event happens, the
unit will no longer communicate on the network. Resetting the
NetportExpress print server will usually solve the problem.
Note: The unit will never print until the LED is green indicating a
successful RBL boot.
NETPORTEXPRESS(TM) XL SERVER FAILS AFTER POST WITH RED FLASHING COS ERROR 1 30
Symptom
Upon power up, the NetportExpress(TM) XL print server fails after POST
with a red flashing COS error 1 3 0.
COS Error 1 3 0 Message:
ether_nic_error_base
Note: The error message is independent of Token Ring or Ethernet
even though it shows "ether."
Description
POST fails to detect the Loopback error (7 Flashes). Even though the XL
server isn't connecting to the ring, it still passes POST and the NIC
driver detects that the XL server isn't connected to the ring.
Solution
Try a different network drop or network cable. Verify the data rate
switch is set correctly. Try attaching the XL server as direct to the
MAU as possible.
This problem has been resolved in v2.20 or higher of the application
code and is available on the Intel online services in the archives
NPXL1.EXE and NPXL2.EXE.
FLASH UPDATE FAILS WITH A COS 702 ERROR. RESETTING THE XL/EL BRINGS UNIT BACK UP BUT FLASH UPDATE DIDN'T TAKE
Symptom
Flash update fails with a COS 702 error. Resetting the XL/EL brings the
unit back up but the Flash updated didn't take.
Description
If a Flash update is performed using Netport(R) Manager version below
2.0 or NPAdmin on a unit to update from Flash version below v2.50 to
v2.50 or above, using the down revved Netport Manager (or NPAdmin) will
work, but the next time it is Flash updated the update will fail with
the COS 702 error. The cause has to do with creating message blocks for
NetBIOS. This is likely to affect those customers that updated to
F02.50a (NPXFIX.EXE) or used NPAdmin.
Solution
The solution is to update the unit via the serial port.
Trademark information