HP Carrier-grade cc2300 UserÆs Guide and Technical UserÆs Gu - Page 128

Cannot Connect to a Server, Problems with Network, PCI Installation Tips

Page 128 highlights

HP cc3300 Carrier Grade Server Product Guide Cannot Connect to a Server • Make sure you are using the drivers that are shipped on the system Configuration Software CD for the onboard network controller. • Make sure the driver is loaded and the protocols are bound. • Make sure the network cable is securely attached to the connector at the system back panel. If the cable is attached but the problem persists, try a different cable. • Make sure the hub port is configured for the same duplex mode as the network controller. • Check with your LAN administrator about the correct networking software that needs to be installed. • If you are directly connecting two servers (no hub), you will need a crossover cable (see your hub documentation for more information on crossover cables). Check the network controller LEDs that are visible through an opening at the system back panel. Problems with Network The server hangs when the drivers are loaded. Change the PCI BIOS interrupt settings. Try the "PCI Installation Tips" below. Diagnostics pass, but the connection fails. • Make sure the network cable is securely attached. • Make sure you specify the correct frame type in your NET.CFG file. The Activity LED doesn't light. • The network activity light is not connected to the HP CC3300 CARRIER GRADE SERVER server board. The controller stopped working when an add-in card was installed. • Make sure the cable is connected to the port from the onboard network controller. • Make sure your PCI BIOS is current. Try the "PCI Installation Tips" below. • Make sure the other adapter supports shared interrupts. Also, make sure your operating system supports shared interrupts; OS/2† does not. • Try reseating the add-in card. The add-in card stopped working without apparent cause. • Try reseating the add-in card first; then try a different slot if necessary. • The network driver files may be corrupt or deleted. Delete and then reinstall the drivers. • Run the diagnostics. PCI Installation Tips Some common PCI tips are listed here. • Reserve interrupts (IRQs) and/or memory addresses specifically for ISA add-in cards. This prevents PCI add-in cards from trying to use the same settings ISA add-in cards are using. Use the SSU to keep track of ISA add-in card resources. • Certain drivers may require interrupts that are not shared with other PCI drivers. The SSU can be used to adjust the interrupt numbers for PCI devices. For certain drivers, it may be necessary to alter settings so that interrupts are not shared. 128 Solving Problems

  • 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

HP cc3300 Carrier Grade Server Product Guide
128
Solving Problems
Cannot Connect to a Server
Make sure you are using the drivers that are shipped on the system Configuration Software CD
for the onboard network controller.
Make sure the driver is loaded and the protocols are bound.
Make sure the network cable is securely attached to the connector at the system back panel.
If
the cable is attached but the problem persists, try a different cable.
Make sure the hub port is configured for the same duplex mode as the network controller.
Check with your LAN administrator about the correct networking software that needs to be
installed.
If you are directly connecting two servers (no hub), you will need a crossover cable (see your
hub documentation for more information on crossover cables).
Check the network controller LEDs that are visible through an opening at the system back panel.
Problems with Network
The server hangs when the drivers are loaded.
Change the PCI BIOS interrupt settings.
Try the “PCI Installation Tips” below.
Diagnostics pass, but the connection fails.
Make sure the network cable is securely attached.
Make sure you specify the correct frame type in your NET.CFG file.
The Activity LED doesn’t light.
The network activity light is not connected to the HP CC3300 CARRIER GRADE SERVER
server board.
The controller stopped working when an add-in card was installed.
Make sure the cable is connected to the port from the onboard network controller.
Make sure your PCI BIOS is current.
Try the “PCI Installation Tips” below.
Make sure the other adapter supports shared interrupts.
Also, make sure your operating system
supports shared interrupts; OS/2
does not.
Try reseating the add-in card.
The add-in card stopped working without apparent cause.
Try reseating the add-in card first; then try a different slot if necessary.
The network driver files may be corrupt or deleted.
Delete and then reinstall the drivers.
Run the diagnostics.
PCI Installation Tips
Some common PCI tips are listed here.
Reserve interrupts (IRQs) and/or memory addresses specifically for ISA add-in cards.
This
prevents PCI add-in cards from trying to use the same settings ISA add-in cards are using.
Use
the SSU to keep track of ISA add-in card resources.
Certain drivers may require interrupts that are not shared with other PCI drivers.
The SSU can
be used to adjust the interrupt numbers for PCI devices.
For certain drivers, it may be
necessary to alter settings so that interrupts are not shared.