Dell Broadcom NetXtreme Family of Adapters Broadcom NetXtreme 57XX User Guide - Page 166

Event Log Messages

Get Dell Broadcom NetXtreme Family of Adapters PDF manuals and user guides View all Dell Broadcom NetXtreme Family of Adapters manuals
Add to My Manuals
Save this manual to your list of manuals

Page 166 highlights

Question: How do I know what driver I am currently using? Answer: In all operating systems, the most accurate method for checking the driver revision is to physically locate the driver file and check the properties. Question: Can SLB detect a switch failure in a Switch Fault Tolerance configuration? Answer: No. SLB can detect only the loss of link between the teamed port and its immediate link partner. SLB cannot detect link failures on other ports. For more information, see LiveLink™ Functionality. Question: Where can I get the latest supported drivers? Answer: Go to Dell support at www.support.dell.com for driver package updates or support documents. Question: Where do I monitor real time statistics for an adapter team in a Windows system? Answer: Use the Broadcom Advanced Control Suite 3 (BACS 3) to monitor general, IEEE 802.3, and custom counters. Event Log Messages Windows System Event Log Messages Base Driver (Physical Adapter/Miniport) Intermediate Driver (Virtual Adapter/Team) Windows System Event Log Messages The known base driver and intermediate driver Windows System Event Log status messages for the Broadcom NetXtreme Gigabit Ethernet adapters as of December 2004 are listed. As a Broadcom adapter driver loads, Windows places a status code in the system event viewer. There may be up to two classes of entries for these event codes depending on whether both drivers are loaded (one set for the base or miniport driver and one set for the intermediate or teaming driver). Base Driver (Physical Adapter/Miniport) Table 9 lists the event log messages supported by the base driver, explains the cause for the message, and provides the recommended action. Table 9. Base Driver Event Log Messages Message Number Message Cause Corrective Action Failed to allocate memory 1 for the device block. Check system memory The driver cannot allocate memory from the operating system. Close running applications to free memory. resource usage. 2 Failed to allocate map registers The driver cannot allocate map registers from the operating system. Unload other drivers that may allocate map registers. 3 Failed to access configuration information. Reinstall the network driver. The driver cannot access PCI configuration space registers on the adapter. For add-in adapters: reseat the adapter in the slot, move the adapter to another PCI slot, or replace the adapter. The network link is down. 4 Check to make sure the The adapter has lost its Check that the network cable is connected, verify that the network cable is the right type, and verify

  • 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
Question:
How do I know what driver I am currently using?
Answer:
In all operating systems, the most accurate method for checking the driver revision is to physically locate the
driver file and check the properties.
Question:
Can SLB detect a switch failure in a Switch Fault Tolerance configuration?
Answer:
No. SLB can detect only the loss of link between the teamed port and its immediate link partner. SLB cannot
detect link failures on other ports. For more information, see
LiveLink™ Functionality
.
Question:
Where can I get the latest supported drivers?
Answer:
Go to Dell support at www.support.dell.com for driver package updates or support documents.
Question:
Where do I monitor real time statistics for an adapter team in a Windows system?
Answer:
Use the Broadcom Advanced Control Suite 3 (BACS 3) to monitor general, IEEE 802.3, and custom counters.
Event Log Messages
Windows System Event Log Messages
Base Driver (Physical Adapter/Miniport)
Intermediate Driver (Virtual Adapter/Team)
Windows System Event Log Messages
The known base driver and intermediate driver Windows System Event Log status messages for the Broadcom NetXtreme
Gigabit Ethernet adapters as of December 2004 are listed. As a Broadcom adapter driver loads, Windows places a status code
in the system event viewer. There may be up to two classes of entries for these event codes depending on whether both
drivers are loaded (one set for the base or miniport driver and one set for the intermediate or teaming driver).
Base Driver (Physical Adapter/Miniport)
Table 9
lists the event log messages supported by the base driver, explains the cause for the message, and provides the
recommended action.
Table 9. Base Driver Event Log Messages
Message
Number
Message
Cause
Corrective Action
1
Failed to allocate memory
for the device block.
Check system memory
resource usage.
The driver cannot allocate memory
from the operating system.
Close running applications to free memory.
2
Failed to allocate map
registers
The driver cannot allocate map
registers from the operating
system.
Unload other drivers that may allocate map
registers.
3
Failed to access
configuration information.
Reinstall the network
driver.
The driver cannot access PCI
configuration space registers on
the adapter.
For add-in adapters: reseat the adapter in the slot,
move the adapter to another PCI slot, or replace
the adapter.
4
The network link is down.
Check to make sure the
The adapter has lost its
Check that the network cable is connected, verify
that the network cable is the right type, and verify