Cisco Wireless: Port duplex status Health Monitor

Jalasoft.Xian.SmartManagementPacks.CiscoWireless.PortDuplexStatus.2.1 (AggregateMonitor)

This monitor catches Xian events that notifies when the Port duplex status has changed its state.

Knowledge Base article:

Summary

Port duplex status (4000/4500/5000/6000/6500) has changed.

The port duplex status has changed to one of the following states: half duplex, full duplex, disagree, auto-duplex.

Causes

A fixed status may be causing performance issues (e.g. when one port on the link operates at half-duplex while the other port operates at full-duplex), or the port could not agree with the far end on a link protocol.

Resolutions

Auto-negotiation is recommended for best performance. The fixed status can be reconfigured to avoid mismatch. If the port could not agree with the far end on a link protocol, its operational status does not agree either and the link must be checked.

Additional

Monitors port duplex status on Cisco Wireless Catalyst 4000/4500/5000/6000/6500 series.

Element properties:

Target

Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXCiscoWirelessModulePortElement

Parent Monitor

System.Health.PerformanceState

Algorithm

WorstOf

Category

StateCollection

Enabled

True

Alert Generate

True

Alert Severity

MatchMonitorHealth

Alert Priority

Low

Alert Auto Resolve

True

Remotable

True

Accessibility

Public

Alert Message

Port duplex status Alert

{0}

Source Code:

<AggregateMonitor ID="Jalasoft.Xian.SmartManagementPacks.CiscoWireless.PortDuplexStatus.2.1" Accessibility="Public" Enabled="true" Target="ThirdParty_Cisco!Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXCiscoWirelessModulePortElement" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">

  <Category>StateCollection</Category>

  <AlertSettings AlertMessage="PortDuplexStatus_AlertMessage">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Low</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/Params/Param[3]$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <Algorithm>WorstOf</Algorithm>

</AggregateMonitor>