270 likes | 410 Views
Enterprise Edition Course 7000. Enterprise Management & Troubleshooting. Topics. Cardholder Management User Replication Access Level Assignment Regional Badge ID Allocation Failed Transactions Multi-Region Alarm Monitoring RMS And System Add-ons. Cardholder Replication.
E N D
Enterprise Edition Course 7000 Enterprise Management & Troubleshooting CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Topics Cardholder Management User Replication Access Level Assignment Regional Badge ID Allocation Failed Transactions Multi-Region Alarm Monitoring RMS And System Add-ons CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Cardholder Replication • Selectable when adding/modifying cardholder record at a Region • All Regions • Local Region Only • New cardholders created at the Master Server are set for ‘All Regions’ and are not selectable • Default replication is set per Badge Type • Can only be set at the Master Server • Allows limiting ‘Edit’ permissions CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Replication Permissions Removing ‘Edit’ Permissions will prevent users from “stealing” All Regions cardholders CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Default Replication Default replication for cardholders must then be set per badge type at the Master CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Enterprise Access Level Assignment • Cardholder and Badge records may be created at the Master Server • Create an <All Segments - Master - Recursive> access group from the Master Server • Add access levels from each region to an Access Group • Assign the group to a Badge Type to be used at all regions • Regional Access Group may be assigned at the region as well CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Prevent Duplicate Badge IDs • Badge ID allocation ranges can be assigned on a per Region basis • Allocation done at Master • Allows a distinct range to be assigned per server • May prevent badges from being added at a particular region (based on Badge Type ID allocation) • Prevents failed transactions based on Badge ID CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Regional Badge ID Allocation CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Edit Badge ID • The ability to edit badge ID has been re-established • The ability to edit the badge ID was disabled in 6.1.222 • Feature now available for 6.1.222 by installing HF 2.1 CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Failed Transactions Duplicate Badge IDs entered at separate Regions will result in a failed transaction at the Parent CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Failed Transactions Select Transaction (checkmark) and right mouse click Select ‘Launch Failed Transaction Recovery Wizard’ CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Failed Transactions • Other examples include: • Duplicate Cardholder • Based on Cardholder ID or SSN • Unexpected/Unknown • Caused when “parent” object is not in database. For example, adding a badge when cardholder is missing or adding an access level if badge is missing • Visit not on Source • Caused when visit information has been archived off prior to being replicated to Master server • Resolve by deleting failed transaction • Adjust ‘Visit’ archive settings (at least 30 days is recommended) CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Multi-Region Alarm Monitoring • Multi-Region Alarm Monitoring • Applicable to all Enterprise customers • Not dependant on multi-level implementation and does not require a license • Uses Monitor Zones that include hardware from multiple regions • Alarms from multiple Regions can be monitored within single Alarm Monitoring instance • Requires login to a Region at a level inclusive of all hardware you want to monitor • Master Server login allows system-wide monitoring • Name resolution to necessary communication servers is required (Does not use ODBC) CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Multi-Region Alarm Monitoring CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Multi-Region Alarm Monitoring CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Enterprise LS Services • LS Replicator on each regional server • Only one per Region • Uploads to /Downloads from Master • LS Linkage Server service at each Region • Only one per Region (configured under System Options) • Triggers the schedule • LS ID Allocation service • One per Enterprise System • Intended to be installed on Master CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
OnGuard Log Files Enterprise related log files (.txt files) are located in: C:\Program Files\OnGuard\Logs Log files include: Replicator ReplicatorSys ReplicatorUpDown ReplicatorUp CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Enterprise Administrative Tasks • Use the Replication Administration program to check • Replicator Schedule • Replicator Status • Enterprise Transactions (DAILY!) • Master • Regions CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
What is RMS? • Remote Managed Services • Preventative maintenance and diagnostic services designed to compliment OnGuard VARS in their efforts in keeping user’s system running at peak performance. • In-house department designed to: • Partner with VAR to support System User • Maintain and optimize System User’s OnGuard systems • Annual contract engagements available through VARS - customizable to meet specific needs • Basic (32ES) to Enterprise level systems CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
RMS • Services • Dedicated remote Enterprise/System Specialists assist with routine maintenance tasks. • Proactive Forum between Lenel, VAR and System User (Security, IT, DBAs) on a recurring basis • Advice on business practices to maximize productivity and reliability of OnGuard system • Plan software upgrades/new feature implementations CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Maintenance • Enterprise Transaction clean up and analysis • Database Maintenance – data counts/backup monitoring • Interested? • Contact Lenel RMS team for details CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
High Availability Systems • Microsoft Clustering • Windows Server 2003 Enterprise Edition SP2/R2 • NEC ExpressCluster Version 1.0 • Oracle 10g Server • NEC ExpressCluster Version 1.0 • Microsoft SQL Server 2005 Standard Edition CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
NEC FT Monitoring Service • The Lenel NEC Fault Tolerant (FT) Server Monitoring Service • A Windows Service designed to monitor changes in hardware and network status on NEC Fault Tolerant servers • Status changes include hardware removal, disconnect, malfunction, or failed diagnostics • Will monitor for these conditions and will send an alarm for each failure to Alarm Monitoring as well as send an e-mail message detailing the status change. CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Licensing • For OnGuard 6.1 • Licensing is controlled internally • Licensing for OnGuard 6.1 and earlier • Requires a license file through Lenel’s Custom Solutions department • Note: To obtain this license, send an e-mail to cs@lenel.com with the MAC address of the server where the NEC FT Server Monitoring service will run, typically the Lenel application server CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
NEC ExpressCluster Monitoring Service Add-On • The NEC ExpressCluster Monitoring Service Add-on • A Windows Service designed to monitor changes in hardware and network status on servers clustered using NEC ExpressCluster software • Status changes include inter-connect network connection failures, disk mirroring failures, critical ExpressCluster service crashes, and all other events that ExpressCluster reports to the Windows Event Viewer • Will monitor for these conditions and sends an alarm for each failure to Alarm Monitoring as well as sending an e-mail notification detailing the status change CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Licensing • For OnGuard 6.3 and later: One instance of the license feature “NEC Express Cluster Monitoring” is required • For OnGuard 6.1 and earlier: Licensing is controlled internally. Licensing for OnGuard 6.1 and earlier requires a license file through Lenel’s Custom Solutions department • Note: To obtain this license, send an e-mail to cs@lenel.com with the MAC addresses from both the primary and secondary servers CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)
Summary Cardholder Management User Replication Access Level Assignment Regional Badge ID Allocation Failed Transactions Multi-Region Alarm Monitoring RMS And System Add-ons CR7000 - M06.01 - 6.4.500 TU 1 (Ent Mgmt and T-Shooting)