Cisco VPN Concentrator: Active session count Health Monitor

Jalasoft.Xian.SmartManagementPacks.CiscoVPN.ActiveSessionCount.1.1 (AggregateMonitor)

This monitor catches Xian events that notifies when the Active session count has changed its state.

Knowledge Base article:

Summary

Active session count is over threshold.

The number of active sessions is above the maximum threshold configured in Xian Network Manager 2012.

Causes

The maximum number of concurrently active sessions allowed on the VPN Concentrator is presented by default for configuration and the situation may reflect network requirement.

Resolutions

If you have limited the number of sessions below default, the VPN Concentrator will not accept additional sessions of any type, so you need to verify configuration. Otherwise, consider upgrading or replacement. Different VPN Concentrator models are used for different numbers of users. For example the clientless sessions, consider that while Cisco VPN 3005 supports 50 clientless sessions, Cisco VPN 3015 support 75 clientless sessions and Cisco VPN 3030,3060 and 3080 support 500 clientless sessions.

Additional

Monitors the total number of active sessions in the VPN Concentrator.

Element properties:

TargetJalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXCiscoVpnConcSnmpDeviceElement
Parent MonitorSystem.Health.PerformanceState
AlgorithmWorstOf
CategoryStateCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityLow
Alert Auto ResolveTrue
RemotableTrue
AccessibilityPublic
Alert Message
Active session count Alert
{0}

Source Code:

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