Cisco VPN Concentrator: Session status Health Monitor

Jalasoft.Xian.SmartManagementPacks.CiscoVPN.SessionStatus.1.2 (AggregateMonitor)

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

Knowledge Base article:

Summary

Session status has changed.

The session status has changed to one of the following states: active or not active.

Causes

Malfunction or lack of connectivity may change the session status from active to not active. Some applications that establish a TCP connection can stay up indefinitely without passing data to these tunnels that have been unused for a long time. Security appliance times out these sessions without indicating a reason. Before releasing 4.0.2, when attempting to delete a file from an FTP session into VPN 3000 Concentrator, it fails and terminates the FTP session.

Resolutions

Active is the desired state. If the state has changed to "not active" without an intended purpose, monitor the sessions and check for connectivity or malfunction in the VPN Concentrator.

Additional

Monitors the status of different sessions on the VPN Concentrator.

Element properties:

TargetJalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXSessionRemoteAccessElement
Parent MonitorSystem.Health.PerformanceState
AlgorithmWorstOf
CategoryStateCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityLow
Alert Auto ResolveTrue
RemotableTrue
AccessibilityPublic
Alert Message
Session status Alert
{0}

Source Code:

<AggregateMonitor ID="Jalasoft.Xian.SmartManagementPacks.CiscoVPN.SessionStatus.1.2" Accessibility="Public" Enabled="true" Target="ThirdParty_Cisco!Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXSessionRemoteAccessElement" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="SessionStatus_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>