Network Controller Problems - HP ProLight Server Troubleshooting Manual

Be sure no line interference exists. Retry the connection by dialing the number several times. If
3.
conditions remain poor, contact the telephone company to have the line tested.
Be sure the modem is current and compliant with CCITT and Bell standards. Replace with a
4.
supported modem if needed.
You are unable to connect to an online subscription service
Action:
If the line you are accessing requires error control to be turned off, do so using the AT command
1.
AT&Q6%C0.
If the ISP you are accessing requires access at a decreased baud rate, reconfigure the
2.
communications software to correct the connection baud rate to match the ISP.
If this does not work, force a slower baud rate (14400 baud) with the AT command
3.
AT&Q6N0S37=11.
You are unable to connect at 56 Kbps
Action:
Find out the maximum baud rate at which the ISP connects, and change the settings to reflect this.
1.
Reattempt to connect at a lower baud rate.
Be sure no line interference exists. Retry the connection by dialing the number several times. If
2.
conditions remain poor, contact the telephone company to have the line tested.

Network controller problems

Network controller is installed but not working
Action:
Check the network controller LEDs to see if any statuses indicate the source of the problem. For LED
1.
information, refer to the network controller documentation.
Be sure no loose connections (on page 15) exist.
2.
Be sure the network cable is working by replacing it with a known functional cable.
3.
Be sure a software problem has not caused the failure. Refer to the operating system documentation
4.
for guidelines on adding or replacing PCI Hot Plug devices, if applicable.
Be sure the server and operating system support the controller. Refer to the server and operating
5.
system documentation.
Be sure the controller is enabled in RBSU.
6.
Check the PCI Hot Plug power LED to be sure the PCI slot is receiving power, if applicable.
7.
Be sure the server ROM is up to date.
8.
Be sure the controller drivers are up to date.
9.
Be sure a valid IP address is assigned to the controller and that the configuration settings are correct.
10.
Run Insight Diagnostics
11.
indicated.
Network controller has stopped working
Action:
Check the network controller LEDs to see if any statuses indicate the source of the problem. For LED
1.
information, refer to the network controller documentation.
("HP Insight Diagnostics" on page 61) and replace failed components as
Hardware problems 47