Contents
Guide for System Center Management Pack for File Server 2012R2 4
Management Pack Purpose 6
Monitoring Scenarios 6
How Health Rolls Up 16
Configuring the Management Pack File Server 2012R2 16
Links 17
Appendix: Management Pack Contents 19
Guide for System Center Management Pack for File Server 2012R2
This guide was written based on version 2017 of the Management Pack for File Server 2012
Guide History
Changes in Version
This version of Management Pack for File Server 2012 R2 includes the following changes:
Deduplication
FSRM
NFS
SMB
Supported Configurations
This management pack requires System Center 2012 Operations Manager or later.
The following table details the supported configurations for the Management Pack for File Server 2012 R2:
|
DeDUP
|
FSRM
|
iSCSI
|
NFS
|
SMB
|
Work Folders
|
Configuration
|
Support
|
|
Windows Server 2012 R2 – Standard/Datacenter
|
X
|
X
|
X
|
X
|
X
|
X
|
Windows Storage Server 2012R2
|
X
|
X
|
X
|
X
|
X
|
X
|
Clustered servers
|
X
|
X
|
X
|
X
|
X
|
|
Agentless monitoring
|
|
X
|
X
|
X
|
|
|
Virtual environment
|
X
|
X
|
X
|
X
|
X
|
X
|
Upgrade from previous versions
|
X
|
|
X
|
|
|
new
|
Management Pack Scope
Scope of support is based on the sub-role feature enabled via the Add Roles and Features wizard from Server Manager.
Prerequisites
The following requirements must be met to run this management pack:
DeDuplication
Installation of System Center Operations Manager and the File Services Management Pack
Windows 2012 R2 servers with the Data Deduplication role installed and volumes enabled
FSRM
iSCSI
NFS
SMB
Files in this Management Pack
The Management Pack includes the following files:
DeDuplication
FSRM
Microsoft.Windows.FileServer.FSRM.6.3.mp
iSCSI
NFS
Microsoft.Windows.FileServices.NFS.6.3.MP
Microsoft.Windows.FileServices.MP
Microsoft.Windows.FileServices.6.3.MP
SMB
Management Pack Purpose
In this section:
Monitoring Scenarios
How Health Rolls Up
For details on the discoveries, rules, monitors, views, and reports contained in this management pack, see Appendix: Management Pack Contents.
Monitoring Scenarios
DeDuplication
Monitoring scenario
|
Description
|
Associated rules and monitors
|
Disabled Volume
|
Looks for a deduplicated volume that has the deduplication feature disabled
|
Alert comes from the server
|
Optimization Job
|
Verifies that an optimization job has run within the last 7 days on deduplication-enabled volumes
|
Volume.OptimizationRun
|
Garbage Collection Job
|
Verifies that a garbage collection job has run within the last 30 days
|
Volume.GarbageCollectionRun
|
Scrubbing Job
|
Verifies that a scrubbing job has run within the last 30 days
|
Volume.ScrubbingRun
|
Optimization Schedule
|
Verifies that at least one regularly scheduled job has been established
|
OptimizationScheduleEnabled
|
Garbage Collection Schedule
|
Verifies that at least one regularly scheduled job has been established
|
GCScheduleEnabled
|
Scrubbing Schedule
|
Verifies that at least one regularly scheduled job has been established
|
ScrubbingScheduleEnabled
|
Scrubbing Job Corruption Threshold
|
Alert if a scrubbing job hits 10,000 corruptions and stops processing a volume
|
Looks for Event ID 12806 for a specific volume
|
FSRM
Monitoring scenario
|
Description
|
Associated rules and monitors
|
An active classification stopped unexpectedly
|
This scenario monitors for classification processes that stop due to a failure of some sort. This is could be caused by corrupted data or classification mechanisms encountering errors while processing a file.
|
(alerting monitor) FCI.ClassificationAborted
|
Classification failed to initialize
|
This scenario monitors for classification processes aborted during initialization. This may occur due to a misconfigured classification rule or a misconfigured classification mechanism.
|
(alerting monitor) FCI.FCIInitialized
|
An orphaned mount point was encountered during classification
|
This scenario monitors the classification processes for any encounters with a mount point that does not have a valid target. These mount points will be ignored during classification.
|
(alerting monitor) FCI.OrphanedMountPoint2
|
Verify the service for FCI is running
|
This scenario monitors that on a machine that may be using FCI, the services required for FCI are running.
|
(alerting monitor) FCI.Service
|
Verify the service for FSRM is running
|
This scenario monitors that on a machine that may be using FSRM, the services required for FSRM are running.
|
(alerting monitor) FSRM.Service
|
Verify that global resource properties from Active Directory, if any, are correctly synchronized with classification property definitions on a domain joined server.
|
This scenario monitors for any errors encountered by a domain joined server when it synchronizes its classification property definitions with global resource property definitions in Active Directory.
|
(alerting monitor) FCI.ADPropertySync
|
Verify that the Dynamic Access Control filter driver is enabled and running
|
This scenario monitors whether the Dynamic Access Control filter driver is enabled and running on servers able to use Dynamic Access Control.
|
(alerting monitor) FCI.Filter
|
Verify that the Quota filter driver is enabled and running
|
This scenario monitors whether the Quota filter driver is enabled and running on servers using FSRM.
|
(alerting monitor) FSRM.QuotaDriverLoaded
|
Verify that the File Screen filter driver is enabled and running
|
This scenario monitors whether the File Screen filter driver is enabled and running on servers using FSRM.
|
(alerting monitor) FSRM.DatascrnDriverLoaded
|
Verify that NTFS is case insensitive
|
This scenario monitors that case the sensitivity option for NTFS is disabled since FCI will not operate correctly otherwise.
|
(non-alerting monitor) FCI.NTFSCaseSensitivity
|
iSCSI
Monitoring scenario
|
Description
|
Associated rules and monitors
|
Firewall check
|
This scenario checks the appropriate firewall ports are opened for iSCSI traffic. When the ports are not opened, the monitor logs the event. The Health Service rolls up the health of the agents and alerts you when the ports are closed.
|
|
Service check
|
This scenario checks the iSCSITarget service is in running state. When the service is stopped, the monitor logs the event. The Health Service rolls up the health of the agents and alerts you when the service is stopped.
|
|
Failures in login with invalid Target name
|
This scenario checks for any initiator failed logins due to invalid Target name. When the Target server receives the login request, but cannot find the requested Target object, the service will log an event. The Health Service rolls up the health of the agents and alerts when this happens.
|
|
Failures in login to a disabled Target
|
This scenario checks for any initiator failed logins due to the Target being disabled. When the Target server receives the login request, but find the Target has been disabled, and not able to handle login, the service will log an event. The Health Service rolls up the health of the agents and alerts when this happens.
|
|
Fail to initialize the Virtual disks
|
This scenario checks if any virtual disks are not loaded by the iSCSI Target service upon start.
|
NA
|
NFS
Monitoring scenario
|
Description / Alert Generation
|
Associated rules and monitors
|
RPC Port Mapper Service
|
This object monitors the RPC portmapper service state.
Generates an alert if the service is not started. **
|
Microsoft.Windows.FileServices.NFS.6.3.Portmap.ServiceState
|
Clustering State
|
This object monitors the status of the Server for NFS cluster listener.
Generates an alert if Server for NFS cannot communicate with the paired server. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.ClusteringState
|
Server for NFS Licensing
|
This object monitors product licensing information.
Generates an alert if Server for NFS cannot validate the license. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.Licensing
|
Netgroup NIS Connection
|
This object monitors the connection to the configured NIS server.
Generates an alert if Server for NFS cannot connect to the NIS server. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.NetgroupNISConnection
|
Server for NFS Network Port Registration
|
This object monitors the registration of ports with the network stack.
Generates an alert if Server for NFS cannot register a port. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.PortRegistration
|
File System Type
|
This object monitor’s file system compatibility.
Generates an alert if one or more NFS file shares are configured to be hosted on an incompatible file system type. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.ShareFileSystemType
|
Provision a Volume for Sharing
|
This object monitors the provisioning of a volume for sharing.
Generates an alert if Server for NFS cannot provision a volume for sharing. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.ShareState
|
Driver Startup State
|
This object monitors the driver startup state.
Generates an alert if the Server for NFS driver does not start. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.StartupState.Driver
|
Server for NFS Runtime State
|
This object monitors Server for NFS.
Generates an alert if the service failed or has been stopped. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.StartupState.Runtime
|
Server for NFS Driver Startup State
|
This object monitors the Server for NFS driver.
Generates an alert if the driver does not start. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.StartupState.Service
|
User Identity Logon
|
This object monitors user name mapping and credentials.
Generates an alert if a user cannot log on. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.UserLogon
|
User Name Mapping LDAP Service Location
|
This object monitors the LDAP Service connection.
Generates an alert if there are problems with the connection. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.UserNameMapping.Config.LDAPService
|
Identity Mapping Source
|
This object monitors the User Name Mapping Service connection.
Generates an alert if Server for NFS cannot connect to the UNMP server or the LDAP server configured for a mapping source. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.UserNameMapping.Config.UNMPService
|
User Name Mapping LDAP Service Connection
|
This object monitors the User Name Mapping LDAP service connection.
Generates an alert if Server for NFS cannot connect to the LDAP server. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.UserNameMapping.LDAPConnection
|
User Name Mapping (UNMP) Service Connection
|
This object monitors the User Name Mapping service connection.
Generates an alert if Server for NFS cannot obtain mapping information. **
|
Microsoft.Windows.FileServices.Service.NFS.6.3.Server.UserNameMapping.UNMPConnection
|
** Alert will be generated only if it is enabled for the monitor.
The following table illustrates the event ID generated for OK, Warning and Error status.
NFS
Monitoring scenario
|
Event ID
OK
|
Event ID
Warning
|
Event ID
Error
|
Clustering State
|
4007, 4019
|
4021, 4022
|
|
Server for NFS Licensing
|
1016
|
1015
|
1017
|
Netgroup NIS Connection
|
1000
|
1069
|
|
Server for NFS Network Port Registration
|
1000
|
1059
|
1060
|
File System Type
|
|
1065, 1070
|
|
Provision a Volume for Sharing
|
1000
|
1064
|
|
Driver Startup State
|
1000
|
|
1058, 1084
|
Server for NFS Runtime State
|
1002
|
1001
|
1003
|
Server for NFS Driver Startup State
|
4018
|
4007
|
4004, 4005, 4018
|
User Identity Logon
|
1000
|
1072, 1073
|
|
User Name Mapping LDAP Service Location
|
|
4012, 4013, 4014, 4015, 4017
|
|
Identity Mapping Source
|
|
1006
|
|
User Name Mapping LDAP Service Connection
|
4010,1007,1055,
1005,1056
|
4016
|
|
User Name Mapping (UNMP) Service Connection
|
4016, 4010, 1007, 1055
|
1005, 1056
|
|
NFS
Alert scenario
|
Associated Rule
|
Event ID
Warning
|
Character Translation Alert
|
Microsoft.Windows.FileServer.NFS.Library.Server.CharacterTranslationAlert
|
1057
|
SMB
Monitoring scenario
|
Description
|
Associated rules and monitors
|
Continuous Availability for File and Storage Services
|
Monitors health of Continuous Availability feature of File and Storage Services
|
Alerting Rules:
WitnessAccessDenied - Generates an alert when SMB witness server denied a request from another computer because the computer did not have the proper security level
WitnessInitFailure - Generates an alert when the SMB witness service fails to initialize.
WitnessClientServerSelectionFailed - Generates an alert when the SMB witness client fails to select an SMB witness server.
WitnessClientServerFailed - Generates an alert when the SMB witness client receives an error from an SMB witness server.
HandleOpenFailure - Generates an alert when the SMB client fails to open a persistent handle.
PersistentHandleFailure - Generates an alert when the SMB client fails to resume a persistent handle on a continuously available file share.
PersistentHandleOrphan - Generates an alert when the SMB client fails to resume a continuously available handle on a continuously available file share.
WitnessMoveFailure - Generates an alert when the SMB client fails to move its connection to the specified cluster node.
SetCAFailureNotClustered - Generates an alert when the SMB server fails to set the continuous availability property for the file share.
SetCAFailureNoRKF - Generates an alert when the SMB server fails to set the continuous availability property on the file share.
CAResumeFailureNoRKF - Generates an alert when the SMB client fails to resume a persistent handle on a continuously available file share.
CCFReopenFailure - Generates an alert when the SMB client fails to reopen a handle for an application that is registered with the server cluster.
Alerting Monitors:
ResumeKeyFilterService – Monitors the Resume Key Filter Service
ResumeKeyLoad – Monitors whether the Resume Key failed to load.
ResumeKeyFilterAttach – Monitors whether the Resume Key filter failed to attach.
ResumeKeyFilterDatabaseLoad - Monitors whether the Resume Key database failed to load.
ResumeKeyFilterDoubleFailover – Monitors whether the Resume Key failed to recover.
ResumeKeyFilterShortNamesNotSupported - Monitors whether the Resume Key did not attach to an unsupported volume.
ResumeKeyFilterChkDskDetected - - Monitors whether the Resume Key detected CHKDSK.
ResumeKeyFilterVssDetected - Monitors whether the Resume Key detected a shadow copy roll-back.
|
File and Storage Services
|
Monitors configuration and health of File and Storage Services
|
Alerting Monitors
Service – Monitors whether the File and Storage Service is running
FirewallPortConfig – Monitors whether the firewall is configured correctly to work with File and Storage Services
StackSizeConfig – Monitors whether the IRP stack size becomes to small
CreateShareEvent – Monitors if creating shares fails too often
|
Work Folders
Monitoring scenario
|
Description
|
Associated rules and monitors
|
Work Folders service running after feature enabled
|
This scenario checks if the Work Foldes feature is enabled, and will check if the service is running. It will alert the service is not running.
|
|
Service check
|
This scenario checks the SyncShareSVC service is in running state. When the service is stopped, the monitor logs the event. The Health Service rolls up the health of the agents and alerts you when the service is stopped.
|
|
Service in a bad state
|
This scenario checks if SyncSharesvc has stopped. The Health Service rolls up the health events. The event text will guide you with specific instructions for starting the service.
|
|
How Health Rolls Up
The following diagram shows how the health states of objects roll up in this management pack.
NOTE: There is no health rollup for the NFS monitors. There is a single entity (NFS) on which all the monitors are defined.
ID: Microsoft.Windows.FileServices.Service.NFS.6.3
Name: NFS (Windows Server 2012R2)
|
