HP Jetdirect 310x HP Jetdirect 310x Print Server - (English) User Guide - Page 133

Light Behavior, Description, Light, Behavior, much power.

Get HP Jetdirect 310x - Print Server For Fast Ethernet PDF manuals and user guides View all HP Jetdirect 310x manuals
Add to My Manuals
Save this manual to your list of manuals

Page 133 highlights

Light Behavior Description Off No network connection. On solid green Network connection is established at 10 Mb/s or at 100Mb/s. USB Light Light Description Behavior Off USB is not operational. This is OK before the print server finishes starting up. After startup completes, this could indicate a faulty print server. On solid USB is enabled and ready for use. This begins before green the USB cable is connected. Blinking (green) Software fault occurred for the firmware. There is a valid USB device and connections, but the device is not supported. Make sure the attached device is a printer. Blinking (amber) Might be a hardware fault (for example, a short-circuit, faulty cable, or a printer drawing too much power). To verify, disconnect the USB cable at the print server. Switch on the printer if it is off. Power cycle the print server (unplug it and plug it back in). Then reconnect the USB cable. If the USB light is now green and steady, then no problem remains. Otherwise, if the USB light is still blinking amber, then there may be a faulty component. Try these steps to determine which component might be causing the problem:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
Light Behavior
Description
Off
No network connection.
On solid green
Network connection is established at 10 Mb/s
or at 100Mb/s.
USB Light
Light
Behavior
Description
Off
USB is not operational. This is OK before the print
server finishes starting up. After startup completes,
this could indicate a faulty print server.
On solid
green
USB is enabled and ready for use. This begins before
the USB cable is connected.
Blinking
(green)
Software fault occurred for the firmware. There is a
valid USB device and connections, but the device is
not supported. Make sure the attached device is a
printer.
Blinking
(amber)
Might be a hardware fault (for example, a
short-circuit, faulty cable, or a printer drawing too
much power).
To verify, disconnect the USB cable at the print
server. Switch on the printer if it is off. Power cycle
the print server (unplug it and plug it back in). Then
reconnect the USB cable. If the USB light is now
green and steady, then no problem remains.
Otherwise, if the USB light is still blinking amber,
then there may be a faulty component. Try these steps
to determine which component might be causing the
problem: