NIC Teaming failed. Redundancy has been reduced by a NIC.
NIC Teaming has failed.
This could be caused by the following:
This trap will be sent any time a physical adapter in a logical adapter group changes to the Failed condition, but at least one physical adapter remains in the OK condition. This can be caused by loss of link due to a cable being removed from the adapter or the Hub or Switch. Internal adapter, Hub, or Switch failures can also cause this condition.
Check the cables to the adapter and the Hub or Switch. If no cable problems are found, the adapter, Hub, or Switch may need replacement.
For additional troubleshooting, the following tasks are available:
HPE System Management Homepage
HPE Integrated Lights-Out
The following are monitored NT Event Log entries by this rule:
Event ID | Publisher | Log Message |
---|---|---|
1283 | NIC Agents | NIC Agent: Redundancy has been reduced by the NIC in slot %1, port %2. Number of functional NICs in the team: %3. |
1287 | NIC Agents | NIC Agent: Redundancy has been reduced by the NIC in slot %1, port %2. Number of functional NICs in the team: %3. |
1293 | NIC Agents | NIC Agent: Redundancy has been reduced by the NIC in slot %1, port %2. Number of functional NICs in the team: %3. |
See the latest information about HPE ProLiant Management Packs:
Insight Control for Microsoft System Center documentation
HPE ProLiant Servers SNMP Management Pack
Target | HewlettPackard.Servers.ProLiant.SNMP.HPProLiantSNMPServerNetworks |
Category | Alert |
Enabled | True |
Event Source | NIC Agents |
Alert Generate | True |
Alert Severity | Error |
Alert Priority | High |
Remotable | True |
Event Log | System |
Comment | Mom2005ID='{D38C666E-79A7-4413-B671-224B846184E5}' |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
_907D4578_146C_11D3_AB21_00A0C98620CE_ | DataSource | Microsoft.Windows.EventProvider | Default |
GenerateAlert | WriteAction | System.Health.GenerateAlert | Default |
<Rule ID="HewlettPackard.Servers.ProLiant.SNMP.NIC_Teaming_failed._5_Rule" Target="HewlettPackard.Servers.ProLiant.SNMP.HPProLiantSNMPServerNetworks" Enabled="true" Comment="Mom2005ID='{D38C666E-79A7-4413-B671-224B846184E5}'">
<Category>Alert</Category>
<DataSources>
<DataSource ID="_907D4578_146C_11D3_AB21_00A0C98620CE_" Comment="{907D4578-146C-11D3-AB21-00A0C98620CE}" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</ComputerName>
<LogName>System</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>NIC Agents</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<RegExExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>MatchesMOM2005BooleanRegularExpression</Operator>
<Pattern>^(1283|1287|1293)$</Pattern>
</RegExExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>2</Priority>
<Severity>2</Severity>
<AlertName>HPE Windows (SNMP) NIC Teaming failed.</AlertName>
<AlertDescription>$Data/EventDescription$</AlertDescription>
<AlertOwner/>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>