HP ProLiant DL380p HP ProLiant Servers Troubleshooting Guide - Page 60

Network controller problems

Page 60 highlights

3. Be sure no line interference exists. Retry the connection by dialing the number several times. If conditions remain poor, contact the telephone company to have the line tested. 4. Be sure the modem is current and compliant with CCITT and Bell standards. Replace with a supported modem if needed. You are unable to connect to an online subscription service Action: 1. If the line you are accessing requires error control to be turned off, do so using the AT command AT&Q6%C0. 2. If the ISP you are accessing requires access at a decreased baud rate, reconfigure the communications software to correct the connection baud rate to match the ISP. 3. If this does not work, force a slower baud rate (14400 baud) with the AT command AT&Q6N0S37=11. You are unable to connect at 56 Kbps Action: 1. Find out the maximum baud rate at which the ISP connects, and change the settings to reflect this. Reattempt to connect at a lower baud rate. 2. Be sure no line interference exists. Retry the connection by dialing the number several times. If conditions remain poor, contact the telephone company to have the line tested. Network controller problems Network controller is installed but not working Action: 1. Check the network controller LEDs to see if any statuses indicate the source of the problem. For LED information, refer to the network controller documentation. 2. Be sure no loose connections (on page 20) exist. 3. Be sure the network cable is working by replacing it with a known functional cable. 4. Be sure a software problem has not caused the failure. Refer to the operating system documentation for guidelines on adding or replacing PCI Hot Plug devices, if applicable. 5. Be sure the server and operating system support the controller. Refer to the server and operating system documentation. 6. Be sure the controller is enabled in RBSU. 7. Check the PCI Hot Plug power LED to be sure the PCI slot is receiving power, if applicable. 8. Be sure the server ROM is up to date. 9. Be sure the controller drivers are up to date. 10. Be sure a valid IP address is assigned to the controller and that the configuration settings are correct. 11. Run Insight Diagnostics ("HP Insight Diagnostics" on page 77) and replace failed components as indicated. Hardware problems 60

  • 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
  • 203
  • 204

Hardware problems 60
3.
Be sure no line interference exists. Retry the connection by dialing the number several times. If
conditions remain poor, contact the telephone company to have the line tested.
4.
Be sure the modem is current and compliant with CCITT and Bell standards. Replace with a supported
modem if needed.
You are unable to connect to an online subscription service
Action
:
1.
If the line you are accessing requires error control to be turned off, do so using the AT command
AT&Q6%C0
.
2.
If the ISP you are accessing requires access at a decreased baud rate, reconfigure the communications
software to correct the connection baud rate to match the ISP.
3.
If this does not work, force a slower baud rate (14400 baud) with the AT command
AT&Q6N0S37=11
.
You are unable to connect at 56 Kbps
Action
:
1.
Find out the maximum baud rate at which the ISP connects, and change the settings to reflect this.
Reattempt to connect at a lower baud rate.
2.
Be sure no line interference exists. Retry the connection by dialing the number several times. If
conditions remain poor, contact the telephone company to have the line tested.
Network controller problems
Network controller is installed but not working
Action
:
1.
Check the network controller LEDs to see if any statuses indicate the source of the problem. For LED
information, refer to the network controller documentation.
2.
Be sure no loose connections (on page
20
) exist.
3.
Be sure the network cable is working by replacing it with a known functional cable.
4.
Be sure a software problem has not caused the failure. Refer to the operating system documentation for
guidelines on adding or replacing PCI Hot Plug devices, if applicable.
5.
Be sure the server and operating system support the controller. Refer to the server and operating system
documentation.
6.
Be sure the controller is enabled in RBSU.
7.
Check the PCI Hot Plug power LED to be sure the PCI slot is receiving power, if applicable.
8.
Be sure the server ROM is up to date.
9.
Be sure the controller drivers are up to date.
10.
Be sure a valid IP address is assigned to the controller and that the configuration settings are correct.
11.
Run Insight Diagnostics ("
HP Insight Diagnostics
" on page
77
) and replace failed components as
indicated.