HP Integrity rx2800 HP Integrity Servers with Microsoft Windows Server 2008 R2 - Page 23

Network Interface Cards NICs

Page 23 highlights

Workaround These are informational events. When the system is booted up, a type DC event entry is generated in the SEL. When the system is gracefully shut down, one or more type DD event entries are generated in the SEL. Unknown IPMI Type-E1 event Issue The iLO SL (Show Event Logs) menu might report an unknown IPMI Type-E1 event after an OS boot completed event or after an OS graceful shutdown occurred event. Servers HP Integrity BL8x0 i2 Server Blade Workaround You can ignore these unknown IPMI Type-E1 events as they are duplicates of the OS boot completed and OS graceful shutdown occurred events. Network Interface Cards (NICs) Possible performance issues with 10 Gb NICs in systems with greater than 32 physical CPUs Issue On systems with greater than 32 physical CPUs and AD385A-HP PCI-X 266MHz 10Gb Ethernet SR multi-OS cards, under heavy networking traffic an issue with the NDIS driver can cause system sluggishness and performance issues. Servers Superdome SX2000 Workaround HP recommends placing the 10Gb Ethernet cards in the I/O chassis attached to the root cell. Additionally, if the task manager reports high utilization on CPU0, HP recommends that you change the RssBaseCpu registry value for the 10 Gb adapter from CPU0 to a non-zero CPU. See the Microsoft Knowledge Base for instructions. A driver with a workaround will be available soon on http://www.hp.com. AD385A NIC card can affect server performance under a load Issue When handling IPv6 traffic, a server with the Neterion AD385A NIC card installed can exhibit sluggish performance. In some cases, a DPC Watchdog timeout event occurs. Servers Superdome SX2000, rx8640, rx7640, rx6600, rx3600, rx2660 Workaround Set the RssBaseCpu registry value in HLKM\System\CurrentControlSet\ Services\NDIS\Parameters to 8 (the default is 4). For more information, see the Receive-Side Scaling Enhancements in Windows Server 2008 white paper at http://www.microsoft.com/whdc/device/network/NDIS_RSS.mspx Server with A9899A or A9900A NIC cards does not reboot after a crash Problem In the unlikely event of system crash, an Integrity server with the A9899A or A9900A NIC card installed might fail to automatically restart. Servers Superdome SX2000, rx8640, rx7640, rx6600, rx3600, rx2660 Workaround Manually reboot the system. HP is aware of this issue. SCSI Event ID 129 errors on Integrity blade servers Issue HP Integrity blade servers with the embedded 1068 SAS controller that are using the in-box driver (revision 1.28.03.51) for the embedded SAS controller can see excessive Event ID 129 errors. Servers HP Integrity BL860c Server Blade and BL870c Server Blade Troubleshooting Common Issues 23

  • 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

Workaround
These are informational events. When the system is booted up, a type
DC
event
entry is generated in the SEL. When the system is gracefully shut down, one or
more type
DD
event entries are generated in the SEL.
Unknown IPMI Type-E1 event
Issue
The iLO
SL (Show Event Logs)
menu might report an unknown IPMI Type-E1
event after an
OS boot completed
event or after an
OS graceful
shutdown occurred
event.
Servers
HP Integrity BL8x0 i2 Server Blade
Workaround
You can ignore these unknown IPMI Type-E1 events as they are duplicates of
the
OS boot completed
and
OS graceful shutdown occurred
events.
Network Interface Cards (NICs)
Possible performance issues with 10 Gb NICs in systems with greater than 32 physical CPUs
Issue
On systems with greater than 32 physical CPUs and AD385A-HP PCI-X 266MHz
10Gb Ethernet SR multi-OS cards, under heavy networking traffic an issue with
the NDIS driver can cause system sluggishness and performance issues.
Servers
Superdome SX2000
Workaround
HP recommends placing the 10Gb Ethernet cards in the I/O chassis attached to
the root cell. Additionally, if the task manager reports high utilization on CPU0,
HP recommends that you change the
RssBaseCpu
registry value for the 10 Gb
adapter from CPU0 to a non-zero CPU. See the Microsoft Knowledge Base for
instructions.
A driver with a workaround will be available soon on
http://www
.hp.com
.
AD385A NIC card can affect server performance under a load
Issue
When handling IPv6 traffic, a server with the Neterion AD385A NIC card
installed can exhibit sluggish performance. In some cases, a DPC Watchdog
timeout event occurs.
Servers
Superdome SX2000, rx8640, rx7640, rx6600, rx3600, rx2660
Workaround
Set the
RssBaseCpu
registry value in
HLKM\System\CurrentControlSet\
Services\NDIS\Parameters
to 8 (the default is 4). For more information,
see the
Receive-Side Scaling Enhancements in Windows Server 2008
white paper at
http://www
.microsoft.com/whdc/device/netw
ork/NDIS_RSS.mspx
Server with A9899A or A9900A NIC cards does not reboot after a crash
Problem
In the unlikely event of system crash, an Integrity server with the A9899A or
A9900A NIC card installed might fail to automatically restart.
Servers
Superdome SX2000, rx8640, rx7640, rx6600, rx3600, rx2660
Workaround
Manually reboot the system. HP is aware of this issue.
SCSI
Event ID 129 errors on Integrity blade servers
Issue
HP Integrity blade servers with the embedded 1068 SAS controller that are
using the in-box driver (revision 1.28.03.51) for the embedded SAS controller
can see excessive Event ID 129 errors.
Servers
HP Integrity BL860c Server Blade and BL870c Server Blade
Troubleshooting Common Issues
23