HP Carrier-grade cc2300 User Information and Service Guide - HP Carrier-Grade - Page 78

Controller Stopped Working When an Add-in Adapter Was Installed, Add-in Adapter Stopped Working

Get HP Carrier-grade cc2300 PDF manuals and user guides View all HP Carrier-grade cc2300 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 78 highlights

Controller Stopped Working When an Add-in Adapter Was Installed 1. Make sure the cable is connected to the port from the onboard network controller. 2. Make sure your PCI BIOS is current. 3. Make sure the other adapter supports shared interrupts. Also, make sure your operating system supports shared interrupts. 4. Try re-seating the add-in adapter. Add-in Adapter Stopped Working Without Apparent Cause 1. Try re-seating the adapter first; then try a different slot if necessary. 2. The network driver files may be corrupt or deleted. Delete and then reinstall the drivers. 3. Run the diagnostics. Cannot Connect to a Server 1. Make sure you are using the drivers that are shipped on the resource CD for the onboard network controller. 2. Make sure the driver is loaded and the protocols are bound. 3. Make sure the network cable is securely attached to the connector at the server back panel. If the cable is attached but the problem persists, try a different cable. 4. Make sure the hub port is configured for the same duplex mode as the network controller. 5. Check with your LAN administrator about the correct networking software that needs to be installed. 6. If you are directly connecting two servers (no hub), you will need a crossover cable (refer to your hub documentation for more information on crossover cables). 7. Check the network controller LEDs that are visible through an opening on the server's back panel. 78 Chapter 6

  • 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
78
Chapter 6
Controller Stopped Working When an Add-in Adapter Was Installed
1.
Make sure the cable is connected to the port from the onboard network controller.
2.
Make sure your PCI BIOS is current.
3.
Make sure the other adapter supports shared interrupts. Also, make sure your operating system
supports shared interrupts.
4.
Try re-seating the add-in adapter.
Add-in Adapter Stopped Working Without Apparent Cause
1.
Try re-seating the adapter first; then try a different slot if necessary.
2.
The network driver files may be corrupt or deleted. Delete and then reinstall the drivers.
3.
Run the diagnostics.
Cannot Connect to a Server
1.
Make sure you are using the drivers that are shipped on the resource CD for the onboard network
controller.
2.
Make sure the driver is loaded and the protocols are bound.
3.
Make sure the network cable is securely attached to the connector at the server back panel. If the cable
is attached but the problem persists, try a different cable.
4.
Make sure the hub port is configured for the same duplex mode as the network controller.
5.
Check with your LAN administrator about the correct networking software that needs to be installed.
6.
If you are directly connecting two servers (no hub), you will need a crossover cable (refer to your hub
documentation for more information on crossover cables).
7.
Check the network controller LEDs that are visible through an opening on the server’s back panel.