Services Reference Manual Version 10.0 Contents
About Services 14
Custom Services 18
Stock Service Items 18
Managing Custom Services 19
Custom Service Properties 20
Adding Services 41
Editing Services 42
Enabling Services on Devices 43
Disabling Services on Devices 43
Deleting Services 44
Enabling or Disabling Services and Service Groupings 44
Service Properties 45
Self-Healing 50
Generating Service Reports 58
Regular Expressions 59
Active Directory Service 60
Active Directory 2012 - DRA Service 62
Active DSOs (Cisco) Service 63
ADTRAN - Device Health Service 63
ADTRAN - Memory Service 64
Agent Status Service 65
APC PDU Service 66
APC UPS Service 67
APC UPS – Humidity Service 68
APC UPS – Temperature Service 69
Application Compliance Service 69 Asigra Backup Service 70
Asigra v12.x 71
AV Defender Security Event Service 72
Notification Numeric Values 74
AV Defender Status Service 74
AV Status Service 78
AV Activity - McAfee 79
AV Activity - McAfee 8 80
AV Activity - Sophos 81
AV Activity - Sophos 5 82
AV Activity - Symantec 83
AV Activity - Trend Micro 84
AV Def. - McAfee 85
AV Def. - McAfee 8 86
AV Def. - Sophos 87
AV Def. - Sophos 5 88
AV Def. - Symantec 89
AV Def. - Trend Micro 90
Backup Exec Service 91
Setting Up the SQL Server in Mixed Mode 94
Backup Manager Status Service 94
Backup Manager Events Service 96
BES Message Status 96
BIOS (Dell iDRAC) Service 97
CA Replication Events Service 98
CA Replication Scenario Service 100
CCM Analog Gateway Service 101
CCM Analog Gateway FXO Port Service 103 CCM Analog Gateway FXS Port Service 103
CCM Annunciator Service 104
CCM Call Activity Service 106
CCM Call Mgr Status Service 107
CCM Conf Activity Service 108
CCM Conference Registration Service 110
CCM CTI Activity Service 110
CCM CTI Registration Service 111
CCM Gateway Registration Service 112
CCM Group Table (Cisco) Service 113
CCM ISDN - Basic Rate Interface Service 114
CCM ISDN - Primary Rate Interface Service 115
CCM ISDN - T1 Trunks Service 115
CCM MGCP Gateway Service 117
CCM MTP - Transcoder Service 119
CCM Media Device Service 121
CCM Music on Hold Service 122
CCM Performance Service 124
CCM Phone Service 125
CCM Phone Registration Service 126
CCM Server Service 127
CCM Table (Cisco) Service 129
CCM Voicemail Device Service 131
CCM VoiceMail Registration Service 133
Chassis Intrusion (Dell iDRAC) Service 133
Cisco - Connections Service 136
Memory - Cisco Service 138
Cisco Unity Express Mailbox Service 138 Citrix® Presentation Server Service 139
Connections – Watchguard Service 140
Connectivity Service 141
CPU Service 143
Properties Queried and Calculations Performed (WMI only) 144
OID/Calculation (SNMP only) 144
CPU (ADTRAN) service 144
CPU (Cisco) Service 145
CPU Status (Dell iDRAC) Service 146
CPU Status (Fujitsu) Service 147
CPU – Juniper (ScreenOS) Service 149
CPU – Juniper Secure Access Service 149
CPU (VMware) Service 150
CPU – Watchguard Service 151
CTIDevices (Cisco) Service 152
Datastore (VMware) Service 153
DHCP Active Queue Length Service 154
DHCP Server Service 155
Disk Service 158
Disk I/O Service 160
DNS Service 163
DNS Performance Counters Service 165
Ethernet Errors Service 168
Exchange 2003 Service 171
Exchange 2007/2010 Service 174
Exchange 2007/2010 Delivery Queue Service 175
Exchange Database 2013 Service 177
Exchange Database Latency 2013 Service 178 Exchange Processing Time Service 179
Exchange Database Store Mount Status Service 180
Fan Status (Cisco) Service 180
Fan Status (Dell) Service 181
Fan Status (EqualLogic) Service 183
Fan Status (Fujitsu) Service 184
Fan Status (HP) Service 185
Fan Status (IBM) Service 187
Fan Status (Intel) Service 188
Fan Status (VMware) Service 190
File Size Service 192
Fortinet CPU Service 193
Fortinet Disk Service 193
Fortinet Memory Service 194
Fortinet Sessions Service 194
Frame Relay Service 195
FTP Service 198
FW-Chk Point Service 199
FW-Cisco Service 200
FW-Fortigate Service 202
FW-Juniper Service 202
FW-SonicWALL Service 203
FW-Watchguard Service 204
FW-ZyWALL Service 205
Generic (TCP) Service 206
Generic Integer (SNMP) Service 207
Generic ODBC Service 208
Generic SQL Server Service 210 Generic String (SNMP) Service 211
Guest Status (VMware) Service 212
HTTP Service 215
HTTP Status Code Definitions to HTTP or HTTPS Service Availability 218
HTTPS Service 221
HTTP Status Code Definitions to HTTPS Service Availability 224
Hyper-V 2008 Guest Status Service 227
Hyper-V 2012 Guest Status Service 228
Hyper-V Health Service 228
IIS Service 229
IIS Application Pool Service 231
IIS ASP.NET Monitoring Service 233
IIS Website Metrics Service 234
IMAP Service 236
Intel® Quiet System Technology Service 237
Intel® vPro™ Agent Status Service 239
Intel® vPro™ Events Service 240
Intel® vPro™ Status Service 241
Interface Health Service 242
Intrusion Detection Service 245
ISA 2000 Service 248
ISA 2006 Service 250
Juniper (ScreenOS) - Sessions Service 253
Juniper Secure Access - Concurrent Users Service 254
Lexmark - Hopper Status Service 254
Lexmark - Paper Jam Status Service 255
Lexmark - Tray Status Service 256
License Compliance Service 257 Licensing Status (VMware) Service 258
LocalIP Service 259
Log Analysis (Appended) Service 260
Log Analysis (Batch) Service 261
Logical Drive (Adaptec) Service 263
Logical Drive (Dell OM 2.2) Service 268
Logical Drive (Fujitsu) Service 272
Logical Drive (Intel) Service 275
Logical Drive (VMware) Service 277
Maintenance Mode (VMware) Service 279
Memory Service 280
Memory – Juniper (ScreenOS) Service 283
Memory – Juniper Secure Access Service 284
Memory Status (Dell iDRAC) Service 285
Memory Status (Fujitsu) Service 286
Memory Status (HP) Service 288
Memory Status (IBM) Service 289
Memory (VMware) Service 290
Memory Status (VMware) Service 291
NetBotz Airflow Service 292
NetBotz Audio Service 293
NetBotz Dewpoint Service 294
NetBotz Door Switch Service 295
NetBotz Humidity Service 296
NetBotz Temperature Service 297
Network Card (Dell iDRAC) Service 298
NIC Status (VMware) Service 300
NNTP Service 301 Overall VPN Status (Cisco) Service 302
Paper Supply Level Service 303
Patch Status Service 304
Physical Drive (Adaptec) Service 307
Physical Drive (Dell) Service 309
Physical Drive (Dell iDRAC) Service 313
Physical Drive (EqualLogic) Service 318
Physical Drive (Fujitsu) Service 322
Physical Drive (HP) Service 325
Physical Drive (Intel) Service 326
Physical Drive (VMware) Service 328
POP Service 330
Power Consumption (VMware) Service 331
Power Supply (Cisco) Service 332
Power Supply (Dell) Service 334
Power Supply (Dell iDRAC) Service 335
Power Supply (EqualLogic) Service 336
Power Supply (Fujitsu) Service 337
Power Supply (HP) Service 338
Power Supply (Intel) Service 340
Power Supply (VMware) Service 341
Printer Conf Changes Service 343
Printer Cover Status Service 344
Printer Display Service 344
Printer Page Count Service 345
Printer Page Count (HP) Service 346
Printer Status Service 347
Printer Toner Level Service 348 Probe Status Service 349
Process Service 350
Process amc (Cisco) Service 354
Process BPS (Cisco) Service 356
Process capf (Cisco) Service 357
Process carschlr (Cisco) Service 359
Process ccm (Cisco) Service 361
Process ccmAgt (Cisco) Service 363
Process CCMDirSync (Cisco) Service 364
Process cef (Cisco) Service 366
Process cdpAgt (Cisco) Service 368
Process cdpd (Cisco) Service 369
Process cdragent (Cisco) Service 371
Process cdrrep (Cisco) Service 373
Process certM (Cisco) Service 375
Process CiscoDRFLocal (Cisco) Service 376
Process CiscoDRFMaster (Cisco) Service 378
Process CiscoLicenseMgr (Cisco) Service 380
Process CiscoSyslogSub (Cisco) Service 382
Process cmi (Cisco) Service 384
Process ctftp (Cisco) Service 386
Process CTIManager (Cisco) Service 387
Process CTLProvider (Cisco) Service 389
Process dblrpc (Cisco) Service 390
Process DHCPMonitor (Cisco) Service 392
Process hostagt (Cisco) Service 393
Process ipvmsd (Cisco) Service 395
Process LpmTool (Cisco) Service 397 Process mib2agt (Cisco) Service 398
Process RisDC (Cisco) Service 400
Process rtmtreporter (Cisco) Service 402
Process sappagt (Cisco) Service 404
Process snmpdm (Cisco) Service 405
Process TAPS (Cisco) Service 407
Process tomcat (Cisco) Service 409
Process tracecollection (Cisco) Service 410
RAID Status (Adaptec) Service 412
RAID Status (Dell) Service 416
RAID Status (EqualLogic) Service 420
RAID Controller Status (Fujitsu) Service 423
RAID Status (HP) Service 426
RAID Status (VMware) Service 427
SCOM Computer Alerts Service 429
SCOM Distributed Application Alerts Service 430
Security Logs Service 431
Server Temp (Dell) Service 432
Server Temp (HP) Service 434
Server Temp (Intel) Service 435
Server Temp (IBM) Service 439
ShadowProtect Service 440
S.M.A.R.T. Status Service 443
Status Details 444
SMTP Service 446
SMTP Queues Service 447
SNMP Service 449
SonicWALL Connections Service 453 SonicWALL CPU Service 453
SonicWALL Memory Service 454
SQL Server Service 455
SQL Database Information Service 457
SQL Memory Manager Service 458
SQL Server Buffer Manager Service 459
SQL Server Locks Service 460
SQL TCP Availability Service 460
SQL Transaction Information Service 461
SSH Service 462
Stack Status (Cisco StackWise) Service 463
Switch Status (Cisco StackWise) Service 464
System Battery Status (Dell iDRAC) Service 465
System Change Service 467
System Check-In Service 468
System Replacement Service 469
System Warranty Service 470
Telnet Service 470
Temperature Probe (Dell iDRAC) Service 471
Temperature Status (Dell iDRAC) Service 473
Temperature Status (Cisco) Service 475
Temperature Status (EqualLogic) Service 476
Temperature Status (Fujitsu) Service 477
Temperature Status (VMware) Service 479
Terminal Server Service 480
Traffic Service 482
Untangle – Firewall Service 485
Untangle – IPS Service 485 Untangle – Phish Service 486
Untangle – Protocol Filter Service 487
Untangle – Router Service 488
Untangle – Spam Service 488
Untangle – Spyware Service 489
Untangle – Virus Service 490
Untangle – Web Filter Service 491
Veeam Failed Jobs Service 491
Veeam Job Monitor Service 492
Veeam Sure Job Monitor Service 494
How To Monitor Veeam Data Backup 496
Veritas Service 497
VNC Service 500
Volume (EqualLogic) Service 501
VPN Tunnel (Cisco) Service 504
Windows Applications and Services Log 505
Checking A Service Status 506
Windows Backup Service 507
Windows Event Log Service 509
Thresholds 511
Windows Server Clock Drift Service 511
Windows Service Service 512
Windows Terminal Server Service 513
XiloCore Backup Service 515
XiloCore v12.x 515
Index 517 N-central 10.0 Services Reference Manual
About Services
In N-central, services give you the ability to monitor the performance and availability of a device. For example, the CPU service monitors the CPU utilization on a computer, while the SQL Server service monitors how well a SQL server installation is performing.
Services are monitored by Agents or Probes. When the Agent or Probe reports data back to N-central about the service, N-central evaluates the data against the thresholds for the service and then makes the service change to one of the following states:
l Normal,
l Warning,
l Failed,
l Misconfigured,
l No Data,
l Stale Data, or,
l Disconnected.
N-central will optionally send an e-mail or SMS notification to alert you that the service has changed state.
N-central comes with a large number of default services and it is easy to create additional custom services.
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Service Types All of the services in N-central (and any custom services that are created) are based on the following types of monitoring:
- 14 - N-central 10.0 Services Reference Manual
Service Description Type
AMT AMT services allow N-central to use Intel® Active Management (AMT) Technology for powering on devices, running custom scripts, and then powering the devices down. The following services belong to this service type:
l Intel® vPro™ Agent Status Service
l Intel® vPro™ Events Service
l Intel® vPro™ Status Service
Note: N-central supports Intel AMT (Active Management Technology) 4.0.
AMP Custom Automation Manager Policy services report on the results generated when Automation Manager Policies are run based on the use of Global Output Parameters. For more information, refer to "Custom Services Based on Automation Manager Policies" in the N-central online help.
Backu Backup services are used to monitor backup applications such as Backup Exec, Xilocore and Asigra. p Backup services are only available on the following device classes:
l Custom
l Laptop - Windows
l Server - Generic
l Server - Windows
l Workstation - Generic
l Workstation - Windows
Backu Backup Manager services allow N-central to monitor its integrated backup functionality based on CA p Technologies' D2D (disk-to-disk) backup software. Mana ger
EDF Customized services use External Data Feed (a small Java agent) to monitor devices and applications through scripts.
ESXi ESXi services allow N-central to monitor various aspects of ESXi servers including power consumption, logical drives, datastores, and related properties.
Local Local services are services monitored by N-central agents. These include the CPU, Disk, Memory and Process services.
- 15 - N-central 10.0 Services Reference Manual
Service Description Type
Log The N-central agents for Windows, OS X, and Linux can scan log files. If they find the text that is File specified in the service then the service will report a Failed status.
The N-central agents can either scan the entire log file each time, which is how the Log Analysis (Batch) service works, or they can scan only the lines in the log file that have been added since the log file was last scanned, which is how the Log Analysis (Appended) service works.
Note: This category includes both the Log Append) and Log Batch service types.
Maint Maint services are used by N-central for internal processes and should not be modified.
ODBC Both the N-central Windows Probe and the N-central Windows Agent can make ODBC queries to SQL databases. This service allows N-central to grab data from an SQL database and alert you if the data doesn’t match what was expected.
QST QST services allow N-central to use Intel® Quiet System Technology to monitor computer operating temperatures.
Secur Syslog-based services are unique in N-central, because instead of sending queries to the target ity device, they wait for the device to tell them that there is a problem. Log Most commonly found on network infrastructure devices (firewalls, switches, and routers), N- (or central’s syslog-based services (for example, FW-Cisco or FW-Juniper) can only be monitored by a Syslo Windows Probe; none of N-central’s agents can monitor the syslog-based services. g)
SNMP SNMP-based services gather data by sending SNMP “GET” queries to the target device. As SNMP is an extremely common protocol, many N-central services (for example, the APC UPS service, or the Traffic service) use SNMP to get their data. SNMP-based services can be used on both Windows devices and non-Windows devices.
Syste Currently, the only System service is the License Compliance service. This monitors the number of m software licenses allowed for a customer based on thresholds specified for individual applications.
- 16 - N-central 10.0 Services Reference Manual
Service Description Type
TCP By querying the TCP port that an application is using, N-central can tell you if that application is responding and available for your customers to use. The HTTP service and the FTP services both use TCP queries. The HTTP service monitors the status of a website, and the FTP service monitors whether or not an FTP server is online.
TCP-based services are only available for monitoring by the Windows Probe and the N-central server.
Note: This category includes both the TCP and GenericTCP service types.
VMwa VMware services allow N-central to monitor elements of a VMware virtualization environment. re
WMI WMI-based services gather data by sending WMI queries to the target device. As WMI is a protocol that’s only supported by devices running a Windows OS, all of the N-central services that use WMI are only available on devices classed as Laptop - Windows, Server - Windows, or Workstation - Windows.
N-central uses WMI primarily to monitor Microsoft applications, such as SQL, Exchange, IIS, and ISA.
Note: This category includes the WMIWorkstation and WMIServer service types.
WSUS WSUS services allow N-central to interact with a WSUS server in order to monitor patch compliance on computers and generate reports.
Why Services Change State When N-central receives data about a service, it compares that data against the thresholds defined for that service, and then changes the state of the service based on what threshold range the data falls into.
For example, if the agent reported back a value of 3, and the service was configured with the following thresholds, N-central would transition the service into a Warning state:
l Normal: 0-2
l Warning: 3 -5
l Failed: 6-10
There are a number of cases where the service may not report a Normal, Warning, or Failed state:
l If the data reported back to N-central does not fall into the Normal, Warning, or Failed ranges, the service will transition to a Misconfigured state.
- 17 - N-central 10.0 Services Reference Manual
l If the agent or probe wasn’t able to gather the requested data, the service will transition to a Misconfigured state.
l If the data being reported to N-central doesn’t match what it expects (for example, if it’s expecting text, but receives an integer), the service will transition to a No Data state.
l If N-central stops receiving data for the service, the service will transition to a Stale state.
l If the device enters a downtime period, the service will transition to a Disconnected state.
l If an N-central user disables the service, the service will transition to a No Data state.
More about states:
l Normal changes the service to Failed when the service stops running.
l Reversed inverts the monitoring process. For example, a process that should not be run- ning on a device can be monitored by the Process service using this method. After the pro- cess starts running, the state for the Process service changes to Failed.
l Custom allows you to set up values for the Normal, Warning, and Failed states. For example, threshold settings for scan details, such as file size, average round trip time, and time to live (TTL) can be customized.
l Off stops processing the scan detail for a state. If one scan detail is set to Off, the service is processed for a state based on the thresholds of the rest of the scan details. If all of the scan details are set to Off, the service is processed for its availability.
Custom Services N-central allows you to quickly create customized services that leverage:
l Automation Manager Policies,
l N-central's proprietary EDF (external data feed) engine,
l TCP port queries,
l Log file monitoring,
l SNMP queries,
l Syslog messages, and,
l WMI queries.
Custom services function similarly to the services that are already included with N-central. You can create, edit, and delete custom services. You can also export a custom service so that you can share it with the rest of the N-central community. You can also import custom services from the N-able Resource Center.
For more information on working with customized services in N-central, refer to Managing Custom Services on page 19.
Stock Service Items A stock service item is a predefined metric for an EDF, SNMP, or WMI custom service. This includes: CPU, Memory, Process, and UPS services.
- 18 - N-central 10.0 Services Reference Manual
You should use stock service items when the data you are collecting with the custom service (for example, CPU usage) needs to be included in N-central's Executive Summary report or in any Report Manager report.
Managing Custom Services There are a number of ways that you can manage or control custom services including:
To add a custom service
1. In the navigation pane, click Administration > Service Management > Custom Ser- vices.
2. Click Add.
3. Select one of the following:
l Service - to create a custom service with no service items.
l Service using Stock Service Item - to create a custom service that already has default service items configured for the service.
Note: A stock service item is a predefined metric for an EDF, SNMP, or WMI custom service. This includes: CPU, Memory, Process, and UPS services.
1. Select the type of custom service to be created.
2. Type a Name to identify the custom service.
3. Type a Description to provide additional information about the service.
4. Configure the properties of the service as required. For more information, refer to Custom Service Properties on page 20.
5. Click Save.
To edit a custom service
1. In the navigation pane, click Administration > Service Management > Custom Ser- vices.
2. Click the Name of the service that you want to modify.
3. Modify the properties of the service as required. For more information, refer to Custom Ser- vice Properties on page 20.
4. Click Save.
- 19 - N-central 10.0 Services Reference Manual
To delete a custom service Note: Deleting a custom service will remove all instances of the service from any device to which it has been associated. In addition, all historical data collected by the service will be also deleted.
1. In the navigation pane, click Administration > Service Management > Custom Ser- vices.
2. Select the check box next to the service that you would like to delete.
Tip: You can select the check box next to the Customer Name column heading to select all of the services.
3. Click Delete.
4. Click OK.
To import a custom service Importing a custom service requires that you must first download a service XML file either from the N-able Resource Center or from an alternate source.
1. In the navigation pane, click Administration > Service Management > Custom Ser- vices.
2. Click Import.
3. Type the path and filename of the custom service's XML file in the Custom Service XML File Location field or click Browse to navigate to the file.
4. Click Import Custom Service.
To export a custom service
1. In the navigation pane, click Administration > Service Management > Custom Ser- vices.
2. In the Action column for a specific service, click Export.
3. When prompted by the browser, save the service's XML file to the location you would like to use for storing custom service files.
4. Click OK.
Custom Service Properties The properties of custom services will differ depending on the type of service that is created.
- 20 - N-central 10.0 Services Reference Manual
Common properties of all types of custom services include:
Service A descriptive and accurate name for the Name service.
Descriptio A description of the service. n
Automation Manager Policy Monitoring Service Note: The timeout interval is the period that N-central will wait for a response from a service before it causes the service to transition to a different state. The timeout interval for custom services based on Automation Manager Policies is calculated by subtracting two (2) minutes from the scan interval. This value can not be modified.
DETAILS TAB
Select Automation Use the drop-down menu to select the specific Automation Manager Policy Policy whose output will be monitored by the service.
Service Identifier Type a unique identification value to be assigned to the custom service.
SCHEDULE TAB
Interval To configure the schedule for when the service will query the TCP port:
1. Select the Interval as either Once a Day or Daily Interval.
2. Select the Start Time and repetition interval for when the com- mand string will be transmitted to the TCP port.
3. Select the End Time for when the command string should stop being transmitted to the TCP port.
4. Select the Days of the Week when the command string will be transmitted to the TCP port.
5. Select the Days of the Month when the command string will be transmitted to the TCP port.
THRESHOLDS TAB
- 21 - N-central 10.0 Services Reference Manual
String Evaluation Select the operator to be used to evaluate the state of the service based on the global output parameters of the associated Automation Manager Policy from one of the following:
l match
l start with
l end with
l contain
String Value Type the character string to be used for evaluating the state of the service based on the global output parameters of the associated Automation Manager Policy.
If String does not Select the state to which the custom service will transition if the string contain {String value is not found from one of the following: value} display state l Normal as l Warning
l Failed
If String does Select the state to which the custom service will transition if the string contain {String value is found from one of the following: value} display state l Normal as l Warning
l Failed
Size of Monitored Select the ranges to be used as thresholds for transitioning the state of File the custom service based on the size of the monitored file.
EDF (External Data Feed) Service An EDF service is the best option if you want to monitor a device that does not support WMI or SNMP and an N-central Agent cannot be installed on it. EDF (External Data Feed) is a small Java Agent that can be used to return the output of a script or application to N-central. N-central then displays the output of the script as if it was a conventional service.
- 22 - N-central 10.0 Services Reference Manual
Metr Each piece of data that you intend to have the Windows Agent or Windows Probe report back ics to N-central is called a metric.
To add a metric to an EDF custom service
1. In the Data and Thresholds tab, click Add Metric.
2. In the Configure Metric dialog box, type the Metric name.
3. From the Data Type drop-down menu, select the appropriate value for the data that is being reported back by the EDF Agent.
4. Select the Unit if the metric being measured should scale automatically based on the data being collected.
Warning! It is critical that you select the appropriate type of data for a metric. If an inappropriate metric is selected, N-central will not accept the data being reported by the EDF Agent and the service will transition to a Stale state.
5. Click Save.
Frequently Asked Questions Q: Where can I download the EDF Agent and samples of EDF code?
A: The EDF SDK (which contains both the EDF agent and sample EDF code) can be downloaded from the N-able Resource Center:
https://nrc.n-able.com/community/Custom%20Services/EDF%20SDK.zip
Q: When would I use a Unit?
A: Units can be useful if you are measuring the amount of traffic that is passed through a particular NIC. The amount of traffic is reported in bits but you can configure your service to report kilobits, megabits, and gigabits as those units are more user-friendly. For that situation, select Bits from the Unit drop-down menu.
Generic TCP Service A Generic TCP service is best used when you have an application that is available over a network (for example, a web page or e-mail server) and you want to monitor the application. The Generic TCP service will allow you to query the port that the application is running on and determine if the port responds, and if the port sends out the correct response.
- 23 - N-central 10.0 Services Reference Manual
SCHEDULE TAB
Interval To configure the schedule for when the service will query the TCP port:
1. Select the Interval as either Once a Day or Daily Interval.
2. Select the Start Time and repetition interval for when the command string will be transmitted to the TCP port.
3. Select the End Time for when the command string should stop being trans- mitted to the TCP port.
4. Select the Days of the Week when the command string will be transmitted to the TCP port.
5. Select the Days of the Month when the command string will be transmitted to the TCP port.
DETAILS TAB
Timeout Type the Timeout Value (in seconds) for the amount of time that the Probe should Value wait for a response from the TCP port.
Port Type the Port Number to identify the TCP port that will be queried if it is different Number than the default provided.
Send Type the Send Command String that will be transmitted to the TCP port. Comman d String
Validatin Type the Validating String that the Probe should receive from the TCP port. g String Note: You must use a string, not a regular expression for the Validating String.
- 24 - N-central 10.0 Services Reference Manual
THRESHOLDS TAB
DNS Configure how the service will respond if the host name of the device can be resolved Resoluti by selecting the states to be displayed for: on l If Test returns False, and,
l If Test returns True.
Generic Configure how the service will respond if the Validating String is received by the Service Probe by selecting the states to be displayed for: Availabil l If Test returns False, and, ity l If Test returns True.
Round Select the ranges for transitioning the service to a Normal, Warning, or Failed state Trip Time based on the amount of time (in milliseconds) it takes for the command string to be (ms) transmitted to the TCP port and for a response to be received.
Log Scan (Appended) Service A Log Scan (Appended) service is used when the log file that you want to monitor is updated by new lines being appended to the end of the log file, and previously added information is not changed. If the log file that you want to monitor is completely overwritten whenever the application writes to the log file, then you should use the Log Scan (Batch) service.
- 25 - N-central 10.0 Services Reference Manual
SCHEDULE TAB
Interval To configure the schedule for when the service will scan the log:
1. Select the Interval as either Once a Day or Daily Inter- val.
2. Select the Start Time and repetition interval for when the log will be scanned.
3. Select the End Time for when the log will stop being scanned.
4. Select the Days of the Week when the log will be scanned.
5. Select the Days of the Month when the log will be scanned.
DETAILS TAB
Log File Name and Path Type the Log File Path to define the path and filename for the log file that will be monitored. If the log file is located on the same computer as N-central, click Browse to identify the file.
Note: The path must be local. UNC paths (for example, \\mydesktop\C$) will not work.
- 26 - N-central 10.0 Services Reference Manual
Rules To add a regular expression Rule:
1. Click Add Rule.
2. Type a descriptive Rule Name to identify the regular expression.
3. Type the Regular Expression.
4. Select the state that the Log Scan (Appended) service to transition to if the regular expression is not found for the Display Text String Not Matched As value.
5. Select the state that the Log Scan (Appended) service to transition to if the regular expression is found for the Dis- play Text String Matched As value.
6. Click Add.
To edit a regular expression Rule:
1. Click on the Rule Name.
2. In the Add Rule dialog box, modify the properties as required.
3. Click Add.
To delete a regular expression Rule:
l In the Actions column for the individual Rules, click Delete.
THRESHOLDS TAB
Difference in minutes Select the ranges for transitioning the service to a Normal, between the last Warning, or Failed state based on the amount of time (in modification date of the file seconds) between when the log file was last modified and when and the local time of the test the service scanned the log.
File Size Select the ranges for transitioning the service to a Normal, Warning, or Failed state based on the size (in bytes) of the log file.
Line Count of Log File Select the ranges for transitioning the service to a Normal, Warning, or Failed state based on the number of lines contained within the log file.
- 27 - N-central 10.0 Services Reference Manual
Log Scan (Batch Service) A Log Analysis (Batch) service is used when the log file that you want to monitor is completely overwritten whenever the application writes to the log file. If the log file that you want to monitor is updated by new lines being appended to the end of the log file and previously added information in the log file is not changed, then you should use the Log Analysis (Appended) service.
Log Analysis (Batch) services can recognize wildcard characters for the name of the log file that is being monitored. If the filename may be modified, you can use a * symbol to instruct the Windows Agent to look for the most recent log file that meets the search criteria.
Example: If the log file is C:\test20091010.log and the only thing that remains constant in the filename is the word "test" and the suffix .log, you could type C:\test*.log in the Log File Name and Path.
SCHEDULE TAB
Interval To configure the schedule for when the service will scan the log:
1. Select the Interval as either Once a Day or Daily Inter- val.
2. Select the Start Time and repetition interval for when the log will be scanned.
3. Select the End Time for when the log will stop being scanned.
4. Select the Days of the Week when the log will be scanned.
5. Select the Days of the Month when the log will be scanned.
DETAILS TAB
Log File Name and Path Type the Log File Path to define the path and filename for the log file that will be monitored. If the log file is located on the same computer as N-central, click Browse to identify the file.
Note: The path must be local. UNC paths (for example, \\mydesktop\C$) will not work.
- 28 - N-central 10.0 Services Reference Manual
Rules To add a regular expression Rule:
1. Click Add Rule.
2. Type a descriptive Rule Name to identify the regular expression.
3. Type the Regular Expression.
4. Select the state that the Log Scan (Appended) service to transition to if the regular expression is not found for the Display Text String Not Matched As value.
5. Select the state that the Log Scan (Appended) service to transition to if the regular expression is found for the Dis- play Text String Matched As value.
6. Click Add.
To edit a regular expression Rule:
1. Click on the Rule Name.
2. In the Add Rule dialog box, modify the properties as required.
3. Click Add.
To delete a regular expression Rule:
l In the Actions column for the individual Rules, click Delete.
THRESHOLDS TAB
Difference in minutes Select the ranges for transitioning the service to a Normal, between the last Warning, or Failed state based on the amount of time (in modification date of the file seconds) between when the log file was last modified and when and the local time of the the service scanned the log. test
File Size Select the ranges for transitioning the service to a Normal, Warning, or Failed state based on the size (in bytes) of the log file.
- 29 - N-central 10.0 Services Reference Manual
Line Count of Log File Select the ranges for transitioning the service to a Normal, Warning, or Failed state based on the number of lines contained within the log file.
Last Parsed Dates in Time Select the range for the service to report a Normal state based Zone on
SNMP Service SNMP is a communications protocol supported by many devices including printers, firewalls, switches, and routers (including both Windows and Linux devices). An SNMP custom service is used to obtain information from those types of devices.
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
- 30 - N-central 10.0 Services Reference Manual
SCHEDULE TAB
Inter To configure the schedule for when the service will query the target device using SNMP: val 1. Select the Interval as either Once a Day or Daily Interval.
2. Select the Start Time and repetition interval for when the SNMP query will be transmitted to the target device.
3. Select the End Time for when the SNMP query will be transmitted to the target device.
4. Select the Days of the Week when the SNMP query will be transmitted to the tar- get device.
5. Select the Days of the Month when the SNMP query will be transmitted to the tar- get device.
QUERIES TAB
- 31 - N-central 10.0 Services Reference Manual
Queri To create an SNMP query: es 1. Click Add.
2. In the Add Query dialog box, type a Query Name to identify the SNMP query.
3. For the OIDs to be used, table, click + to add variables up to a maximum of 25 variables per SNMP query.
4. Edit the variables in the table by double-clicking the OID Name and the OID to Query to modify the values.
5. To delete a variable, click Delete in the same row as the variable to be removed.
6. Configure the SNMP Index to be used with the OIDs by selecting one of the fol- lowing:
l Use this Index to type an index value.
l Let the Agent/Probe get the SNMP Index by querying an OID with a specific value to type the OID and specific Value.
7. Select Enable editing of this field in N-central to provide users with the cap- ability to edit this field when they are configuring the service.
8. For Field Label, type the name that the users will see in the N-central UI beside the new field that you are creating.
9. For Hint Help, type the text that will be displayed when the user clicks on the ques- tion mark in the N-central UI next to the new field.
10. Click Save.
To delete an SNMP query, click Delete in the Actions column.
To reorder the queries, click the up or down arrow to the left of each query.
For each query, you can uniquely identify and display each instance with the SNMP index or the text description (for example, CPU-O or Process - store.exe). This only applies if you want to have multiple instances of the service on a device.
DATA AND THRESHOLDS TAB
- 32 - N-central 10.0 Services Reference Manual
Metrics Each piece of data that you intend to have the Windows Agent or Windows Probe report back to N-central is called a metric. A maximum of thirty (30) metrics can be configured for each custom SNMP service.
To add a metric to a custom SNMP service
1. Type the Metric Name.
2. Select one of the following:
l Variable to Use - if no calculations are to be performed on the data that is gathered through SNMP. This option requires selecting the appropriate vari- able.
l Calculation to Use - type the appropriate algebraic calculation if cal- culations are to be performed on the data that is gathered through SNMP.
3. From the Data Type drop-down menu, select the appropriate value for the data that is reported back by SNMP.
Warning! If an inappropriate value for the Data Type is selected, N-central will not accept the data being reported by the Agent or Probe and the service will transition to a Stale state.
4. Select the appropriate Unit if the metric being measured should scale auto- matically based on the data being collected.
5. Click Save.
To configure thresholds
1. Select Use Mapping to map specific values or ranges of values to Normal, Warn- ing, or Failed.
2. When you enable Use Mapping with a numeric Type of Data, you can specify numeric ranges (for example, 1,3,5, or 1,3-20,21,25,30-35). When you enable Use Mapping with a string Type of Data, you can map number values returning through SNMP to string values (for example, if SNMP returns a value of 1, the N- central UI could display Good.
3. Specify the appropriate thresholds for your service. If you do not want to set thresholds for this metric (for example, if it is a string value), clear the Configure Thresholds check box.
To delete a metric, click Delete in the Actions column.
To reorder the metrics, click the up or down arrow to the left of each metric.
Frequently Asked Questions Q: What is an SNMP Index?
- 33 - N-central 10.0 Services Reference Manual
A: Everything in SNMP has a unique numeric identifier – called an SNMP index. For example, if you have two NIC cards on a device, one NIC may have an SNMP index of .1 while the other may have an SNMP index of .2. When you make an SNMP query to find out information about the NIC (for example, the NIC speed), you must specify the OID to be queried and the SNMP index to be used.
N-central allows you to configure up to 15 SNMP queries within one service. If you have six different metrics that you want to measure but from two different SNMP indices, you can have two separate SNMP queries in the service: one for the first SNMP index, and one for the second SNMP index.
Q: What mathematical operators does the SDK accept?
A: N-central accepts the following mathematical operators:
/ = Divide
* = Multiply
+ = Add
- = Subtract
Note that variables in the SDK start with a $ symbol (for example, $Var1, $Var2)
Example calculations:
$Var1 + $Var2
($Var1 + $Var2) / 100
If you would like to perform a delta calculation (for example, collect two data samples and then return the difference), replace the $ in front of the variable with a carat ^ (for example, type ^Var1 in the Calculation to Use field).
Q: When would I use a Unit?
A: An example of when units can be useful is if you are measuring the amount of traffic that is passed through a particular NIC. The amount of traffic is reported in bits but you would like your service to report kilobits, megabits, and gigabits in the N-central UI as those units are more user- friendly. For that situation, you would choose Bits from the Units drop-down menu.
Syslog Service Many networking devices such as switches, routers, or firewalls will send a syslog message when they detect that an event has occurred. For example, a denial of service attack could trigger a syslog message. Custom Syslog services are used to monitor these types of events.
- 34 - N-central 10.0 Services Reference Manual
SCHEDULE TAB
Interval To configure the schedule for when the service will scan the syslog:
1. Select the Interval as either Once a Day or Daily Interval.
2. Select the Start Time and repetition interval for when the syslog will be scanned.
3. Select the End Time for when the syslog will stop being scanned.
4. Select the Days of the Week when the syslog will be scanned.
5. Select the Days of the Month when the syslog will be scanned.
DETAILS TAB
Rules To add a regular expression Rule:
1. Click Add Rule.
2. Type a descriptive Rule Name to identify the regular expression.
3. Type the Regular Expression.
4. Select the state that the Syslog service will transition to if the regular expres- sion is not found for the Display Text String Not Matched As value.
5. Select the state that the Syslog service will transition to if the regular expres- sion is found for the Display Text String Matched As value.
6. Click Add.
To edit a regular expression Rule:
1. Click on the Rule Name.
2. In the Add Rule dialog box, modify the properties as required.
3. Click Add.
To delete a regular expression Rule:
l In the Actions column for the individual Rules, click Delete.
THRESHOLDS TAB
Number of Select the ranges for transitioning the service to a Normal, Warning, or Failed Lines state based on the number of lines in the syslog file that are processed. Processed
- 35 - N-central 10.0 Services Reference Manual
Frequently Asked Questions Q: How do I add a new regular expression?
A: To add a new regular expression, click Add String to Match up to a maximum of six regular expressions.
Q: How does the Windows Probe receive syslog messages?
A: When you add an syslog message-based service to a device, the Windows Probe begins monitoring port 514. Any syslog messages that the probe receives are then logged and the Windows Probe then scans the syslog for any regular expressions that you have specified in your custom service.
The log file is:
C:\Program Files\N-able Technologies\Windows Probe\syslog\log\syslog.log
Q: How does the Windows Probe know when a new syslog message has been received from a specific device?
A: When the Windows Probe receives a new syslog message, it records that message in the syslog.log file. This entry is preceded by a date/time stamp as well as the IP address of the device that sent the syslog message.
For example:
07/07/2009 12:42 192.168.1.1
By tracking the IP address of the device that sent the syslog message, the Windows Probe can recognize if the syslog message has originated from a device that it has been configured to monitor by N-central.
WMI Service A WMI custom service is used to collect either performance information or asset information from Windows devices using the WMI (Windows Management Instrumentation) protocol.
- 36 - N-central 10.0 Services Reference Manual
Previously in the N-central SDK (before it was integrated into the N-central UI), variable names were configured in the format of a combination of the WMI Property and WMI class. For example, if the WMI Class was Class and the WMI Property was Property, the variable name would be $Property.Class which would be a unique name. If a new WMI Query was added and the same WMI Class and WMI Property were used, the SDK would configure the new variable with an incremental number such as $Property.Class.1 to ensure that the variable name was unique.
Adding an incremental number to the end of a variable name was not considered to be an optimal method to ensure that variable names are unique and so when the SDK was incorporated into N-central, this model was changed.
Now with the creation of custom services in N-central itself, variable names are formatted as a combination of the WMI Namespace, WMI Class and WMI Property with the addition of validation to ensure the uniqueness of any variable names. With this new method in place, an example of this new configuration would be $Property.Class.root\cimv2\Ncentral.
- 37 - N-central 10.0 Services Reference Manual
SCHEDULE TAB
Inter To configure the schedule for when the service will scan the target devices: val 1. Select the Interval as either Once a Day or Daily Interval.
2. Select the Start Time and repetition interval for when the syslog will be scanned.
3. Select the End Time for when the syslog will stop being scanned.
4. Select the Days of the Week when the syslog will be scanned.
5. Select the Days of the Month when the syslog will be scanned.
QUERIES TAB
- 38 - N-central 10.0 Services Reference Manual
Queri To create a WMI query: es 1. Click Add.
2. Type the WMI Namespace.
3. In the Variables in SELECT Statement table, click + to add variables to the query statement.
4. Edit the variables in the table by double-clicking the WMI Property to modify the value.
5. To delete a variable, click Delete in the same row as the variable to be removed.
6. Type the FROM WMI Class that will be queried.
7. From Calculate As, select the format for the data that will be reported by the query from one of the following:
l Value - The unaltered data value of the variable
l Count - The number of times the specified data appears in WMI
l Sum - The total of all instances of the variable
8. After WHERE, click + to add constraints that will be applied to the query.
9. In the Constraints in WHERE Clause table, edit the constraints by double-click- ing the elements:
l Type the WMI Property name.
l Type the Value of the WMI property.
l Select Enable editing to allow the value of the WMI property to be mod- ified in the N-central UI.
l For Field Label, type the name that the users will see in the N-central UI beside the new field that you are creating.
l For Hint Help, type the text that will be displayed when the user clicks on the question mark in the N-central UI next to the new field.
10. Click Save.
To delete a WMI query, click Delete in the Actions column.
To reorder the queries, click the up or down arrow to the left of each query.
DATA AND THRESHOLDS TAB
- 39 - N-central 10.0 Services Reference Manual
Metrics Each piece of data that you intend to have the Windows Agent or Windows Probe report back to N-central is called a metric. A maximum of thirty (30) metrics can be configured for each custom WMI service.
To add a metric to a custom WMI service
1. Type the Metric Name.
2. Select one of the following:
l Variable to Use - if no calculations are to be performed on the data that is gathered through WMI. This option requires selecting the appropriate vari- able.
l Calculation to Use - type the appropriate algebraic calculation if cal- culations are to be performed on the data that is gathered through WMI.
3. From the Data Type drop-down menu, select the appropriate value for the data that is reported back by WMI.
Warning! If an inappropriate value for the Data Type is selected, N-central will not accept the data being reported by the Agent or Probe and the service will transition to a Stale state.
4. Select the appropriate Unit if the metric being measured should scale auto- matically based on the data being collected.
5. Click Save.
To configure thresholds
1. Select Use Mapping to map specific values or ranges of values to Normal, Warn- ing, or Failed.
2. When you enable Use Mapping with a numeric Type of Data, you can specify numeric ranges (for example, 1,3,5, or 1,3-20,21,25,30-35). When you enable Use Mapping with a string Type of Data, you can map number values returning through WMI to string values (for example, if WMI returns a value of 1, the N-cent- ral UI could display "Good".
3. Specify the appropriate thresholds for your service. If you do not want to set thresholds for this metric (for example, if it is a string value), clear the Configure Thresholds check box.
To delete a metric, click Delete in the Actions column.
To reorder the metrics, click the up or down arrow to the left of each metric.
- 40 - N-central 10.0 Services Reference Manual
Adding Services You can add services to be monitored on a device either to a single device or to multiple devices at the same time.
When adding services to one device, N-central lists the services that are available based on the device's class, monitoring options, and the selected monitoring probe.
When adding services to multiple devices, N-central lists only the services that are available to all of the selected devices based on the device class, monitoring options, and selected monitoring Probe.
Example: If a Workstation - Generic and a Workstation - Windows are selected, only the services that can be monitored by both types of device classes will be listed.
When adding services to multiple devices, the number of instances displayed for each service is based on the least number remaining for all of the devices.
Example: If the number of instances of the CPU service remaining for Device A is 1 and for Device B is 0, the number of instances displayed for both devices will be 0.
After adding services, you must ensure that the service's information displayed on the Service Details tab and the Thresholds tab is accurate.
Note: Only services that have been enabled can be monitored on the status dashboards.
To add a service to one or more devices
1. In the navigation pane, click Views > All Devices.
2. Select the check box next to the device or devices for which you would like to add services.
Tip: You can select the check box next to the Customer/Site column heading to select all of the devices.
3. Click Add Services.
Note: Alternatively, you can click on the device name itself, and then when you've been redirected to the Services screen under the Status tab, click Add.
4. Select the Monitoring Appliance in the Add Services screen.
Note: If you are adding services to more than one device, only the services available to all of the devices are displayed.
5. Specify the number of Instances for each service that you would like to add.
- 41 - N-central 10.0 Services Reference Manual
Note: For the Asigra Backup and XiloCore Backup services, you will need to select the specific type of service that you want to add from the drop-down list displayed in the Services column.
Note: Set the Instances of the Windows Applications and Services Logs to any number smaller than Max Instances.
6. Click OK.
Note: For the Backup Exec, Asigra Backup, and XiloCore Backup services, the Discovered Jobs screen will appear. For all other services, the Devices screen will appear and the selected services will have been added. If any of the selected services could not be added to all of the devices, a System Error screen appears indicating which services could not be added to all of the devices.
7. For the Backup Exec, Asigra Backup and XiloCore Backup services, select the check box next to the discovered backup jobs that you want to monitor.
Tip: You can select the check box next to the Device Name column heading to select all of the backup sets.
Warning! A service cannot be added to a device if the device has exceeded its task limit. A service grouping cannot be added to a device if one of the services in the service grouping cannot be added to the device.
8. Click Add.
Editing Services You can edit the service details and thresholds. When you add a service to a device, default service details and thresholds are set. You must edit the service to modify the default settings.
Tip: When editing a service, you can also view the current service status on the Status tab or generate a report on a service from the Reports tab.
To edit a service
1. In the navigation pane, click Views > All Devices.
2. In the Name column of the All Devices view, click the device for which you would like to edit a service.
3. Click the Status tab in the Edit Device screen.
4. In the Service column, click the service that you would like to edit.
- 42 - N-central 10.0 Services Reference Manual
The Edit Service screen appears and displays the Status, Service Details, Threshold, and Reports tabs.
Note: If you have clicked on a service grouping instead of an individual service, a list of the services associated with the service grouping will appear. Click on the individual service that you would like to edit and the Edit Service screen will appear or click Back to return to the Edit Device screen.
5. Update the required fields.
6. Click OK.
Enabling Services on Devices You can enable and monitor a service on a device. By default, services that are added to a device are enabled.
To enable a service on a device
1. In the navigation pane, click Views > All Devices.
2. In the Name column of the All Devices view, click the device for which you would like to enable a service.
3. Click the Status tab in the Edit Device screen.
4. Select the check box next to the service that you would like to enable.
Tip: You can select the check box next to theService field to select all of the services.
5. Click Enable.
Disabling Services on Devices You can disable a service on a device to prevent it from being monitored on a device. When you would like to temporarily stop the monitoring process, we suggest disabling a service rather than deleting the service. This retains the specified settings for when you enable the service again.
For example, you can disable the services on a device that is to be shut down for maintenance and then enable the services again once the device is back up and running, without having to reset the service details and thresholds.
To disable a service on a device
1. In the navigation pane, click Views > All Devices.
- 43 - N-central 10.0 Services Reference Manual
2. In the Name column of the All Devices view, click the device for which you would like to disable a service.
3. Click the Status tab in the Edit Device screen.
4. Select the check box next to the service that you would like to disable.
Tip: You can select the check box next to the Service field to select all of the services.
5. Click Disable.
Note: When the service is disabled on the device, the service state will change to No Data.
Deleting Services You can remove a service that is being monitored on a device.
To delete a service
1. In the navigation pane, click Views > All Devices.
2. In the Name column of the All Devices view, click the device for which you would like to delete a service.
3. Click the Status tab in the Edit Device screen.
4. Select the check box next to the service that you would like to delete.
Tip: You can select the check box next to the Service field to select all of the services.
5. Click Delete.
6. Click Yes in the Confirmation screen.
Enabling or Disabling Services and Service Groupings You can enable or disable the services and service groupings to which you have permission. When disabled, a service or service grouping is removed from devices and dashboards.
Warning! If a service is included in a service grouping, it cannot be disabled until the service grouping to which it belongs has been deleted.
The accounts and their permissions are summarized in the table, below.
- 44 - N-central 10.0 Services Reference Manual
Has permission to enable/disable Account Level in N-central services
Product Admin (PA) System For all customers in system
PA, Service Service Organization For all customers of an individual Service Organization Admin Organization (SO Admin, SO Tech)
PA, SO Admin, SO Customer For an individual customer Tech, Customer Admin (Admin)
To enable or disable services and service groupings
1. In the navigation pane, click Administration > Service Management > Service Control.
2. Select the check boxes next to the services that you would like to enable or disable.
Tip: You can select the check box next to the Name field to select all of the services on the screen.
Warning! If you need to click Next to select more services on the following screen, you must first click Enable or Disable to apply the changes to the services selected on the current screen. Otherwise, the selection is lost. For example, if you selected CPU, clicked Next, then selected HTTPS on the following screen, and clicked Disable, only the HTTPS service is disabled. To disable CPU, you must have clicked Disable on the same screen on which the CPU service was listed.
3. Click Enable or Disable.
A Confirmation screen appears and, if you are disabling services, lists any devices on which the selected services are set.
4. Click Yes.
The services are enabled or disabled and the Service Control screen appears with the updated status of the services and service groupings.
If you disabled services that were set on any device, the services are removed from the devices.
Service Properties Every N-central service has a wide variety of properties that can be modified depending on the type of service.
- 45 - N-central 10.0 Services Reference Manual
Status
Service Status
Property Description
Current Status Displays the icon that represents the current status (Normal, Failed, or Mis- configured).
Scan Time Displays the time that the latest service scan took place.
Transition Time Displays the time of the last transition.
Service Details
Property Description
Monitoring Define the status of the service (enabled or disabled):
l Enabled - begins the immediate monitoring of the ser- vice on the device.
l Disabled - prevents monitoring of the service on the device.
Monitored By This service can be monitored by either an Agent or a Probe.
Service Description A description of the service.
Generate A Notification When An Event When selected, a notification will be sent with each event that is Is Detected detected.
Scan Interval The period of time, in minutes, allotted between each scan (e.g. scan every 5 minutes).
Service Identifier The unique name used to identify the service.
Enable Reset on Notification Behavior When selected, the service will automatically return to a for the Service normal state when a notification is generated.
If left unselected, the service returns to normal only if no new events are detected. Additionally, leaving this option unselected allows for the configuration and use of Self- Healing for this service.
Log to Monitor Select a log from the list of available custom providers.
Note: Only one custom provider can be selected per service.
- 46 - N-central 10.0 Services Reference Manual
Monitored Error Type List List of errors to monitor during a scan. The options available in this list will change according to the type of log selected in the Log to Monitor section.
Note: Click >> to move all of the items from the left column to the right or << to move all of the items from the right column to the left. You can also use Ctrl-click to deselect an item from either column.
Event Conditions (optional) Allows you to add conditions for N-central to recognize the event.
From the drop-down menu, select one of the child condition options that must be satisfied (either AND or OR).
Event Condition Options Note: Choose a condition by selecting it from the drop-down list and then clicking the Add Condition button. Once the condition has been added, you can add the event ID(s) in the field underneath. To delete a condition, click Delete on the right-hand side.
Event ID Include List The event IDs that you would like to monitor. You can specify individual event IDs or a range of comma-separated event IDs. For example: 100,200,250-400,500-650 This field allows a maximum of 200 characters. Spaces are not allowed.
- 47 - N-central 10.0 Services Reference Manual
Event ID Exclude List The event IDs that you would like to exclude from monitoring. You can specify individual event IDs or a range of comma- separated event IDs. For example: 100,200,250-400,500-650 This field allows a maximum of 200 characters.
Event Source Include Regex Filter The names of the sources that you would like to monitor. Note: You must use the CSV format. For a range of Event IDs, you can use a dash (-).
For example: Userenv, Security, W32Time
Event Source Exclude Regex Filter The names of the Event Log sources that you would like to exclude from monitoring. Note: You must use the CSV format. For a range of Event IDs, you can use a dash (-).
For example: Userenv, Security, W32Time
Event Description Regex Filter The name of the text string or regular expression you would like to look for in the Description field of the event. For more information on Regular Expressions, please refer to the topic, Regular Expressions on page 59.
Thresholds The thresholds for the Windows Event Log service are used for monitoring as follows:
l Custom Event Log Module Status - indicates the number of times the defined event identifiers can be recorded in the same line of a log before triggering the transition to a dif- ferent state. Normally, this threshold should remain at the default values of 0 and 1 to indic- ate whether or not the specified event identifier has been recorded in the log.
l # of duplicate events - indicates the number of identical identifiers that can be recorded in the log within the configured scan interval before triggering the transition to a different state.
Self-Healing For a list of self-healing properties, please visit our Self-Healing Properties page.
- 48 - N-central 10.0 Services Reference Manual
Reports
Property Description
Report Specify the type of report that you would like to view.
Period Specify the time period to be displayed in the report.
Start Date and Time Specify the start time period in which Event Logs will be included.
Scan Details Specify the scan details that you would like included in the report.
Note: This field is only available for the Service Metrics report.
Overlay Thresholds Selecting this box will display threshold lines on the graphs of the report.
Export
Export report as The report can be exported as a PDF or a CSV.
Default Paper Size The default paper size is Letter.
Summary Type the Summary of the report to be included with the export.
File Name Type the name of the file to be included with the exported report.
To Specify the recipient email address.
From Specify your email address.
Subject Type the title of the email in this section.
Email Body Type the message to be included in the email.
Export report as The report can be exported as a PDF or a CSV.
Default Paper Size The default paper size is Letter.
Summary Type the summary of the report to be included with the export.
File Name Type the name of the file to be included with the exported report.
- 49 - N-central 10.0 Services Reference Manual
View Report
Property Description
Company Name The name of the Service Organization.
Report The name of the report.
Created on The date and time that the report was created.
Start Date and Time The start time period in which Event Logs were included.
End Date and Time The end time period in which Event Logs were included.
Device Name The name of the device.
Event Logs The names of the Event Logs that are included in the report.
Event Levels The names of the event levels that are included in the report.
Summary
This section displays a summary of the report in tabular form. From the drop-down menu, select the type of information that you would like displayed in the graph (Application, Setup, System). Below the graph is a more detailed summary of the information. Beneath this detailed information is a log of the reports that have been generated.
Note: This graph is also displayed in the Status section of the device.
Note: You can also access the View Report screen by navigating to Reports > Events > Windows Event Log. This is only available at the Customer-level.
Self-Healing The N-central Self-Healing feature refers to pre-configured responses and actions to specific types of service failures. When a specified failure type occurs, N-central will automatically restart the service or execute a script that has been configured by the administrator to try to resolve the issue. The system will then verify whether the issue has been resolved and will send the appropriate notifications.
Limitations
1. Services monitored by the N-central server cannot use Self-Healing.
2. Self-Healing at the device level is only available under the following conditions:
- 50 - N-central 10.0 Services Reference Manual
l The device on which the service has been added is in Professional mode.
l The operating system of the device is a Microsoft Windows variant.
l The device on which the service has been added is being monitored by a Windows agent or a Windows probe.
3. Self-Healing can not be applied to services that are in service groups.
Excluded Services As the following services are not applicable to Windows devices, they cannot leverage N-central’s Self-Healing functionality. This includes:
- 51 - N-central 10.0 Services Reference Manual
l CPU (ADTRAN) service on page 144 l Lexmark - Paper Jam Status Service
l ADTRAN - Device Health Service on page on page 255
63 l Lexmark - Tray Status Service on
l ADTRAN - Memory Service on page 64 page 256
l Agent Status Service on page 65 l License Compliance Service on page l Application Compliance Service on page 69 257
l Backup Manager Events Service on page l Logical Drive (VMware) Service on 96 page 277
l Backup Manager Status Service on page l Maintenance Mode (VMware) Service 94 on page 279
l CA Replication Events Service on page 98 l Memory - Cisco Service on page 138
l CCM CTI Registration Service on page 111 l Memory – Juniper (ScreenOS) Ser- l CCM Call Mgr Status Service on page 107 vice on page 283
l CCM Conference Registration Service on l Memory – Juniper Secure Access Ser- page 110 vice on page 284
l CCM Gateway Registration Service on page l Memory (VMware) Service on page 112 290
l CCM MGCP Gateway Service on page 117 l NetBotz Airflow Service on page 292
l CCM Media Device Service on page 121 l NetBotz Audio Service on page 293
l CCM Phone Service on page 125 l NetBotz Dewpoint Service on page l CCM Phone Registration Service on page 294
126 l NetBotz Door Switch Service on page l CCM Voicemail Device Service on page 131 295 l CCM VoiceMail Registration Service on page l NetBotz Humidity Service on page 133 296 l Cisco - Connections Service on page 136 l NetBotz Temperature Service on l CPU – Juniper (ScreenOS) Service on page page 297 149 l NIC Status (VMware) Service on page l CPU – Juniper Secure Access Service on 300 page 149 l Paper Supply Level Service on page l CPU (VMware) Service on page 150 303 l CPU – Watchguard Service on page 151 l Physical Drive (VMware) Service on l CPU (Cisco) Service on page 145 page 328 l Cisco Unity Express Mailbox Service on l Power Consumption (VMware) Ser- page 138 vice on page 331 l Connections – Watchguard Service on l Printer Page Count (HP) Service on page 140 page 346 l Datastore (VMware) Service on page 153 l Printer Conf Changes Service on page l Ethernet Errors Service on page 168 343 l Fan Status (VMware) Service on page 190 l Printer Cover Status Service on page l FW-Cisco Service on page 200 344 l FW-Fortigate Service on page 202 l Printer Display Service on page 344 l FW-Juniper Service on page 202 l Printer Page Count Service on page l FW-SonicWALL Service on page 203 345 l FW-Watchguard Service on page 204 l Printer Status Service on page 347 l FW-ZyWALL Service on page 205 l Printer Toner Level Service on page l Fortinet CPU Service on page 193 348 l Fortinet Disk Service on page 193 l Probe Status Service on page 349 l Fortinet Memory Service on page 194 l Power Supply (VMware) Service on l Fortinet Sessions Service on page 194 page 341 l Frame Relay Service on page 195 - 52 - l RAID Status (VMware) Service on l Juniper (ScreenOS) - Sessions Service on page 253 page 427 l Security Logs Service on page 431 l Juniper Secure Access - Concurrent Users l SonicWALL CPU Service on page 453 Service on page 254 l SonicWALL Memory Service on page l Lexmark - Hopper Status Service on page 454 254 l Temperature Status (VMware) Ser- vice on page 479
l Untangle – Firewall Service on page 485
l Untangle – IPS Service on page 485
l Untangle – Phish Service on page 486
l Untangle – Protocol Filter Service on page 487
l Untangle – Router Service on page 488
l Untangle – Spam Service on page 488
l Untangle – Spyware Service on page 489
l Untangle – Virus Service on page 490
l Untangle – Web Filter Service on page 491
l Windows Event Log Service on page 509 N-central 10.0 Services Reference Manual
Applying Self-Healing Self-Healing can be applied to individual services and also through service templates. For more information on how service templates can be used to configure services, refer to "Service Templates" in N-central online help.
To configure a service to use Self-Healing at the device level
1. In the navigation pane, click Views > All Devices.
2. In the Name column of the All Devices view, click the device for which you would like to configure a service to use Self-Healing.
3. Click the Status tab in the Services screen.
4. In the Service column, click the service that you want to configure.
5. Click the Self-Healing tab at the top of the screen.
6. Modify the Self-Healing configuration to suit your specific requirements. For more inform- ation, refer to "Self-Healing Properties" in the N-central online help.
7. Click OK.
To configure a service to use Self-Healing through service templates
1. In the navigation pane, click Configuration > Monitoring > Service Templates.
2. In the Name column of the Service Templates screen, click the service template that you would like to edit.
3. In the Name column under Service Template Services, click the service that you want to configure.
4. Click the Self-Healing tab in the Edit Service Template Service Configuration screen.
5. Modify the Self-Healing configuration to suit your specific requirements. For more inform- ation, refer to "Self-Healing Properties" in the N-central online help.
6. Click OK.
Self-Healing Properties Self-Healing functionality in N-central includes the following properties:
- 53 - N-central 10.0 Services Reference Manual
Trigger Tab
Property Description
When the Select the status in the left-hand column that will start Self-Healing. status Click > to move the status to the right-hand column. changes Tip: Click >> to move all of the items from the left column to the right or << to move all of the items from the right column to the left. You can also use Ctrl-click to deselect an item from either column.
The subsequent options will not be available until status criteria are configured.
BEFORE SELF-HEALING ACTION
Retry Select this option to have Self-Healing attempt to renew monitoring of the service Monitoring before continuing with any configured Self-Healing actions.
Scan the Type a numeric value in the times field to indicate the number of attempts N-central service will make to re-monitor the service before continuing with any configured Self-Healing actions.
Wait Type a numeric value in the seconds field to indicate how long N-central will wait between before attempting to re-monitor the service. each scan
SELF-HEALING
Execute Select this option to have Self-Healing perform a configured action if the status Self- change criteria have been met. Healing action
- 54 - N-central 10.0 Services Reference Manual
Property Description
AFTER SELF-HEALING ACTION
After Type a numeric value in the Minutes field to indicate how long N-central will wait executing before scanning the service to determine that the Self-Healing action was successful. Self- Healing wait
Scan the Type a numeric value in the times field to indicate the number of attempts N-central service will make to scan the service to determine that the Self-Healing action was successful.
Wait Type a numeric value in the seconds field to indicate how long N-central will wait between before attempting to scan the service. each scan
Action Tab
Property Description
SCHEDULE
Limit Type a numeric value in the times per field to indicate the limit of attempts to perform number the configured Self-Healing action. of Self- Select either Hour or Day to determine the time period in which attempts to perform the Healing configured Self-Healing action will be made. actions to
Executio Select the number of hours after which N-central will discontinue attempting to perform n the configured Self-Healing action. Timeout
CREDENTIALS
- 55 - N-central 10.0 Services Reference Manual
Property Description
Credenti Select the security credentials that N-central will use in order to perform the configured als to Self-Healing action from one of the following: Use
l Use Local System credentials - the user name and password of the Local Sys- tem Account.
l Use Device credentials - the user name and password already configured on the Properties tab of the device.
l Custom credentials - a user name and password specifically configured for Self-Healing.
SELF-HEALING ACTION
- 56 - N-central 10.0 Services Reference Manual
Property Description
Self- Select the type of Self-Healing action to be performed from one of the following: Healing l Restart Windows Service Action l Execute Script
l Execute Automation Policy
If Restart Windows Service is selected:
1. Select how the Windows Service Name will be determined from:
l By Service Caption
l By Service Name
l Monitored Service (only for Windows services)
Note: Selecting Monitored Service will use the task identifier that has been configured for the monitored service to determine the service name. For example, this option could be selected in a Service Template that may be applied to multiple services in order to be able to determine the names of each of the associated services.
2. From the drop-down menu that is displayed, select the Windows service to be restarted.
Note: If By Service Caption is selected, the Matching Service Name will be displayed. If By Service Name is selected, the Matching Service Caption will be displayed.
If Execute Script is selected:
1. Select the Location of the script as either From N-central's Script Repository or From My Computer.
a. If From N-central's Script Repository was selected, use the Repos- itory Item drop-down menu to select the script.
b. If From My Computer was selected, type a Name and the File Location (or use Browse) to locate the script.
2. Type any additional Command Line Parameters that are required. You can click Append Monitored Service Parameters to add a variable to the command line that will insert the task identifier for the monitored service.
Example: When selecting Windows Service - Start/Stop from the repository, instead of using the Command Line ParametersGeneric_Service_ Control.bat "Windows Firewall" stop, you can use Generic_Service_ Control.bat {{serviceParameter}} stop.
If Execute Automation Policy is selected:
1. Select the Policy to be used from the Select Automation Policy drop-down menu.
2. Depending on the Policy that is selected, use the Text Input field to type custom input parameters or select Monitored Service Parameter to have the Policy use the specific value for the monitored service.
Example: When selecting the CHKDSK Policy, you can type C: as the Text Input - 57 - value or select Monitored Service Parameter to have the Policy use the task identifier that has been configured for the monitored service. N-central 10.0 Services Reference Manual
Notification Tab
Property Description
After Select a notification rule from one of the following: Self- l Notify me that a Self-Healing attempt occurred, even if successful, and Healing then follow standard notification rules to receive a notification about every Self-Healing action.
l Notify me only if Self-Healing fails and then follow standard notification rules to receive a notification when Self-Healing actions are unsuccessful.
l Follow standard notification rules to use the current notification settings.
Recipie Select a recipient to receive Self-Healing notifications from the Available Recipients nts column.
Click > to move the recipient to the Selected Recipients column.
Tip: Click >> to move all of the items from the left column to the right or << to move all of the items from the right column to the left. You can also use Ctrl-click to deselect an item from either column.
Results Tab The Self-Healing Results tab will display the results of the last Self-Healing action whether it was restarting a Windows Service, running a Script, or running an Automation Policy.
Only the last Self-Healing action will be displayed. To review more than just the last Self-Healing action, refer to the Job Status view in the N-central UI.
Generating Service Reports You can generate a default report for a service on a device the first time you click on the Reports tab. After the default report generates, you can change the report details and regenerate the default report.
You can also select one of the following reports to generate on a device:
l Security Incidents By Service
l Service Metrics
l Status Distribution
l Detailed Status
l Availability Of One Service On Multiple Devices
l Availability Aggregated For One Service On One Device
l Raw Monitored Data
Note: If you generate the Availability Of One Service On Multiple Devices report, it will only display the results for the device you are editing.
- 58 - N-central 10.0 Services Reference Manual
To generate a report
1. In the navigation pane, click Views > All Devices.
2. In the Name column of the All Devices view, click the device for which you would like to generate a service report.
3. Select the service for which you would like to generate a report.
4. Click the Status tab in the Services screen.
Note: This screen will display data, in tabular form, from your event log scan. If a graph does not appear, it means that no event logs have been found during the selected scan period. By default, the scan period is set at 1 day. To expand the scan period, select a different number of days from the drop-down menu next to the Period field (either 1, 7, or 30 days).
5. Click the Reports tab at the top of the screen.
6. If you would like to regenerate this report with different details, update the fields as required.
7. Click View Report.
8. If you would like to view a different report than the default report that will be displayed, select the Report you would like to generate for the service.
9. Update the fields as required.
10. Click View Report.
Tip: You can download or e-mail the report as a PDF file or a comma-separated values (CSV) file.
Regular Expressions Regular expressions contain strings of characters and metacharacters specified by the user to find predetermined key words in a log file. Metacharacters are symbols that take the form of grammatical punctuation, numbers, and the alphabet. In N-central, metacharacters are used with character strings to increase the probability of finding keywords in a specified log file. Regular expressions are specified in the Service Details tab for some of the N-central services. The parameters for the regular expressions are specified in the Thresholds tabs of these services.
The table below describes the basic regular expressions that can be used. For more specific information on regular expressions, please refer to the MSDN article, at http://msdn.microsoft.com/en- us/library/az24scfc.aspx.
- 59 - N-central 10.0 Services Reference Manual
Metacharacter Match Example
. Matches any single character b.t except newline. Scans for the line containing a b followed by any character and a t.
* Matches an expression that bt* has 0 or more of the preceding Scans for the line containing a b followed by 0 or more t's. character.
+ Matches an expression that bt+ has one or more of the Scans for the line containing a b followed by 1 or more t's. preceding character.
^ Matches the beginning of a ^bt line. Scans for the line that begins with bt.
$ Matches the end of a line. bt$ Scans for the line that ends with bt.
\ Prevents the function of the file1\.dll (The escape subsequent metacharacter. Scans for the line containing file1.dll. character) To allow the period to be a part of the line, the \ prevents the period from functioning as a metacharacter.
[ ] Matches any character that is [Bb]t[0-9] within these brackets. Scans for the line that contains an upper or lowercase b, a lowercase t, followed by a digit that is between and including zero and nine.
? Matches an expression that bt? has 0 or 1 of the proceeding Scans for the line that contains a b that may or may not be character. followed by a t.
Active Directory Service The Active Directory service monitors the performance of the Active Directory LDAP service.
Service Type WMI
Instances on a Device 1
Supported Windows 2000, Windows 2003, and Windows 2008 Domain Systems/Applications Controllers
Device Class Server - Windows
Monitored By Windows Agents
Scan Interval 15 minutes
- 60 - N-central 10.0 Services Reference Manual
Properties Queried and Calculations Performed
NameSpace root\cimv2
WMIClassName Win32_PerfRawData_NTDS_NTDS
Var.0.Property LDAPBindTime
Var.1.Property LDAPSuccessfulBindsPersec
Var.2.Property LDAPWritesPersec
Var.3.Property LDAPUDPoperationsPersec
Var.4.Property LDAPActiveThreads
Var.5.Property LDAPClientSessions
Var.6.Property DRAInboundObjectUpdatesRemaininginPacket
Var.7.Property DRAPendingReplicationSynchronizations
Status Details
Status Detail Description
Bind Time (ms) Time (in milliseconds) taken for the last successful LDAP bind.
Successful Binds Number of LDAP binds since last reboot.
Writes The rate at which LDAP clients perform write operations, per second.
UDP Operations The number of UDP operations the LDAP server is processing.
Active Threads The current number of threads in use by the LDAP subsystem of the local directory service.
Client Sessions The number of connected LDAP client sessions.
Inbound Updates in The number of object updates received in the current directory Packet replication updates packets that have not yet been applied to the local server. This counter tells you if the monitored server is receiving changes, and is taking too long to apply them to the database.
Pending Replication The number of directory synchronizations that are in queue for this Syncs server. This counter identifies replication backlog - the larger the number, the larger the backlog.
- 61 - N-central 10.0 Services Reference Manual
Active Directory 2012 - DRA Service The Active Directory 2012 - DRA service monitors replication activity by measuring the performance of the Active Directory and the DRA (Directory Replication Agent).
Service Type WMI
Instances on a Device 15
Supported Windows 2012 Systems/Applications
Device Class Server - Windows
Monitored By Windows Agents
Scan Interval 15 minutes
Status Detail Description
DRA Inbound Full Sync Specifies the number of objects remaining until the full synchronization process is com- Objects Remaining pleted.
DRA Inbound Values Specifies the number of values of object properties received (measured per second) DNS Only (Request- from replication partners in which the values are for object properties that belong to s/Second) distinguished names.
DRA Outbound Values Specifies the number of values of object properties sent (measured per second) to rep- DNS Only (Request- lication partners in which the values are for object properties that belong to dis- s/Second) tinguished names.
DRA Pending Rep- Specifies the number of directory synchronizations that are queued for this server but lication Syn- are not yet processed chronizations
DS Directory Reads Specifies the number of directory reads performed per second. (Requests/Second)
DS Directory Writes Specifies the number of directory writes performed per second. (Requests/Second)
LDAP Searches Specifies the number of search operations (measured per second) that are performed (Requests/Second) by LDAP clients.
LDAP Successful Binds Specifies the number of LDAP bindings (measured per second) that occurred suc- (Requests/Second) cessfully.
- 62 - N-central 10.0 Services Reference Manual
Active DSOs (Cisco) Service The Active DSOs (Cisco) service monitors the number of DSO (digital switchover) channels on a Cisco Voice Gateway device that are currently active.
Service Type SNMP
Instances on a Device 1
Supported Cisco Voice Gateway devices. Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
Object Numerical OID Descriptors
$ActiveDSOs 1.3.6.1.4.1.9.10.19.1.1.4
Status Description Detail
ActiveDSOs The number of active DSO (digital switchover) channels on the specified device.
The number of active DSOs is mapped as follows:
l Normal = 0 to 99
l Warning = 100 to 999
l Failed = more than 1000
ADTRAN - Device Health Service The ADTRAN - Device Health service monitors the health of ADTRAN switch/router devices.
Note: This service cannot use N-central’s Self-Healing feature.
- 63 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported ADTRAN Switch/Router devices Systems/Applications
Device Class Switch/Router
Monitored By Windows Probes
Scan Interval 5 minutes
OID/Calculation
Metric Name OID/Calculation Description
Device Health Summary 1.3.6.1.4.1.664.5.53.1.1.7 Device Health is mapped as follows: Okay: 0 to 3 Warning: 4 Failed: 5, 6
Device Health State Returns the following states: (1) Unknown (2) Unused (3) OK (4) Warning (5) Critical (6) Non-recoverable
ADTRAN - Memory Service ADTRAN - Memory monitors the heap memory usage of an ADTRAN switch/router device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Systems/Applications ADTRAN Switch/Router devices
Device Class Switch/Router
Monitored By Windows Probes
Scan Interval 5 minutes
- 64 - N-central 10.0 Services Reference Manual
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation Description
Total Memory 1.3.6.1.4.1.664.5.53.1.4.7 The total memory for that memory pool.
Memory Used Total Memory - Free Heap Memory The amount of used memory.
Percent of Memory [1- (Free Heap Memory / Total The amount of used memory as a percentage of the Used Memory)] x 100 total memory.
Free Heap Memory 1.3.6.1.4.1.664.5.53.1.4.8 The amount of available memory.
Agent Status Service The Agent Status service monitors the time since the agent last checked in.
This service only monitors devices that have an agent. In addition, the Agent Status service will automatically begin monitoring the device when an agent is installed.
When Agent Status is first added to a device, the service will be in a Misconfigured state until the agent first makes contact with the central server.
During the monitoring process, the central server queries the time of the most recent connection of a device's agent to the network. This is compared to the current time and the resulting difference is then compared to the specified threshold values so that it can be represented by the appropriate state on the status dashboard for the service.
Example: If the time difference between the previous and current connection is within 10 minutes, the service state will display Normal; between 10 and 20 minutes, Warning; and over 20 minutes, Failed.
If this service enters a Failed state, the central server will disconnect all other services with the exception of the following:
l Intel® vPro™ Status,
l Intel® vPro™ Agent Status,
l System Check-In,
l System Replacement, and
l System Warranty.
To prevent services from being disconnected, ensure that the Unscheduled Downtime check box on the Add Device screen (or in the Properties tab of the Edit Device screen) is not selected.
Note: This service cannot use N-central’s Self-Healing feature.
You can choose to show this service in the Active Issues view.
- 65 - N-central 10.0 Services Reference Manual
Service Type Central Server Asset
Instances on a Device 1
Supported All available agents Systems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Central Server Asset
Scan Interval 5 minutes
Status Details
Status Detail Description
Check-In The threshold that compares the time difference between the Interval current time and the most recent connection to the specified threshold values.
APC PDU Service The APC PDU service monitors the phase status of the user-specified phase (circuit), and reports the low/medium/high thresholds for that sensor, as dictated by the PDU.
Service Type SNMP
Instances on a Device 3
Supported Any APC PDU device that supports the PowerNet392 SNMP MIB Systems/Applications
Device Class Other
Monitored By Windows probe
Scan Interval 5 minutes
Phase Number Enter the phase number (either 1, 2, or 3) to be monitored. The default value is 1, and the only values that are accepted are 1, 2, or 3.
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
- 66 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation
Load (Amperes) 1.3.6.1.4.318.1.1.12.2.3.1.1.2/ 10
Maximum Acceptable Load (Amperes) 1.3.6.1.4.318.1.1.12.2.2.1.1.4
Phase Utilization ((Load/10)/Maximum Acceptable Load)*100
APC UPS Service The APC UPS service provides basic and advanced APC UPS battery information.
Service Type SNMP
Instances on a Device 1
Supported Any PowerNet-MIB Compliant Device from APC Systems/Applications
Device Class Server - Generic, Other, Printer, Scanner/Camera, Switch/Router, and Server - Windows
Monitored By Windows Probes
Scan Interval 15 minutes
OID/Calculation
Metric Description OID/Calculation Name
Status 1.3.6.1.4.1.318.1.1.1.2.1.1 The status of the UPS battery. A batteryLow(3) value indicates the UPS will be unable to sustain the current load, and its services will be lost if power is not restored:
l unknown(1) translates to Warning,
l batteryNormal(2) translates to Normal,
l batteryLow(3) translates to Failed.
Time On 1.3.6.1.4.1.318.1.1.1.2.1.2 The elapsed time since the UPS has switched to battery power.
Last 1.3.6.1.4.1.318.1.1.1.2.1.3 The date when the UPS system's batteries were last replaced, in Replaced mm/dd/yy format. For Smart-UPS models, this value is originally set in the factory. When the UPS batteries are replaced, this value should be reset by the administrator.
Capacity 1.3.6.1.4.1.318.1.1.1.2.2.1 The remaining battery capacity expressed as a percentage.
- 67 - N-central 10.0 Services Reference Manual
Metric Description OID/Calculation Name
Temperature 1.3.6.1.4.1.318.1.1.1.2.2.2 The current internal UPS temperature, expressed in degrees Celsius.
Time 1.3.6.1.4.1.318.1.1.1.2.2.3 The run time remaining before battery exhaustion. Remaining
Replace 1.3.6.1.4.1.318.1.1.1.2.2.4 Indicates if the UPS batteries need to be replaced:
Indicator l noBatteryNeedsReplacing(1) translates to Normal,
l batteryNeedsReplacing(2) translates to Failed.
APC UPS – Humidity Service The APC UPS - Humidity services monitors the status and reported humidity of the specified environment sensor.
Service Type SNMP
Instances on a Device 1
Supported Any APC UPS device that supports the PowerNet392 SNMP MIB, and Systems/Applications has an attached environment sensor that reports humidity read- ings.
Device Class Other
Monitored By Windows Probe
Scan Interval 5 minutes
Environment Sensor Enter the name of the environment sensor to be monitored. To find out the name of the environment sensor attached to the UPS, query the UPS device with the .1.3.6.1.4.1.318.1.1.10.2.3.2.1.2 SNMP OID. The default name is Int Sensor.
OID/Calculation
Metric Name OID/Calculation Description
Humidity 1.3.6.1.4.1.318.1.1.10.2.3.2.1.6 The humidity reading
Sensor Status 1.3.6.1.4.1.318.1.1.10.2.3.2.1.3 Monitors the status of the humidity sensor
Sensor Status 1.3.6.1.4.1.318.1.1.10.2.3.2.1.3 Displays the current status of the humidity sensor. Two Description values can be returned: Connected or Disconnected.
- 68 - N-central 10.0 Services Reference Manual
APC UPS – Temperature Service The APC UPS - Temperature service monitors the status and reported temperature of the specified environment sensor.
Service Type SNMP
Instances on a Device 1
Supported Any APC UPS device that supports the PowerNet392 SNMP MIB Systems/Applications
Device Class Other
Monitored By Windows Probe
Scan Interval 5 minutes
Environment Sensor Enter the name of the environment sensor to be monitored. To find out the name of the environment sensor attached to the UPS, query the UPS device with the .1.3.6.1.4.1.318.1.1.10.2.3.2.1.2 SNMP OID. The default name is Int Sensor.
OID/Calculation
Metric Name OID/Calculation Description
Temperature 1.3.6.1.4.1.318.1.1.10.2.3.2.1.4 Displays the temperature reading reported by the tem- perature sensor.
Temperature 1.3.6.1.4.1.318.1.1.10.1.2.2.1.5 Displays the Temperature Unit : Celcius/Farenheit Unit
Sensor Status 1.3.6.1.4.1.318.1.1.10.2.3.2.1.3 Monitors the status of the temperature sensor
Sensor Status 1.3.6.1.4.1.318.1.1.10.2.3.2.1.3 Displays the current status of the temperature sensor. Description Two values can be returned: Connected or Disconnected.
Application Compliance Service The Application Compliance service ensures that your organization's network complies with your organization's software policies. By ensuring continued policy compliance, this service helps you protect your organization from outside threats and the use of unauthorized software.
During the monitoring process, the Application Compliance service collects the names of the installed applications from the Windows registry and compares them with a default list of applications that is approved by your organization. This list of names are entered by your administrator. When the service detects an application name that is not on the list of approved application names, it changes to a Failed state.
- 69 - N-central 10.0 Services Reference Manual
Note: This service cannot use N-central’s Self-Healing feature.
Service Type WMI
Instances on a Device 1
Supported Windows Systems/Applications
Device Class Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Central server asset
Scan Interval 1440 minutes (24 hours).
Application List A list of the applications that you would like to monitor. Use the selection buttons to move applications from the Discovered list to the Allowed list in order to monitor them.
Properties Queried and Calculations Performed
Namespace root\default
WMI Class StdRegProv
WMI Property 0 DisplayName
Status Details
Status Detail Description
Applications are Displays the list of applications that are non-compliant. in Compliance Notifies when an unauthorized application has been identified.
Asigra Backup Service The Asigra Backup service is used for monitoring Asigra backup sets. A separate instance of the Asigra Backup service is required to monitor each individual backup set.
Note: Monitoring an Asigra backup set on a device that uses a Red Hat Enterprise or CentOS Linux operating system requires the use of a Windows Probe. In order for the Windows Probe to successfully discover the Linux device, you must first install the Microsoft Visual C++ 2010 Distributable Package on the device on which the Windows Probe is installed. For more information on the Microsoft Visual C++ 2010 Distributable Package, refer to http://www.microsoft.com/en-ca/download/details.aspx?id=5555.
- 70 - N-central 10.0 Services Reference Manual
Note: After upgrading an Agent that monitors the Asigra Backup service or the XiloCore Backup service, you will need to stop the Windows Agent services, place the Asigra .DLL files to the Agent's bin directory and re-start the Windows Agent services.
Asigra v12.x In order for N-central to monitor Asigra v12.x backup sets, you must redistribute the Asigra API bundle as well as the Microsoft Visual C++ 2010 Distributable Package (which includes the msvcp100.dll and msvcr100.dll files) as follows:
l If using a previously-installed Probe and you are installing Asigra for the first time, you must store the API bundle and the MSVC .DLL files in the Probe's bin directory.
l If monitoring Asigra using a previously-installed Agent, you must store the API bundle and the MSVC .DLL files in the Agent's bin directory.
l If installing a Probe and including an Asigra discovery during the installation, you must ensure that the MSVC .DLL files are stored in the directory that is configured in the DLL path field of the installation software.
l If adding the API bundle and the new MSVC .DLL files to an existing Agent or Probe configuration, you must re-start the Agent or Probe after storing the MSVC .DLL files in order for N-central to start using them.
For more information on the Microsoft Visual C++ 2010 Distributable Package, refer to http://www.microsoft.com/en-ca/download/details.aspx?id=5555.
Service Type ODBC
Instances on a Device 100
Supported Asigra version 9.2 and newer Systems/Applications
Device Class Server - Windows
Monitored By Agent (Windows), Windows Probe
Job Timeout The time (in hours) that the N-central server waits for the backup job to report data. If the backup job has not reported data in the specified time, the service will transition to a Failed state. The default value is 24 hours.
Backup Set Names The identifying names of the discovered Asigra backup sets.
Scan Interval in The time (in minutes) between each scan. The default scan interval for Asigra Backup is Minutes 30 minutes.
Repeat Weekly on The scan is repeated weekly on the specified days. Days
Repeat Monthly on The scan is repeated monthly on the specified days. Days
- 71 - N-central 10.0 Services Reference Manual
Metrics
Metric Name Description
Last Attempted Backup Start Date and The last date and time that a backup was tried (whether successful or Time not).
Backup Status The current status of the backup set.
Backup Status Description A description of the current status of the backup set.
Last Successful Backup Start Date and The last date and time that a backup was successful. Time
Last Sync Time The last time that the backup set was synchronized.
Backup Duration The time it took for the backup to be completed.
Backup Data Type The type of data being backed up (for example, HyperV or Sybase).
Backup Set Type The type of backup set as either Local Only or Local and Offsite.
Stored Size The size of the backed up data in its stored location.
Protected Size The size of the backed up data prior to compression or encryption.
Native Size The size of the backed up data in its original location.
AV Defender Security Event Service The AV Defender Security Event service reports on security events when they are detected on a device that has AV Defender installed .
Note: This service cannot use N-central’s Self-Healing feature.
Service Type Custom API
Instances on a Device 1
Supported Systems/Applications Any device with AV Defender installed
Device Class Workstation - Windows, Laptop - Windows, Server - Windows
Monitored By Windows Agents
Scan Interval 5 minutes
This service is configured by selecting the detection types that are to be reported by AV Defender and then choosing the actions to be taken on detected security threats.
- 72 - N-central 10.0 Services Reference Manual
To configure the AV Defender Event service 1. Click All Devices in the navigation pane.
2. In the Name column of the All Devices screen, click the device for which you would like to edit a service.
3. In the Edit Device screen, click the Status tab.
4. In the Service column of the Status tab, click the AV Defender Security Event service.
5. Click the Service Details tab in the AV Defender Security Event service screen.
6. Under Malware Detection Type, select the types in the left-hand column that you want to monitor.
7. Click > to move the type to the right-hand column.
Tip: Click >> to move all of the items from the left column to the right or << to move all of the items from the right column to the left. You can also use Ctrl-click to deselect an item from either column.
Detection types that can be monitored include:
l Boot Sector l Phishing Untrust
l Cookie l POP3
l File l Process
l HTTP l Registry
l Other l SMTP
l Phishing l Stream
l Phishing Fraud
8. Under Monitoring Actions, select the actions and status you want returned by the AV Defender Security Event service based on the column in which the action is listed as follows:
l To return a Normal status, click Move to Normal,
l To return a Warning status, click Move to Warning, or,
l To return a Failed status, click Move to Failed.
The monitoring actions include:
l Blocked
l Cleaned
l Deleted
l Phishing Webpage Blocked
l Present
- 73 - N-central 10.0 Services Reference Manual
l Quarantined
l Restored
9. Click OK.
Notification Numeric Values Notifications for the AV Defender Security Event service use numeric values to report different elements of security events with the values mapped as follows by default:
Malware Type Malware Threat Type Malware State Malware Taken Actions
1 = File 0 = Virus 1 = Present 1 = Deny/Ignore
2 = HTTP 1 = Spyware 2 = Deleted 3 = Disinfect
3 = Cookie 2 = Adware 3 = Blocked 5 = Delete
4 = POP3 3 = Spam 4 = 7 or 9 = Move To Quarantined Quarantine 5 = SMTP 4 = Rootkit 5 = Cleaned 10 = Disinfect Only 6 = Process 5 = Diar
7 = Boot 6 = Application Sector 7 = Archive Bomb 8 = Registry
9 = Stream
AV Defender Status Service The AV Defender Status service monitors the following:
l Installation Status
l Whether AV Defender’s Definition Files are up-to-date
l Whether or not AV Defender is up-to-date
l Detected Errors
l The Number of Days Since the Last Successful Scan
- 74 - N-central 10.0 Services Reference Manual
Service Type Custom API
Instances on a Device 1
Supported Any device on which AV Defender or Bitdefender Cloud Security for Systems/Applications Endpoints version 3.5 is installed
Device Class Workstation - Windows, Laptop - Windows, Server - Windows
Monitored By Windows Agents
Scan Interval Scans will be conducted based on scan tasks that can be started either manually or based on a schedule.
The scan interval is the number of minutes between scans that the Windows Agent will report data for this service provided that none of the following antivirus actions or issues are detected:
l "Installation",
l "Upgrade", or,
l "SignatureUpdate".
If any of the antivirus actions or issues listed above are detected, the Windows Agent will report the information immediately
- 75 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Installation Status The current status of the installation of AV Defender on the device.
The thresholds for this scan detail include:
l Normal
l Warning
l Failed
Protection Status The current status of AV Defender's protection of the device from security threats.
The thresholds for this scan detail include:
l Normal
l Warning
l Failed
Detected Errors The current status of security threats detected by AV Defender.
The thresholds for this scan detail include:
l Normal
l Warning
l Failed
Detected Errors The security engine errors detected.
Last Successful Scan Time The date and time at which the last successful security scan was carried out.
Days since last successful The amount of time (in days) that has passed since the last successful scan (or from installation security scan was carried out. If no security scans have been performed date if no scans have been since the service was added to the device, this value will indicate the performed since service was amount of time (in days) since AV Defender was successfully installed. added)
Last Successful Scan Result Specific results detected by the last successful security scan. Additional information on detected security threats can be displayed on the Reports tab of the AV Defender Events service.
Product Is Licensed The license status of AV Defender indicated as either True or False.
- 76 - N-central 10.0 Services Reference Manual
Status Detail Description
Antivirus - Anti-malware The installation status of the anti-malware module of AV Defender indicated as either True or False.
Signature Age (In Days) The amount of time (in days) that has passed since the signature file was updated.
Firewall The installation status of the firewall module of AV Defender indicated as either True or False (0 = False, 1 = True).
User Control The installation status of the user control module of AV Defender indicated as either True or False (0 = False, 1 = True).
Privacy Control The installation status of the privacy control module of AV Defender indicated as either True or False (0 = False, 1 = True).
Product Update Enabled The status of automatic updates to AV Defender indicated as either Yes or No.
Last Product Update The date and time of the last successful update to AV Defender.
Product Version The current version of the AV Defender engine installed on the device.
Product Update Error Code A numeric code indicating any errors with updates to AV Defender.
Product Update Error A description of any errors with updates to AV Defender. Message
Definitions Up To Date Whether AV Defender definition files are current indicated as either Yes or No.
Scanning Enabled The operational state of security scanning indicated as either Yes or No.
Enabled Components The AV Defender modules that are currently enabled on the device.
Installed Components The AV Defender modules that have been successfully installed on the device.
- 77 - N-central 10.0 Services Reference Manual
AV Status Service The AV Status service provides consolidated management of antivirus applications. The service reports the following information for antivirus software:
l product name,
l scanning status,
l current status of updates, and
l version information.
Note: To add the AV Status service to a device, you must run the AV Security Center script that is available in the Management Scripts section of the N-able Resource Center.
Service Type WMI
Instances on a Device 1
Supported Windows XP, Windows Vista Systems/Applications
Device Class Laptop - Windows, Server - Windows, Workstation - Windows
Monitored By Windows Probe, Windows Agent
Service Description This service uses the root\SecurityCenter WMI class on a Windows XP/Vista workstation to establish the Antivirus Product name, Scanning status, Up-to-date status, and Version number.
Scan Interval 15 minutes (default), 60 minutes (maximum) (Minutes)
Properties Queried and Calculations Performed
Namespace root\SecurityCenter
WMI Class AntiVirusProduct
WMI Property 0 DisplayName
WMI Property 1 onAccessScanningEnabled
WMI Property 2 productUptoDate
WMI Property 3 versionNumber
- 78 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Antivirus Product Identifies the antivirus software being monitored (normally including both the vendor Name name as well as the specific product name).
Virus Scanning Indicates whether the antivirus software is currently actively scanning or if it has been Enabled disabled.
Antivirus Product Indicates whether the virus dictionary being used by the antivirus software is current or UptoDate outdated.
Version Number The release identifier of the antivirus software being monitored.
AV Activity - McAfee
Service Type Log Appended
Instances on a Device 1
Supported McAfee® VirusScan® Enterprise 7.1 Systems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Central Server (Agent: Windows)
Scan Interval 4 hours
Repeat Weekly on Days Indicates specific days of the week (Monday-Sunday) on which antivirus scans will occur.
Repeat Monthly on Days The scan is repeated weekly on the specified days.
Log File Name and Path The scan is repeated monthly on the specified days.
- 79 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Virus found These threshold values determine the status change of the service. If the related regular expression is found, the test is successful. Otherwise, Files moved the test is unsuccessful. Based on the test results, the appropriate status is Files cleaned or then displayed for the service. files deleted
The line count The number of lines, in the log file, on which the keyword has been located matched and returned by the agent. This information is displayed for each regular regex... expression on the status details screen for the service, any applicable reports, and any triggered notifications (except for numeric pages).
The first line The first 250 characters of the first line, in the log file, containing the matched matching keyword returned by the agent. This information is displayed on the service's status details screen, any applicable reports, and any triggered notifications (except for numeric pages).
AV Activity - McAfee 8
Service Type Log Appended
Instances on a Device 1
Supported McAfee® VirusScan® Enterprise 8.0i Systems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Central Server (Agent: Windows)
Scan Interval 4 hours
Repeat Weekly on Days Indicates specific days of the week (Monday-Sunday) on which antivirus scans will occur.
Repeat Monthly on Days The scan is repeated weekly on the specified days.
Log File Name and Path The scan is repeated monthly on the specified days.
- 80 - N-central 10.0 Services Reference Manual
Status Details
Status Description Details
Virus The threshold values that determine the status change of the service. found If the related regular expression is found, the test is successful. Otherwise, the test is unsuccessful. Based on the test results, the appropriate status is then displayed for the service. Files moved
Files cleaned or files deleted
The line The number of lines, in the log file, on which the keyword has been located and returned by the count agent. This information is displayed for each regular expression on the status details screen for the matched service, any applicable reports, and any triggered notifications (except for numeric pages). regex...
The first The first 250 characters of the first line, in the log file, containing the matching keyword returned line by the agent. This information is displayed on the service's status details screen, any applicable matched reports, and any triggered notifications (except for numeric pages).
AV Activity - Sophos
Service Type Log Appended
Instances on a Device 1
Supported Sophos Anti-Virus for Windows NT/2000/XP/2003 3.xx Systems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent (Windows))
Scan Interval 4 hours
Repeat Weekly on Days Indicates specific days of the week (Monday-Sunday) on which antivirus scans will occur.
Repeat Monthly on Days Indicates specific days of the month (1-31) on which antivirus scans will occur.
Log File Name and Path The name and location of the log file that was specified when setting options to export the scanned data to a log file.
- 81 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
No virus found The threshold values that determine the status change of the service. If the related regular expression is found, the test is successful. Otherwise, Virus found the test is unsuccessful. Based on the test results, the appropriate status is Virus found and then displayed for the service. fix unsuccessful
Virus found and fix successful
The line count The number of lines, in the log file, on which the keyword has been located matched regex... and returned by the agent. This information is displayed for each regular expression on the status details screen for the service, any applicable reports, and any triggered notifications (except for numeric pages).
The first line The first 250 characters of the first line, in the log file, containing the matched matching keyword returned by the agent. This information is displayed on the service's status details screen, any applicable reports, and any triggered notifications (except for numeric pages).
AV Activity - Sophos 5
Service Type Log Appended
Instances on a Device 1
Supported Sophos Anti-Virus for Windows 2000/XP/2003 5.0 Systems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent (Windows)
Scan Interval 4 hours
Repeat Weekly on Days The scan is repeated weekly on the specified days.
Repeat Monthly on The scan is repeated monthly on the specified days. Days
Log File Name and Path The name and location of the log file that was specified when setting options to export the scanned data to a log file.
- 82 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
No virus found The threshold values that determine the status change of the service. If the related regular expression is found, the test is successful. Otherwise, Virus found the test is unsuccessful. Based on the test results, the appropriate status is Virus found and then displayed for the service. fix unsuccessful
Virus found and fix successful
The line count The number of lines, in the log file, on which the keyword has been located matched regex... and returned by the agent. This information is displayed for each regular expression on the status details screen for the service, any applicable reports, and any triggered notifications (except for numeric pages).
The first line The first 250 characters of the first line, in the log file, containing the matched matching keyword returned by the agent. This information is displayed on the service's status details screen, any applicable reports, and any triggered notifications (except for numeric pages).
AV Activity - Symantec The AV Activity -Symentec Service supports Symantec Endpoint Protection 11.0.
Service Type Log Appended
Instances on a Device 1
Supported Symantec Endpoint Protection 11.0 Systems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent (Windows)
Scan Interval 4 hours
Repeat Weekly on Days The scan is repeated weekly on the specified days.
Repeat Monthly on Days The scan is repeated monthly on the specified days.
Log File Name and Path The name and location of the log file that was specified when setting options to export the scanned data to a log file.
- 83 - N-central 10.0 Services Reference Manual
Status Details
Status Description Detail
Quarantined The threshold values that determine the status change of the service. file If the related regular expression is found, the test is successful, otherwise it is unsuccessful. Based on the test results, the appropriate status is then displayed for the service. Renamed file
Deleted infected file
Logged corrupt file
Cleaned and removed file (virus)
Cleaned and removed file (macro virus)
The line The number of lines, in the log file, on which the keyword has been located and returned by the count agent. This information is displayed for each regular expression on the status details screen for matched the service, any applicable reports, and any triggered notifications (except for numeric pages). regex...
The first The first 250 characters of the first line, in the log file, containing the matching keyword line returned by the agent. This information is displayed on the service's status details screen, any matched applicable reports, and any triggered notifications (except for numeric pages).
AV Activity - Trend Micro The Antivirus Activity-Trend Micro service monitors the scanning activities of all of the versions of the Trend Micro ServerProtect application.
Service Type Log Appended
Instances on a Device 1
Supported Trend Micro™ ServerProtect™ 5.58 Systems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
- 84 - N-central 10.0 Services Reference Manual
Monitored By Agent (Windows)
Log File Name and Path The name and location of the log file that was specified when setting options to export the scanned data to a log file.
Scan Interval 4 hours
Repeat Weekly on Days The scan is repeated weekly on the specified days.
Repeat Monthly on Days The scan is repeated monthly on the specified days.
Status Details
Status Detail Description
Quarantine The threshold values that determine the status change of the service. success If the related regular expression is found, the test is successful. Otherwise, the test is unsuccessful. Based on the test results, the appropriate status is Clean success then displayed for the service. Delete success
Pass success
Rename success
The line count The number of lines, in the log file, on which the keyword has been located matched regex... and returned by the agent. This information is displayed for each regular expression on the status details screen for the service, any applicable reports, and any triggered notifications (except for numeric pages).
The first line The first 250 characters of the first line, in the log file, containing the matched matching keyword returned by the agent. This information is displayed on the service's status details screen, any applicable reports, and any triggered notifications (except for numeric pages).
AV Def. - McAfee
Service Type Log Appended
Instances on a Device 1
Supported McAfee® VirusScan® Enterprise 7.1 Systems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent (Windows)
- 85 - N-central 10.0 Services Reference Manual
Log File Name and Path The name and location of the log file that was specified when setting options to export the scanned data to a log file.
Scan Interval 4 hours
Repeat Weekly on Days The scan is repeated weekly on the specified days.
Repeat Monthly on Days The scan is repeated monthly on the specified days.
Status Details
Status Detail Description
Regular expressions 1 to 5 The threshold values that determine the status change of Update success the service. If the related regular expression is found, the test is Regular expression 6 Update successful. Otherwise, the test is unsuccessful. Based on failed the test results, the appropriate status is then displayed for the service.
The line count matched regex... The number of lines, in the log file, on which the keyword has been located and returned by the agent. This information is displayed for each regular expression on the status details screen for the service, any applicable reports, and any triggered notifications (except for numeric pages).
The first line matched The first 250 characters of the first line, in the log file, containing the matching keyword returned by the agent. This information is displayed on the service's status details screen, any applicable reports, and any triggered notifications (except for numeric pages).
AV Def. - McAfee 8
Service Type Log Appended
Instances on a Device 1
Supported McAfee® VirusScan® Enterprise 8.0i Systems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent (Windows)
Log File Name and Path The name and location of the log file that was specified when setting options to export the scanned data to a log file.
- 86 - N-central 10.0 Services Reference Manual
Log File Name and Path The name and location of the log file that was specified when setting options to export the scanned data to a log file.
Scan Interval 4 hours
Repeat Weekly on Days The scan is repeated weekly on the specified days.
Repeat Monthly on Days The scan is repeated monthly on the specified days.
Status Details
Status Details Description
Regular expressions 1 to 5 The threshold values that determine the status change of the Update success service. If the related regular expression is found, the test is successful. Regular expression 6 Otherwise, the test is unsuccessful. Based on the test results, the Update failed appropriate status is then displayed for the service.
The line count matched The number of lines, in the log file, on which the keyword has regex... been located and returned by the agent. This information is displayed for each regular expression on the status details screen for the service, any applicable reports, and any triggered notifications (except for numeric pages).
The first line matched The first 250 characters of the first line, in the log file, containing the matching keyword returned by the agent. This information is displayed on the service's status details screen, any applicable reports, and any triggered notifications (except for numeric pages).
AV Def. - Sophos
Service Type Log Appended
Instances on a Device 1
Supported Sophos Anti-Virus for Windows NT/2000/XP/2003 3.xx Systems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent (Windows)
Scan Interval 4 hours
Repeat Weekly on Days The scan is repeated weekly on the specified days.
Repeat Monthly on Days The scan is repeated monthly on the specified days.
- 87 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Update Started The threshold value that determines the status change of the service. If the related regular expression is found, the test is successful. Otherwise, the test is unsuccessful. Based on the test results, the appropriate status is then displayed for the service.
The line count matched The number of lines, in the log file, on which the keyword has been regex... located and returned by the agent. This information is displayed for each regular expression on the status details screen for the service, any applicable reports, and any triggered notifications (except for numeric pages).
The first line matched The first 250 characters of the first line, in the log file, containing the matching keyword returned by the agent. This information is displayed on the service's status details screen, any applicable reports, and any triggered notifications (except for numeric pages).
AV Def. - Sophos 5
Service Type Log Appended
Instances on a Device: 1
Supported Sophos Anti-Virus for Windows 2000/XP/2003 5.0 Systems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored by Agent (Windows)
Log File Name and Path The name and location of the log file that was specified when setting options to export the scanned data to a log file.
Scan Interval 4 hours
Repeat Weekly on Days The scan is repeated weekly on the specified days.
Repeat Monthly on Days The scan is repeated monthly on the specified days.
- 88 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Update Started The threshold value that determines the status change of the service. If the related regular expression is found, the test is successful. Otherwise, the test is unsuccessful. Based on the test results, the appropriate status is then displayed for the service.
Update Complete The threshold value that determines the status change of the service. If the related regular expression is found, the test is successful. Otherwise, the test is unsuccessful. Based on the test results, the appropriate status is then displayed for the service.
Update Failed The threshold value that determines the status change of the service. If the related regular expression is found, the test is successful. Otherwise, the test is unsuccessful. Based on the test results, the appropriate status is then displayed for the service.
The line count The number of lines, in the log file, on which the keyword has been matched regex... located and returned by the agent. This information is displayed for each regular expression on the status details screen for the service, any applicable reports, and any triggered notifications (except for numeric pages).
The first line matched The first 250 characters of the first line, in the log file, containing the matching keyword returned by the agent. This information is displayed on the service's status details screen, any applicable reports, and any triggered notifications (except for numeric pages).
AV Def. - Symantec
Service Type Log Appended
Instances on a Device 1
Supported Symantec Antivirus Corporate Edition 8.0 and Norton® Antivirus® Systems/Applications Corporate Edition 7.6
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent (Windows)
Scan Interval 5 days
Log File Name and Path The name and location of the log file that was specified when setting options to export the scanned data to a log file.
- 89 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Patches were found and The threshold values that determine the status change of the applied service. If the related regular expression is found, the test is successful. Issue contacting LiveUpdate Otherwise, the test is unsuccessful. Based on the test results, server the appropriate status is then displayed for the service. Issue extracting update zip file
The line count matched The number of lines, in the log file, on which the keyword has regex... been located and returned by the agent. This information is displayed for each regular expression on the status details screen for the service, any applicable reports, and any triggered notifications (except for numeric pages).
The first line matched The first 250 characters of the first line, in the log file, containing the matching keyword returned by the agent. This information is displayed on the service's status details screen, any applicable reports, and any triggered notifications (except for numeric pages).
AV Def. - Trend Micro
Service Type Log Batch
Instances on a Device 1
Supported Trend Micro™ ServerProtect™ 5.58 Systems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent (Windows)
Log File Name and Path The name and location of the log file that was specified when setting options to export the scanned data to a log file.
Scan Interval 4 hours
Repeat Weekly on Days The scan is repeated weekly on the specified days.
Repeat Monthly on Days The scan is repeated monthly on the specified days.
- 90 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Update success The threshold value that determines the status change of the service. If the related regular expression is found, the test is successful. Otherwise, the test is unsuccessful. Based on the test results, the appropriate status is then displayed for the service.
The line count The number of lines, in the log file, on which the keyword has been located matched regex... and returned by the agent. This information is displayed for each regular expression on the status details screen for the service, any applicable reports, and any triggered notifications (except for numeric pages).
The first line The first 250 characters of the first line, in the log file, containing the matched matching keyword returned by the agent. This information is displayed on the service's status details screen, any applicable reports, and any triggered notifications (except for numeric pages).
Backup Exec Service The Backup Exec service monitors the status of backups that have been performed by Symantec™ Backup Exec™. Using the Open Database Connectivity (ODBC) protocol, the Backup Exec service can monitor up to 50 jobs.
For Backup Exec, the following job types can be discovered by N-central (and can be monitored by the Backup Exec service):
l Backup
l Catalog
l Duplicate to Tape
l Report
l Restore
l TestRun
l Utility
l Verify
Service Type ODBC
Instances on a Device 50
Supported Backup Exec™ version 9.x to 12.x, and Backup Exec™ 2010 to 2012 Systems/Applications
Device Class Server - Windows
Monitored By Agent (Windows), Windows probe
- 91 - N-central 10.0 Services Reference Manual
Timeout Value The time (in seconds) that the N-central server waits before considering the ODBC connection a failure. The default is 5 seconds.
Failed Job Status List The list of Backup Exec job status codes that will make the service transition to a Failed state.
Warning Job Status The list of Backup Exec job status codes that will make the service transition to a List Warning state.
Job Timeout Job Timeout is measured in hours. If the Backup Exec job has not run in the specified time, the Backup Exec service will transition to a Failed Status.
Scan Interval in The time (in minutes) between each scan. The default scan interval for Backup Exec is Minutes 30 minutes.
Repeat Weekly on The scan is repeated weekly on the specified days. Days
Repeat Monthly on The scan is repeated monthly on the specified days. Days
Metrics
Metric Name Description
Backup Exec Job Return Code A numeric value that indicates the status of the backup.
Elapsed Time The amount of time taken to perform the backup.
Number of directories backed up The details of the backup.
Number of files backed up
Number of files skipped
Number of files corrupted
Number of files in use
Total bytes backed up
Byte rate (MB per minute) The speed of the backup.
Backup Exec Job Status Codes
You can view the return values for the associated job status on the status screen for the Backup Exec service. These values represent specific critical issues.
- 92 - N-central 10.0 Services Reference Manual
1 Job is terminal due to cancellation
2 Job has been completed by the engine and is waiting on final disposition
3 Job is terminal with success but there are some exceptions
4 Job has been sent for execution
5 Job is in a hold state
6 Job is terminal with an error
7 The schedule for the task is invalid
8 The time window is mutually exclusive thus job will never run
9 Job is eligible for dispatch and is late
10 Date of job makes it eligible to run, but time is not in window
11 DEPRECATE: Set as sub-status on READY job now
12 The job needs to be dispositioned to an actual state
13 The system forced recovery of the job
14 Job has been disabled in the system
15 The job will be restarted with checkpoint restart enabled, this value is only set in job history summary
16 Job is currently running on server
17 Job is eligible for dispatch
18 The job has a due date in the future
19 Job is terminal with success
20 Job is ready, but another higher precedence task is eligible to run
21 The job was aborted due to AbortThreshold timeout
22 The job needs to have the due date calculated
23 The job is linked to another job so will not start until master job is finished
24 The job failed somewhere between RunJob() and before it was inserted on remote machine
25 The job's scheduled start time has passed but a dependant job has not yet completed
- 93 - N-central 10.0 Services Reference Manual
Setting Up the SQL Server in Mixed Mode Before the Backup Exec service can monitor the results of the discovered jobs that have been performed by Microsoft SQL Server database, you must set up SQL Server in mixed mode.
Warning! The following changes should be reviewed, approved, and implemented by a Microsoft certified professional. For more information about switching SQL Server to Mixed Mode, contact Microsoft Corporation.
To set up Microsoft SQL Server in mixed mode
1. Click Start>All Programs>Microsoft SQL Server>Enterprise Manager.
The SQL Server Enterprise Manager screen appears.
2. Navigate to the appropriate SQL Server Group.
3. In the contents pane, right-click the appropriate SQL server.
4. Click Properties.
The SQL Server Properties dialog appears.
5. Select the Security tab.
The Security tab contents display.
6. Under the Security heading, locate the Authentication section and select SQL Server and Windows.
7. Click OK.
Backup Manager Status Service The Backup Manager Status service is automatically added to any device that has N-central's Backup Manager installed and monitors the status of the Backup Manager software.
Note: This service cannot use N-central’s Self-Healing feature.
- 94 - N-central 10.0 Services Reference Manual
Instances on a Device 1
Supported Systems/Applications Any Backup Manager device
Device Class Workstation - Windows, Laptop - Windows, Server - Windows
Monitored By Windows Agents
Scan Interval 60 minutes
Status Detail Description
Destination Drive - Indicates the amount of free space on the destination backup drive. Free Space
Full Backup Provides information about the different types of backups that Backup Manager has performed including:
Incremental Backup l the number (or Count) of backups,
l the Total Size of the backups,
l the Schedule for performing backups, Verify Backup l the date and time of the Last Backup,
l the date and time when the Next Backup will take place, File Copy l the Destination drive where backups will be stored, l Status Details of the most recent backup,
l the current Status of backups, and
Recovery Point Copy l the Thresholds currently in effect for backups.
Product Status Indicates information about the Backup Manager software including:
l Version
l Status
l Is a Newer Version of Backup Manager Available?
l Is the Backup Manager Service running?
Note: The reference to a Backup Manager service is for the Windows service and does not refer to an N-central service.
Recovery Points Indicates information about configured recovery points including: Status l Status Details
l Maximum Configured Number of Recovery Points
l Current Number of Recovery Points
l Oldest Recovery Point
l Most Recent Recovery Point
l Days Since Most Recent Recovery Point
l Total Storage Size of All Recovery Points (GB)
- 95 - N-central 10.0 Services Reference Manual
Backup Manager Events Service The Backup Manager Events service is automatically added to any device that has N-central's Backup Manager installed and monitors the events that are logged by Backup Manager.
Note: This service cannot use N-central’s Self-Healing feature.
Instances on a Device 1
Supported Systems/Applications Any Backup Manager device
Device Class Workstation - Windows, Laptop - Windows, Server - Windows
Monitored By Windows Agents
Scan Interval 60 minutes
Status Description Detail
Details A list of event types reported by Backup Manager Events. Use the selection buttons to move types from the Backup Type list on the left to the Monitored Backup Type list on the right in order to view the event details.
Monitoring Select the severity of Events from Backup Manager corresponding to a Normal, Warning, or Failed Actions state. You can move a Severity Level to another service status column by selecting it and pressing the corresponding button (Move to Normal, Move to Warning, or Move to Failed).
BES Message Status The BES Message Status service monitors the following message statistics on a Blackberry Enterprise Server:
l the number of Failed messages,
l the number of Pending messages,
l the number of Expired messages,
l the number of messages sent per minute, and,
l the number of messages received per minute.
- 96 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 10
Supported Any BLACKBERRYSERVER-MIB compliant device Systems/Applications
Device Class Server - Generic, Server - Windows
Monitored By Windows Probes
Scan Interval 5 minutes
SRP Identifier The Server Routing Protocol (SRP) Identifier is a unique value used to register and authenticate the BlackBerry Enterprise Server on the network.
OID/Calculation
Metric Name OID/Calculation Description
Failed Messages 1.3.6.1.4.1.3530.5.25.1.27 Indicates the number of messages to handheld devices that have failed.
Expired Messages 1.3.6.1.4.1.3530.5.25.1.26 Indicates the number of messages to handheld devices that have expired.
Pending Messages 1.3.6.1.4.1.3530.5.25.1.25 Indicates the number of messages pending for delivery to handheld devices.
Messages Sent per 1.3.6.1.4.1.3530.5.25.1.207 Indicates the total number of messages sent from hand- Minute held devices per minute.
Messages Received 1.3.6.1.4.1.3530.5.25.1.208 Indicates the total number of messages delivered to per Minute handheld devices per minute.
BES Instance Name 1.3.6.1.4.1.3530.5.20.1.2 Indicates the BlackBerry Enterprise Server's unique SRP identifier.
BIOS (Dell iDRAC) Service The BIOS (Dell iDRAC) service monitors the Basic Input/Output System (BIOS) firmware interface of a Dell PowerEdge server using the embedded integrated Dell Remote Access Controller (iDRAC).
- 97 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 100
Supported Dell PowerEdge servers with integrated Dell Remote Access Controller Systems/Applications (iDRAC)
Device Class for CPU (SNMP) Servers - Management Interface
Monitored By Windows Agent
Scan Interval 5 minutes
SNMP Index Type or select the name of the SNMP Index to be used by this service.
Status Object Numerical OID Description Detail Descriptors
Release $releaseDat 1.3.6.1.4.1.674.10892.5.4.300.50. The release date of the system Date e 1.7 BIOS.
Version $version 1.3.6.1.4.1.674.10892.5.4.300.50. The specific version identifier of the 1.8 system BIOS.
Status $status 1.3.6.1.4.1.674.10892.5.4.300.50. The current status of the system 1.5 BIOS mapped as follows:
1 - other,
2 - unknown,
3 - ok,
4 - nonCritical,
5 - critical, and,
6 - nonRecoverable.
CA Replication Events Service The CA Replication Events service retrieves events from the CA Replication Control Console. To display the details of detected events, click on the Reports tab for the service.
- 98 - N-central 10.0 Services Reference Manual
Note: Accessing the the CA Replication Control Console requires that the service be configured with the user name and password that are used to sign in to the CA Replication Control Console.
The service must be installed on the same computer on which the CA Replication Control Console is installed.
Note: This service cannot use N-central’s Self-Healing feature.
Instances on a Device 1
Supported Systems/Applications Any CA Replication Control Console device
Device Class Workstation - Windows, Laptop - Windows, Server - Windows
Monitored By Windows Agents
Scan Interval 15 minutes
Status Description Detail
Date and The date and time at which the event took place displayed in HH:MM format. Time
State The current state of the service in N-central with the following default thresholds:
l Failed = Critical or Error
l Warning = Warning
l Normal = SignificantInfo or Info
Event ID The unique identifier assigned to an individual CA Replication event.
Status The numeric value indicating the event status
Event A description of the event. Message
Time Stamp The precise date and time stamp assigned to the event when it occurred.
Host The host device on which the event occurred.
- 99 - N-central 10.0 Services Reference Manual
Status Description Detail
Sequence A numeric identifier indicating the order in which the event occurred.
Event The CA value indicating the severity of the event from one of the following: Severity l Critical
l Error
l Warning
l SignificantInfo
l Info
Scenario ID The unique identifier of the replication scenario in which the event occurred.
Error If the service transitions to a Failed state, the associated error message is Message displayed.
CA Replication Scenario Service The CA Replication Scenario service monitors a CA replication scenario with one instance of the service being required for each individual scenario.
This service accesses the CA Replication Control Console which requires that it be configured with the user name and password that are used to sign in to the console.
Instances on a Device 500
Supported Systems/Applications Any device running the CA Replication Control Console
Device Class Workstation - Windows, Laptop - Windows, Server - Windows
Monitored By Windows Agents
Scan Interval 15 minutes
- 100 - N-central 10.0 Services Reference Manual
Status Detail Description
Scenario State Indicates the current state of the replication scenario from one of the following:
l Normal
l Warning
l Failed
Master State Indicates the current state of the master data configured for the replication scenario from one of the following:
l Normal
l Warning
l Failed
Replica State Indicates the current state of the replica data configured for the replication scenario from one of the following:
l Normal
l Warning
l Failed
Scenario ID The unique identifier of the replication scenario.
Master Spool The current utilization of the master data spool indicated as a percentage (%) of the total Utilization size of the spool.
Replica Spool The current utilization of the replica data spool indicated as a percentage (%) of the total Utilization size of the spool.
CCM Analog Gateway Service The Cisco CallManager (CCM) Analog Gateway service monitors the state of the different ports on the gateway that is connected to the Call Manager.
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions Systems/Applications 4.x
Device Class Server - Windows
- 101 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Properties Queried and Calculations Performed
Namepace root\cimv2
WMI Class Win32_PerfRawData_CiscoCM_CiscoCallManager
WMI Property 0 FXOPortsInService
WMI Property 1 FXOPortsActive
WMI Property 2 FXSPortsInService
WMI Property 3 FXSPortsActive
Status Details
Status Detail Description
FXO Ports in The total number of Foreign eXchange Office (FXO) ports that are currently available for Service use.
Active FXO Ports The total number of FXO ports that are currently registered with the CallManager and are in use (active).
FXO Port A calculated percentage of the FXO port utilization: Utilization (%) (FXO Ports Active * 100)/(FXO Ports Active + FXO Ports in Service)
FXS Ports in The total number of Foreign eXchange Subscriber (FXS) ports that are currently Service available for use.
FXS Ports Active The total number of FXS ports that are currently registered with the CallManager and are in use (active).
FXS Port A calculated percentage of the FXS port utilization: Utilization (%) FXS Ports Active * 100/(FXS Ports Active + FXS Ports in Service)
- 102 - N-central 10.0 Services Reference Manual
CCM Analog Gateway FXO Port Service The Cisco CallManager (CCM) Analog Gateway FXO Port service monitors the state of the FXO ports on the gateway that is connected to the Call Manager.
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows probe
Scan Interval 15 minutes
Properties Queried and Calculations Performed
Namepace root\cimv2
WMI Class Win32_PerfRawData_CiscoCM_CiscoCallManager
WMI Property FXOPortsInService 0
WMI Property FXOPortsActive 1
Status Details
Status Detail Description
FXO Ports in Service The total number of Foreign eXchange Office (FXO) ports that are currently available for use.
FXO Ports Active The total number of FXO ports that are currently registered with the CallManager and are in use (active).
FXO Port Utilization (%) A calculated percentage of the FXO port utilization: (FXO Ports Active * 100)/(FXO Ports Active + FXO Ports in Service)
CCM Analog Gateway FXS Port Service The Cisco CallManager (CCM) Analog FXS Port Gateway service monitors the state of the FXS ports on the gateway that is connected to the Call Manager.
- 103 - N-central 10.0 Services Reference Manual
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows probe
Scan Interval 15 minutes
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_CiscoCM_CiscoCallManager
WMI Property 0 FXSPortsInService
WMI Property 1 FXSPortsActive
Status Details
Status Detail Description
FXS Ports in Service The total number of Foreign eXchange Subscriber (FXS) ports that are currently available for use.
FXS Ports Active The total number of FXS ports that are currently registered with the CallManager and are in use (active).
FXS Port Utilization (%) A calculated percentage of the FXS port utilization: FXS Ports Active * 100/(FXS Ports Active + FXS Ports in Service)
CCM Annunciator Service The Cisco CallManager (CCM) Annunciator service monitors the state of the resources associated with the call recorded announcements that are connected to the CallManager.
If the Total Annunciator Resources is greater than 0, the service status is Normal.
If the Annunciator Out of Resources Incidents is 30% or less than the Total Annunciator Resources, the service status is Warning.
If the Annunciator Out of Resources Incidents is a value other than 0 and the Available Annunciator Resources percentage is 10% or less than the Total Annunciator Resources, the service status is Failed.
- 104 - N-central 10.0 Services Reference Manual
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows Probe
Scan Interval 15 minutes
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_CiscoCM_CiscoCallManager
WMI Property 0 AnnunciatorResourceTotal
WMI Property 1 AnnunciatorResourceAvailable
WMI Property 2 AnnunciatorResourceActive
WMI Property 3 AnnunciatorOutOfResources
Status Details
Status Detail Description
Total Annunciator Resources The total number of resources for all of the devices.
Available Annunciator Resources The total number of annunciator resources that are currently registered with the CallManager and are in use (active).
Active Annunciator Resources The total number of annunciator resources that are currently registered with the CallManager and are not in use (available).
Annunciator Resources Utilization (%) A calculated percentage of the annunciator resources utilization: (Active Annunciator Resources * 100) / Total Annunciator Resources
Annunciator Out of Resources Incidents The total number of attempts made to find an annunciator resource when all other registered annunciator resources were in use.
- 105 - N-central 10.0 Services Reference Manual
CCM Call Activity Service The Cisco CallManager (CCM) Call Activity service monitors the state of all calls on the Call Manager. This includes the active calls, attempted calls, calls in progress, and completed calls.
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows probe
Scan Interval 15 minutes
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_CiscoCM_CiscoCallManager
WMI Property 0 CallsActive
WMI Property 1 CallsAttempted
WMI Property 2 CallsCompleted
WMI Property 3 CallsInProgress
WMI Property 4 AuthenticatedCallsActive
WMI Property 5 AuthenticatedCallsCompleted
Scandetail.6.Recipe $activecalls + $completedcalls + $authenticatedactive + $authenticatedcompleted
Status Details
Status Detail Description
Active Calls The number of active calls.
Attempted Calls The number of attempted calls.
Completed Calls The number of completed calls.
Calls in Progress The number of calls in progress.
- 106 - N-central 10.0 Services Reference Manual
Status Detail Description
Authenticated Active Calls The total number of calls that have been authenticated and are in progress.
Authenticated Calls Completed The total number of authenticated calls that have been terminated.
Calls Active + Calls Completed Total number of calls in progress + Total number of calls terminated.
CCM Call Mgr Status Service The Cisco CallManager (CCM) Call Mgr Status service monitors the availability of the CCM sub- applications. These sub-applications include the CallManager, Call Dispatcher, TFTP Service, and Messaging Interface.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x to 6.x Systems/Applications
Device Class Server - Windows, Switch/Router
Monitoring Probe Windows probe
Scan Interval 15 minutes
ccmStatus Index The index corresponding to the row in the ccmTable that contains the ccmStatus. The index is typically a value of 1 or 2, but can also be an integer.
- 107 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Call Manager 1.3.6.1.4.1.9.9.156.1.1.2.1.5 The host name of the CallManager. Status
Call Manager 1.3.6.1.4.1.9.9.156.1.1.2.1.2 The current status of the CCM server. The CCM server is Name available if the SNMP agent received a system up event from the local CCM. The statuses are mapped as follows: Failed: 3 Warning: 0,1,4-4294967295 Normal: 2
The meaning of the statuses: 1 : Unknown – The status cannot be determined 2: Up – Call manager is up 3: Down – Call Manager is down
Call Manager 1.3.6.1.4.1.9.9.156.1.1.2.1.4 The version number of the CallManager software. Version Num- ber
Call Manager 1.3.6.1.4.1.9.9.156.1.1.2.1.8 The unique ID of the Cluster to which this CallManager Cluster Name belongs.
CCM Conf Activity Service The Cisco CallManager (CCM) Conf Activity service monitors the state of all of the conference hardware resources that are connected to the CallManager.
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows probe
Scan Interval 15 minutes
- 108 - N-central 10.0 Services Reference Manual
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_CiscoCM_CiscoCallManager
WMI Property 0 HWConferenceActive
WMI Property 1 HWConferenceCompleted
WMI Property 2 HWConferenceResourceAvailable
WMI Property 3 HWConferenceResourceActive
WMI Property 4 HWConferenceOutOfResources
Status Details
Status Details Description
Active Hardware Conferences The total number of hardware conference devices that are currently registered with the CallManager and are in use (active).
Completed Hardware Conferences The total number of hardware conferences on which conferences have been terminated.
Total Hardware Conference Resources Available Hardware Conf Resources + Active Hardware Conferences
Available Hardware Conf Resources The total number of hardware conference resources that are currently registered with the CallManager and are in use (active).
Active Hardware Conference The total number of hardware conference resources Resources that are currently registered with the CallManager and are not in use (available).
Hardware Conf Resource Utilization A calculated percentage of the hardware conference (%) resource utilization: Active Hardware Conferences * 100 / (Active Hardware Conference + Available Hardware Conf Resources)
Out of HW Conf Resources Incidents The total number of attempts made to find a hardware conference resource when all other registered hardware conference resources were in use.
- 109 - N-central 10.0 Services Reference Manual
CCM Conference Registration Service The Cisco CallManager (CCM) Conference Registration service monitors the state of all of the conference media devices that are connected to the CCM server. This includes the media that have been registered, unregistered, or have lost contact with the CCM manager. In addition, this service monitors the number of registration requests that have been rejected by the CCM server.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x to 6.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows Probe
Scan Interval 15 minutes
OID/Calculation
Metric Name OID/Calculation Description
Registered Media Devices 1.3.6.1.4.1.9.9.156.1.5.11 The total number of registered conference media devices that are present in the network.
Unregistered Media 1.3.6.1.4.1.9.9.156.1.5.12 The total number of conference devices that have Devices been removed or have lost contact with the CCM server.
Rejected Media Devices 1.3.6.1.4.1.9.9.156.1.5.13 The total number of conference devices that have been configured incorrectly.
CCM CTI Activity Service The Cisco CallManager (CCM) Computer Telephony Interface (CTI) Activity service monitors the state of the lines and devices that are connected to the CallManager.
- 110 - N-central 10.0 Services Reference Manual
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows probe
Scan Interval 15 minutes
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_CiscoCtiMgr_CiscoCTIManager
WMI Property 0 CcmLinkActive
WMI Property 1 CTIConnectionActive
WMI Property 2 DevicesOpen
WMI Property 3 LinesOpen
Status Details
Status Detail Description
CCM Links Active The total number of links that are currently registered with the CallManager and are in use (active).
CTI Connections Active The total number of links that are currently registered with the CallManager and are not in use (available).
Devices Open The total number of devices, such as hardware IP phones, CTI ports, and CTI route points that are connected to the CallManager and are controlled and/or monitored by CTI applications.
Open Lines The total number of lines that are connected to the CallManager and are controlled and/or monitored by CTI applications.
CCM CTI Registration Service The Cisco CallManager (CCM) Computer Telephony Interface (CTI) Registration service monitors the state of the CTI devices that are connected to the CCM server. This includes the CTI devices that have been registered, unregistered, or have lost contact with the CCM manager. In addition, this service monitors the number of registration requests that have been rejected by the CCM server.
- 111 - N-central 10.0 Services Reference Manual
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x to 6.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows Probe
Scan Interval 15 minutes
OID/Calculation
Metric Name OID/Calculation Description
Registered CTI 1.3.6.1.4.1.9.9.156.1.5.14 The total number of registered CTI devices that are present in Devices the network.
Unregistered CTI 1.3.6.1.4.1.9.9.156.1.5.15 The total number of CTI devices that have been removed or Devices have lost contact with the CCM server.
Rejected CTI 1.3.6.1.4.1.9.9.156.1.5.16 The total number of CTI devices that have been configured Devices incorrectly.
Object Identifiers (OIDs)
l 1.3.6.1.4.1.9.9.156.1.5.14 ccmRegisteredCTIDevices
l 1.3.6.1.4.1.9.9.156.1.5.15 ccmUnregisteredCTIDevices
l 1.3.6.1.4.1.9.9.156.1.5.16 ccmRejectedCTIDevices
CCM Gateway Registration Service The Cisco CallManager (CCM) Gateway Registration service monitors the state of all gateway devices that are connected to the CCM server. This includes the gateway devices that have been registered, unregistered, or have lost contact with the CCM manager. In addition, this service monitors the number of registration requests that have been rejected by the CCM server.
Note: This service cannot use N-central’s Self-Healing feature.
- 112 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x to Systems/Applications 6.x
Device Class Server - Windows
Monitoring Probe Windows Probe
Scan Interval 15 minutes
OID/Calculation
Metric Name OID/Calculation Description
Registered 1.3.6.1.4.1.9.9.156.1.5.8 The total number of gateways that are registered with the CCM Gateways server.
Unregistered 1.3.6.1.4.1.9.9.156.1.5.9 The total number of unregistered gateways that have been Gateways removed or have lost contact with the CCM server.
Rejected 1.3.6.1.4.1.9.9.156.1.5.10 The total number of gateways that have been configured Gateways incorrectly.
CCM Group Table (Cisco) Service The CCM Group Table (Cisco) service monitors the name of the CallManager Group and whether or not the group is the default TFTP server group.
Service Type SNMP
Instances on a Device 1
Supported Any Cisco device that provides VPN capabilities. Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 30 minutes
ccmGroupName Type the name of the CUCM (Cisco Unified Communications Manager) server. For a list of the ccmGroup attached to a CUCM server, query 1.3.6.1.4.1.9.9.156.1.1.1.1.2 SNMP OID.
- 113 - N-central 10.0 Services Reference Manual
Status Detail Object Descriptors Numerical OID Description
CUCM ccmGroupName 1.3.6.1.4.1.9.9.156.1.1.1.1.2 Identifies the CallManager ccmGroupName Group.
CUCM ccmGroupTft- ccmGroupTftpDefault 1.3.6.1.4.1.9.9.156.1.1.1.1.3 Identifies whether or not the pDefault group is the default TFTP server group.
CCM ISDN - Basic Rate Interface Service The Cisco CallManager (CCM) ISDN - Basic Rate Interface service monitors the utilization of Basic Rate Interface (BRI) trunks.
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows probe
Scan Interval 15 minutes
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_CiscoCM_CiscoCallManager
WMI Property 0 BRIChannelsActive
WMI Property 1 BRISpansInService
Status Details
Status Detail Description
Active BRI Voice Channels The number of active calls on the BRI trunk.
BRI Spans in Service The number of available BRI trunk spans.
BRI Utilization (%) A calculated percentage of the BRI utilization: Active BRI Voice Channels * 100 / BRI Spans in Service * 2
- 114 - N-central 10.0 Services Reference Manual
CCM ISDN - Primary Rate Interface Service The Cisco CallManager (CCM) ISDN - Primary Rate Interface service monitors the utilization of ISDN Primary Rate Interface (PRI) trunks.
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows probe
Scan Interval 15 minutes
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_CiscoCM_CiscoCallManager
WMI Property 0 PRIChannelsActive
WMI Property 1 PRISpansInService
Status Details
Status Detail Description
Active PRI Voice Channels The number of active calls on the PRI trunk.
PRI Spans in Service The number of available PRI trunk spans.
PRI Utilization (%) A calculated percentage of the PRI utilization: Active PRI Voice Channels * 100 / PRI Spans in Service * 23
CCM ISDN - T1 Trunks Service The Cisco CallManager (CCM) ISDN - T1 Trunks service monitors the utilization of T1 trunks.
- 115 - N-central 10.0 Services Reference Manual
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows probe
Scan Interval 15 minutes
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_CiscoCM_CiscoCallManager
WMI Property 0 PRIChannelsActive
WMI Property 1 PRISpansInService
WMI Property 2 T1ChannelsActive
WMI Property 3 T1SpansInService
WMI Property 4 BRIChannelsActive
WMI Property 5 BRISpansInService
Scandetail.2.Recipe $prichannelsactive 100 * $prispansinservice 23 * /
Scandetail.8.Recipe $brichannelsactive 100 * $brispansinservice 2 * /
Status Details
Status Detail Description
Active T1 CAS Voice Channels The number of active calls on the T1 trunk.
T1 CAS Spans in Service The number of available T1 trunk spans.
T1 Utilization (%) A calculated percentage of the T1 utilization: Active T1 CAS Voice Channels * 100 / T1 CAS Spans in Service * 24
- 116 - N-central 10.0 Services Reference Manual
CCM MGCP Gateway Service The CCM MGCP Gateway service monitors the registration status and D Channel status of an MGCP gateway. A Call Manager is up if the SNMP Agent received a system up event from the local CCM.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x to 6.x Systems/Applications
Device Class Server - Windows, Server - Generic
Monitored By Windows Probe
Scan Interval 5 minutes
MGCP Gateway Name Enter the name of the MGCP Gateway to be monitored. For a list of the gateways attached to the CCM server, query the CCM server with the 1.3.6.1.4.1.9.9.156.1.3.1.1.2 SNMP OID.
- 117 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Description OID/Calculation Name
Description 1.3.6.1.4.1.9.9.156.1.3.1.1.4
Status 1.3.6.1.4.1.9.9.156.1.3.1.1.5 The Status metric is a mapped value: Normal: 2 Warning: 3,5 Failed: 1,4
The meaning of the statuses: 1: Unknown 2: Registered 3: Unregistered 4: Rejected 5: Partially Registered
Status 1.3.6.1.4.1.9.9.156.1.3.1.1.5 Describes the status as: Description Unknown Registered Unregistered Rejected Partially Registered
D Channel 1.3.6.1.4.1.9.9.156.1.3.1.1.14 The D-Channel number of the gateway. A value of -1 in this Number field indicates that the DChannel number is not applicable for this gateway.
- 118 - N-central 10.0 Services Reference Manual
Metric Description OID/Calculation Name
D Channel 1.3.6.1.4.1.9.9.156.1.3.1.1.13 The D-Channel status of the gateway. Status The statuses are as follows
1: The D-Channel is up
2: The D-Channel is down
3: The D-Channel status is unknown
4: The D-channel status is not applicable for this gateway. This metric has the following thresholds:
Normal: 2
Warning: 3,5
Failed: 1,4
D Channel 1.3.6.1.4.1.9.9.156.1.3.1.1.13 The statuses are as follows: Status 1: The D-Channel is up Reason 2: The D-Channel is down
3: The D-Channel status is unknown
4: The D-channel status is not applicable for this gateway.
CCM MTP - Transcoder Service The Cisco CallManager (CCM) Media Termination Point (MTP) - Transcoder service monitors the state of the transcoder resources that are available to the CallManager.
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows probe
Scan Interval 15 minutes
- 119 - N-central 10.0 Services Reference Manual
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_CiscoCM_CiscoCallManager
WMI Property 0 MTPResourceActive
WMI Property 1 MTPResourceAvailable
WMI Property 2 MTPOutOfResources
WMI Property 3 TranscoderResourceActive
WMI Property 4 TranscoderResourceAvailable
WMI Property 5 TranscoderOutOfResources
Status Details
Status Detail Description
Total MTP Resources The total of active and available MTP resources: Active MTP Resources + Available MTP Resources
Active MTP Resources The total number of MTP resources that are currently registered with the CallManager and are in use (active).
Available MTP Resources The total number of MTP resources that are currently registered with the CallManager and are not in use (available).
MTP Resource Utilization (%) A calculated percentage of the MTP resource utilization: Active MTP Resources * 100 / (Active MTP Resources + Available MTP Resources)
MTP Out of Resources Incidents The total number of attempts made to find an MTP resource when all other registered MTP resources were in use.
Total Transcoder Resources The total number of active and available transcoder resources: Active Transcoder Resources + Available Transcoder Resources
- 120 - N-central 10.0 Services Reference Manual
Status Detail Description
Active Transcoder Resources The total number of transcoder resources that are currently registered with the CallManager and are in use (active).
Available Transcoder Resources The total number of transcoder resources that are currently registered with the CallManager and are not in use (available).
Transcoder Resource Utilization (%) A calculated percentage of the transcoder resource utilization: Active Transcoder Resources * 100 / (Active Transcoder Resources + Available Transcoder Resources)
Transcoder Out of Resources The total number of attempts made to find a transcoder Incidents resources when all other registered MTP resources were in use.
CCM Media Device Service The CCM Media Device service monitors the status of the specified CCM Voicemail device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x to 6.x Systems/Applications
Device Class Server - Windows, Server - Generic
Monitored By Probe
Scan Interval 5 minutes
Media Device Name Type the name of the media device to be monitored. For a list of the media devices attached to the CCM server, query the CCM server with the 1.3.6.1.4.1.9.9.156.1.6.1.1.2 SNMP OID.
- 121 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Description 1.3.6.1.4.1.9.9.156.1.6.1.1.4
Status 1.3.6.1.4.1.9.9.156.1.6.1.1.5 The Status metric is a mapped value: Normal: 2 Warning: 1,3,4,5
The meaning of the values is as follows: 1: Unknown 2: Registered 3: Unregistered 4: Rejected 5: Partially Registered
Status Description 1.3.6.1.4.1.9.9.156.1.6.1.1.5 Describes the status as one of the following: Unknown Registered Unregistered Rejected Partially Registered
CCM Music on Hold Service The Cisco CallManager (CCM) Music on Hold (MoH) service monitors the state of the MoH resources that are connected to the CallManager.
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows probe
Scan Interval 15 minutes
- 122 - N-central 10.0 Services Reference Manual
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_CiscoCM_CiscoCallManager
WMI Property 0 MOHTotalMulticastResources
WMI Property 1 MOHMulticastResourceActive
WMI Property 2 MOHMulticastResourceAvailable
WMI Property 3 MOHOutOfResources
WMI Property 4 MOHTotalUnicastResources
WMI Property 5 MOHUnicastResourceActive
WMI Property 6 MOHUnicastResourceAvailable
Status Details
Status Detail Description
Total Multicast Resources The total number of MoH multicast resources that are currently registered with the CallManager.
Active Multicast Resources The total number of MoH multicast resources that are currently registered with the CallManager and are in use (active).
Available Multicast The total number of MoH multicast resources that are currently Resources registered with the CallManager and are not in use (available).
Multicast Resource A calculated percentage of the multicast resource utilization: Utilization (%) Active Multicast Resources * 100 / Total Multicast Resources
Out of Resources The total number of attempts made to find an MoH resource when all other registered MoH resources were in use.
- 123 - N-central 10.0 Services Reference Manual
Status Detail Description
Total Unicast Resources The total number of unicast MoH resources that are registered with the CallManager.
Active Unicast Resources The total number of unicast MoH resources that are currently registered with the CallManager and are in use (active).
Available Unicast Resources The total number of unicast MoH resources that are currently registered with the CallManager and are not in use (available).
Unicast Resource Utilization A calculated percentage of the unicast resource utilization: (%) Active Unicast Resource * 100 / Total Unicast Resources
CCM Performance Service The Cisco CallManager (CCM) Performance service monitors key performance indicators on the CallManager. This includes:
l the average expected delay before calls are answered;
l the number of calls rejected due to call throttling; and
l metrics on code entry and exit conditions.
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows probe
Scan Interval 15 minutes
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_CiscoCM_CiscoCallManagerSystemPerformance
WMI Property 0 AverageExpectedDelay
WMI Property 1 CallsRejectedDueToThrottling
WMI Property 2 CodeRedEntryExit
WMI Property 3 CodeYellowEntryExit
- 124 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Average Expected Delay (ms) The CallManager's delay in responding to the calls.
Calls rejected due to call throttling The Number of calls rejected due to call throttling.
Code Red Entry and Exit The number of times the CallManager fails.
Code Yellow Entry and Exit The number of warnings that are displayed before CallManager failure.
CCM Phone Service The CCM Phone service monitors the status and IP address of the specified phone.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 100
Supported Cisco® CallManager Versions 4.x to 6.x Systems/Applications
Device Class Server - Windows
Monitored By Windows Probe
Scan Interval 5 minutes
Phone You need to specify the name of the phone to be monitored. For a list of the phones asso- ciated with the CCM server, query the server with the 1.3.6.1.4.1.9.9.156.1.2.1.1.4 SNMP OID.
- 125 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Status 1.3.6.1.4.1.9.9.156.1.2.1.1.7 The Status metric is mapped as follows:
Normal: 2 Warning: 5 Failed: 1,3,4
Status Description 1.3.6.1.4.1.9.9.420.1.2.2.1.7 The description of the statuses: 1: Unknown 2: Registered 3: Unknown 4: Rejected 5: Partially Registered
IP Address 1.3.6.1.4.1.9.9.156.1.2.1.1.6
CCM Phone Registration Service The Cisco CallManager (CCM) Phone Registration service monitors the presence of all phones that are connected to the CCM server. This includes the phones that have been registered, unregistered, or have lost contact with the CCM manager. In addition, this service monitors the number of registration requests that have been rejected by the CCM server.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x to 6.x Systems/Applications
Device Class Server - Windows
Monitoring Probe Windows Probe
Scan Interval 15 minutes
- 126 - N-central 10.0 Services Reference Manual
OID/Calculation
Status Detail OID/Calculation Description
Registered 1.3.6.1.4.1.9.9.156.1.5.5 The registered phone instruments that are present in the Phones network.
Unregistered 1.3.6.1.4.1.9.9.156.1.5.6 The phones that have been removed or have lost contact with Phones the CCM server.
Rejected Phones 1.3.6.1.4.1.9.9.156.1.5.7 The phones that have been configured incorrectly.
Object Identifiers (OIDs)
l 1.3.6.1.4.1.9.9.156.1.5.5 ccmRegisteredPhones
l 1.3.6.1.4.1.9.9.156.1.5.6 ccmUnregisteredPhones
l 1.3.6.1.4.1.9.9.156.1.5.7 ccmRejectedPhones
CCM Server Service The Cisco CallManager (CCM) Server service monitors the server on which the Cisco CallManager application is installed. The service merges the CPU (WMI), Disk (WMI), and Memory (WMI) services and monitors the CPU, Disk, and Memory utilization of the CallManager through one task.
If there are multiple CPUs, an average of the CPU utilization is calculated and, similarly, if there are multiple disks, an average Disk utilization is calculated. There is only one memory pool on the x86 platform, therefore, an average of the memory utilization does not need to be calculated.
If you would like to monitor a specific CPU or disk, set the CPU (WMI) or Disk (WMI) service on the CallManager.
Service Type WMI
Instances on a Device 1
Supported Cisco® CallManager Versions Systems/Applications 4.x
Device Class Server - Windows
Monitoring Probe Windows probe
Scan Interval 15 minutes
- 127 - N-central 10.0 Services Reference Manual
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_Processor
WMI Property 0 LoadPercentage
Namespace root\cimv2
WMI Class Win32_Processor
WMI Property 0 LoadPercentage
NameSpace root\cimv2
WMI Class Win32_LogicalDisk
WMI Property 0 Size
WMI Property 1 FreeSpace
Namespace root\cimv2
WMI Class Win32_OperatingSystem
WMI Property 0 TotalVirtualMemorySize
WMI Property 1 TotalVisibleMemorySize
WMI Property 2 FreeVirtualMemory
WMI Property 3 FreePhysicalMemory
- 128 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
CPU Utilization (%) A calculated percentage of the CPU utilization: Sum of Processor.LoadPercentage / Count of Processor Objects
Free Disk Space A calculated percentage of the free disk space utilization: Sum of LogicalDisk.FreeSpace / 1000
Disk Utilization (%) A calculated percentage of the disk utilization: (Sum of LogicalDisk.Size - Sum of LogicalDisk.FreeSpace) * 100 / Sum of LogicalDisk.Size
Physical Memory A calculated percentage of the physical memory utilization: Utilization (%) (OperatingSystem.TotalVisibleMemorySize - OperatingSystem.FreePhysicalMemory) * 100 / OperatingSystem.TotalVisibleMemorySize
Virtual Memory A calculated percentage of the virtual memory utilization: Utilization (%) (OperatingSystem.TotalVirtualMemorySize - OperatingSystem.FreeVirtualMemory) * 100 / OperatingSystem.TotalVirtualMemorySize
CCM Table (Cisco) Service The CCM Table (Cisco) service monitors the availability of the applications used to deliver a specific IP Telephony solution.
Service Type SNMP
Instances on a Device 1
Supported Any Cisco device that provides VPN capabilities. Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 30 minutes
Index for ccmStatus Type the index corresponding to the row in the ccmTable that contains the ccmStatus. The index is typically 1, but can also be any integer. The ccmStatus is the current status of the Unified Communication Manager.
- 129 - N-central 10.0 Services Reference Manual
Status Detail Object Numerical OID Description Descriptors
CUCM ccmStatus 1.3.6.1.4.1.9.9.156.1.1.2.1. The current status of the ccmStatus 5 CallManager. A CallManager is running properly if the SNMP Agent received a 'system up' event from the local CUCM server.
The status of the CallManager is mapped as follows:
l Unknown - the current status of the CallMan- ager is not currently known.
l Up - the CallManager is currently running and is able to communicate with other CallManagers.
l Down - the CallManager is not running or the Agent is unable to com- municate with the local CallManager.
CUCM ccmVersion 1.3.6.1.4.1.9.9.156.1.1.2.1. Identifies the version number of ccmVersion 4 the CallManager software.
CUCM ccmClusterId 1.3.6.1.4.1.9.9.156.1.1.2.1. Provides the unique ID ccmClusterID 8 (identifier) of the cluster to which the target CallManager belongs. At any point in time, the Cluster ID helps in associating a CallManager to any given Cluster.
- 130 - N-central 10.0 Services Reference Manual
Status Detail Object Numerical OID Description Descriptors
CUCM Status ccmStatus 1.3.6.1.4.1.9.9.156.1.1.2.1. The current status of the (Mapped) 5 CallManager. A CallManager is running properly if the SNMP Agent received a 'system up' event from the local CUCM server.
The status of the CallManager is mapped as follows:
l Unknown - the current status of the CallMan- ager is not currently known.
l Up - the CallManager is currently running and is able to communicate with other CallManagers.
l Down - the CallManager is not running or the Agent is unable to com- municate with the local CallManager.
CUCM ccmInetAddres 1.3.6.1.4.1.9.9.156.1.1.2.1. Identifies the IP address of the ccmInetAddres s 7 Cisco Call Manager. The type of s address for this is identified by ccmInetAddressType.
CUCM ccmInetAddres 1.3.6.1.4.1.9.9.156.1.1.2.1. Identifies the additional IP ccmInetAddres s2 10 (v4/v6) address details of Cisco s2 Unified Communications Manager. The type of address for this object is identified by ccmInetAddress2Type.
CUCM ccmDescriptio 1.3.6.1.4.1.9.9.156.1.1.2.1. The description for the ccmDescription n 3 CallManager.
CCM Voicemail Device Service The CCM Voicemail Device service monitors the status of the specified CCM Voicemail device.
Note: This service cannot use N-central’s Self-Healing feature.
- 131 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x to 6.x Systems/Applications
Device Class Server - Windows, Server - Generic
Monitored By Windows probe, Windows agent
Scan Interval 5 minutes
Voicemail Device Name Enter the name of the voicemail device to be monitored. For a list of the voicemail devices attached to the CCM server, query the CCM server with the 1.3.6.1.4.1.9.9.156.1.12.1.1.2 SNMP OID.
OID/Calculation
Metric Description OID/Calculation Name
Device 1.3.6.1.4.1.9.9.156.1.12.1.1.4 The description of the Voice Messaging Device. This description Description is given when the Voice Messaging Device is configured in the CCM.
Status 1.3.6.1.4.1.9.9.156.1.12.1.1.5 The Status metric is a mapped value: Normal: 2 Warning: 5 Failed: 1,3,4
Meanings are as follows: 1 = Unknown 2 = Registered 3 = Unregistered 4 = Rejected 5 = Partially Registered
Status 1.3.6.1.4.1.9.9.156.1.12.1.1.5 Describes the status as one of: Description Unknown Registered Unregistered Rejected Partially Registered
Status 1.3.6.1.4.1.9.9.156.1.12.1.1.9 The reason for the current status of the voicemail device. Reason
- 132 - N-central 10.0 Services Reference Manual
CCM VoiceMail Registration Service The Cisco CallManager (CCM) VoiceMail Registration service monitors the presence of the voice mail devices that are connected to the CallManager. This includes voice mail devices that have been registered, become unregistered, or have lost contact with the CCM server. In addition, this service monitors the number of registration requests that have been rejected by the CCM server.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Cisco® CallManager Versions 4.x to Systems/Applications 6.x
Device Class Server - Windows
Monitoring Probe Windows Probe
Scan Interval 15 minutes
OID/Calculation
Metric Name OID/Calculation Description
Registered Voice Mail 1.3.6.1.4.1.9.9.156.1.5.17 The registered voice mail devices that are present in the Devices network.
Unregistered Voice 1.3.6.1.4.1.9.9.156.1.5.18 The voice mail devices that have been removed or have Mail Devices lost contact with the CCM server.
Rejected Voice Mail 1.3.6.1.4.1.9.9.156.1.5.19 The voice mail devices that have been configured Devices incorrectly.
Chassis Intrusion (Dell iDRAC) Service The Chassis Intrusion (Dell iDRAC) service monitors the chassis security feature that detects if a chassis component is removed or replaced from a Dell PowerEdge server using the embedded integrated Dell Remote Access Controller (iDRAC).
- 133 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 100
Supported Dell PowerEdge servers with integrated Dell Remote Access Controller Systems/Applications (iDRAC)
Device Class for CPU (SNMP) Servers - Management Interface
Monitored By Windows Agent
Scan Interval 15 minutes
SNMP Index Type or select the name of the SNMP Index to be used by this service.
- 134 - N-central 10.0 Services Reference Manual
Object Status Descriptor Numerical OID Description Detail s
Statu $Status 1.3.6.1.4.1.674.10892.5.4.300.70. Indicates the current status of the s 1.5 chassis intrusion sensor mapped as follows:
1 - other,
2 - unknown,
3 - ok,
4 - nonCritical,
5 - critical, and,
6 - nonRecoverable.
Readi $Reading 1.3.6.1.4.1.674.10892.5.4.300.70. Indicates where or not the chassis ng 1.6 intrusion sensor is currently being read mapped as follows:
1 - chassisNotBreached,
2 - chassisBreached,
3 - chassisBreachedPrior, and,
4 - chassisBreachSensorFailure.
Type $Type 1.3.6.1.4.1.674.10892.5.4.300.70. Indicates the type of the intrusion sensor 1.7 being used for chassis security mapped as follows:
1 - chassisBreachDetectionWhenPower ON, and,
2 - chassisBreachDetectionWhenPower OFF.
- 135 - N-central 10.0 Services Reference Manual
Object Status Descriptor Numerical OID Description Detail s
Settin $Setting 1.3.6.1.4.1.674.10892.5.4.300.70. Indicates the current state settings of the gs 1.4 intrusion sensor mapped as follows:
1 - unknown,
2 - enabled,
4 - notReady, and
6 - enabledAndNotReady.
Cisco - Connections Service The Cisco - Connections service monitors the number of connections currently in use by the Cisco firewall.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Cisco PIX and Cisco ASA firewalls Systems/Applications
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, and Server - Windows
Monitored By Windows Probe
Scan Interval 15 minutes
- 136 - N-central 10.0 Services Reference Manual
Cisco Firewall The index corresponding to the following string: number of connections currently in Connection Stat use by the entire firewall, which is determined by performing an SNMP walk on the Description Index cfwConnectionStatTable and locating the cfwConnectionStatDescription (.1.3.6.1.4.1.9.9.147.1.2.2.2.1.3).
Cisco Firewall The following string: number of connections currently in use by the entire firewall. Connection Stat Description Value
Cisco Firewall The index corresponding to the following string: highest number of connections in use Connection Stat at any one time since system startup, which is determined by performing an SNMP walk Index on the cfwConnectionStatTable and locating cfwConnectionStatDescription (.1.3.6.1.4.1.9.9.147.1.2.2.2.1.3).
Cisco Firewall The following string: highest number of connections in use at any one time since Connection Stat system startup. Description
OID/Calculation
Metric Name OID/Calculation Description
Current 1.3.6.1.4.1.9.9.147.1.2.2.2.1.5 The number of connections currently in use by the entire Connections firewall.
Max 1.3.6.1.4.1.9.9.147.1.2.2.2.1.5 The highest number of connections in use at any one time Connections since system startup.
To configure Cisco - Connections
Walk the cfwConnectionStatTable table and look at cfwConnectionStatDescription.
Example:
# snmpwalk -Cp -On -c public -v1 10.150.1.20 .1.3.6.1.4.1.9.9.147.1.2.2.2.1.3
.1.3.6.1.4.1.9.9.147.1.2.2.2.1.3.40.6 = STRING: "number of connections currently in use by the entire firewall"
.1.3.6.1.4.1.9.9.147.1.2.2.2.1.3.40.7 = STRING: "highest number of connections in use at any one time since system startup"
Variables found: 2
The default strings for the two parameters in the UI must correspond to these values.
- 137 - N-central 10.0 Services Reference Manual
Memory - Cisco Service Memory - Cisco monitors memory pool utilization on any Cisco device using SNMP. The device must publish its memory usage in the CISCO-MEMORY-POOL-MIB.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a 1 Device
Device Class Switch/Router
Monitored By SNMP (Windows Probe)
Scan Interval 15 minutes
Cisco Memory The index of the textual name assigned to the memory pool, which is determined by Pool Name performing an SNMP walk on ciscoMemoryPoolName (.1.3.6.1.4.1.9.9.48.1.1.1.2). Index
Cisco Memory The value of the textual name assigned to the memory pool, which is determined by Pool Name performing an SNMP walk on ciscoMemoryPoolName (.1.3.6.1.4.1.9.9.48.1.1.1.2). Value
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation Description
Name 1.3.6.1.4.1.9.9.48.1.1.1.2 The name of the memory pool being monitored.
Used 1.3.6.1.4.1.9.9.48.1.1.1.5 The amount of used memory.
Free 1.3.6.1.4.1.9.9.48.1.1.1.6 The amount of free memory.
Total Used + Free The total memory for that memory pool.
% Memory [Used / (Used + Free)] x 100 The utilization of memory as a percentage of total Utilization memory.
Cisco Unity Express Mailbox Service The Cisco Unity Express Mailbox service monitors the capacity (in minutes), available time, number of messages, and status (enabled or disabled) of the specified mailbox.
- 138 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Cisco Call Unity Express Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
Voicemail Box Enter the name of the voicemail box to be monitored. For a list of the voicemail boxes associated with the CCM Unity Express server, query the server with the .1.3.6.1.4.1.9.9.420.1.2.2.1.2 SNMP OID.
OID/Calculation
Metric Name OID/Calculation Description
Mailbox Size 1.3.6.1.4.1.9.9.420.1.2.2.1.6
Mailbox Time Used 1.3.6.1.4.1.9.9.420.1.2.2.1.7
Mailbox Time Used (percentage of time used) 1.3.6.1.4.1.9.9.420.1.2.2.1.8
Is Voicemail Enabled? 1.3.6.1.4.1.9.9.420.1.2.2.1.16
Number of Messages 1.3.6.1.4.1.9.9.420.1.2.2.1.9
Citrix® Presentation Server Service The Citrix Presentation Server service monitors the availability of the port on which the Citrix Metaframe Presentation Server application runs. The availability of the port, which is determined by the service testing the port's connectivity, indicates that the Citrix Metaframe Presentation Server application is running. This service also measures the domain name system (DNS) resolution and the round trip time of the initial connection request and response. The availability results of the TCP service are then reflected on the status dashboard for the Citrix Presentation Server service.
A maximum of three instances of this service can be set on a device, with each instance monitoring a different port on the device.
Note: The Citrix Presentation Server service does not use the Warning state.
- 139 - N-central 10.0 Services Reference Manual
Service Type Generic TCP
Instances on a Device 3
Supported Citrix MetaFrame® Presentation Systems/Applications
Device Class Server - Generic, Workstation - Generic, Novell, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Probe
Scan Interval 5 minutes
Timeout Value The time (in seconds) that the N-central server waits before considering the test a failure. The default is 30 seconds.
Port Number The TCP port number used to monitor the Citrix Presentation Server service.
Status Details
Status Detail Description
Citrix Presentation The threshold that determines the availability of the port. Server service Availability
Average Round Trip The time (in milliseconds) for a request to be sent and received. Time (ms)
Generic DNS The threshold that determines whether the device name can be resolved. Resolution If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings. If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
Connections – Watchguard Service The Connections - Watchguard service the number of active connections and the number of dropped connections going through a Watchguard device.
- 140 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Any device compliant with the WATCHGUARD-SYSTEM-STATISTICS Systems/Applications MIB
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Metric Name OID/Calculation Description
Active Connections 1.3.6.1.4.1.3097.6.3.80
Dropped Connections 1.3.6.1.4.1.3097.6.3.34
Connectivity Service The Connectivity services monitors whether or not a device is accessible on the network. By querying the device with ICMP (Internet Control Message Protocol) packets, the Connectivity service can alert you when the device is not accessible from the network in the same manner as the "ping" command.
Warning! The connectivity service may not function properly when monitored by probes installed on systems using Windows Vista. This is due to the default setting in Windows Firewall with Advanced Security that does not allow incoming ICMP Echo messages. This may be resolved by enabling ICMP Echo messages through the creation of new inbound custom rules to allow ICMPv4 and ICMPv6 Echo Requests. For more information, refer to Microsoft documentation on Windows Firewall with Advanced Security.
Changes made to the Connectivity service for N-central 9.5 have modified how the service tolerates dropped data packets. If previously modified to be more tolerant of dropped data packets, existing deployments of the Connectivity service may need to be revised if they are overly tolerant of lost packets as these tolerances will be cumulative with the modifications made to the service.
- 141 - N-central 10.0 Services Reference Manual
Service TCP/ICMP Type
Instances 1 on a Device
Device Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Class Windows, Server - Windows, and Workstation - Windows
Monitored Windows probe, Central Server By
Scan 5 minutes Interval
Timeout The time (in seconds) that the N-central server waits before considering the test a failure. The Value default is 30 seconds.
Packet The time (in milliseconds) between packets. The default is 1 millisecond. Interval Note: To define the packet interval in full seconds, the value must be expressed in units of one thousand. For example, a packet interval of 2000 will be 2,000 milliseconds or two (2) seconds.
Packet The number of packets to send for each scan. The default is 5. Number
Packet The number of data bytes in each packet. The default is 32. Size
Default TTL (time to live) is the number of hops that a data packet must take before being discarded or TTL returned. The default is 255
- 142 - N-central 10.0 Services Reference Manual
Status Details
Status Description Details
Packet Loss A packet is dropped when its TTL value reaches zero or when the remote host is unreachable. (percentage) When a packet is dropped, the echoed packet is never received.
Time to Live A state transition for the service occurs when the threshold value exceeds the specified range (hops) for any of these threshold types.
Round Trip The time (in milliseconds) for a request to be sent and received. Time (ms)
DNS The threshold that determines whether the device name can be resolved. Resolution If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings. If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
CPU Service The CPU service monitors the utilization rate of the central processing unit (CPU) on a device. Depending on the device, the CPU service will gather information using one of the following methods:
l Local API call,
l SNMP, or,
l WMI.
Note: If an Agent is installed on the device, local API calls will be used to collect data.
For information on the CPU (Cisco) service, please refer to CPU (Cisco) Service on page 145.
Service Type Local API SNMP WMI
Instances on a Device 8
Supported Windows devices Windows devices and devices that Windows devices Systems/Applications support the HOST-RESOURCES MIB
Device Class for CPU Server - Generic, Server - Generic, Workstation - Gen- Laptop - Windows, (Local API) Workstation - Generic, eric, Other, Printer, Scanner/Camera, Laptop - Windows, Laptop - Windows, Switch/Router, Laptop - Windows, Server - Windows, Server - Windows, and Server - Windows, and Workstation - and Workstation - Workstation - Windows Windows Windows
- 143 - N-central 10.0 Services Reference Manual
Monitored By Agent (Windows) Probe, Agent (Red Hat Enterprise Probe, Agent (Win- Linux or Mac OSX 10.x) dows)
Scan Interval 60 minutes
Processor Number The ID number of the n/a n/a processor that you would like to monitor.
Processor Index n/a The index of the processor to mon- n/a itor.
Processor Name A unique identifier, which represents the processor.
Properties Queried and Calculations Performed (WMI only)
Namespace root\cimv2
WMI Class Win32_Processor
WMI Property 0 LoadPercentage
OID/Calculation (SNMP only)
Metric Name OID/Calculation Description
CPU Usage 1.3.6.1.2.1.25.3.3.1.2 The usage of the CPU, expressed as a (%) percentage.
To configure the Processor Index
To obtain the processor index, walk the object ID .1.3.6.1.2.1.25.3.3.1.2 on the target device's address to determine which indices are available for monitoring.
Example:
.1.3.6.1.2.1.25.3.3.1.2.1 50
.1.3.6.1.2.1.25.3.3.1.2.2 10
There are two indices in this case-"1" and "2".
To monitor both processors, add the service to the device and enter 1 for the Processor Index. Add the service a second time and enter 2 for the Processor Index.
CPU (ADTRAN) service The CPU (ADTRAN) service monitors the utilization rate of the CPU on ADTRAN Switch/Router devices.
- 144 - N-central 10.0 Services Reference Manual
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported ADTRAN Switch/Router Systems/Applications devices
Device Class Switch/Router
Monitored By Windows Probes
Scan Interval 5 minutes
OID/Calculation
Metric Description OID/Calculation Name
CPU Usage 1.3.6.1.4.1.664.5.53.1.4.4 CPU usage as a percentage of total CPU, compared to threshold (%) values.
CPU (Cisco) Service The CPU (Cisco) service monitors the CPU usage on Cisco devices that support CISCO-PROCESS-MIB. For information on other CPU services, please refer to CPU Service on page 143.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 32
Supported Any Cisco device that supports CISCO-PROCESS-MIB Systems/Applications
Device Class for CPU Switch/Router (SNMP)
Monitored By Windows Probes
Scan Interval 15 minutes
CPU Index The SNMP index of the CPU, which is determined by performing an SNMP walk on cpmCPUTotal5sec (.1.3.6.1.4.1.9.9.109.1.1.1.1.3).
- 145 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
% CPU Utilization (5 1.3.6.1.4.1.9.9.109.1.1.1.1.3 How busy the CPU was over the last 5 seconds as a Seconds) percentage of its capacity.
% CPU Utilization (1 1.3.6.1.4.1.9.9.109.1.1.1.1.4 How busy the CPU was over the last 1 minute as a Minute) percentage of its capacity.
% CPU Utilization (5 1.3.6.1.4.1.9.9.109.1.1.1.1.5 How busy the CPU was over the last 5 minutes as a Minutes) percentage of its capacity.
CPU Status (Dell iDRAC) Service The CPU Status (Dell iDRAC) service monitors the health of a physical CPU on a Dell PowerEdge server using the embedded integrated Dell Remote Access Controller (iDRAC).
Service Type SNMP
Instances on a 100 Device
Supported Dell PowerEdge servers with integrated Dell Remote Access Controller (iDRAC) Systems/Applicatio ns
Device Class for Servers - Management Interface CPU (SNMP)
Monitored By Windows Agent
Scan Interval 15 minutes
SNMP Value Type or select the name of the CPU to be monitored in the format ProcessorFQDD (Fully Qualified Device Descriptor) of each processor device. For a list of CPUs, query the device with the .1.3.6.1.4.1.674.10892.5.4.1100.30.1.26 SNMP OID.
- 146 - N-central 10.0 Services Reference Manual
Status Object Numerical OID Description Detail Descriptors
Name $DeviceBrandNa 1.3.6.1.4.1.674.10892.5.4.1100.30.1. Indicates the brand name and me 23 model of the processor device.
Statu $Status 1.3.6.1.4.1.674.10892.5.4.1100.30.1. Indicates the current status of s 5 the processor device mapped as follows:
1 - other,
2 - unknown,
3 - ok,
4 - nonCritical,
5 - critical, and,
6 - nonRecoverable.
CPU Status (Fujitsu) Service The CPU Status (Fujitsu) service monitors the health of a physical CPU on a Fujitsu server.
Service Type SNMP
Instances on a Device 100
Supported Fujitsu workstations, laptops or servers running the Fujitsu ServerView agent. Systems/Applications
Device Class for CPU Servers - Generic or Servers - Windows (SNMP)
Monitored By Windows Agent
CPU Name Type the name of the CPU to be monitored. For a list of CPUs, query the device with the .1.3.6.1.4.1.231.2.10.2.2.10.6.4.1.3 SNMP OID.
Scanning The scan interval can be configured according to either a Once a Day or Daily Interval schedule.
- 147 - N-central 10.0 Services Reference Manual
Object Descriptors Numerical OID
$Status 1.3.6.1.4.1.231.2.10.2.2.10.6.4.1.4
$Model 1.3.6.1.4.1.231.2.10.2.2.10.6.4.1.5
$Manufacturer 1.3.6.1.4.1.231.2.10.2.2.10.6.4.1.6
$Cores 1.3.6.1.4.1.231.2.10.2.2.10.6.4.1.9
$ConfigurationStatus 1.3.6.1.4.1.231.2.10.2.2.10.6.4.1.17
Status Description Detail
Status Describes the current status of the CPU that is being monitored with values mapped as follows:
1. unknown - CPU status could not be evaluated 2. not-present - CPU socket is empty 3. ok - CPU is available and working properly 4. disabled - CPU was manually disabled in BIOS setup 5. error - CPU has encountered errors but is still in use 6. failed - CPU has failed and is disabled 7. missing-termination - CPU socket needs a terminator module when not populated but the terminator is missing 8. prefailure-warning - CPU has encountered too many correctable errors within a cer- tain time period and is predicted to fail in near future
Model The model name of the CPU that is being monitored (for example, Pentium Xeon).
Manufacturer The name of the manufacturer of the CPU that is being monitored (for example, Intel).
Cores Specifies the number of physically available logical processors within one physical CPU (for hyper-threading and multi-core CPUs). This is the sum of all cores and all logical CPUs of a hyper-threading CPU.
Configuration Describes the current status of the configuration of the CPU that is being monitored with Status values mapped as follows:
1. unknown - CPU status could not be evaluated 2. normal - Regular CPU configuration 3. disabledManually - CPU was manually disabled (in BIOS setup) 4. hotSpare - CPU is a hot-spare CPU (for future use) 5. mirror - CPU is mirrored (for future use) 6. notUsable - CPU is currently not usable (due to configuration problems) 7. configurationError - CPU misconfiguration
- 148 - N-central 10.0 Services Reference Manual
CPU – Juniper (ScreenOS) Service The CPU - Juniper (ScreenOS) service monitors the CPU usage of a Juniper device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Netscreen OS 5.4 and later Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
CPU Index Enter the SNMP index of the CPU. For a list of the CPU indices, query the device with the .1.3.6.1.4.1.3224.16.1.1 SNMP OID.
OID/Calculation
Metric OID/Calculation Name
CPU Usage 1.3.6.1.4.1.3224.16.1.1
CPU – Juniper Secure Access Service The CPU - Juniper Secure Access service monitors the memory and CPU usage of a Juniper Secure Access (SA) device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported IVE OS 6.0 and later Systems/Applications
Device Class Switch/Router
- 149 - N-central 10.0 Services Reference Manual
Monitored By Windows Probe
Scan Interval 5 minutes
CPU Index Although unlikely, you may need to specify a CPU Index value other than 0. To see the available index values, query the Juniper SA device with the 1.3.6.1.4.1.12532.10 SNMP OID. The default value is 0.
OID/Calculation
Metric Name OID/Calculation
CPU Utilization 1.3.6.1.4.1.12532.10
CPU (VMware) Service The CPU (VMware) service monitors the CPU usage on ESXi servers.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type ESXi
Instances on a 1 Device Note: One instance of the CPU (VMware) service is aggregated across multiple processors on the ESXi server if there are multiple CPUs on the device.
Supported ESX or ESXi 4.x, 5.x and later Systems/Applicatio ns Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 15 minutes
Metric Name Description
CPU Usage The usage of the CPU, expressed as a (%) percentage.
- 150 - N-central 10.0 Services Reference Manual
CPU – Watchguard Service The CPU - Watchguard service monitors the instantaneous, 1 minute, 5 minute, and 15 minute CPU usage.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Any device compliant with the WATCHGUARD-SYSTEM-STATISTICS Systems/Applications MIB
Device Class Switch/Router, Other
Monitored By Windows Probe
Scan Interval 5 minutes
CPU Index Enter the SNMP index of the CPU to be monitored. For a list of the SNMP indices, query the device with the .1.3.6.1.4.1.3097.6.3.4 SNMP OID.
SNMP OID
Metric Name OID/Calculation
Current CPU 1.3.6.1.4.1.3097.6.3.4
1 Minute CPU 1.3.6.1.4.1.3097.6.3.77
5 minute CPU 1.3.6.1.4.1.3097.6.3.78
15 minute CPU 1.3.6.1.4.1.3097.6.3.79
Metric
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
- 151 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Current CPU Usage Current CPU / 100 The current CPU usage of the Watchguard device.
1 Minute CPU 1 Minute CPU / The average CPU usage of the Watchguard device over the past Usage 100 minute.
5 Minute CPU 5 Minute CPU / The average CPU usage of the Watchguard device over the past 5 Usage 100 minutes.
15 Minute CPU 15 Minute CPU / The average CPU usage of the Watchguard device over the past 15 Usage 100 minutes.
CTIDevices (Cisco) Service The CTIDevices (Cisco) service monitors the number of registered CTI devices that are connected to the CallManager.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a Device 8
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applications
Device Class Server - Windows
Monitored By Probe
Scan Interval 30 minutes
ccmRegisteredCTIDevi Type the name of the CUCM. For a list of the ccmRegisteredCTIDevices attached ces Index to a CUCM server, query 1.3.6.1.4.1.9.9.156.1.5.14 SNMP OID.
- 152 - N-central 10.0 Services Reference Manual
Status Object Descriptors Numerical OID Description Detail
Registered cuccmRegisteredCTIDevices 1.3.6.1.4.1.9.9.156.1.5.14 Indicates the number of CTI CTI Devices devices that are registered and actively in communication with the local call manager.
Unregistered cuccmUnregisteredCTIDevices 1.3.6.1.4.1.9.9.156.1.5.15 Indicates the number of CTI CTI Devices devices that are unregistered or have lost contact with the local call manager.
Rejected CTI cuccmRejectedCTIDevices 1.3.6.1.4.1.9.9.156.1.5.16 Indicates the number of CTI Devices devices whose registration requests were rejected by the local call manager.
Datastore (VMware) Service The Datastore (VMware) service monitors the storage location for virtual machine files on ESXi servers.
Note: If your ESX/ESXi server is operating on either Dell or HP hardware, it is strongly recommended that you install the Dell or HP Offline Bundle before the Windows Probe discovers the ESX/ESXi server. For instructions on installing the Dell or HP Offline Bundle, refer to the following articles in the N-central online knowledge base:
l KBA10019: Installing the HP Offline Bundle on ESX/ESXi Servers
l KBA10020: Installing the Dell Offline Bundle on ESX/ESXi Servers
Service Type ESXi
Instances on a Device 100
Supported vCenter, ESX or ESXi 4.x, 5.x and later Systems/Applications Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 5 minutes
Datastore Name The name of the Datastore to be monitored.
- 153 - N-central 10.0 Services Reference Manual
Note: This service cannot use N-central’s Self-Healing feature.
To access information on the Datastores on your ESXi server, use a browser to access the following URL:
https://
Example: https://192.168.101.207/mob/?moid=ha-datacenter
Metric Name Description
Total Disk Space (GB) The total size (in GB) of the datastore.
Disk Space Used (GB) The amount of space (in GB) currently in use on the datastore.
Disk Space Free (GB) The amount of space (in GB) that is currently unoccupied on the datastore.
Disk Usage (%) The amount of space (in GB) currently unoccupied on the datastore expressed as a percentage of the total space.
List of Snapshots A list of the record files that store configuration data for ESXi servers at par- ticular points in time.
Guests The virtual machine guest operating systems currently configured on the ESXi server.
Total Disk Space used by all Vir- The amount of space (in GB) currently used by all snapshot files including tual Machine files (GB) the original snapshot.
Total Disk Space used by Snap- The amount of space (in GB) currently used by all snapshot files since the ori- shot Overhead files (GB) ginal snapshot but not including the original snapshot.
Oldest Snapshot The name of the snapshot record files that have the oldest creation date and time.
DHCP Active Queue Length Service The DHCP Active Queue Length service monitors the number of packets in the processing queue of a DHCP server.
Service Type WMI
Instances on a Device 15
Supported Windows 2012 Systems/Applications
Device Class Server - Windows
- 154 - N-central 10.0 Services Reference Manual
Monitored By Windows Agents
Scan Interval 15 minutes
Status Description Detail
Active Specifies the current length of the internal message queue of the DHCP server. This value is equal to Queue the number of unprocessed messages that have been received by the server. Large values may indic- Length ate heavy server traffic.
DHCP Server Service The DHCP Server service monitors the status of the DHCP Server running on a Windows device.
Service Type WMI
Instances on a Device 100
Supported Any WMI-enabled Server - Windows. Systems/Applications
Device Class Server - Windows
- 155 - N-central 10.0 Services Reference Manual
Monitored By Local Agent
Scanning schedule 1. Based on your requirements for monitoring Shad- owProtect backup jobs, select either Once a Day or Daily Interval.
2. If you selected Once a Day, configure the fol- lowing:
a. Time - to identify when you would like to scan the ShadowProtect backup jobs.
b. Repeat Weekly on Days - to identify the days of the week on which backup jobs will be scanned. All days of the week are selec- ted by default.
c. Repeat Monthly on Days - to identify the numeric dates of the month on which backup jobs will be scanned.
3. If you selected Daily Interval, configure the fol- lowing:
a. Start Hour and End Hour - to identify the period during which you would like to scan the ShadowProtect backup jobs.
b. Scan Interval in Minutes - to determine the time (in minutes) between each scan.
c. Repeat Weekly on Days - to identify the days of the week on which backup jobs will be scanned. All days of the week are selec- ted by default.
- 156 - N-central 10.0 Services Reference Manual
Status Details Description
Acks/sec The number of DHCP acknowledgment messages (DHCPACKs) sent per second by the DHCP server to clients.
Active The current length of the internal message queue of the DHCP server. This number equals Queue the number of unprocessed messages received by the server. Length
Packets The number of packets per second that expire and are dropped by the DHCP server. When a Expired/sec DHCP-related message packet is internally queued for 30 seconds or more, it is determined to be stale and expired by the server.
Packets The number of message packets received per second by the DHCP server. Received/s ec
Releases/s The number of DHCP release messages (DHCPRELEASEs) received per second by the DHCP ec server from clients. This number only exists if a DHCP client sends a release to the server. This can occur manually, such as when the ipconfig command is used at the client computer. Release messages can also be sent by the client if it is configured with the "Release DHCP lease on shutdown" option.
Requests/s The number of DHCP request messages (DHCPREQUESTs) received per second by the DHCP ec server from clients.
Conflict The current length of the conflict check queue for the DHCP server. This queue holds Check messages without responses while the DHCP server performs address conflict detection. Queue Length
Declines/s The number of DHCP decline messages (DHCPDECLINEs) received per second by the DHCP ec server from clients.
Discovers/s The number of DHCP discover messages (DHCPDISCOVERs) received per second by the ec server. These messages are sent by clients when they start on the network and obtain a new address lease.
Duplicates The number of duplicated packets per second dropped by the DHCP server. This number can Dropped/se be affected by multiple DHCP relay agents or network interfaces forwarding the same packet c to the server.
- 157 - N-central 10.0 Services Reference Manual
Status Details Description
Informs/se The number of DHCP information messages (DHCPINFORMs) received per second by the c DHCP server. DHCP inform messages are used when the DHCP server queries for the directory service for the enterprise root and when dynamic updates are being done on behalf of clients by the server.
Millisecond The average time (in milliseconds) used by the DHCP server to process each packet it s per receives. This number can vary depending on the server hardware and its I/O subsystem. Packet (Avg)
Nacks/sec The number of DHCP negative acknowledgment messages (DHCPNAKs) sent per second by the DHCP server to clients.
Offers/sec The number of DHCP offer messages (DHCPOFFERs) sent per second by the DHCP server to clients.
Disk Service The Disk service monitors a hard disk for its used, free, and total disk space.
Service Type Local API, SNMP, and WMI
Instances on a 15 Device
Device Class for Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Disk (Local API) Workstation - Windows
Device Class for Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Disk (SNMP) Laptop - Windows, Server - Windows, and Workstation - Windows
Device Class for Laptop - Windows, Server - Windows, and Workstation - Windows Disk (WMI)
Monitored By Agent (Windows, Red Hat Enterprise Linux, and Mac OSX 10.4) and Windows Probe (SNMP and WMI)
Scan Interval 60 minutes
Drive Designation The designation letter of the hard disk or partition to monitor (for example, C: or D:). Letter
Volume Index The index of the SNMP object representing the partition of hard disk to monitor. (SNMP only)
- 158 - N-central 10.0 Services Reference Manual
Properties Queried and Calculations Performed (WMI only)
Namespace root\cimv2
WMI Class Win32_ LogicalDisk
WMI Property 0 Size
WMI Property 1 FreeSpace
To configure Volume Name or Volume Index
Walk the .1.3.6.1.2.1.25.2.3.1.3 SNMP OID on the target device's IP address to determine which disks are available for monitoring.
Example:
.1.3.6.1.2.1.25.2.3.1.3.1 "A:\"
.1.3.6.1.2.1.25.2.3.1.3.2 "C:\ Label: Serial Number 74ebc3fb"
.1.3.6.1.2.1.25.2.3.1.3.3 "D:\ Label:SP2POEM_EN Serial Number 356563d9"
.1.3.6.1.2.1.25.2.3.1.3.4 "Virtual Memory"
OID/Calculation (SNMP Only)
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
- 159 - N-central 10.0 Services Reference Manual
Metric Description OID/Calculation Name
Total Disk (Total Disk Size x $hrStorageAllocationUnit) / 1024 The size of the disk. Size
Disk Space (Disk Space Used x $hrStorageAllocationUnit) / 1024 The amount of space used on the Used disk.
Disk Free [(Total Disk Size - Disk Space Used) x The unoccupied space on the Space $hrStorageAllocationUnit] / 1024 partition or disk.
Disk Usage (Disk Space Used / Total Disk Size) x 100 The percentage of space used on the (%) disk.
Disk I/O Service The Disk I/O service monitors read and write operations on the disk.
Note: Devices running Windows 2000 cannot monitor the Disk I/O service.
Service Type WMI
Instances on a Device 16
Supported Any WMI-enabled Server - Windows or workstation Systems/Applications
Device Class Laptop - Windows, Server - Windows, Workstation - Windows
- 160 - N-central 10.0 Services Reference Manual
Monitored By Windows Probes
Scan Interval 15 minutes
Instance An instance of the WMI class Win32_PerfRawData_ PerDisk_PhysicalDisk; for example, _Total.
To find the disk name to monitor, start Perfmon in Windows. Then click the Add Counters button and in the Performance Object drop down choose "Physical Disk". The available instances display in the right hand window under "Select instances from list:". For Disk Constraint, enter the value contained within the quotations.
You must specify a WSP probe as the monitoring endpoint since this is a WMI service. The device class of the device must be Laptop - Windows, Server - Windows or Workstation - Windows.
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_PerfDisk_LogicalDisk
WMI Property 0 CurrentDiskQueueLength
WMI Property 1 AvgDiskQueueLength
WMI Property 2 Timestamp_Sys100NS
WMI Property 3 Frequency_Sys100NS
Scandetail.1.Recipe ^scandetail1 / ^timeelapse02
- 161 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Current Queue Number of requests outstanding on the disk at the time the performance data is collected, including requests in service at the time of the snapshot. The value represents an instantaneous length, not an average over a time interval. Multi-spindle disk devices can have multiple requests active at one time, but other concurrent requests await service. This property may reflect a transitory high or low queue length. If the disk drive has a sustained load, the value will be consistently high. Requests experience delays proportional to the length of the queue minus the number of spindles on the disks. This difference should average less than 2 for good performance.
Average Queue Average number of both read and write requests that were queued for the selected disk during the sample interval.
Write The number of write operations performed per second Operations/Second on the selected disk during the sample interval.
Read The number of read operations performed per second Operations/Second on the selected disk during the sample interval.
Total The total number of both read and write operations Operations/Second performed per second on the selected disk during the sample interval.
Data Written (KB) The amount of data (in kilobytes) written to the selected disk during the sample interval.
Data Read (KB) The amount of data (in kilobytes) read from the selected disk during the sample interval.
- 162 - N-central 10.0 Services Reference Manual
Status Detail Description
Total Data The total amount of data (in kilobytes) both read from Sent/Received (KB) and written to the selected disk during the sample interval.
Idle Time (%) The percentage of time during the sample interval in which the selected disk remained in an idle state (all the requests from the operating system to the disk have been completed and there is no pending read or write requests).
Disk Time (%) The average number of both read and write requests that were queued for the selected disk during the sample interval expressed as a percentage.
Disk Read Time (%) The average number of read requests that were queued for the selected disk during the sample interval expressed as a percentage.
DNS Service The DNS service monitors the domain name system (DNS) server for its availability. The results from monitoring are displayed on the status dashboard under the service and, if specified, can also be provided in any notifications triggered by the service.
Service Type TCP/UDP
Instances on a Device 1
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Probe, Central server
Scan Interval 5 minutes
Timeout Value The time (in seconds) that the N-central server waits before considering the test a failure. The default is 30 seconds.
Port Number The TCP port number used to monitor the DNS service.
FQDN to Resolve The resolvable fully qualified domain name (FQDN) used to determine service availability.
- 163 - N-central 10.0 Services Reference Manual
During the monitoring process, a name server lookup (nslookup) is run at the preset scan intervals to test the availability of the DNS server. If the DNS server returns all of the IP addresses of the specified FQDN, the test is successful.
The nslookup is run using the user datagram protocol (UDP). If a DNS response to the DNS query is too large for the UDP packet, then the service state is displayed as Failed, although the DNS server is functional. For this reason, to receive accurate results of the DNS server's availability, specify an FQDN that will return fewer IP addresses for the FQDN to Resolve service detail. An FQDN that returns fewer IP addresses has a greater chance of fitting into the UDP packet.
The DNS service can monitor the DNS server through the central server or a Windows probe. If the DNS server is on a public network, the central server is used. If the DNS server is on a private network, a probe is used to send the information received from the DNS server through the firewall to the central server.
The figures below display the monitoring processes of the DNS server on a private and public network.
Monitoring the DNS Server on a Private Network
Monitoring the DNS Server on a Public Network
- 164 - N-central 10.0 Services Reference Manual
To monitor the DNS server, you must:
l Add the DNS server as a device.
l Add the DNS service to the device.
Status Details
Status Detail Description
DNS Service Determines whether the DNS service is up or down. The DNS service Availability does not use the Warning state. For example, a DNS test is considered successful if the target DNS server is able to resolve www.
Round Trip Time (ms) The time (in milliseconds) for a request to be sent and received.
DNS Resolution The threshold that determines whether the device name can be resolved. If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings. If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
DNS Performance Counters Service The DNS Performance Counters service monitors the status of the DNS Server service on a Windows device.
Service Type WMI
Instances on a Device 100
Supported Any WMI-enabled Server - Windows. Systems/Applications
Device Class Server - Windows
- 165 - N-central 10.0 Services Reference Manual
Monitored By Local Agent
Scanning schedule 1. Based on your requirements for monitoring Shad- owProtect backup jobs, select either Once a Day or Daily Interval.
2. If you selected Once a Day, configure the fol- lowing:
a. Time - to identify when you would like to scan the ShadowProtect backup jobs.
b. Repeat Weekly on Days - to identify the days of the week on which backup jobs will be scanned. All days of the week are selec- ted by default.
c. Repeat Monthly on Days - to identify the numeric dates of the month on which backup jobs will be scanned.
3. If you selected Daily Interval, configure the fol- lowing:
a. Start Hour and End Hour - to identify the period during which you would like to scan the ShadowProtect backup jobs.
b. Scan Interval in Minutes - to determine the time (in minutes) between each scan.
c. Repeat Weekly on Days - to identify the days of the week on which backup jobs will be scanned. All days of the week are selec- ted by default.
Status Details Description
Caching Memory The total amount of system memory in use by the DNS server for caching.
Database Node Memory The total amount of system memory in use by the DNS server on this node for database pages.
Secure Update Received The average number of secure update requests received by the DNS Per sec server per second.
TCP Message Memory The total amount of TCP message memory used by the DNS server.
- 166 - N-central 10.0 Services Reference Manual
Status Details Description
TCP Query Received Per sec The average number of TCP queries received by the DNS server per second.
TCP Response Sent Per sec The average number of TCP responses sent by the DNS server per second.
Total Query Received Per The average number of queries received by the DNS server in each sec second.
Total Response Sent Per The average number of responses sent by the DNS server in each second. sec
UDP Message Memory The total UDP message memory used by the DNS server.
UDP Query Received Per The average number of UDP queries received by the DNS server in each sec second.
UDP Response Sent Per sec The average number of UDP responses sent by the DNS server in each second.
Nbstat Memory The total amount of system memory in use by the DNS server for Nbtstat.
Record Flow Memory The total amount of system memory in use by the DNS server for record flow.
Dynamic Update No The average number of No-operation/Empty dynamic update requests Operation Per sec received by the DNS server in each second.
Dynamic Update Received The average number of dynamic update requests received by the DNS Per sec server in each second.
- 167 - N-central 10.0 Services Reference Manual
Status Details Description
Dynamic Update Written to The average number of dynamic updates written to the database by the Database Per sec DNS server in each second.
Recursive Queries Per sec The average number of recursive queries received by the DNS server in each second.
Recursive Query Failure The average number of recursive query failures in each second. Per sec
Recursive Time Out Per sec The average number of recursive query sending time-outs in each second.
Ethernet Errors Service The Ethernet Errors service monitors the NIC interfaces on a device for the following issues: Alignment Errors, FCS Errors, Collisions, MAC Receive Errors, MAC Send Errors, Carrier Sense Errors, and frames that are too long.
Note: The Ethernet Errors service only works with network infrastructure devices, such as switches, routers, fire walls, wireless access points. It will not work on servers, laptops, or workstations. To monitor NIC issues on those devices, use the Interface Health Service on page 242.
To monitor the Ethernet service on a device:
1. On the Properties tab of the device, check to see if the Use SNMP option is selected. a. If it is selected, skip to step 2
b. Otherwise, select Use SNMP and click Save.
2. On the Status tab, click Add, enter 1 for the number of instances of the Ethernet Errors service.
3. Click OK.
4. Click the Ethernet Errors service and then click the Service Details tab.
5. In Interfaces to Monitor, select the NICs/ports that you would like to monitor.
Tip: Use CTRL + SHIFT to select multiple NICs/ports.
6. Click OK.
Note: This service cannot use N-central’s Self-Healing feature.
- 168 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 60
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, and Server - Windows
Monitored By Windows Probe
Interfaces to Monitor Select the name or SNMP index of the NICs or ports that you would like to monitor. Tip: Hold down CTRL or SHIFT to select multiple NICs or ports.
Scan Interval 60 minutes
To monitor the Ethernet Errors service on a device, you must:
l Select the SNMP Enabled option when adding the device
l Add the Ethernet Errors service to the device and set the Interfaces to Monitor service detail
The tables IF-MIB and EtherLike-MIB describe the SNMP objects that are queried by the probe.
EtherLike-MIB
Object Descriptors Numerical OID
dot3StatsIndex 1.3.6.1.2.1.10.7.2.1.1
dot3StatsAlignmentErrors 1.3.6.1.2.1.10.7.2.1.2
dot3StatsFCSErrors 1.3.6.1.2.1.10.7.2.1.3
dot3Stats1CollisionFrames 1.3.6.1.2.1.10.7.2.1.4
dot3StatsMultipleCollisionFrames 1.3.6.1.2.1.10.7.2.1.5
dot3StatsInternalMacReceiveErrors 1.3.6.1.2.1.10.7.2.1.16
dot3StatsInternalMacTransmitErrors 1.3.6.1.2.1.10.7.2.1.10
dot3StatsCarrierSenseErrors 1.3.6.1.2.1.10.7.2.1.11
dot3StatsFrameTooLongs 1.3.6.1.2.1.10.7.2.1.13
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
- 169 - N-central 10.0 Services Reference Manual
Metric Description OID/Calculation Name
Alignment ^ dot3StatsAlignmentErrors An Alignment Error can indicate the following about a Errors received packet:
l The number of bits in the received packet has an uneven byte count (not an integral multiple of 8).
l The received packet has a Frame Check Sequence (FCS) error.
l Alignment Errors often result from MAC layer packet formation problems and cabling prob- lems. These problems cause corruption of data, loss in data and the transmission of packets through more than two cascaded multi-port transceivers.
FCS ^ dot3StatsFCSErrors FCS Errors, a type of cyclic redundancy checking, indicate Errors that frames received by an interface are an integral number of octets long, but do not pass the FCS check. Both Alignment Errors and FCS Errors can be caused by equipment powering up or down or by noise interference on unshielded twisted-pair (10BASE-T) segments. In a network that complies with the Ethernet standard, FCS Errors or Alignment Errors indicate bit errors during a transmission or reception. A very low rate is acceptable. Although Ethernet allows a 1 in 108 bit error rate, typical Ethernet performance is 1 in 1012 or better.
Collisions ^ dot3Stats1CollisionFrames + ^ Collisions indicate that two or more devices detect that the dot3StatsMultipleCollisionFrames network is idle and try to send packets at exactly the same time (within one round-trip delay). Because only one device can transmit at a time, both devices must stop sending and attempt to retransmit. Collisions are detected by the transmitting stations. The retransmission algorithm helps to ensure that the packets do not retransmit at the same time. However, if the devices retry at nearly the same time, packets can collide again; the process repeats until either the packets finally pass onto the network without collisions, or 16 consecutive collisions occur and the packets are discarded.
MAC ^ dot3Stat- MAC receive errors can indicate the malfunction of an Receive sInternalMacReceiveErrors ethernet card on the subnet. You can identify the subnet Errors and possibly the unit in question from the MAC address and the IP number.
- 170 - N-central 10.0 Services Reference Manual
Metric Description OID/Calculation Name
MAC Send ^ dot3Stat- This type of error indicates that the transmission failed Errors sInternalMacTransmitErrors because of an internal MAC sublayer error that is not caused by a collision or a carrier sense error.
Carrier ^ dot3StatsCarrierSenseErrors Indicates that the transmission failed because the carrier Sense was not present during any or all of the transmission Errors attempts.
Frame ^ dot3StatsFrameTooLongs A packet that is longer than 1518 octets (including FCS Too Long octets) can cause a Frames Too Long Error. This type of error is often caused by a malfunction in the jabber protection mechanism on a transceiver, or the presence of excessive noise on the transmission cable. The threshold value units are measured in packets.
Exchange 2003 Service The Exchange 2003 service uses the Windows probe to monitor the Microsoft Exchange 2003 Server for its availability and performance.
Service Type WMI
Instances on a Device 10
Supported Microsoft® Exchange Server 2003 Systems/Applications
Device Class Server - Windows
Monitored By Windows probe
Scan Interval 15 minutes
- 171 - N-central 10.0 Services Reference Manual
Public Information Store The location of the Exchange Database (EDB) and Streaming Database EDB file (STM) files that you would like to monitor. The service monitors the combined size of the files and displays a status based on the specified Public Information Store thresholds on the Windows Services dashboard. STM file These files contain all of the data on the Public Information Store. Access to the Public Information Store is not restricted. The default limit reflects the size of the standard edition, which is 16 GB. These limits should be modified to reflect the actual disk limitations for non- standard versions of the Information Store server. Ensure that you include the double backslashes when specifying your own EDB and STM files.
Private Information Store The Exchange Database (EDB) and Streaming Database (STM) files EDB file that you would like to monitor. The service monitors the combined size of the files and displays a status based on the specified thresholds on Private Information Store the Windows Services dashboard. STM file These files contain all of the data on the Private Information Store. Access to the Private Information Store is restricted. The default limit reflects the size of the standard edition, which is 16 GB. These limits should be modified to reflect the actual disk limitations for non- standard versions of the Information Store server. Ensure that you include the double backslashes when specifying your own EDB and STM files.
During the monitoring process, the probe uses the WMI protocol to query the following events on the Exchange Server:
l the number of users currently using the Information Store,
l the public and private Information Store sizes,
l the send queue size of the MS Exchange Information Store Mailbox,
l the receive queue size of the MS Exchange Information Store Mailbox, and
l the Remote Procedure Call (RPC) requests.
To monitor the Exchange Server, you must:
l Add the Exchange Server as a device.
l Add a Windows probe.
l Use the Window probe to add the Exchange 2003 service to the device.
- 172 - N-central 10.0 Services Reference Manual
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_MSExchangeIS_MSExchangeIS
WMI Property 0 ActiveUserCount
WMI Property 1 RPCRequests
Namespace root\cimv2
WMI Class Win32_PerfRawData_MSExchangeIS_MSExchangeISMailbox
WMI Property 0 SendQueueSize
WMI Property 1 ReceiveQueueSize
Namespace root\cimv2
WMI Class CIM_DataFile
WMI Property 0 FileSize
Namespace root\cimv2
WMI Class CIM_DataFile
WMI Property 0 FileSize
Status Details
Status Detail Description
The number of people currently using The number of user connections that have shown the Information Store activity in the last 10 minutes.
The number of client requests The number of requests that the Information Store currently being processed by the store is currently handling.
The queue of messages outbound from The number of messages that are in the outbound the Information Store queue of the Information Store.
The queue of messages inbound to the The number of messages that are inbound to the Information Store Information Store.
Public Information store size The size of the Public Information database.
Private Information store size The size of the Private Information database.
- 173 - N-central 10.0 Services Reference Manual
Exchange 2007/2010 Service The Exchange 2007/2010 service uses a Windows probe or Windows agent to monitor the performance of Microsoft Exchange Server 2007 and Microsoft Exchange Server 2010.
Service Type Registry Query
Instances on a Device 10
Supported Microsoft® Exchange Server 2007 and Microsoft® Exchange Server Systems/Applications 2010
Device Class Server - Windows
Monitored By Windows probe, Windows agent
Scan Interval 15 minutes
Status Details
Status Detail Description
RPC Averaged Latency The RPC latency in milliseconds averaged for the past 1024 packets.
RPC Requests The number of client requests that are currently being processed by the information store.
Local Delivery Rate The rate at which messages are delivered locally.
Active Remote Delivery Queue Length The number of items in the active remote delivery queues.
Retry Remote Delivery Queue Length The number of items in retry in the remote delivery queues.
Messages Received/sec The number of messages received by the SMTP server each second.
Messages Sent/sec The number of messages sent by the SMTPSend connector each second.
Monitoring Microsoft Exchange Server 2007 with a Probe
In order to monitor the Exchange 2007/2010 service with a Windows probe, the "LOCAL SERVICE" account must have Read Permission for the following registry key:
HKLM\System\CurrentControlSet\Control\SecurePipeServers\winreg
- 174 - N-central 10.0 Services Reference Manual
To give the LOCAL SERVICE account Read permission for the specified registry key, please complete the following steps:
1. On the machine running Exchange Service 2007/2010, navigate to Start>Run, Type "regedit", and press Enter.
2. Navigate to HKLM\System\CurrentControlSet\Control\SecurePipeServers\winreg.
3. Right-click on winreg, and select Permissions.
4. In the Permissions for winreg window, click LOCAL SERVICE.
5. Select the Allow Column check box.
6. Click OK
Exchange 2007/2010 Delivery Queue Service The Exchange 2007/2010 Delivery Queue service uses a Windows Agent to monitor the message queues of Microsoft Exchange Server 2007 and Microsoft Exchange Server 2010.
Service Type WMI
Instances on a 100 Device
Supported Microsoft® Exchange Server 2007 and Microsoft® Exchange Server 2010 Systems/Applicatio ns
Device Class Server - Windows
Monitored By Windows Agent
Scan Interval 15 minutes
Queue Name Type the name of the SNMP queue to be monitored. For a list of SMTP queues, query the Win32_PerfRawData_MSExchangeTransportQueues_ MSExchangeTransportQueues WMI class. The default value is _total.
- 175 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Active Mailbox The number of active items in the mailbox delivery queue. Delivery Queue Length (Messages)
Active Non-SMTP The number of active items in the non-SMTP delivery queue. Delivery Queue Length (Messages)
Active Remote The number of active items in the remote delivery queue. Delivery Queue Length (Messages)
Aggregate Delivery The total number of items in all of the delivery queues. Queue Length All Queues (Messages)
Largest Delivery The largest number of items in any of the delivery queues. Queue Length (Messages)
Poison Queue Length The number of items in the poison delivery queue (the special queue used to isolate (Messages) messages that are determined to be harmful to the Exchange server after a transport server or service failure).
Retry Mailbox The number of items in retry in the mailbox delivery queue. Delivery Queue Length (Messages)
- 176 - N-central 10.0 Services Reference Manual
Status Detail Description
Retry Non-SMTP The number of items in retry in the non-SMTP delivery queue. Delivery Queue Length (Messages)
Retry Remote The number of items in retry in the remote delivery queue. Delivery Queue Length (Messages)
Submission Queue The number of items in the submission queue (the queue used to gather all Length (Messages) messages that have to be resolved, routed, and processed by transport agents on the transport server).
Unreachable Queue The number of items in the unreachable queue (the queue used for messages that Length (Messages) can't be routed to their destinations).
Exchange Database 2013 Service The Exchange Database 2013 service monitors the health of an Microsoft Exchange 2013 database.
Service Type WMI
Instances on a Device 1
Supported Systems/Applications Microsoft Exchange Server 2013
Device Class Server - Windows
Monitored By Windows Agent
Scan Interval 5 minutes
Database Name Type the name of the database that you want to monitor.
- 177 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Database Page Indicates the rate of page faults that cannot be serviced because there are no pages available for Fault Stalls allocation from the database cache.
Database Cache Indicates the percentage of database file page requests that were fulfilled by the database cache Percent Hit without causing a file operation since the server was started.
Log Record Indicates the number of log records that cannot be added to the log buffers (expressed in stalls Stalls per second) because the log buffers are full.
Log Threads Indicates the number of threads waiting to complete an update of the database by writing their Waiting data to the log.
Exchange Database Latency 2013 Service The Exchange Database Latency 2013 service monitors latencies of a Microsoft Exchange 2013 database that can be caused by a number of issues including disk latencies due to a bad disk, domain controller latencies, or high user workload.
Service Type WMI
Instances on a Device 1
Supported Systems/Applications Microsoft Exchange Server 2013
Device Class Server - Windows
Monitored By Windows Agent
Scan Interval 15 minutes
Database Instance The name of the Exchange 2013 database being monitored.
- 178 - N-central 10.0 Services Reference Manual
Status Description Detail
Log Gen- Indicates that messages are being received faster than they can be written to the transport queue eration database due to reduced flow of intra-site, inter-site, or external mail messages. This may be due to Checkpoint message volume exceeding server capacity, applications other than Microsoft Exchange Server are Depth accessing or placing file locks on the transaction log files, or hard disks are not performing at a level to meet the disk I/O requirements of the Exchange environment.
IO Data- Indicates the average time, in milliseconds (ms), to read from the database file. base Reads Aver- age Latency
IO Data- Indicates the average time, in ms, to write to the database file. base Writes Average Latency
Exchange Processing Time Service The Exchange Processing Time service monitors the request time and processing time for a Microsoft Exchange server.
Service Type WMI
Instances on a Device 1
Supported Systems/Applications Microsoft Exchange
Device Class Server - Windows
Monitored By Windows Agent
Scan Interval 15 minutes
Status Detail Description
Average Search Processing Indicates the average time that elapsed while waiting for searches to be completed. Time
Outbound Proxy Requests Indicates the average time (in milliseconds) that requests sent to a secondary client Average Response Time access server took to be completed during the scanning period.
Requests Average Indicates the average time (in milliseconds) that the Exchange Control Panel took to Response Time respond to requests during the scanning period.
- 179 - N-central 10.0 Services Reference Manual
Exchange Database Store Mount Status Service The Exchange Database Store Mount Status service monitors whether or not Exchange databases on Exchange servers are mounted and accessible.
Service Type WMI
Instances on a 1 Device
Supported Microsoft® Exchange Server 2007 and Microsoft® Exchange Server 2010 Systems/Applicatio ns
Device Class Server - Windows
Monitored By Windows Agent
Scan Interval 5 minutes
Database Name Type the name of the database that you want to monitor. You can also use _Total, which will return the sum of the DatabaseMounted values for all databases. If _Total is used, you should adjust your thresholds accordingly.
Status Details
Status Detail Description
Database Name The name of the Exchange database being monitored.
Database Mount Indicates the status of the database's accessibility as one of the Status following:
l Normal
l Warning
l Failed
Fan Status (Cisco) Service The Fan Status (Cisco) Service monitors the state of the specified fan on a Cisco device.
- 180 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Most Cisco switches/routers running IOS. Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
Fan Index The SNMP index of the fan to be monitored. For a list of the fans installed in the Cisco device, query it with the 1.3.6.1.4.1.9.9.13.1.4.1.2 SNMP OID.
Fan Name The name of the fan to be monitored.
Object Numerical OID Descriptors
$FanState 1.3.6.1.4.1.9.9.13.1.4.1.3
Status Detail Description
Fan State The status of the fan which is mapped as follows:
Normal: 1
Warning: 2
Failed: 3-6
Fan State A description of the fan's state as follows: Description 1: Normal
2: Warning
3: Critical
4: Shutdown
5: Not Present
6: Not Functioning
Fan Status (Dell) Service The Fan Status (Dell) service monitors the status and speed (RPMs) of the fans on a Dell server.
- 181 - N-central 10.0 Services Reference Manual
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type SNMP
Instances on a Device 20
Supported Dell servers running Dell OpenManage Server Administrator software Systems/Applications
Device Class Server - Generic, Server - Windows
Monitored By Windows Probe
Scan Interval 15 minutes
Cooling Device The SNMP index of the fan to be monitored. Query the Location Name Index 1.3.6.1.4.1.674.10892.1.700.12.1.8 OID to get a list of the fan names and their SNMP indices.
Cooling Device The name of the fan to be monitored. Location Name Value
- 182 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Fan (Dell) 1.3.6.1.4.1.674.10892.1.700.12.1.5 The status of the fan. Status The status is mapped as follows: Normal : 3 Warning : 0-2, 4, 11-4294967295 Failed : 5, 6, 8-10
The meaning of the status: 1: Other 2: Unknown 3:OK 4: NonCritical Upper 5:Critical Upper 6: NonRecoverable Upper 7:NonCritical Lower 8:Critical Lower 9: NonRecoverable Lower 10: Failed
Fan (Dell) 1.3.6.1.4.1.674.10892.1.700.12.1.6 The speed in revolutions per minute (RPM) of the Speed fan.
Fan Status (EqualLogic) Service The Fan Status (EqualLogic) service monitors the status and speed (RPMs) of the fans on a Model PS6100 Dell EqualLogic SAN running v6.0.2 firmware.
Service Type SNMP
Instances on a Device 10
Supported Sys- Model PS6100 Dell EqualLogic SAN running v6.0.2 firmware tems/Applications
Device Class Server - Generic, Server - Windows
Monitored By Windows Probe
Scan Interval 5 minutes
Fan Sensor Type the name of the fan sensor to be monitored. For a list of fan sensors, query the SAN with the .1.3.6.1.4.1.12740.2.1.7.1.2 SNMP OID.
- 183 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Sensor State 1.3.6.1.4.1.12740.2.1.7. The status of the fan. 1.4 The meaning of the status: 0: Unknown 1: Normal 2: Warning 3: Critical
Fan Speed 1.3.6.1.4.1.12740.2.1.7. The speed in revolutions per minute (RPM) of the (RPM) 1.3 fan.
Fan Status (Fujitsu) Service The Fan Status (Fujitsu) service monitors the status of a fan on a Fujitsu server.
Service Type SNMP
Instances on a Device 100
Supported Fujitsu workstations, laptops or servers running the Fujitsu ServerView agent. Systems/Applications
Device Class for CPU Servers - Generic or Servers - Windows (SNMP)
Monitored By Windows Agent
Fan Name Type the name of the fan to be monitored. For a list of fans, query the device with the .1.3.6.1.4.1.231.2.10.2.2.10.5.2.1.3 SNMP OID.
Scanning The scan interval can be configured according to either a Once a Day or Daily Interval schedule.
Object Numerical OID Descriptors
$Status 1.3.6.1.4.1.231.2.10.2.2.10.5.2.1.5
$CurrentSpeed 1.3.6.1.4.1.231.2.10.2.2.10.5.2.1.6
$Quality 1.3.6.1.4.1.231.2.10.2.2.10.5.2.1.7
$FailureReaction 1.3.6.1.4.1.231.2.10.2.2.10.5.2.1.8
$ShutdownDelay 1.3.6.1.4.1.231.2.10.2.2.10.5.2.1.9
- 184 - N-central 10.0 Services Reference Manual
Status Detail Description
Status Describes the current status of the fan that is being monitored with values mapped as follows:
Normal: 3
Warning: 6
Failed: 1, 2, 4, 5, 7, 8
1: Unknown
2: Disabled
3: OK
4: Failed
5: Failure Predicted
6: Redundant Fan Failed
7: Not Manageable
8: Not Present
Current Speed Specifies the current speed of the fan (measured in revolutions per minute).
Fan Output Specifies the current quality of the fan indicated as a percentage of nominal speed.
Reaction to Failure Describes the reaction if the fan fails with one of the following reported:
l Unknown
l Continue
l Shutdown and Power Off
Shutdown Delay if Fail- Indicates the amount of delay (measured in seconds) when shutdown should be ure Occurs committed upon failure of the fan.
Fan Status (HP) Service The Fan Status (HP) service monitors the condition of the system and CPU fans for Compaq/HP ProLiant servers.
- 185 - N-central 10.0 Services Reference Manual
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type SNMP
Instances on a Device 1
Supported HP Proliant Servers running HP Insight Manager agents Systems/Applications
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, and Server - Windows
Monitored By Windows Probe
Scan Interval 15 minutes
- 186 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
System Fan .1.3.6.1.4.1.232.6.2.6.4 The status of the fans in the system is mapped as follows: (HP) Normal: 1, 2 Warning: 3 Failed: 4
Here are the meanings: 1: Other, fan status detection is not supported by this system or driver 2: OK, all fans are operating properly 3: Degraded, a non-required fan is not operating properly 4: Failed, a required fan is not operating properly
CPU Fan (HP) .1.3.6.1.4.1.232.6.2.6.5 The status of the processor fans in the system is mapped as follows: Normal: 1, 2 Warning: 3 Failed: 4
Here are the meanings: 1: Other, fan status detection is not supported by this system or driver 2: OK, all fans are operating properly 3: Degraded, a non-required fan is not operating properly 4: Failed, a required fan is not operating properly
Fan Status (IBM) Service The Fan Status (IBM) service monitors the status of the specified fan sensor on IBM servers.
- 187 - N-central 10.0 Services Reference Manual
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type SNMP
Instances on a Device 10
Supported Any UMSLMSENSOR-MIB Compliant Device Systems/Applications
Device Class Server - Windows, Server - Generic
Monitored By Windows agent, Windows probe
Scan Interval 5 minutes
Fan Sensor Name The name of the fan sensor to be monitored. The name can be obtained by querying the device with the .1.3.6.1.4.1.2.6.159.1.1.80.5.1.1 SNMP OID. The default setting is Fan Sensor 1.
OID/Calculation
Metric Name OID/Calculation Description
Fan Sensor Status .1.3.6.1.4.1.2.6.159.1.1.80.5.1.20 The status of the fan sensor.
Fan Speed (RPM) .1.3.6.1.4.1.2.6.159.1.1.80.5.1.2 The speed of the fan in RPMs.
Fan Status (Intel) Service The Fan (Intel) Status service monitors the status and speed of specified fans for devices that use Intel motherboards and that have the Intel SMS software installed.
- 188 - N-central 10.0 Services Reference Manual
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type SNMP
Instances on a Device 10
Supported Systems/Applications Devices using an Intel motherboard with the Intel SMS software installed
Device Class Server - Generic, Server - Windows
Monitored By Windows Probe
Scan Interval 5 minutes
- 189 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Fan Status 1.3.6.1.4.1.343.2.10.3.5.600.20.1.5 The fan status is mapped as follows: Normal: 3 Warning: 1, 2, 4 Failed: 5, 6
The meaning of the status: 1: Other 2: Unknown 3: OK 4: Non-critical 5, 6: Critical or Non-recoverable
Fan Status 1.3.6.1.4.1.343.2.10.3.5.600.20.1.5 Describes the status of the fan: Description Other Unknown OK Non-Critical Critical or Non-recoverable
Fan Speed 1.3.6.1.4.1.343.2.10.3.5.600.20.1.6 The speed at which the fan is turning as measured in (RPM) RPM (revolutions per minute).
Fan Status (VMware) Service The Fan Status (VMware) service monitors the status and speed (RPMs) of the fans on ESXi servers.
Note: If your ESX/ESXi server is operating on either Dell or HP hardware, it is strongly recommended that you install the Dell or HP Offline Bundle before the Windows Probe discovers the ESX/ESXi server. For instructions on installing the Dell or HP Offline Bundle, refer to the following articles in the N-central online knowledge base:
l KBA10019: Installing the HP Offline Bundle on ESX/ESXi Servers
l KBA10020: Installing the Dell Offline Bundle on ESX/ESXi Servers
- 190 - N-central 10.0 Services Reference Manual
Service Type ESXi
Instances on a Device 100
Supported ESX or ESXi 4.x, 5.x and later Systems/Applications Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 5 minutes
Fan Name The name of the fan to be monitored.
Note: This service cannot use N-central’s Self-Healing feature.
To access information on the fans on your ESXi server, use a browser to access the following URL:
https://
Example: https://192.168.101.207/mob/?moid=ha- host&doPath=runtime.healthSystemRuntime.systemHealthInfo.numericSensorInfo
Metric Name Description
Fan Speed (R.P.M) The speed in revolutions per minute (RPM) of the fan.
State Indicates whether the fan has been enabled or disabled.
State Description n/a
Fan Health State The fan status is mapped as follows:
Normal: 1
Warning: 1, 2, 4
Failed: 5, 6
- 191 - N-central 10.0 Services Reference Manual
Metric Name Description
Fan Health State Description Describes the status of the fan:
Other
Unknown
OK
Non-Critical
Critical or Non-recoverable
File Size Service The File Size service monitors the size of a file as collected from the WMI Class: CIM_DataFile and Property: FileSize.
Service Type WMI
Instances on a Device 100
Supported Any Windows device that supports WMI Systems/Applications
Device Class Laptop - Windows, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Probes
Scan Interval 15 minutes
File Name and Path The directory path and name of the file that you would like monitored by the service. Example: c:\Program Files\Internet Explorer\iexplore.exe
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class CIM_DataFile
WMI Property 0 FileSize
Status Details
Status Detail Description
File Size The file size of the service, in bytes, kilobytes, megabytes, gigabytes.
- 192 - N-central 10.0 Services Reference Manual
Fortinet CPU Service The Fortinet CPU service monitors CPU usage in Fortinet devices.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Fortinet FortiGate™ 50B Series, 60B Series, 100A, 200A, 224B, 300A, 400A, Systems/Applications 500A, 800
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Metric Description OID/Calculation Name
CPU Usage 1.3.6.1.4.1.12356.1.8 Indicates CPU usage as a percentage.
Fortinet Disk Service The Fortinet Disk service monitors the amount of disk space used on a Fortinet device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Fortinet FortiGate™ 50B Series, 60B Series, 100A, 200A, 224B, 300A, 400A, Systems/Applications 500A, 800
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
- 193 - N-central 10.0 Services Reference Manual
Metric OID/Calculation Description Name
Disk Usage 1.3.6.1.4.1.12356.1.12 Indicates the amount of space used on the disk, in MB.
Disk Capa- 1.3.6.1.4.1.12356.1.11 Indicates the total capacity of the disk, in MB. city
Percent (Disk Usage / Disk Capacity) x Indicates disk space currently in use as a percentage of the total Used 100 disk space.
Fortinet Memory Service The Fortinet Memory service monitors the memory (RAM) usage of Fortinet devices.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Fortinet FortiGate™ 50B Series, 60B Series, 100A, 200A, 224B, 300A, Systems/Applications 400A, 500A, 800
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Metric Name OID/Calculation Description
Memory 1.3.6.1.4.1.12356.1.9 Measures the memory usage of the Fortinet device as a Usage percentage.
Fortinet Sessions Service The Fortinet Sessions service monitors the number of active sessions on a Fortinet device.
Note: This service cannot use N-central’s Self-Healing feature.
- 194 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Fortinet FortiGate™ 50B Series, 60B Series, 100A, 200A, 224B, 300A, 400A, Systems/Applications 500A, 800
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Metric Name OID/Calculation Description
Number of Sessions 1.3.6.1.4.1.12356.1.10 Indicates the number of active sessions on the device.
Frame Relay Service Frame Relay is an efficient data transmission technique used to send digital information such as voice, data, local area network (LAN), and wide area network (WAN) traffic quickly and cost-efficiently to many destinations using virtual circuits. Frame Relay is characterized by connection-oriented, permanent or switched virtual circuits (PVC and SVC) at speeds up to 50 Mbps.
Note: This service cannot use N-central’s Self-Healing feature.
N-central can monitor the Frame Relay circuit status, congestion notifications and the amount of traffic on the Frame Relay virtual circuits. In addition, thresholds can be set against counters that indicate congestion on the network.
To monitor the Frame Relay service on a device:
1. On the Properties tab of the device, check to see if the Use SNMP option is selected. a. If it is selected, skip to step 2
b. Otherwise, select Use SNMP and click Save.
2. On the Status tab, click Add, enter 1 for the number of instances of the Frame Relay service.
3. Click OK.
4. Click the Frame Relay service and then click the Service Details tab.
5. In Interfaces to Monitor, select the NICs/ports that you would like to monitor.
- 195 - N-central 10.0 Services Reference Manual
Tip: Use CTRL + SHIFT to select multiple NICs/ports.
6. Click OK.
Service Type SNMP
Instances on a 60 Device
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, and Server - Windows
Monitored By Windows Probe
Scan Interval 15 minutes
Interfaces to Select the name or SNMP index of the NICs or ports that you would like to monitor. Monitor Tip: Hold down CTRL or SHIFT to select multiple NICs or ports.
The tables IF-MIBand FRAME-RELAY-DTE-MIB describe the SNMP objects that are queried by the probe.
IF-MIB
Object Descriptors Numerical OID
sysUptime 1.3.6.1.2.1.1.3
ifIndex 1.3.6.1.2.1.2.2.1.1
ifDescr 1.3.6.1.2.1.2.2.1.2
ifSpeed 1.3.6.1.2.1.2.2.1.5
FRAME-RELAY-DTE-MIB
Object Descriptors Numerical OID
frCircuitIfIndex 1.3.6.1.2.1.10.32.2.1.1
frCircuitState 1.3.6.1.2.1.10.32.2.1.3
frCircuitReceivedFECNs 1.3.6.1.2.1.10.32.2.1.4
frCircuitReceivedBECNs 1.3.6.1.2.1.10.32.2.1.5
- 196 - N-central 10.0 Services Reference Manual
Object Descriptors Numerical OID
frCircuitSentFrames 1.3.6.1.2.1.10.32.2.1.6
frCircuitSentOctets 1.3.6.1.2.1.10.32.2.1.7
frCircuitReceivedFrames 1.3.6.1.2.1.10.32.2.1.8
frCircuitReceivedOctets 1.3.6.1.2.1.10.32.2.1.9
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Description OID/Calculation Name
Octets ^frCircuitSentOctets + ^ The total number of transmitted and received octets. (Transmitted frCircuitReceivedOctets and Received)
Frames ^frCircuitSentFrames + The total number of transmitted and received frames. (Transmitted ^ and frCircuitReceivedFrames Received)
Average (^frCircuitSentOctets + The average number of octets sent and received over this virtual Packet Size ^ circuit calculated as a percentage of the total capacity of the virtual frCircuitReceivedOctets) circuit. / (^ frCircuitSentFrames + ^ frCircuitReceivedFrames)
Transmitted ( ^frCircuitSentOctets * The number of octets transmitted over the Frame Relay virtual Utilization 80000) / ($ifSpeed * ^ circuit during a scan interval time, which is calculated as a sysUptime) percentage of the total capacity of the virtual circuit: Transmitted octets is the difference between the number of octets transmitted during the previous scan and the number of octets transmitted during the current scan. This threshold is measured as a percentage value.
- 197 - N-central 10.0 Services Reference Manual
Metric Description OID/Calculation Name
Received ( The number of octets received over the Frame Relay virtual circuit Utilization ^frCircuitReceivedOctets during a scan interval time, which is calculated as a percentage of * 80000) / ($ifSpeed * ^ the total capacity of the virtual circuit: sysUptime) Received octets is the difference between the number of octets received during the previous scan and the number of octets received during the current scan. This threshold is measured as a percentage value.
Fwd Explicit ^frCircuitReceivedFECNs This type of notification is transmitted from the source terminal Congestion requesting the destination terminal to slow its requests for data. Notification The notification occurs when the data capacity level of the source terminal reaches the value set by the data terminal equipment (DTE), or when a switch queues a frame to a trunk that is congested. This field displays the number of FECNs received from the network indicating forward congestion since the virtual circuit was created. This threshold is measured in frames.
Bkwd ^frCircuitReceivedBECNs This type of notification is transmitted from the destination terminal Explicit requesting the source terminal to slow its data transmission. The Congestion notification occurs when the data capacity level of the destination Notification terminal reaches the value set by the data terminal equipment (DTE), or when a switch receives a frame from a trunk that is congested. This field displays the number of BECNs received from the network indicating forward congestion since the virtual circuit was created. This threshold is measured in frames.
Circuit $frCircuitState Indicates whether the particular virtual circuit is operational. Status There are two possible states: Active (displayed as ‘Normal’) = 2 Inactive (displayed as ‘Failed’) = 3
FTP Service The FTP service supports file transfers between local and remote computers.
The File Transfer Protocol (FTP) test checks the status of the FTP service on the network device. During the test, N-central can determine the availability status of the FTP service by comparing the availability of the FTP service to the threshold value.
- 198 - N-central 10.0 Services Reference Manual
Service Type TCP
Instances on a Device 1
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Probe, Central server
Scan Interval 5 minutes
Timeout Value The time (in seconds) that the N-central server waits before considering the test a failure. The default is 30 seconds.
Port Number The port the system uses to monitor the service.
Validation String The response you expect to receive from the port that is being queried. If the validation string that you specify is not returned by the port being queried, the service will transition to a Failed state. The default validation string is 220.
Status Details
Status Detail Description
FTP Service Availability N-central determines whether the FTP service is up or down. The FTP service does not use thresholds or the Warning state.
Round Trip Time (ms) The time (in milliseconds) for a request to be sent and received.
DNS Resolution The threshold that determines whether the device name can be resolved. If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings. If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
FW-Chk Point Service The FW-Chk Point service collects vendor-supplied metrics from the .1.3.6.1.4.1.2620 Check Point private branch, such as packets accepted, packets rejected, packets dropped, packets logged, last trap event sent.
- 199 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Systems/Applications Check Point FireWall-1 V5.4
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 15 minutes
OID/Calculation
Metric Name OID/Calculation Description
Module State 1.3.6.1.4.1.2620.1.1.1 The state of the firewall module.
Filter Name 1.3.6.1.4.1.2620.1.1.2 The name of the loaded filter.
Filter Date 1.3.6.1.4.1.2620.1.1.3 The date the filter was installed.
Accepted Packets 1.3.6.1.4.1.2620.1.1.4 The number of accepted packets.
Rejected Packets 1.3.6.1.4.1.2620.1.1.5 The number of rejected packets.
Dropped Packets 1.3.6.1.4.1.2620.1.1.6 The number of dropped packets.
Logged Packets 1.3.6.1.4.1.2620.1.1.7 The number of logged packets.
Major Version Number 1.3.6.1.4.1.2620.1.1.8 The major version of the Check Point OS.
Minor Version Number 1.3.6.1.4.1.2620.1.1.9 The minor version of the Check Point OS.
Product Name 1.3.6.1.4.1.2620.1.1.10 The model of the Check Point firewall.
Last Trap Sent 1.3.6.1.4.1.2620.1.1.11 A string containing the last SNMP trap sent from the firewall.
FW-Cisco Service The FW-Cisco service monitors syslog entries from a Cisco ASA or PIX Firewall.
Note: This service cannot use N-central’s Self-Healing feature.
- 200 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Cisco PIX and Cisco ASA firewalls Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
Regular Expression for The strings of characters and metacharacters that you would like to use to find Severity 1 to 5 predetermined key words in the log files. You can set a different threshold option for each regular expression.
Status Details
Status Description Detail
Severity The severity levels to be reported by N-central are based on the regular expressions that you 1 configure. Up to five (5) different severity levels can be reported using the format \% ((PIX\|)?(ASA)|(PIX)\- followed by the number corresponding to the Cisco severity Severity level. 2 The Cisco severity levels are as follows:
Severity l \%((PIX\|)?(ASA)|(PIX)\-0 = Emergency
3 l \%((PIX\|)?(ASA)|(PIX)\-1 = Alert
l \%((PIX\|)?(ASA)|(PIX)\-2 = Critical
Severity l \%((PIX\|)?(ASA)|(PIX)\-3 = Error 4 l \%((PIX\|)?(ASA)|(PIX)\-4 = Warning
l \%((PIX\|)?(ASA)|(PIX)\-5 = Notification
Severity l \%((PIX\|)?(ASA)|(PIX)\-6 = Informational 5 l \%((PIX\|)?(ASA)|(PIX)\-7 = Debugging
The line The number of lines, in the log file, on which the keyword has been located and returned by the count agent. This information is displayed for each regular expression on the status details screen for the matched service, any applicable reports, and any triggered notifications (except for numeric pages). regex...
The first This is the first line of the lines that were scanned, not the first line in the file. line matched
- 201 - N-central 10.0 Services Reference Manual
FW-Fortigate Service The FW-Fortigate service monitors syslog messages from FortiGate devices.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type Syslog
Instances on a Device 1
Supported Fortinet FortiGate™ 50B Series, 60B Series, 100A, 200A, 224B, 300A, Systems/Applications 400A, 500A, 800
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
Status Details
Status Detail Description
Emergency The threshold values that determine the status change of the service. If the related regular expression is found, the test is successful. Otherwise, Alert the test is unsuccessful. Based on the test results, the appropriate status is Critical then displayed for the service.
Error
Warning
The line count The number of lines, in the log file, on which the keyword has been located matched regex... and returned by the agent. This information is displayed for each regular expression on the status details screen for the service, any applicable reports, and any triggered notifications (except for numeric pages).
The first line This is the first line of the lines that were scanned, not the first line in the matched file.
FW-Juniper Service The default keywords that are displayed in the regular expression fields are obtained from Juniper.
Note: Your firewall must be configured to send syslog messages to the IP address of the Windows probe. The IP address of the firewall that is registered as a device in N-central must be the same as the IP address that sends SNMP traps to the probes.
Note: This service cannot use N-central’s Self-Healing feature.
- 202 - N-central 10.0 Services Reference Manual
Service Type Syslog
Instances on a Device 1
Supported Juniper® 25 Systems/Applications
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Probe
Scan Interval 5 minutes
Status Details
Status Description Detail
Emergency The threshold values that determine the status change of the service. If the related regular expression is found, the test is successful. Otherwise, the test is Alert unsuccessful. Based on the test results, the appropriate status is then displayed for the service. Critical
Error
Warning
The line The number of lines, in the log file, on which the keyword has been located and returned by the count agent. This information is displayed for each regular expression on the status details screen for matched the service, any applicable reports, and any triggered notifications (except for numeric pages). regex...
The first This is the first line of the lines that were scanned, not the first line in the file. line matched
FW-SonicWALL Service The FW-SonicWall service monitors syslog messages from SonicWALL devices.
Note: This service cannot use N-central’s Self-Healing feature.
- 203 - N-central 10.0 Services Reference Manual
Service Type Syslog
Instances on a Device 1
Supported Systems/Applications SonicWALL® TZ-Series, PRO-Series, and NSA-Series devices
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
Status Details
Status Detail Default Keyword
Severity 0 An event with a severity of emergency was detected.
Severity 1 An event with a severity of alert was detected.
Severity 2 An event with a severity of critical was detected.
Severity 3 An event with a severity of error was detected.
The line count The number of lines, in the log file, on which the keyword has been located matched and returned by the agent. This information is displayed for each regular regex... expression on the status details screen for the service, any applicable reports, and any triggered notifications (except for numeric pages).
The first line This is the first line of the lines that were scanned, not the first line in the file. matched
FW-Watchguard Service The FW-Watchguard service allows you to track the status of your firewall and generate notifications and trend reports on its activities.
Note: Your firewall must be configured to send syslog messages to the IP address of the Windows probe. The IP address of the firewall that is registered as a device in N-central must be the same as the IP address that sends SNMP traps to the probes.
Note: This service cannot use N-central’s Self-Healing feature.
- 204 - N-central 10.0 Services Reference Manual
Service Type Syslog
Instances on a Device 1
Supported WatchGuard® Firebox® X Edge e-Series, X Core e-Series, X Peak e- Systems/Applications Series
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
Status Details
Status Description Detail
Fail The threshold values that determine the status change of the service. If the related regular expression is found, the test is successful. Otherwise, the test is Warning unsuccessful. Based on the test results, the appropriate status is then displayed for the service. Attack
Flood
Ping of Death
IP Source Spoofing
The line The number of lines, in the log file, on which the keyword has been located and returned by the count agent. This information is displayed for each regular expression on the status details screen for the matched service, any applicable reports, and any triggered notifications (except for numeric pages). regex...
The first This is the first line of the lines that were scanned that matches the regular expression. line matched
FW-ZyWALL Service The FW-ZyWALL service allows you to track the status of your firewall and generate notifications and trend reports on its activities.
Note: This service cannot use N-central’s Self-Healing feature.
- 205 - N-central 10.0 Services Reference Manual
Service Type Security Log
Instances on a Device 1
Supported ZyWALL 2 Plus, 2WG, 5 UTM, 35 UTM, and 70UTM firewalls Systems/Applications
Device Class Switch/Router, Other
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Metric Name Description
System Errors Monitors for any system errors reported by the ZyWALL device.
IPSec IKE or PKI Monitors for any IPSec IKE or PKI attacks reported by the ZyWALL device.
Blocked Web Monitors for any attempts to access blocked web sites. Sites
Attacks Monitors for any attacks.
Other Cat- Monitors for any other issues reported by the ZyWALL device. egories
Generic (TCP) Service The Generic (TCP) service monitors the connectivity of a socket on a specified port on a device and, if the port is available, a specific TCP service functioning on the port.
After the port has successfully passed the test for connectivity, the Generic (TCP) service can continue on to use an appropriate command string to test the TCP service it is monitoring and a validation string against which to check the response it receives. The availability results of the TCP service are then reflected on the status dashboard for the Generic (TCP) service. For example, the command string 201 receiving the appropriate response code 220 indicates that the FTP service is running and available for use. The service also measures the round trip time for the request and the domain name system (DNS) resolution.
A maximum of six instances of the Generic (TCP) service can be set on a device, with each instance monitoring a different port on the device.
Note: The Generic (TCP) service does not use the Warning state.
- 206 - N-central 10.0 Services Reference Manual
Service Type Generic TCP
Instances on a Device 10
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows probe, Central Server
Scan Interval 5 minutes
Timeout Value The time (in seconds) that the N-central server waits before considering the test a failure. The default is 30 seconds.
Port Number The TCP port number used to monitor the Generic (TCP) service.
Send Command String A predefined set of characters specific to the TCP service. The string is transmitted upon connection to the host and requests the response about the TCP service.
Validation String The response you expect to receive from the port that is being queried. If the validation string that you specify is not returned by the port being queried, the service will transition to a Failed state.
Generic (TCP) Status Details
Status Detail Description
Generic Service The threshold that determines the availability of the port. Availability
Round Trip Time The time (in milliseconds) for a request to be sent and received. (ms)
DNS Resolution The threshold that determines whether the device name can be resolved. If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings. If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
Generic Integer (SNMP) Service The Generic Integer (SNMP) service can be set up to monitor any integer value by using Simple Network Management Protocol (SNMP). This service monitors one integer value at a time by allowing you to specify the SNMP object identifier (OID) and the SNMP index of the value that you would like to monitor. The OID can be any 32-bit integer.
- 207 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 25
Device Class Server - Generic, Workstation - Generic, Other, Printer, Switch/Router, and Server - Windows
Monitored By Windows Probe
Target OID Index The SNMP Index of the variable that you would like to monitor.
Target OID Variable The SNMP OID of the variable that you would like to monitor.
Scan Interval 15 minutes.
OID/Calculation
Metric Name OID/Calculation Description
OID Value Monitors the instance, which is obtained by combining the value of the target OID index and the target OID variable that are set on the Service Details tab.
System Up Time 1.3.6.1.2.1.1.3 How long the device has been online. OID
Generic ODBC Service The Generic ODBC service monitors the results of an ODBC query sent to a SQL database.
The data returned by the ODBC query is then evaluated against the regular expressions specified in the service.
Service Type ODBC
Instances on a Device 50
Supported ODBC-compliant SQL servers Systems/Applications
Device Class Server - Generic and Server - Windows
Monitored By Agent (Windows and Red Hat Linux), Windows Probe
Scan Interval 5 minutes
ODBC Driver Name The name of the ODBC driver that allows the Generic ODBC service to query the specified database.
- 208 - N-central 10.0 Services Reference Manual
Database Port The port on which the database accepts incoming queries.
Database Name The name of the database to be queried.
Database Username The username that is used to access the database.
Database Password The password that is used to access the database.
Database Query The SQL query statement that is submitted to the database.
Column 1 Name The name of the database values that are being queried for the value.
Column 2 Name
Column 3 Name
Column 1 Regular The values that N-central should look for in the results of the ODBC Expression query.
Column 2 Regular Expression
Column 3 Regular Expression
ODBC Driver Support
Agent/Probe ODBC Driver and Version
MDAC ODBC Unix ODBC Driver Postgres SQL ODBC Driver 2.8 2.2.10 Driver 8.01
Windows Agent x
Red Hat Agent x x
Suse Agent x x
Windows Probe x
- 209 - N-central 10.0 Services Reference Manual
Generic ODBC Status Details
Status Detail Description
Transaction time in The total transaction time (in milliseconds) to connect, milliseconds authenticate, send a query, retrieve results, and disconnect.
Rows returned by the query The number of rows returned by a query.
Rows returned by the query The number of rows that matched all of the column regular that matched all column expressions. regular expressions
Generic SQL Server Service The Generic SQL Server service monitors the availability of the port on which the MS SQL Server application runs. The availability of the port, which is determined by the service testing the port's connectivity, indicates that the MS SQL Server application is running. This service also measures the domain name system (DNS) resolution and the round trip time of the initial connection request and response. The availability results of the TCP service are then reflected on the status dashboard for the Generic SQL Server service.
A maximum of three instances of this service can be set on a device, with each instance monitoring a different port on the device.
Note: The Generic SQL Server service does not use the Warning state.
Service Type Generic TCP
Instances on a Device 3
Supported Microsoft SQL Server Systems/Applications
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Probe, central server
Scan Interval 5 minutes
Timeout Value The time (in seconds) that the N-central server waits before considering the test a failure. The default is 30 seconds.
Port Number The TCP port number used to monitor the Generic SQL service is 1433.
- 210 - N-central 10.0 Services Reference Manual
Generic SQL Server Thresholds
Status Detail Description
Generic SQL Server The threshold that determines the availability of the port. Availability
Round Trip Time (ms) The time (in milliseconds) for a request to be sent and received.
DNS Resolution The threshold that determines whether the device name can be resolved.
If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
Generic String (SNMP) Service The Generic String (SNMP) service will collect any OID using a configurable OID parameter field. It is returned as a string in N-central's database regardless of the original SNMP data type. Thresholds cannot be applied to Generic String.
Service Type SNMP
Instances on a Device 1000
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, and Server - Windows
Monitored By Windows Probe
Target OID Index The Index of the object that you would like to monitor.
Target OID Variable The OID that you would like to monitor.
Scan Interval 15 minutes
ObjectID - .1.3.6.1 The unfinished OID. Append the rest of the dotted decimal values that correspond to the snmp object you wish to query to this unfinished OID. For example, if the OID is .1.3.6.1.2.1.2.2.1.8, enter .2.1.2.2.1.8. You must also include the index. For example, to collect the sysDescr system description, enter 2.1.1.1.0 in this field.
- 211 - N-central 10.0 Services Reference Manual
The Generic String (SNMP) service can be set up to monitor any variable by using the Simple Network Management Protocol (SNMP). This service monitors one value at a time by allowing you to specify the SNMP object identifier (OID) and the index of the object that you would like to monitor.
Generic String (SNMP) Status Details
Status Detail Description
Generic String The returned string.
System Uptime The uptime of the device. This status detail is required.
Guest Status (VMware) Service The Guest Status (VMware) service monitors Guest instances on an ESX server.
Note: If your ESX/ESXi server is operating on either Dell or HP hardware, it is strongly recommended that you install the Dell or HP Offline Bundle before the Windows Probe discovers the ESX/ESXi server. For instructions on installing the Dell or HP Offline Bundle, refer to the following articles in the N-central online knowledge base:
l KBA10019: Installing the HP Offline Bundle on ESX/ESXi Servers
l KBA10020: Installing the Dell Offline Bundle on ESX/ESXi Servers
Service Type ESXi
Instances on a Device 1 per discovered Guest
Supported ESX or ESXi 4.x, 5.x and Systems/Applications later
Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 5 minutes
Note: This service cannot use N-central’s Self-Healing feature.
- 212 - N-central 10.0 Services Reference Manual
Metric Name Description
Guest Status Indicates whether the Guest is running or not.
Guest Status Provides a description of the Guest's current status. Description
VMware Tools Indicates the current status of VMWare Tools. Status
VMware Tools Provides a description of the current status of VMWare Tools. Status Descrip- tion
Is VMware Tools Indicates whether VMWare Tools is running or not. Running?
Guest CPU Shares Indicates the allocation of CPU resources to the Guest.
CPU Reservation Indicates the minimum amount of CPU resources, in MHz, that have been reserved for use by the Guest.
Guest CPU Limit Indicates the maximum amount of CPU resources, in MHz, that can be used by the Guest.
Host CPU Con- Indicates the current amount of CPU resources, in MHz, that are being used by the Host. sumed
Host CPU Usage Indicates the current amount of CPU resources, expressed as a percentage (%) of the total CPU resources, that are being used by the Host.
CPU Ready Time Indicates the amount of time, in milliseconds, that the virtual machine was ready but could not get scheduled to run on the physical CPU.
CPU Ready Indicates the amount of time, expressed as a percentage (%) of the total CPU availability, that the virtual machine was ready but could not get scheduled to run on the physical CPU.
CPU Count Indicates the number of CPUs used by the virtual machine.
Disk Shares Indicates the amount of virtual hard disk shares that have been allocated to the virtual machine.
IOPs Limit Indicates the maximum number of I/O operations per second that can be used by the vir- tual machine.
Disk Read Rate Indicates the average number of kilobytes read from each virtual disk on the virtual machine during the scan interval.
- 213 - N-central 10.0 Services Reference Manual
Metric Name Description
Disk Write Rate Indicates the average number of kilobytes written to each virtual disk on the virtual machine during the scan interval.
Provisioned Disk Indicates the maximum disk space, in GB, that can be utilized by the virtual machine. Space
Disk Space Used Indicates the amount of disk space, in GB, that is currently being utilized by the virtual machine.
Disk Usage Indicates the amount of disk space, expressed as a percentage (%) of total disk space, that is currently being utilized by the virtual machine.
Memory Shares A configured value that indicates the amount of virtual memory shares that have been alloc- ated to the virtual machine.
Provisioned A configured value that indicates the amount of memory, in GB, that has been guaranteed Memory for use by the virtual machine.
Active Memory Indicates the amount of memory, in GB, that has recently been accessed by the virtual machine.
Active Memory Indicates the amount of memory, expressed as a percentage (%) of total memory, that has (%) recently been accessed by the virtual machine.
Consumed Indicates the amount of memory, in GB, that is being used by the virtual machine. Memory
Consumed Indicates the amount of memory, expressed as a percentage (%) of total memory, that is Memory (%) being used by the virtual machine.
Memory Bal- Indicates the amount of memory, in GB, allocated by the virtual machine memory-man- looning agement driver that controls ballooning.
Memory Reser- A configured value that indicates the minimum amount of memory, in GB, that has been spe- vation cifically reserved for use by the virtual machine.
Memory Limit Indicates the maximum amount of memory, in GB, that can be used by the virtual machine.
Power Con- Indicates the amount of power, in Watts, being used by the virtual machine. sumption
Guest Data The transfer rate, in bytes/second, that the virtual machine receives data. Receive Rate
- 214 - N-central 10.0 Services Reference Manual
Metric Name Description
Guest Data Trans- The transfer rate, in bytes/second, that the virtual machine transmits data. mit Rate
Guest Dropped The number of data packets lost during the reception of data by the virtual machine. Packets (Received)
Guest Dropped The number of data packets lost during the transmission of data by the virtual machine. Packets (Trans- mitted)
Guest Network Indicates the total bandwidth consumption, in KB/second, of the virtual machine. Usage
HTTP Service The Hyper Text Transfer Protocol (HTTP) service monitors a Web server to ensure it is running and publishing Web pages, without reporting any errors. The HTTP service must be added on the Web server, which must also be added as a device in N-central.
The HTTP service also includes Web Transaction Service (WTS) functionality that monitors the specific content on a Web site by searching for a matching regular expression. For example, you can monitor the availability of specific content on an ecommerce site that uses a database-driven architecture. The results from monitoring are displayed on the status dashboard under the HTTP service. If specified, the results can also be provided in any notifications triggered by the service.
During the monitoring process, the HTTP service first attempts to resolve the domain name system (DNS) entry for the Web server. If the DNS test is successful, the service then checks the availability and response time of the Web server using a specified URL. If the DNS test is not successful, the service changes to the Misconfigured state. A code in the response header from the Web server determines whether the server is in a Normal, Warning, or Failed state. The Normal or Warning response codes are tracked as parameters on the status dashboard. The Failed response codes are automatically change the service to the Failed state.
Note: To avoid potential security risks, we recommend that you configure this service to use an account that has limited privileges. A potential security risk exists when generating a Configuration Summary Report for this service. This report will display all of the service's parameters including the passwords for the accounts that are used by the HTTP service to monitor Web servers.
- 215 - N-central 10.0 Services Reference Manual
Service Type TCP
Instances on 20 a Device
Device Class Server - Generic, Other, Printer, Scanner/Camera, Switch/Router, Workstation - Windows, Workstation - Generic, and Server - Windows
Monitored By Windows probe, Central Server
Scan Interval 5 minutes
Timeout The time (in seconds) that the N-central server waits before considering the test a failure. Value The default is 30 seconds.
Port Number 80
Validation HTTP. This field displays a predefined set of characters that the system compares to the String response to determine whether the response is valid.
HTTP URL The URL used to test the availability of the Web server.
For example:
l www.xyz.com,
l index.html,
l http://www.xyz.com/index.html, or
l http://www.xyz.com/
A partial URL of the network address of the Web server can also be used.
Login The username that is used to sign in to the designated URL. The Login Username can be Username used for latency testing but does not need to be configured if the designated web page does not require credentials.
Login The security password that is used to sign in to the designated URL. The Login Password Password can be used for latency testing but does not need to be configured if the designated web page does not require credentials.
- 216 - N-central 10.0 Services Reference Manual
Authenticatio The security authentication scheme used by the designated URL for determining whether n Scheme requests for access are valid or not. This property should be configured as one of the following:
l Basic,
l Digest,
l NTLM,
l Kerberos, or
l Negotiate.
Normal The codes in the response header that indicate a Normal state. Response Code
Warning The codes in the response header that indicate a Warning state. Response Code
Note: Any codes in the response header that are not configured as either a Normal Response Code or a Warning Response Code will result in the service being transitioned into a Failed state.
Content The regular expression used to find a specific match in the content on the Web page. Verification For example: The page cannot be displayed. Regular Expression
- 217 - N-central 10.0 Services Reference Manual
Status Detail Description
HTTP Service The availability of a Web server based on the response code returned by the HTTP Availability response header.
Average Round The average time (in milliseconds) for a request to be sent and received. Trip Time (ms)
DNS Resolution The FQDN or IP address that determines whether the device name can be resolved.
If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
If an IP address has been specified, the service checks only the IP address' format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
Content The regular expression that triggers the status for the matched contents on the Web Verification page. Regular Expression
HTTP Status Code Definitions to HTTP or HTTPS Service Availability The three possible values for HTTP Service Availability or HTTPS Service Availability (Normal: 1, Warning: 2, and, Failed: 0) are based on HTTP Status Code Definitions. RFC 2616 'Hypertext Transfer Protocol -- HTTP/1.1' defines the protocol referred to as "HTTP/1.1". This protocol includes more stringent requirements than HTTP/1.0 in order to ensure reliable implementation of its features.
Normal By default, N-central evaluates the following 'HTTP or HTTPS Status Code Definitions' as Normal (HTTP or HTTPS Service Availability 1):
- 218 - N-central 10.0 Services Reference Manual
Status HTTP or HTTPS Service Avail- Definition RFC Description Code ability
100 Continue RFC 2616 Section Normal (1) 10.1.1
101 Switching Protocols RFC 2616 Section Normal (1) 10.1.2
200 OK RFC 2616 Section Normal (1) 10.2.1
201 Created RFC 2616 Section Normal (1) 10.2.2
202 Accepted RFC 2616 Section Normal (1) 10.2.3
203 Non-Authoritative Inform- RFC 2616 Section Normal (1) ation 10.2.4
204 No Content RFC 2616 Section Normal (1) 10.2.5
205 Reset Content RFC 2616 Section Normal (1) 10.2.6
206 Partial Content RFC 2616 Section Normal (1) 10.2.7
Warning By default, N-central evaluates the following 'HTTP Status Code Definitions' as Warning (HTTP or HTTPS Service Availability 2):
Status Code Definition RFC Description HTTP or HTTPS Service Availability
300 Multiple Choices RFC 2616 Section 10.3.1 Warning (2)
301 Moved Permanently RFC 2616 Section 10.3.2 Warning (2)
302 Found RFC 2616 Section 10.3.3 Warning (2)
303 See Other RFC 2616 Section 10.3.4 Warning (2)
- 219 - N-central 10.0 Services Reference Manual
Status Code Definition RFC Description HTTP or HTTPS Service Availability
304 Not Modified RFC 2616 Section 10.3.5 Warning (2)
305 Use Proxy RFC 2616 Section 10.3.6 Warning (2)
306 (Unused) RFC 2616 Section 10.3.7 Warning (2)
307 Temporary Redirect RFC 2616 Section 10.3.8 Warning (2)
Failed By default, N-central evaluates the following 'HTTP Status Code Definitions' as Failed (HTTP or HTTPS Service Availability 0):
HTTP or HTTPS Ser- Status Code Definition RFC Description vice Availability
400 Bad Request RFC 2616 Section 10.4.1 Failed (0)
401 Unauthorized RFC 2616 Section 10.4.2 Failed (0)
402 Payment Required RFC 2616 Section 10.4.3 Failed (0)
403 Forbidden RFC 2616 Section 10.4.4 Failed (0)
404 Not Found RFC 2616 Section 10.4.5 Failed (0)
405 Method Not Allowed RFC 2616 Section 10.4.6 Failed (0)
406 Not Acceptable RFC 2616 Section 10.4.7 Failed (0)
407 Proxy Authentic- RFC 2616 Section 10.4.8 Failed (0) ation Required
408 Request Timeout RFC 2616 Section 10.4.9 Failed (0)
409 Conflict RFC 2616 Section 10.4.10 Failed (0)
410 Gone RFC 2616 Section 10.4.11 Failed (0)
411 Length Required RFC 2616 Section 10.4.12 Failed (0)
412 Precondition Failed RFC 2616 Section 10.4.13 Failed (0)
- 220 - N-central 10.0 Services Reference Manual
HTTP or HTTPS Ser- Status Code Definition RFC Description vice Availability
413 Request Entity Too RFC 2616 Section 10.4.14 Failed (0) Large
414 Request-URI Too RFC 2616 Section 10.4.15 Failed (0) Long
415 Unsupported Media RFC 2616 Section 10.4.16 Failed (0) Type
416 Requested Range RFC 2616 Section 10.4.17 Failed (0) Not Satisfiable
417 Expectation Failed RFC 2616 Section 10.4.18 Failed (0)
500 Internal Server RFC 2616 Section 10.5.1 Failed (0) Error
501 Not Implemented RFC 2616 Section 10.5.2 Failed (0)
502 Bad Gateway RFC 2616 Section 10.5.3 Failed (0)
503 Service Unavailable RFC 2616 Section 10.5.4 Failed (0)
504 Gateway Timeout RFC 2616 Section 10.5.5 Failed (0)
505 HTTP Version Not RFC 2616 Section 10.5.6 Failed (0) Supported
HTTPS Service The Hypertext Transfer Protocol over Secure Socket Layer (HTTP over SSL or HTTPS) service monitors all of the scan details of the HTTP service and the validity and expiry date of an SSL certificate on a device.
The scan details for the SSL certificates can be monitored only if the certificates have been signed by a Certificate Authority (CA) that has been uploaded in the N-central Administrator Console (NAC) or is listed in the default CA certificate file provided by N-central. For information about uploading the CA Certificate of an SSL certificate, contact your administrator.
Note: The HTTPS service does not currently provide the ability to interact with web sites that use self- signed certificates.
The HTTPS service also includes Web Transaction Service (S) (WTSS) functionality that monitors the specific content on a Web site over a secure Web connection by searching for a matching regular expression. For example, you can monitor the availability of specific content on an ecommerce site that uses a databasedriven architecture. The results from monitoring are displayed on the status dashboard
- 221 - N-central 10.0 Services Reference Manual
under the HTTP service. If specified, the results can also be provided in any notifications triggered by the service.
Note: The N-central HTTPS service does not support forms-based authentication.
Service Type TCP
Instances on 20 a Device
Device Class Server - Generic, Other, Printer, Scanner/Camera, Switch/Router, Workstation - Windows, Workstation - Generic, and Server - Windows
Monitored By Windows probe, Central Server
Scan Interval 5 minutes
Timeout The time (in seconds) that the central server waits before considering the test a failure. Value The default is 30 seconds.
Port Number 443
HTTPS URL The URL used to test the availability of the Web server.
For example:
l www.xyz.com, index.html,
l http://www.xyz.com/index.html, or
l http://www.xyz.com/
A partial URL is accessed using the network address of the Web server.
Login The username that is used to sign in to the designated URL. The Login Username can be Username used for latency testing but does not need to be configured if the designated web page does not require credentials.
Login The security password that is used to sign in to the designated URL. The Login Password Password can be used for latency testing but does not need to be configured if the designated web page does not require credentials.
- 222 - N-central 10.0 Services Reference Manual
Authenticatio The security authentication scheme used by the designated URL for determining whether n Scheme requests for access are valid or not. This property should be configured as one of the following:
l Basic,
l Digest,
l NTLM,
l Kerberos, or
l Negotiate.
Normal The codes in the response header that indicate a Normal state. Response Code
Warning The codes in the response header that indicate a Warning state. Response Code
Note: Any codes in the response header that are not configured as either a Normal Response Code or a Warning Response Code will result in the service being transitioned into a Failed state.
Content The regular expression used to find a specific match in the content on the Web page. Verification For example: The page cannot be displayed. Regular Expression
- 223 - N-central 10.0 Services Reference Manual
Status Detail Description
HTTPS Service The availability of a Web server based on the response code returned by the HTTPS Availability response header.
This will appear as Failed if the CA certificate of the Web server has not been uploaded or if it is not in the default CA certificate file.
Round Trip The time (in milliseconds) for a request to be sent and received. Time (ms)
DNS Resolution The FQDN and IP address that determines whether the device name can be resolved.
If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
If an IP address has been specified, the service checks only the IP address' format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
Server The validity of the SSL certificate (indicated as either valid or invalid). Certificate Signature
Server The number of days remaining before the expiration of the SSL certificate. Certificate Expiration (days)
Content The regular expression that triggers the status for the matched contents on the Web Verification page. Regular Expression
HTTP Status Code Definitions to HTTPS Service Availability The three possible values for HTTPS Service Availability (Normal: 1, Warning: 2, and, Failed: 0) are based on HTTP Status Code Definitions. RFC 2616 'Hypertext Transfer Protocol -- HTTP/1.1' defines the protocol referred to as "HTTP/1.1". This protocol includes more stringent requirements than HTTP/1.0 in order to ensure reliable implementation of its features.
Normal By default, N-central evaluates the following 'HTTP or HTTPS Status Code Definitions' as Normal (HTTP or HTTPS Service Availability 1):
- 224 - N-central 10.0 Services Reference Manual
Status HTTP or HTTPS Service Avail- Definition RFC Description Code ability
100 Continue RFC 2616 Section Normal (1) 10.1.1
101 Switching Protocols RFC 2616 Section Normal (1) 10.1.2
200 OK RFC 2616 Section Normal (1) 10.2.1
201 Created RFC 2616 Section Normal (1) 10.2.2
202 Accepted RFC 2616 Section Normal (1) 10.2.3
203 Non-Authoritative Inform- RFC 2616 Section Normal (1) ation 10.2.4
204 No Content RFC 2616 Section Normal (1) 10.2.5
205 Reset Content RFC 2616 Section Normal (1) 10.2.6
206 Partial Content RFC 2616 Section Normal (1) 10.2.7
Warning By default, N-central evaluates the following 'HTTP Status Code Definitions' as Warning (HTTP or HTTPS Service Availability 2):
Status Code Definition RFC Description HTTP or HTTPS Service Availability
300 Multiple Choices RFC 2616 Section 10.3.1 Warning (2)
301 Moved Permanently RFC 2616 Section 10.3.2 Warning (2)
302 Found RFC 2616 Section 10.3.3 Warning (2)
303 See Other RFC 2616 Section 10.3.4 Warning (2)
- 225 - N-central 10.0 Services Reference Manual
Status Code Definition RFC Description HTTP or HTTPS Service Availability
304 Not Modified RFC 2616 Section 10.3.5 Warning (2)
305 Use Proxy RFC 2616 Section 10.3.6 Warning (2)
306 (Unused) RFC 2616 Section 10.3.7 Warning (2)
307 Temporary Redirect RFC 2616 Section 10.3.8 Warning (2)
Failed By default, N-central evaluates the following 'HTTP Status Code Definitions' as Failed (HTTP or HTTPS Service Availability 0):
HTTP or HTTPS Ser- Status Code Definition RFC Description vice Availability
400 Bad Request RFC 2616 Section 10.4.1 Failed (0)
401 Unauthorized RFC 2616 Section 10.4.2 Failed (0)
402 Payment Required RFC 2616 Section 10.4.3 Failed (0)
403 Forbidden RFC 2616 Section 10.4.4 Failed (0)
404 Not Found RFC 2616 Section 10.4.5 Failed (0)
405 Method Not Allowed RFC 2616 Section 10.4.6 Failed (0)
406 Not Acceptable RFC 2616 Section 10.4.7 Failed (0)
407 Proxy Authentic- RFC 2616 Section 10.4.8 Failed (0) ation Required
408 Request Timeout RFC 2616 Section 10.4.9 Failed (0)
409 Conflict RFC 2616 Section 10.4.10 Failed (0)
410 Gone RFC 2616 Section 10.4.11 Failed (0)
411 Length Required RFC 2616 Section 10.4.12 Failed (0)
412 Precondition Failed RFC 2616 Section 10.4.13 Failed (0)
- 226 - N-central 10.0 Services Reference Manual
HTTP or HTTPS Ser- Status Code Definition RFC Description vice Availability
413 Request Entity Too RFC 2616 Section 10.4.14 Failed (0) Large
414 Request-URI Too RFC 2616 Section 10.4.15 Failed (0) Long
415 Unsupported Media RFC 2616 Section 10.4.16 Failed (0) Type
416 Requested Range RFC 2616 Section 10.4.17 Failed (0) Not Satisfiable
417 Expectation Failed RFC 2616 Section 10.4.18 Failed (0)
500 Internal Server RFC 2616 Section 10.5.1 Failed (0) Error
501 Not Implemented RFC 2616 Section 10.5.2 Failed (0)
502 Bad Gateway RFC 2616 Section 10.5.3 Failed (0)
503 Service Unavailable RFC 2616 Section 10.5.4 Failed (0)
504 Gateway Timeout RFC 2616 Section 10.5.5 Failed (0)
505 HTTP Version Not RFC 2616 Section 10.5.6 Failed (0) Supported
Hyper-V 2008 Guest Status Service The Hyper-V 2008 Guest Status service monitors the status of Hyper-V guests on a Windows Server 2008 device.
Service Type WMI
Instances on a Device 1
Supported Systems/Applications Windows Server 2008
Device Class Server - Windows
Monitored By Windows Agent
Scan Interval 15 minutes
VM Name The name of the guest Virtual Machine.
- 227 - N-central 10.0 Services Reference Manual
Status Details
Status Description Detail
Enabled State Indicates if the Hyper-V guest has been enabled.
Days Running Indicates the number of days that the Hyper-V guest has been active.
Health State Indicates the current status of the Hyper-V guest.
Hyper-V 2012 Guest Status Service The Hyper-V 2012 Guest Status service monitors the status of Hyper-V guests on a Windows Server 2012 R2 device.
Service Type WMI
Instances on a Device 1
Supported Systems/Applications Windows Server 2012 R2
Device Class Server - Windows
Monitored By Windows Agent
Scan Interval 15 minutes
VM Name The name of the guest Virtual Machine.
Status Details
Status Description Detail
Enabled State Indicates if the Hyper-V guest has been enabled.
Days Running Indicates the number of days that the Hyper-V guest has been active.
Health State Indicates the current status of the Hyper-V guest.
Hyper-V Health Service The Hyper-V Health service monitors the status of a Hyper-V server.
- 228 - N-central 10.0 Services Reference Manual
Service Type WMI
Instances on a Device 1
Supported Systems/Applications Windows Server 2012 R2
Device Class Server - Windows
Monitored By Windows Probes
Scan Interval 15 minutes
Status Details
Status Detail Description
Number of Partitions in Critical The total number of partitions in the Hyper-V server that are currently not func- State tioning properly.
Ratio of Virtual to Logical Pro- The number of virtual processors present in the Hyper-V server expressed as a cessors ratio to the total number of logical processors.
Guest Utilization (%) The percentage of processor resources currently in use by guest virtual machines.
Logical Processor 0: % Total The total combined percentage of processor utilization used by guest operating Runtime (%) systems and hypervisor software.
Root CPU: % Utilization The percentage of processor utilization of the root CPU.
Root Virtual Processor: % The percentage of processor utilization of the root virtual processor running as a Hypervisor Runtime (%) hypervisor.
IIS Service The IIS service monitors the availability and performance of the Microsoft Internet Information Server (IIS), which is a group of server applications that are compatible with the Windows NT and Windows 2000 Server operating systems. The IIS sets up and administers Web sites and search engines, and supports the writing of Web-based applications that access databases.
During the monitoring process, the IIS service uses the Windows probe to measure the IIS server's key metrics. The results are displayed on the Windows Services dashboard.
- 229 - N-central 10.0 Services Reference Manual
Service Type WMI
Instances on a Device 1
Supported Microsoft IIS Systems/Applications
Device Class Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Probe
Scan Interval 15 minutes
Web Site Instance Name The name of the Web site that you would like to monitor.
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_W3SVC_WebService
Var.0.Property BytesTotalPersec
Var.1.Property ConnectionAttemptsPersec
Var.2.Property CurrentAnonymousUsers
Var.3.Property CurrentNonAnonymousUsers
Var.4.Property CurrentConnections
Var.5.Property GetRequestsPersec
Var.6.Property LogonAttemptsPersec
Var.7.Property Timestamp_Sys100NS
Var.8.Property Frequency_Sys100NS
Scandetail.0.Recipe (^VarBytesTotal * $timebase08) / ^timeelapse07
Scandetail.1.Recipe (^VarConnectionAttempts * $timebase08) / ^timeelapse07
Scandetail.5.Recipe (^VarGetRequests * $timebase08) / ^timeelapse07
Scandetail.6.Recipe (^VarLogonAttempts * $timebase08) / ^timeelapse07
- 230 - N-central 10.0 Services Reference Manual
IIS Status Details
Status Detail Description
Send and receive bytes/sec The total number of bytes that the server sent and received per second.
Connection attempts/sec The total number of attempts made to connect to the Web per second.
Total anonymous users/sec The total number of anonymous users who accessed a Web page per second.
Total known users/sec The total number of known users who accessed a Web page, per second.
Total current connections The total number of current Web connections.
Total Get requests/sec The total number of "Get" requests made to retrieve Web sites per second.
Total log-on attempts/sec The total number of attempts made to log-on to a Web service per second.
IIS Application Pool Service The IIS Application Pool service is used to obtain metrics for IIS application pools, configured groups of different web applications and web sites that are isolated from other application pools.
Requirements N-central can monitor the IIS Application Pool on devices provided that they meet the following minimum requirements:
l The operating system on the device must be one of the following: o Windows 2003 Server (all editions), o Windows 2003 R2 Server (all editions), o Windows 2008 Server (all editions), or, o Windows 2008 R2 Server (all editions).
l Microsoft .NET 4.0 or later is installed on the device.
l Windows PowerShell 2.0 is installed on the device.
Note: This service can not be associated with devices that use Windows XP, Windows Vista, Windows 7, Windows 8, or Windows 2012 Server (all editions).
- 231 - N-central 10.0 Services Reference Manual
Service Type WMI
Instances on a Device 100
Supported Internet Information Services Systems/Applications (IIS)
Device Class Server - Windows
Monitored By Windows Agent
Scan Interval 15 minutes
Status Detail Description
Application Pool State Indicates the current state of an application pool as one of the following:
l 1 - Uninitialized,
l 2 - Initialized,
l 3 - Running,
l 4 - Disabling,
l 5 - Disabled,
l 6 - Shutdown Pending,
l 7 - Delete Pending
Application Pool Name Indicates the unique identifier assigned to the individual IIS application pool that is being monitored.
Application Pool Indicates the total amount of time, in seconds, that the monitored pool has been Uptime In Seconds running since it was last started.
Work Process Count Indicates the total number of worker processes that have been applied to the pool.
- 232 - N-central 10.0 Services Reference Manual
Status Detail Description
Total Worker Process Indicates the total number of worker processes that have been applied to the pool Failures and that have failed.
Total Work Process Indicates the total number of ping attempts to the pool that have failed. Ping Failures
Total Worker Process Indicates the total number of attempts to shut down worker processes associated Shutdown Failures with the pool that is being monitored that have failed.
Total Worker Process Indicates the total number of attempts to start worker processes associated with the Startup Failures pool that is being monitored that have failed.
IIS ASP.NET Monitoring Service The IIS ASP.NET Monitoring service monitors IIS metrics for application pools, ASP.net metrics and related processes.
Service Type WMI
Instances on a Device 15
Supported Systems/Applications Internet Information Services (IIS)
Device Class Server - Windows
Monitored By Windows Agent
Scan Interval 15 minutes
- 233 - N-central 10.0 Services Reference Manual
Status Description Detail
ASPNET Indicates the number of times that an application has been restarted during the period that the Application web server is monitored. Unexpected increases can indicate that problems are causing your web Restarts applications to recycle. This value is reset to zero every time the Internet Information Services (IIS) host is restarted.
ASPNET Indicates the number of times that a worker process has been restarted on the web server. A Worker Pro- worker process can be restarted if it fails unexpectedly or if it is intentionally recycled. cess Restarts
ASPNET Indicates the amount of time (expressed in milliseconds) that the most recent request waited in the Request Wait queue to be processed. Time
ASPNET Indicates the number of requests waiting for service from the application queue. Apps - Requests In Application Queue
IIS Website Metrics Service The IIS Website Metrics service is used to obtain metrics for web sites hosted using IIS.
Requirements N-central can monitor the IIS Application Pool on devices provided that they meet the following minimum requirements:
l The operating system on the device must be one of the following: o Windows 2003 Server (all editions), o Windows 2003 R2 Server (all editions), o Windows 2008 Server (all editions), o Windows 2008 R2 Server (all editions), or, o Windows 2012 Server (all editions).
l Microsoft .NET 4.0 or later is installed on the device.
l Windows PowerShell 2.0 is installed on the device.
Note: This service can not be associated with devices that use Windows XP, Windows Vista, Windows 7, or Windows 8.
- 234 - N-central 10.0 Services Reference Manual
Service Type WMI
Instances on a Device 100
Supported Internet Information Services Systems/Applications (IIS)
Device Class Server - Windows
Monitored By Windows Agent
Scan Interval 15 minutes
Status Description Detail
Anonymous Indicates the rate at which users are making anonymous requests to the monitored IIS web Users Per site. Second
Bytes Indicates the rate at which data (measured in bytes per second) is received by the monitored Received IIS web site. Per Second
Bytes Sent Indicates the rate at which data (measured in bytes per second) is sent by the monitored IIS Per Second web site.
CGI Indicates the rate at which CGI requests are being processed simultaneously by the monitored Requests IIS web site. Per Second
Files Indicates the rate at which files are received by the monitored IIS web site. Received Per Second
Files Sent Indicates the rate at which files are sent by the monitored IIS web site. Per Second
- 235 - N-central 10.0 Services Reference Manual
Status Description Detail
Get Indicates the rate at which HTTP requests using the GET method are made to the monitored IIS Requests web site. Per Second
Known Indicates the rate at which users are making non-anonymous requests to the monitored IIS Users Per web site. Second
Not Found Indicates the rate of errors (measured per second) due to requests that could not be satisfied Errors Per by the server because the requested document could not be found on the monitored IIS web Second site.
Post Indicates the rate at which requests using the POST method are made to the monitored IIS web Requests site. Per Second
IMAP Service The Internet Message Access Protocol (IMAP) test checks the status of the IMAP process on the network device. IMAP is an email protocol that allows a client to access email messages on a server.
N-central can determine the up or down status of the IMAP service. The IMAP service does not use the Warning state.
N-central averages the availability of the IMAP service over the scan interval. It compares the availability of the IMAP service to the threshold to determine the status.
Service Type TCP
Instances on a Device 1
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows probe, Central Server
- 236 - N-central 10.0 Services Reference Manual
Scan interval 5 minutes
Timeout Value The time (in seconds) that the N-central server waits before considering the test a failure. The default is 30 seconds.
Port Number The port number to be queried. The default port is 143.
Validation String The response you expect to receive from the port that is being queried. If the validation string that you specify is not returned by the port being queried, the service will transition to a Failed state. The default validation string is *OK.
Status Details
Status Detail Description
IMAP Service Availability N-central determines whether the IMAP service is up or down. The IMAP service does not use the Warning state. N-central averages the availability of the IMAP service over the scan interval and compares the availability of the IMAP service to the threshold to determine the status.
Round Trip Time (ms) The time (in milliseconds) for a request to be sent and received.
DNS Resolution The threshold that determines whether the device name can be resolved. If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings. If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
Intel® Quiet System Technology Service The Intel® Quiet System Technology service supports the monitoring of computer operating temperatures in order to reduce perceived noise by minimizing fan speed changes. Intel® Quiet System Technology algorithms are time-based and enhance both thermal control and noise reduction by directing how cooling fans regulate computer operating temperatures.
Intel Quiet System Technology features are only available for Intel® vPro™-enabled devices and only through agents and not probes.
The Intel® Quiet System Technology service is used to monitor sub-components such as fans, fan controllers, voltage regulators and temperature sensors.
Note: Accessing Quiet System Technology sub-systems requires the installation of the Intel Management Engine Interface (MEI) which does not support Windows 2003 Server.
- 237 - N-central 10.0 Services Reference Manual
Service Type QST
Instances on a Device 1
Supported Systems/Applications Intel® QST
Device Class Server - Windows, Workstation - Windows, or Laptop - Windows
Monitored By Local Agent
Scan Interval 5 minutes
Status Details
Status Description Detail
Temperature Indicates the most serious state reported by all of the device's temperature sensors as one of:
Sensors l Normal
l Warning
l Failed
Temperature Reports all information from the device's temperature sensors when error conditions are met. Sensors Info Will not report any information when the temperature state is Normal.
Fan Speed Indicates the most serious state reported by all of the device's fan sensors as one of:
Sensors l Normal
l Warning
l Failed
Fan Speed Reports all information from the device's fan sensors when error conditions are met. Will not Sensors Info report any information when the fan state is Normal.
Voltage Indicates the most serious state reported by all of the device's voltage monitors as one of:
Sensors l Normal
l Warning
l Failed
Voltage Reports all information from the device's voltage monitors when error conditions are met. Will Sensors Info not report any information when the voltage state is Normal.
Fan Controller Indicates the most serious state reported by all of the device's fan controller as one of:
Sensors l Normal
l Warning
l Failed
Fan Controller Reports all information from the device's fan controller when error conditions are met. Will not Sensors Info report any information when the controller state is Normal.
- 238 - N-central 10.0 Services Reference Manual
Intel® vPro™ Agent Status Service The Intel® vPro™ Agent Status service monitors the status of Windows agents on Intel® vPro™- enabled devices by checking the AMT Agent Watchdog on the device for the last time that the agent was active.
Note: It is recommended that a discovery job be performed to ensure that the AMT Agent Watchdog is set up on Intel® vPro™-enabled devices. If a device is entered manually, the AMT Agent Watchdog will not be installed.
This service only monitors IntelN-central vPro™-enabled devices that have an agent. In addition, the Intel® vPro™ Agent Status service will automatically begin monitoring the device when an agent is installed.
If this service enters a Failed state, the central server will disconnect all other services with the exception of the following:
l Agent Status Service on page 65,
l Intel® vPro™ Status Service on page 241,
l System Check-In Service on page 468,
l System Replacement Service on page 469, and
l System Warranty Service on page 470.
To prevent services from being disconnected, ensure that the Unscheduled Downtime check box on the Add Device screen (or in the Properties tab of the Edit Device screen) is not selected.
You can choose to display the Intel® vPro™ Agent Status service in the Active Issues view.
Service Type AMT
Instances on a Device 1
Supported Intel® vPro™ Systems/Applications
Device Class Laptop - Windows, and Workstation - Windows
Monitored By Windows probe
Scan Interval 5 minutes
Status Details
Status Detail Description
Check-In The threshold that compares the time difference between Interval the current time and the most recent connection to the specified threshold values.
- 239 - N-central 10.0 Services Reference Manual
Intel® vPro™ Events Service The Intel® vPro™ Events service scans the event log for Intel® vPro™ events. Multiple instances of this service may be applied to a device up to a limit of five (5) instances.
Note: This service is only available on Intel® vPro™-enabled devices.
You can choose to show this service in the Active Issues view.
Service Type AMT
Instances on a Device 5
Supported Intel® vPro™ Systems/Applications
Device Class any
Monitored By Windows probe
Scan Interval 5 minutes
Timeout Value The time (in seconds) that the N-central server waits before considering the test a fail- ure. The default is 30 seconds
Event Severity List of event severities used to filter events by event severity.
Event Type List of event types used to filter events by event type.
Event Sensor Type List of event sensor types used to filter events by event sensor type.
Event Source Type List of event source types used to filter events by event source type.
Entity List of entities used to filter events by entity.
Event Offset List of event offsets used to filter events by event offset.
Sensor Number List of sensor numbers used to filter events by sensor number.
Entity Instance List of event entity instances used to filter events by entity instance.
Device Address List of device addresses used to filter events by device address.
Status Details
Status Detail Description
Occurence Normal=No event logged as matched. count Failed=More than one event logged as matched.
- 240 - N-central 10.0 Services Reference Manual
Intel® vPro™ Status Service The Intel® vPro™ Status service monitors the network availability of the Intel® vPro™ interface and the power status of an Intel® vPro™ device.
If the Network Connectivity state is Normal (the interface is connected), a device may still be on or off and the Power Status can be Normal or Warning. If Network Connectivity is Failed, Power Status will display Failed, regardless of whether or not the device is on or off. Please refer to the summary below.
You can choose to display the Intel® vPro™ Status service in the Active Issues view.
Service Type AMT
Instances on a Device 1
Supported Intel® vPro™ Systems/Applications
Device Class Server - Windows
Monitored By Windows probe
Scan Interval 5 minutes
Port Number The TCP port number used to monitor a specific Intel® vPro™ device.
Normal Response Code A response code is returned when an Intel® vPro™ device is queried. A response code of 0 or 11 indicates a normal status.
Status Details
Status Detail Description
Network Availability The availability of the Intel® vPro™ interface:
l Normal = The interface is available.
l Failed = The interface is unavailable.
Power Status The power status of the Intel® vPro™ device:
l Normal = The device is on.
l Warning = The device is off.
Power Status State may If Network Connectivity State is... be...
Normal Normal or Warning
Failed Failed
- 241 - N-central 10.0 Services Reference Manual
Interface Health Service The Interface Health service monitors the health of NIC interfaces using SNMP. This service collects inbound discards, inbound errors, outbound discards, outbound errors and outbound queue length from the generic RFC1213-MIB.
To monitor the Interface Health service on a device
1. Configure SNMP on the device (for more information, review the manufacturer's doc- umentation).
2. Login to N-central.
3. Click the All Devices view in the navigation pane.
4. Select the appropriate tab for the type of device that you would like to edit from one of the following: Network Devices, Mobile Devices, or, SaaS Devices.
5. Click the Name of the device on which you would like to monitor the Interface Health ser- vice.
6. If the Use SNMP option has not already been enabled on the Properties tab of the device, select Use SNMP.
Note: You will need to click Save to enable SNMP for the device.
7. On the Status tab, click Add,
8. Type 1 for the number of instances of the Interface Health service that you would like to associate to the device.
9. Click OK.
10. Click the Interface Health service.
11. Click the Service Details tab.
12. For Monitored Interface, select the NICs/ports that you would like to monitor.
Tip: Use CTRL + SHIFT to select multiple NICs/ports.
13. Click OK.
A new instance of the Interface Health service will be created for every NIC or port that is being monitored.
- 242 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a 400 Device
Supported Any SNMP MIB-II Compliant Device (RFC1213-MIB or IF-MIB) Systems/Applicatio ns
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, and Server - Windows
Monitored By Windows Probes
Scan Interval 5 minutes
Monitored Interface Select the the NICs or ports that you would like to monitor (identified by SNMP Index, Interface Name, or Interface Alias.
Tip: Hold down CTRL or SHIFT to select multiple NICs or ports.
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
- 243 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Inbound Discards 1.3.6.1.2.1.2.2.1.13
Calculation: Sample2 - Sample1
Inbound Errors 1.3.6.1.2.1.2.2.1.14
Calculation: Sample2 - Sample1
Outbound Discards 1.3.6.1.2.1.2.2.1.19
Calculation: Sample2 - Sample1
Outbound Errors 1.3.6.1.2.1.2.2.1.20
Calculation: Sample2 - Sample1
- 244 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Administrative Status 1.3.6.1.2.1.2.2.1.7
Operational Status 1.3.6.1.2.1.2.2.1.8 Mapped as follows:
Normal: 1, 5
Warning: 2
Failed: 3, 4, 6, 7
The meaning of the status:
1: Up
2: Down
3: Testing
4: Unknown
5: Dormant
6: Not Present
7: Lower Layer Down
Operational Status Describes the operational status: Description Up
Down
Testing
Unknown
Dormant
Not Present
Lower Layer Down
Detected Port Speed 1.3.6.1.2.1.2.2.1.5 Indicates the interface's current bandwidth in bits per second.
Intrusion Detection Service The Intrusion Detection service monitors events that are generated by Snort and any other intrusion detection applications installed on your network.
- 245 - N-central 10.0 Services Reference Manual
The intrusion detection application searches the network packets for suspicious patterns that match its predefined class-types and logs them to a local log file or to its database. If the intrusion detection application has been configured to log its events to a local log file, then N-central can monitor the application.
During the monitoring process, the agent that is used for the Intrusion Detection service scans the log file for any keywords that match the regular expressions specified for the service. If a match is found, the agent reports it to the central server. Based on the specified threshold, N-central then displays the appropriate status for the service.
If the status triggers a notification, the notification includes the first line and the line numbers on which the keyword was found unless a numeric pager was used for the notification. The first line and any subsequent line numbers are also displayed in the applicable reports and on the status details screen for the service. This service also supports wide characters.
By default, the Snort class-types are contained in the service's regular expressions, which are classified as Failed or Warning.
Note: The Intrusion Detection service is supported by the Linux agent and all of the Windows agents.
Service Type Log Appended
Instances on a Device 1
Supported Snort and IDS applications Systems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent (Windows and Red Hat Enterprise Linux)
Scan Interval 5 minutes
Log File Name and Path The directory path and name of the log file that is to be monitored by this service. The name and path specified can be complete or partial, and will change depending on the Intrusion Detection software you use. For example: C:\N-able\Rocks\MSP.log
- 246 - N-central 10.0 Services Reference Manual
Critical (1) Regular Expression 1
Class Type Description
attempted-admin Attempted Administrator Privilege Gain
attempted-user Attempted User Privilege Gain
shellcode-detect Executable code was detected
successful-user Successful Administrator Privilege Gain
successful-admin Successful User Privilege Gain
Critical (2) Regular Expression 2
Class Type Description
trojan activity A Network Trojan was detected
unsuccessful-user Unsuccessful User Privilege Gain
web-application attack Web Application Attack
Warning (1) Regular Expression 3
Class Type Description
attempted-dos Attempted Denial of Service
attempted-recon Attempted Information Leak
bad-unknown Potentially Bad Traffic
denial-of-service Detection of a Denial of Service Attack
misc-attack Misc Attack
non-standard-protocol Detection of a non-standard protocol or event
rpc-portmap-decode Decode of an RPC Query
successful-dos Denial of Service
- 247 - N-central 10.0 Services Reference Manual
Class Type Description
successful-recon- Large Scale Information Leak largescale
successful-recon-limited Information Leak
suspicious-filename-detect A suspicious filename was detected
suspicious-login An attempted login using a suspicious username was detected
Warning (2) Regular Expression 4
Class Type Description
system-call-detect A system call was detected
unusual-client-port- A client was using an unusual port connection
web-application-activity access to a potentially vulnerable web application
Other status details
Status Details Class Type Description
The line count Off The number of lines, in the log file, on matched regex... which the keyword has been located and returned by the agent. This information is displayed for each regular expression on the status details screen for the service, any applicable reports, and any triggered notifications (except for numeric pages).
The first line matched The first 250 characters of the first line, in the log file, containing the matching keyword returned by the agent. This information is displayed on the service's status details screen, any applicable reports, and any triggered notifications (except for numeric pages).
ISA 2000 Service The ISA 2000 service monitors the availability of the Microsoft Internet Security and Acceleration (ISA) server, which serves as an enterprise firewall and a cache server. The ISA firewall scans circuit,
- 248 - N-central 10.0 Services Reference Manual
application, and packet data and the ISA cache server manages Web page requests and provides faster access to frequently used sites by saving them.
During the monitoring process, the ISA 2000 service uses the Windows probe to measure the ISA server's key metrics. The results are then displayed on the dashboard for the service.
Service Type WMI
Instances on a Device 1
Supported Microsoft ISA server and the enterprise edition of the ISA server 2000 Systems/Applications
Device Class Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows probe
Scan Interval 5 minutes
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_BwcPerf_ISAServerBandwidthControl
WMI Property 0 Actualinboundbandwidth
WMI Property 1 Actualoutboundbandwidth
Namespace root\cimv2
WMI Class Win32_PerfRawData_Fwsrv_ISAServerFirewallService
WMI Property 0 ActiveSessions
Namespace root\cimv2
WMI Class Win32_PerfRawData_isactrl_ISAServerPacketFilter
WMI Property 0 Packetsdroppedduetofilterdenial
WMI Property 1 Packetsdroppedduetoprotocolviolations
Namespace root\cimv2
WMI Class Win32_PerfRawData_W3Proxy_ISAServerWebProxyservice
WMI Property 0 CacheRunningHitRatioPercent
WMI Property 1 RequestsPersec
- 249 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Inbound bandwidth The amount of incoming traffic.
Outbound bandwidth The amount of outgoing traffic.
Current active sessions The total number of current Web sessions.
Packets dropped by filter The total number of packets that were dropped based on the denial firewall policies set by your organization.
Packets dropped by protocol breach
Cache running hit ratio (%) The hit rate for the last specified number of requests. This helps you determine the current performance of the ISA server's cache.
Total requests/sec The number of times data is requested from a cache per second.
ISA 2006 Service The ISA 2006 service monitors the Microsoft Internet Security and Acceleration (ISA) 2006 server for the following:
l active connections,
l connections/second,
l traffic,
l dropped packets/second,
l packets/second,
l active sessions,
l requests/second, and,
l average milliseconds/request.
During the monitoring process, the ISA 2006 service uses the Windows probe to measure the ISA server's key metrics. The results are then displayed on the dashboard for the service.
Service Type WMI
Instances on a Device 1
Supported Any WMI-enabled Microsoft ISA 2006 server Systems/Applications
Device Class Server - Windows
Monitored By Windows probe
Scan Interval 5 minutes
- 250 - N-central 10.0 Services Reference Manual
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_FWeng_ISAServerFirewallPacketEngine
WMI Property 0 ActiveConnections
WMI Property 1 ConnectionsPerSec
WMI Property 2 BytesPerSec
WMI Property 3 DroppedPacketspersec
WMI Property 4 Packetspersec
WMI Property 5 Timestamp_Sys100NS
WMI Property 6 Frequency_Sys100NS
Namespace root\cimv2
WMI Class Win32_PerfRawData_Fwsrv_ISAServerFirewallService
WMI Property 0 ActiveSessions
Namespace root\cimv2
WMI Class Win32_PerfRawData_W3Proxy_ISAServerWebProxy
WMI Property 0 Requestspersec
WMI Property 1 AverageMillisecondsPerRequest
WMI Property 2 Timestamp_Sys100NS
WMI Property 3 Frequency_Sys100NS
WMI Property 4 TotalRequests
Scandetail.1.Recipe (^ConnectionsPerSec / ^ATimestamp_Sys100NS) / $AFrequency_Sys100NS
Scandetail.2.Recipe (^BytesPerSec 8 * ^ATimestamp_Sys100NS) / $AFrequency_Sys100NS
Scandetail.3.Recipe (^DroppedPacketspersec / ^ATimestamp_Sys100NS) $AFrequency_Sys100NS /
- 251 - N-central 10.0 Services Reference Manual
Scandetail.4.Recipe (^Packetspersec / ^ATimestamp_Sys100NS) / $AFrequency_Sys100NS
Scandetail.5.Recipe $ActiveSessions
Scandetail.6.Recipe (^Requestspersec * $BFrequency_Sys100NS) / ^BTimestamp_Sys100NS
Scandetail.7.Recipe ^AverageMillisecondsPerRequest / ^TotalRequests
Status Details
Status Detail Description
Active Connections Indicates the total number of active connections currently passing data as one of the following:
l Normal
l Warning
l Failed
Connections/sec Indicates the number of new connections created per second as one of the following:
l Normal
l Warning
l Failed
Traffic Indicates the number of bytes passed through the ISA 2006 Server per second.
Dropped Packets/sec Indicates the number of packets dropped by ISA Server per second as one of the following:
l Normal
l Warning
l Failed
- 252 - N-central 10.0 Services Reference Manual
Status Detail Description
Packets/sec Indicates the number of packets inspected by ISA Server per second as one of the following:
l Normal
l Warning
l Failed
Active Sessions Indicates the number of active sessions for the firewall service as one of the following:
l Normal
l Warning
l Failed
Requests/Sec Indicates the rate of incoming requests that have been made to the web proxy as one of the following:
l Normal
l Warning
l Failed
Average Mil- Indicates the mean number of milliseconds required to service a liseconds/Request web proxy client request as one of the following:
l Normal
l Warning
l Failed
Juniper (ScreenOS) - Sessions Service The Juniper (ScreenOS) - Sessions service monitors the number of sessions being handled by a Juniper device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Netscreen OS 5.4 and later Systems/Applications
Device Class Other, Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
- 253 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Active Sessions 1.3.6.1.4.1.3224.16.3.2
Total Sessions 1.3.6.1.4.1.3224.16.3.3
Sessions Used (Active Sessions / Total Sessions) x 100
Juniper Secure Access - Concurrent Users Service The Juniper Secure Access - Concurrent Users service monitors the number of currently logged in users of a Juniper Secure Access (SA) device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported IVE OS 6.0 and later Systems/Applications
Device Class Other, Switch/Router
Monitored By Windows Probe
Scan Interval 5
Users Index Enter the SNMP Index of the Users on the Juniper SA device (default=0). For a list of indices on the Juniper device, query it with the 1.3.6.1.4.1.12532.12 SNMP OID.
OID/Calculation
Metric Name OID/Calculation Description
CPU Utilization 1.3.6.1.4.1.12532.12 The total number of users logged into the IVE console.
Lexmark - Hopper Status Service The Lexmark Hopper Status service monitors Lexmark printers to see if the output hopper is full.
Note: This service cannot use N-central’s Self-Healing feature.
- 254 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Lexmark N4000e, MarkNet N2000t, MarkNet N2001e, MarkNet N2002e, MarkNet Systems/Applications N2003fx, MarkNet N2401e, MarkNet N2501e, MarkNet N2601e, MarkNet Pro, MarkNet Pro 1, MarkNet Pro 3, MarkNet S, MarkNet X2011e, MarkNet X2012e, MarkNet X2030t, MarkNet X2031e, MarkNet XI, MarkNet XL, MarkNet XLe, MarkNet XP, N5 Wireless Adapter
Device Class Printer
Monitored By Windows probe
Scan Interval 5 minutes
OID/Calculation
Metric Name OID/Calculation Description
Output Hopper Status 1.3.6.1.4.1.641.2.1.3.1.3 The Output Hopper Status metric is mapped as follows: Normal: 1 Warning: 3 Failed: 2
Meaning of the status: 1: Not Full 2: Full 3: Unknown
Output Hopper Status Describes the status of the output hopper: Description Not Full
Full
Unknown
Lexmark - Paper Jam Status Service The Lexmark Paper Jam Status service monitors Lexmark devices for any jammed paper problems.
Note: This service cannot use N-central’s Self-Healing feature.
- 255 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Lexmark N4000e, MarkNet N2000t, MarkNet N2001e, MarkNet N2002e, MarkNet Systems/Applications N2003fx, MarkNet N2401e, MarkNet N2501e, MarkNet N2601e, MarkNet Pro, MarkNet Pro 1, MarkNet Pro 3, MarkNet S, MarkNet X2011e, MarkNet X2012e, MarkNet X2030t, MarkNet X2031e, MarkNet XI, MarkNet XL, MarkNet XLe, MarkNet XP, N5 Wireless Adapter
Device Class Printer
Monitored By Windows probe
Scan Interval 5 minutes
OID/Calculation
Metric Name OID/Calculation Description
Paper Jam Status 1.3.6.1.4.1.641.2.1.3.1.5 The Paper Not Jammed metric status is mapped as follows: Normal: 1 Warning: 3 Failed: 2
Meaning of the status: 1: Not Jammed 2: Jammed 3: Unknown
Paper Jam Status 1.3.6.1.4.1.641.2.1.3.1.5 Describes the status: Description Not Jammed Jammed unknown
Lexmark - Tray Status Service The Lexmark Tray Status service monitors the status of the input paper tray of Lexmark printers.
Note: This service cannot use N-central’s Self-Healing feature.
- 256 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Lexmark N4000e, MarkNet N2000t, MarkNet N2001e, MarkNet N2002e, MarkNet Systems/Applications N2003fx, MarkNet N2401e, MarkNet N2501e, MarkNet N2601e, MarkNet Pro, MarkNet Pro 1, MarkNet Pro 3, MarkNet S, MarkNet X2011e, MarkNet X2012e, MarkNet X2030t, MarkNet X2031e, MarkNet XI, MarkNet XL, MarkNet XLe, MarkNet XP, N5 Wireless Adapter
Device Class Printer
Monitored By Windows probe
Scan Interval 5 minutes
OID/Calculation
Metric Name OID/Calculation Description
Input Tray Status 1.3.6.1.4.1.641.2.1.3.1.4 The Input Tray Status metric is mapped as follows: Normal: 1 Warning: 3 Failed: 2
Meaning of the status: 1: Not Empty 2: Empty 3: Unknown
Input Tray Status Describes the status of the paper tray: Description Not Empty Empty unknown
License Compliance Service The License Compliance service monitors the number of software licenses allowed for a customer based on the thresholds specified for individual applications. For example, if a customer has a total of 100 licenses for an application and 88 instances of the application are discovered on their network, this service will report that 88% of the available licenses are in use.
Note: This service cannot use N-central’s Self-Healing feature.
To configure license monitoring for a customer, refer to "Setting the License Compliance Service Details" in the online help.
- 257 - N-central 10.0 Services Reference Manual
Note: This service is available only for Windows devices that have been discovered by a Windows Agent or a Windows probe.
Service Type System
Instances on a Device 1 (one for each customer account)
Supported Systems/Applications Microsoft® Windows®
Device Class Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Probe
Scan Interval 30 minutes
Status Details
Status Detail Description
Vendor The name of the vendor or publisher of the application.
Software Name The name of the application.
Version The version of the application.
Licenses The number of licenses for the application.
Percent of The current number of licenses in use expressed as a percentage of the total number of licenses used application licenses allowed.
Detected The total number of application licenses discovered to be currently in use. Installations
Licensing Status (VMware) Service The Licensing Status (VMware) service monitors the VMware licenses on ESXi servers.
Service Type ESXi
Instances on a Device 1
Supported vCenter, ESX or ESXi 4.x, 5.x and Systems/Applications later
Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
- 258 - N-central 10.0 Services Reference Manual
Monitored By Windows Probes
Scan Interval 5 minutes
To access information on the licenses on your ESXi server, use a browser to access the following URL:
https://
Example: https://192.168.101.207/mob/?moid=ha-license-manager&doPath=licenses
Metric Name Description
License Key The license key of the ESXi server.
License Days The number of days remaining before the expiration of the VMware license. Remaining
License Details The name and other properties of the VMware license issued to the ESXi server.
LocalIP Service The LocalIP test allows you to keep the N-central database up to date by checking the IP address of a monitored device. The Local IP test returns the IP address of the monitored device to the central server and displays it on the details screen for a device. You should use the Local IP test to monitor networks that use dynamic IP addressing.
If you would like to monitor the local IP of a device, you select Update Monitored Address on the Agent tab of the device. Selecting this option causes the central server to update the device's network address that is monitored by the server. The central server updates the address when the device's local IP address changes based on the information gathered by the agent on the device.
N-central does not monitor the status of the Local IP service and cannot create reports for it.
Service Type Local API
Instances on a 1 Device
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent (Windows)
- 259 - N-central 10.0 Services Reference Manual
Scan Interval 5 minutes
About the LocalIP Address (%) Threshold
The LocalIP Address (%) threshold value is 100 in the following situations:
l when the Local IP service first scans, or
l if the local agent is manually restarted, or
l if the scanned IP address does not equal the defined address in the device settings network address field.
The Local IP Address (%) threshold value is 50 if the scanned IP address equals the defined in the device settings network address field.
Log Analysis (Appended) Service The Log Analysis (Appended) is an agent-based service and works only on log files that are located on a file system that is local to the agent. It allows you to monitor text that an application, such as a Web server or a firewall, writes to its log file. During the monitoring process, the service executes a check on the log file at regular intervals, and it scans logged lines that were added to the file since its last execution. Through the use of regular expression matching and timestamp comparison, this service can notify you when the application stops logging to its log file, or when it logs an error or a warning message. This service monitors up to 4 log files for each device and supports wide characters.
Service Log Appended Type
Instances 10 on a Device
Device Server - Generic and Server - Windows Class
Monitored Agent (Windows, Red Hat Enterprise Linux, and Mac OSX 10.4) By
Scan 5 minutes Interval
Log File The directory path and name of the log file that is to be monitored by the service. The name and Name and path specified can be complete or partial. You must specify the directory name as well, for Path example: c:\\test.log
- 260 - N-central 10.0 Services Reference Manual
Status Details
Status Description Detail
File Size N-central reads the size of the file and compares it with the values your threshold specifications. (Bytes) Threshold options can vary for each specified regular expression.
Regular The thresholds for the regular expressions that you specified on the Service Details tab. Expressions (1 to 6)
Difference N-central compares the values that you specify in this field with the age of the log file that is in calculated by the agent. The age is the difference between the time the log file was generated minutes... and the current time.
Line Count The number of lines in the file that are scanned and compared with your threshold specifications. of Log File
The line The number of lines, in the log file, on which the keyword has been located and returned by the count agent. This information is displayed for each regular expression on the status details screen for matched the service, any applicable reports, and any triggered notifications (except for numeric pages). regex...
The first The first 250 characters of the first line, in the log file, containing the matching keyword line returned by the agent. This information is displayed on the service's status details screen, any matched applicable reports, and any triggered notifications (except for numeric pages).
Log Analysis (Batch) Service The Log Analysis (Batch) is an agent-based service and works only on log files that are located on a file system that is local to the agent. It allows you to monitor text that N-central writes to a log file during the execution of a scheduled process or task, such as a nightly virus scan or a weekly backup. During the monitoring process, the service scans the complete log file created during the scheduled process. Through the use of regular expression matching and timestamp comparison, it ensures that the task was completed successfully.
Each time N-central or the application performs a scheduled task or process, it creates a new Batch log file. The names of the files are numbered in sequence according to a specific application's recording convention. The Log Analysis (Batch) service uses the latest modified date as the metric to determine which log file it should scan during the monitoring process. This service monitors up to 4 log files for each device and supports wide characters.
- 261 - N-central 10.0 Services Reference Manual
Service Log Batch Type
Instances 10 on a Device
Device Server - Generic and Server - Windows Class
Monitored Agent (Windows, Red Hat Enterprise Linux, and Mac OSX 10.4) By
Log File The directory path and name of the log file that is to be monitored by the service. The name and Name and path specified can be complete or partial. You must specify the directory name as well, for example: Path c:\\test.log
Scan 5 minutes Interval
Repeat The scan is repeated weekly on the specified days. Weekly on Days
Repeat The scan is repeated monthly on the specified days. Monthly on Days
- 262 - N-central 10.0 Services Reference Manual
Status Details
Status Description Detail
File Size N-central reads the size of the file and compares it with the values your threshold specifications. (Bytes) Threshold options can vary for each specified regular expression.
Regular The thresholds for the regular expressions that you specified on the Service Details tab. Expressions (1 to 6)
Last Parse- The time zone off-set based on Greenwich Mean Time (GMT) or Universal Time Coordinated able Dates (UTC). Time Zone
Difference N-central compares the values that you specify in this field with the age of the log file that is in calculated by the agent. The age is the difference between the time the log file was generated minutes... and the current time.
Number of N-central scans the number of lines in the file and compares it with your threshold lines in the specifications. file
The line The number of lines, in the log file, on which the keyword has been located and returned by the count agent. This information is displayed for each regular expression on the status details screen for matched the service, any applicable reports, and any triggered notifications (except for numeric pages). regex...
The first The first 250 characters of the first line, in the log file, containing the matching keyword line returned by the agent. This information is displayed on the service's status details screen, any matched applicable reports, and any triggered notifications (except for numeric pages).
Logical Drive (Adaptec) Service The Logical Drive (Adaptec) service monitors the status of the specified logical drive on an Adaptec RAID controller.
Note: Adaptec Storage Manager or IBM ServeRAID Manager must be installed on the machine that you would like to monitor. For a complete list of supported models, please refer to:
l http://www.adaptec.com/en-US/products/asm/, or,
l https://www-304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR- 61707&brandind=5000008
- 263 - N-central 10.0 Services Reference Manual
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type SNMP
Instances on a Device 10
Supported Any device using an Adaptec HostRAID card or an IBM ServeRAID card. Systems/Applications
Device Class Server - Generic and Server - Windows
Monitored By Windows Probes
Scan Interval 5 minutes
Logical Drive The name of the logical drive to be monitored. The name can be obtained by querying the device with the .1.3.6.1.4.1.795.14.1.1000.1.1.2 SNMP OID.
- 264 - N-central 10.0 Services Reference Manual
OID/Calculation
- 265 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Logical Drive State 1.3.6.1.4.1.795.14.1.1000.1.1.7 Logical Drive State is mapped as follows: Normal: 3 Warning: 1,2,4,5,6,8 Failed: 7
The meanings for each of the possible drive states: 1: Unknown 2: Other 3: Optimal 4: QuickInited 5: Impacted 6: Degraded 7: Failed 8: Compacted
Logical Drive State 1.3.6.1.4.1.795.14.1.1000.1.1.7 Describes the current health of the logical drive Description as one of: Unknown Other Optimal QuickInited Impacted Degraded Failed Compacted
RAID Level 1.3.6.1.4.1.795.14.1.1000.1.1.4 Indicates the RAID level used by this array.
- 266 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Task 1.3.6.1.4.1.795.14.1.1000.1.1.6 Task is mapped as follows: Normal: 3 Warning: 1,2,4,5,6,7,8,9,10,11,12
The meanings for each of the possible mappings: 1: Unknown 2: Other 3: No Task Active 4: Reconstruct 5: Zero Initialize 6: Verify 7: Verify With Fix 8: Modification 9: Copyback 10: Compaction 11: Expansion 12: Snapshot Backup
Task Description 1.3.6.1.4.1.795.14.1.1000.1.1.6 Describes the task status of the logical drive as one of: Unknown Other No Task Active Reconstruct Zero Initialize Verify verify With Fix Modification Copyback Compaction Expansion Snapshot Backup
- 267 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Task Completion 1.3.6.1.4.1.795.14.1.1000.1.1.7 Task is mapped as follows: Normal: 3 Warning: 1,2,4,5,6,7,8,9,10,11,12
The meanings for each of the possible mappings: 1: Unknown 2: Other 3: No Task Active 4: Reconstruct 5: Zero Initialize 6: Verify 7: Verify With Fix 8: Modification 9: Copyback 10: Compaction 11: Expansion 12: Snapshot Backup
Logical Drive (Dell OM 2.2) Service The Logical Drive (Dell OM 2.2) service monitors the overall status of a logical drive on a Dell server running Dell OpenManage Version 2.2 and later.
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
- 268 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 256
Supported Dell PowerEdge series servers running Dell OpenManage Server Administrator Systems/Applications Version 2.2 and later
Device Class Server - Generic and Server - Windows
Monitored By Windows Probes
Scan Interval 15 minutes
Virtual Disk State Index The SNMP index of the logical volume to be monitored.
- 269 - N-central 10.0 Services Reference Manual
OID/Calculation
- 270 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Virtual Disk Status 1.3.6.1.4.1.674.10893.1.20.140.1.1.4 Virtual Disk Status is mapped as follows: Normal = 1,3 Warning = 5-4294967295 Failed = 2,4
Where: 1 = Ready 2 = Failed 3 = Online 4 = Offline 6 = Degraded 7 = Verifying 15 = Resynching 18 = Failed Reduncancy 24 = Rebuilding 26 = Formatting 35 = Initializing
Virtual Disk Roll Up 1.3.6.1.4.1.674.10893.1.20.140.1.1.19 Virtual Disk Roll Up Status is mapped as Status follows: Normal = 3 Warning = 1,2,4,7-4294967295 Failed = 5-4294967295
Where: 1 = Other 2 = Unknown 3 = OK 4 = Non-critical 5 = Critical 6 = Non-recoverable
- 271 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Virtual Disk Component 1.3.6.1.4.1.674.10893.1.20.140.1.1.20 Virtual Disk Component Status is Status mapped as follows: Normal = 3 Warning = 1,2,4,7-4294967295 Failed = 5,6
Where: 1 = Other 2 = Unknown 3 = OK 4 = Non-critical 5 = Critical 6 = Non-recoverable
Logical Drive (Fujitsu) Service The Logical Drive (Fujitsu) service monitors the status of a logical drive on a Fujitsu server.
Service Type SNMP
Instances on a Device 100
Supported Fujitsu servers running the Fujitsu ServerView agent. Systems/Applications
Device Class for CPU Servers - Generic or Servers - Windows (SNMP)
Monitored By Windows Agent
Logical Drive Type the name of the logical drive to be monitored. For a list of logical drives, query the device with the .1.3.6.1.4.1.231.2.49.1.6.2.1.14 SNMP OID.
Scanning The scan interval can be configured according to either a Once a Day or Daily Interval schedule.
- 272 - N-central 10.0 Services Reference Manual
Object Numerical OID Descriptors
$Status 1.3.6.1.4.1.231.2.49.1.6.2.1.19
$ArraySize 1.3.6.1.4.1.231.2.49.1.6.2.1.3
$RAIDLevel 1.3.6.1.4.1.231.2.49.1.6.2.1.6
$StripeSize 1.3.6.1.4.1.231.2.49.1.6.2.1.7
$WriteMode 1.3.6.1.4.1.231.2.49.1.6.2.1.8
$ReadMode 1.3.6.1.4.1.231.2.49.1.6.2.1.15
$CacheMode 1.3.6.1.4.1.231.2.49.1.6.2.1.16
$DiskCacheMode 1.3.6.1.4.1.231.2.49.1.6.2.1.17
$InitializationStatus 1.3.6.1.4.1.231.2.49.1.6.2.1.18
- 273 - N-central 10.0 Services Reference Manual
Status Description Detail
Status Describes the current status of the logical drive that is being monitored with values mapped as follows:
Normal: 2
Failed: 1, 3-14
1. Unknown 2. Operational 3. Partially Degraded 4. Degraded 5. Failed 6. Rebuilding 7. Checking 8. MDCing 9. Initializing 10. Background Initializing 11. Migrating 12. Copying 13. Offline 14. In Use Spare
Initializati Describes the current status of the initialization of the logical drive with values mapped as on Status follows:
Normal: 2
Failed: 1, 3
1. Unknown 2. Initialized 3. Not Initialized
Array Indicates the total size of the disk array. Size
RAID Indicates the RAID level used by this array. Level
Stripe Specifies the size of the stripe (equal-sized sections of the associated hard disks to which the Size data is distributed) for the logical drive that is being monitored.
- 274 - N-central 10.0 Services Reference Manual
Status Description Detail
Write Specifies the write mode for the logical drive which can be configured as one of the following: Mode
l Write−back - The controller sends a signal to the server when the data has been written to the controller's cache.
l Write−through - The controller sends a signal to the server only when the data has been written to the drive.
l Adaptive - When a charged battery is connected, this configuration operates as described under Write−back. If a charged battery is not connected, the controller behaves similarly to the Write−through option.
l Adaptive write−back - This display appears when Adaptive is selected and the con- troller currently handles the write requests as described under Write−back. After a bat- tery failure, the controller automatically switches to Write−through.
l Adaptive write−through - This display appears when Adaptive is selected and the con- troller currently handles the write requests as described under Write−through. When a charged battery becomes available again, the controller automatically switches back to Write−back.
Read Specifies the read mode for the logical drive which can be configured as one of the following: Mode
l Read-ahead - Uses advance read-access to the memory.
l No read−ahead - No advance read-access to the memory is used.
l Adaptive - When most of the last read-accesses to successive sectors have taken place, the controller switches to Read−ahead mode. When the read-accesses have been dis- tributed, it switches back to No read−ahead mode.
Cache Specifies whether Read and Write operations are forwarded directly or are buffered in the Mode cache.
Disk Specifies the current status of the disk cache mode. Cache Mode
Logical Drive (Intel) Service The Logical Drive (Intel) service monitors the status of the logical drive attached to a supported Intel® RAID controller.
- 275 - N-central 10.0 Services Reference Manual
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type SNMP
Instances on 1 a Device
Monitored By Windows Probe
Scan Interval 60 minutes
Drive Iden- Type the SNMP identifier for the drive. The identifier can be found by querying the device with tifier the 1.3.6.1.4.1.3582.4.1.4.3.1.2.1.1 SNMP OID.
OID/Calculation
Metric Name OID/Calculation Description
Logical Drive 1.3.6.1.4.1.3582.4.1.4.3.1.2. The current state of the monitored logical drive is State 1.5 mapped as follows:
l Normal= 3
l Warning= 1,2
l Failed= 0
The meanings for each of the possible drive states:
l 0: Offline
l 1: Partially Degraded
l 2: Degraded
l 3: Optimal
Logical Drive 1.3.6.1.4.1.3582.4.1.4.3.1.2. The name of the logical drive to be monitored. Name 1.6
- 276 - N-central 10.0 Services Reference Manual
Logical Drive (VMware) Service The Logical Drive (VMware) service monitors the status of a logical drive on an ESXi server.
Note: If your ESX/ESXi server is operating on either Dell or HP hardware, it is strongly recommended that you install the Dell or HP Offline Bundle before the Windows Probe discovers the ESX/ESXi server. For instructions on installing the Dell or HP Offline Bundle, refer to the following articles in the N-central online knowledge base:
l KBA10019: Installing the HP Offline Bundle on ESX/ESXi Servers
l KBA10020: Installing the Dell Offline Bundle on ESX/ESXi Servers
A Logical Drive (also referred to as a Storage Adapter) represents a drive (either local or available through a SAN) that can be accessed by an ESXi server. When a Guest issues a read or write command, that command must first be processed by the VMware kernel and then by the physical drive itself. The Logical Drive (VMware) service provides in-depth monitoring of that process including:
l How long the ESXi kernel takes to process read and write commands (which may indicate a CPU issue on the host).
l How long the physical drive takes to process read and write commands (which may indicate an overloaded/under-performing physical drive).
l Whether any read/write commands that have been issued were aborted because the ESXi server itself was unable to process them in time.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type ESXi
Instances on a Device 100
Supported ESX or ESXi 4.x, 5.x and later Systems/Applications Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 5 minutes
Logical Drive Name The name of the logical drive to be monitored.
- 277 - N-central 10.0 Services Reference Manual
To access information on the logical drives on your ESXi server, use a browser to access the following URL:
https://
Example: https://192.168.101.207/mob/?moid=ha- host&doPath=runtime.healthSystemRuntime.hardwareStatusInfo.storageStatusInfo
Metric Description Name
Read Average amount of time, in milliseconds, to complete read from the physical device. Latency (msec)
Write Average amount of time, in milliseconds, to write to the physical device (LUN). Latency (msec)
Disk Com- Number of SCSI commands issued during the collection interval. mands
Aborted Number of SCSI commands aborted during the collection interval. Disk Com- mands
Data Trans- The amount of data, in megabytes, transferred from the logical drive. ferred (MB)
Data The amount of data, in kilobytes, received by the logical drive. Received (KB)
Bus Resets Number of SCSI-bus reset commands issued during the collection interval.
- 278 - N-central 10.0 Services Reference Manual
Metric Description Name
Device Average amount of time, in milliseconds, to complete a SCSI command from the physical device. Latency (msec)
Kernel Average amount of time, in milliseconds, spent by VMkernel processing each SCSI command. Latency (msec)
Queue Average amount of time spent in the VMkernel queue, per SCSI command, during the collection Latency interval. (msec)
Total Highest latency value across all disks used by the host. Latency measures the time taken to pro- Latency cess a SCSI command issued by the guest OS to the virtual machine. The kernel latency is the (msec) time VMkernel takes to process an IO request. The device latency is the time it takes the hardware to handle the request.
Maintenance Mode (VMware) Service The Maintenance Mode (VMware) service monitors the ESXi servers for whenever they enter Maintenance Mode.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type ESXi
Instances on a Device 1
Supported vCenter, ESX and ESXi 4.x, 5.x and Systems/Applications later
Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 5 minutes
To access information about the maintenance mode on your ESXi server, use a browser to access the following URL:
- 279 - N-central 10.0 Services Reference Manual
https://
Example: https://192.168.101.207/mob/?moid=ha-host&doPath=runtime
Note: Refer to the inMaintenanceMode property.
Metric Name Description
Is Maintenance Mode Identifies whether the ESXi server is in Maintenance Mode or Enabled? not.
Memory Service The Memory service monitors the following properties of the physical memory and virtual memory on a device.
l used memory,
l free memory,
l total memory, and
l memory utilization by the top five processes.
Note: If the Memory service is first being monitored by a Probe and then by an Agent, the first few scans performed by the Probe will measure total memory usage only and not memory utilization by the top five processes. When the Agent begins monitoring this service, data will be reported for memory utilization by the top five processes. This may lead to a temporary discrepancy between the results reported by the Probe and the Agent.
One instance of this service can monitor all of the detected swap files on multiple volumes. The maximum size of a swap file that is monitored by this service is 16GB.
The Memory service can be added to a monitored device in one of three different types: Local, SNMP, and WMI.
Memory Service (Local API)
Service Type Local
Instances on a 1 Device
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent
- 280 - N-central 10.0 Services Reference Manual
Scan Interval 60 minutes
Memory Service (SNMP)
Warning! If a Probe discovers a Windows device using SNMP and associates the Memory service to the device, the default values assigned for the following must be manually changed:
l Physical Memory Name - the default assigned value of Physical memory must be changed to Physical Memory as Windows is case-sensitive, and,
l Virtual Memory Name - the default assigned value of Swap Space must be changed to Virtual Memory.
If these modifications are not made to the device in N-central, the Memory service will transition to a Failed state.
Service SNMP Type
Instan 1 ces on a Device
Device Server - Generic, Workstation - Generic, Other, Switch/Router, Laptop - Windows, Server Class - Windows, and Workstation - Windows
Monito Agent, Windows Probe red By
Scan 60 minutes Interval
- 281 - N-central 10.0 Services Reference Manual
Physic The SNMP index for the physical memory to be monitored. The index values can be al obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.2.3.1.3 Memor (hrStorageDescr). You must determine which OID and index value is relevant. y Index The OID value is contained in the HOST-RESOURCES-MIB definition file.
Physic The string corresponding to the row in the hrStorageTable, which describes the type and al instance of the table for the Memory (SNMP) service. The string can be obtained by Memor performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.2.3.1.3 (hrStorageDescr). y Name
Virtual The SNMP index for the virtual memory to be monitored. The index values can be obtained Memor by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.2.3.1.3 (hrStorageDescr). y Index You must determine which OID and index value is relevant.
The OID value is contained in the HOST-RESOURCES-MIB definition file.
Virtual The string corresponding to the row in the hrStorageTable, which describes the type and Memor instance of the table for the Memory (SNMP) service. The string can be obtained by y Name performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.2.3.1.3 (hrStorageDescr).
OID/Calculation Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation Description
Physical Used Physical The percentage of physical memory used. This Memory Memory/Total Memory * percentage is compared to the thresholds. Usage (%) 100
Virtual Used Virtual Memory/Total The percentage of virtual memory used. This Memory Virtual Memory * 100 percentage is compared to the thresholds. Usage (%)
- 282 - N-central 10.0 Services Reference Manual
Memory Service (WMI)
Service Type WMI
Instances on a 1 Device
Device Class Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent, Windows Probe
Scan Interval 60 minutes
Properties Queried and Calculations Performed Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Namespace root\cimv2
WMI Class Win32_OperatingSystem
WMI Property 0 TotalVirtualMemorySize
WMI Property 1 TotalVisibleMemorySize
WMI Property 2 FreeVirtualMemory
WMI Property 3 FreePhysicalMemory
Scan- $VarTotalPhysicalMemSize - $VarFreePhysicalMemSize detail.2.Recipe
Scan- [($VarTotalPhysicalMemSize - $VarFreePhysicalMemSize) / $VarTotalPhys- detail.3.Recipe icalMemSize] * 100
Scan- $VarTotalVirtualMemSize - $VarFreeVirtualMemSize detail.6.Recipe
Scan- [($VarTotalVirtualMemSize - $VarFreeVirtualMemSize) / $VarTotalVirtualMemSize] detail.7.Recipe * 100
Memory – Juniper (ScreenOS) Service The Memory - Juniper (ScreenOS) service monitors the memory usage of a Juniper device.
Note: This service cannot use N-central’s Self-Healing feature.
- 283 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Netscreen OS 5.4 and later Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation Description
Memory Allocated 1.3.6.1.4.1.3224.16.2.1
Memory Left 1.3.6.1.4.1.3224.16.2.2
Total Memory Memory Allocated + Memory Left
Used Memory [Memory Allocated/(Memory Allocated + Memory Left)] x 100
Memory – Juniper Secure Access Service The Memory -Juniper Secure Access service monitors the memory and swap usage of a Juniper Secure Access (SA) device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported IVE OS 6.0 and later Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5
Memory Index Enter the SNMP index of the memory to be monitored (default=0). For a list of indices on the Juniper device, query it with the 1.3.6.1.4.1.12532.11 SNMP OID.
- 284 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation
Memory Utilization 1.3.6.1.4.1.12532.11
Memory Swapped 1.3.6.1.4.1.12532.24
Memory Status (Dell iDRAC) Service The Memory Status (Dell iDRAC) service monitors the status of specified memory devices on a Dell PowerEdge server using the embedded integrated Dell Remote Access Controller (iDRAC).
Service Type SNMP
Instances on a 100 Device
Supported Dell PowerEdge servers with integrated Dell Remote Access Controller (iDRAC) Systems/Applicatio ns
Device Class for Servers - Management Interface CPU (SNMP)
Monitored By Windows Agent
Scan Interval 15 minutes
SNMP Value Type or select the name of the memory device to be monitored in the format MemoryFQDD (Fully Qualified Device Descriptor). For a list of memory devices, query the device with the .1.3.6.1.4.1.674.10892.5.4.1100.50.1.26 SNMP OID.
- 285 - N-central 10.0 Services Reference Manual
Status Object Numerical OID Description Detail Descriptors
Manufactur $DeviceBrandNa 1.3.6.1.4.1.674.10892.5.4.1100.50.1. Indicates the name of e Name me 21 the manufacturer of the memory device.
Size (GB) $Size 1.3.6.1.4.1.674.10892.5.4.1100.50.1. Indicates the size (in 14 gigabytes) of the memory device. A value of zero (0) indicates that no memory is installed.
Speed $Speed 1.3.6.1.4.1.674.10892.5.4.1100.50.1. Indicates the data (1,000s of 15 transfer speed (in Nanosecon thousands of ds) nanoseconds) of the memory device. A value of zero (0) indicates that the data transfer speed is unknown.
Serial $SerialNumber 1.3.6.1.4.1.674.10892.5.4.1100.50.1. Indicates the identifying Number 23 serial number of the memory device.
Status $Status 1.3.6.1.4.1.674.10892.5.4.1100.50.1. Indicates the current 5 status of the memory device mapped as follows:
1 - other,
2 - unknown,
3 - ok,
4 - nonCritical,
5 - critical, and,
6 - nonRecoverable.
Memory Status (Fujitsu) Service The Memory Status (Fujitsu) service monitors the status, size, form, type, and whether or not RAM is approved for use in a Fujitsu device.
- 286 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 100
Supported Fujitsu workstations, laptops or servers running the Fujitsu ServerView agent. Systems/Applications
Device Class for CPU Servers - Generic or Servers - Windows (SNMP)
Monitored By Windows Agent
Memory Label Type the label of the memory to be monitored. For a list of memory labels, query the device with the .1.3.6.1.4.1.231.2.10.2.2.10.6.5.1.3 SNMP OID.
Scanning The scan interval can be configured according to either a Once a Day or Daily Interval schedule.
Object Numerical OID Descriptors
$Status 1.3.6.1.4.1.231.2.10.2.2.10.6.5.1.4
$Size 1.3.6.1.4.1.231.2.10.2.2.10.6.5.1.6
$Form 1.3.6.1.4.1.231.2.10.2.2.10.6.5.1.8
$Type 1.3.6.1.4.1.231.2.10.2.2.10.6.5.1.9
$Approved 1.3.6.1.4.1.231.2.10.2.2.10.6.5.1.12
- 287 - N-central 10.0 Services Reference Manual
Status Detail Description
Status Describes the current status of the memory that is being monitored with values mapped as follows:
Normal: 3, 8, 9, 10, 11
Warning: 7
Failed: 1, 2, 4, 5, 6
1. Unknown - Module status could not be evaluated. 2. Not Present - Module socket is empty. 3. OK - Module is available and working properly. 4. Disabled - Module was manually disabled in BIOS setup. 5. Error - Module has encountered errors but is still in use. 6. Failed - Module has failed and was disabled. 7. Prefailure Predicted - Module has encountered too many correctable errors within a certain time period and is predicted to fail in near future. 8. Hot Spare 9. Mirror 10. RAID 11. Hidden - Module socket is not available and should be hidden.
Size Specifies the current size (in Megabytes) of the memory that is being monitored.
Form Specifies the form (for example, SIMM or DIMM) of the memory that is being monitored.
Type Specifies the type (for example, SDRAM, DDRAM, DDR2, or DDR3) of the memory that is being monitored.
Is the RAM Approved Specifies whether or not the memory that is being monitored is approved for the for Use in this Device? target device.
Memory Status (HP) Service The Memory Status (HP) service monitors the status of the memory on an HP server by testing to see whether or not the Advanced Memory Protection subsystem has been engaged.
- 288 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Any HP ProLiant ML and DL 300- and 500-series servers Systems/Applications
Device Class Server - Generic, Server - Windows
Monitored By Windows Probes
Scan Interval 5 minutes
SNMP Index Type the SNMP Index to be used by this service. The default SNMP index is 0, and should not need to be changed. For a list of SNMP indices, query the HP server with the 1.3.6.1.4.1.232.6.2.14.4 SNMP OID.
Status Detail Description
Memory Status Indicates the current status of memory on the monitored device mapped as follows:
l 0 = Normal
l 1 = Failed
Memory Status Describes the current status of memory on the monitored device as one of the following: Description l Normal - This system is operating normally.
l Failed - The system does not support fault tolerant memory or the state cannot be determined by the Management Agent.
l Failed - The system is running in a degraded state because the Advanced Memory Protection subsystem has been engaged.
Memory Status (IBM) Service Memory Status (IBM) monitors the status of specified memory banks on IBM servers.
- 289 - N-central 10.0 Services Reference Manual
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type SNMP
Instances on a Device 8
Supported Any IBM-SYSTEM-MEMORY-MIB compliant device Systems/Applications
Device Class Server - Generic, Server - Windows
Monitored By Windows Probes
Scan Interval 5 minutes
Memory Bank Name The name of the memory bank to be monitored. OID: 1.3.6.1.4.1.2.6.159.1.1.120.1.1.1
OID/Calculation
Metric Description OID/Calculation Name
Error 1.3.6.1.4.1.2.6.159.1.1.120.1.1.3 Indicates if the Memory Bank is experiencing any issues. The Detected returned value is a Boolean (true/false), where, True=Failed, and False=Normal.
Memory 1.3.6.1.4.1.2.6.159.1.1.120.1.1.13 Indicates the physical location of the memory bank in the IBM Location server.
Memory (VMware) Service The Memory (VMware) service monitors the memory usage on ESXi servers.
Note: This service cannot use N-central’s Self-Healing feature.
- 290 - N-central 10.0 Services Reference Manual
Service Type ESXi
Instances on a Device 1
Supported ESX or ESXi 4.x, 5.x and Systems/Applications later
Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 5 minutes
Metric Name Description
Total Physical Memory The total amount (in GB) of memory on the device.
Used Physical Memory The amount (in GB) of memory currently in use.
Free Physical Memory The amount (in GB) of memory not currently being used.
Physical Memory Usage The amount of memory currently in use expressed as a percentage of the total memory.
Used Swap (MB) The amount (in MB) of swap memory currently in use.
Memory Status (VMware) Service Memory Status (VMware) monitors the status of specified memory modules on ESXi servers.
Note: This service cannot use N-central’s Self-Healing feature.
Note: If your ESX/ESXi server is operating on either Dell or HP hardware, it is strongly recommended that you install the Dell or HP Offline Bundle before the Windows Probe discovers the ESX/ESXi server. For instructions on installing the Dell or HP Offline Bundle, refer to the following articles in the N-central online knowledge base:
l KBA10019: Installing the HP Offline Bundle on ESX/ESXi Servers
l KBA10020: Installing the Dell Offline Bundle on ESX/ESXi Servers
- 291 - N-central 10.0 Services Reference Manual
Service Type ESXi
Instances on a Device 1
Supported ESX or ESXi 4.x, 5.x and Systems/Applications later
Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 5 minutes
Metric Name Description
All Memory is Indicates whether the specified memory modules on an ESXi server are in a Functioning Properly Normal or Failed state.
Memory Status Displays failure messages related to the specified memory modules. Description
NetBotz Airflow Service The NetBotz Airflow service monitors the airflow reading and airflow sensor status of the specified temperature sensor.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 68
Supported Any NetBotz device that has an attached airflow sensor Systems/Applications
Device Class Other
- 292 - N-central 10.0 Services Reference Manual
Monitored By Windows Probe
Scan Interval 5 minutes
Airflow Sensor To find out the name of the airflow sensors attached to the NetBotz device, query the NetBotz device with the 1.3.6.1.4.1.5528.100.4.1.5.1.1 SNMP OID.The default name is nbHawkEnc_0_AFLW.
OID/Calculation
Metric Description OID/Calculation Name
Airflow 1.3.6.1.4.1.5528.100.4.1.5.1.8
Sensor Status 1.3.6.1.4.1.5528.100.4.1.5.1.3 This status can be either Connected or Disconnected. The service will report a Failed Status if the sensor reports Dis- connected.
Sensor Status 1.3.6.1.4.1.5528.100.4.1.5.1.3 Description
NetBotz Audio Service The NetBotz Audio service monitors the audio reading and sensor status of the specified audio sensor.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 68
Supported Any NetBotz device that has an attached audio sensor Systems/Applications
Device Class Other
Monitored By Windows Probe
Scan Interval 5 minutes
Audio Sensor To find out the name of the audio sensors attached to the NetBotz device, query the NetBotz device with the 1.3.6.1.4.1.5528.100.4.1.4.1.1 SNMP OID. The default name is nbHawkEnc_0_AUDI.
- 293 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Description OID/Calculation Name
Audio 1.3.6.1.4.1.5528.100.4.1.4.1.2
Sensor Status 1.3.6.1.4.1.5528.100.4.1.4.1.3 This status can be either Connected or Disconnected. The service will report a Failed Status if the sensor reports Dis- connected.
Sensor Status 1.3.6.1.4.1.5528.100.4.1.4.1.3 Description
NetBotz Dewpoint Service The NetBotz Dewpoint service monitors the dew point reading (in degrees Celsius by default) and sensor status of the specified dewpoint sensor.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 68
Supported Any NetBotz device that has an attached dewpoint sensor Systems/Applications
Device Class Other
Monitored By Windows Probe
Scan Interval 5 minutes
Dewpoint Sensor To find out the name of the dewpoint sensors attached to the NetBotz device, query the NetBotz device with the 1.3.6.1.4.1.5528.100.4.1.3.1.1 SNMP OID. The default name is nbHawkEnc_0_DEW.
- 294 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Description OID/Calculation Name
Dewpoint 1.3.6.1.4.1.5528.100.4.1.3.1.8 The dew point temperature as measured in degrees Celsius.
Dewpoint 1.3.6.1.4.1.5528.100.4.1.3.1.9 The dew point temperature as measured in degrees Fahren- heit.
Sensor Status 1.3.6.1.4.1.5528.100.4.1.3.1.3 This status can be either Connected or Disconnected. The service will report a Failed Status if the sensor reports Dis- connected.
Sensor Status 1.3.6.1.4.1.5528.100.4.1.3.1.3 Description
NetBotz Door Switch Service The NetBotz Door Switch service monitors whether or not the door switch is open or closed, and the status of the door sensor.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 68
Supported Any NetBotz device that has an attached door switch Systems/Applications
Device Class Other
Monitored By Windows Probe
Scan Interval 5 minutes
Door Switch To find out the name of the door switches attached to the NetBotz device, query the NetBotz device with the .1.3.6.1.4.1.5528.100.4.2.2.1.1 SNMP OID. Default name is DOOR.
- 295 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Description OID/Calculation Name
Door 1.3.6.1.4.1.5528.100.4.2.2.1.2 An integer value representing whether or not the door switch Switch is connected (the door is closed) or disconnected (the door is Status open). The service will transition to a Failed state if the door switch reports a disconnected status.
Door 1.3.6.1.4.1.5528.100.4.2.2.1.2 Reports back either Connected or Disconnected. Switch Status Description
Sensor 1.3.6.1.4.1.5528.100.4.2.2.1.3 The health status of the sensor. There are 6 possible statuses: Status 0: Normal 1: Info 2: Warning 3: Error 4:Critical 5: Failure
This metric is mapped as follows: Normal: 0 Warning: 1,2 Failed: 3,4,5
Sensor 1.3.6.1.4.1.5528.100.4.2.2.1.3 A description of the health status of the sensor. Status Description
NetBotz Humidity Service The NetBotz Humidity service monitors the the humidity reading and sensor status of the specified temperature sensor..
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 68
Supported Any NetBotz device that has an attached humidity sensor Systems/Applications
Device Class Windows Probe
- 296 - N-central 10.0 Services Reference Manual
Monitored By 5 minutes
Scan Interval 5 minutes
Humidity Sensor To find out the name of the humidity sensors attached to the NetBotz device, query the NetBotz device with the 1.3.6.1.4.1.5528.100.4.1.2.1.1 SNMP OID. The default name is nbHawkEnc_0_HUMI.
OID/Calculation
Metric Description OID/Calculation Name
Humidity 1.3.6.1.4.1.5528.100.4.1.2.1.8 The humidity reading reported by the sensor.
Sensor 1.3.6.1.4.1.5528.100.4.1.2.1.3 An integer value representing whether or not the humidity Status sensor is connected or disconnected. The service will transition to a Failed state if the door switch reports a disconnected status.
Sensor 1.3.6.1.4.1.5528.100.4.1.2.1.3 A description of the sensor’s status. Status Description
NetBotz Temperature Service The NetBotz Temperature service monitors the status and reported temperature (in Fahrenheit and Celsius) of the specified temperature sensor.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 68
Supported Any NetBotz device that has an attached temperature sensor Systems/Applications
Device Class Other
Monitored By Windows Probe
Scan Interval 5 minutes
Temperature Sensor To find out the name of the temperature sensors attached to the NetBotz device, query the NetBotz device with the 1.3.6.1.4.1.5528.100.4.1.1.1.1 SNMP OID. The default name is nbHawkEnc_0_TEMP.
- 297 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Description OID/Calculation Name
Temperature 1.3.6.1.4.1.5528.100.4.1.1.1.8 The temperature reading in Celsius. (\u00baC)
Temperature 1.3.6.1.4.1.5528.100.4.1.1.1.9 The temperature reading in Fahrenheit. (\u00baF)
Sensor 1.3.6.1.4.1.5528.100.4.1.1.1.3 An integer value representing whether or not the temperature Status sensor is connected or disconnected. The service will trans- ition to a Failed state if the door switch reports a disconnected status.
Sensor 1.3.6.1.4.1.5528.100.4.1.1.1.3 A description of the sensor’s status. Status Description
Network Card (Dell iDRAC) Service The Network Card (Dell iDRAC) service monitors the status of specified Network Interface Controllers (NICs) on a Dell PowerEdge server using the embedded integrated Dell Remote Access Controller (iDRAC).
Service Type SNMP
Instances on a 100 Device
Supported Dell PowerEdge servers with integrated Dell Remote Access Controller (iDRAC) Systems/Applicatio ns
Device Class for Servers - Management Interface CPU (SNMP)
Monitored By Windows Agent
Scan Interval 15 minutes
SNMP Value Type or select the name of the network device to be monitored in the format NetworkDeviceFQDD (Fully Qualified Device Descriptor). For a list of network devices, query the device with the .1.3.6.1.4.1.674.10892.5.4.1100.90.1.30 SNMP OID.
- 298 - N-central 10.0 Services Reference Manual
Status Object Numerical OID Description Detail Descriptors
Product $Name 1.3.6.1.4.1.674.10892.5.4.1100.90.1. Indicates the product name Name 6 of the network device.
MAC $MacAddress 1.3.6.1.4.1.674.10892.5.4.1100.90.1. Indicates the current MAC Address 15 address of the network device.
Connecti $ConnectionStat 1.3.6.1.4.1.674.10892.5.4.1100.90.1. Indicates the current on us 4 connection status of the Status network device mapped as follows:
1 - connected
2 - disconnected
3 - driverBad
4 - driverDisabled
10 - hardwareInitalizing
11 - hardwareResetting
12 - hardwareClosing
13 - hardwareNotReady
Status $Status 1.3.6.1.4.1.674.10892.5.4.1100.90.1. Indicates the current status 3 of the network device mapped as follows:
1 - other,
2 - unknown,
3 - ok,
4 - nonCritical,
5 - critical, and,
6 - nonRecoverable.
- 299 - N-central 10.0 Services Reference Manual
NIC Status (VMware) Service The NIC Status (VMware) service monitors Network Interface Controllers (NICs) on ESXi servers.
Note: If your ESX/ESXi server is operating on either Dell or HP hardware, it is strongly recommended that you install the Dell or HP Offline Bundle before the Windows Probe discovers the ESX/ESXi server. For instructions on installing the Dell or HP Offline Bundle, refer to the following articles in the N-central online knowledge base:
l KBA10019: Installing the HP Offline Bundle on ESX/ESXi Servers
l KBA10020: Installing the Dell Offline Bundle on ESX/ESXi Servers
Service Type ESXi
Instances on a Device 100
Supported ESX or ESXi 4.x, 5.x and later Systems/Applications Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 5 minutes
NIC ID The unique identifier of the NIC being monitored.
Note: This service cannot use N-central’s Self-Healing feature.
To access information about the NICs on your ESXi server, use a browser to access the following URL:
https://
Example: https://192.168.101.207/mob/?moid=ha-host&doPath=config.network
- 300 - N-central 10.0 Services Reference Manual
Metric Name Description
Enabled State Indicates whether the NIC has been enabled or disabled.
Enabled State Description n/a
Is the NIC Using Full-Duplex? Indicates whether the NIC is in full-duplex mode or not.
NIC Speed (Mbps) The total data transfer rate, in megabytes/second, of the NIC.
Data Receive Rate The transfer rate, in bytes/second, that the NIC receives data.
Data Transmit Rate The transfer rate, in bytes/second, that the NIC transmits data.
Dropped Packets (Received) The number of data packets lost during the reception of data by the NIC.
Dropped Packets (Transmitted) The number of data packets lost during the transmission of data by the NIC.
NNTP Service The Network News Transfer Protocol (NNTP) test checks the status of the NNTP process on the network device. NNTP is a request-reply protocol that is similar in style to the Simple Mail Transfer Protocol (SMTP) or FTP. It provides a network news transport service and is the standard for the Internet exchange of Usenet messages.
N-central can determine the up or down status of the NNTP service. The NNTP service does not use the Warning state.
N-central averages the availability of the NNTP service over the scan interval. It compares the availability of the NNTP service to the threshold to determine the status.
Service TCP Type
Instances 1 on a Device
Device Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Class Windows, Server - Windows, and Workstation - Windows
Monitored Windows probe, N-central Server By
- 301 - N-central 10.0 Services Reference Manual
Scan 5 minutes Interval
Time Out 30 seconds Value
Port 119 Number
Validation The response you expect to receive from the port that is being queried. If the validation string that String you specify is not returned by the port being queried, the service will transition to a Failed state. The default validation string is 200.
Status Details
Status Description Detail
NNTP N-central determines whether the NNTP service is up or down. The NNTP service does not use the Service Warning state. N-central averages the availability of the NNTP service over the scan interval and Availability compares the availability of the NNTP service to the threshold to determine the status.
Round The time (in milliseconds) for a request to be sent and received. Trip Time (ms)
DNS The threshold that determines whether the device name can be resolved. Resolution If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings. If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
Overall VPN Status (Cisco) Service The Overall VPN Status (Cisco) service monitors a number of different properties of VPN tunnels to Cisco devices.
Service Type SNMP
Instances on a Device 1
Supported Any Cisco device that provides VPN capabilities. Systems/Applications
Device Class Switch/Router
- 302 - N-central 10.0 Services Reference Manual
Monitored By Windows Probe
Scan Interval 5 minutes
SNMP Index The SNMP index of the status of the VPN tunnel.
Object Descriptors Numerical OID
$Active Tunnels 1.3.6.1.4.1.9.9.171.1.2.1.1
$GlobalLocalTunnelFails 1.3.6.1.4.1.9.9.171.1.2.1.20
$GlobalRemoteTunnelFails 1.3.6.1.4.1.9.9.171.1.2.1.21
$SysCapFail 1.3.6.1.4.1.9.9.171.1.2.1.22
$AuthFail 1.3.6.1.4.1.9.9.171.1.2.1.23
$DecFail 1.3.6.1.4.1.9.9.171.1.2.1.24
$HashFail 1.3.6.1.4.1.9.9.171.1.2.1.25
Status Detail Description
Locally Initiated Tunnel The number of VPN tunnels initiated by the monitored device that failed. Failures
Remotely Initiated Tunnel The number of VPN tunnels that connected to the monitored device that failed. Failures
System Capacity Failures The number of VPN tunnels that failed due to the capacity of the monitored device being exceeded.
Authentication Failures The number of VPN tunnels that failed due to problems with authentication.
Decryption Failures The number of VPN tunnels that failed due to problems with decrypting the data.
Hash Failures The number of VPN tunnels that failed due to problems with encrypting the data using hash values.
Paper Supply Level Service The Paper Supply Level service monitors the amount of paper available to a printer as a percentage of the total capacity of the printer. The printers monitored by this service include any printer that supports the Printer-MIB.
Note: This service cannot use N-central’s Self-Healing feature.
- 303 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 6
Supported Any printer that supports the Printer-MIB. Systems/Applications
Device Class Printer
Monitored By Windows Probe
Scan Interval 15 minutes
Printer Input The SNMP index for the Printer Input Tray, which is determined by performing an SNMP Description Index walk on the prtInputDescription OID (.1.3.6.1.2.1.43.8.2.1.18.).
Printer Input The SNMP description for the Printer Input Tray, which is determined by performing an Description Value SNMP walk on the prtInputDescription OID (.1.3.6.1.2.1.43.8.2.1.18).
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Description OID/Calculation Name
Description 1.3.6.1.2.1.43.8.2.1.18 A description of the paper tray.
Max Capacity 1.3.6.1.2.1.43.8.2.1.9 The maximum capacity of the paper tray.
Level 1.3.6.1.2.1.43.8.2.1.10 The current capacity of the paper tray.
Paper Level (Level / Max Capacity) x 100 How much of the paper tray's capacity is being % used.
Patch Status Service The Patch Status service is automatically added to Windows devices and monitors them to determine whether or not required software updates and patches have been installed.
Note: This service is only available for Windows devices.
- 304 - N-central 10.0 Services Reference Manual
Instances on 1 a Device
Device Class Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows agent
Scan Interval The default interval is five (5) minutes.
Time To Stale The time (in minutes) that N-central waits to receive data about the service. If no data is received within the specified time period, the service will transition to a Stale status. The default value is 4320 minutes (72 hours or 3 days).
Threshold for The duration (in days) that a patch can be approved but not installed before the patch is Monitoring added to the Missing Patches That Were Approved Over xx Days Ago metric. The old patches default value is 60 days. (days)
Include The types of patches to be reported by the service. Patches in the following categories
- 305 - N-central 10.0 Services Reference Manual
Status Details
Status Description Detail
OVERVIEW TAB
Patch A table providing the total number of software patches listed by category that are Approved but Details Not Installed or Not Approved.
Patch Additional detail provided for the installation of software patches including: Summ
ary l Patches installed with errors - Identifies the total number of patches with installation errors.
l Next Patch Scan Schedule - Indicates the date and time when the next scan of the status of software patch installations will take place.
l Next Installation Schedule - Indicates the date and time when the next installation of software patches will take place. Note that for versions of N-central earlier than N-central 9.5, Patch installation is in progress may be displayed when software patches are being downloaded and are not actually in the process of being installed.
l Patch Download Source - Indicates the source from which the device is synchronizing software patches.
l Reboot Required - Indicates whether the device must be restarted in order for software patch installation to be completed. If this value is True, the service will transition to a Warning state.
APPROVED PATCHES TAB
- 306 - N-central 10.0 Services Reference Manual
Status Description Detail
Missin A table providing the total number of missing software patches categorized as: g
Patche l Missing Patches - Identifies the total number of missing patches. s Details l Missing Patches Older Than 60 Days - Identifies the total number of patches that have been missing for more than 60 days.
Missin Lists the total number of missing patches by the following categories: g l Security Updates Patche l Critical Updates s by l Service Packs Catego l Third Party Updates ry l Update Rollups
l Feature Packs
l Updates
l Software Driver Updates
Click View to display the missing patches for each category. Once the list of missing patches is displayed, click Hide to conceal the list of missing patches.
NOT APPROVED PATCHES TAB
Not Lists the total number of software patches that have not been approved by the following Approv categories: ed l Security Updates Patche l Critical Updates s by l Service Packs Catego l Third Party Updates ry l Update Rollups
l Feature Packs
l Updates
l Software Driver Updates
l Definition File Updates
l Tools Updates
l Unknown Updates
Physical Drive (Adaptec) Service The Physical Drive (Adaptec) service monitors the S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) status of the specified physical drive.
Note: Adaptec Storage Manager or IBM ServeRAID Manager must be installed. For a complete list of supported models, please refer to:
l http://www.adaptec.com/en-US/products/asm/, or,
- 307 - N-central 10.0 Services Reference Manual
l https://www-304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR- 61707&brandind=5000008
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type SNMP
Instances on a Device 10
Supported Any device using an Adaptec HostRAID card or an IBM ServeRAID card Systems/Applications
Device Class Server - Generic and Server - Windows
Monitored By Windows Probes
Scan Interval 5 minutes
Physical Drive Iden- The SNMP index (unique identifier) of the physical drive to be monitored. The index can tifier be obtained by querying the device with the .1.3.6.1.4.1.795.14.1.410.1.1.1 SNMP OID.
- 308 - N-central 10.0 Services Reference Manual
OID/Calculations
Metric Name OID/Calculation Description
S.M.A.R.T. .1.3.6.1.4.1.795.14.1.410.1.1.8 An integer value that reports the S.M.A.R.T. status of Status the physical drive. The following thresholds are used: Normal: 2, 4 Warning: 1 Failed: 3, 5
The meaning of the drive status: 1: Unknown 2: Unsupported 3: Disable 4: Okay 5: Error Predicted
S.M.A.R.T. .1.3.6.1.4.1.795.14.1.410.1.1.8 Describes the status of the physical drive. Status Description
Physical Drive .1.3.6.1.4.1.795.14.1.410.1.1.2 A text description of the physical drive being Description monitored.
Physical Drive .1.3.6.1.4.1.795.14.1.410.1.1.3 The storage capacity of the physical drive. Size
Physical Drive (Dell) Service The Physical Drive (Dell) service monitors the overall status of physical drives attached to Dell servers running Dell OpenManage Server Administrator software.
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
- 309 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a 50 Device
Supported Dell servers running Dell OpenManage Server Administrator software Systems/Applicatio ns
Device Class Server - Generic and Server - Windows
Monitored By Windows probe
Scan Interval 5 minutes
Physical Drive Index The SNMP index of the physical drive. The index can be obtained by querying the device with the 1.3.6.1.4.1.674.10893.1.20.130.4.1.2 SNMP OID.
- 310 - N-central 10.0 Services Reference Manual
OID/Calculation
- 311 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Drive State 1.3.6.1.4.1.674.10893.1.20.130.4.1. An integer value that represents the states Code 4 of the drive. This metric is mapped as follows:
Normal: 3, 35, 40
Warning: 1, 15, 25, 26, 28
Failed: 0, 2, 4, 6, 7, 11, 24, 34, 39, 41, 53
The meaning of the drive state code statuses:
0: Unknown
1: Ready - Available for use, but no RAID configuration has been assigned.
2: Failed - Not operational.
3: Online - Operational. RAID configuration has been assigned.
4: Offline - The drive is not available to the RAID controller.
6: Degraded - Refers to a fault-tolerant array/virtual disk that has a failed disk.
7: Recovering - Refers to state of recovering from bad blocks on disks.
11: Removed - Indicates that array disk has been removed.
15: Resynching - Indicates one of the following types of disk operations: Transform Type, Reconfiguration, and Check Consistency.
24: Rebuild
25: No Media - CD-ROM or removable disk has no media.
26: Formatting - In the process of formatting.
28: Diagnostics - Diagnostics are running.
34: Predictive failure
35: Initializing:Applies only to virtual disks on PERC, PERC 2/SC, and PERC 2/DC controllers. - 312 - 39: Foreign
40: Clear
41: Unsupported
53: Incompatible N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Make 1.3.6.1.4.1.674.10893.1.20.130.4.1. The manufacturer of the physical drive. (DriveVendor) 3
Model The model name and/or number of the (DriveProductI 1.3.6.1.4.1.674.10893.1.20.130.4.1. physical drive. D) 6
Drive Name 1.3.6.1.4.1.674.10893.1.20.130.4.1. Identifies the name of the array disk as 2 represented in Storage Management.
Drive Spare 1.3.6.1.4.1.674.10893.1.20.130.4.1. Identifies the status of the array disk as a State 22 spare. Possible states:
1: Disk is a member of a virtual disk
2: Disk is a member of a disk group
3: Disk is a global hot spare
4: Disk is a dedicated hot spare
5: Not a spare
99: Not applicable
Drive Status 1.3.6.1.4.1.674.10893.1.20.130.4.1. Severity of the array disk state. This is the 23 combined status of the array disk and its components. Possible values:
1: Other
2: Unknown
3: OK
4: Non-critical
5: Critical
6: Non-recoverable
Physical Drive (Dell iDRAC) Service The Physical Drive (Dell iDRAC) service monitors various elements related to the status of a physical drive in a Dell PowerEdge server using the embedded integrated Dell Remote Access Controller (iDRAC).
- 313 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a 100 Device
Supported Dell PowerEdge servers with integrated Dell Remote Access Controller (iDRAC) Systems/Applicatio ns
Device Class for Servers - Management Interface CPU (SNMP)
Monitored By Windows Agent
Scan Interval 15 minutes
SNMP Index Type or select the name of the drive to be monitored. For a list of drives, query the device with the .1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1.54 SNMP OID.
- 314 - N-central 10.0 Services Reference Manual
Status Object Numerical OID Description Detail Descriptors
Disk $Name 1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1. Indicates the physical disk's Name 2 name as represented in Storage Management.
- 315 - N-central 10.0 Services Reference Manual
Status Object Numerical OID Description Detail Descriptors
State $State 1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1. The current state of the 4 physical disk being monitored mapped as follows:
l 1: Unknown - The current state could not be determined.
l 2: Ready - The phys- ical disk is available for use but no RAID con- figuration has been assigned.
l 3: Online - A RAID configuration has been assigned to the phys- ical disk.
l 4: Foreign - The phys- ical disk has been moved from another controller and contains all or some portion of a virtual disk.
l 5: Offline - The phys- ical disk is not avail- able to the RAID controller.
l 6: Blocked - The physical disk is cur- rently blocked by con- troller.
l 7: Failed - The phys- ical disk is not oper- ational.
l 8: Non-RAID - The physical disk is not a RAID capable disk.
l 9: Removed - The physical disk has been removed.
- 316 - N-central 10.0 Services Reference Manual
Status Object Numerical OID Description Detail Descriptors
Serial $SerialNo 1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1. Indicates the physical disk's Number 7 unique identification number provided by the manufacturer.
Disk $DiskCapait 1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1. Indicates the size of the Capacity y 11 physical disk (in megabytes).
Used $UsedSpac 1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1. Indicates the amount of space Space e 17 (in gigabytes) currently being (GB) used on the physical disk.
Used n/a n/a Calculated using the formula: Space $UsedSpace $DiskCapaity / Percenta 100.0 * ge (%)
- 317 - N-central 10.0 Services Reference Manual
Status Object Numerical OID Description Detail Descriptors
Free $FreeSpace 1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1. Indicates the amount of space Space 19 (in megabytes) currently (MB) available on the physical disk.
Spare $SpareStat 1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1. Indicates the status of the State e 22 array disk as a spare mapped as follows:
l 1: notASpare - Phys- ical disk is not a spare.
l 2: ded- icatedHotSpare - Physical disk is a ded- icated hot spare.
l 3: globalHotSpare - Physical disk is a global hot spare.
Display $DisplayNa 1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1. Indicates the physical disk's Name me 55 friendly FQDD as represented in Storage Management.
Smart $SmartAlert 1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1. Indicates whether or not the Alert 31 physical disk has received a predictive failure alert.
Physical Drive (EqualLogic) Service The Physical Drive (Dell) service monitors the overall status of a physical drive attached to a Model PS6100 Dell EqualLogic SAN running v6.0.2 firmware.
Service Type SNMP
Instances on a Device 100
Supported Sys- Model PS6100 Dell EqualLogic SANs running v6.0.2 firmware tems/Applications
Device Class Server - Generic and Server - Windows
- 318 - N-central 10.0 Services Reference Manual
Monitored By Windows Probe
Scan Interval 5 minutes
Drive Identifier Type the name of the physical drive to be monitored. For a list of the physical drives, query the EqualLogic SAN with the 1.3.6.1.4.1.12740.3.1.1.1.1 SNMP OID.
- 319 - N-central 10.0 Services Reference Manual
OID/Calculation
- 320 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Drive Status 1.3.6.1.4.1.12740.3.1.1. Describes the current status of the physical drive. The Description 1.8 possible values are:
1 On-line The disk is being used in the RAID set.
2 Spare The disk is not currently being used by RAID con- figuration but may be used when status of a currently on-line disk changes.
3 Failed Either the disk is faulty or when there is no power.
4 Offline The disk doesn't fall into any of these other cat- egories.
5 Alt-sig
6 Too-small The drive is too small to be used. The drive cannot be converted to spare.
7 History-of- The drive has a history of failures failures. The drive can be converted to spare.
8 Unsupported- The drive label is from a version later release. The drive can be converted to spare.
9 Unhealthy The drive is unhealthy.
10 Replacement The drive is a replacement drive.
11 Encrypted The drive is encrypted and cannot be decrypted.
12 NotApproved The drive is not DELL approved.
13 Preempt- The drive is off-line due to failed excessive errors.
- 321 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Disk Serial 1.3.6.1.4.1.12740.3.1.1. The serial number of the physical drive. Number 1.5
Disk Model 1.3.6.1.4.1.12740.3.1.1. The model name and/or number of the physical drive. Number 1.3
Disk Model 1.3.6.1.4.1.12740.3.1.1. The revision number of the physical drive's firmware. Revision 1.4 Number
Disk Error 1.3.6.1.4.1.12740.3.1.1. Specifies the number of disk errors that have taken place Count 1.9 since the physical drive was last powered on.
Disk Capacity 1.3.6.1.4.1.12740.3.1.1. Specifies the size of the physical drive (measured in (MB) 1.6 megabytes).
Physical Drive (Fujitsu) Service The Physical Drive (Fujitsu) service monitors various elements related to the status of a Physical Drive in a Fujitsu device.
Service Type SNMP
Instances on a Device 100
Supported Fujitsu servers running the Fujitsu ServerView agent. Systems/Applications
Device Class for CPU Servers - Generic or Servers - Windows (SNMP)
Monitored By Windows Agent
Physical Drive Type the name of the physical drive to be monitored. For a list of physical drives, query the device with the .1.3.6.1.4.1.231.2.49.1.5.2.1.24 SNMP OID.
Scanning The scan interval can be configured according to either a Once a Day or Daily Interval schedule.
- 322 - N-central 10.0 Services Reference Manual
Object Descriptors Numerical OID
$Status 1.3.6.1.4.1.231.2.49.1.5.2.1.15
$SMARTStatus 1.3.6.1.4.1.231.2.49.1.5.2.1.14
$BadBlocks 1.3.6.1.4.1.231.2.49.1.5.2.1.13
$DeviceErrors 1.3.6.1.4.1.231.2.49.1.5.2.1.12
$PowerStatus 1.3.6.1.4.1.231.2.49.1.5.2.1.25
$Vendor 1.3.6.1.4.1.231.2.49.1.5.2.1.6
$Model 1.3.6.1.4.1.231.2.49.1.5.2.1.5
$SerialNumber 1.3.6.1.4.1.231.2.49.1.5.2.1.17
$Capacity 1.3.6.1.4.1.231.2.49.1.5.2.1.7
$DiskConnectionInterface 1.3.6.1.4.1.231.2.49.1.5.2.1.11
$FirmwareVersion 1.3.6.1.4.1.231.2.49.1.5.2.1.16
$MaxTransferRate 1.3.6.1.4.1.231.2.49.1.5.2.1.8
- 323 - N-central 10.0 Services Reference Manual
Status Detail Description
Status Describes the current status of the physical drive that is being monitored with values mapped as follows:
Normal: 3, 4
Warning: 6, 7, 8, 11
Failed: 1, 2, 5, 9, 10, 12
1. Unknown 2. No Disk 3. Online 4. Ready 5. Failed 6. Rebuilding 7. Global Hot Spare 8. Dedicated Hot Spare 9. Offline 10. Failed Unconfigured 11. Formatting 12. Dead
S.M.A.R.T. Describes the current S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) Status status of the physical drive that is being monitored with values mapped as follows:
1. OK 2. Failure Predicted 3. S.M.A.R.T. Not Available 4. S.M.A.R.T. Monitoring Disabled
Bad Blocks Indicates the number of bad blocks on the physical drive that is being monitored that cannot be reliably used for storing and retrieving data.
Read/Write/S Indicates the total combined number of read, write, and seek errors on the physical drive eek Errors that is being monitored.
Power Status Describes the current status of the power supply for the physical drive that is being monitored with values mapped as follows:
1. Device is Active 2. Device is Powered Down 3. Device Has Changed its Power Status
Manufacturer The manufacturer of the physical drive that is being monitored.
- 324 - N-central 10.0 Services Reference Manual
Status Detail Description
Model The model name of the physical drive that is being monitored.
Serial Number The serial number of the physical drive that is being monitored.
Capacity The total capacity of the physical drive (measured in Gigabytes) that is being monitored.
Disk Interface The type of interface of the physical drive that is being monitored (for example, IDE, SCSI, or SAS).
Firmware The version number of the firmware that is running on the physical drive that is being Version monitored.
Maximum Disk The maximum speed (measured in bytes per second) of data transfer of the physical drive Transfer Rate that is being monitored.
Physical Drive (HP) Service The Physical Drive (HP) service monitors the overall status of physical drives attached to HP servers running HP’s Insight Manager software.
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
- 325 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 50
Supported HP servers running HP’s Insight Manager software Systems/Applications
Device Class Server - Generic and Server - Windows
Monitored By Windows probe
Scan Interval 5 minutes
Physical Drive (HP) The unique identifier of the physical drive. This can be obtained by querying the device with the 1.3.6.1.4.1.232.3.2.5.1.1.2 SNMP OID.
OID/Calculation
Metric Name OID/Calculation Description
Physical Drive 1.3.6.1.4.1.232.3.2.5.1.1.6 The status is mapped as follows: State Normal: 2 Failed: 1, 3, 4
The meaning of the physical drive status: 1: The HP Insight Manager Agent doesn't recognize the drive; you may need to upgrade your HP Insight Manager agent and/or driver software 2: The drive is functioning properly 3: The drive is no longer operating and should be replaced 4: The drive has a predictive failure error and should be replaced
Physical Drive 1.3.6.1.4.1.232.3.2.5.1.1.6 Describes the status of the physical drive. State Description
Model 1.3.6.1.4.1.232.3.2.5.1.1.3 The model name and/or number of the physical drive.
Serial Number 1.3.6.1.4.1.232.3.2.5.1.1.51 The serial number of the physical drive.
Drive Bay 1.3.6.1.4.1.232.3.2.5.1.1.5 The bay in which the physical drive is currently installed.
Physical Drive (Intel) Service The Physical Drive (Intel) service monitors the status of the physical drive attached to a supported Intel® RAID controller.
- 326 - N-central 10.0 Services Reference Manual
The service requires a Drive Identifier. The default configuration for the service identifies the logical drive as 0 but this may not be the correct identifier for all devices. To see the list of available logical drive identifiers, query the device with the 1.3.6.1.4.1.3582.4.1.4.2.1.2.1.1 SNMP OID.
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type SNMP
Instances on a Device 16
Supported Intel(R) RAID controllers SRCSAS18E, SRCSAS144E, SROMBSAS18E, SRCSASJV, Systems/Applications SRCSASRB and SRCSATAWB with Intel® RAID WEB Console Utility 2.34-00
Device Class Server - Generic and Server - Windows
Monitored By Agent
Scan Interval 5 minutes
Drive Identifier Specify the SNMP identifier for the drive. The identifier can be found by querying the device with the 1.3.6.1.4.1.3582.4.1.4.2.1.2.1.1 SNMP OID.
- 327 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Physical Drive State 1.3.6.1.4.1.3582.4.1.4.2.1.2.1.10 The status of the physical drive is mapped as follows: Normal: 0,24 Warning: 2 Failed: 1,16,17,20
The meaning of the status: 0: Unconfigured - Good 1: Unconfigured - Bad 2: Hot Spare 16: Offline 17: Failed 20: Rebuild 24: Online
Physical Drive State 1.3.6.1.4.1.3582.4.1.4.2.1.2.1.10 Describes the status of the physical drive as Description one of: Unconfigured - Good Unconfigured - Bad Hot Spare Offline Failed Rebuild Online
Vendor 1.3.6.1.4.1.3582.4.1.4.2.1.2.1.24 The manufacturer of the physical drive.
Model 1.3.6.1.4.1.3582.4.1.4.2.1.2.1.25 The model name and/or number of the physical drive.
Capacity 1.3.6.1.4.1.3582.4.1.4.2.1.2.1.15 The total capacity of the physical drive measured in MB.
Physical Drive (VMware) Service The Physical Drive (VMware) service monitors the overall status of a physical drive on an ESXi server.
Note: If your ESX/ESXi server is operating on either Dell or HP hardware, it is strongly recommended that you install the Dell or HP Offline Bundle before the Windows Probe discovers the ESX/ESXi
- 328 - N-central 10.0 Services Reference Manual
server. For instructions on installing the Dell or HP Offline Bundle, refer to the following articles in the N-central online knowledge base:
l KBA10019: Installing the HP Offline Bundle on ESX/ESXi Servers
l KBA10020: Installing the Dell Offline Bundle on ESX/ESXi Servers
Service Type ESXi
Instances on a Device 1
Supported ESX or ESXi 4.x, 5.x and later Systems/Applications Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 5 minutes
Physical Drive ID The unique identifier of the physical drive being monitored.
Note: This service cannot use N-central’s Self-Healing feature.
To access information about the physical drives on your ESXi server, use a browser to access the following URL:
https://
Example: https://192.168.101.207/mob/?moid=ha- host&doPath=runtime.healthSystemRuntime.hardwareStatusInfo.storageStatusInfo
- 329 - N-central 10.0 Services Reference Manual
Metric Name Description
State The physical drive status is mapped as follows:
Normal: 0
Warning: 1
Failed: 2
State Description Describes the status of the physical drive:
l Critical Failure
l Degraded
l Major Failure
l Minor Failure
l Non-Recoverable Error
l OK
l Unknown
Enabled State Indicates whether the physical drive has been enabled or disabled.
Enabled State n/a Description
POP Service N-centralcan monitor a network device for the presence of a Post Office Protocol, version 3 (POP 3) mail server that is available to the network. POP 3 is a protocol designed for user-to-mailbox access. It is used on the Internet to retrieve email from a mail server.
N-central can determine the up or down status of the POP service. The POP service does not use the Warning state. N-central averages the availability of the POP service over the scan interval. It compares the availability of the POP service to the threshold to determine the status.
- 330 - N-central 10.0 Services Reference Manual
Service TCP Type
Instances 1 on a Device
Device Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Class Windows, Server - Windows, and Workstation - Windows
Monitored Windows probe, Central Server By
Scan 5 minutes Interval
Timeout The time (in seconds) that the N-central server waits before considering the test a failure. The Value default is 30 seconds.
Port 110 Number
Validation The response you expect to receive from the port that is being queried. If the validation string that String you specify is not returned by the port being queried, the service will transition to a Failed state. The default validation string is +OK.
Status Details
Status Description Detail
POP N-central determines whether the POP service is up or down. The POP service does not use the Service Warning state. N-central averages the availability of the POP service over the scan interval and Availability compares the availability of the POP service to the threshold to determine the status.
Round The time (in milliseconds) for a request to be sent and received. Trip Time (ms)
DNS The threshold that determines whether the device name can be resolved. Resolution If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings. If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
Power Consumption (VMware) Service The Power Consumption (VMware) service monitors the overall power consumption of ESXi servers.
- 331 - N-central 10.0 Services Reference Manual
If the ESXi host does not provide any power consumption data, this service will not display the Power Usage metric.
Note: If your ESX/ESXi server is operating on either Dell or HP hardware, it is strongly recommended that you install the Dell or HP Offline Bundle before the Windows Probe discovers the ESX/ESXi server. For instructions on installing the Dell or HP Offline Bundle, refer to the following articles in the N-central online knowledge base:
l KBA10019: Installing the HP Offline Bundle on ESX/ESXi Servers
l KBA10020: Installing the Dell Offline Bundle on ESX/ESXi Servers
Service Type ESXi
Instances on a Device 1
Supported ESX or ESXi 4.x, 5.x and Systems/Applications later
Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 5 minutes
Note: This service cannot use N-central’s Self-Healing feature.
Metric Name Description
Power Usage Indicates the amount of power, in Watts, being used by the ESXi server.
Power Man- Indicates the CPU power management technology currently being used by the ESXi server. agement Tech- ESX/ESXi supports both Enhanced Intel SpeedStep and Enhanced AMD PowerNow! nology
Power Man- Indicates the CPU power management policy currently in effect for the ESXi server. agement Policy
Power Supply (Cisco) Service The Power Supply (Cisco) Service monitors the state of the specified power supply, and it's line input, on a Cisco device.
- 332 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Most Cisco switches/routers running IOS. Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
Power Supply Index The SNMP index of the power supply to be monitored. For a list of the fans installed in the Cisco device, query it with the 1.3.6.1.4.1.9.9.13.1.5.1.2 SNMP OID.
Power Supply Name The name of the power supply to be monitored.
Object Numerical OID Descriptors
$PSState 1.3.6.1.4.1.9.9.13.1.5.1.3
$PSSource 1.3.6.1.4.1.9.9.13.1.5.1.4
Status Detail Description
Power Supply State The status of the power supply which is mapped as follows:
Normal: 1
Warning: 2
Failed: 3-6
Power Supply State A description of the power supply's state as follows: Description 1: Normal
2: Warning
3: Critical
4: Shutdown
5: Not Present
6: Not Functioning
Power Supply Source The line input of the power supply.
- 333 - N-central 10.0 Services Reference Manual
Power Supply (Dell) Service The Power Supply (Dell) service monitors the overall condition of the power supply for Dell servers.
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type SNMP
Instances on a Device 16
Supported Dell PowerEdge series servers running Dell OpenManage Server Administrator software Systems/Applications
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, and Server - Windows
Monitored By Windows Probe
Scan Interval 15 minutes
Power Supply The SNMP index of the power supply, which is determined by performing an SNMP walk Location Index on powerSupplyLocationName (.1.3.6.1.4.1.674.10892.1.600.12.1.8).
Power Supply The name of the power supply, which is determined by performing an SNMP walk on Location Value powerSupplyLocationName (.1.3.6.1.4.1.674.10892.1.600.12.1.8).
- 334 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Power Supply 1.3.6.1.4.1.674.10892.1.600.12.1.5 The status of the power supply is mapped as Status follows: Normal: 3 Warning: 0,1,2,4,7-4294967295 Failed: 5,6
The meaning of the statuses are: 1: Other 2: Unknown 3: OK 4: Non Critical 5: Critical 6: Non Recoverable
Power Supply (Dell iDRAC) Service The Power Supply (Dell iDRAC) service monitors the status of a power supply on a Dell PowerEdge server using the embedded integrated Dell Remote Access Controller (iDRAC).
Service Type SNMP
Instances on a 100 Device
Supported Dell PowerEdge servers with integrated Dell Remote Access Controller (iDRAC) Systems/Applicatio ns
Device Class for Servers - Management Interface CPU (SNMP)
Monitored By Windows Agent
Scan Interval 15 minutes
SNMP Value Type or select the name of the power supply to be monitored in the format PowerSupplyFQDD (Fully Qualified Device Descriptor). For a list of power supplies, query the device with the .1.3.6.1.4.1.674.10892.5.4.600.12.1.15 SNMP OID.
- 335 - N-central 10.0 Services Reference Manual
Status Object Numerical OID Description Detail Descriptors
Name $Name 1.3.6.1.4.1.674.10892.5.4.600.12. Indicates the location name of the 1.8 power supply.
Chassis $ChassisIn 1.3.6.1.4.1.674.10892.5.4.600.12. Indicates the index of the system Index dex 1.1 chassis as an integer value between 1 and 128.
Power $Status 1.3.6.1.4.1.674.10892.5.4.600.12. Indicates the current status of the Supply 1.5 power supply mapped as follows: Status 1 - other,
2 - unknown,
3 - ok,
4 - nonCritical,
5 - critical, and,
6 - nonRecoverable.
Power Supply (EqualLogic) Service The Power Supply (EqualLogic) service monitors the overall condition of the power supply for a PS6100 Equallogic SAN using v6.0.2 firmware.
Service Type SNMP
Instances on a Device 5
Supported PS6100 Equallogic SANs using v6.0.2 firmware Systems/Applications
Device Class Server - Generic and Server - Windows
Monitored By Windows Probe
Scan Interval 5 minutes
Power Supply Type the name of the power supply to be monitored. For a list of power supplies, query the SAN with the .1.3.6.1.4.1.12740.2.1.8.1.2 SNMP OID.
- 336 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Power Supply 1.3.6.1.4.1.12740.2.1.8. The status of the power supply is mapped as follows: Status 1.3 1: On and operating
2: No AC power
3: Failed or no data
Power Supply Fan 1.3.6.1.4.1.12740.2.1.8. If the Power Supply Status is On and operating, this Status 1.4 field indicates that the fan is operational.
Fan states are mapped as follows:
0: Not applicable
1: Fan is operational
2: Fan is not operational
Power Supply 1.3.6.1.4.1.12740.2.1.8. Specifies the power supply's firmware version. Firmware Version 1.5
Power Supply (Fujitsu) Service The Power Supply (Fujitsu) service monitors the status and current load of a power supply in a Fujitsu device.
Service Type SNMP
Instances on a Device 100
Supported Fujitsu servers running the Fujitsu ServerView agent. Systems/Applications
Device Class for CPU Servers - Generic or Servers - Windows (SNMP)
Monitored By Windows Agent
Power Supply Type the name of the power supply to be monitored. For a list of power supplies, query the device with the .1.3.6.1.4.1.231.2.10.2.2.10.6.2.1.3 SNMP OID.
Scanning The scan interval can be configured according to either a Once a Day or Daily Interval schedule.
- 337 - N-central 10.0 Services Reference Manual
Object Numerical OID Descriptors
$Status 1.3.6.1.4.1.231.2.10.2.2.10.6.2.1.5
$Load 1.3.6.1.4.1.231.2.10.2.2.10.6.2.1.6
Status Detail Description
Status Describes the current status of the power supply that is being monitored with values mapped as follows:
Normal: 3
Warning: 9
Failed: 1, 2, 4, 5, 6, 7, 8, 10, 11, 12, 13
1. Unknown 2. Not Present 3. OK 4. Failed 5. AC Failed 6. DC Failed 7. Critical Temperature 8. Not Manageable 9. Fan Failure Predicted 10. Fan Failure 11. Power Safe Mode 12. Non Redundant DC Fail 13. Non Redundant AC Fail
Power Supply Describes the current actual output load (measured in Watts) of the power supply Output Load that is being monitored.
Power Supply (HP) Service The Power Supply (HP) service monitors the overall condition of the power supply for HP ProLiant servers.
- 338 - N-central 10.0 Services Reference Manual
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type: SNMP
Instances on a Device 1
Supported HP Proliant Servers running HP Insight Manager 5.1 agents Systems/Applications
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, and Server - Windows
Monitored By Windows Probes
Scan Interval 15 minutes
OID/Calculation
Metric Name OID/Calculation Description
Power Supply .1.3.6.1.4.1.232.6.2.9.1 The status of the power supply is mapped as (HP) follows: Normal: 2 Warning: 1, 3 Failed: 4
The meaning of the statuses: 1: Other 2: OK 3: Degraded 4: Failed
- 339 - N-central 10.0 Services Reference Manual
Power Supply (Intel) Service The Power Supply (Intel) service monitors the overall condition of the specified power supply on a server with an Intel Motherboard.
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type SNMP
Instances on a Device 2
Supported Devices using an Intel motherboard, with the Intel SMS software installed Systems/Applications
Device Class Server - Generic, Server - Windows
Monitored By Windows Probes
Scan Interval 5 minutes
Power Supply Name The name of the power supply to be monitored. The names of power supplies available for monitoring can be obtained by querying the device with the 1.3.6.1.4.1.343.2.10.3.5.400.20.1.3 SNMP OID.
- 340 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Power Supply Status 1.3.6.1.4.1.343.2.10.3.5.400.20.1.5 The status of the power supply is mapped as follows: Normal: 3 Warning: 1, 2, 4, 5 Failed: 6
The meaning of the status: 1: Other 2: Unknown 3: OK 4: Non-critical 5: Critical 6: Non-recoverable
Power Supply Status 1.3.6.1.4.1.343.2.10.3.5.400.20.1.5 Describes the status of the power supply Description as one of: Other Unknown OK Non-critical Critical Non-recoverable
Power Supply (VMware) Service The Power Supply (VMware) service monitors the overall condition of a power supply on an ESXi server.
Note: If your ESX/ESXi server is operating on either Dell or HP hardware, it is strongly recommended that you install the Dell or HP Offline Bundle before the Windows Probe discovers the ESX/ESXi server. For instructions on installing the Dell or HP Offline Bundle, refer to the following articles in the N-central online knowledge base:
l KBA10019: Installing the HP Offline Bundle on ESX/ESXi Servers
l KBA10020: Installing the Dell Offline Bundle on ESX/ESXi Servers
- 341 - N-central 10.0 Services Reference Manual
Service Type ESXi
Instances on a Device 100
Supported ESX or ESXi 4.x, 5.x and later Systems/Applications Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 5 minutes
Power Supply Name The name of the logical drive to be monitored.
Note: This service cannot use N-central’s Self-Healing feature.
To access information about the power supply on your ESXi server, use a browser to access the following URL:
https://
Example: https://192.168.101.207/mob/?moid=ha- host&doPath=runtime.healthSystemRuntime.systemHealthInfo.numericSensorInfo
- 342 - N-central 10.0 Services Reference Manual
Metric Name Description
State The power supply status is mapped as follows:
Normal: 1
Warning: 1, 2, 4
Failed: 5, 6
State Description Describes the status of the power supply:
Other
Unknown
OK
Non-Critical
Critical or Non-recoverable
Enabled State Indicates whether the power supply has been enabled or disabled.
Enabled State Description n/a
Printer Conf Changes Service The Printer Conf Changes service monitors the number of configuration changes that affect the capabilities of a printer such as the addition or deletion of input/output bins, the addition or deletion of print interpreters, or modifications to the media size. These changes can often affect the ability of the printer to service specific types of print jobs.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Systems/Applications Any SNMP Printer-MIB Compliant Device (RFC1759)
Device Class Printer
Monitored By Windows Probe
Scan Interval 15 minutes
- 343 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Printer Conf 1.3.6.1.2.1.43.5.1.1.1 A numeric counter indicating the number of configuration Changes (Counter changes that have been applied to the target printer. 32)
Printer Cover Status Service The Printer Cover Status service monitors the current status of the printer cover.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Systems/Applications Any SNMP Printer-MIB Compliant Device (RFC1759)
Device Class Printer
Monitored By Windows Probe
Scan Interval 15 minutes
OID/Calculation
Metric OID/Calculation Description Name
Print Cover 1.3.6.1.2.1.43.6.1.1.2 The description value for Printer Cover device, which is determined by Description performing an SNMP walk on prtMarkerSuppliesDescription (.1.3.6.1.2.1.43.6.1.1.2).
Printer 1.3.6.1.2.1.43.6.1.1.3 Indicates the current condition of the printer cover as one of the Cover following:
Status l Normal - the printer cover is closed and the device can func- tion normally.
l Warning - the printer cover may be open or partially open pre- venting the device from functioning normally.
l Failed - the printer cover is open preventing the device from functioning normally.
Printer Display Service The Printer Display service monitors the message displayed on the message screen of the printer.
Note: This service cannot use N-central’s Self-Healing feature.
- 344 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 100
Supported Systems/Applications Any printer that reports the contents of its display through the Printer- MIB
Device Class Printer
Monitored By Windows Probe
Scan Interval 15 minutes
OID/Calculation
Metric OID/Calculation Description Name
Display Text 1.3.6.1.2.1.43.16.5.1.2 The text currently being shown in the printer's console display.
System 1.3.6.1.2.1.1.3 The time that has passed since the printer was last turned on or Uptime restarted.
Printer Page Count Service The Printer Page Count service monitors how many pages the printer has printed since it was first turned on (Page Count) and since it was last rebooted (Power On Count).
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 6
Supported Any SNMP Printer-MIB Compliant Device (RFC1759) Systems/Applications
Device Class Printer
Monitored By Windows Probe
Scan Interval 15 minutes
Printer Marker Index The SNMP index of the printer, which is determined by performing an SNMP walk on prtMarkerLifeCount (.1.3.6.1.2.1.43.10.2.1.4).
- 345 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Page Count 1.3.6.1.2.1.43.10.2.1.4 The count of pages printed during the lifetime of the printer.
Power On 1.3.6.1.2.1.43.10.2.1.5 The count of pages printed since the printer was last booted Count rebooted.
Printer Page Count (HP) Service The Printer Page Count (HP) service monitors the number of pages (including a total count as well as color and black-and-white) printed over the lifetime of an HP printer.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported All network-enabled HP LaserJet printers Systems/Applications
Device Class Printer
Monitored By Windows Probe
Scan Interval 15 minutes
Printer Marker Index The SNMP index of the printer device, which is determined by performing an SNMP walk on prtMarkerLifeCount (.1.3.6.1.2.1.43.10.2.1.4).
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation Description
Total Page Count 1.3.6.1.2.1.43.10.2.1.4 The number of pages printed over the lifetime of the device.
Color Page Count 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2.7 The number of pages printed in color over the lifetime of the device.
Black and White Total Page Count OID - Color Page The number of pages printed in black-and-white over Page Count Count OID the lifetime of the equipment.
- 346 - N-central 10.0 Services Reference Manual
Printer Status Service The Printer Status service monitors the current status of a specified printer.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Systems/Applications Any SNMP HOST-RESOURCES-MIB Compliant Device (RFC1514)
Device Class Printer
Monitored By Windows Probe
Scan Interval 15 minutes
- 347 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Printer Status 1.3.6.1.2.1.25.3.5.1.1 Indicates the current condition of the printer as one of the following: 1: Other
2: Unknown
3: Idle
4: Printing
5: Warming Up
Printer Detected 1.3.6.1.2.1.25.3.5.1.2 If the printer is in an error state, the conditions that defined this Error State state are reported as one of the following: 0: Low supply of paper
1: No paper available
2: Low supply of toner
3: No toner available
4: A door on the printer is open
5: The printer is jammed
6: The printer is offline
7: Technical service is requested for the printer
8: The input tray is missing or not installed properly
9: The output tray is missing or not installed properly
10: The marker supply is missing or not installed properly
11: The output tray is nearly full
12: The output tray is full
13: The input tray is empty
14: The printer is overdue for preventative maintenance
Printer Toner Level Service The Printer Toner Level service monitors the amount of toner as a percentage of the total capacity of the monitored printer.
- 348 - N-central 10.0 Services Reference Manual
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 15
Supported Any SNMP Printer-MIB Compliant Device (RFC1759) Systems/Applications
Device Class Printer
Monitored By Windows Probe
Scan Interval 15 minutes
Printer Marker The SNMP index of the toner cartridge, which is determined by performing an SNMP Supplies Description walk on prtMarkerSuppliesDescription (.1.3.6.1.2.1.43.11.1.1.6). Index
Print Marker Supplies The name of the toner cartridge, which is determined by performing an SNMP walk on Description Value prtMarkerSuppliesDescription (.1.3.6.1.2.1.43.11.1.1.6).
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric OID/Calculation Description Name
Max Capacity 1.3.6.1.2.1.43.11.1.1.8 The maximum capacity of toner cartridge.
Level 1.3.6.1.2.1.43.11.1.1.9 The current level of the toner cartridge.
Toner Level (Level / Max Capacity) x 100 The percentage of toner remaining.
Probe Status Service The Probe Status service monitors the time since the probe last checked in.
Note: This service cannot use N-central’s Self-Healing feature.
When Probe Status is first added to a device, the service will be in a Misconfigured state until the probe first makes contact with the central server.
During the monitoring process, the central server queries the time of the most recent connection of the probe to the central server. This is compared to the current time and the resulting difference is then compared to the specified threshold values so that it can be represented by the appropriate state on the status dashboard for the service.
- 349 - N-central 10.0 Services Reference Manual
Example: If the time difference between the previous and current connection is within 10 minutes, the service state will display Normal; between 10 and 20 minutes, Warning; and over 20 minutes, Failed.
You can choose to display the Probe Status service in the Active Issues view by selecting Show in the Active Issues View in the Service Details tab.
Service Type Central Server Asset
Instances on a Probe 1
Supported Systems/Applications Windows Probe
Monitored By Central Server Asset
Scan Interval 15 minutes
Status Details
Status Description Detail
Check-In The threshold that compares the time difference between the current time and the most recent Interval connection to the specified threshold values.
Process Service The Process service monitors the status of an individual process on Windows, MAC OS X, and Linux devices.
- 350 - N-central 10.0 Services Reference Manual
Service Local API, SNMP, and WMI Workstation Type
Instanc 20 es on a Device
Device Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation Class - Windows for Process (Local API)
Device Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop Class - Windows, Server - Windows, and Workstation - Windows for Process (SNMP)
Device Laptop - Windows, Server - Windows, and Workstation - Windows Class for Process (WMI)
Monitor Agent (Windows, Red Hat Enterprise Linux, and Mac OS X 10.4, 10.5) ed By
- 351 - N-central 10.0 Services Reference Manual
Scan 15 minutes Interval
Process The SNMP index of the status of the process. The SNMP index values can be obtained by Index performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1 l .544 l .972
l .8 l .564 l .1016
l .164 l .576 l .1032
l .192 l .628 l .1060
l .212 l .692 l .1084
l .240 l .708 l .1212
l .252 l .740 l .1256
l .420 l .800 l .1792
l .448 l .868 l .1800
l .512 l .900
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Process The name of the process to be monitored. If the Process service is monitored by a Windows Name Probe, the name must match the executable name that is listed in the Processes tab of the Windows Task Manager (and must also include the file extension).
Example: IEXPLORER.EXE
For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Note: For Linux Agents, the process name will usually be the same as the name of the process identification (PID) file but there are exceptions. To avoid potential failures, verify that the name of the process identified in the PID file is identical to the name configured as the process name.
Process The directory path of the process identification (PID) number file. PID File The PID file is used for Linux (Local API) agents only. (Linux Only) To avoid generating an unnecessary Failed status for this service, ensure that you provide access to:
l the directory in which the PID file is located, and
l the PID file itself.
- 352 - N-central 10.0 Services Reference Manual
Properties Queried and Calculations Performed (WMI only)
Namespace root\cimv2
WMI Class Win32_Process
WMI Property 0 Name
OID/Calculation
Metric Name OID/Calculation Description
Is the Process 1.3.6.1.2.1.25.4.2.1.7 The current status of the Process service indicated as Running? either Yes or No.
The Number of Process 1.3.6.1.2.1.25.4.2.1.2 The number of occurrences of the process that are Instances running at the same time.
Status Details
Status Detail Description
Process Users The name of the user account that initiated the process. (PIDs)
CPU Usage The percentage of CPU capacity that is used by the process.
Physical The percentage of physical memory that is used by the process. Memory Usage
Virtual The percentage of virtual memory that is used by the process. Memory Usage
IO Transfer The rate of I/O read operations used by the process (as indicated in bytes per second). Read
IO Transfer The rate of I/O write operations used by the process (as indicated in bytes per second). Write
- 353 - N-central 10.0 Services Reference Manual
Status Detail Description
IO Transfer The rate of I/O operations used by the process that are neither read nor write (as Other indicated in bytes per second).
IO Read The number of I/O read operations used by the process (as indicated in transactions per Operations second).
IO Write The number of I/O write operations used by the process (as indicated in transactions per Operations second).
IO Other The number of I/O operations used by the process that are neither read nor write (as Operations indicated in transactions per second).
Note: If I/O operations are consistently reported as either 0 bytes/second (for I/O transfers) or 0 transactions/second (for I/O operations), the Windows device on which the process is running may require configuration of its Update Speed. To modify the Update Speed, perform the following:
1. Start the Windows Task Manager. 2. Click the Processes tab. 3. Select the process that you want to edit. 4. Click View. 5. Under Update Speed, select Normal.
Process amc (Cisco) Service The Process amc (Cisco) service monitors the Alert Manager and Collector service for the Cisco Unified Communication server.
The Alert Manager and Collector is used for the real-time monitoring tool (RTMT) and was a component of the Cisco RIS Data Collector service in previous Windows releases of Cisco Unified Communications Manager. This service allows RTMT to retrieve real-time information that exists on nodes in the cluster.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
- 354 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
- 355 - N-central 10.0 Services Reference Manual
Status Detail Object Numerical OID Description Descriptors
Cisco AMC hrSWRunStatu 1.3.6.1.2.1.25.4.2. The status of the target software mapped Service s 1.7 as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process BPS (Cisco) Service The Process BPS (Cisco) service monitors the Cisco Bulk Provisioning Service for the Cisco Unified Communication server.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 356 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco Bulk hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software Provisioning Service us 1.7 mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process capf (Cisco) Service The Process capf (Cisco) service monitors the Cisco Certificate Authority Proxy Function (CAPF) service for the Cisco Unified Communication server.
- 357 - N-central 10.0 Services Reference Manual
Depending on your configuration, the Cisco Certificate Authority Proxy Function (CAPF) service can perform the following tasks:
l Issue locally significant certificates to supported Cisco Unified IP Phone models.
l Using SCEP, request certificates from third-party certificate authorities on behalf of supported Cisco Unified IP Phone models.
l Upgrade existing certificates on the phones.
l Retrieve phone certificates for troubleshooting.
l Delete locally significant certificates on the phone.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 358 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco Certificate hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target Authority Proxy Function us 1.7 software mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process carschlr (Cisco) Service The Process carschlr (Cisco) service monitors the Cisco CAR Scheduler service for the Cisco Unified Communication server.
- 359 - N-central 10.0 Services Reference Manual
The Cisco CAR Scheduler service allows you to schedule CAR-related tasks (for example, you can schedule report generation or CDR file loading into the CAR database).
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 360 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco CAR hrSWRunStatu 1.3.6.1.2.1.25.4.2. The status of the target software mapped Scheduler s 1.7 as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process ccm (Cisco) Service The Process ccm (Cisco) service monitors critical processes such as signaling and call control functionality for the Cisco Unified Communication server.
- 361 - N-central 10.0 Services Reference Manual
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
Monitored By Probe
Scan Interval 30 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
- 362 - N-central 10.0 Services Reference Manual
Status Object Numerical OID Description Detail Descriptors
CCM hrSWRunNa 1.3.6.1.2.1.25.4.2. Provides a description of the software including Name me 1.2 the manufacturer, revision, and the name by which it is commonly known.
If this software was installed locally, this should be the same string as used in the corresponding hrSWInstalledName.
CCM Stat hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software mapped as us us 1.7 follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process ccmAgt (Cisco) Service The Process ccmAgt (Cisco) service monitors the SNMP access to provisioning and statistics information that is available to the Cisco Unified Communication server.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 363 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco CallManager hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software SNMP Service us 1.7 mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process CCMDirSync (Cisco) Service The Process CCMDirSync (Cisco) service monitors the Cisco DirSync service for the Cisco Unified Communication server.
- 364 - N-central 10.0 Services Reference Manual
If you use an integrated corporate directory (for example, Microsoft Active Directory or Netscape/iPlanet Directory) with Cisco Unified Communications Manager, the Cisco DirSync service migrates the user data to the Cisco Unified Communications Manager database. The Cisco DirSync service does not synchronize the passwords from the corporate directory.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 365 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Object Numerical OID Description Detail Descriptors
Cisco hrSWRunStatus 1.3.6.1.2.1.25.4.2. The status of the target software mapped as DirSync 1.7 follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process cef (Cisco) Service The Process cef (Cisco) service monitors critical processes for the Cisco ExtendedFunctions service of the Cisco Unified Communication server.
- 366 - N-central 10.0 Services Reference Manual
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
- 367 - N-central 10.0 Services Reference Manual
Status Detail Object Numerical OID Description Descriptors
Cisco Extended hrSWRunNa 1.3.6.1.2.1.25.4.2. Provides a description of the software Functions me 1.2 including the manufacturer, revision, and Name the name by which it is commonly known.
If this software was installed locally, this should be the same string as used in the corresponding hrSWInstalledName.
Cisco Extended hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software mapped Functions Stat us 1.7 as follows: us 1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process cdpAgt (Cisco) Service The Process cdpAgt (Cisco) service monitors the Cisco CDP Agent for the Cisco Unified Communication server.
The Cisco CDP Agent uses the Cisco Discovery Protocol to provide SNMP access to network connectivity information on the Cisco Unified Communications Manager node.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 368 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco CDP hrSWRunStatus 1.3.6.1.2.1.25.4.2. The status of the target software mapped Agent 1.7 as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process cdpd (Cisco) Service The Process cdpd (Cisco) service monitors the CDP service for the Cisco Unified Communication server.
Cisco Discovery Protocol (CDP) is a Cisco protocol used to share information about other Cisco devices that are directly connected to the CUCM server. This information can include the operating system
- 369 - N-central 10.0 Services Reference Manual
version and IP address but CDP can also be used for on-demand routing which includes routing information in CDP messages so that dynamic routing protocols do not need to be used.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 370 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Object Numerical OID Description Detail Descriptors
Cisco hrSWRunStatus 1.3.6.1.2.1.25.4.2. The status of the target software mapped as CDP 1.7 follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process cdragent (Cisco) Service The Process cdragent (Cisco) service monitors the Cisco CDR Agent service for the Cisco Unified Communication server.
- 371 - N-central 10.0 Services Reference Manual
The Cisco CDR Agent service transfers CDR and CMR files that are generated by Cisco Unified CallManager from the local host to the CDR repository node where the CDR Repository Manager service runs over an SFTP connection. For this service to work, activate the Cisco CallManager service on the first node and ensure that it is running.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 372 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco CDR hrSWRunStatus 1.3.6.1.2.1.25.4.2. The status of the target software mapped Agent 1.7 as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process cdrrep (Cisco) Service The Process cdrrep (Cisco) service monitors the Cisco CDR Repository Manager for the Cisco Unified Communication server.
- 373 - N-central 10.0 Services Reference Manual
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
- 374 - N-central 10.0 Services Reference Manual
Status Detail Object Numerical OID Description Descriptors
Cisco CDR hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software Repository Manager us 1.7 mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process certM (Cisco) Service The Process certM (Cisco) service monitors the Certificate Expiry Monitor Service for the Cisco Unified Communication server.
The Certificate Expiry Monitor Service periodically checks the expiration status of certificates that Cisco Unified CallManager generates and sends notification when a certificate gets close to its expiration date.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 375 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco Certificate hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software Expiry Monitor us 1.7 mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process CiscoDRFLocal (Cisco) Service The Process CiscoDRFLocal (Cisco) service monitors the Cisco DRF Local service for the Cisco Unified Communication server.
- 376 - N-central 10.0 Services Reference Manual
The Cisco DRF Local service supports the Cisco DRF Local Agent that acts as the primary engine for the DRF Master Agent. Components on a node will register with the Cisco DRF Local Agent to use the disaster recovery framework. The Cisco DRF Local Agent then runs commands that it receives from the Cisco DRF Master Agent. The Cisco DRF Local Agent also transmits the status, logs, and command results to the Cisco DRF Master Agent.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 377 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco DRF hrSWRunStatus 1.3.6.1.2.1.25.4.2. The status of the target software mapped as Local 1.7 follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process CiscoDRFMaster (Cisco) Service The Process CiscoDRFMaster (Cisco) service monitors the Cisco DRF Master Agent service for the Cisco Unified Communication server.
- 378 - N-central 10.0 Services Reference Manual
The Cisco DRF Master Agent service supports the DRF Master Agent that works with the graphical user interface (GUI) or command line interface (CLI) to perform the following:
l scheduling backups,
l performing restorations,
l viewing dependencies,
l checking status of jobs, and,
l cancelling jobs.
The Cisco DRF Master Agent also provides the storage medium for the backup and restoration process.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 379 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco DRF hrSWRunStatu 1.3.6.1.2.1.25.4.2. The status of the target software mapped Master s 1.7 as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process CiscoLicenseMgr (Cisco) Service The Process CiscoLicenseMgr (Cisco) service monitors the License Manager service for the Cisco Unified Communication server.
The Cisco License Manager performs the following:
- 380 - N-central 10.0 Services Reference Manual
l tracks the licenses that a customer purchases and uses,
l controls licenses checkins and checkouts, and,
l takes responsibility for issuing and reclaiming licenses.
Cisco License Manager manages the Cisco Unified CallManager application and the number of IP phone unit licenses. When the number of telephones exceeds the number of licenses, it issues alarms to notify the administrator. This service runs on all the nodes but the service on the first node has the responsibility for issuing and reclaiming licenses.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 381 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco License hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software Manager us 1.7 mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process CiscoSyslogSub (Cisco) Service The Process CiscoSyslogSub (Cisco) service monitors the Syslog Service for the Cisco Unified Communication server.
- 382 - N-central 10.0 Services Reference Manual
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
- 383 - N-central 10.0 Services Reference Manual
Status Detail Object Numerical OID Description Descriptors
Cisco Syslog hrSWRunStatu 1.3.6.1.2.1.25.4.2. The status of the target software mapped Agent s 1.7 as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process cmi (Cisco) Service The Process cmi (Cisco) service monitors critical processes for the Cisco Messaging Interface of the Cisco Unified Communication server.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 384 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Object Numerical OID Description Detail Descriptors
CMI hrSWRunNa 1.3.6.1.2.1.25.4.2. Provides a description of the software including Name me 1.2 the manufacturer, revision, and the name by which it is commonly known.
If this software was installed locally, this should be the same string as used in the corresponding hrSWInstalledName.
CMI Stat hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software mapped as us us 1.7 follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
- 385 - N-central 10.0 Services Reference Manual
Process ctftp (Cisco) Service The Process ctftp (Cisco) service monitors the Cisco Trivial File Transfer Protocol (TFTP) that builds and serves files that are consistent with the trivial file transfer protocol, a simplified version of FTP, for the Cisco Unified Communication server. Cisco TFTP serves embedded component executable files, ringer files, and device configuration files.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 386 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 30 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Object Numerical OID Description Detail Descriptors
Cisco Tftp hrSWRunStatus 1.3.6.1.2.1.25.4.2. The status of the target software mapped as 1.7 follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process CTIManager (Cisco) Service The Process CTIManager (Cisco) service monitors critical processes for the CTI Manager of the Cisco Unified Communication server. The CTI Manager contains the CTI components that interface with applications.
- 387 - N-central 10.0 Services Reference Manual
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
- 388 - N-central 10.0 Services Reference Manual
Status Detail Object Numerical OID Description Descriptors
Cisco CTI hrSWRunNa 1.3.6.1.2.1.25.4.2. Provides a description of the software Manager me 1.2 including the manufacturer, revision, and Name the name by which it is commonly known.
If this software was installed locally, this should be the same string as used in the corresponding hrSWInstalledName.
Cisco CTI hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software mapped as Manager Stat us 1.7 follows: us 1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process CTLProvider (Cisco) Service The Process CTLProvider (Cisco) service monitors the Cisco CTL Provider service which works for Cisco Unified Communications Manager with the Cisco CTL Provider Utility, a client-side plug-in, to change the security mode for the cluster from nonsecure to mixed mode. When you install the plug-in, the Cisco CTL Provider service retrieves a list of all Cisco Unified Communications Manager and Cisco TFTP servers in the cluster for the CTL file, which contains a list of security tokens and servers in the cluster.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 389 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco CTL hrSWRunStatu 1.3.6.1.2.1.25.4.2. The status of the target software mapped Provider s 1.7 as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process dblrpc (Cisco) Service The Process dblrpc (Cisco) service monitors the Cisco DB Replicator service that ensures database configuration and data synchronization between the first and subsequent nodes in the cluster for the Cisco Unified Communication server.
- 390 - N-central 10.0 Services Reference Manual
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
- 391 - N-central 10.0 Services Reference Manual
Status Detail Object Numerical OID Description Descriptors
A Cisco DB hrSWRunStatu 1.3.6.1.2.1.25.4.2. The status of the target software replicator s 1.7 mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process DHCPMonitor (Cisco) Service The Process DHCPMonitor (Cisco) service monitors IP address changes for IP phones in the database tables of the Cisco Unified Communication server.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 392 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco Messaging hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the Cisco Messaging Interface us 1.7 Interface mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process hostagt (Cisco) Service The Process hostagt (Cisco) service monitors the Host Resources Agent for the Cisco Unified Communication server.
The Host Resources Agent provides SNMP access to host information such as:
- 393 - N-central 10.0 Services Reference Manual
l storage resources,
l process tables,
l device information, and,
l installed software base.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 394 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Host Resources hrSWRunStatu 1.3.6.1.2.1.25.4.2. The status of the target software Agent s 1.7 mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process ipvmsd (Cisco) Service The Process ipvmsd (Cisco) service monitors critical processes for the Cisco IP Voice Media Streaming Application of the Cisco Unified Communication server.
- 395 - N-central 10.0 Services Reference Manual
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
- 396 - N-central 10.0 Services Reference Manual
Status Detail Object Numerical OID Description Descriptors
Cisco IP Voice hrSWRunNa 1.3.6.1.2.1.25.4.2. Provides a description of the software Media me 1.2 including the manufacturer, revision, Streaming Name and the name by which it is commonly known.
If this software was installed locally, this should be the same string as used in the corresponding hrSWInstalledName.
Cisco IP Voice hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software Media us 1.7 mapped as follows: Streaming Statu s 1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process LpmTool (Cisco) Service The Process LpmTool (Cisco) service monitors the Log Partition Monitoring Tool Service for the Cisco Unified Communication server.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 397 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco Log Partition hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software Monitoring Tool us 1.7 mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process mib2agt (Cisco) Service The Process mib2agt (Cisco) service monitors the MIB2 Agent for the Cisco Unified Communication server.
- 398 - N-central 10.0 Services Reference Manual
The MIB2 Agent provides SNMP access to variables that are defined in RFC 1213 which read and write variables (for example, system, interfaces, and, IP address).
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 399 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Object Numerical OID Description Detail Descriptors
MIB2 hrSWRunStatus 1.3.6.1.2.1.25.4.2. The status of the target software mapped as Agent 1.7 follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process RisDC (Cisco) Service The Process RisDC (Cisco) service monitors the Real-time Information Server (RIS) feature for the Cisco Unified Communication server.
- 400 - N-central 10.0 Services Reference Manual
The Real-time Information Server (RIS) maintains real-time Cisco Unified Communications Manager information such as device registration status, performance counter statistics, and critical alarms generated. The Cisco RIS Data Collector service provides an interface for applications, such as Real-Time Monitoring Tool (RTMT), SOAP applications, Cisco Unified Communications Manager Administration and AlertMgrCollector (AMC) to retrieve the information that is stored in all RIS nodes in the cluster.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 401 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco RIS Data hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software Collector us 1.7 mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process rtmtreporter (Cisco) Service The Process rtmtreporter (Cisco) service monitors the Cisco Serviceability Reporter service for the Cisco Unified Communication server.
- 402 - N-central 10.0 Services Reference Manual
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
Monitored By Probe
Scan Interval 30 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
- 403 - N-central 10.0 Services Reference Manual
Status Detail Object Numerical OID Description Descriptors
Cisco CallManager hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target Serviceability RTMT us 1.7 software mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process sappagt (Cisco) Service The Process sappagt (Cisco) service monitors the System Application Agent for the Cisco Unified Communication server.
The System Application Agent provides SNMP access to the applications that are installed and running on the CUCM server. It also implements the SYSAPPL-MIB.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 404 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
System hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software Application Agent us 1.7 mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process snmpdm (Cisco) Service The Process snmpdm (Cisco) service monitors the SNMP Master Agent for the Cisco Unified Communication server.
This service acts as the agent protocol engine and provides the following related to SNMP requests:
- 405 - N-central 10.0 Services Reference Manual
l authentication,
l authorization,
l access control, and,
l privacy functions.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 406 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
SNMP Master hrSWRunStatu 1.3.6.1.2.1.25.4.2. The status of the target software mapped agent s 1.7 as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process TAPS (Cisco) Service The Process TAPS (Cisco) service monitors the Auto-Registered Phone Tool for the Cisco Unified Communication server. The Auto-Registered Phone Tool allows you to upload a customized configuration on an automatically registered phone after a user responds to Interactive Voice Response (IVR) prompts.
- 407 - N-central 10.0 Services Reference Manual
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
- 408 - N-central 10.0 Services Reference Manual
Status Detail Object Numerical OID Description Descriptors
Cisco TAPS hrSWRunStatu 1.3.6.1.2.1.25.4.2. The status of the target software mapped Service s 1.7 as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process tomcat (Cisco) Service The Process tomcat (Cisco) service monitors the Cisco Tomcat service that supports the web server for the Cisco Unified Communication server.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 409 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Object Numerical OID Description Detail Descriptors
Cisco hrSWRunStatus 1.3.6.1.2.1.25.4.2. The status of the target software mapped as Tomcat 1.7 follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
Process tracecollection (Cisco) Service The Process tracecollection (Cisco) service monitors the Cisco Trace Collection Service for the Cisco Unified Communication server.
- 410 - N-central 10.0 Services Reference Manual
Cisco Trace Collection is a web-based trace tool used by the system administrator and support personnel to troubleshoot Cisco Unified CallManager problems. Trace collection provides three main functions: configuring trace parameters, collecting trace files, and analyzing trace data for troubleshooting problems.
Note: For more information on Cisco Unified Communication Manager, refer to http://www.cisco.com/c/en/us/products/unified-communications/unified-communications- manager-callmanager/
Service Type SNMP
Instances on a 16 Device
Supported Cisco Unified Communications Manager Version 8.6, 9.0, 9.1, and 9.2 Systems/Applicatio ns
Device Class Server - Windows
- 411 - N-central 10.0 Services Reference Manual
Monitored By Probe
Scan Interval 15 minutes
Process Name Type the name of the process to monitor. For the Process (SNMP) service, the name must match the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
Process Index The resulting OID index for the status of running processes over the last minute for the Process (SNMP) service.
The index values can be obtained by performing an SNMP walk on the OID value: .1.3.6.1.2.1.25.4.2.1.2 (hrSWRunName).
The index values are:
l .1, l .544, l .972,
l .8, l .564, l .1016,
l .164, l .576, l .1032,
l .192, l .628, l .1060,
l .212, l .692, l .1084,
l .240, l .708, l .1212,
l .252, l .740, l .1256,
l .420, l .800, l .1792, and
l .448, l .868, l .1800.
l .512, l .900,
Only a maximum of 10 values can be monitored. You must determine which OID index value is relevant. The OID description is contained in the HOST-RESOURCES-MIB definition file.
Status Detail Object Numerical OID Description Descriptors
Cisco Trace hrSWRunStat 1.3.6.1.2.1.25.4.2. The status of the target software Collection Service us 1.7 mapped as follows:
1. Running 2. Runnable 3. Not Runnable 4. Invalid
RAID Status (Adaptec) Service The RAID Status (Adaptec) service monitors the status of the specified Adaptec RAID controller.
Note: Adaptec Storage Manager or IBM ServeRAID Manager must be installed. For a complete list of supported models, please refer to:
- 412 - N-central 10.0 Services Reference Manual
l http://www.adaptec.com/en-US/products/asm/, or,
l https://www-304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR- 61707&brandind=5000008
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type SNMP
Instances on a Device 10
Supported Any device using an Adaptec HostRAID card or an IBM ServeRAID card Systems/Applications
Device Class Server - Generic and Server - Windows
Monitored By Windows Probes
Scan Interval 5 minutes
RAID Controller SNMP Iden- Used to specify the SNMP identifier for the RAID controller. tifier The identifier can be found by querying the device with the 1.3.6.1.4.1.795.14.1.201.1.1.1 SNMP OID.
- 413 - N-central 10.0 Services Reference Manual
OID/Calculation
- 414 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
RAID Controller Status 1.3.6.1.4.1.795.14.1.201.1.1.15 The “RAID Controller Status” scandetail is mapped as follows: Normal: 3 Warning: 4 Failed: 1,2,5
Here are the meanings for each of the possible statuses: 1: Unknown 2: Other 3: Okay 4: Warning 5: Failure
RAID Controller Status 1.3.6.1.4.1.795.14.1.201.1.1.15 Describes the status of the RAID Controller as Description one of: Unknown Other Okay Warning Failure
Battery Status 1.3.6.1.4.1.795.14.1.201.1.1.14 The “Battery Status” scandetail is mapped as follows: Normal: 3,5 Warning: 1,2,4,7,8,9,10 Failed: 6
Here are the meanings for each of the possible statuses: 1: Unknown 2: Other 3: Applicable 4: Not Installed 5: Okay 6: Failed 7: Charging 8: Discharging 9: In Maintenance Mode 10: Charging Disabled
- 415 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Battery Status Descrip- 1.3.6.1.4.1.795.14.1.201.1.1.14 Describes the status of the battery for the RAID tion controller as one of: Unknown Other Applicable Not Installed Okay Failed Charging Discharging In Maintenance Mode Charging Disabled
Model 1.3.6.1.4.1.795.14.1.201.1.1.4 Indicates the model (descriptive name) of the RAID controller.
Serial Number 1.3.6.1.4.1.795.14.1.201.1.1.6 Indicates the serial number of the RAID con- troller.
Firmware Version 1.3.6.1.4.1.795.14.1.201.1.1.5 Indicates the version of the RAID controller firm- ware.
RAID Status (Dell) Service The RAID Status (Dell) service monitors the state of the RAID controller, the state of the RAID controller’s battery, and the firmware version of the RAID controller.
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
- 416 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 2
Supported Dell servers running Dell OpenManage Server Administrator software Systems/Applications
Device Class Server - Windows, Server - Generic
Monitored By Windows agent, Windows Probe
Scan Interval 5 minutes
RAID Controller Enter the name of the RAID controller to be monitored. To get a list of the RAID controller names, query the device with the 1.3.6.1.4.1.674.10893.1.20.130.1.1.2 SNMP OID.
RAID Battery Enter the name of the battery to be monitored. For a list of the available batteries, query the device with the .1.3.6.1.4.1.674.10893.1.20.130.15.1.2 SNMP OID.
- 417 - N-central 10.0 Services Reference Manual
OID/Calculation
- 418 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Controller State 1.3.6.1.4.1.674.10893.1.20.130.1.1.5 The status of the controller is mapped as follows: Normal: 1, 3 Warning: 0, 6 Failed: 2, 4
The meanings of the possible statuses: 0: Unknown 1: Ready 2: Failed 3: Online 4: Offline 6: Degraded
Controller State Descrip- 1.3.6.1.4.1.674.10893.1.20.130.1.1.5 Describes the status of the controller as tion one of: Unknown Ready Failed Online Offline Degraded
Firmware Version 1.3.6.1.4.1.674.10893.1.20.130.1.1.8 The controller's current firmware version.
- 419 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Battery State 1.3.6.1.4.1.674.10893.1.20.130.15.1.4 The status of the battery is mapped as follows: Normal: 1 Warning: 0, 7, 9, 10, 12, 36 Failed: 2, 6, 21
The meanings of the possible statuses: 0: Unknown 1: Ready 2: Failed 6: Degraded 7: Reconditioning 9: High 10: Low Power 12: Charging 21: Missing 36: Learning
Battery State Descrip- 1.3.6.1.4.1.674.10893.1.20.130.15.1.4 Describes the status of the battery as one tion of: Unknown Ready Failed Degraded Reconditioning High Low Power Charging Missing Learning
RAID Status (EqualLogic) Service The RAID Status (EqualLogic) service monitors the state of the RAID controller for a PS6100 Equallogic SAN using v6.0.2 firmware.
- 420 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 100
Supported Sys- Model PS6100 Dell EqualLogic SAN running v6.0.2 firmware tems/Applications
Device Class Server - Windows, Server - Generic
Monitored By Windows agent, Windows Probe
Scan Interval 5 minutes
RAID Array Type the name of the RAID array to be monitored. For a list of the available RAID arrays, query the SAN with the .1.3.6.1.4.1.12740.2.1.1.1.9 SNMP OID.
- 421 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
RAID Status 1.3.6.1.4.1.12740.2.1.13. Specifies the status of the RAID using a composite view of 1.1 the underlying sub-systems with the status mapped to:
1. OK - The RAID is operating normally. 2. Degraded - The RAID is in a degraded state, pos- sibly because no spares are available. 3. Verifying - A verification pass is being run with a percentage complete value being displayed. 4. Reconstructing - A drive is being reconstructed with a percentage complete value being displayed. 5. Failed - The RAID experienced a failure, possibly due to a failed drive with no spare being available. 6. Catastrophic Loss = This may not be visible to the user since the RAID may not be able to start up. This means that administrator intervention is required to correct the problem. 7. Expanding 8. Mirroring - Indicates that a bad drive is being mirrored onto a spare drive.
RAID Capacity 1.3.6.1.4.1.12740.2.1.10. This value is expressed as a percentage and is calculated (%) 1.2 (UsedStorage) by dividing the UsedStorage value by the TotalStorage value and then multiplying the result by 100. 1.3.6.1.4.1.12740.2.1.10. 1.1 (TotalStorage)
Are There Lost 1.3.6.1.4.1.12740.2.1.13. Specifies whether there are lost blocks in the RAID array RAID Blocks 1.3 which the user may want to clear. Mapped to: To Be Cleared? 1. True 2. False
Number Of 1.3.6.1.4.1.12740.2.1.13. Specifies the number of disks that have been allocated as Spares 1.4 spares in an array.
- 422 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Number Of 1.3.6.1.4.1.12740.2.1.11. Specifies the number of controller modules in the array. Controllers 1.3
Number Of 1.3.6.1.4.1.12740.2.1.11. Specifies the total number of disks that have been installed Disks 1.4 in the array.
Read/Write 1.3.6.1.4.1.12740.2.1.11. Specifies the size (in MB) of the Read/Write cache within Cache Size 1.5 the array.
Read/Write 1.3.6.1.4.1.12740.2.1.11. Specifies the mode that the Read/Write cache is currently Cache Mode 1.6 in within the array. The default is Write-back but the array will be configured to Write-thru whenever there is a battery failure. Mapped to:
0 - Unknown
1 - Write-thru
2 - Write-back
RAID Controller Status (Fujitsu) Service The RAID Controller Status (Fujitsu) service monitors various elements of a RAID Controller in a Fujitsu device.
Service Type SNMP
Instances on a Device 100
Supported Fujitsu servers running the Fujitsu ServerView agent. Systems/Applications
Device Class for CPU Servers - Generic or Servers - Windows (SNMP)
Monitored By Windows Agent
RAID Contoller Type the name of the RAID controller to be monitored. For a list of RAID controllers, query the device with the .1.3.6.1.4.1.231.2.49.1.4.2.1.25 SNMP OID.
Scanning The scan interval can be configured according to either a Once a Day or Daily Interval schedule.
- 423 - N-central 10.0 Services Reference Manual
Object Descriptors Numerical OID
$Manufacturer 1.3.6.1.4.1.231.2.49.1.4.2.1.3
$Model 1.3.6.1.4.1.231.2.49.1.4.2.1.2
$BusLocation 1.3.6.1.4.1.231.2.49.1.4.2.1.5
$FirmwareRevision 1.3.6.1.4.1.231.2.49.1.4.2.1.7
$BIOSRevision 1.3.6.1.4.1.231.2.49.1.4.2.1.8
$NumberOfChannels 1.3.6.1.4.1.231.2.49.1.4.2.1.9
$NumberOfPhysicalDisks 1.3.6.1.4.1.231.2.49.1.4.2.1.11
$NumberOfLogicalDrives 1.3.6.1.4.1.231.2.49.1.4.2.1.12
$CacheSize 1.3.6.1.4.1.231.2.49.1.4.2.1.13
$Status 1.3.6.1.4.1.231.2.49.1.4.2.1.15
$Interface 1.3.6.1.4.1.231.2.49.1.4.2.1.16
$SerialNumber 1.3.6.1.4.1.231.2.49.1.4.2.1.21
$DriverName 1.3.6.1.4.1.231.2.49.1.4.2.1.22
$DriverRevision 1.3.6.1.4.1.231.2.49.1.4.2.1.23
$BBUSStatus 1.3.6.1.4.1.231.2.49.1.4.2.1.24
$UEFIDriverRevision 1.3.6.1.4.1.231.2.49.1.4.2.1.27
- 424 - N-central 10.0 Services Reference Manual
Status Detail Description
Controller Describes the current status of the RAID controller that is being monitored with values Status mapped as follows:
Normal: 1
Warning: 2, 5
Failed: 3
1. OK 2. Warning 3. Error 5. Unknown
Battery Backup Describes the current status of the backup battery for the RAID controller that is being Status monitored with values mapped as follows:
Normal: 3
Warning: 6
Failed: 1, 2, 4, 5, 7
1. Unknown 2. Not Installed 3. Normal 4. Charging 5. Discharging 6. Warning 7. Failed
Manufacturer Indicates the name of the manufacturer of the RAID controller.
Model Indicates the model (descriptive name) of the RAID controller.
Serial Number Indicates the serial number of the RAID controller.
Firmware Indicates the version of the RAID controller firmware. Version
BIOS Version Indicates the version of the BIOS of the RAID controller that is being monitored.
UEFI Version Indicates the version of the UEFI (Unified Extensible Firmware Interface) of the RAID controller that is being monitored.
- 425 - N-central 10.0 Services Reference Manual
Status Detail Description
Driver Name Specifies the name of the software driver for the RAID controller that is being monitored.
Driver Version Specifies the version of the software driver for the RAID controller that is being monitored.
Bus Location Indicates the location of the bus interface for the RAID controller that is being monitored.
Number of Specifies the number of hard disk channels available for the RAID controller that is being Channels monitored.
Number of Specifies the total number of physical disks that have been installed in the array. Physical Disks
Number of Specifies the total number of logical disks that have been installed in the array. Logical Drives
Onboard Cache Specifies the size (in MB) of the onboard cache within the array. Size
Disk Indicates the type of disk interface of the RAID controller that is being monitored (for Connection example, IDE, SCSI, or SAS). Interface
RAID Status (HP) Service The RAID Status (HP) service monitors the overall status of a RAID array on an HP/ProLiant server.
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
- 426 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Systems/Applications HP Proliant Servers running HP Insight Manager 5.1 and later agents
Device Class Server - Generic and Server - Windows
Monitored By Windows Probes
Scan Interval 15 minutes
OID/Calculation
Metric Name OID/Calculation Description
RAID Status 1.3.6.1.4.1.232.3.1.3 The overall condition status of the disk array is mapped as (HP) follows: Normal = 1, 2 Warning = 3 Failed = 4
Where the meanings of the possible statuses are: 1 = Other 2 = OK 3 = Failed 4 = Predictive Failure
RAID Status (VMware) Service The RAID Status (VMware) service monitors the state of a RAID controller on an ESXi server.
Note: If your ESX/ESXi server is operating on either Dell or HP hardware, it is strongly recommended that you install the Dell or HP Offline Bundle before the Windows Probe discovers the ESX/ESXi server. For instructions on installing the Dell or HP Offline Bundle, refer to the following articles in the N-central online knowledge base:
l KBA10019: Installing the HP Offline Bundle on ESX/ESXi Servers
l KBA10020: Installing the Dell Offline Bundle on ESX/ESXi Servers
- 427 - N-central 10.0 Services Reference Manual
Service Type ESXi
Instances on a Device 100
Supported ESX or ESXi 4.x, 5.x and later Systems/Applications Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 5 minutes
RAID Controller Name The unique identifier of the RAID controller being monitored.
Note: This service cannot use N-central’s Self-Healing feature.
To access information about the RAID controllers on your ESXi server, use a browser to access the following URL:
https://
Example: https://192.168.101.207/mob/?moid=ha- host&doPath=runtime.healthSystemRuntime.hardwareStatusInfo.storageStatusInfo
- 428 - N-central 10.0 Services Reference Manual
Metric Name Description
State The RAID controller status is mapped as follows:
Normal: 1
Warning: 1, 2, 4
Failed: 5, 6
State Description Describes the status of the RAID controller:
Other
Unknown
OK
Non-Critical
Critical or Non-recoverable
Enabled State Indicates whether the RAID controller has been enabled or disabled.
Enabled State Description n/a
SCOM Computer Alerts Service The SCOM Computer Alerts service monitors the computer alerts raised by System Center Operations Manager.
Note: To use the SCOM Computer Alerts Service or the SCOM Distributed Application Alerts Service, Windows probes and Windows agents require Microsoft .NET Framework version 3.0.34353
Service Type SCOM SDK
Instances on a Device 1
Supported Any Server - Windows with SCOM or SCE installed Systems/Applications
Device Class Server - Windows
Monitored By Windows Probes, Windows Agents
Scan Interval 5 minutes
- 429 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Computers in Displays the number of computers that System Center Operations Manager is the Critical State reporting as being in a Critical state.
Computers in Displays the number of computers that System Center Operations Manager is the Warning reporting as being in a Warning state. state
Computers in Displays the number of computers that System Center Operations Manager is the Success reporting as being in a Success state. State
Computers in Displays the number of computers that System Center Operations Manager is Maintenance reporting as being in a Maintenance state.
Computers in Displays the number of computers that System Center Operations Manager is the Unknown reporting as being in an Unknown state. state
SCOM Distributed Application Alerts Service The SCOM Distributed Application Alerts service monitors the distributed application alerts raised by System Center Operations Manager.
Note: To use the SCOM Computer Alerts Service or the SCOM Distributed Application Alerts Service, Windows probes and Windows agents require Microsoft .NET Framework version 3.0.34353
Service Type SCOM SDK
Instances on a Device: 1
Supported Any Server - Windows with SCOM or SCE installed Systems/Applications
Device Class Server - Windows
Monitored By Windows Probes, Windows Agents
Scan Interval 5 minutes
- 430 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Distributed Displays the number of distributed applications that System Center Oper- Applications in ations Manager is reporting as being in a Critical state. the Critical State
Distributed Displays the number of distributed applications that System Center Oper- Applications in ations Manager is reporting as being in a Warning state. the Warning state
Distributed Displays the number of distributed applications that System Center Oper- Applications in ations Manager is reporting as being in a Success state. the Success State
Distributed Displays the number of distributed applications that System Center Oper- Applications in ations Manager is reporting as being in a Maintenance state. Maintenance
Distributed Displays the number of distributed applications that System Center Oper- Applications in ations Manager is reporting as being in an Unknown state. the Unknown state
Security Logs Service This service monitors the SNMP traps and syslog messages that are transmitted to the monitoring probe. Appliances and applications that run on a computer, such as a server, can be configured to record events to the probe.
Note: This service cannot use N-central’s Self-Healing feature.
During the monitoring process, this service listens for SNMP traps and log messages that are transmitted to the probe. The service then interprets these events and displays the appropriate status based on the regular expressions that you define. The service also supports wide characters.
Note: The monitored device must be configured to send syslog messages to the IP address of the Windows probe. The IP address of the device that is registered in N-central must be the same as the IP address that sends SNMP traps to the probes.
- 431 - N-central 10.0 Services Reference Manual
Service Type Syslog
Instances on a 1 Device
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, and Server - Windows
Monitored By Windows Probe
Scan Interval 5 minutes
Status Details
Status Description Detail
Regular The threshold values for the regular expressions that you specified on the Service Details tab. Expressions (1 to 6)
The line The number of lines, in the log file, on which the keyword has been located and returned by the count agent. This information is displayed for each regular expression on the status details screen for matched the service, any applicable reports, and any triggered notifications (except for numeric pages). regex...
The first The first 250 characters of the first line, in the log file, containing the matching keyword line returned by the agent. This information is displayed on the service's status details screen, any matched applicable reports, and any triggered notifications (except for numeric pages).
Server Temp (Dell) Service The Server Temp (Dell) service monitors the Status and temperature reading of a temperature sensor on a Dell server.
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
- 432 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 256
Supported Dell PowerEdge series servers running Dell OpenManage Server Administrator software Systems/Applications
Device Class Server - Generic, Other, Printer, Scanner/Camera, Switch/Router, Server - Windows
Monitored By Windows Probes
Scan Interval 15 minutes
Temperature Probe The SNMP index of the temperature probe, which is determined by performing an SNMP Location Name Index walk on temperatureProbeLocationName (.1.3.6.1.4.1.674.10892.1.700.20.1.8).
Temperature Probe The name of the temperature probe, which is determined by performing an SNMP walk Location Name Value on temperatureProbeLocationName (.1.3.6.1.4.1.674.10892.1.700.20.1.8).
OID/Calculation
Metric Name OID/Calculation Description
Server Temp (Dell) 1.3.6.1.4.1.674.10892.1.700.20.1.5 The probe status of the temperature probe is Status mapped as follows: Normal: 3 Warning: 0-2, 4, 7, 11-4294967295 Failed: 5, 6, 8-10
The meanings of the possible statuses: 1: Other 2: Unknown 3: OK 4: Non-critical Upper 5: Critical Upper 6: Non-Recoverable Upper 7: Non-critical Lower 8: Critical Lower 9: Non-recoverable Lower 10: Failed
Server Temp (Dell) 1.3.6.1.4.1.674.10892.1.700.20.1.6 The temperature reading of the temperature Reading sensor (in degrees Centigrade.)
- 433 - N-central 10.0 Services Reference Manual
Server Temp (HP) Service The Server Temp (HP) service monitors the overall condition of the thermal environment on an HP ProLiant server.
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
Service Type SNMP
Instances on a Device 1
Supported HP Proliant Servers running HP Insight Manager 5.1 and later agents Systems/Applications
Device Class Server - Generic, Other, Printer, Scanner/Camera, Switch/Router, and Server - Windows
Monitored By Windows Probes
Scan Interval 15 minutes
- 434 - N-central 10.0 Services Reference Manual
OID/Calculation
Metric Name OID/Calculation Description
Server Temp (HP) 1.3.6.1.4.1.232.6.2.6.1 The status of the thermal environment is mapped as follows: Normal: 1, 2 Warning: 3 Failed: 4
The meanings of the possible statuses: 1: Other 2: OK 3: Degraded 4: Failed
Server Temp (Intel) Service The Server Temp (Intel) service monitors the status and temperature reading of the temperature sensors on Intel motherboards.
The service requires the names of the temperature probes being monitored. To see the list of available temperature probes, query the device with the 1.3.6.1.4.1.343.2.10.3.5.600.40.1.3 SNMP OID.
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
- 435 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Devices using an Intel motherboard, with the Intel SMS software installed Systems/Applications
Device Class Server - Generic, Server - Windows
Monitored By Windows Probes
Scan Interval 15 minutes
Baseboard Probe The name of the baseboard temperature probe to be monitored. The names of tem- perature probes available for monitoring can be obtained by querying the device with the 1.3.6.1.4.1.343.2.10.3.5.600.40.1.3 SNMP OID.
Panel Probe The name of the panel temperature probe to be monitored. The names of temperature probes available for monitoring can be obtained by querying the device with the 1.3.6.1.4.1.343.2.10.3.5.600.40.1.3 SNMP OID.
- 436 - N-central 10.0 Services Reference Manual
OID/Calculation
- 437 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Baseboard Probe Status 1.3.6.1.4.1.343.2.10.3.5.600.40.1.5 Probe Status is mapped as follows: Normal: 3 Warning: 1, 2, 4 Failed: 5, 6
The meanings for each of the possible fan statuses: 1: Other 2: Unknown 3: OK 4: Non Critical 5: Critical 6: Non Recoverable
Baseboard Probe Status Description 1.3.6.1.4.1.343.2.10.3.5.600.40.1.5 Describes the baseboard temperature probe status as one of: Other Unknown OK Non Critical Critical Non Recoverable
Baseboard Temperature (\u00b0 C) 1.3.6.1.4.1.343.2.10.3.5.600.40.1.6 Displays the baseboard temperature in degrees Celsius.
Front Panel Probe Status 1.3.6.1.4.1.343.2.10.3.5.600.40.1.5 Indicates the front panel temperature probe status.
- 438 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Front Panel Probe Status Description 1.3.6.1.4.1.343.2.10.3.5.600.40.1.5 Describes the front panel temperature probe status as one of: Normal, Warning, or, Failed.
Front Panel Temperature (\u00b0 C) 1.3.6.1.4.1.343.2.10.3.5.600.40.1.6 Displays the front panel temperature in degrees Celsius.
Server Temp (IBM) Service The Server Temp (IBM) service monitors the status of the specified temperature sensor on an IBM server.
The service requires the names of the temperature probes being monitored. To see the list of available temperature probes, query the device with the 1.3.6.1.4.1.2.6.159.1.1.80.1.1.1 SNMP OID.
Special Note
This service operates in conjunction with the vendor-supplied hardware agent and requires SNMP to be configured so that it is accessible from both the N-central Agent and the N-central Probe.
The following are the requirements in order to associate this service with a device:
l The device must undergo discovery using a Probe-based asset scan.
l The device must have SNMP enabled (refer to the Properties tab of the device).
l Once SNMP has been enabled for the device, a community string must be configured (the default community string is public).
For more information, refer to "Configuring Servers for Hardware Montoring" in the N-central online help.
- 439 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 10
Supported Any UMSMSENSOR-MIB Compliant Device Systems/Applications
Device Class Server - Generic, Server - Windows
Monitored By Windows Probes
Scan Interval 5 minutes
Temperature Sensor The name of the temperature sensor to be monitored. The name can be obtained by Name querying the device with the 1.3.6.1.4.1.2.6.159.1.1.80.1.1.1 SNMP OID.The name of the temperature sensor to be monitored.
OID/Calculation
Metric Name OID/Calculation Description
Temperature 1.3.6.1.4.1.2.6.159.1.1.80.1.1.2
Temperature Sensor 1.3.6.1.4.1.2.6.159.1.1.80.1.1.21 Describes the current status of the temperature Status sensor as one of: OK Degraded Pred Fail (predicted failure)
ShadowProtect Service The ShadowProtect service monitors StorageCraft's ShadowProtect backup software.
The service will monitor the following information about ShadowProtect backup jobs:
l Job Status
l Elapsed Run Time
l Remaining Run Time
l Throughput
Note: You must verify that all of your ShadowProtect backup jobs have a Job Name. N-central will be unable to monitor StorageCraft ShadowProtect backup jobs if they do not have unique identifying names.
- 440 - N-central 10.0 Services Reference Manual
Service Type WMI
Instances on a 100 Device
Supported StorageCraft ShadowProtect 4.1 to 5.1 Systems/Applicatio ns
Device Class Server - Windows, Workstations - Windows, Laptop - Windows
Monitored By Agent
Backup Job The identifying name of the ShadowProtect backup job to be monitored.
Scanning schedule 1. Based on your requirements for monitoring ShadowProtect backup jobs, select either Once a Day or Daily Interval.
2. If you selected Once a Day, configure the following:
a. Time - to identify when you would like to scan the ShadowProtect backup jobs.
b. Repeat Weekly on Days - to identify the days of the week on which backup jobs will be scanned. All days of the week are selected by default.
c. Repeat Monthly on Days - to identify the numeric dates of the month on which backup jobs will be scanned.
3. If you selected Daily Interval, configure the following:
a. Start Hour and End Hour - to identify the period during which you would like to scan the ShadowProtect backup jobs.
b. Scan Interval in Minutes - to determine the time (in minutes) between each scan.
c. Repeat Weekly on Days - to identify the days of the week on which backup jobs will be scanned. All days of the week are selected by default.
- 441 - N-central 10.0 Services Reference Manual
Status Detail Description
Job Status The numeric value indicating the status of the most recent ShadowProtect backup job as one of the following:
l 0 = Normal
l 1 = Warning
l 2 = Failed
Job Status A brief description indicating the status of the most recent ShadowProtect backup job. Description These are mapped to the Job Status values as follows:
l Normal = 3, 4, 9, and 10
l Warning = 1, 2, 5, 6, 11, 12 and 13
l Failed = 7 and 8
The description values are mapped as follows:
1. Initialized, but not saved or executed. 2. Initialized. Created, saved, and ready to execute. 3. Queued, scheduled, and waiting to be executed. 4. Running. 5. Aborting. Canceled but is still running. 6. Aborted, canceled, and has finished processing. 7. Failed. Executed, but failed, and will not run next time 8. Failed. Queued, executed, failed, but will run next time 9. Completed. Executed and finished successfully. 10. Completed. Queue executed, finished successfully, and will run next time. 11. Deleted. Deleted, but has external locks. 12. Expired. 13. Disabled.
Elapsed Run The amount of time (in seconds) that it took to complete the most recent ShadowProtect Time (sec) backup job.
Remaining Run The amount of time (in seconds) remaining for the most recent ShadowProtect backup Time (sec) job to be completed.
- 442 - N-central 10.0 Services Reference Manual
Status Detail Description
Throughput The average speed at which data was transmitted (measured in kilobytes per second) (KBytes/Secon during the most recent ShadowProtect backup job. d)
Job Start Time The time at which the most recent ShadowProtect backup job was started.
Last Backup The date and time at which the most recent ShadowProtect backup activity took place. Activity Date
Last Script The date and time at which the ShadowProtect.vbs script was run most recently. Execution Date
S.M.A.R.T. Status Service The S.M.A.R.T. Status service monitors the S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) monitoring system on computer drives.
Service Type WMI
Instances on a Device 100
Supported Any WMI-enabled Server - Windows or workstation Systems/Applications with S.M.A.R.T. installed.
Device Class Laptop - Windows, Server - Windows, Workstation - Windows
Monitored By Local Agent
Scan Interval 120 minutes
Disk Name The Instance Name of the disk to be monitored. The Instance Name is obtained from WMI under the namespace rootwmi under the class MSStorageDriver_ FailurePredictStatus.
- 443 - N-central 10.0 Services Reference Manual
Properties Queried and Calculations Performed
Namespace root\wmi
WMI Class MSStorageDriver_FailurePredictStatus
WMI Property 0 CurrentDiskQueueLength
WMI Property 1 AvgDiskQueueLength
Status Details Failure Predicted - Indicates whether or not imminent failure of the drive is predicted as either True or False.
Reason Code - Indicates the reason for the predicted failure mapped as follows:
l 1 = Raw Read Error Rate
l 2 = Throughput Performance
l 3 = Spin Up Time
l 4 = Start/Stop Count
l 5 = Reallocated Sector Count
l 6 = Read Channel Margin
l 7 = Seek Error Rate
l 8 = Seek Time Performance
l 9 = Power On Hours
l 10 = Spin Retry Count
l 11 = Calibration Retry Count
l 12 = Power Cycle Count
l 13 = Soft Read Error Rate
l 170 = Available Reserved Space
l 171 = SSD Program Fail Count
l 172 = SSD Erase Fail Count
l 174 = Unexpected Power Loss Count
l 175 = Power Loss Protection Failure
l 177 = Wear Range Delta
l 179 = Used Reserved Block Count Total
l 180 = Unused Reserved Block Count Total
l 181 = Program Fail Count Total or Non-4K Aligned Access Count
l 182 = Erase Fail Count
l 183 = SATA Downshift Error Count or Runtime Bad Block
l 184 = End-to-End error/IOEDC
l 185 = Head Stability
l 186 = Induced Op-Vibration Detection
l 187 = Reported Uncorrectable Errors
l 188 = Command Timeout
l 189 = High Fly Writes
- 444 - N-central 10.0 Services Reference Manual
l 190 = Airflow Temperature (WDC) resp. Airflow Temperature Celsius (HP)
l 191 = G-sense Error Rate
l 192 = Power-off Retract Count
l 193 = Load Cycle Count
l 194 = Temperature
l 196 = Reallocation Event Count
l 197 = Current Pending Sector Count
l 198 = Off-line Scan Uncorrectable Sector Count
l 199 = Ultra DMA CRC Error Count
l 201 = Soft Read Error Rate
l 202 = Data Address Mark Errors
l 203 = Run Out Cancel
l 204 = Soft ECC Correction
l 205 = Thermal Asperity Rate (TAR)
l 206 = Flying Height
l 207 = Spin High Current
l 208 = Spin Buzz
l 209 = Offline Seek Performance
l 210 = Vibration During Write (Maxtor)
l 211 = Vibration During Write
l 212 = Shock During Write
l 220 = Disk Shift
l 221 = G-Sense Error Rate
l 222 = Loaded Hours
l 223 = Load/Unload Retry Count
l 224 = Load Friction
l 225 = Load/Unload Cycle Count
l 226 = Load 'In'-time
l 227 = Torque Amplification Count
l 228 = Power-Off Retract Cycle
l 230 = GMR Head Amplitude or Drive Life Protection Status
l 231 = Temperature or SSD Life Left
l 232 = Endurance Remaining or Available Reserved Space
l 233 = Power-On Hours or Media Wearout Indicator
l 234 = Average erase count AND Maximum Erase Count
l 235 = Good Block Count AND System(Free) Block Count
l 240 = Head Flying Hours or Transfer Error Rate (Fujitsu)
l 241 = Total LBAs Written
l 242 = Total LBAs Read
l 249 = NAND_Writes_1GiB
l 250 = Read Error Retry Rate
l 254 = Free Fall Protection
Note: Failure codes are vendor-specific and may differ from the list above. For more information, refer to http://en.wikipedia.org/wiki/S.M.A.R.T.
- 445 - N-central 10.0 Services Reference Manual
SMTP Service The Simple Mail Transfer Protocol (SMTP) test monitors the status of the SMTP process on a network device. SMTP is the standard Internet host-to-host email transport protocol. Typically, you use SMTP to send your email to a POP3 server, from where the recipient retrieves the message.
N-central can determine the up or down status of the SMTP service. The SMTP service does not use the Warning state. N-central averages the availability of the SMTP service over the scan interval. It compares the availability of the SMTP service to the threshold to determine the status.
Service TCP Type
Instances 1 on a Device
Device Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Class Windows, Server - Windows, and Workstation - Windows
Monitored Windows Probe, Central Server By
Scan 15 minutes Interval
Timeout The time (in seconds) that the N-central server waits before considering the test a failure. The Value default is 30 seconds.
Port 25 Number
Validation The response you expect to receive from the port that is being queried. If the validation string that String you specify is not returned by the port being queried, the service will transition to a Failed state. The default validation string is 220.
- 446 - N-central 10.0 Services Reference Manual
Status Details
Status Description Detail
SMTP N-central determines whether the SMTP service is up or down. The SMTP service does not use the Service Warning state. N-central averages the availability of the SMTP service over the scan interval and Availability compares the availability of the SMTP service to the threshold to determine the status.
Round The time (in milliseconds) for a request to be sent and received. Trip Time (ms)
DNS The threshold that determines whether the device name can be resolved. Resolution If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings. If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
SMTP Queues Service The SMTP Queues service monitors the performance of the SMTP Server based on metrics obtained from the following properties:
l the remote queue length,
l the local queue length,
l the current inbound connections,
l the current outbound connections.
Service Type WMI
Instances on a Device 1
Supported Any WMI-enabled Server - Windows that has an SMTP service running which reports Systems/Applications data through the Win32_PerfRawData_SMTPServer class; for example, Microsoft Exchange
Device Class Server - Windows
Monitored By Windows Probes
Scan Interval 15 minutes
SMTP Service Name An instance of the class Win32_PerfRawData_SMTPSvc_SMTPServe, for example, SMTP1.
- 447 - N-central 10.0 Services Reference Manual
Properties Queried and Calculations Performed (WMI only)
Namespace root\cimv2
WMI Class Win32_PerfRawData_SMTPSvc_SMTPServer
WMI Property 0 RemoteQueueLength
WMI Property 1 LocalQueueLength
WMI Property 2 InboundConnectionsCurrent
WMI Property 3 OutboundConnectionsCurrent
Configuring SMTP Service Name
Use the Web Based Enterprise Management (wbemtest) tool in Windows to get the service name to enter in the setup.
To configure SMTP Service Name
1. Press the Windows Explorer key + R.
The Run dialog box appears.
2. Specify wbemtest in the Open field, and press Enter.
The Windows Management Instrumentation Tester dialog box appears.
3. Click Connect.
The Connect dialog box appears.
4. In the first field, specify the namespace: \\
5. Click Connect.
The Windows Management Instrumentation Tester dialog box appears, with the namespace you have specified.
6. Click Enum Instances.
The Class Info dialog box appears.
7. In the Enter superclass name field, specify: Win32_PerfRawData_SMTPSvc_SMTPServer.
8. Click OK.
- 448 - N-central 10.0 Services Reference Manual
The Query Results dialog box appears, listing SMTP instances.
9. Enter an instance name from the list exactly as it is displayed, preserving the case and the spaces, in the SMTP Service Name field in the task properties of the All Devices view on the central server.
Status Details
Status Detail Description
Number of messages in the remote queue See Status Detail.
Number of messages in the local queue See Status Detail.
Number of connections currently inbound See Status Detail.
Number of connections currently See Status outbound Detail.
SNMP Service The SNMP service monitors the performance and health of the SNMP agent on a device. SNMP is a widely used network management protocol that is present in a majority of network infrastructures (routers, switches, firewalls, and so on) as well as in different types of computing platforms.
Service Type SNMP
Instances on a 1 Device
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, and Workstation - Windows
Monitored By Windows Probe
Scan Interval 15 minutes
The table SNMPV2-MIB describes the SNMP objects that are queried by the probe.
- 449 - N-central 10.0 Services Reference Manual
SNMPV2-MIB
Object Descriptors Numerical OID
snmpInBadVersions 1.3.6.1.2.1.11.3
snmpInBadCommunityNames 1.3.6.1.2.1.11.4
snmpInBadCommunityUses 1.3.6.1.2.1.11.5
snmpInASNParseErrs 1.3.6.1.2.1.11.6
snmpInTooBigs 1.3.6.1.2.1.11.8
snmpInNoSuchNames 1.3.6.1.2.1.11.9
snmpInBadValues 1.3.6.1.2.1.11.10
snmpInGenErrors 1.3.6.1.2.1.11.12
snmpOutTooBigs 1.3.6.1.2.1.11.20
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
- 450 - N-central 10.0 Services Reference Manual
Metric Descriptio OID/Calculation Name n
Number ^snmpInBadVersions The of SNMP number of message SNMP s with queries version received by error the SNMP agent on the target device that were for an unsupport ed version of SNMP.
Number ^snmpInBadCommunityNames The of wrong number of communi SNMP ty string queries message received by s the SNMP agent on the device that used an incorrect SNMP community string.
- 451 - N-central 10.0 Services Reference Manual
Metric Descriptio OID/Calculation Name n
Number ^snmpInBadCommunityUses The of number of message SNMP s with an messages invalid received by user the SNMP agent on the device which requested an SNMP operation which was not allowed by the SNMP community string in the message.
Number ^snmpInASNParseErrs The of SNMP number of message SNMP s messages unparsed received by the SNMP agent on the device with syntax errors.
- 452 - N-central 10.0 Services Reference Manual
Metric Descriptio OID/Calculation Name n
Number ^sn- The of mpInTooBig+^s- number of message nmpNoSuchName+^snmpBadValue+^snmpGenError+^snmpOutTooBig SNMP s with messages invalid received by status or bits transmitte d from the SNMP agent on the target device, which indicates an error status.
SonicWALL Connections Service The SonicWALL Connections service monitors the number of active connections passing through a SonicWALL firewall.
Service Type SNMP
Instances on a Device 1
Supported Any device that supports the SonicWALL Enterprise MIB Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculations
Metric Name OID/Calculation Description
Active 1.3.6.1.4.1.8741.1.3.1.2.0 The number of active connections currently being managed by Connections the SonicWALL firewall.
SonicWALL CPU Service The SonicWALL CPU service monitors the CPU usage of a SonicWALL firewall.
- 453 - N-central 10.0 Services Reference Manual
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 4
Supported SonicWALL® TZ-Series, PRO-Series, and NSA-Series devices Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculations
Metric OID/Calculations Description Name
CPU Index 1.3.6.1.4.1.8741.1.3.1.3 Monitors the CPU usage of the SonicWALL firewall as a percentage.
SonicWALL Memory Service The SonicWALL Memory service monitors the memory usage of a SonicWALL firewall.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported SonicWALL® TZ-Series, PRO-Series, and NSA-Series devices Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Metric Name OID/Calculation Description
Memory 1.3.6.1.4.1.8741.1.3.1.4.0 Monitors the CPU usage of the SonicWALL firewall as a Usage percentage..
- 454 - N-central 10.0 Services Reference Manual
SQL Server Service The SQL Server service monitors the database files of Microsoft SQL server, including individual database instances and the sum of all of the specified instances of SQL server.
During the monitoring process, the SQL Server service uses the Windows probe to measure Microsoft SQL server's key activities. The results are then displayed on the status dashboard for the service.
Service Type WMI
Instances on a Device 50
Supported Systems/Applications Microsoft SQL Server
Device Class Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows probe
Scan Interval 15 minutes
WMI class name of Database The name of the WMI class of the Database Performance Counter that is to Performance Counter be monitored.
Instance Name The instance name of the class that is specified in the WMI class name of Database Performance Counter. The instance will be monitored for active transactions, log file size (KB), data file size (KB), and the number of transactions occurred per second.
WMI class name of Server The name of the WMI class server general statistics performance counter General Statistics Performance that is to be monitored. Counter
WMI class name of Server Lock The name of the WMI class of the server lock performance counter that is to Performance Counter be monitored.
Instance Name The instance name that is applied to the class names specified in WMI class name of server lock performance counter. The instance will be monitored for the average wait time and number of deadlocks occurred per second.
- 455 - N-central 10.0 Services Reference Manual
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_MSSQLSERVER_SQLServerDatabases
WMI Property 0 ActiveTransactions
WMI Property 1 LogFilesSizeKB
WMI Property 2 DataFilesSizeKB
WMI Property 3 TransactionsPersec
WMI Property 4 Timestamp_Sys100NS
WMI Property 5 Frequency_Sys100NS
Namespace root\cimv2
WMI Class Win32_PerfRawData_MSSQLSERVER_SQLServerGeneralStatistics
WMI Property 0 UserConnections
Namespace root\cimv2
WMI Class Win32_PerfRawData_MSSQLSERVER_SQLServerLocks
WMI Property 0 AverageWaitTimems
WMI Property 1 NumberofDeadlocksPersec
WMI Property 2 Timestamp_Sys100NS
WMI Property 3 Frequency_Sys100NS
Scandetail.3.Recipe (^VarTransactionsPersec * $timebase05) / ^timeelapse04
Scandetail.5.Recipe (^VarAverageWaitTimems * $timebase23) / ^timeelapse22
Scandetail.6.Recipe (^VarNumberofDeadlocksPersec * $timebase23) / ^timeelapse22
- 456 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Active transactions The threshold values that determine the status change of the service.
Log file size (KB)
Data file size (KB)
Transactions/second
Number of user connections
Average waiting time (ms)
Deadlocks/second
SQL Database Information Service The SQL Database Information service monitors information about an SQL database including file sizes and transaction rates.
Service Type WMI
Instances on a Device 15
Supported Sys- Microsoft SQL Server tems/Applications
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Agent
Scan Interval 15 minutes
SQL Server Instance The specific instance of the SQL Server database engine that is running on the tar- get server.
Database Name The name of the SQL database that is being monitored.
- 457 - N-central 10.0 Services Reference Manual
Status Detail Description
Log Files Size (KB) Indicates the current size of the transaction log (in kilobytes) for the data- base that is being monitored.
Transactions per second (Trans- Indicates the number of database operations (transactions) performed per actions/Second) second.
Data Files Size (KB) Indicates the current size of the data file (in kilobytes) for the database that is being monitored.
SQL Memory Manager Service The SQL Memory Manager service monitors various aspects of how an SQL Server uses memory.
Service Type WMI
Instances on a Device 3
Supported Sys- Microsoft SQL Server tems/Applications
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Agent
Scan Interval 15 minutes
SQL Server Instance The specific instance of the SQL Server database engine that is running on the target server.
Status Detail Description
Connections Specifies the total amount of dynamic memory that the server is using for maintaining con- Memory (KB) nections.
Lock Memory (KB) Specifies the total amount of dynamic memory that the server is using for locks.
Optimizer Memory Specifies the total amount of dynamic memory (measured in kilobytes) on the server that is (KB) being used for query optimization.
SQL Cache Specifies the total amount of dynamic memory (measured in kilobytes) that the server is Memory (KB) using for the dynamic SQL plan cache.
Total Server Specifies the amount of memory that the server has committed using the memory manager. Memory (KB)
Memory Grants Specifies the total number of processes that are waiting for a workspace memory grant. Pending
- 458 - N-central 10.0 Services Reference Manual
SQL Server Buffer Manager Service The SQL Server Buffer Manager service monitors how an SQL Server uses memory to store data pages, the physical Input/Output as SQL Server reads and writes database pages, and the buffer cache by using fast non-volatile storage such as solid-state drives (SSD).
Service Type WMI
Instances on a Device 15
Supported Sys- Microsoft SQL Server tems/Applications
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Agent
Scan Interval 15 minutes
SQL Server Instance The specific instance of the SQL Server database engine that is running on the target server.
Status Description Detail
Buffer Indicates the percentage of pages found in the buffer cache without having to be read from a disk. Cache Hit Ratio
Page Reads Indicates the number of physical database page reads that are issued per second. Per Second
Page Indicates the number of physical database page writes that are issued per second. Writes Per Second
Page Life Indicates the number of seconds that a page will stay in the buffer pool without references. Expectancy (sec)
Lazy Indicates the number of buffers written per second by the buffer manager's lazy writer. The lazy Writes Per writer is a system process that flushes out batches of dirty, aged buffers (buffers that contain Second changes that must be written back to disk before the buffer can be reused for a different page) and makes them available to user processes. The lazy writer eliminates the need to perform fre- quent checkpoints in order to create available buffers.
- 459 - N-central 10.0 Services Reference Manual
SQL Server Locks Service The SQL Server Locks service monitors how an SQL Server manages locks on individual resource types. Locks are maintained on SQL Server resources (for example, rows read or modified during a transaction) to prevent concurrent use of the resources by different transactions.
Service Type WMI
Instances on a Device 15
Supported Sys- Microsoft SQL Server tems/Applications
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Agent
Scan Interval 15 minutes
SQL Server Instance The specific instance of the SQL Server database engine that is running on the target server.
Resource Name The name of the lock resource for which to obtain statistics.
Status Detail Description
Lock Waits per Second Specifies the number of lock requests per second that required originators to wait.
Average Wait Time in Mil- Specifies the average amount of wait time (measured in milliseconds) for each lock liseconds request that resulted in a wait.
Lock Timeouts per Specifies the number of lock requests per second that timed out (including requests Second for NOWAIT locks).
Number of Deadlocks Specifies the number of lock requests per second that resulted in a deadlock. per Second
SQL TCP Availability Service The SQL TCP Availability service monitors the availability of the port on which the MS SQL Server application runs. The availability of the port, which is determined by the service testing the port's connectivity, indicates that the MS SQL Server application is running. This service also measures the domain name system (DNS) resolution and the round trip time of the initial connection request and response. The availability results of the TCP service are then reflected on the status dashboard for the SQL TCP Availability service.
- 460 - N-central 10.0 Services Reference Manual
Service Type WMI
Instances on a Device 15
Supported Sys- Microsoft SQL Server tems/Applications
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Probe
Scan Interval 15 minutes
Port Number The port that will be used to monitor the SQL server.
Send Command A predefined set of characters specific to the TCP service. The string is transmitted upon String connection to the host and requests the response from the TCP service.
Validating String A regular expression that determines whether the responses sent by the queried device is valid.
Status Description Detail
DNS The threshold that determines whether the device name can be resolved. Resolution If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
Generic The threshold that determines the availability of the port. SQL Server Availability
Round Trip The time (in milliseconds) for a request to be sent and received. Time (ms)
SQL Transaction Information Service The SQL Transaction Information service monitors the transaction performance of an SQL server.
- 461 - N-central 10.0 Services Reference Manual
Service Type WMI
Instances on a Device 15
Supported Sys- Microsoft SQL Server tems/Applications
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows Agent
Scan Interval 15 minutes
Status Detail Description
Latch Waits Per Specifies the number of latch requests (per second) that could not be granted imme- Second diately.
Full Scans Per Second Specifies the number of full scans performed (per second) on base tables or indexes.
User Connections Specifies the number of users that are currently connected to the SQL server.
Logins Per Second Specifies the total number of login attempts that were started (per second).
SSH Service N-central can monitor the availability of a Secure Shell (SSH) daemon on a network device. SSH is a shell program for logging into and executing commands on a remote computer. It provides strong authentication and secure communications over a vulnerable connection. It also provides a UNIX shell augmented with a range of cryptographic options.
N-central can determine the up or down status of the SSH service. The SSH service does not use the Warning state. N-central averages the availability of the SSH service over the scan interval. It compares the availability of the SSH service to the threshold to determine the status.
Service TCP Type
Instances 1 on a Device
Device Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Class Windows, Server - Windows, and Workstation - Windows
Monitored Windows probe, Central Server By
- 462 - N-central 10.0 Services Reference Manual
Scan 5 minutes Interval
Timeout The time (in seconds) that the N-central server waits before considering the test a failure. The Value default is 30 seconds.
Port 22 Number
Validation The response you expect to receive from the port that is being queried. If the validation string that String you specify is not returned by the port being queried, the service will transition to a Failed state. The default validation string is SSH.
Status Details
Status Description Detail
SSH N-central determines whether the SSH service is up or down. The SSH service does not use the Service Warning state. N-central averages the availability of the SSH service over the scan interval and Availability compares the availability of the SSH service to the threshold to determine the status.
Round The time (in milliseconds) for a request to be sent and received. Trip Time (ms)
DNS The threshold that determines whether the device name can be resolved. Resolution If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings. If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
Stack Status (Cisco StackWise) Service The Stack Status (Cisco StackWise) service monitors the status of the global stack for a specified Cisco StackWise switch.
Service Type SNMP
Instances on a Device 1
Supported Most Cisco switches/routers running IOS. Systems/Applications
Device Class Router/Switch
Monitored By Windows Probe
Scan Interval 5 minutes
- 463 - N-central 10.0 Services Reference Manual
Object Numerical OID Descriptors
$Max_Switches 1.3.6.1.4.1.9.9.500.1.1.1
$Max_SwitchPriority 1.3.6.1.4.1.9.9.500.1.1.2
$RingRedundancy 1.3.6.1.4.1.9.9.500.1.1.3
Status Detail Description
Maximum Number of The maximum number of switches that can be configured on this stack. Switches
Maximum Configured The maximum configurable priority for a switch in this stack. Switch Priority
Stackring Redundancy Indicates when the stack ports are connected in such a manner as to form a redundant ring.
Switch Status (Cisco StackWise) Service The Switch Status (Cisco StackWise) service monitors the status of individual Cisco StackWise switches.
Service Type SNMP
Instances on a Device 1
Supported Most Cisco switches/routers running IOS. Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
Switch Number The number of the switch in the stack. This should be a value between 1 and 9 depending on the type of switches.
- 464 - N-central 10.0 Services Reference Manual
Object Descriptors Numerical OID
$StackNumAtReload 1.3.6.1.4.1.9.9.500.1.2.1.1.2
$SwitchStackRole 1.3.6.1.4.1.9.9.500.1.2.1.1.3
$SwitchStatus 1.3.6.1.4.1.9.9.500.1.2.1.1.6
$SwitchStackPriority 1.3.6.1.4.1.9.9.500.1.2.1.1.4
$SwitchMAC 1.3.6.1.4.1.9.9.500.1.2.1.1.7
$SwitchSoftwareImage 1.3.6.1.4.1.9.9.500.1.2.1.1.8
Status Detail Description
Switch Stack The stack number to be assigned to the switch the next time that it is reloaded. Number at Next Reload
Switch Stack Identifies whether the switch is the stack master or a regular member of the stack. Role
Switch Stack Identifies the priority value of the switch which is used to determine which stack member Priority becomes the new stack master when the current stack master or switch stack resets.
Switch Status Provides a description of the current status of the specified switch. Description
Switch Status The status of the switch is mapped as follows: Alerting l Warning = 1 to 3
l Normal = 4
l Failed = 5 to 255
Switch MAC The MAC address of the switch being monitored. Address
Switch The software image type that is currently running on the switch. Software Image
System Battery Status (Dell iDRAC) Service The System Battery Status (Dell iDRAC) service monitors the status of a system board CMOS battery on a Dell PowerEdge server using the embedded integrated Dell Remote Access Controller (iDRAC).
- 465 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a 100 Device
Supported Dell PowerEdge servers with integrated Dell Remote Access Controller (iDRAC) Systems/Applicatio ns
Device Class for Servers - Management Interface CPU (SNMP)
Monitored By Windows Agent
Scan Interval 15 minutes
SNMP Value Type or select the name of the battery to be monitored. For a list of batteries, query the device with the .1.3.6.1.4.1.674.10892.5.4.600.50.1.7 SNMP OID.
Status Object Numerical OID Description Detail Descriptors
Chas $ChassisIn 1.3.6.1.4.1.674.10892.5.4.600.50. Indicates the index of the system sis dex 1.1 chassis that contains the battery as an Inde integer value between 1 and 128. x
Statu $Status 1.3.6.1.4.1.674.10892.5.4.600.50. Indicates the current status of the s 1.5 battery mapped as follows:
1 - other,
2 - unknown,
3 - ok,
4 - nonCritical,
5 - critical, and,
6 - nonRecoverable.
- 466 - N-central 10.0 Services Reference Manual
System Change Service The System Change service monitors the hardware components that have been discovered on a Windows device. Once these components have been discovered, N-central creates a snapshot of this asset information. This snapshot is then used by the System Change service as a baseline to monitor any changes that occur in the assets of the device. The service scans the device for changes every day at 9:00 a.m. For example, the removal of a network adapter at 1:00 p.m. is reflected in the state of the service at 9:00 a.m. the next day. This change is also reflected in the updated snapshot, which can then be reset as the new baseline.
The System Change service requires the following configurations:
l The service can only be monitored on discovered assets, not on devices that have been manually created.
l The service needs to have a recurring Windows Asset Discovery task targeted against the IP address of the target device.
l The data presented in the service is collected by a Windows probe. You must either install a Win- dows probe at the customer's
Service Type System
Instances on a Device 1
Supported Systems/Applications Microsoft Windows®
Device Class Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Central Server Asset
Scan Interval One day (1,440 minutes)
- 467 - N-central 10.0 Services Reference Manual
Status Details
Status Detail Description
Change in number of network The change in the number of assets. The number can reflect any addition or adapters removal of assets. Information about the changes that have occurred in the asset details. Change in network adapter Information about the changes that have occurred to the asset. details The Stale state is displayed when a device's MAC address changes due to Change in number of CPUs changes in its network adapter.
Change in CPU details
Change in number of media access devices
Change in media access device details
Change in number of video controllers
Change in video controller details
Change in size of RAM
Change in OS
System Check-In Service The System Check-In service monitors roaming devices, such as laptops, to ensure their presence on the network. Their presence is determined by the frequency at which they connect to the network. For an accurate state to be determined, the device must remain connected to the network for the specified scan interval time.
When System Check-in is first added to a device, the service will be in a Misconfigured state until the device's agent first makes contact with the central server.
During the monitoring process, the central server queries the time of the most recent connection of a device's agent to the network. This is compared to the current time and the resulting difference is then compared to the specified threshold values so that it can be represented by the appropriate state on the status dashboard for the service.
Example: If the time difference between the previous and current connection is within 10 days, the service state will display Normal; between 10 and 15 days, Warning; and over 15 days, Failed.
- 468 - N-central 10.0 Services Reference Manual
Service Type Central Server Asset
Instances on a 1 Device
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Central Server Asset
Scan Interval 15 minutes
Status Details
Status Description Detail
System The threshold that compares the time difference between the current time and the most recent Check-In connection to the specified threshold values.
System Replacement Service The System Replacement service monitors a device's expected replacement date, which can be specified when adding or editing the device. This service allows you to better monitor the life cycle of a device and avoid issues, such as excessive maintenance and support costs, and the inadequate total cost of ownership (TCO) data for purchase planning.
Service Central Server Asset Type
Instances 1 on a Device
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored Central Server Asset By
Scan One day (1,440 minutes) Interval
Status Details
Status Detail Description
System The threshold that determines when the device is to be Replacement replaced.
- 469 - N-central 10.0 Services Reference Manual
System Warranty Service The System Warranty service monitors a device's expected warranty expiry date, which can be specified when adding or editing the device. This service allows you to avoid issues, such as leasing penalties, additional buying costs, and the inadequate total cost of ownership (TCO) data for purchase planning.
Service Central Server Asset Type
Instances 1 on a Device
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored Central Server Asset By
Scan One day (1,440 minutes) Interval
Status Details
Status Details Description
System The threshold for expiry of the Warranty warranty.
Telnet Service The Terminal Network Protocol (Telnet) test checks the status of the telnet port on the network device. The Telnet protocol is designed for terminal-oriented remote login sessions.
N-central can determine the up or down status of the Telnet service. The Telnet service does not use the Warning state. N-central averages the availability of the Telnet service over the scan interval. It compares the availability of the Telnet service to the threshold to determine the status.
Service TCP Type
Instances 1 on a Device
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored Windows probe, Central Server By
- 470 - N-central 10.0 Services Reference Manual
Scan 5 minutes Interval
Timeout The time (in seconds) that the N-central server waits before considering the test a failure. The Value default is 30 seconds.
Port 23 Number
Status Details
Status Description Detail
Telnet N-central determines whether the Telnet service is up or down. The Telnet service does not use Service the Warning state. N-central averages the availability of the Telnet service over the scan interval Availability and compares the availability of the Telnet service to the threshold to determine the status.
Round The time (in milliseconds) for a request to be sent and received. Trip Time (ms)
DNS The threshold that determines whether the device name can be resolved. Resolution If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings. If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
Temperature Probe (Dell iDRAC) Service The Temperature Probe (Dell iDRAC) service monitors the status of a temperature sensor on a Dell PowerEdge server using the embedded integrated Dell Remote Access Controller (iDRAC).
Service Type SNMP
Instances on a Device 100
Supported Dell PowerEdge servers with integrated Dell Remote Access Controller Systems/Applications (iDRAC)
Device Class for CPU (SNMP) Servers - Management Interface
- 471 - N-central 10.0 Services Reference Manual
Monitored By Windows Agent
Scan Interval 5 minutes
SNMP Value Type or select the name of the temperature sensor to be monitored.
- 472 - N-central 10.0 Services Reference Manual
Status Object Numerical OID Description Detail Descriptors
Locati $LocationNa 1.3.6.1.4.1.674.10892.5.4.700.20. Indicates the location name of the on me 1.8 temperature probe. Name
Settin $Setting 1.3.6.1.4.1.674.10892.5.4.700.20. Indicates the state settings of the gs 1.4 temperature probe mapped as follows:
1 - unknown
2 - enabled
4 - notReady
6 - enabledAndNotReady
Status $Status 1.3.6.1.4.1.674.10892.5.4.700.20. Indicates the current status of the 1.5 temperature sensor mapped as follows:
1 - other
2 - unknown
3 - ok
4 - nonCriticalUpper
5 - criticalUpper
6 - nonRecoverableUpper
7 - nonCriticalLower
8 - criticalLower
9 - nonRecoverableLower
10 - failed
Temperature Status (Dell iDRAC) Service The Temperature Status (Dell iDRAC) service monitors the temperature of a Dell PowerEdge server using the embedded integrated Dell Remote Access Controller (iDRAC).
- 473 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 100
Supported Dell PowerEdge servers with integrated Dell Remote Access Controller Systems/Applications (iDRAC)
Device Class for CPU (SNMP) Servers - Management Interface
Monitored By Windows Agent
Scan Interval 15 minutes
SNMP Index Type or select the index of the chassis for which the temperature will be monitored.
Status Object Descriptors Numerical OID Description Detail
Chassis $ChassisIndex 1.3.6.1.4.1.674.10892.5.4.200.10.1. Indicates the index of Index 1 the system chassis as an integer value between 1 and 128.
Temperat $TemperatureCombin 1.3.6.1.4.1.674.10892.5.4.200.10.1. Indicates the ure ed 63 combined status of all temperature statistics objects of this system mapped as follows:
1 - other,
2 - unknown,
3 - ok,
4 - nonCritical,
5 - critical, and,
6 - nonRecoverable.
- 474 - N-central 10.0 Services Reference Manual
Temperature Status (Cisco) Service The Temperature Status (Cisco) service monitors the temperature of the specified Cisco device.
Service Type SNMP
Instances on a Device 1
Supported Most Cisco switches/routers running IOS. Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
Temperature Sensor The name of the temperature sensor to be monitored.
Object Numerical OID Descriptors
$Temperature 1.3.6.1.4.1.9.9.13.1.3.1.3
$TempSensorStatus 1.3.6.1.4.1.9.9.13.1.3.1.6
$HighTemp 1.3.6.1.4.1.9.9.13.1.3.1.4
Status Detail Description
Temperature (°C) The current temperature reading in degrees Celsius.
Maximum Allowable Temperature The maximum allowable operating temperature of the device in degrees (°C) Celsius.
Temperature (°F) The current temperature reading in degrees Farenheit.
Maximum Allowable Temperature The maximum allowable operating temperature of the device in degrees (°F) Farenheit.
- 475 - N-central 10.0 Services Reference Manual
Status Detail Description
Temperature Sensor Status The temperature sensor status is mapped as follows:
l Normal = 1
l Warning = 2
l Failed = 3, 4, 5, or 6
Temperature Sensor Status Describes the status of the temperature sensor: Description l 1 = Normal
l 2 = Warning
l 3 = Critical
l 4 = Shutdown
l 5 = Not Present
l 6 = Not Functioning
Temperature Status (EqualLogic) Service The Temperature Status (EqualLogic) service monitors the temperature of a Model PS6100 Dell EqualLogic SAN running v6.0.2 firmware.
Service Type SNMP
Instances on a Device 1
Supported Model PS6100 Dell EqualLogic SAN running v6.0.2 firmware Systems/Applications
Device Class Server - Generic, Server - Windows
Monitored By Windows Agent
Scan Interval 5 minutes
Temperature Sensor Type the name of the temperature sensor to be monitored. For a list of temperature sensors, query the SAN with the .1.3.6.1.4.1.12740.2.1.6.1.2 SNMP OID.
Object Numerical OID Descriptors
$Temperature 1.3.6.1.4.1.12740.2.1.6.1.3
$SensorState 1.3.6.1.4.1.12740.2.1.6.1.4
- 476 - N-central 10.0 Services Reference Manual
Status Detail Description
Temperature (°C) The current temperature reading in degrees Celsius.
Sensor State The temperature sensor status is mapped as follows:
l Normal = 1
l Warning = 2, 0
l Failed = 3
Sensor State Describes the status of the temperature sensor: Description l 0 = Unknown
l 1 = Normal
l 2 = Warning
l 3 = Critical
Temperature Status (Fujitsu) Service The Power Supply (Fujitsu) service monitors the status of a temperature sensor in a Fujitsu device.
Service Type SNMP
Instances on a Device 100
Supported Fujitsu servers running the Fujitsu ServerView agent. Systems/Applications
Device Class for CPU Servers - Generic or Servers - Windows (SNMP)
Monitored By Windows Agent
Power Supply Type the name of the temperature sensor to be monitored. For a list of temperature sensors, query the device with the .1.3.6.1.4.1.231.2.10.2.2.10.5.1.1.4 SNMP OID.
Scanning The scan interval can be configured according to either a Once a Day or Daily Interval schedule.
- 477 - N-central 10.0 Services Reference Manual
Status Description Numerical OID Object Descriptors Detail
Status 1.3.6.1.4.1.231.2.10.2.2.10.5.1. $Status Describes the current status 1.5 of the temperature sensor that is being monitored with values mapped as follows:
Normal: 3, 8
Warning: 6, 9
Failed: 1, 2, 4, 5, 7
1. Unknown 2. Not Available 3. OK 4. Sensor Failed 5. Failed 6. Temperature Warn- ing – Too Hot 7. Temperature – Crit- ical 8. Temperature – Normal 9. Temperature Warn- ing
Current 1.3.6.1.4.1.231.2.10.2.2.10.5.1. $CurrentTemperat Indicates the current Temperat 1.6 ure temperature measured by ure the sensor (in degrees Celsius) that is being monitored.
Warning 1.3.6.1.4.1.231.2.10.2.2.10.5.1. $WarningLevel Indicates the temperature Level 1.7 measured by the sensor (in degrees Celsius) that will trigger a warning.
Critical 1.3.6.1.4.1.231.2.10.2.2.10.5.1. $CriticalLevel Indicates the temperature Level 1.8 measured by the sensor (in degrees Celsius) that will trigger a critical warning.
Critical 1.3.6.1.4.1.231.2.10.2.2.10.5.1. $CriticalReaction Describes the reaction that Reaction 1.9 will result when the Critical Level temperature is reached.
- 478 - N-central 10.0 Services Reference Manual
Temperature Status (VMware) Service The Temperature Status (VMware) service monitors the status and temperature readings of temperature sensors on ESXi servers.
Note: If your ESX/ESXi server is operating on either Dell or HP hardware, it is strongly recommended that you install the Dell or HP Offline Bundle before the Windows Probe discovers the ESX/ESXi server. For instructions on installing the Dell or HP Offline Bundle, refer to the following articles in the N-central online knowledge base:
l KBA10019: Installing the HP Offline Bundle on ESX/ESXi Servers
l KBA10020: Installing the Dell Offline Bundle on ESX/ESXi Servers
Service Type ESXi
Instances on a Device 100
Supported ESX or ESXi 4.x, 5.x and later Systems/Applications Note: ESXi 3.5 is not supported.
Device Class Server - ESXi
Monitored By Windows Probes
Scan Interval 5 minutes
Temperature Sensor Name The unique identifier of the temperature sensor being monitored.
Note: This service cannot use N-central’s Self-Healing feature.
To access information about the temperature sensors on your ESXi server, use a browser to access the following URL:
https://
Example: https://192.168.101.207/mob/?moid=ha- host&doPath=runtime.healthSystemRuntime.systemHealthInfo.numericSensorInfo
- 479 - N-central 10.0 Services Reference Manual
Metric Name Description
State The temperature sensor status is mapped as follows:
Normal: 1
Warning: 1, 2, 4
Failed: 5, 6
State Description Describes the status of the temperature sensor:
Other
Unknown
OK
Non-Critical
Critical or Non-recoverable
Temperature (°C) The current temperature reading in degrees Celsius.
Temperature (°F) The current temperature reading in degrees Farenheit.
Terminal Server Service The Terminal Server service monitors the availability of the Microsoft Windows Terminal Services, which allows remote login to a server using the Microsoft Remote Desktop client.
During the monitoring process, the Terminal Server service uses the Windows probe to track the terminal server's key activities. The results are then displayed on the status dashboard for the service.
Note: When adding your terminal server as a device, ensure that you select Server - Windows as the Class. The Operating System must be a server.
Service Type WMI
Instances on a Device 1
Supported Microsoft Windows® Terminal Services Systems/Applications
Device Class Server - Windows
- 480 - N-central 10.0 Services Reference Manual
Monitored By Windows probe, Central Server
Scan Interval 15 minutes
WMI Class The default value for WMI Class is Win32_PerfRawData_TermService_ TerminalServices which should be used for most Server - Windowss. For servers using Windows 2008 or Windows Vista SP1, however, the WMI Class should be set to Win32_PerfRawData_LocalSessionManager_TerminalServices.
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_PerfRawData_TermService_TerminalServices
WMI Property 0 ActiveSessions
WMI Property 1 InactiveSessions
WMI Property 2 TotalSessions
Status Details
Threshold Description
Active sessions Counts the sessions that are currently connected and have users logged on.
Inactive Counts the sessions that are:
sessions l Waiting for the initial connection;
l Both, connected and waiting for users to log on; or
l Both, disconnected and on which a user is logged on.
For more information, refer to the table below.
Total sessions The sum of the active and inactive sessions.
- 481 - N-central 10.0 Services Reference Manual
Examples of Active and Inactive Session Counts
Example Session Count
Terminal Server Shutting Down Active Session Count = 0 Inactive Session Count = 0 Total Sessions = 0
Terminal Server Freshly Started Active Session Count = 0 Inactive Session Count = 1 Total Sessions = 1
Session Connected But Not Logged On Active Session Count = 0 Inactive Session Count = 2 Total Sessions = 2
Session Connected AND Logged On Active Session Count = 1 Inactive Session Count = 1 Total Sessions = 2
Session Disconnected BUT Logged On Active Session Count = 0 Inactive Session Count = 2 Total Sessions = 2
Traffic Service The Traffic service uses the Windows Probe to monitor the amount of data transmitted to and from the full duplex network interfaces on a device. Upload and download speeds can be monitored independently allowing for accurate reporting on network interfaces that have a download speed that is different from the upload speed.
To monitor the Traffic service on a device
1. Configure SNMP on the device (for more information, review the manufacturer's doc- umentation).
2. Login to N-central.
3. Click the All Devices view in the navigation pane.
- 482 - N-central 10.0 Services Reference Manual
4. Select the appropriate tab for the type of device that you would like to edit from one of the following: Network Devices, Mobile Devices, or, SaaS Devices.
5. Click the Name of the device on which you would like to monitor the Traffic service.
6. If the Use SNMP option has not already been enabled on the Properties tab of the device, select Use SNMP.
Note: You will need to click Save to enable SNMP for the device.
7. On the Status tab, click Add,
8. Type 1 for the number of instances of the Traffic service that you would like to associate to the device.
9. Click OK.
10. Click the Traffic service.
11. Click the Service Details tab.
12. In Interfaces to Monitor, select the NICs/ports that you would like to monitor.
Tip: Use CTRL + SHIFT to select multiple NICs/ports.
13. Click OK.
Service Type SNMP
Instances on a Device 400
Device Class Server - Generic, Other, Printer, Scanner/Camera, Switch/Router, and Server - Windows
Monitored By Windows Probe
Interfaces to Monitor Select the name or SNMP index of the NICs or ports that you would like to monitor. Tip: Hold down CTRL or SHIFT to select multiple NICs or ports.
Scan Interval 15 minutes
Upload Speed (MBits/sec) Enter the upload speed of the interface, in MBits/sec
Download Speed Enter the download speed of the interface, in MBits/sec (MBits/sec)
- 483 - N-central 10.0 Services Reference Manual
OIDs used by the Traffic Service
Object Numerical OID Descriptors
sysUpTime 1.3.6.1.2.1.1.3
ifDescr 1.3.6.1.2.1.2.2.1.2
ifSpeed 1.3.6.1.2.1.2.2.1.5
ifInOctets 1.3.6.1.2.1.2.2.1.10
ifOutOctets 1.3.6.1.2.1.2.2.1.16
OID/Calculations
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation
Total Traffic Throughput ((^ifInOctets+ ^ifOutOctets)*8000) /^SysUpTime
Incoming Traffic Throughput (^ifInOctets*800)/(^sysUpTime)
Outgoing Traffic Throughput (^ifOutOctets*800)/(^sysUpTime)
Total Bandwidth Utilization ((^ifInOctets+ ^ifOutOctets)*8000)/ (^SysUpTime*$downbitspersecspeed*10485 76)
Outgoing Bandwidth Utilization (^ifOutOctets*8000)/ (^SysUpTime*$downbitspersecspeed*10485 76)
Incoming Bandwidth Utilization (^ifInOctets*8000)/ (^SysUpTime*$downbitspersecspeed*10485 76)
- 484 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation
Incoming Traffic ^ifInOctets
Outgoing Traffic ^ifOutOctets
Total Traffic ^ifInOctets + ^ifOutOctets
Detected Port Speed ^ifSpeed
Untangle – Firewall Service The Untangle - Firewall service monitors the number of blocked requests and allowed requests received by the Untangle device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type Firewall
Instances on a Device 1
Supported Any Untangle UTM device Systems/Applications
Device Class Other, Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation Description
Blocked ^1.3.6.1.4.1.30054.2.0.19.7 The number of connection requests blocked by the Untangle Requests device.
Allowed ^1.3.6.1.4.1.30054.2.0.19.8 The number of connection requests allows by the Untangle Requests device.
Untangle – IPS Service The Untangle - IPS service monitors the number of scans, detected intrusions, and blocked intrusions received by the Untangle device.
Note: This service cannot use N-central’s Self-Healing feature.
- 485 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Any Untangle UTM device Systems/Applications
Device Class Other, Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation Description
Scans ^1.3.6.1.4.1.30054.5.0.19.7 The number of scans performed by the Untangle device.
Detected Intru- ^1.3.6.1.4.1.30054.5.0.19.8 The number of intrusions detected by the Untangle device. sions
Blocked Intru- ^1.3.6.1.4.1.30054.5.0.19.9 The number of intrusions that were blocked by the sions Untangle device.
Untangle – Phish Service The Untangle - Phish service monitors the number of scans, blocked phishing attempts, passed phishing attempts, and removed phishing attempts detected by the Untangle device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Any Untangle UTM device Systems/Applications
Device Class Other, Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
- 486 - N-central 10.0 Services Reference Manual
Metric Name OID/Calculation Description
Scans ^1.3.6.1.4.1.30054.6.0.19.7 The number of scans performed by the Untangle device.
Detected Phishing ^1.3.6.1.4.1.30054.6.0.19.8 The number of phishing attempts detected by the Attempts Untangle device.
Passed Phishing ^1.3.6.1.4.1.30054.6.0.19.9 The number of phishing attempts passed by the Attempts Untangle device.
Removed Phishing ^1.3.6.1.4.1.30054.6.0.19.10 The number of phishing attempts blocked by the Attempts Untangle device.
Untangle – Protocol Filter Service The Untangle - Protocol Filter service monitors the number of scans, protocol filter detections, and protocol filter blocks detected by the Untangle device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Any Untangle UTM device Systems/Applications
Device Class Other, Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation Description
Scans ^1.3.6.1.4.1.30054.6.0.19.7 The number of scans performed by the Untangle device.
Protocol Filter ^1.3.6.1.4.1.30054.6.0.19.8 The number of protocol filter detections performed by Detections the Untangle device.
Protocol Filter ^1.3.6.1.4.1.30054.6.0.19.9 The number of protocol filter blocks performed by the Blocks Untangle device.
- 487 - N-central 10.0 Services Reference Manual
Untangle – Router Service The Untangle - Router service monitors the number of blocked requests, NAT requests, Router redirects, and DMZ requests detected by the Untangle device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Any Untangle UTM device Systems/Applications
Device Class Other, Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation Description
Blocked ^1.3.6.1.4.1.30054.7.0.19.7 The number of requests blocked by the Untangle device. Requests
NAT Requests ^1.3.6.1.4.1.30054.7.0.19.8 The number of NAT requests serviced by the Untangle device.
Router Redir- ^1.3.6.1.4.1.30054.7.0.19.9 The number of router redirects serviced by the Untangle ects device.
DMZ Requests ^1.3.6.1.4.1.30054.7.0.19.10 The number of DMZ requests serviced by the Untangle device.
Untangle – Spam Service The Untangle - Spam service monitors the number of clean messages, blocked messages, marked messages, and quarantined messages detected by the Untangle device.
Note: This service cannot use N-central’s Self-Healing feature.
- 488 - N-central 10.0 Services Reference Manual
Service Type SNMP
Instances on a Device 1
Supported Any Untangle UTM device Systems/Applications
Device Class Other, Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation Description
Clean Messages ^1.3.6.1.4.1.30054.10.0.19.7 The number of clean messages detected by the Untangle device.
Blocked Messages ^1.3.6.1.4.1.30054.10.0.19.8 The number of messages blocked by the Untangle device.
Marked Messages ^1.3.6.1.4.1.30054.10.0.19.9 The number of messages marked by the Untangle device.
Quarantined Mes- ^1.3.6.1.4.1.30054.10.0.19.10 The number of messages quarantined by the sages Untangle device.
Untangle – Spyware Service The Untangle - Spyware service monitors the number of scans, blocked spyware, and passed spyware detected by the Untangle device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Any Untangle UTM device Systems/Applications
Device Class Other, Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
- 489 - N-central 10.0 Services Reference Manual
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation Description
Scans ^1.3.6.1.4.1.30054.8.0.19.7 The number of spyware scans performed by the Untangle device.
Blocked ^1.3.6.1.4.1.30054.8.0.19.8 The amount of spyware blocked by the Untangle device. Spyware
Passed Mail ^1.3.6.1.4.1.30054.8.0.19.9 The amount of mail passed by the Untangle device.
Untangle – Virus Service The Untangle - Virus service monitors the number of scanned messages, blocked viruses, passed messages, and removed viruses detected by the Untangle device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Any Untangle UTM device Systems/Applications
Device Class Other, Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation Description
Scanned Messages ^1.3.6.1.4.1.30054.9.0.19.7 The number of messages scanned for viruses.
Blocked Viruses ^1.3.6.1.4.1.30054.9.0.19.8 The number of blocked viruses.
Passed Messages ^1.3.6.1.4.1.30054.9.0.19.9 The number of messages found to be virus-free.
Removed Viruses ^1.3.6.1.4.1.30054.9.0.19.9 The number of viruses that were removed.
- 490 - N-central 10.0 Services Reference Manual
Untangle – Web Filter Service The Untangle - Web Filter service monitors the number of scans, web filter blocks, and web filter passes detected by the Untangle device.
Note: This service cannot use N-central’s Self-Healing feature.
Service Type SNMP
Instances on a Device 1
Supported Any Untangle UTM device Systems/Applications
Device Class Other, Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
OID/Calculation
Note: N-central services use Reverse Polish Notation (RPN) for all calculation formulae.
Metric Name OID/Calculation Description
Scans ^1.3.6.1.4.1.30054.1.0.19.7 The number of web requests scanned by the Untangle device.
Web Filter Blocks ^1.3.6.1.4.1.30054.1.0.19.8 The number of web requests blocked by the Untangle device.
Web Filter ^1.3.6.1.4.1.30054.1.0.19.9 The number of web requests allows by the Untangle device. Passes
Veeam Failed Jobs Service The Veeam Failed Jobs service monitors Veeam Backup and Replication software for failed data backup jobs.
For information on monitoring Veeam backup jobs with N-central, refer to "How To Monitor Veeam Data Backup" in the N-central online help.
- 491 - N-central 10.0 Services Reference Manual
Service Type Automation Manager Policy
Instances on a Device 100
Supported Veeam Backup and Replication 6.5, 7, and 8 Systems/Applications
Device Class Laptop - Windows, Server - Windows, and, Workstation - Windows
Monitored By Agent
Scan Interval in Minutes The time (in minutes) between each scan.
Service Identifier The unique identifier assigned to this instance of the service.
Metric Name Description
Number of Failed Backups The total number of Veeam backup jobs that have failed.
Names of Failed Backups The names of all of the Veeam backup jobs that have failed.
Number of Failed Sure The number of Veeam Sure backup jobs that have Backups failed.
Names of Failed Sure The names of the Veeam Sure backup jobs that have Backups failed.
Number of Failed Tape The number of Veeam tape backup jobs that have failed. Backups
Names of Failed Tape The names of the Veeam tape backup jobs that have Backups failed.
Veeam Job Monitor Service The Veeam Job Monitor service monitors an individual Veeam data backup job.
For information on monitoring Veeam backup jobs with N-central, refer to "How To Monitor Veeam Data Backup" in the N-central online help.
- 492 - N-central 10.0 Services Reference Manual
Service Type Automation Manager Policy
Instances on a Device 100
Supported Veeam Backup and Replication 6.5, 7, and 8 Systems/Applications
Device Class Laptop - Windows, Server - Windows, and, Workstation - Windows
Monitored By Agent
Scan Interval in Minutes The time (in minutes) between each scan.
Job Name The identifying name of the Veeam backup job to be monitored.
Service Identifier The unique identifier assigned to this instance of the service.
Metric Name Description
Last Job Result Indicates the result of the monitored job the last time that it was run.
Job Name Indicates the name of the Veeam backup job that is being monitored.
Job State Indicates the current state of the Veeam backup job that is being monitored as one of the following:
l Stopped
l Started
Job Type Indicates the type of Veeam backup job that is being monitored from one of the following:
l Replication
l Migration
l VM Copy
l File Copy
Time Since Last Indicates the amount of hours since the last time that the monitored job was run. Run (Hours)
Start Time Indicates the time at which the monitored job started running.
- 493 - N-central 10.0 Services Reference Manual
Metric Name Description
Duration Indicates the amount of time (in minutes) it took for the monitored job to run. (Minutes)
Stop Time Indicates the time at which the monitored job finished running.
Backup Size Indicates the size of the data (in kilobytes) after it has been compressed. (KBytes)
Compress Ratio Indicates as a percentage the amount by which the original data was reduced in size by compression.
Data Size Indicates the original size of the data (in kilobytes) prior to being compressed. (KBytes)
Dedupe Ratio Indicates the ratio of the amount of data prior to deduplication compared to the amount of data after deduplication has taken place.
Job ID Indicates the unique identifier of the Veeam backup job that is being monitored.
Job Result Indicates the results of the Veeam backup job that is being monitored mapped as Status follows:
l 0 - Success
l 1 - Working
l 2 - Warning
l 3 - Failed
Veeam Sure Job Monitor Service The Veeam Sure Job Monitor service monitors an individual Veeam sure data backup job.
For information on monitoring Veeam backup jobs with N-central, refer to "How To Monitor Veeam Data Backup" in the N-central online help.
- 494 - N-central 10.0 Services Reference Manual
Service Type Automation Manager Policy
Instances on a Device 100
Supported Veeam Backup and Replication 6.5, 7, and 8 Systems/Applications
Device Class Laptop - Windows, Server - Windows, and, Workstation - Windows
Monitored By Agent
Scan Interval in Minutes The time (in minutes) between each scan.
Job Name The identifying name of the Veeam sure backup job to be monitored.
Service Identifier The unique identifier assigned to this instance of the service.
Metric Name Description
Job Name Indicates the name of the Veeam backup job that is being monitored.
Job Type Indicates the type of Veeam backup job that is being monitored from one of the following:
l Replication
l Migration
l VM Copy
l File Copy
Last Job Result Indicates the result of the monitored job the last time that it was run.
Time Since Last Run Indicates the amount of hours since the last time that the monitored job was run. (Hours)
Job State Indicates the current state of the Veeam backup job that is being monitored as one of the following:
l Stopped
l Started
- 495 - N-central 10.0 Services Reference Manual
Metric Name Description
Job Start Time Indicates the time at which the monitored job started running.
Job Duration Indicates the amount of time (in minutes) it took for the monitored job to run. (Minutes)
Stop Time Indicates the time at which the monitored job finished running.
Job ID Indicates the unique identifier of the Veeam backup job that is being monitored.
Job Result Status Indicates the results of the Veeam backup job that is being monitored mapped as follows:
l 0 - Success
l 1 - Working
l 2 - Warning
l 3 - Failed
How To Monitor Veeam Data Backup
Requirements N-central can monitor Veeam backup and replication software on devices provided that they meet the following minimum requirements:
l A Professional Mode license applied to the device in N-central
l A current N-central Agent (Version 9.5.1.243 or later)
l Veeam Backup and Replication 6.5, 7, or 8 installed
l Windows PowerShell 2.0 installed
l Veeam Powershell Snap-in installed
Note: For information on how to install the Veeam Powershell Snapin, refer to Veam KB1489.
Procedure To monitor Veeam backup jobs on a managed device, perform the following:
1. If you have not already done so, run a discovery job and import the computers that are using Veeam backup and replication software. For more information, refer to "Discovery Jobs" in the N- central online help.
Once the device has been imported and the asset discovery has completed (approximately five minutes), the Veeam Backup and Replication service template should automatically be applied to the devices which will associate the Veeam Failed Jobs, Veeam Job Monitor, and Veeam Sure Job Monitor services for each active backup job that is detected.
- 496 - N-central 10.0 Services Reference Manual
2. To verify that the Veeam services have been associated with the device, click All Devices >
3. If the Veeam services have not been associated with the device, click All Devices >
4. If this fails to associate the necessary Veeam services to the device, confirm that the require- ments stated above have all been met and re-run the asset discovery job. Veeam should appear on the list of applications displayed for the device.
5. If the appropriate Veeam services still cannot be associated with the device, contact SolarWinds N-able Technical Support for further assistance.
Veritas Service The Veritas service determines the success or failure of a Veritas backup by locating and reviewing the log files generated by the backup software.
The Veritas service looks for system-specified status codes in the xml log file. If these status codes match specified job status values, the agent displays the Failed status on the status dashboard. If the agent does not find a match, it displays the Normal state to the central server.
Service Type Log Appended
Instances on a Device 1
Supported Symantec™ Backup Exec™ version 10 and earlier Systems/Applications
Device Class Server - Windows
Monitored By Agent (Windows)
Keyword The keyword (default value: Fail) is how N-central determines whether or not a Veritas backup has succeeded or failed. If the keyword is found, the Veritas service will transition to a failed state.
- 497 - N-central 10.0 Services Reference Manual
Log File Prefix The log file prefix is a string used to find log files within the log file directory. If the log file directory exists, the agent strips the prefix from the file names and looks for the file with the newest timestamp. If you use the defaults, the agent selects all of the files matching bex*.txt for consideration. For example: If you change the prefix to veritas and log.txt, the agent selects all of the files matching veritas*log.txt for consideration.The prefix cannot contain spaces or use wildcards.If the agent cannot find a file with the specified prefix, it reports the Failed state to the N- central server. If the log file has a .xml suffix, then N-central processes this file as a Veritas 9 or 10 file.
Log File Suffix The log file suffix is a string used to find log files within the log file directory. If the log file directory exists, the agent strips the suffix from the file names and looks for the file with the newest timestamp. If you use the defaults, the agent selects all of the files matching bex*.txt for consideration. For example: If you change the suffix to veritas and log.txt, the agent selects all of the files matching veritas*log.txt for consideration. The suffix cannot contain spaces or use wildcards and must include the period. If the agent cannot find a file with the specified suffix, it reports the Failed state to the central server. If the log file has a .xml suffix, then N- central processes this file as a Veritas 9 or 10 file. The suffix for Veritas 9 and 10 is not case-sensitive.
Log File Directory The Log File Directory is the file in which to search for log files. The default value is a full path and can contain spaces. The trailing backslash is required. For example: C:\Program Files\Veritas\Logs\
Time Offset The maximum allowable age, in hours, of the Veritas log file. The agent will calculate the time that has passed between the current time and when the Veritas log file was last modified. If the difference is more than the time offset, the log is considered out of date, and the Veritas service will report a Failed state.
Scan Interval Every day at 4:59am
Repeat Weekly on The log file scan is repeated weekly on the specified days. Days
Repeat Monthly on The log file scan is repeated monthly on the specified days. Days
- 498 - N-central 10.0 Services Reference Manual
Metrics
Metric Description Name
Veritas N-central determines the quality of performance by comparing the monitored data to the Service thresholds. The availability range is 0-255, which corresponds to the following: Normal = 1, Availability Warning = 2-255, and Failed = 0.
Backup How long the backup took to complete. duration (Seconds)
Data The amount of data backed up by the Veritas backup job. amount backed up (Bytes)
Job Status You can view the return values for the associated job status on the status screen for the Veritas for Veritas service. These values represent specific critical issues. They are returned by Veritas Backup Exec 9 and 10 and reported by the agent. For the return values: 1, 5, 6, 7, 8, 9, 10, 11, 12, 14, 16, 20, 21, 22, and 23, the agent reports the Failed state to the central server. For the value 3, the agent reports the Warning state.
Veritas Describes the results of the latest scan. Service For example: Details Job start time is beyond the offset, this log file c:\Program Files\Veritas\Backup Exec\Nt\Data\BEX01586.xml is an old log file
Return Values of Veritas 9 and 10 Job Statuses and Critical Issues
Return Job Status Description of Critical Issue Value
1 Cancelled Job is terminal due to cancellation.
2 Completed Job has been completed by the engine and is waiting final disposition.
3 Successful with Job is terminal with success but there are some exceptions. exceptions
4 Dispatched Job has been sent for execution.
5 Hold Job is in a hold state.
6 Error Job is terminal with an error.
7 Invalid schedule The schedule for the task is invalid.
- 499 - N-central 10.0 Services Reference Manual
Return Job Status Description of Critical Issue Value
8 Invalid time The time window is mutually exclusive thus job will never run. window
9 Missed Job is eligible for dispatch and is late.
10 Not in window Date of job makes it eligible to run, but time is not in window.
11 Ready but paused Job is ready, but dispatcher is paused.
12 Pending The job needs to be dispositioned to an actual state.
13 Recovered The system forced recovery of the job.
14 Disabled Job has been disabled in the system.
15 Resumed The job will be restarted with check point restart enabled, this value is only set in the job history summary.
16 Active Job is currently running on server.
17 Ready Job is eligible for dispatch.
18 Scheduled The job has a due date in the future.
19 Success Job is terminal with success.
20 Superseded Job is ready, but another higher precedence task is eligible to run.
21 Threshold auto- The job was aborted due to Abort Threshold time-out. abort
22 To be scheduled The job needs to have the due date calculated.
23 Linked job The job is linked to another job so will not start until the master job is finished.
VNC Service N-central can monitor the availability of a Virtual Network Computing (VNC) server.
N-central can determine the up or down status of the VNC service. The VNC service does not use the Warning state.
N-central averages the availability of the VNC service over the scan interval. It compares the availability of the VNC service to the threshold to determine the status.
- 500 - N-central 10.0 Services Reference Manual
Service TCP Type
Instances 1 on a Device
Device Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Class Windows, Server - Windows, and Workstation - Windows
Monitored Windows probe, Central Server By
Scan The number of minutes between scan. The default is 5 minutes Interval
Timeout The time (in seconds) that the N-central server waits before considering the test a failure. The Value default is 30 seconds.
Port 5900 Number
Validation The response you expect to receive from the port that is being queried. If the validation string that String you specify is not returned by the port being queried, the service will transition to a Failed state. The default validation string is RFB.
Status Details
Status Description Detail
VNC N-central determines whether the VNC service is up or down. The VNC service does not use the Service Warning state. N-central averages the availability of the VNC service over the scan interval and Availability compares the availability of the VNC service to the threshold to determine the status.
Volume (EqualLogic) Service The Volume (EqualLogic) service monitors the the status of a disk volume on a Model PS6100 Dell EqualLogic SAN running v6.0.2 firmware.
Service Type SNMP
Instances on a Device 1
Supported Model PS6100 Dell EqualLogic SAN running v6.0.2 firmware Systems/Applications
Device Class Server - Generic, Server - Windows
- 501 - N-central 10.0 Services Reference Manual
Monitored By Windows Agent
Scan Interval 5 minutes
Volume Name Type the name of the volume to be monitored. For a list of available volumes, query the SAN with the .1.3.6.1.4.1.12740.5.1.7.1.1.4 SNMP OID.
Object Numerical OID Descriptors
$Description 1.3.6.1.4.1.12740.5.1.7.1.1.6
$Size 1.3.6.1.4.1.12740.5.1.7.1.1.8
$AdminStatus 1.3.6.1.4.1.12740.5.1.7.1.1.9
$AllocatedSpace 1.3.6.1.4.1.12740.5.1.7.7.1.13
$OperStatus 1.3.6.1.4.1.12740.5.1.7.7.1.8
- 502 - N-central 10.0 Services Reference Manual
Status Description Detail
Admin Specifies whether the target volume has been configured as either online or offline by the Status administrator.
If a volume is offline, it cannot be accessed by ISCSI initiators.
When lost blocks that belong to a particular volume are found, the Operational Status of the volume is set to not-available-due-to-lost-cached-blocks.
When the volume is in this state and if the user chooses to ignore the lost blocks by setting the volume status to Online, the Admin Status is automatically set to online-lost-cached-blocks by the subsystem.
The online-lost-cached-blocks state of Admin Status indicates that the user acknowledged and acted upon the lost-blocks state of the volume.
Upon re-start and if the subsystem finds a volume with $AdminStatus as online-lost-cached- blocks, it will configure the Operational Status to Online instead of not-available-due-to- lost-cached-blocks as the user has already acknowledged the lost-blocks state and has chosne to ignore them.
Admin Mapped as follows: Status Descripti 1. online on 2. offline 3. online-lost-cached-blocks 4. online-control 5. offline-control
Operatio Specifies the current operational status of the volume. nal Status
Operatio Mapped as follows: nal Status 1. available Descripti 2. not-available on 3. not-available-due-to-snap-reserve-met 4. not-available-due-to-members-offline 5. not-available-due-to-lost-cached-blocks 6. not-available-due-to-thin-max-growth-met 7. not-available-due-to-nospace-for-auto-grow 8. not-available-due-to-missing-pages
- 503 - N-central 10.0 Services Reference Manual
Status Description Detail
Volume Specifies the total size of the volume (in MB) that is being monitored. Size Volume size is rounded to a multiple of 15MB. For thin provisioned volumes, this value (MB) represents the advertized size of the volume.
Used Calculated as ((Allocated Space/Size)*100) and expressed as a percentage of the total size of Space the volume. (%)
VPN Tunnel (Cisco) Service The VPN Tunnel (Cisco) Service monitors the status of a VPN tunnel running on a Cisco VPN provider (for example, an ASA firewall or a VPN Concentrator).
Service Type SNMP
Instances on a Device 1
Supported Any Cisco device that provides VPN capabilities. Systems/Applications
Device Class Switch/Router
Monitored By Windows Probe
Scan Interval 5 minutes
Object Descriptors Numerical OID
$ActiveTime 1.3.6.1.4.1.9.9.171.1.2.3.1.16
$HashAlgo 1.3.6.1.4.1.9.9.171.1.2.3.1.13
$DroppedInBoundPackets 1.3.6.1.4.1.9.9.171.1.2.3.1.21
$DroppedOutBoundPackets 1.3.6.1.4.1.9.9.171.1.2.3.1.29
- 504 - N-central 10.0 Services Reference Manual
Status Detail Description
Tunnel Uptime The duration of the VPN tunnel being monitored.
Hash Algorithm The hashing algorithm used to compute a hash value from a base input number to encrypt the VPN tunnel.
Dropped Inbound The number of data packets being sent to the monitored device that were lost during Packets the VPN tunnel.
Dropped Outbound The number of data packets being sent from the monitored device that were lost dur- Packets ing the VPN tunnel.
Windows Applications and Services Log The Windows Applications and Services Log allows you to monitor the Applications and Services Logs on Windows devices, similar to the Windows Event Log Service.
Since you can assign up to 1,000 instances of this service to a device, each instance can be given a Service Identifier. The Service Identifier will be included in e-mail notifications and on service-related displays (including the Active Issues view and the Status tab when editing a device). This allows you to maintain multiple instances of the Windows Applications and Services Log in an organized fashion.
For some sources, the Agent may not be able to retrieve an event description due to one of the following:
l the relevant Windows registry keys do not exist,
l the relevant Windows registry keys do not contain valid data, or,
l the Event Message Files are corrupted or were not found.
For any of the scenarios described above, the following message will be displayed: "The description for Event ID ( Event ID Number ) in Source ( Source Name ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer."
Service Type WMI
Instances on a Device 25
Device Class Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent (Windows), Windows Probe
Generate a Notification When selected, this directs the service to generate notifications whenever events when an Event is detected are detected.
Scan Interval 30 minutes
- 505 - N-central 10.0 Services Reference Manual
Options to Monitor: The names of the Windows Event Viewer logs that are to be monitored:
l Security (Failure, Success)
l Application (Error, Information, Warning)
l System (Error, Information, Warning)
l Directory Service (Error, Information, Warning)
l File Replication Service (Error, Information, Warning)
l DNS Server (Error, Information, Warning)
Include List The event IDs that you would like to monitor. You can specify individual event IDs or a range of comma-separated event IDs. For example: 100,200,250-400,500-650 This field allows a maximum of 200 characters. Spaces are not allowed.
Exclude List The event IDs that you would like to exclude from monitoring. You can specify individual event IDs or a range of comma-separated event IDs. For example: 100,200,250-400,500-650 This field allows a maximum of 200 characters.
Event Source Include Filter The names of the sources that you would like to monitor. You must use the CSV format. For a range of Event IDs, you can use a dash (-). For example: Userenv,Security,W32Time
Event Source Exclude Filter The names of the Event Log sources that you would like to exclude from monitoring. You must use the CSV format. For a range of Event IDs, you can use a dash (-). For example: Userenv,Security,W32Time
Event Description Regex Fil- The name of the text string or regular expression you would like to look for in the ter Description field of the event. For more information on Regular Expressions, please refer to the topic, Regular Expressions on page 59.
Checking A Service Status To check the status of a particular service, follow these steps:
1. Click All Devices in the left-hand pane.
2. Under the Network Devices tab, click on the relevant device.
3. Click on a specific Window Applications and Services Log to view its status.
- 506 - N-central 10.0 Services Reference Manual
4. Once you have been directed to the screen under the Status tab, you will see a graph containing data from the event log scan.
Note: If a graph does not appear, it means that no event logs have been found during the selected scan period. By default, the scan period is set at 1 day. To expand the scan period, select a different number of days from the drop-down menu next to the Period field (either 1, 7, or 30).
5. Click OK.
Windows Backup Service The Windows Backup service monitors the Windows Backup and Restore feature on managed Windows devices.
Requirements N-central can monitor Windows Backup and Restore on devices provided that they meet the following minimum requirements:
l The operating system on the device is either Windows 2008 R2, Windows 2012, or Win- dows 2012 R2.
l A Professional Mode license is applied to the device in N-central.
l A current N-central Agent (Version 9.5.1.243 or later) is installed on the device.
l Windows Backup and Restore is installed on the device.
l Windows PowerShell 2.0 is installed on the device.
Note: Windows 2008 R2 devices must also have the Command-line Tools option enabled when installing Windows Server Backup on the device.
To monitor Windows Backup jobs on a managed device
1. If you have not already done so, run a discovery job and import the computers that are using Windows Backup and Restore functionality. For more information, refer to "Discovery Jobs" in the N-central online help.
Once the device has been imported and the asset discovery has completed (approximately five minutes), the Windows Server Backup service template should automatically be applied to the devices which will associate the Windows Backup service for each active backup job that is detected.
2. To verify that the Windows Backup service has been associated with the device, click All Devices >
- 507 - N-central 10.0 Services Reference Manual
3. If the Windows Backup service has not been associated with the device, click All Devices >
4. If this fails to associate the Windows Backup service to the device, confirm that the require- ments stated above have all been met and re-run the asset discovery job.
5. If the Windows Backup service still cannot be associated with the device, contact SolarWinds N-able Technical Support for further assistance.
Service Type Automation Manager Policy
Instances on a Device 100
Supported Windows 2008 R2, Windows 2012, or Windows 2012 R2 Systems/Applications
Device Class Laptop - Windows, Server - Windows, and, Workstation - Windows
Monitored By Agent
Scan Interval in Minutes The time (in minutes) between each scan.
Service Identifier The unique identifier assigned to this instance of the service.
Metric Name Description
Last Backup Time Indicates the last time that a Windows Backup job was performed.
Last Backup Target Indicates the path to the destination folder where the backup files are configured to be stored.
Last Backup Detailed Result Indicates the result of the last backup job with 0.00 indicating success.
Last Backup Result Indicates the result of the last backup job with 0.00 indicating success.
Last Successful Backup Indicates the path to the destination folder where the last set of backup Target Path files were successfully stored.
- 508 - N-central 10.0 Services Reference Manual
Metric Name Description
Last Successful Backup Time Indicates the last time that a Windows Backup job was successfully performed.
Next Scheduled Backup Indicates when the next Windows Backup job is scheduled to be performed.
Number of Stored Versions Indicates the number of versions or copies of backup files that have been stored.
Current In-Progress Indicates whether or not a backup job is currently in progress. Operation
Time Since Last Backup Indicates the number of hours since the last Windows Backup job was (Hours) performed.
Time Since Last Successful Indicates the number of hours since the last successful Windows Backup Backup (Hours) job was performed.
Last Error Description Provides a description of the last error received during a backup job.
Last Error Status Indicates the status of the last backup job for which an error message was received.
Windows Event Log Service The Windows Event Log service allows you to monitor the Event logs on Windows devices.
Since you can assign multiple instances of the Windows Event Log service to a device, each instance can be given a Service Identifier. The Service Identifier will be included in e-mail notifications and on service- related displays (including the Active Issues view and the Status tab when editing a device), this allows you to maintain multiple instances of the Windows Event Log service in an organized fashion.
Note: This service cannot use N-central’s Self-Healing feature.
For some sources, the Agent may not be able to retrieve an event description due to one of the following:
l the relevant Windows registry keys do not exist,
l the relevant Windows registry keys do not contain valid data, or,
l the Event Message Files are corrupted or were not found.
For any of the scenarios described above, the following message will be displayed: "The description for Event ID ( Event ID Number ) in Source ( Source Name ) cannot be found.
- 509 - N-central 10.0 Services Reference Manual
The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer."
The Windows Event Viewer can manage the following types of logs on a computer:
l Security,
l Application,
l System Log,
l Directory Service Log (only available on devices classed as Server-Windows),
l File Replication Service Log (only available on devices classed as Server-Windows), and
l DNS Server Log (only available on devices classed as Server-Windows).
Note: The initial scan of the Windows Event Log service will scan the most recent 100 entries in the Event log.
Service Type WMI
Instances on a Device 25
Device Class Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Agent (Windows), Windows probe
Generate a Notification When selected, this directs the service to generate notifications whenever events when an Event is detected are detected.
Scan Interval 30 minutes
Options to Monitor: The names of the Windows Event Viewer logs that are to be monitored:
l Security (Failure, Success)
l Application (Error, Information, Warning)
l System (Error, Information, Warning)
l Directory Service (Error, Information, Warning)
l File Replication Service (Error, Information, Warning)
l DNS Server (Error, Information, Warning)
Include List The event IDs that you would like to monitor. You can specify individual event IDs or a range of comma-separated event IDs. For example: 100,200,250-400,500-650 This field allows a maximum of 200 characters. Spaces are not allowed.
- 510 - N-central 10.0 Services Reference Manual
Exclude List The event IDs that you would like to exclude from monitoring. You can specify individual event IDs or a range of comma-separated event IDs. For example: 100,200,250-400,500-650 This field allows a maximum of 200 characters.
Event Source Include Filter The names of the sources that you would like to monitor. You must use the CSV format. For a range of Event IDs, you can use a dash (-). For example: Userenv,Security,W32Time
Event Source Exclude Filter The names of the Event Log sources that you would like to exclude from monitoring. You must use the CSV format. For a range of Event IDs, you can use a dash (-). For example: Userenv,Security,W32Time
Event Description Regex Fil- The name of the text string or regular expression you would like to look for in the ter Description field of the event. For more information on Regular Expressions, please refer to the topic, Regular Expressions on page 59.
Thresholds The thresholds for the Windows Event Log service are used for monitoring as follows:
Event This is the status that is sent if you have selected Generate A Notification When An Event is Log Mod- Detected check box under the Service Details tab. The threshold for this module is 0 for normal ule and 1 for failed and all of the specified criteria under the Service Details tab have been met. Status
# of Indicates the number of identical identifiers that can be recorded in the log within the configured Duplicate scan interval before triggering the transition to a different state. The default for this threshold is 0 Events for normal and 1 for failed.
Windows Server Clock Drift Service The Windows Server Clock Drift service is used to monitor the time difference (in seconds) between a monitored Windows server and a Network Time Protocol (NTP) server.
- 511 - N-central 10.0 Services Reference Manual
Service Type Automation Manager Policy
Instances on a 100 Device
Supported Any Windows device running the Windows Time (W32Time) service. Systems/Applicatio ns
Device Class Laptop - Windows, Server - Windows, Workstation - Windows
Monitored By Local Agent
Scan Interval 5 minutes
NTP Server Type the address of the Network Time Protocol (NTP) server that will be used to compare the clock time of the monitored device.
Service Identifier Assign a unique identifier to this instance of the service.
Status Description Details
Time Indicates the difference (in seconds) between the clock time of the monitored device and the Offset designated NTP server.
Windows Service Service The Windows Service service monitors the status of a specified Windows service.
Service Type WMI
Instances on a 100 Device
Supported Any WMI-enabled workstation or server running Windows XP, Windows 2000, Windows Platforms 2003, or Windows Vista
Device Class Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - Windows
- 512 - N-central 10.0 Services Reference Manual
Monitored By Agent (Windows)
Scan Interval 15 minutes
Service Name The name of the Windows service being monitored.
Properties Queried and Calculations Performed
Namespace root\cimv2
WMI Class Win32_Service
WMI Property 0 Started
WMI Property 1 StartMode
WMI Property 2 Status
Status Details
Status Detail Description
Is the Service Started? State of the service:
l Normal if found
l Failed if not found
Service Start Mode Defines the monitored service's method for starting as one of the following:
l Boot
l System
l Auto
l Manual
l Disabled
Service Status Identifies the current operational status of the monitored service as one of the following:
l OK
l Error
l Degraded
l Unknown
l Pred Fail
l Starting
l Stopping
l Service
Windows Terminal Server Service The Windows Terminal Server service monitors the availability of the port, which the clients of the Microsoft Terminal Services use to connect to the Terminal Services application. The availability of the port, which is determined by the service testing the port's connectivity, indicates that the Terminal
- 513 - N-central 10.0 Services Reference Manual
Services are able to connect to the Terminal Services application. This service also measures the domain name system (DNS) resolution and the round trip time of the initial connection request and response. The availability results of the TCP service are then reflected on the status dashboard for the Windows Terminal Server service.
A maximum of three instances of this service can be set on a device, with each instance monitoring a different port on the device.
Note: The Windows Terminal Server service does not use the Warning state.
Service Type Generic TCP
Instances on a Device 3
Supported Microsoft Terminal Services Systems/Applications
Device Class Server - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored By Windows probe, Central Server
Scan Interval The time (in minutes) between each scan. The default is 5 minutes
Timeout Value The time (in seconds) that the central server waits before considering the test a failure. The default is 30 seconds.
Port Number 3389
Status Details
Threshold Description
Terminal Server The threshold that determines the availability of the port. Services Availability
Generic DNS The threshold that determines whether the device name can be resolved. Resolution If an FQDN has been specified, the service searches for its IP address. If the IP address is found, the state will be Normal. Otherwise, it will be Failed, based on the default settings. If an IP address has been specified, the service checks only the IP address's format. If the format is correct, the state will be Normal. Otherwise, it will be Failed, based on the default settings.
Round Trip The time (in milliseconds) for a request to be sent and received. Time (msec)
- 514 - N-central 10.0 Services Reference Manual
XiloCore Backup Service The XiloCore Backup service is used for monitoring Xilocore backup sets. A separate instance of the XiloCore Backup service is required to monitor each individual backup set.
Note: Monitoring a Xilocore backup set on a device that uses a Red Hat Enterprise or CentOS Linux operating system requires the use of a Windows Probe. In order for the Windows Probe to successfully discover the Linux device, you must first install the Microsoft Visual C++ 2010 Distributable Package on the device on which the Windows Probe is installed. For more information on the Microsoft Visual C++ 2010 Distributable Package, refer to http://www.microsoft.com/en-ca/download/details.aspx?id=5555.
Note: After upgrading an Agent that monitors the Asigra Backup service or the XiloCore Backup service, you will need to stop the Windows Agent services, place the Asigra .DLL files to the Agent's bin directory and re-start the Windows Agent services.
XiloCore v12.x In order for N-central to monitor XiloCore v12.x backup sets, you must redistribute the XiloCore API bundle as well as the msvcp100.dll and msvcr100.dll files as follows:
l If using a previously-installed Probe and you are installing XiloCore for the first time, you must store the API bundle and the MSVC .DLL files in the Probe's bin directory.
l If monitoring XiloCore using a previously-installed Agent, you must store the API bundle and the MSVC .DLL files in the Agent's bin directory.
l If installing a Probe and including an XiloCore discovery during the installation, you must ensure that the MSVC .DLL files are stored in the directory that is configured in the DLL path field of the installation software.
l If adding the API bundle and the new MSVC .DLL files to an existing Agent or Probe configuration, you must re-start the Agent or Probe after storing the MSVC .DLL files in order for N-central to start using them.
Service Type ODBC
Instances on a Device 100
Supported XiloCore version 9.2 and newer Systems/Applications
Device Class Server - Windows
Monitored By Agent (Windows), Windows probe
Job Timeout The time (in hours) that the N-central server waits for the backup job to report data. If the backup job has not reported data in the specified time, the service will transition to a Failed state. The default value is 24 hours.
- 515 - N-central 10.0 Services Reference Manual
Backup Set ID The unique identifying number of the selected XiloCore backup set
Backup Set Names The identifying names of the discovered XiloCore backup sets.
Scan Interval in The time (in minutes) between each scan. The default scan interval for XiloCore Backup Minutes is 30 minutes.
Repeat Weekly on The scan is repeated weekly on the specified days. Days
Repeat Monthly on The scan is repeated monthly on the specified days. Days
Metrics
Metric Name Description
Last Attempted Backup Start Date and The last date and time that a backup was tried (whether successful or Time not).
Backup Status The current status of the backup set.
Backup Status Description A description of the current status of the backup set.
Last Successful Backup Start Date and The last date and time that a backup was successful. Time
Last Sync Time The last time that the backup set was synchronized.
Backup Duration The time it took for the backup to be completed.
Backup Data Type The type of data being backed up (for example, HyperV or Sybase).
Backup Set Type The type of backup set as either Local Only or Local and Offsite.
Stored Size The size of the backed up data in its stored location.
Protected Size The size of the backed up data prior to compression or encryption.
Native Size The size of the backed up data in its original location.
- 516 - Index: about – Backup Exec service
APC UPS - Temperature service 69 Index APC UPS service 67
A Application Compliance service 69
about Asigra Backup service 70
self healing 50 audio service
services 14 NetBotz 293
Active Directory service 60 AV Activity - McAfee 79
add AV Activity - McAfee 8 service 80 services 41 AV Activity - Sophos 5 service 82 ADTRAN - Device Health service 63 AV Activity - Sophos service 81 ADTRAN - Memory service 64 AV Activity - Symantec service 83 Agent Status service 65 AV Activity - Trend Micro service 84 antivirus services AV Def - Sophos service 87 AV Activity - McAfee 79
AV Activity - McAfee 8 80 AV Def - Symantec service 89
AV Activity - Sophos 81 AV Def. - McAfee 8 service 86 AV Activity - Sophos 5 82 AV Def. - McAfee service 85 AV Activity - Symantec 83
AV Activity - Trend Micro 84 AV Def. - Sophos 5 service 88
AV Def - Sophos 87 AV Def. - Trend Micro service 90 AV Def - Symantec 89 AV Defender Security Event service 72 AV Def, - Trend Micro 90
AV Def. - McAfee 85 AV Defender Status service 74
AV Def. - McAfee 8 86 AV Status service 78 AV Def. - Sophos 5 88
APC PDU service 66 B
APC UPS - Humidity service 68 Backup Exec service 91
- 517 - Index: Backup Manager Events service – CPU service
Backup Manager Events service 96 CCM MTP - Transcoder service 119
Backup Manager Status service 94 CCM Music on Hold service 122
BES Message Status service 96 CCM Performance service 124
CCM Phone Registration service 126 C CCM Phone service 125 CA Replication Events service 98 CCM Server service 127 CA Replication Scenario service 100 CCM Voicemail Device service 131 CCM Analog Gateway FXO Port service 101, 103 CCM VoiceMail Registration service 133
CCM Analog Gateway FXS service 103 circuit sensor thresholds 66
CCM Annunciator service 104 Cisco CPU (Adtran) service 144 CCM Call Activity service 106 memory service 138 CCM Call Mgr Status service 107 Cisco Unity Express Mailbox service 138 CCM Conf Activity service 108 Citrix Presentation Server service 139 CCM Conference Registration service 110 Connections - Watchguard service 140 CCM CTI Activity service 110 Connections (Cisco) service 136 CCM CTI Registration service 111 Connectivity service 141 CCM Gateway Registration service 112 CPU - Juniper (ScreenOS) service 149 CCM ISDN - Basic Rate Interface service 114 CPU - Juniper Secure Access service 149
CCM ISDN - Primary Rate Interface ser- CPU - Watchguard service 151 vice 115 CPU (Adtran) service 144 CCM ISDN - T1 Trunks service 115 CPU (Cisco) service 145 CCM Media Device service 121 CPU (VMware) service 150 CCM MGCP Gateway service 117 CPU service 143
- 518 - Index: Datastore (VMware) service – FW - SonicWALL
Exchange Server 2007/2010 delivery D queue service 175
Datastore (VMware) service 153 Exchange Server 2007/2010 service 174 delete
service 44 F
Dell Fan Status (Dell) service 181 Fan Status (Dell) service 181 Fan Status (HP) service 185 Power Supply (Dell) service 334
Server Temperature service 432 Fan Status (IBM) service 187
Dell Physical Drive service 309 Fan Status (Intel) service 188 disable FanStatus (VMware) service 190
service 43 File Size service 192 serviceor service grouping 44 Firewall Untangle service 485 Disk I/O service 160 Fortinet CPU service 193 Disk service 158 Fortinet Disk service 193 DNS service 163 Fortinet Memory service 194 door Fortinet Sessions service 194
E Frame Relay service 195 edit FTP service 198
service 42 FW-Zywall service 205 enable FW - Chk Point service 199 service 43 FW - Cisco 200 service or service grouping 44
FW - Fortigate service 202 Ethernet Errors service 168
FW - Juniper service 202 Exchange Server 2003 service 171
FW - SonicWALL 203
- 519 - Index: FW - Watchguard service – Juniper service
FW - Watchguard service 204 IIS service 229
IMAP service 236 G Intel
gateway service 117 power supply service 340
generating service reports 58-59 Server Temp (Intel) service 435
Generic (TCP) service 206 Intel logical drive service 275
Generic Integer (SNMP) service 207 Intel physical drive service 326
Generic ODBC service 208 Intel® Quiet System Technology service 237 Generic SQL Server service 210 Intel® vPro™ Agent Status service 239 Generic String (SNMP) service 211 Intel® vPro™ Events service 240 Guest Status (VMware) service 212 Intel® vPro™ Status service 241
H Interface Health service 242
HP Intrusion Detection service 245
Fan Status (HP) service 185 ISA 2000 service 248 Fan Status (Intel) service 188 ISA 2006 service 250 Physical Drive Service 325
Power Supply (HP) service 338 J server temperature service 434 Juniper (ScreenOS) - Sessions HTTP service 215 service 253
HTTPS service 221 Juniper (ScreenOS) memory service 283
Juniper Secure Access - Concurrent Users I service 254
IBM Juniper Secure Access memory memory service 289 service 284
server temperature service 439 Juniper service 149
- 520 - Index: Lexmark - Hopper Status service – Physical Drive (VMware) service
Memory (VMware) service 290 L Memory service 280 Lexmark - Hopper Status service 254 Memory Status (IBM) service 289 Lexmark - Paper Jam Status service 255 Memory Status (VMware) service 291 Lexmark - Tray Status service 256 monitoring services 41 License Compliance service 257
Licensing Status (VMware) service 258 N
LocalIP service 259 Netbotz Airflow service 292
Log Analysis (Appended) service 260 NetBotz Audio service 293
Log Analysis (Batch) service 261 Netbotz Dewpoint service 294
Logical Drive (Adaptec) service 263 NetBotz Door Switch service 295
Logical Drive (Dell) service 268 Netbotz Humidity service 296
Logical Drive (Intel) service 275 NetBotz Temperature service 297
Logical Drive (VMware) service 277 NIC Status (VMware) service 300
NNTP service 301 M mailbox service P
Cisco 138 Paper Supply Level service 303
Maintenance Mode (VMware) service 279 Patch Status service 304 media service 121 Physical Drive (Adaptec) service 307
Memory - Cisco service 138 Physical Drive (Dell) service 309
Memory - Juniper (ScreenOS) Physical Drive (HP) service 325 service 283
Physical Drive (Intel) service 326 Memory - Juniper Secure Access service 284 Physical Drive (VMware) service 328
- 521 - Index: POP service – Server Temp (Intel) service
POP service 330 Probe Status service 349
Power Consumption (VMware) Process service 350 service 331
Power Supply (Dell) service 334 R
Power Supply (HP) service 338 RAID Status (Adaptec) service 412
Power Supply (Intel) service 340 RAID Status (Dell) service 416
Power Supply(VMware) service 341 RAID Status (HP) service 426
Printer Conf service 343 RAID Status (VMware) service 427
Printer Cover Status service 344 regular expressions
Printer Display service 344 valid in N-central 59
Printer Page Count (HP) service 346 report service level generation 58-59 Printer Page Count service 345
printer services S
Lexmark - Paper Jam Status 255 SCOM Computer Alerts service 429 Lexmark Hopper Status 254
Lexmark Tray Status 256 SCOM Distributed Application Alerts ser- vice 430 paper supply level 303
printer configuration 343 Security Logs service 431
printer cover status 344 Self-Healing 50 Printer Display 344 sensor status and humidity 68 printer page count 345
Printer Page Count (HP) 346 Server Temp (Dell) service 432
printer status 347 Server Temp (HP) service 434 printer toner lLevel 348 Server Temp (IBM) service 439 Printer Status service 347 Server Temp (Intel) service 435 Printer Toner Level service 348
- 522 - Index: service – services
service AV Def. - Trend Micro 90
Backup Manager Status 94 AV Defender Security Event 72
AV Defender Status 74 service failure AV Status 78 responses 50 Backup Exec 91 service grouping Backup Manager Events 96 disable or enable 44 BES Message Status 96 services CA Replication Scenario 98, 100
about services 14 CCM Analog Gateway FXO Port 101, 103 Active Directory 60 CCM Analog Gateway FXS Port 103 add 41 CCM Annunciator 104 ADTRAN - Device Health 63 CCM Call Activity 106 ADTRAN - Memory 64 CCM Call Mgr Status 107 Agent Status 65 CCM Conf Activity 108 APC PDU 66 CCM Conference Registration 110 APC UPS 67 CCM CTI Registration 111 APC UPS - Humidity 68 CCM Gateway Registration 112 APC UPS - Temperature 69 CCM ISDN - Basic Rate Interface 114 Application Compliance 69 CCM ISDN - Primary Rate Interface 115 Asigra Backup 70 CCM ISDN - T1 Trunks 115 AV Activity - McAfee 79 CCM Media Device 121 AV Activity - McAfee 8 80 CCM MGCP Gateway 117 AV Activity - Sophos 81 CCM MTP - Transcoder 119 AV Activity - Sophos 5 82 CCM Music on Hold 122 AV Activity - Symantec 83 CCM Performance 124 AV Activity - Trend Micro 84 CCM Phone Registration 126 AV Def - Sophos 87 CCM Phone service 125 AV Def - Symantec 89 CCM Server 127 AV Def. - McAfee 85 CCM Voicemail Device 131 AV Def. - McAfee 8 86 CCM VoiceMail Registration 133 AV Def. - Sophos 5 88
- 523 - Index: Services Properties – services
changing statuses 14 Fan Status (VMware) 190
Cisco Unity Express Mailbox 138 File Size 192
Citrix Presentation Server 139 Firewall - Chk Point 199
Connections - Watchguard 140 Fortinet CPU 193
Connections (Cisco) 136 Fortinet Disk 193
Connectivity 141 Fortinet Memory 194
CPU 143 Fortinet Sessions 194
CPU - Juniper (ScreenOS) 149 Frame Relay 195
CPU - Juniper Secure Access 149 FTP 198
CPU (Adtran) 144 FW- Watchguard 204
CPU (VMware) 150 FW-Zywall 205
CPU CISCO 145 FW - Cisco 200
CPU Watchguard 151 FW - Fortigate 202
Datastore (VMware) 153 FW - Juniper 202
delete 44 FW - SonicWALL 203
disable 43 FW - SonicWALL CPU 453
disable or enable 44 Generic (TCP) 206
Disk 158 Generic Integer SNMP 207
Disk I/O 160 Generic ODBC 208
DNS 163 Generic SQL Server 210
edit 42 Generic String (SNMP) 211
enable 43 Guest Status (VMware) 212
Ethernet Errors 168 HTTP 215
Exchange Server 2003 171 HTTPS 221
Exchange Server 2007/2010 174 IIS 229
Exchange Server 2007/2010 delivery IMAP 236 queue 175 Intel® Quiet System Technology 237 Fan Status (Dell) 181 Intel® vPro™ Agent Status 239 Fan Status (HP) 185 Intel® vPro™ Events 240 Fan Status (IBM) 187 Intel® vPro™ Status 241 Fan Status (Intel) 188 Interface Health 242
- 524 - Index: Services Properties – services
Intrusion Detection 245 NetBotz Dewpoint 294
ISA 2000 248 NetBotz Door Switch 295
ISA 2006 250 NetBotz Humidity 296
Juniper (ScreenOS) - Sessions 253 NetBotz Temperature 297
Juniper Secure Access - Concurrent NIC Status (VMware) 300 Users 254 NNTP 301 Lexmark - Hopper Status 254 Paper Supply Level 303 Lexmark - Paper Jam Status 255 Patch Status 304 Lexmark - Tray Status 256 Physical Drive (Adaptec) 307 License Compliance 257 Physical Drive (Dell) 309 Licensing Status (VMware) 258 Physical Drive (HP) 325 local API, SNMP, WMI processes 350 Physical Drive (Intel) 326 LocalIP 259 Physical Drive (VMware) 328 Log Analysis (Appended) 260 POP 330 Log Analysis (Batch) 261 Power Consumption (VMware) 331 Logical Drive (Adaptec) 263 Power Supply (Dell) 334 Logical Drive (Dell) 268 Power Supply (HP) 338 Logical Drive (Intel) 275 Power Supply (Intel) 340 Logical Drive (VMware) 277 Power Supply (VMware) 341 Maintenance Mode (VMware) 279 Printer Conf 343 Memory 280 Printer Cover Status 344 Memory - Cisco 138 Printer Display 344 Memory - Juniper (ScreenOS) Printer Page Count 345 service 283 Printer Page Count (HP) 346 Memory - Juniper Secure Access service 284 Printer Status 347
Memory (VMware) 290 Printer Toner Level 348
Memory Status (IBM) 289 Probe Status 349
Memory Status (VMware) 291 Process 350 monitoring 41 properties 45
NetBotz Airflow 292 RAID Status (Adaptec) 412
Netbotz Audio 293 RAID Status (Dell) 416
- 525 - Index: Services Properties – SSH service
RAID Status (HP) 426 Untangle - Phish 486
RAID Status (VMware) 427 Untangle - Protocol Filter 487
regular expressions valid in N- Untangle - Router 488 central 59 Untangle - Spam 488 SCOM Computer Alerts 429 Untangle - Spyware 489 SCOM Distributed Application Untangle - Virus 490 Alerts 430 Untangle - Web Filter 491 Security Logs 431 Veritas 497 Server Temp (Dell) 432 VNC 500 Server Temp (HP) 434 Windows Event Log 505, 509 Server Temp (IBM) service 439 Windows Service 512 Server Temp (Intel) service 435 WindowsTerminal Services 513 ShadowProtect 440 Xilocore Backup 515 SMTP 446
SMTP Queues 447 Services Properties 45
SNMP 449 set up SonicWALL Connections 453 SQL Server in mixed mode 94 SonicWALL Memory 454 ShadowProtect Service 440 SQL Server 455
SSH 462 SMTP Queues service 447
System Change 467 SMTP service 446 System Check-In 468 SNMP service 449 System Replacement 469
System Warranty 470 SonicWALL Connections service 453
Telnet 470 SonicWALL CPU service 453 Temperature Status (VMware) 479 SonicWALL Memory service 454 Terminal Server 480
Traffic 482 SQL Server
types 14 set up in mixed mode 94
Untangle - Firewall 485 SQL Server service 455 Untangle - IPS 485 SSH service 462
- 526 - Index: System Change service – Xilocore Backup Service
System Change service 467 V System Check-In service 468 Veritas service 497 System Replacement service 469 VMware System Warranty service 470 memory status service 291
T VNC service 500
Telnet service 470 W temperature service Watchguard service 140 APC UPS 69 web filter service, Untangle 491 Temperature Status (VMware) service 479 Windows Event Log service 505, 509
Terminal Server service 480 Windows Service service 512
Traffic service 482 WindowsTerminal Server service 513
U X
Untangle - Firewall service 485 Xilocore Backup Service 515
Untangle - IPS service 485
Untangle - Phish service 486
Untangle - Protocol Filter service 487
Untangle - Router service 488
Untangle - Spam service 488
Untangle - Spyware service 489
Untangle - Virus service 490
Untangle - Web Filter service 491
- 527 - © 2015 N-able Technologies, Inc.
All rights reserved. No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of N-able Technologies, Inc. (“N-able Technologies”). All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of N-able Technologies and its respective licensors.
N-ABLE TECHNOLOGIES DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL N-ABLE TECHNOLOGIES, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The N-ABLE TECHNOLOGIES and N-CENTRAL marks are the exclusive property of N-able Technologies and its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other N-able Technologies trademarks, service marks, and logos may be common law marks, registered or pending registration in the United States or in other countries. All other trademarks mentioned herein are used for identification purposes only and may be or are trademarks or registered trademarks of their respective companies.
Feedback
SolarWinds N-able (formerly known as N-able Technologies) is a market driven organization that places importance on customer, partner and alliance feedback. All feedback is welcome at the following email address: [email protected].
About SolarWinds N-able
SolarWinds N-able is the global leader in remote monitoring and management software for managed service providers and IT departments. SolarWinds N-able’s award-winning N-central platform and complementary toolsets, backed by best-in-class business and technical services, are proven to reduce IT support costs, improve network performance and increase productivity through the proactive monitoring, management and optimization of IP-enabled devices and IT infrastructure. SolarWinds N-able is 100% channel-friendly and maintains operations in North America, the U.K., the Netherlands and Australia.