This monitor catches Xian events that notifies when the Failed reassembly requests if has changed its state.
Failed reassembly requests are over threshold.
The number of failing reassembly requests is above the maximum threshold configured in Xian Network Manager.
www.jalasoft.com/KnowledgeBase
If the count is at a suspect level, there might be a capacity problem; however, this is not necessarily a count of discarded IP fragments.
Verify that the threshold is set at a reasonable value. It is also possible to design an internal network to avoid fragmentation and the subsequent reassembly requirement.
Monitors the number of reassembly requests that have failed on a Cisco Nexus.
Target | Jalasoft.Xian.Common.Types.ThirdParty.Cisco.JsXCiscoNexusInterfaceElementContainer | ||
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 |
|
<AggregateMonitor ID="Jalasoft.Xian.SmartManagementPacks.CiscoNexus.FailedReassemblyRequests.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_Cisco!Jalasoft.Xian.Common.Types.ThirdParty.Cisco.JsXCiscoNexusInterfaceElementContainer" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="FailedReassemblyRequests_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>