Enterasys csx150 Guida Utente
![Enterasys](https://files.manualsbrain.com/attachments/0d61cd0d9a60e36f1a6c1364af6a0a9788bcf75b/common/fit/150/50/0c43aa9c6913c8f0c68912f62e6506afc95280a8d9a1fc71e52e7f54646e/brand_logo.jpeg)
Small Office Remote Access Switch 401
LED I
NDICATORS
Service Indicator
S
ERVICE
I
NDICATOR
R
EMAINS
L
IT
If the Service indicator remains lit during the power-on sequence, this means the system software
is unable to boot. The system may be having some type of operational problem. While the Service
indicator remains lit, the other LEDs will blink a certain number of times, pause, then blink that
number of times again (See following table). This pattern will be repeated five times. The actions to
take if this occurs are:
is unable to boot. The system may be having some type of operational problem. While the Service
indicator remains lit, the other LEDs will blink a certain number of times, pause, then blink that
number of times again (See following table). This pattern will be repeated five times. The actions to
take if this occurs are:
1.
Make note of the number of consecutive blinks.
2.
Restart the system.
3.
If the Service LED is still lit, and the other LEDs are still flashing, contact your distributor and
provide them with the count of consecutive blinks.
provide them with the count of consecutive blinks.
The table below provides an error description corresponding to the number of consecutive LED
blinks:
blinks:
* FSB: First Stage Boot; SSB: Second Stage Boot.
S
ERVICE
I
NDICATOR
B
LINKS
If the Service indicator blinks at any time during system operation, access your administrative
console (using the status command) for further information. One or more of the following messages
should be displayed:
•
console (using the status command) for further information. One or more of the following messages
should be displayed:
•
OUT SVC 1
•
OUT SVC 2
•
OUT SVC 3
•
OUT SVC 4
•
OUT SVC 5
•
LAN XMIT ERROR
Number of Blinks
Error Description
1
Failure during erasure of main block during SSB* recovery
2
Failure during programming of main block during SSB
recovery
recovery
3
Timed out during recovery of SSB
4
Individual record error during recovery of SSB
5
Communications error during recovery of SSB
6
Incompatibility between FSB* and new SSB versions
7
Currently not used
8
Bad address information contained in SSB received during
recovery
recovery
9
SSB, received during Recovery, contained a bad checksum
for entire image
for entire image