| | DisplayName | Description | ID | Target | Category | Enabled | Instance Name | Counter Name | Frequency | Event_ID | Event Source | Alert Generate | Alert Severity | Alert Priority | Remotable | Event Log |
|---|
 | Task Management Function abort was received on a task that is not present. [BE2ISCSI_10] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_10 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10 | be2iscsi | True | Error | High | True | System |
| Error in determining firmware configuration. [BE2ISCSI_11] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_11 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 11 | be2iscsi | True | Error | High | True | System |
| iSCSI error was detected on session A, ExpCmdSn B, MaxCmdSn C. [BE2ISCSI_14] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_14 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 14 | be2iscsi | True | Warning | Normal | True | System |
| The iSCSI target on session id N failed to open the command window within configured timeout. [BE2ISCSI_15] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_15 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 15 | be2iscsi | True | Warning | Normal | True | System |
| Encountered an error offloading an iSCSI connection, error code N. [BE2ISCSI_16] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_16 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 16 | be2iscsi | True | Warning | Normal | True | System |
| The IOCTL opcode A requires more scatter gather elements than allowed. Transfer length is B. [BE2ISCSI_17] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_17 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 17 | be2iscsi | True | Warning | Normal | True | System |
| Unrecoverable error detected. UE Low: A UE High: B FW Line: C. An unrecoverable error was detected by the iSCSI driver. [BE2ISCSI_18] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_18 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 18 | be2iscsi | True | Error | High | True | System |
| Hardware initialization failed, failing driver load The iSCSI driver detected a failure in the hardware during initialization. [BE2ISCSI_19] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_19 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 19 | be2iscsi | True | Error | High | True | System |
| Failed to retrieve scatter gather list for an SRB, an IO has failed. [BE2ISCSI_20] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_20 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 20 | be2iscsi | True | Warning | Normal | True | System |
| ACIT library table initialization failed. An internal API failed in the iSCSI driver during initialization. [BE2ISCSI_21] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_21 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 21 | be2iscsi | True | Error | High | True | System |
| An ACIT API failed. An internal API failed in the iSCSI driver during initialization. [BE2ISCSI_22] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_22 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 22 | be2iscsi | True | Error | High | True | System |
| Unsupported hardware, failing driver load. [BE2ISCSI_23] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_23 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 23 | be2iscsi | True | Error | High | True | System |
| Memory could not be allocated, failing driver load. [BE2ISCSI_24] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_24 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 24 | be2iscsi | True | Error | High | True | System |
| WMI driver error, code A. The iSCSI driver failed a WMI IOCTL request from the port driver. [BE2ISCSI_25] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_25 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 25 | be2iscsi | True | Warning | Normal | True | System |
| WMI IOCTL error, code A. The iSCSI driver failed a WMI IOCTL request from the port driver because the request was failed by the ARM firmware. [BE2ISCSI_26] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_26 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 26 | be2iscsi | True | Warning | Normal | True | System |
| A configuration parameter is out of range. [BE2ISCSI_27] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_27 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 27 | be2iscsi | True | Warning | Normal | True | System |
| A configuration parameter is invalid. [BE2ISCSI_29] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_29 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 29 | be2iscsi | True | Warning | Normal | True | System |
| Failed to map Base Address Register, failing driver load. [BE2ISCSI_30] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_30 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 30 | be2iscsi | True | Error | High | True | System |
| Hardware initialization has failed ? error code A. [BE2ISCSI_31] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_31 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 31 | be2iscsi | True | Error | High | True | System |
| Initial memory allocation failed, driver is running with reduced capabilities. [BE2ISCSI_32] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_32 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 32 | be2iscsi | True | Warning | Normal | True | System |
| Interrupt Redirection capability is not supported by this firmware. [BE2ISCSI_35] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_35 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 35 | be2iscsi | True | Warning | Normal | True | System |
| Device is not supported on Windows 7 Operating System, failing driver load. [BE2ISCSI_36] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_36 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 36 | be2iscsi | True | Error | High | True | System |
| Logical link on the OneConnect Port is down, traffic is disallowed on this function. [BE2ISCSI_38] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_38 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 38 | be2iscsi | True | Warning | Normal | True | System |
| Firmware returned invalid data in its configuration. [BE2ISCSI_39] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_39 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 39 | be2iscsi | True | Error | High | True | System |
| Firmware version does not match with driver version. [BE2ISCSI_4] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_4 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 4 | be2iscsi | True | Error | High | True | System |
| Error Recovery is not being attempted. [BE2ISCSI_40] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_40 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 40 | be2iscsi | True | Warning | Normal | True | System |
| The firmware appears unresponsive [BE2ISCSI_44] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_44 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 44 | be2iscsi | True | Error | High | True | System |
| Solicited command was invalidated internally due to a Data Digest error. [BE2ISCSI_47] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_47 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 47 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally [BE2ISCSI_48] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_48 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 48 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally [BE2ISCSI_49] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_49 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 49 | be2iscsi | True | Warning | Normal | True | System |
| Port link is down, check connection to UCNA. [BE2ISCSI_5] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_5 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally [BE2ISCSI_50] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_50 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 50 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally due to a Header Digest warning. [BE2ISCSI_51] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_51 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 51 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally due to a bad opcode in the PDU header. [BE2ISCSI_52] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_52 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 52 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally due to a received ITT/TTT that did not belong to this connection. [BE2ISCSI_53] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_53 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 53 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally [BE2ISCSI_54] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_54 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 54 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally due to an incoming TCP RST. [BE2ISCSI_55] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_55 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 55 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally due to TCP protocol warning (SYN received, maximum retransmits exceeded, urgent received, etc.). [BE2ISCSI_56] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_56 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 56 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally due to TCP RST sent by the transmit side. [BE2ISCSI_57] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_57 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 57 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally due to an incoming TCP FIN. [BE2ISCSI_58] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_58 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 58 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally due to a bad unsolicited PDU (unsolicited PDUs are PDUs with ITT=0xffffffff). [BE2ISCSI_59] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_59 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 59 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally due to a bad WRB index. [BE2ISCSI_60] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_60 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 60 | be2iscsi | True | Warning | Normal | True | System |
| Command was invalidated internally [BE2ISCSI_61] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_61 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 61 | be2iscsi | True | Warning | Normal | True | System |
| Command was invalidated internally [BE2ISCSI_62] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_62 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 62 | be2iscsi | True | Warning | Normal | True | System |
| Command was invalidated internally [BE2ISCSI_63] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_63 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 63 | be2iscsi | True | Warning | Normal | True | System |
| Command was invalidated internally [BE2ISCSI_64] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_64 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 64 | be2iscsi | True | Warning | Normal | True | System |
| Command was invalidated internally [BE2ISCSI_65] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_65 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 65 | be2iscsi | True | Warning | Normal | True | System |
| Command was invalidated internally [BE2ISCSI_66] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_66 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 66 | be2iscsi | True | Warning | Normal | True | System |
| Command was invalidated [BE2ISCSI_67] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_67 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 67 | be2iscsi | True | Warning | Normal | True | System |
| Command was invalidated [BE2ISCSI_68] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_68 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 68 | be2iscsi | True | Warning | Normal | True | System |
| Command was invalidated internally [BE2ISCSI_69] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_69 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 69 | be2iscsi | True | Warning | Normal | True | System |
| Link down timeout expired on the port, all targets are lost. [BE2ISCSI_7] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_7 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 7 | be2iscsi | True | Error | High | True | System |
| Connection invalidation completion notification. [BE2ISCSI_70] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_70 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 70 | be2iscsi | True | Warning | Normal | True | System |
| Connection invalidation completion with data PDU index. [BE2ISCSI_71] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_71 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 71 | be2iscsi | True | Warning | Normal | True | System |
| Command invalidation completion notification. [BE2ISCSI_72] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_72 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 72 | be2iscsi | True | Warning | Normal | True | System |
| Unsolicited header notification. [BE2ISCSI_73] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_73 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 73 | be2iscsi | True | Warning | Normal | True | System |
| Unsolicited data notification. [BE2ISCSI_74] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_74 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 74 | be2iscsi | True | Warning | Normal | True | System |
| Unsolicited data digest warning notification. [BE2ISCSI_75] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_75 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 75 | be2iscsi | True | Warning | Normal | True | System |
| TCP acknowledge based notification. [BE2ISCSI_76] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_76 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 76 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally [BE2ISCSI_77] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_77 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 77 | be2iscsi | True | Warning | Normal | True | System |
| Solicited command was invalidated internally due to DIF warning. [BE2ISCSI_78] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_78 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 78 | be2iscsi | True | Warning | Normal | True | System |
| Connection was invalidated internally due to an incoming unsolicited PDU that had immediate data on the connection that does not support it. [BE2ISCSI_79] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_79 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 79 | be2iscsi | True | Warning | Normal | True | System |
| Target with session id N failed to connect within the configured timeout. [BE2ISCSI_8] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_8 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8 | be2iscsi | True | Error | High | True | System |
| Task Management request N was unhandled. The iSCSI driver received a Task Management Function that is not supported, and it rejected this request. [BE2ISCSI_9] | Error message of driver of Emulex iSCSI Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2ISCSI_9 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 9 | be2iscsi | True | Error | High | True | System |
| The network device detected an error. [BE2NET_10] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_10 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10 | be2net | True | Error | High | True | System |
| The device firmware does not support ETS functionality in SR-IOV or multichannel mode. [BE2NET_1073741880] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_1073741880 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 1073741880 | be2net | True | Warning | Normal | True | System |
| The network driver was reset. [BE2NET_16] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_16 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 16 | be2net | True | Warning | Normal | True | System |
| The driver is incompatible with the device. [BE2NET_17] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_17 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 17 | be2net | True | Error | High | True | System |
| Failed to enable bus mastering. [BE2NET_18] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_18 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 18 | be2net | True | Error | High | True | System |
| Resource conflict. The operating system failed to allocate resources for the device. [BE2NET_19] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_19 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 19 | be2net | True | Error | High | True | System |
| The network driver initialization failed. [BE2NET_2] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_2 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 2 | be2net | True | Error | High | True | System |
| Failed to read registry configuration. [BE2NET_20] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_20 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 20 | be2net | True | Error | High | True | System |
| Firmware version does not match driver version. [BE2NET_21] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_21 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 21 | be2net | True | Warning | Normal | True | System |
| Firmware does not support GRE encapsulation. [BE2NET_2147483705] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_2147483705 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 2147483705 | be2net | True | Warning | Normal | True | System |
| Vital product data is not initialized correctly. [BE2NET_28] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_28 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 28 | be2net | True | Error | High | True | System |
| Unsupported medium. [BE2NET_3] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_3 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 3 | be2net | True | Error | High | True | System |
| The Ethernet link is down due to a local fault. [BE2NET_34] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_34 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 34 | be2net | True | Warning | Normal | True | System |
| The Ethernet link is down due to a remote fault. [BE2NET_35] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_35 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 35 | be2net | True | Warning | Normal | True | System |
| The device firmware does not support network functionality. [BE2NET_36] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_36 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 36 | be2net | True | Error | High | True | System |
| The device firmware does not support TCP offload functionality. [BE2NET_37] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_37 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 37 | be2net | True | Warning | Normal | True | System |
| The device firmware does not support RSS functionality for this network adapter. [BE2NET_38] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_38 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 38 | be2net | True | Warning | Normal | True | System |
| Failed to map device registers. [BE2NET_4] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_4 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 4 | be2net | True | Error | High | True | System |
| The firmware is outdated and does not support TOE offloads for this driver. [BE2NET_40] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_40 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 40 | be2net | True | Warning | Normal | True | System |
| Legacy driver loaded. [BE2NET_41] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_41 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 41 | be2net | True | Warning | Normal | True | System |
| Legacy driver loaded. [BE2NET_42] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_42 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 42 | be2net | True | Warning | Normal | True | System |
| Error recovery is disabled on the system. [BE2NET_44] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_44 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 44 | be2net | True | Warning | Normal | True | System |
| Error recovery failed. [BE2NET_45] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_45 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 45 | be2net | True | Error | High | True | System |
| Device is not supported on Windows 7 Operating System. [BE2NET_46] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_46 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 46 | be2net | True | Error | High | True | System |
| VMQ offload is disabled. [BE2NET_47] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_47 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 47 | be2net | True | Warning | Normal | True | System |
| SR-IOV is not enabled. [BE2NET_48] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_48 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 48 | be2net | True | Warning | Normal | True | System |
| RSS is limited to 4 queues. [BE2NET_49] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_49 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 49 | be2net | True | Warning | Normal | True | System |
| Failed to register scatter gather DMA. [BE2NET_5] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_5 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5 | be2net | True | Error | High | True | System |
| The Ethernet link is down due to PHY over-temperature condition. [BE2NET_50] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_50 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 50 | be2net | True | Warning | Normal | True | System |
| SR-IOV virtualization failed initialization. [BE2NET_51] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_51 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 51 | be2net | True | Warning | Normal | True | System |
| Optics faulted/incorrectly installed/not installed. [BE2NET_52] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_52 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 52 | be2net | True | Warning | Normal | True | System |
| Optics of two types installed-Remove one optic or install matching pair of optics. [BE2NET_53] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_53 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 53 | be2net | True | Warning | Normal | True | System |
| Incompatible optics [BE2NET_54] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_54 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 54 | be2net | True | Warning | Normal | True | System |
| This adapter may have a problem recovering from corrupted use of SR-IOV. [BE2NET_55] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_55 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 55 | be2net | True | Warning | Normal | True | System |
| Driver load failed due to memory allocation failure [BE2NET_6] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_6 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 6 | be2net | True | Error | High | True | System |
| A memory allocation failure occurred during driver load. [BE2NET_7] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_7 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 7 | be2net | True | Warning | Normal | True | System |
| Failed to get TCP offload handlers. [BE2NET_8] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_8 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8 | be2net | True | Error | High | True | System |
| Failed to register interrupt service routine. [BE2NET_9] | Error message of driver of Emulex NIC/TOE Controller | Fujitsu.Servers.PRIMERGY.Windows.Rules.BE2NET_9 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 9 | be2net | True | Error | High | True | System |
| Failed to allocate memory for the device block [BROADCOM_B57W2K_01] | Error message of driver of Broadcom LAN Adapter BCM57xx. Check system memory resource usage | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_B57W2K_01 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 1 | B57W2K | True | Error | High | True | System |
| Failed to allocate map registers [BROADCOM_B57W2K_02] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_B57W2K_02 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 2 | B57W2K | True | Error | High | True | System |
| Failed to access configuration information [BROADCOM_B57W2K_03] | Error message of driver of Broadcom LAN Adapter BCM57xx. Re-install network driver | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_B57W2K_03 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 3 | B57W2K | True | Error | High | True | System |
| The network link is down [BROADCOM_B57W2K_04] | Error message of driver of Broadcom LAN Adapter BCM57xx.Check to make sure the network cable is properly connected | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_B57W2K_04 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4 | B57W2K | True | Warning | Normal | True | System |
| Medium not supported [BROADCOM_B57W2K_12] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_B57W2K_12 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 12 | B57W2K | True | Error | High | True | System |
| Unable to register the interrupt service routine [BROADCOM_B57W2K_13] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_B57W2K_13 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 13 | B57W2K | True | Error | High | True | System |
| Unable to map IO space [BROADCOM_B57W2K_14] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_B57W2K_14 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 14 | B57W2K | True | Error | High | True | System |
| Cannot enter low-power mode because the driver may not be able to auto-negotiate the link down to 10Mbps [BROADCOM_B57W2K_17] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_B57W2K_17 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 17 | B57W2K | True | Error | High | True | System |
| Unknown PHY detected. Using a default PHY initialization routine [BROADCOM_B57W2K_18] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_B57W2K_18 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 18 | B57W2K | True | Error | High | True | System |
| This driver does not support this device [BROADCOM_B57W2K_19] | Error message of driver of Broadcom LAN Adapter BCM57xx. Upgrade to the latest driver | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_B57W2K_19 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 19 | B57W2K | True | Error | High | True | System |
| Driver initialization failed [BROADCOM_B57W2K_20] | Error message of driver of Broadcom LAN Adapter BCM57xx. | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_B57W2K_20 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 20 | B57W2K | True | Error | High | True | System |
| Unable to register with NDIS [BROADCOM_BT_02] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_BT_02 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 2 | BT | True | Error | High | True | System |
| Unable to instantiate the management interface [BROADCOM_BT_03] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_BT_03 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 3 | BT | True | Error | High | True | System |
| Unable to create symbolic link for the management interface [BROADCOM_BT_04] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_BT_04 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 4 | BT | True | Error | High | True | System |
| Could not allocate memory for internal data structures [BROADCOM_BT_07] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_BT_07 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 7 | BT | True | Error | High | True | System |
| Could not bind to adapter [BROADCOM_BT_08] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_BT_08 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8 | BT | True | Error | High | True | System |
| Network adapter is disconnected [BROADCOM_BT_10] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_BT_10 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 10 | BT | True | Warning | Normal | True | System |
| Broadcom Advanced Program Features Driver is NOT designed to run on this version of Operating System [BROADCOM_BT_12] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_BT_12 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 12 | BT | True | Error | High | True | System |
| Network adapter is disabled via management interface [BROADCOM_BT_16] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_BT_16 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 16 | BT | True | Warning | Normal | True | System |
| Network adapter is de-activated and is no longer participating in network traffic [BROADCOM_BT_18] | Error message of driver of Broadcom LAN Adapter BCM57xx | Fujitsu.Servers.PRIMERGY.Windows.Rules.BROADCOM_BT_18 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 18 | BT | True | Warning | Normal | True | System |
| Thread allocation failed! [DDM_1] | DDM cannot control this device correctly because there is a lack of memory. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_1 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 1 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: Configuration error. Mirror size less used disk space. Data loss possible! [DDM_16] | The size of the disk, to which the data of the other disk of the DW group should be copied (Mirror) is less than all partitions listed in the partition-table of the source disk. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_16 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 16 | ddm | True | Warning | Normal | True | System |
| MP PxPxTxLx: failed and was disabled! [DDM_18] | DDM has detected a failure on this path. The path is not usable anymore. Recovering from error will be logged by event id 4354. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_18 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 18 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx failed! [DDM_2] | DDM has discovered a failure at the device PxPxTxLx. The status of the device is set to error, and no data is written to this device anymore. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_2 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 2 | ddm | True | Warning | Normal | True | System |
| MP PxPxTxLx: Memory allocation problem! [DDM_21] | DDM cannot control this device correctly because there is a lack of memory. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_21 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 21 | ddm | True | Warning | Normal | True | System |
| MP PxPxTxLx: Device was removed / path gone! This path was removed by Plug and Play functions of the system, after an error was detected. [DDM_25] | This event may occur after event id 18, but may also appear without any other id. If the path reappears, this will be logged by event id 4354. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_25 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 25 | ddm | True | Warning | Normal | True | System |
| DDM PxPxTxLx: Device had signature that was already found for another disk! [DDM_26] | All disks should have signatures (stored in the Master Boot Record (MBR)), which are unique to the system. Exception: The two pieces (or two disks) of a DuplexWrite group are identical and have the same signature. When this error is logged, DDM has found a disk which has the same signature as another disk in the system, and which are not members of a DuplexWrite group. That disk will be disabled and not be accessible. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_26 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 26 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: Memory allocation problem! [DDM_3] | DDM cannot control this device correctly because there is a lack of memory. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_3 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 3 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: Signatures on piece0 and piece1 are different but cannot be restored. [DDM_4368] | This is a serious problem which cannot be fixed by the driver. It is necessary to repair signatures on both pieces by hand (i.e. with ddmutil). | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4368 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4368 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: Second try to write FastRecoverArray while both pieces are online! [DDM_4369] | There was an error keeping track of the changes written to disk. Delta Recover is disabled. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4369 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 4369 | ddm | True | Error | High | True | System |
| DW PxPxTxLx: Someone has written a wrong Signature to MBR! [DDM_4370] | This could destroy a cluster, a cluster resource or a Duplex Write group! | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4370 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 4370 | ddm | True | Error | High | True | System |
| DW PxPxTxLx: Piece was removed. [DDM_4371] | Duplex Write piece was removed by Plug and Play event. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4371 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4371 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: The other piece is missing! [DDM_4373] | Logged only if 'StrictChecking' is enabled. In this case, IO to a DW group is only possible if both pieces of a DW group are accessible - if not this event entry is logged. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4373 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4373 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: The array for Delta Recover Information is already initialized. [DDM_4374] | FastRecoverEnabled is already set! This might be an internal error. Contact your local Fujitsu Helpdesk. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4374 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4374 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: DWLun for this piece is not set. [DDM_4376] | In data structure DeviceExtension is flag DWLun not set. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4376 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4376 | ddm | True | Warning | Normal | True | System |
| Fault tolerance for the RootDisk is not warranted anymore. [DDM_4384] | Fault tolerance for the RootDisk is not warranted anymore. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4384 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 4384 | ddm | True | Error | High | True | System |
| DW PxPxTxLx: DuplexWrite has discovered a possible split brain situation, caused by a broken fibre channel connection. [DDM_4385] | In this situation, both nodes have access to one piece of this DW-Group. To avoid data corruption, this may occur, if the node, which did not own this disk, does a failover of it, this piece was set to DISABLED. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4385 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4385 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: The second piece of this DW-Group is more recent, but it is not set to online, because there were write-commands sent to the first piece. [DDM_4387] | This event log may occur, if a piece of a DW-group is returned to its original system after it was attached to another system, which also runs with DDM. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4387 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4387 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: A command was retried after failure. [DDM_4388] | This event log may occur, if an access to a device in Failover Cluster (Windows Server 2008, Persistent Reservation) failed. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4388 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4388 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: A DuplexWrite RootDisk mirror (system mirror) was detected. Therefore the DuplexDataManager support for Microsoft Failover Clustering is switched off. [DDM_4389] | This event log may occur, if the Microsoft Failover Clustering feature is enabled and a DuplexWrite RootDisk mirror (system mirror) is configured. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_4389 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4389 | ddm | True | Warning | Normal | True | System |
| Error: DuplexDataManager Service could not initialize. [DDM_5122] | Check for a correct installation. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5122 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5122 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - No NVRAM or BIOS access. [DDM_5123] | DuplexWrite cannot support an automatic reboot in case of system/boot disk failure. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5123 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5123 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Consistency Check (SCSI address of both pieces) READ at block number failed. [DDM_5125] | The data for comparing will be read from both pieces via SCSI PassThrough commands. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5125 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5125 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Consistency Check (SCSI addresses of both pieces) failed. The data is different at block number. [DDM_5126] | DDM SERVICE CONSISTENCY CHECK INTERRUPT | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5126 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5126 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Consistency Check (SCSI addresses of both pieces) failed (no normal termination). [DDM_5127] | DDM SERVICE CONSISTENCY CHECK CATCH | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5127 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5127 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Consistency Check (SCSI addresses of both pieces) canceled at block number. There are different numbers of blocks found! [DDM_5129] | The consistency check is canceled by user. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5129 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5129 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Consistency Check (SCSI addresses of both pieces) finished with different blocks found. [DDM_5131] | Consistency Check (SCSI addresses of both pieces) finished with different blocks found. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5131 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5131 | ddm | True | Error | High | True | System |
| Error: Error: DuplexDataManager Service - xxx. [DDM_5132] | Only used for development or debugging case! | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5132 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5132 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Found inconsistent signatures in DuplexWrite group www:xxx, yyy:zzz. [DDM_5133] | Please check if anyone changed the disk signature in the master boot record (MBR). Use ddmutil to fix this problem. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5133 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5133 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Fatal error caught in a routine. [DDM_5135] | DDM SERVICE FATAL ERROR | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5135 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5135 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - CloneData (port/path/target/lun) failed (no normal termination). [DDM_5138] | Please restart DuplexDataManager service. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5138 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5138 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - CloneData (port/path/target/lun of device) READ at block number failed. [DDM_5139] | DuplexDataManager Service - CloneData (4/0/2/0) READ at block number 254378 failed. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5139 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5139 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - CloneData (data) WRITE at block number failed. [DDM_5140] | DuplexDataManager Service - CloneData (4/0/2/0) WRITE at block number 254378 failed. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5140 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5140 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - CloneData (port/path/target/lun). [DDM_5144] | Terminate CloneData because status of source piece changed | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5144 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5144 | ddm | True | Error | High | True | System |
| Warning: DuplexDataManager Service - Manage AutoAdjust xxx: Unexpected storage access path configuration (ctrl/port: yyy). [DDM_5146] | The feature AutoAdjust not released. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5146 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5146 | ddm | True | Warning | Normal | True | System |
| Warning: DuplexDataManager Service - Manage AutoAdjust xxx: Different access paths to storage -> activate yyy. [DDM_5147] | The feature AutoAdjust not released. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5147 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5147 | ddm | True | Warning | Normal | True | System |
| Error: DuplexDataManager Service - Due starting the DuplexDataManager service the process ddmwatch.exe is still running / hanging. [DDM_5151] | DDM SERVICE DDMWATCH RUNNING | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5151 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5151 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - MultiPath configuration changed. The path is missing. [DDM_5152] | DDM SERVICE MONITOR | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5152 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5152 | ddm | True | Error | High | True | System |
| Warning: DuplexDataManager Service. [DDM_5156] | DDM_SERVICE MPIO WARNING | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5156 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5156 | ddm | True | Warning | Normal | True | System |
| Error: DuplexDataManager Service [DDM_5157] | DDM SERVICE MPIO ERROR | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5157 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5157 | ddm | True | Error | High | True | System |
| Warning: DuplexDataManager Service - The Virtual Disk Service (VDS) is active. The Storage Manager for SANs may produce VDS error entries in the system event log. [DDM_5158] | DDM SERVICE VDS ACTIVE | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5158 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5158 | ddm | True | Warning | Normal | True | System |
| Error: DuplexDataManager Service - Found inconsistent Disk GUIDs in DuplexWrite group xxx. [DDM_5162] | Please check if anyone changed the Disk GUID in the GPT partition table. Use ddmutil to fix this problem. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5162 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5162 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - The MultiPath configuration changed. The disk identification is different: xxx. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. [DDM_5163 | This error event only generated for acknowledged (stored) MultiPath configurations, where no disk signature available / accessible at the acknowledge time. Please check the MultiPath configuration for missing paths and devices. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5163 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5163 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - The MultiPath configuration changed. Path(s) missing to disk: xxx. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. [DDM_5164] | Please check the MultiPath configuration for missing paths and devices. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5164 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5164 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - The MultiPath configuration changed. The disk: xxx is missing. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. [DDM_5165] | Please check the MultiPath configuration for missing paths and devices. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5165 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5165 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - The MultiPath configuration changed. There are xxx disk(s) missing. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. [DDM_5166] | Please check the MultiPath configuration for missing paths and devices. If the current configuration is correct, please acknowledge this configuration via the MMC snap-in to suppress this error message. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5166 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5166 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Failed to start x10sureIS configuration script: xxx - yyy [DDM_5168] | The DDM service calls the x10sureIS script to manage the DuplexWrite groups. Check if script is available and accessible. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5168 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5168 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - No any xxx disk for x10sureIS configuration found. [DDM_5169] | The DDM service does not find x10sureIS supported disks. Check iSCSI and disk configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5169 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5169 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - In a Microsoft Failover Cluster environment a DuplexWrite RootDisk (system mirror) is not supported. [DDM_5171] | DuplexDataManager does support RootDisk (system mirror) and Microsoft Failover Cluster configurations, but not both together in a configuration. This restriction is only valid for Windows Server 2008 and newer. Please determine one configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5171 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5171 | ddm | True | Error | High | True | System |
| Warning: DuplexDataManager Service - Failed to remove the Boot Flag on the degraded RootDisk (system mirror) piece xxx. [DDM_5174] | To prevent a boot inconsistent RootDisk piece, the Boot Flag is removed. The Boot Flag will be set to active when the recover is finished. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5174 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5174 | ddm | True | Warning | Normal | True | System |
| Warning: DuplexDataManager Service - Failed to update the Boot Flag on the online RootDisk (system mirror) piece xxx. [DDM_5176] | To prevent a boot inconsistent RootDisk piece, the Boot Flag is removed. The Boot Flag will be set to active when the recover is finished. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5176 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5176 | ddm | True | Warning | Normal | True | System |
| Error: DuplexDataManager Service - Any automatic fail-safe configuration stopped. Found a newer (most recent) operating system on disk xxx. [DDM_5178] | In an x10sureIS environment a DuplexWrite group was found which holds an operating system which is most recent. If the current booted operating system (RootDisk) should further be used, please delete the newer DuplexWrite group using the DuplexDataManager MMC snap-in. If the newer (most recent) operating system should be used, please shutdown the operating system and reconfigure the boot settings. (Additional a message box is displayed on all active terminals.) | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5178 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5178 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Any automatic fail-safe configuration stopped. Found a newer (most recent) DuplexWrite data group xxx. [DDM_5179] | In an x10sureIS environment a DuplexWrite group was found which holds the newer data lun which is most recent. If the current used DuplexWrite data group should further be used, please delete the newer DuplexWrite group using the DuplexDataManager MMC snap-in. If the newer (most recent) DuplexWrite data group should be used, please stop all I/O to the older one, delete this group, adapt the drive letters and start I/O. (Additional a message box is displayed on all active terminals.) | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5179 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5179 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - The protection (change disk signature) of the xxx against the error/missing piece failed. [DDM_5180] |
x10sureIS environment:
1. Change the disk signature of the RootDisk.
2. RootDisk: Update the boot menu (BCD).
One of these actions failed.
The operation system may not be bootable!
Please open a command box and type the following three commands:
"bcdedit.exe /set {current} device partition=c:"
"bcdedit.exe /set {current} osdevice partition=c:"
"bcdedit.exe /set {bootmgr} device partition=c:"
| Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5180 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5180 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - An invalid configuration found. Found a DuplexWrite partner group xxx with 2 pieces. [DDM_5181] | In an x10sureIS environment found another DuplexWrite group with a same COD key with 2 pieces. Please the check DuplexWrite configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5181 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5181 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Delete of the xxx failed. In an x10sureIS environment one piece of the mirror is failed or missing. Therefore this piece ... [DDM_5184] | In an x10sureIS environment one piece of the mirror is failed or missing. Therefore this piece has to be deleted and the disk signature of the remaining piece has to be changed. This saves the operating system for unauthorized access to the error or missing piece. Please the check the configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5184 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5184 | ddm | True | Error | High | True | System |
| Warning: DuplexDataManager Service - In an x10sureIS installation the DuplexWrite parameter 'Autostart Recover' should be enabled. [DDM_5186] | Please enable DuplexWrite 'Autostart Recover'. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5186 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5186 | ddm | True | Warning | Normal | True | System |
| Warning: DuplexDataManager Service - The update of the bootstat.dat files failed. [DDM_5189] | In a RootDisk configuration the DDM service updates the bootstat.dat file(s). Please check your RootDisk configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5189 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5189 | ddm | True | Warning | Normal | True | System |
| Warning: DuplexDataManager Service - x10sure DuplexWrite Data Group Protection not supported! [DDM_5203] | In an x10sure environment the identity (Production Node or Control Node) is needed to protect the DuplexWrite data groups in a failover case. Please the check the configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5203 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5203 | ddm | True | Warning | Normal | True | System |
| Error: DuplexDataManager Service - Delete missing piece of partner group xxx failed. This DuplexWrite group should be prepared (deleted) for using as mirror for the DuplexWrite group yyy. [DDM_5205] | Please the check the configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5205 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5205 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Delete missing piece of partner group xxx failed. This DuplexWrite group should be prepared (deleted) for using as mirror for the DuplexWrite group yyy. [DDM_5206] | Please the check the configuration. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5206 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5206 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Any automatic fail-safe configuration stopped. The Boot Configuration Data (BCD) is not accessible. For the x10sureIS failover processing it is mandatory to access the BCD data. Please contact ... [DDM_5207] | Please the check the configuration or contact system operator immediately to solve this problem. (Additional a message box is displayed on all active terminals.) | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5207 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5207 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Any automatic fail-safe configuration stopped. The operating system is running on the disk xxx. The future mirror disk belongs to the DuplexWrite group yyy. Please solve this inconsistence. [DDM_5209] | Please use the DuplexDataManager MMC snap-in to solve this inconsistence. At least restart the DuplexDataManager service. (Additional a message box is displayed on all active terminals.) | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5209 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5209 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Any automatic fail-safe configuration stopped. The operating system is running on the disk xxx. Found the DuplexWrite group yyy on other port. Please solve this inconsistence. [DDM_5210] | Please use the DuplexDataManager MMC snap-in to solve this inconsistence. At least restart the DuplexDataManager service. (Additional a message box is displayed on all active terminals.) | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5210 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5210 | ddm | True | Error | High | True | System |
| Error: DuplexDataManager Service - Any automatic fail-safe configuration stopped. An invalid x10sure environment found. [DDM_5211] | Please check the x10sureIS environment. (Additional a message box is displayed on all active terminals.) | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5211 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5211 | ddm | True | Error | High | True | System |
| Warning: The DuplexWrite error piece xxx of the DuplexWrite group yyy is the most recent piece. Nevertheless it was set to error, because write commands were sent to the other piece, before the more recent piece appeared. If ... [DDM_5212] |
The data on the more recent piece should be overwritten:
Disable the error piece and start recover.
The data on the more recent piece should be conserved:
If it is a system disk, the system has to be rebooted, while the first piece with older data must be disconnected. (Unmap LUN or change BIOS settings etc.) If it is a data disk, you can either reboot with disconnected older piece (see above) or follow these steps: Stop applications accessing this disk - remove drive letters - disable the online piece - set the error piece to online - start recover - reassign drive letters - start applications.
(Additional a message box is displayed on all active terminals.)
| Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_5212 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 5212 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: No or invalid on disk configuration found! [DDM_6] | DDM cannot find the configuration data on this disk. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_6 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 6 | ddm | True | Warning | Normal | True | System |
| Error: DuplexDataManager MPIO event watch process - Fatal error caught in routine. [DDM_6144] | DDM WATCH PROCESS FATAL ERROR | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_6144 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 6144 | ddm | True | Error | High | True | System |
| DW PxPxTxLx: Too many SCSI ports in system! [DDM_7] | DDM supports up to 256 ports. This number is reached now. DDM will not work in this case. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_7 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 7 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: Recover aborted! [DDM_8] | While a DuplexWrite group (DW group) was recovering, this recover process was aborted. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_8 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 8 | ddm | True | Warning | Normal | True | System |
| DW PxPxTxLx: Forced to be ONLINE! [DDM_9] | This piece of a DW-Group was set from a non-online state (error, disabled, recover) to online by the driver. This may happen, if the other piece was not online too. | Fujitsu.Servers.PRIMERGY.Windows.Rules.DDM_9 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 9 | ddm | True | Warning | Normal | True | System |
| Event from Emulex FC Adapter driver [Emulex_11] | Event from Emulex FC Adapter driver. | Fujitsu.Servers.PRIMERGY.Windows.Rules.Emulex_11 | Fujitsu.Servers.PRIMERGY.Windows.Server | Alert | True | | | 0 | 0 | | True | | | True | |
| Failure (SMART) has been predicted on a hard disk [HD_MIB_10750] | Sent if a failure (SMART) has been predicted on a hard disk. SMART predicts failure on disk | Fujitsu.Servers.PRIMERGY.Windows.Rules.HD_MIB_10750 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10750 | ServerView Agents | True | Error | High | True | Application |
| Adapter link down [INTEL_ANS_11] | Adapter link down | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_11 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 11 | iANSMiniport | True | Warning | Normal | True | System |
| Adapter has been deactivated from the team [INTEL_ANS_13] | Adapter has been deactivated from the team | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_13 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 13 | iANSMiniport | True | Warning | Normal | True | System |
| The last Team adapter has lost link. Network connection has been lost [INTEL_ANS_16] | The last Team adapter has lost link. Network connection has been lost | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_16 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 16 | iANSMiniport | True | Error | High | True | System |
| Unable to allocate required resources [INTEL_ANS_2] | Unable to allocate required resources. - Free some memory resources and restart. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_2 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 2 | iANSMiniport | True | Error | High | True | System |
| Primary Adapter does not sense any Probes. Possible reason: partitioned Team [INTEL_ANS_22] | Primary Adapter does not sense any Probes. Possible reason: partitioned Team | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_22 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 22 | iANSMiniport | True | Warning | Normal | True | System |
| A Virtual Team Adapter failed to initialize [INTEL_ANS_23] | A Virtual Team Adapter failed to initialize | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_23 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 23 | iANSMiniport | True | Error | High | True | System |
| Adapter failed to join because it lacked IPSec TaskOffLoad capabilities [INTEL_ANS_24] | Adapter failed to join because it lacked IPSec TaskOffLoad capabilities | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_24 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 24 | iANSMiniport | True | Error | High | True | System |
| Adapter failed to join because it lacked TCP CheckSum TaskOffLoad capabilities [INTEL_ANS_25] | Adapter failed to join because it lacked TCP CheckSum TaskOffLoad capabilities | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_25 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 25 | iANSMiniport | True | Error | High | True | System |
| Adapter failed to join because it lacked TCP LargeSend TaskOffLoad capabilities [INTEL_ANS_26] | Adapter failed to join because it lacked TCP LargeSend TaskOffLoad capabilities | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_26 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 26 | iANSMiniport | True | Error | High | True | System |
| Adapter failed to join because of insufficient PnP capabilities [INTEL_ANS_27] | Adapter failed to join because of insufficient PnP capabilities | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_27 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 27 | iANSMiniport | True | Error | High | True | System |
| Adapter failed to join because MaxFrameSize too small [INTEL_ANS_28] | Adapter failed to join because MaxFrameSize too small | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_28 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 28 | iANSMiniport | True | Error | High | True | System |
| Adapter failed to join because MulticastList size too small [INTEL_ANS_29] | Adapter failed to join because MulticastList size too small | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_29 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 29 | iANSMiniport | True | Error | High | True | System |
| Unable to read required registry parameters [INTEL_ANS_3] | Unable to read required registry parameters. - Reconfigure the adapter team by double-clicking the PROSet icon in the control panel. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_3 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 3 | iANSMiniport | True | Error | High | True | System |
| An illegal loopback situation has occurred on the adapter [INTEL_ANS_32] | An illegal loopback situation has occurred on the adapter. - Check the configuration to verify that all the adapters in the team are connected to 802.3ad compliant switch ports. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_32 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 32 | iANSMiniport | True | Warning | Normal | True | System |
| No 802.3ad response from the link partner of any adapters in the team [INTEL_ANS_33] | No 802.3ad response from the link partner of any adapters in the team | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_33 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 33 | iANSMiniport | True | Warning | Normal | True | System |
| More than one Link Aggregation Group was found. Only one group will be functional within the team [INTEL_ANS_34] | More than one Link Aggregation Group was found. Only one group will be functional within the team | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_34 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 34 | iANSMiniport | True | Warning | Normal | True | System |
| Initializing Team with missing adapters [INTEL_ANS_35] | Initializing Team with missing adapters. - Check the configuration to verify that all the adapters are present and functioning. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_35 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 35 | iANSMiniport | True | Warning | Normal | True | System |
| Initializing Team failed. Not all base drivers have the correct MAC address, ANS ("Teaming") will not load [INTEL_ANS_36] | Initializing Team failed. Not all base drivers have the correct MAC address, ANS ("Teaming") will not load | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_36 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 36 | iANSMiniport | True | Error | High | True | System |
| The driver failed to initialize properly. You may not be able to change the virtual adapter settings [INTEL_ANS_39] | The driver failed to initialize properly. You may not be able to change the virtual adapter settings. - To resolve, reload the driver. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_39 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 39 | iANSMiniport | True | Warning | Normal | True | System |
| Unable to bind to physical adapter [INTEL_ANS_4] | Unable to bind to physical adapter. - Reconfigure the adapter team by double-clicking the PROSet icon in the control panel. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_4 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 4 | iANSMiniport | True | Error | High | True | System |
| Virtual adapter unload process may have not completed successfully. Driver may not be unloaded [INTEL_ANS_40] | Virtual adapter unload process may have not completed successfully. Driver may not be unloaded. - To resolve, reboot the system. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_40 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 40 | iANSMiniport | True | Warning | Normal | True | System |
| Adapter is improperly configured. The adapter cannot process the remote management features and be a member of an EtherChannel or 802.3ad network team at the same time [INTEL_ANS_41] | Adapter is improperly configured. The adapter cannot process the remote management features and be a member of an EtherChannel or 802.3ad network team at the same time | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_41 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 41 | iANSMiniport | True | Warning | Normal | True | System |
| Adapter is improperly configured. The adapter cannot process the remote management features and be a member of a network team at the same time [INTEL_ANS_42] | Adapter is improperly configured. The adapter cannot process the remote management features and be a member of a network team at the same time | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_42 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 42 | iANSMiniport | True | Warning | Normal | True | System |
| Adapter has been disabled in the team because its TCP Connection Offload capability was enabled. [INTEL_ANS_43] | Adapter has been disabled in the team because its TCP Connection Offload capability was enabled. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_43 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 43 | iANSMiniport | True | Error | High | True | System |
| Unable to initialize an adapter team [INTEL_ANS_5] | Unable to initialize an adapter team. - Reconfigure the adapter team by double-clicking the PROSet icon in the control panel. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_ANS_5 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5 | iANSMiniport | True | Error | High | True | System |
| Could not allocate memory for receive structures [INTEL_E1000_10] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_10 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10 | | True | Error | High | True | System |
| Could not allocate memory for receive descriptors [INTEL_E1000_11] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_11 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 11 | | True | Error | High | True | System |
| Could not allocate memory for receive buffers [INTEL_E1000_12] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_12 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 12 | | True | Error | High | True | System |
| Could not establish link [INTEL_E1000_13] | Warning message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_13 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 13 | | True | Warning | Normal | True | System |
| The PCI BIOS has NOT properly configured the PRO/1000 adapter [INTEL_E1000_14] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_14 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 14 | | True | Error | High | True | System |
| The PCI BIOS has NOT properly configured the PRO/1000 adapter [INTEL_E1000_15] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_15 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 15 | | True | Error | High | True | System |
| The PCI BIOS has NOT properly configured the PRO/1000 adapter [INTEL_E1000_16] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_16 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 16 | | True | Error | High | True | System |
| The PCI BIOS has NOT properly configured the PRO/1000 adapter [INTEL_E1000_17] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_17 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 17 | | True | Error | High | True | System |
| The PRO/1000 adapter was not configured for bus mastering by the PCI BIOS [INTEL_E1000_18] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_18 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 18 | | True | Error | High | True | System |
| Could not allocate the NDIS receive packets necessary for operation [INTEL_E1000_19] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_19 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 19 | | True | Error | High | True | System |
| Could not allocate the NDIS receive buffers necessary for operation [INTEL_E1000_20] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_20 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 20 | | True | Error | High | True | System |
| The OS was unable to assign PCI resources to the PRO/1000 adapter [INTEL_E1000_21] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_21 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 21 | | True | Error | High | True | System |
| The driver was unable to claim PCI resources of this PRO/1000 adapter [INTEL_E1000_22] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_22 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 22 | | True | Error | High | True | System |
| The EEPROM on your PRO/1000 adapter may have errors [INTEL_E1000_23] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_23 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 23 | | True | Error | High | True | System |
| Could not start the PRO/1000 adapter [INTEL_E1000_24] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_24 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 24 | | True | Error | High | True | System |
| MDIX setting conflict with the AutoNeg Settings [INTEL_E1000_25] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_25 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 25 | | True | Warning | Normal | True | System |
| Link has been disconnected [INTEL_E1000_27] | Warning message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_27 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 27 | | True | Warning | Normal | True | System |
| Could not start the gigabit network connection [INTEL_E1000_29] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_29 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 29 | | True | Error | High | True | System |
| Link is set up for auto-negotiation but the link partner is not configured for auto-negotiation [INTEL_E1000_30] | Warning message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_30 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 30 | | True | Warning | Normal | True | System |
| Could not allocate all resources necessary for the high priority transmit queue [INTEL_E1000_37] | Warning message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_37 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 37 | | True | Warning | Normal | True | System |
| The driver failed to initialize properly [INTEL_E1000_38] | Warning message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_38 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 38 | | True | Warning | Normal | True | System |
| Adapter unload process may have not completed successfully [INTEL_E1000_39] | Warning message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_39 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 39 | | True | Warning | Normal | True | System |
| Could not find a PRO/1000 adapter [INTEL_E1000_4] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_4 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 4 | | True | Error | High | True | System |
| Driver could not determine which PRO/1000 adapter to load on [INTEL_E1000_5] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_5 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 5 | | True | Error | High | True | System |
| Could not allocate the MAP REGISTERS necessary for operation [INTEL_E1000_6] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_6 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 6 | | True | Error | High | True | System |
| Could not assign an interrupt for the PRO/1000 [INTEL_E1000_7] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_7 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 7 | | True | Error | High | True | System |
| Could not allocate memory necessary for operation [INTEL_E1000_8] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8 | | True | Error | High | True | System |
| Could not find a supported gigabit network connection [INTEL_E1000_8196] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8196 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8196 | | True | Error | High | True | System |
| Driver could not determine which supported gigabit network connection to load on [INTEL_E1000_8197] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8197 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8197 | | True | Error | High | True | System |
| Could not allocate the MAP REGISTERS necessary for operation [INTEL_E1000_8198] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8198 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8198 | | True | Error | High | True | System |
| Could not assign an interrupt for the supported gigabit network connection [INTEL_E1000_8199] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8199 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8199 | | True | Error | High | True | System |
| Could not allocate memory necessary for operation [INTEL_E1000_8199] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8200 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8200 | | True | Error | High | True | System |
| Could not allocate shared memory necessary for operation [INTEL_E1000_8201] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8201 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8201 | | True | Error | High | True | System |
| Could not allocate memory for receive structures [INTEL_E1000_8202] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8202 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8202 | | True | Error | High | True | System |
| Could not allocate memory for receive descriptors [INTEL_E1000_8203] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8203 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8203 | | True | Error | High | True | System |
| Could not allocate memory for receive buffers [INTEL_E1000_8204] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8204 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8204 | | True | Error | High | True | System |
| Could not establish link [INTEL_E1000_8205] | Warning message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8205 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 8205 | | True | Warning | Normal | True | System |
| The PCI BIOS has NOT properly configured the gigabit network connection [INTEL_E1000_8206] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8206 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8206 | | True | Error | High | True | System |
| The PCI BIOS has NOT properly configured the gigabit network connection [INTEL_E1000_8207] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8207 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8207 | | True | Error | High | True | System |
| The PCI BIOS has NOT properly configured the gigabit network connection [INTEL_E1000_8208] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8208 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8208 | | True | Error | High | True | System |
| The PCI BIOS has NOT properly configured the gigabit network connection [INTEL_E1000_8209] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8209 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8209 | | True | Error | High | True | System |
| The gigabit network connection was not configured for bus mastering by the PCI BIOS [INTEL_E1000_8210] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8210 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8210 | | True | Error | High | True | System |
| Could not allocate the NDIS receive packets necessary for operation [INTEL_E1000_8211] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8211 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8211 | | True | Error | High | True | System |
| Could not allocate the NDIS receive buffers necessary for operation [INTEL_E1000_8212] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8212 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8212 | | True | Error | High | True | System |
| The OS was unable to assign PCI resources to the gigabit network connection [INTEL_E1000_8213] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8213 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8213 | | True | Error | High | True | System |
| The driver was unable to claim PCI resources of this gigabit network connection [INTEL_E1000_8214] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8214 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8214 | | True | Error | High | True | System |
| The EEPROM on your gigabit network connection may have errors [INTEL_E1000_8215] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8215 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8215 | | True | Error | High | True | System |
| Could not start the gigabit network connection [INTEL_E1000_8216] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8216 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 8216 | | True | Error | High | True | System |
| MDIX setting conflict with the AutoNeg Settings. MDIX will not work [INTEL_E1000_8217] | Warning message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_8217 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 8217 | | True | Warning | Normal | True | System |
| Could not allocate shared memory necessary for operation [INTEL_E1000_9] | Error message of driver of Intel LAN Adapter PRO1000XT, PRO1000XF, PRO1000MT Desktop, PRO1000MT Dual, PRO1000MT, PRO1000P and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E1000_9 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 9 | | True | Error | High | True | System |
| Adapter Link Down [INTEL_E100B_4] | Warning message of driver of Intel LAN Adapter PRO100S Dual, PRO100S Server, PRO100 Server and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E100B_4 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 4 | E100B | True | Warning | Normal | True | System |
| Hardware failure detected [INTEL_E100B_6] | Error message of driver of Intel LAN Adapter PRO100S Dual, PRO100S Server, PRO100 Server and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E100B_6 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 6 | E100B | True | Error | High | True | System |
| EEPROM corruption detected [INTEL_E100B_7] | Error message of driver of Intel LAN Adapter PRO100S Dual, PRO100S Server, PRO100 Server and Intel onboard LAN | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_E100B_7 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 7 | E100B | True | Error | High | True | System |
| The EEPROM on the network adapter may be corrupt. [INTEL_IE10G_23] | The EEPROM on the network adapter may be corrupt. - Visit "http://www.intel.com/p/en_US/support/network/" for assistance. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_23 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 23 | | True | Error | High | True | System |
| Unable to start the network adapter. [INTEL_IE10G_24] | Unable to start the network adapter. - Install the latest driver from "http://www.intel.com/p/en_US/support/network/". | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_24 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 24 | | True | Error | High | True | System |
| Unable to start the network adapter. [INTEL_IE10G_25] | Unable to start the network adapter. - Install the latest driver from "http://www.intel.com/p/en_US/support/network/". | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_25 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 25 | | True | Error | High | True | System |
| Network link is disconnected. [INTEL_IE10G_27] | Network link is disconnected. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_27 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 27 | | True | Warning | Normal | True | System |
| The network adapter is configured for auto-negotiation but the link partner is not. This may result in a duplex mismatch. [INTEL_IE10G_30] | The network adapter is configured for auto-negotiation but the link partner is not. This may result in a duplex mismatch. - Configure the link partner for auto-negotiation. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_30 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 30 | | True | Warning | Normal | True | System |
| PCI Express bandwidth available for this adapter is not sufficient for optimal performance. [INTEL_IE10G_37] | PCI Express bandwidth available for this adapter is not sufficient for optimal performance. - Move the adapter to a x8 PCI Express slot. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_37 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 37 | | True | Error | High | True | System |
| The driver failed to initialize properly. You may not be able to change the adapter settings. [INTEL_IE10G_38] | The driver failed to initialize properly. You may not be able to change the adapter settings. - Install the latest driver from "http://www.intel.com/p/en_US/support/network/" and restart the computer. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_38 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 38 | | True | Warning | Normal | True | System |
| The network adapter driver did not unload successfully. [INTEL_IE10G_39] | The network adapter driver did not unload successfully. - Install the latest driver from "http://www.intel.com/p/en_US/support/network/" and restart the computer. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_39 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 39 | | True | Warning | Normal | True | System |
| Could not allocate shared memory necessary for operation. [INTEL_IE10G_43] | Could not allocate shared memory necessary for operation. - Select the adapter in the network control panel. Click properties. Reduce the number of transmit and receive descriptors, then restart. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_43 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 43 | | True | Error | High | True | System |
| Could not allocate memory necessary for operation. [INTEL_IE10G_44] | Could not allocate memory necessary for operation. - Select the adapter in the network control panel. Click properties. Reduce the number of transmit and receive descriptors, then restart. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_44 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 44 | | True | Error | High | True | System |
| Could not allocate a resource pool necessary for operation. [INTEL_IE10G_45] | Could not allocate a resource pool necessary for operation. - Select the adapter in the network control panel. Click properties. Reduce the number of transmit and receive descriptors, then restart. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_45 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 45 | | True | Error | High | True | System |
| Could not initialize scatter-gather DMA resources necessary for operation. [INTEL_IE10G_46] | Could not initialize scatter-gather DMA resources necessary for operation. - Select the adapter in the network control panel. Click properties. Reduce the number of transmit descriptors and restart. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_46 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 46 | | True | Error | High | True | System |
| Could not map the network adapter flash. [INTEL_IE10G_47] | Could not map the network adapter flash. - Install the latest driver from "http://www.intel.com/p/en_US/support/network/". (Or) Try another slot. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_47 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 47 | | True | Error | High | True | System |
| The fan on the network adapter has failed. [INTEL_IE10G_48] | The fan on the network adapter has failed. - Power off the machine and replace the network adapter. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_48 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 48 | | True | Error | High | True | System |
| The driver was unable to load due to an unsupported SFP+ module installed in the adapter. [INTEL_IE10G_49] | The driver was unable to load due to an unsupported SFP+ module installed in the adapter. - Replace the module. (Or) Install the latest driver from "http://www.intel.com/p/en_US/support/network/". | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_49 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 49 | | True | Error | High | True | System |
| The network adapter has been stopped because it has overheated. [INTEL_IE10G_50] | The network adapter has been stopped because it has overheated. - Restart the computer. If the problem persists, power off the computer and replace the network adapter. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_50 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 50 | | True | Error | High | True | System |
| Unable to allocate the map registers necessary for operation. [INTEL_IE10G_6] | Unable to allocate the map registers necessary for operation. - Select the adapter in the network control panel. Click properties. Reduce the number of transmit descriptors and restart. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_6 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 6 | | True | Error | High | True | System |
| Unable to allocate the map registers necessary for operation. [INTEL_IE10G_7] | Unable to allocate the map registers necessary for operation. - Select the adapter in the network control panel. Click properties. Reduce the number of transmit descriptors and restart. | Fujitsu.Servers.PRIMERGY.Windows.Rules.INTEL_IE10G_7 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 7 | | True | Error | High | True | System |
| SNMP cannot access cluster software [NTCLUSTER_MIB_10810] | The SNMP agent started but could not communicate with the cluster service | Fujitsu.Servers.PRIMERGY.Windows.Rules.NTCLUSTER_MIB_10810 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10810 | ServerView Agents | True | Error | High | True | Application |
| SNMP lost access to the cluster software [NTCLUSTER_MIB_10812] | The SNMP agent has lost communication with the cluster service | Fujitsu.Servers.PRIMERGY.Windows.Rules.NTCLUSTER_MIB_10812 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10812 | ServerView Agents | True | Error | High | True | Application |
| The node has changed its state [NTCLUSTER_MIB_10832] | A cluster node has changed its state | Fujitsu.Servers.PRIMERGY.Windows.Rules.NTCLUSTER_MIB_10832 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10832 | ServerView Agents | True | Error | High | True | Application |
| Group has changed its state [NTCLUSTER_MIB_10852] | A resource group has changed its state | Fujitsu.Servers.PRIMERGY.Windows.Rules.NTCLUSTER_MIB_10852 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10852 | ServerView Agents | True | Error | High | True | Application |
| Resource has changed its state [NTCLUSTER_MIB_10862] | A cluster resource has changed its state | Fujitsu.Servers.PRIMERGY.Windows.Rules.NTCLUSTER_MIB_10862 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10862 | ServerView Agents | True | Error | High | True | Application |
| Network has changed its state [NTCLUSTER_MIB_10912] | A Network has changed its state | Fujitsu.Servers.PRIMERGY.Windows.Rules.NTCLUSTER_MIB_10912 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10912 | ServerView Agents | True | Error | High | True | Application |
| Network interface has changed its state [NTCLUSTER_MIB_10922] | A network interface has changed its state | Fujitsu.Servers.PRIMERGY.Windows.Rules.NTCLUSTER_MIB_10922 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10922 | ServerView Agents | True | Error | High | True | Application |
| Cluster group has failed [NTCLUSTER_MIB_10932] | A cluster resource group has failed | Fujitsu.Servers.PRIMERGY.Windows.Rules.NTCLUSTER_MIB_10932 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10932 | ServerView Agents | True | Error | High | True | Application |
| Cluster resource has failed [NTCLUSTER_MIB_10935] | A cluster resource has failed | Fujitsu.Servers.PRIMERGY.Windows.Rules.NTCLUSTER_MIB_10935 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10935 | ServerView Agents | True | Error | High | True | Application |
| Cluster network unavailable [NTCLUSTER_MIB_10938] | A cluster network is unavailable | Fujitsu.Servers.PRIMERGY.Windows.Rules.NTCLUSTER_MIB_10938 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10938 | ServerView Agents | True | Error | High | True | Application |
| Cluster network interface has failed [NTCLUSTER_MIB_10940] | A cluster network interface has failed | Fujitsu.Servers.PRIMERGY.Windows.Rules.NTCLUSTER_MIB_10940 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10940 | ServerView Agents | True | Error | High | True | Application |
| Cluster network interface unreachable [NTCLUSTER_MIB_10941] | A cluster network interface is unreachable | Fujitsu.Servers.PRIMERGY.Windows.Rules.NTCLUSTER_MIB_10941 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10941 | ServerView Agents | True | Error | High | True | Application |
| Cluster network interface unavailable [NTCLUSTER_MIB_10942] | A cluster network interface is unavailable | Fujitsu.Servers.PRIMERGY.Windows.Rules.NTCLUSTER_MIB_10942 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 10942 | ServerView Agents | True | Error | High | True | Application |
| Error Event from QLogic FC Adapter driver [QL2300_11] | Error Event from QLogic FC Adapter driver 'ql2300'. Detail event code is 4001xxxx, 4002xxxx, etc. | Fujitsu.Servers.PRIMERGY.Windows.Rules.QL2300_11 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 0 | | True | Error | High | True | System |
| Driver Monitoring detected a warning event [SC2_MIB_12151] | Driver Monitoring detected a warning event | Fujitsu.Servers.PRIMERGY.Windows.Rules.SC2_MIB_12151 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 12151 | ServerView Agents | True | Warning | Normal | True | Application |
| Driver Monitoring detected an error event [SC2_MIB_12152] | Driver Monitoring detected an error event | Fujitsu.Servers.PRIMERGY.Windows.Rules.SC2_MIB_12152 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 12152 | ServerView Agents | True | Error | High | True | Application |
| Unable to connect to WMI. [SVISCOM_VBS_110] | A VBscript was unable to connect to WMI: /root/default:StdRegProv. | Fujitsu.Servers.PRIMERGY.Windows.Rules.SVISCOM_VBS_110 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 110 | Health Service Script | True | Error | High | True | Operations Manager |
| Unsupported ServerView Agents version. [SVISCOM_VBS_111] | A VBscript found ServerView Agents installed, but the version installed is not supported. See Remark for old HW in knowledge base article! | Fujitsu.Servers.PRIMERGY.Windows.Rules.SVISCOM_VBS_111 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 116 | Health Service Script | True | Warning | Normal | True | Operations Manager |
| SCCI interface not supported. [SVISCOM_VBS_120] | The SCCI 'RSwitch' COM object could not be created. This object is used to communicate with the agents. | Fujitsu.Servers.PRIMERGY.Windows.Rules.SVISCOM_VBS_120 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 121 | Health Service Script | True | Warning | Normal | True | Operations Manager |
| WMI class returned invalid data. [SVISCOM_VBS_130] |
A VBscript tried to access a WMI class, which returned invalid data:
{0}
| Fujitsu.Servers.PRIMERGY.Windows.Rules.SVISCOM_VBS_130 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 113 | Health Service Script | True | Error | High | True | Operations Manager |
| Error retrieving FC events. [SVISCOM_VBS_192] | The VBscript 'PRIMERGYFCEvents.vbs' tried to retrieve FC events from WMI but got invalid data. | Fujitsu.Servers.PRIMERGY.Windows.Rules.SVISCOM_VBS_192 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 192 | Health Service Script | True | Error | High | True | Operations Manager |
| New PRIMERGY Server components detected [SVISCOM_VBS_200] |
Detected new components for a PRIMERGY Server:
'{0}'
| Fujitsu.Servers.PRIMERGY.Windows.Rules.SVISCOM_VBS_200 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 200 | Health Service Script | True | Information | Low | True | Operations Manager |
| PRIMERGY Server Components are missing [SVISCOM_VBS_250] |
Could not detect all known components for a PRIMERGY Server:
'{0}'
| Fujitsu.Servers.PRIMERGY.Windows.Rules.SVISCOM_VBS_250 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 250 | Health Service Script | True | Error | High | True | Operations Manager |
| The configured threshold has been exceeded [THRESHOLD_MIB_12200] | Threshold exceeded at server. The rule (rule) met condition with value (value). | Fujitsu.Servers.PRIMERGY.Windows.Rules.THRESHOLD_MIB_12200 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 12200 | ServerView Agents | True | Error | High | True | Application |
| The configured threshold has been exceeded [THRESHOLD_MIB_12201] | Threshold exceeded at server. The rule (rule) met condition with value (value). | Fujitsu.Servers.PRIMERGY.Windows.Rules.THRESHOLD_MIB_12201 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | True | | | 0 | 12201 | ServerView Agents | True | Error | High | True | Application |
| The configured threshold has been exceeded [THRESHOLD_MIB_12202] | Threshold exceeded at server. The rule (rule) met condition with value (value). | Fujitsu.Servers.PRIMERGY.Windows.Rules.THRESHOLD_MIB_12202 | Fujitsu.Servers.PRIMERGY.Windows.Server | EventCollection | False | | | 0 | 12202 | ServerView Agents | True | Warning | Normal | True | Application |
Home