This monitor catches Xian events that notifies when the Session connection time has changed its state.
Session connection time is over/under threshold.
Over threshold: The total number of hours of session connection time is above the maximum threshold configured in Xian Network Manager 2012.
Under threshold: The total number of hours of session connection time is below the minimum threshold configured in Xian Network Manager 2012.
Over threshold: The total amount of session time connected is above your set value. If your VPN session has been inactive for 30 minutes, it automatically terminates. Commonly, your connection automatically terminates after 8 hours of continuous connection time (it depends on the maximum connect timeout value configured). You can have only one VPN session per username open at a time, if you try to open a second session, either from the same computer or from a different one, the second logon attempt will fail.
Under threshold: The total amount of session time connected is below your set value. If your VPN session has been inactive for 30 minutes, it automatically terminates. Commonly, your connection automatically terminates after 8 hours of continuous connection time (it depends the maximum connect timeout value configured). You can have only one VPN session per username open at a time, if you try to open a second session, either from the same computer or from a different one, the second logon attempt will fail.
Over threshold: Monitor session, check the threshold set to reflect management requirements. If your connection has been active during this 8-hour period, it will self-terminate. If this happens, or your session terminates due to inactivity, you can reconnect in both cases. If you find your connection is frequently terminated before 30 minutes of inactivity have elapsed, you might need to increase the VPN timeout period.
Under threshold: Monitor session, check the threshold set to reflect management requirements. If your connection has been active during this 8-hour period, it will self-terminate. If this happens, or your session terminates due to inactivity, you can reconnect in both cases. If you find your connection is frequently terminated before 30 minutes of inactivity have elapsed, you might need to increase the VPN timeout period.
Monitors the connection time of a VPN Concentrator session.
| Target | Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXSessionLanToLanElement | ||
| 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 |
|
Home<AggregateMonitor ID="Jalasoft.Xian.SmartManagementPacks.CiscoVPN.SessionConnectionTime.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_Cisco!Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXSessionLanToLanElement" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="SessionConnectionTime_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>