INFORMANT-ADV: View SNMP OID List / Download MIB

The MIB module for SNMP Informant Advanced performance counter entries.

The ACS/RSVP Service performance object counters report statistics about Resource Reservation Protocol (RSVP) and Quality of Service (QoS) Admission Control (ACS) activity, flow, bandwidth, RSVP messages sent, and so on. The ACS/RSVP Service object is available if QoS Admission Control is installed, even if the service is not running.

Performance information for one particular instance of 'ACS/RSVP Service' object.

Instance name.

A running total of the number of bytes delivered in QoS Notifications to QoS-enabled applications.

The number of QoS requests generated by QoS-enabled applications that have been rejected by the ACS/RSVP service. Failed QoS requests can be caused by invalid QoS requests.

The number of QoS notifications the ACS/RSVP service that could not be sent to the QoS applications. Failed QoS sends can be caused by terminated applications.

The number of local network interfaces visible to, and used by the RSVP service.

The total number of raw sockets opened for the purpose of RSVP signaling.

The number of QoS notifications delivered to QoS-enabled applications by the QoS RSVP service.

The number of sockets that are currently QoS enabled.

Indicates the number of RESV messages sent for QoS-enabled receivers. This number increments each time a RESV is refreshed.

Indicates the number of PATH messages sent for QoS-enabled senders. This number increments each time a PATH is refreshed.

The current number of active RSVP sessions on the ACS/RSVP service.

The number of timer events scheduled to take place. Shows the activity level of the ACS/RSVP service.

The Active Server Pages performance object monitors errors, requests, sessions, or other data generated from Active Server Pages (ASP) applications.

Number of debugging document requests.

The number of engines invalidated in the cache due to change notification.

Number of requests failed due to runtime errors.

Number of requests failed due to preprocessor errors.

Number of requests failed due to script compilation errors.

The number of errors per second.

Percent of requests found in cached in memory.

The number of compiled templates cached in memory.

The total size, in bytes, of all requests.

The total size, in bytes, of responses sent to clients. This does not include standard HTTP response headers.

The number of milliseconds that it took to execute the most recent request.

The number of milliseconds the most recent request was waiting in the queue.

The number of requests that were disconnected due to communication failure.

The number of requests currently executing.

The total number of requests failed due to errors, authorization failure, and rejections.

Number of requests failed due to insufficient access rights.

The number of requests for files that were no found.

The number of requests waiting for service from the queue.

The total number of requests not executed because there were insufficient resources to process them.

The number of requests that executed successfully.

The number of requests that timed out.

The total number of requests since the service was started.

The number of requests executed per second.

Percent of requests found in script engine cache.

The number of script engines in cache.

The number of milliseconds that the most recent session persisted.

The current number of sessions being serviced.

The number of sessions timed out.

The total number of sessions since the service was started.

Percent of requests found in template cache.

The number of templates invalidated in the cache due to change notification.

The number of templates currently cached.

The number of transactions aborted.

The number of transactions committed.

Number of transactions in progress.

The total number of transactions since the service was started.

Transactions started per second.

The AppleTalk performance object consists of counters that monitor traffic on the AppleTalk network.

Performance information for one particular instance of 'AppleTalk' object.

Instance name.

Number of AARP packets per second received by Appletalk on this port.

Number of ATP At-least-once transaction responses per second on this port.

Number of ATP packets per second received by Appletalk on this port.

Number of ATP transaction release packets per second received on this port.

Number of ATP release timers that have expired on this port.

Number of ATP requests retransmitted on this port.

Number of ATP requests retransmitted to this port.

Number of ATP Exactly-once transaction responses per second on this port.

Average time in milliseconds to process an AARP packet on this port.

Average time in milliseconds to process an ATP packet on this port.

Average time in milliseconds to process a DDP packet on this port.

Average time in milliseconds to process an NBP packet on this port.

Average time in milliseconds to process an RTMP packet on this port.

Average time in milliseconds to process a ZIP packet on this port.

Number of bytes received per second by Appletalk on this port.

Number of bytes sent per second by Appletalk on this port.

The current amount of nonpaged memory resources used by AppleTalk.

Number of DDP packets per second received by Appletalk on this port.

Number of NBP packets per second received by Appletalk on this port.

Number of packets received per second by Appletalk on this port.

Number of packets sent per second by Appletalk on this port.

Number of packets routed in on this port.

Number of packets routed out on this port.

Number of packets dropped due to resource limitations on this port.

Number of RTMP packets per second received by Appletalk on this port.

Number of ZIP packets per second received by Appletalk on this port.

ASP.NET supports the following ASP.NET system performance counters. These aggregate information for all ASP.NET applications on a Web server computer, or they apply generally to a system of ASP.NET servers running the same applications. These can include Web farms and Web gardens.

Number of times the application has been restarted during the web server's lifetime.

Number of currently running web applications.

The number of milliseconds that it took to execute the most recent request.

The number of milliseconds the most recent request was waiting in the queue.

The current number of requests, including those that are queued, currently executing, or waiting to be written to the client. Under the ASP.NET process model, when this counter exceeds the requestQueueLimit defined in the processModel configuration section, ASP.NET will begin rejecting requests.

The number of requests disconnected due to communication errors or user terminated.

The number of requests waiting to be processed.

The number of requests rejected because the request queue was full.

The number of sessions that have been explicitly abandoned.

The current number of sessions currently active.

The number of sessions timed out.

The number of sessions total.

Number of times a worker process has restarted on the machine.

Number of worker processes running on the machine.

Number of audit failures in the application since it was started.

Number of audit successes in the application since it was started.

Number of error events raised since the application was started.

Number of HTTP error events raised since the application was started.

Number of runtime error events raised since the application was started.

ASP.NET supports the following application performance counters, which you can use to monitor the performance of a single instance of an ASP.NET application. A unique instance appears for these counters, named __Total__, which aggregates counters for all applications on a Web server (similar to the global counters described in the first section of this topic). The __Total__ instance is always available. The counters will display zero when no applications are present on the server.

Performance information for one particular instance of 'ASP.NET Applications' object.

Instance name.

Number of requests utilizing anonymous authentication.

Number of Authentication Anonymous Requests/Sec

Total number of entries within the cache added by the user.

Ratio of hits called from user code.

Number of cache hits from user code.

Number of cache misses called from user code.

Number of additions and removals to the API cache per second.

Total number of entries within the cache (both internal and user added)

Ratio of hits from all cache calls.

Total number of hits from the cache.

Total number of cache misses.

Number of additions and removals to the total cache per second.

Number of .asax, .ascx, .ashx, .asmx, or .aspx source files dynamically compiled.

Number of debugging requests processed.

Number of errors that have occurred during compilation.

Number of errors that have occurred during the processing of a request.

Number of errors that have occurred during parsing and configuration.

Total number of errors occurred.

Rate of errors occurred.

Number of errors not handled by user code, but by the default error handler.

Rate of unhandled errors.

Current number of entries in the output cache.

Ratio of hits to requests for output cacheable requests.

Total number of output cacheable requests served from the output cache.

Total number of output cacheable requests not served from the output cache.

Number of additions and removals to the output cache per second.

Number of active pipeline instances.

The total size, in bytes, of all requests.

The total size, in bytes, of responses sent to a client. This does not include standard HTTP response headers.

The number of requests currently executing.

Total number of failed requests.

The number of requests in the application request queue.

Number of requests failed due to unauthorized access.

The number of requests for resources that were not found.

The number of requests that executed successfully.

The number of requests that timed out.

The total number of requests since the application was started.

The number of requests executed per second.

The total number of connections to the SQL Server used by session state.

The total number of connections to the State Server used by session state.

The number of sessions that have been explicitly abandoned.

The current number of sessions currently active.

The number of sessions timed out.

Total number of sessions since the application was started.

The number of transactions aborted.

The number of transactions committed.

Number of transactions in progress.

The total number of transactions since the application was started.

Transactions started per second.

Number of application events raised since the application was started.

Number of application events raised per second.

Number of audit failures in the application since it was started.

Number of audit successes in the application since it was started.

Number of error events raised since the application was started.

Number of error events per second.

Total number of instrumentation events raised since the application was started.

Total number of instrumentation events per second.

Number of failed forms authentication ticket validations since the application was started.

Number of successful forms authentication ticket validations since the application was started.

Number of HTTP error events raised since the application was started.

Number of HTTP error events raised per second.

Number of failed membership credential validations since the application was started.

Number of successful membership credential validations since the application was started.

Number of runtime error events raised since the application was started.

Number of runtime error events per second.

Number of request events raised since the application was started

Number of request events raised per second.

The number of milliseconds that it took to execute the most recent request.

The number of milliseconds the most recent request was waiting in the queue.

The number of requests disconnected due to communication errors or user terminated.

The number of requests rejected because the application request queue was full.

Number of viewstate MAC validations that failed since the application was started.

The amount of physical memory used by the machine divided by the physical memory limit for the cache, as a percentage. When this reaches 100%, half of the cache entries will be forcibly removed. The __Total__ instance is the average of all instances, and therefore cannot be used to determine when cache entries will be forcibly removed.

The value of private bytes for the worker process divided by the private bytes memory limit for the cache, as a percentage. When this reaches 100%, half of the cache entries will be forcibly removed. The __Total__ instance is the average of all instances, and therefore cannot be used to determine when cache entries will be forcibly removed.

Total number of entries forcibly removed from the cache due to memory pressure that were originally inserted into the cache using one of the public cache APIs.

Total number of entries forcibly removed from the cache due to memory pressure.

Total number of entries forcibly removed from the cache due to memory pressure that were originally inserted into the cache by the output cache feature.

The Browser performance object consists of counters that measure the rates of announcements, enumerations, and other browser transmissions.

Announcements Domain/sec is the rate at which a domain has announced itself to the network.

Announcements Server/sec is the rate at which the servers in this domain have announced themselves to this server.

Announcements Total/sec is the sum of Announcements Server/sec and Announcements Domain/sec.

Duplicate Master Announcements indicates the number of times that the master browser has detected another master browser on the same domain.

Election Packets/sec is the rate at which browser election packets have been received by this workstation.

Enumerations Domain/sec is the rate at which domain browse requests have been processed by this workstation.

Enumerations Other/sec is the rate at which browse requests processed by this workstation are not domain or server browse requests.

Enumerations Server/sec is the rate at which server browse requests have been processed by this workstation.

Enumerations Total/sec is the rate at which browse requests have been processed by this workstation. This is the sum of Enumerations Server/sec, Enumerations Domain/sec, and Enumerations Other/sec.

Illegal Datagrams/sec is the rate at which incorrectly formatted datagrams have been received by the workstation.

Mailslot Allocations Failed is the number of times the datagram receiver has failed to allocate a buffer to hold a user mailslot write.

Mailslot Opens Failed/sec indicates the rate at which mailslot messages to be delivered to mailslots that are not present are received by this workstation.

Mailslot Receives Failed indicates the number of mailslot messages that could not be received due to transport failures.

Mailslot Writes Failed is the total number of mailslot messages that have been successfully received, but that could not be written to the mailslot.

Mailslot Writes/sec is the rate at which mailslot messages have been successfully received.

Missed Mailslot Datagrams is the number of Mailslot Datagrams that have been discarded due to configuration or allocation limits.

Missed Server Announcements is the number of server announcements that have been missed due to configuration or allocation limits.

Missed Server List Requests is the number of requests to retrieve a list of browser servers that were received by this workstation, but could not be processed.

Server Announce Allocations Failed/sec is the rate at which server (or domain) announcements have failed due to lack of memory.

Server List Requests/sec is the rate at which requests to retrieve a list of browser servers have been processed by this workstation.

The Cache performance object consists of counters that monitor the file system cache, an area of physical memory that stores recently used data as long as possible to permit access to the data without having to read from the disk. Because applications typically use the cache, the cache is monitored as an indicator of application input/output (I/O) operations. When memory is plentiful, the cache can grow, but when memory is scarce, the cache can become too small to be effective.

Async Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The application will regain control immediately even if the disk must be accessed to retrieve the page.

Async Data Maps/sec is the frequency that an application using a file system, such as NTFS, to map a page of a file into the file system cache to read the page, and does not wait for the page to be retrieved if it is not in main memory.

Async Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests will invoke the appropriate file system to retrieve data from a file, but this path permits data to be retrieved from the cache directly (without file system involvement) if the data is in the cache. Even if the data is not in the cache, one invocation of the file system is avoided. If the data is not in the cache, the request (application program call) will not wait until the data has been retrieved from disk, but will get control immediately.

Async MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the pages. The MDL contains the physical address of each page in the transfer, thus permitting Direct Memory Access (DMA) of the pages. If the accessed page(s) are not in main memory, the calling application program will not wait for the pages to fault in from disk.

Async Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. The file system will regain control immediately even if the disk must be accessed to retrieve the page. While pinned, a page's physical address will not be altered.

Copy Read Hits is the percentage of cache copy read requests that hit the cache, that is, they did not require a disk read in order to provide access to the page in the cache. A copy read is a file read operation that is satisfied by a memory copy from a page in the cache to the application's buffer. The LAN Redirector uses this method for retrieving information from the cache, as does the LAN Server for small transfers. This is a method used by the disk file systems as well.

Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The LAN Redirector uses this method for retrieving information from the file system cache, as does the LAN Server for small transfers. This is a method used by the disk file systems as well.

Data Flush Pages/sec is the number of pages the file system cache has flushed to disk as a result of a request to flush or to satisfy a write-through file write request. More than one page can be transferred on each flush operation.

Data Flushes/sec is the rate at which the file system cache has flushed its contents to disk as the result of a request to flush or to satisfy a write-through file write request. More than one page can be transferred on each flush operation.

Data Map Hits is the percentage of data maps in the file system cache that could be resolved without having to retrieve a page from the disk, because the page was already in physical memory.

Data Map Pins/sec is the frequency of data maps in the file system cache that resulted in pinning a page in main memory, an action usually preparatory to writing to the file on disk. While pinned, a page's physical address in main memory and virtual address in the file system cache will not be altered.

Data Maps/sec is the frequency that a file system such as NTFS, maps a page of a file into the file system cache to read the page.

Fast Read Not Possibles/sec is the frequency of attempts by an Application Program Interface (API) function call to bypass the file system to get to data in the file system cache that could not be honored without invoking the file system.

Fast Read Resource Misses/sec is the frequency of cache misses necessitated by the lack of available resources to satisfy the request.

Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests invoke the appropriate file system to retrieve data from a file, but this path permits direct retrieval of data from the cache without file system involvement if the data is in the cache. Even if the data is not in the cache, one invocation of the file system is avoided.

Lazy Write Flushes/sec is the rate at which the Lazy Writer thread has written to disk. Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding. More than one page can be transferred by each write operation.

Lazy Write Pages/sec is the rate at which the Lazy Writer thread has written to disk. Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding. More than one page can be transferred on a single disk write operation.

MDL Read Hits is the percentage of Memory Descriptor List (MDL) Read requests to the file system cache that hit the cache, i.e., did not require disk accesses in order to provide memory access to the page(s) in the cache.

MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the data. The MDL contains the physical address of each page involved in the transfer, and thus can employ a hardware Direct Memory Access (DMA) device to effect the copy. The LAN Server uses this method for large transfers out of the server.

Pin Read Hits is the percentage of pin read requests that hit the file system cache, i.e., did not require a disk read in order to provide access to the page in the file system cache. While pinned, a page's physical address in the file system cache will not be altered. The LAN Redirector uses this method for retrieving data from the cache, as does the LAN Server for small transfers. This is usually the method used by the disk file systems as well.

Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. While pinned, a page's physical address in the file system cache will not be altered.

Read Aheads/sec is the frequency of reads from the file system cache in which the Cache detects sequential access to a file. The read aheads permit the data to be transferred in larger blocks than those being requested by the application, reducing the overhead per access.

Sync Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The file system will not regain control until the copy operation is complete, even if the disk must be accessed to retrieve the page.

Sync Data Maps/sec counts the frequency that a file system, such as NTFS, maps a page of a file into the file system cache to read the page, and wishes to wait for the page to be retrieved if it is not in main memory.

Sync Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests invoke the appropriate file system to retrieve data from a file, but this path permits direct retrieval of data from the cache without file system involvement if the data is in the cache. Even if the data is not in the cache, one invocation of the file system is avoided. If the data is not in the cache, the request (application program call) will wait until the data has been retrieved from disk.

Sync MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the pages. The MDL contains the physical address of each page in the transfer, thus permitting Direct Memory Access (DMA) of the pages. If the accessed page(s) are not in main memory, the caller will wait for the pages to fault in from the disk.

Sync Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. The file system will not regain control until the page is pinned in the file system cache, in particular if the disk must be accessed to retrieve the page. While pinned, a page's physical address in the file system cache will not be altered.

The DHCP Server performance object provides counters for monitoring DHCP service activity. The DHCP service enables the server to perform as a DHCP server and configure DHCP-enabled client computers on your network as described in the DHCP standard. This object is available when the service is running. The following table describes the counters provided by the DHCP Server object and how to interpret the values when monitoring DHCP service performance.

Rate of DHCP Acks sent by the DHCP server.

The Number of packets in the processing queue of the DHCP server.

The Number of packets in the DHCP server queue waiting on conflict detection (ping).

Rate of DHCP Declines received by the DHCP server.

Rate of DHCP Discovers received by the DHCP server.

Duplicates Dropped/sec is the rate at which the DHCP server received duplicate packets.

Rate of DHCP Informs received by the DHCP server.

The average time per packet taken by the DHCP server to send a response.

Rate of DHCP Nacks sent by the DHCP server.

Rate of DHCP Offers sent out by the DHCP server.

Packets Expired/sec is the rate at which packets get expired in the DHCP server message queue.

Packets Received/sec is the rate at which packets are received by the DHCP server.

Rate of DHCP Releases received by the DHCP server.

Rate of DHCP Requests received by the DHCP server.

The Distributed Transaction Coordinator performance object provides statistics about Distributed Transaction Coordinator (MS DTC), part of Component Services (formerly known as Transaction Server) that coordinates external, or two-phase transactions. Among other things, MS DTC is used to coordinate two-phase transactions by Message Queuing.

Number of aborted transactions

Transactions aborted per second

Number of currently active transactions

Maximum number of transactions ever concurrently active

Number of committed transactions

Transactions committed per second

Number of transactions aborted by the system administrator

Number of transactions committed by the system administrator

Number of in doubt transactions

Average time delta between transaction begin and commit

Maximum time delta between transaction begin and commit

Minimum time delta between transaction begin and commit

Transactions performed per second

The DNS performance object provides counters for monitoring various areas of performance of the DNS service that enables client computers on your network to register and resolve DNS domain names. These names are used to find and access resources offered by other computers on your network or other networks, such as the Internet. The data reported by the DNS object includes the number of overall queries and responses processed by a DNS server, the number of DNS queries and responses processed using either the User Datagram Protocol (UDP) or the Transmission Control Protocol (TCP), the number of queries and responses that used recursion to look up and fully resolve DNS names on behalf of requesting clients, and the number of queries and responses made to servers using the WINS lookup integration features of the DNS service.

AXFR Request Received is the total number of full zone transfer requests received by the master DNS server.

AXFR Request Sent is the total number of full zone transfer requests sent by the secondary DNS server.

AXFR Response Received is the total number of full zone transfer responses received by the secondary DNS server.

AXFR Success Received is the total number of successful full zone transfers received by the secondary DNS server.

AXFR Success Sent is the total number of successful full zone transfers of the master DNS server.

Caching Memory is the total caching memory used by DNS server.

Database Node Memory is the total database node memory used by DNS server.

Dynamic Update NoOperation is the total number of No-operation/Empty dynamic update requests received by the DNS server.

Dynamic Update NoOperation/sec is the average number of No-operation/Empty dynamic update requests received by the DNS server in each second.

Dynamic Update Queued is the total number of dynamic updates queued by the DNS server.

Dynamic Update Received is the total number of dynamic update requests received by the DNS server.

Dynamic Update Received/sec is the average number of dynamic update requests received by the DNS server in each second.

Dynamic Update Rejected is the total number of dynamic updates rejected by the DNS server.

Dynamic Update TimeOuts is the total number of dynamic update timeouts of the DNS server.

Dynamic Update Written to Database is the total number of dynamic updates written to the database by the DNS server.

Dynamic Update Written to Database/sec is the average number of dynamic updates written to the database by the DNS server in each second.

IXFR Request Received is the total number of incremental zone transfer requests received by the master DNS server.

IXFR Request Sent is the total number of incremental zone transfer requests sent by the secondary DNS server.

IXFR Response Received is the total number of incrementalzone transfer responses received by the secondary DNS server.

IXFR Success Received is the total number of successful incremental zone transfers received by the secondary DNS server.

IXFR Success Sent is the total number of successful incremental zone transfers of the master DNS server.

IXFR TCP Success Received is the total number of successful TCP incremental zone transfers received by the secondary DNS server.

IXFR UDP Success Received is the total number of successful UDP incremental zone transfers received by the secondary DNS server.

Nbstat Memory is the total Nbstat memory used by DNS server.

Notify Received is the total number of notifies received by the secondary DNS server.

Notify Sent is the total number of notifies sent by the master DNS server.

Record Flow Memory is the total record flow memory used by DNS server.

Recursive Queries is the total number of recursive queries received by DNS server.

Recursive Queries/sec is the average number of recursive queries received by DNS server in each sencond.

Recursive Query Failure is the total number of recursive query failures.

Recursive Query Failure/sec is the average number of recursive query failures in each second.

Recursive TimeOuts is the total number of recursive query sending timeouts.

Recursive TimeOut/sec is the average number of recursive query sending timeouts in each second.

Secure Update Failure is the total number of secure updates failed of the DNS server.

Secure Update Received is the total number of secure update requests received by the DNS server.

Secure Update Received/sec is the average number of secure update requests received by the DNS server in each second.

TCP Message Memory is the total TCP message memory used by DNS server.

TCP Query Received is the total number of TCP queries received by DNS server.

TCP Query Received/sec is the average number of TCP queries received by DNS server in each second.

TCP Response Sent is the total number of TCP reponses sent by DNS server.

TCP Response Sent/sec is the average number of TCP reponses sent by DNS server in each second.

Total Query Received is the total number of queries received by DNS server.

Total Query Received/sec is the average number of queries received by DNS server in each second.

Total Response Sent is the total number of reponses sent by DNS server.

Total Response Sent/sec is the average number of reponses sent by DNS server in each second.

UDP Message Memory is the total UDP message memory used by DNS server.

UDP Query Received is the total number of UDP queries received by DNS server.

UDP Query Received/sec is the average number of UDP queries received by DNS server in each second.

UDP Response Sent is the total number of UDP reponses sent by DNS server.

UDP Response Sent/sec is the average number of UDP reponses sent by DNS server in each second.

WINS Lookup Received is the total number of WINS lookup requests received by the server.

WINS Lookup Received/sec is the average number of WINS lookup requests received by the server in each second.

WINS Response Sent is the total number of WINS lookup responses sent by the server.

WINS Response Sent/sec is the average number of WINS lookup responses sent by the server in each second.

WINS Reverse Lookup Received is the total number of WINS reverse lookup requests received by the server.

WINS Reverse Lookup Received/sec is the average number of WINS reverse lookup requests received by the server in each second.

WINS Reverse Response Sent is the total number of WINS Reverse lookup responses sent by the server.

WINS Reverse Response Sent/sec is the average number of WINS Reverse lookup responses sent by the server in each second.

Zone Transfer Failure is the total number of failed zone transfers of the master DNS server.

Zone Transfer Request Received is the total number of zone transfer requests received by the master DNS server.

Zone Transfer SOA Request Sent is the total number of zone transfer SOA requests sent by the secondary DNS server.

Zone Transfer Success is the total number of successful zone transfers of the master DNS server.

The Performance console .NET CLR Data category includes counters that provide information about the exceptions thrown by an application.

Performance information for one particular instance of '.NET CLR Data' object.

Instance name.

Current number of pools associated with the process.

Current number of connections, pooled or not.

Current number of connections in all pools associated with the process.

The highest number of connections in all pools since the process started.

The total number of command executes that have failed for any reason.

The total number of connection open attempts that have failed for any reason.

The Performance console .NET CLR Exceptions category includes counters that provide information about the exceptions thrown by an application.

Performance information for one particular instance of '.NET CLR Exceptions' object.

Instance name.

This counter displays the total number of exceptions thrown since the start of the application. These include both .NET exceptions and unmanaged exceptions that get converted into .NET exceptions e.g. null pointer reference exception in unmanaged code would get re-thrown in managed code as a .NET System.NullReferenceException; this counter includes both handled and unhandled exceptions. Exceptions that are re-thrown would get counted again. Exceptions should only occur in rare situations and not in the normal control flow of the program.

This counter displays the number of exceptions thrown per second. These include both .NET exceptions and unmanaged exceptions that get converted into .NET exceptions e.g. null pointer reference exception in unmanaged code would get re-thrown in managed code as a .NET System.NullReferenceException; this counter includes both handled and unhandled exceptions. Exceptions should only occur in rare situations and not in the normal control flow of the program; this counter was designed as an indicator of potential performance problems due to large (>100s) rate of exceptions thrown. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the number of .NET exception filters executed per second. An exception filter evaluates whether an exception should be handled or not. This counter tracks the rate of exception filters evaluated; irrespective of whether the exception was handled or not. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the number of finally blocks executed per second. A finally block is guaranteed to be executed regardless of how the try block was exited. Only the finally blocks that are executed for an exception are counted; finally blocks on normal code paths are not counted by this counter. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the number of stack frames traversed from the frame that threw the .NET exception to the frame that handled the exception per second. This counter resets to 0 when an exception handler is entered; so nested exceptions would show the handler to handler stack depth. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

The Performance console .NET CLR Interop category includes counters that provide information about an application's interaction with COM components, COM+ services, and external type libraries.

Performance information for one particular instance of '.NET CLR Interop' object.

Instance name.

This counter displays the current number of Com-Callable-Wrappers (CCWs). A CCW is a proxy for the .NET managed object being referenced from unmanaged COM client(s). This counter was designed to indicate the number of managed objects being referenced by unmanaged COM code.

This counter displays the current number of stubs created by the CLR. Stubs are responsible for marshalling arguments and return values from managed to unmanaged code and vice versa; during a COM Interop call or PInvoke call.

Reserved for future use.

Reserved for future use.

This counter displays the total number of times arguments and return values have been marshaled from managed to unmanaged code and vice versa since the start of the application. This counter is not incremented if the stubs are inlined. (Stubs are responsible for marshalling arguments and return values). Stubs usually get inlined if the marshalling overhead is small.

The Performance console .NET CLR JIT category includes counters that provide information about code that has been JIT-compiled.

Performance information for one particular instance of '.NET CLR Jit' object.

Instance name.

This counter displays the total IL bytes jitted since the start of the application. This counter is exactly equivalent to the 'Total # of IL Bytes Jitted' counter.

This counter displays the total number of methods compiled Just-In-Time (JIT) by the CLR JIT compiler since the start of the application. This counter does not include the pre-jitted methods.

This counter displays the percentage of elapsed time spent in JIT compilation since the last JIT compilation phase. This counter is updated at the end of every JIT compilation phase. A JIT compilation phase is the phase when a method and its dependencies are being compiled.

This counter displays the rate at which IL bytes are jitted per second. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the peak number of methods the JIT compiler has failed to JIT since the start of the application. This failure can occur if the IL cannot be verified or if there was an internal error in the JIT compiler.

This counter displays the total IL bytes jitted since the start of the application. This counter is exactly equivalent to the '# of IL Bytes Jitted' counter.

The Performance console .NET CLR Loading category includes counters that provide information about assemblies, classes, and application domains that are loaded.

Performance information for one particular instance of '.NET CLR Loading' object.

Instance name.

Reserved for future use.

Reserved for future use.

This counter displays the current size (in bytes) of the memory committed by the class loader across all AppDomains. (Committed memory is the physical memory for which space has been reserved on the disk paging file.)

This counter displays the current number of Assemblies loaded across all AppDomains in this application. If the Assembly is loaded as domain-neutral from multiple AppDomains then this counter is incremented once only. Assemblies can be loaded as domain-neutral when their code can be shared by all AppDomains or they can be loaded as domain-specific when their code is private to the AppDomain.

This counter displays the current number of classes loaded in all Assemblies.

This counter displays the current number of AppDomains loaded in this application. AppDomains (application domains) provide a secure and versatile unit of processing that the CLR can use to provide isolation between applications running in the same process.

This counter displays the number of Assemblies loaded across all AppDomains per second. If the Assembly is loaded as domain-neutral from multiple AppDomains then this counter is incremented once only. Assemblies can be loaded as domain-neutral when their code can be shared by all AppDomains or they can be loaded as domain-specific when their code is private to the AppDomain. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the number of classes loaded per second in all Assemblies. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the number of classes that failed to load per second. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval. These load failures could be due to many reasons like inadequate security or illegal format. Full details can be found in the profiling services help.

This counter displays the number of AppDomains loaded per second. AppDomains (application domains) provide a secure and versatile unit of processing that the CLR can use to provide isolation between applications running in the same process. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the number of AppDomains unloaded per second. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the peak number of classes that have failed to load since the start of the application. These load failures could be due to many reasons like inadequate security or illegal format. Full details can be found in the profiling services help.

This counter displays the peak number of AppDomains loaded since the start of this application. AppDomains (application domains) provide a secure and versatile unit of processing that the CLR can use to provide isolation between applications running in the same process.

This counter displays the total number of Assemblies loaded since the start of this application. If the Assembly is loaded as domain-neutral from multiple AppDomains then this counter is incremented once only. Assemblies can be loaded as domain-neutral when their code can be shared by all AppDomains or they can be loaded as domain-specific when their code is private to the AppDomain.

This counter displays the cumulative number of classes loaded in all Assemblies since the start of this application.

This counter displays the total number of AppDomains unloaded since the start of the application. If an AppDomain is loaded and unloaded multiple times this counter would count each of those unloads as separate.

The Performance console .NET CLR LocksAndThreads category includes counters that provide information about managed locks and threads that an application uses.

Performance information for one particular instance of '.NET CLR LocksAndThreads' object.

Instance name.

This counter displays the number of current .NET thread objects in the application. A .NET thread object is created either by new System.Threading.Thread or when an unmanaged thread enters the managed environment. This counters maintains the count of both running and stopped threads. This counter is not an average over time; it just displays the last observed value.

This counter displays the number of native OS threads created and owned by the CLR to act as underlying threads for .NET thread objects. This counters value does not include the threads used by the CLR in its internal operations; it is a subset of the threads in the OS process.

This counter displays the number of threads that are currently recognized by the CLR; they have a corresponding .NET thread object associated with them. These threads are not created by the CLR; they are created outside the CLR but have since run inside the CLR at least once. Only unique threads are tracked; threads with same thread ID re-entering the CLR or recreated after thread exit are not counted twice.

This counter displays the total number of threads that have been recognized by the CLR since the start of this application; these threads have a corresponding .NET thread object associated with them. These threads are not created by the CLR; they are created outside the CLR but have since run inside the CLR at least once. Only unique threads are tracked; threads with same thread ID re-entering the CLR or recreated after thread exit are not counted twice.

Rate at which threads in the runtime attempt to acquire a managed lock unsuccessfully. Managed locks can be acquired in many ways; by the 'lock' statement in C# or by calling System.Monitor.Enter or by using MethodImplOptions.Synchronized custom attribute.

This counter displays the total number of threads currently waiting to acquire some managed lock in the application. This counter is not an average over time; it displays the last observed value.

This counter displays the number of threads per second waiting to acquire some lock in the application. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the total number of threads that waited to acquire some managed lock since the start of the application.

This counter displays the total number of times threads in the CLR have attempted to acquire a managed lock unsuccessfully. Managed locks can be acquired in many ways; by the 'lock' statement in C# or by calling System.Monitor.Enter or by using MethodImplOptions.Synchronized custom attribute.

This counter displays the number of threads per second that have been recognized by the CLR; these threads have a corresponding .NET thread object associated with them. These threads are not created by the CLR; they are created outside the CLR but have since run inside the CLR at least once. Only unique threads are tracked; threads with same thread ID re-entering the CLR or recreated after thread exit are not counted twice. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

The Performance console .NET CLR Memory category includes counters that provide information about the garbage collector.

Performance information for one particular instance of '.NET CLR Memory' object.

Instance name.

This counter is the sum of four other counters; Gen 0 Heap Size; Gen 1 Heap Size; Gen 2 Heap Size and the Large Object Heap Size. This counter indicates the current memory allocated in bytes on the GC Heaps.

This counter displays the current number of GC Handles in use. GCHandles are handles to resources external to the CLR and the managed environment. Handles occupy small amounts of memory in the GCHeap but potentially expensive unmanaged resources.

This counter displays the number of times the generation 0 objects (youngest; most recently allocated) are garbage collected (Gen 0 GC) since the start of the application. Gen 0 GC occurs when the available memory in generation 0 is not sufficient to satisfy an allocation request. This counter is incremented at the end of a Gen 0 GC. Higher generation GCs include all lower generation GCs. This counter is explicitly incremented when a higher generation (Gen 1 or Gen 2) GC occurs. _Global_ counter value is not accurate and should be ignored. This counter displays the last observed value.

This counter displays the number of times the generation 1 objects are garbage collected since the start of the application. The counter is incremented at the end of a Gen 1 GC. Higher generation GCs include all lower generation GCs. This counter is explicitly incremented when a higher generation (Gen 2) GC occurs. _Global_ counter value is not accurate and should be ignored. This counter displays the last observed value.

This counter displays the number of times the generation 2 objects (older) are garbage collected since the start of the application. The counter is incremented at the end of a Gen 2 GC (also called full GC). _Global_ counter value is not accurate and should be ignored. This counter displays the last observed value.

This counter displays the peak number of times a garbage collection was performed because of an explicit call to GC.Collect. Its a good practice to let the GC tune the frequency of its collections.

This counter displays the amount of virtual memory (in bytes) currently committed by the Garbage Collector. (Committed memory is the physical memory for which space has been reserved on the disk paging file).

This counter displays the amount of virtual memory (in bytes) currently reserved by the Garbage Collector. (Reserved memory is the virtual memory space reserved for the application but no disk or main memory pages have been used.)

This counter displays the number of pinned objects encountered in the last GC. This counter tracks the pinned objects only in the heaps that were garbage collected e.g. a Gen 0 GC would cause enumeration of pinned objects in the generation 0 heap only. A pinned object is one that the Garbage Collector cannot move in memory.

This counter displays the current number of sync blocks in use. Sync blocks are per-object data structures allocated for storing synchronization information. Sync blocks hold weak references to managed objects and need to be scanned by the Garbage Collector. Sync blocks are not limited to storing synchronization information and can also store COM interop metadata. This counter was designed to indicate performance problems with heavy use of synchronization primitives.

% Time in GC is the percentage of elapsed time that was spent in performing a garbage collection (GC) since the last GC cycle. This counter is usually an indicator of the work done by the Garbage Collector on behalf of the application to collect and compact memory. This counter is updated only at the end of every GC and the counter value reflects the last observed value; its not an average.

This counter displays the rate of bytes per second allocated on the GC Heap. This counter is updated at the end of every GC; not at each allocation. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the number of garbage collected objects that survive a collection because they are waiting to be finalized. If these objects hold references to other objects then those objects also survive but are not counted by this counter; the 'Promoted Finalization-Memory from Gen 0' and 'Promoted Finalization-Memory from Gen 1' counters represent all the memory that survived due to finalization. This counter is not a cumulative counter; its updated at the end of every GC with count of the survivors during that particular GC only. This counter was designed to indicate the extra overhead that the application might incur because of finalization.

This counter displays the bytes per second that are promoted from generation 0 (youngest) to generation 1; objects that are promoted just because they are waiting to be finalized are not included in this counter. Memory is promoted when it survives a garbage collection. This counter was designed as an indicator of relatively long-lived objects being created per sec. This counter displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the maximum bytes that can be allocated in generation 0 (Gen 0); its does not indicate the current number of bytes allocated in Gen 0. A Gen 0 GC is triggered when the allocations since the last GC exceed this size. The Gen 0 size is tuned by the Garbage Collector and can change during the execution of the application. At the end of a Gen 0 collection the size of the Gen 0 heap is infact 0 bytes; this counter displays the size (in bytes) of allocations that would trigger the next Gen 0 GC. This counter is updated at the end of a GC; its not updated on every allocation.

This counter displays the bytes per second that are promoted from generation 1 to generation 2 (oldest); objects that are promoted just because they are waiting to be finalized are not included in this counter. Memory is promoted when it survives a garbage collection. Nothing is promoted from generation 2 since it is the oldest. This counter was designed as an indicator of very long-lived objects being created per sec. This counter displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the current number of bytes in generation 1 (Gen 1); this counter does not display the maximum size of Gen 1. Objects are not directly allocated in this generation; they are promoted from previous Gen 0 GCs. This counter is updated at the end of a GC; its not updated on every allocation.

This counter displays the current number of bytes in generation 2 (Gen 2). Objects are not directly allocated in this generation; they are promoted from Gen 1 during previous Gen 1 GCs. This counter is updated at the end of a GC; its not updated on every allocation.

This counter displays the current size of the Large Object Heap in bytes. Objects greater than 20 KBytes are treated as large objects by the Garbage Collector and are directly allocated in a special heap; they are not promoted through the generations. This counter is updated at the end of a GC; its not updated on every allocation.

This counter displays the bytes of memory that are promoted from generation 0 to generation 1 just because they are waiting to be finalized. This counter displays the value observed at the end of the last GC; its not a cumulative counter.

This counter displays the bytes of memory that are promoted from generation 1 to generation 2 just because they are waiting to be finalized. This counter displays the value observed at the end of the last GC; its not a cumulative counter. This counter is reset to 0 if the last GC was a Gen 0 GC only.

This counter displays the bytes of memory that survive garbage collection (GC) and are promoted from generation 0 to generation 1; objects that are promoted just because they are waiting to be finalized are not included in this counter. This counter displays the value observed at the end of the last GC; its not a cumulative counter.

This counter displays the bytes of memory that survive garbage collection (GC) and are promoted from generation 1 to generation 2; objects that are promoted just because they are waiting to be finalized are not included in this counter. This counter displays the value observed at the end of the last GC; its not a cumulative counter. This counter is reset to 0 if the last GC was a Gen 0 GC only.

This counter displays the process ID of the CLR process instance being monitored.

The Performance console .NET CLR Networking category includes counters that provide information about data that an application sends and receives over the network.

Performance information for one particular instance of '.NET CLR Networking' object.

Instance name.

The cumulative total number of bytes received over all open socket connections since the process was started. This number includes data and any protocol information that is not defined by the TCP/IP protocol.

The cumulative total number of bytes sent over all open socket connections since the process was started. This number includes data and any protocol information that is not defined by the TCP/IP protocol.

The cumulative total number of socket connections established for this process since the process was started.

The cumulative total number of datagram packets received since the process was started.

The cumulative total number of datagram packets sent since the process was started.

The Performance console .NET CLR Remoting category includes counters that provide information about the remoted objects that an application uses.

Performance information for one particular instance of '.NET CLR Remoting' object.

Instance name.

This counter displays the total number of remoting channels registered across all AppDomains since the start of the application. Channels are used to transport messages to and from remote objects.

This counter displays the total number of remoting proxy objects created in this process since the start of the process. Proxy object acts as a representative of the remote objects and ensures that all calls made on the proxy are forwarded to the correct remote object instance.

This counter displays the current number of context-bound classes loaded. Classes that can be bound to a context are called context-bound classes; context-bound classes are marked with Context Attributes which provide usage rules for synchronization; thread affinity; transactions etc.

This counter displays the number of context-bound objects allocated per second. Instances of classes that can be bound to a context are called context-bound objects; context-bound classes are marked with Context Attributes which provide usage rules for synchronization; thread affinity; transactions etc. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the current number of remoting contexts in the application. A context is a boundary containing a collection of objects with the same usage rules like synchronization; thread affinity; transactions etc.

This counter displays the number of remote procedure calls invoked per second. A remote procedure call is a call on any object outside the caller;s AppDomain. This counter is not an average over time; it displays the difference between the values observed in the last two samples divided by the duration of the sample interval.

This counter displays the total number of remote procedure calls invoked since the start of this application. A remote procedure call is a call on any object outside the caller;s AppDomain.

The Performance console .NET CLR Security category includes counters that provide information about the security checks that the common language runtime performs for an application.

Performance information for one particular instance of '.NET CLR Security' object.

Instance name.

This counter displays the total number of linktime Code Access Security (CAS) checks since the start of the application. Linktime CAS checks are performed when a caller makes a call to a callee demanding a particular permission at JIT compile time; linktime check is performed once per caller. This count is not indicative of serious performance issues; its indicative of the security system activity.

Reserved for future use.

This counter displays the percentage of elapsed time spent in performing runtime Code Access Security (CAS) checks since the last such check. CAS allows code to be trusted to varying degrees and enforces these varying levels of trust depending on code identity. This counter is updated at the end of a runtime security check; it represents the last observed value; its not an average.

This counter displays the depth of the stack during that last runtime Code Access Security check. Runtime Code Access Security check is performed by crawling the stack. This counter is not an average; it just displays the last observed value.

This counter displays the total number of runtime Code Access Security (CAS) checks performed since the start of the application. Runtime CAS checks are performed when a caller makes a call to a callee demanding a particular permission; the runtime check is made on every call by the caller; the check is done by examining the current thread stack of the caller. This counter used together with 'Stack Walk Depth' is indicative of performance penalty for security checks.

The FileReplicaConn performance object displays performance statistics of the REPLICACONN object that defines replica connections to distributed file system (Dfs) roots.

Performance information for one particular instance of 'FileReplicaConn' object.

Instance name.

The number of successful authentication checks made on packets received from the partner associated with this connection.

The cumulative number of authentication check failures detected on packets received from the partner associated with this connection.

The number of successful RPC bind requests to the FRS server on the partner associated with this connection.

The cumulative number of unsuccessful RPC bind requests to the FRS server on the partner associated with this connection.

The cumulative number of times a communication request has taken too long to the partner associated with this connection.

The number of blocks of staging file data received from the partner associated with this connection. The underlying transport may break a block into a smaller number of packets on the wire.

The number of bytes of staging file data received from the partner associated with this connection.

The number of blocks of staging file data sent to the partner associated with this connection. The underlying transport may break a block into a smaller number of packets on the wire.

The number of bytes of staging file data sent to the partner associated with this connection.

The number of staging files received from the partner associated with this connection.

The number of staging files requested from the partner associated with this connection.

The number of change orders received from the partner associated with this connection that have been filtered out by the inbound dampening check.

The number of partner join notifications received from the partner associated with this connection.

The number of partner join requests (if this is an inbound connection) or ready-to-join notifications (if this is an outbound connection) sent to the partner associated with this connection.

The number of successful joins with the partner associated with this connection.

The number of locally originated replication change orders that have been sent to the partner associated with this connection.

The number of locally originated replication change orders produced by a partner induced version vector scan that have been sent to the partner associated with this connection.

The number of change orders sent to the partner associated with this connection that have been filtered out by the outbound dampening check and thus were never sent.

The total number of FRS data and control packets sent to the partner associated with this connection.

The total number of FRS data and control bytes sent to the partner associated with this connection.

The cumulative number of FRS data or control packets not sent because of some error condition associated with this connection.

The number of change orders received from the partner associated with this connection that have passed the inbound dampening check.

The number of replication change orders originating upstream from this member (i.e. remote) that have been sent to the partner associated with this connection.

The number of unjoins with the partner associated with this connection.

The FileReplicaSet performance object displays performance statistics of the REPLICASET object that defines a replica set (one or more replicas, shared volumes or directories that store duplicates of the contents of an original share). The object reports statistics for the computer that constitutes the original share. For example, in a bidirectional ring topology of three computers A, B, and C, where computer A and computer C both replicate from computer B, the FileReplicaSet counters would provide data for computer B.

Performance information for one particular instance of 'FileReplicaSet' object.

Instance name.

The number of successful authentication checks made on packets received from any partner associated with this replica set member.

The cumulative number of authentication check failures detected on packets received from any partner associated with this replica set member.

The number of successful RPC bind requests to the FRS server on any partner associated with this replica set member.

The cumulative number of unsuccessful RPC bind requests to the FRS server on any partner associated with this replica set member.

The total number of bytes of staging file data that have been installed on this replica set member.

The total number of bytes of staging file data received by this replica set member from its inbound partners.

The total number of bytes of staging file data generated by this replica set member not including the number of bytes produced as part of regeneration.

The total number of bytes of staging file data regenerated by this replica set member for a specific outbound partner request.

The number of local plus remote file updates that were aborted on this replica set member.

The number of local file updates that were never processed because the underlying file was deleted first.

The number of local plus remote file updates initiated on this replica set member.

The number of local plus remote file updates that encountered a name space collision on this replica set member.

The number of local plus remote file updates that were propagated to the outbound log of this replica set member. The update remains pending in the outbound log until it has been delivered to all outbound partners.

The number of local plus remote file updates that have been received by this replica set member. Note that depending on the replication topology it is possible for the same remote file update to be sent from multiple inbound partners. However, only one will send the actual file data.

The number of local plus remote file updates retired on this replica set member.

The number of local plus remote file updates that were retried for any reason on this replica set member.

The number of local plus remote file updates that were retried due to a stage file fetch problem on this replica set member.

The number of local plus remote file updates that were retried due to a stage file generation problem on this replica set member.

The number of local plus remote file updates that were retried due to a stage file install problem on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory.

The number of local plus remote file updates that were retried due to a problem during the final target file rename or delete operation on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory.

The number of local plus remote file updates that have been sent to the outbound partners of this replica set member.

The cumulative number of FRS data or control packets not sent to an outbound partner because the send request timed out.

The number of times FRS has attempted to acquire a binding handle to the active directory.

The cumulative number of attempts to acquire a binding handle to the active directory that failed with some error status.

The number of FRS configuration Objects retreived from the directory service.

The cumulative count of FRS configuration objects retreived from the directory service that were missing either the distinguished name, object GUID or the relative distinguished name attributes.

The number of times FRS has polled the active directory for FRS configuration information on this computer.

The number of times FRS has polled the active directory for FRS configuration information and configuration changes were found.

The number of times FRS has polled the active directory for FRS configuration information and no configuration changes were found.

The number of times FRS has made a search request to the active directory.

The cumulative number of times FRS has made a search request to the active directory and the request returned with an error condition.

The number of blocks of staging file data received from all inbound partners associated with this replica set member. The underlying transport may break a block into a smaller number of packets on the wire.

The total number of bytes of staging file data received by this replica set member from all inbound partners.

The number of blocks of staging file data sent to any outbound partner associated with this replica set member. The underlying transport may break a block into a smaller number of packets on the wire.

The total number of bytes of staging file data sent to the outbound partners of this replica set member.

The number of staging files received from all inbound partners associated with this replica set member.

The number of staging files requested from any inbound partner associated with this replica set member.

The number of file updates and deletes performed on this replica set member.

The cumulative number of file updates that were aborted because of some non-recoverable error.

The number of remotely originated file updates that were dampened because the update was already delivered by another member.

The number of partner join notifications received from all inbound partners associated with this replica set member.

The number of inbound partner join requests or outbound partner ready-to-join notifications sent to all partners associated with this replica set member.

The number of successful joins with any partner associated with this replica set member.

The amount of staging space (in Kilobyte units) currently available within the staging space limit. Note that there may not actually be this amount of free space left on the staging volume.

The amount of staging space (in Kilobyte units) currently in use.

The number of locally originated file updates that were aborted. Most likely because a file was deleted before a change to it could be propagated so no stage file could be generated.

The number of locally originated file updates initiated on this replica set member.

The number of locally originated file updates that encountered a name space collision on this replica set member. Most likely caused by the reanimation of a parent dir.

The number of locally originated file updates that were propagated to the outbound log of this replica set member. The update remains pending in the outbound log until it has been delivered to all outbound partners.

The number of locally originated file updates retired on this replica set member.

The number of locally originated file updates that were retried for any reason on this replica set member.

The number of locally originated file updates that were retried due to a stage file fetch problem on this replica set member.

The number of locally originated file updates that were retried due to a stage file generation problem on this replica set member. Most likely caused by a sharing conflict trying to access the target file.

The number of locally originated file updates that were retried due to a stage file install problem on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory.

The number of locally originated file updates that were retried due to a problem during the final target file rename or delete operation on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory.

The number of locally originated file updates that have been sent to the outbound partners of this replica set member.

The number of locally originated file updates which were created by a partner induced version vector scan that have been sent to the outbound partners of this replica set member.

The number of pending outbound file updates that were dampened because the outbound partner has already received it from another source.

The number of FRS data or control packets (RPC calls) received by FRS.

The total number of FRS data and control bytes received by all replica sets on this computer.

The cumulative number of FRS data or control packets received that were out of rev or otherwise malformed.

The number of FRS data and control packets sent to all outbound partners associated with this replica set member.

The total number of FRS data and control bytes sent by this replica set member to other members.

The cumulative number of FRS data or control packets not sent to an outbound partner because of some error condition.

The number of remotely originated file updates that were aborted. Most likely because of an attempt to fetch a staging file from an inbound partner and the partner no longer has the file because it has been deleted.

The number of remotely originated file updates initiated on this replica set member.

The number of remotely originated file updates that encountered a name space collision on this replica set member. Most likely caused by simultaneous create of a file or directory with the same name on more than one replica set member.

The number of remotely originated file updates that were propagated to the outbound log of this replica set member. The update remains pending in the outbound log until it has been delivered to all outbound partners.

The number of remotely originated file updates that have been received by this replica set member. Note that depending on the replication topology it is possible for the same file update to be sent from multiple inbound partners. However, only one will send the actual file data.

The number of remotely originated file updates retired on this replica set member.

The number of remotely originated file updates that were retried for any reason on this replica set member.

The number of remotely originated file updates that were retried due to a stage file fetch problem on this replica set member.

The number of remotely originated file updates that were retried due to a stage file generation problem on this replica set member.

The number of remotely originated file updates that were retried due to a stage file install problem on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory.

The number of remotely originated file updates that were retried due to a problem during the final target file rename or delete operation on this replica set member. Most likely caused by a sharing conflict trying to access the target file or directory.

The number of remotely originated file updates that have been sent to the outbound partners of this replica set member.

The cumulative number of replica sets to which this computer has been added as a member.

The cumulative number of replica sets from which this computer's membership has been provisionally deleted, but could still be reanimated.

The cumulative number of replica sets from which this computer's membership has been permanently deleted.

The number of replica sets for which processing has been started.

The number of staging files requested by this replica set member.

The number of staging files generated by this replica set member.

The cumulative number of staging files generated by this replica set member where an error was detected during generation.

The number of staging files regenerated by this replica set member for a specific outbound partner request.

The number of execution threads that have terminated.

The number of new execution threads started.

The number of unjoins with any partner associated with this replica set member.

The number of times FRS has initiated a read on the NTFRS change log. Each volume has its own change log.

The number of NTFS change log records accepted by FRS for further processing.

The number of NTFS change log records examined by FRS.

The number of NTFS change log records skipped by FRS. Most likely because the change log record was for a file not part of any active replica set.

The FTP Service performance object consists of counters that show data about the Internet Information Services FTP service.

Performance information for one particular instance of 'FTP Service' object.

Instance name.

Bytes Received/sec is the rate that data bytes are received by the FTP service.

Bytes Sent/sec is the rate that data bytes are sent by the FTP service.

Bytes Total/sec is the sum of Bytes Sent/sec and Bytes Received/sec. This is the total rate of bytes transferred by the FTP service.

Current Anonymous Users is the number of users who currently have an anonymous connection using the FTP service.

Current Connections is the current number of connections established with the FTP service.

Current NonAnonymous Users is the number of users who currently have a non-anonymous connection using the FTP service.

FTP Serive and FTP site uptime in seconds.

Maximum Anonymous Users is the maximum number of users who established concurrent anonymous connections using the FTP service (since service startup).

Maximum Connections is the maximum number of simultaneous connections established with the FTP service.

Maximum NonAnonymous Users is the maximum number of users who established concurrent non-anonymous connections using the FTP service (since service startup).

Total Anonymous Users is the total number of users who established an anonymous connection with the FTP service (since service startup).

Total Connection Attempts is the number of connections that have been attempted using the FTP service (since service startup). This counter is for all instances listed.

Total Files Received is the total number of files received by the FTP service since service startup.

Total Files Sent is the total number of files sent by the FTP service since service startup.

Total Files Transferred is the sum of Files Sent and Files Received. This is the total number of files transferred by the FTP service since service startup.

Total Logon Attempts is the number of logons that have been attempted using the FTP service (since service startup).

Total NonAnonymous Users is the total number of users who established a non-anonymous connection with the FTP service (since service startup).

The Gateway for NetWare Service performance object consists of counters that measure packet transmission rates and activity of the Gateway for NetWare service.

Bytes Received/sec is the rate of bytes coming in to the Redirector from the network. It includes all application data as well as network protocol information (such as packet headers).

Bytes Total/sec is the rate the Redirector is processing data bytes. This includes all application and file data in addition to protocol information such as packet headers.

Bytes Transmitted/sec is the rate at which bytes are leaving the Redirector to the network. It includes all application data as well as network protocol information (such as packet headers and the like).

Connect NetWare 2.x counts connections to NetWare 2.x servers.

Connect NetWare 3.x counts connections to NetWare 3.x servers.

Connect NetWare 4.x counts connections to NetWare 4.x servers.

File Data Operations/sec is the rate the Redirector is processing data operations. One operation includes (hopefully) many bytes. We say hopefully here because each operation has overhead. You can determine the efficiency of this path by dividing the Bytes/sec by this counter to determine the average number of bytes transferred/operation.

File Read Operations/sec is the rate at which applications are asking the Redirector for data. Each call to a file system or similar Application Program Interface (API) call counts as one operation.

File Write Operations/sec is the rate at which applications are sending data to the Redirector. Each call to a file system or similar Application Program Interface (API) call counts as one operation.

Packet Burst IO/sec is the sum of Packet Burst Read NCPs/sec and Packet Burst Write NCPs/sec.

Packet Burst Read NCP Count/sec is the rate of NetWare Core Protocol requests for Packet Burst Read. Packet Burst is a windowing protocol that improves performance.

Packet Burst Read Timeouts/sec is the rate the NetWare Service needs to retransmit a Burst Read Request because the NetWare server took too long to respond.

Packet Burst Write NCP Count/sec is the rate of NetWare Core Protocol requests for Packet Burst Write. Packet Burst is a windowing protocol that improves performance.

Packet Burst Write Timeouts/sec is the rate the NetWare Service needs to retransmit a Burst Write Request because the NetWare server took too long to respond.

Packets Received/sec is the rate at which the Redirector is receiving packets (also called SMBs or Server Message Blocks). Network transmissions are divided into packets. The average number of bytes received in a packet can be obtained by dividing Bytes Received/sec by this counter. Some packets received might not contain incoming data, for example an acknowledgment to a write made by the Redirector would count as an incoming packet.

Packets Transmitted/sec is the rate at which the Redirector is sending packets (also called SMBs or Server Message Blocks). Network transmissions are divided into packets. The average number of bytes transmitted in a packet can be obtained by dividing Bytes Transmitted/sec by this counter.

Packets/sec is the rate the Redirector is processing data packets. One packet includes (hopefully) many bytes. We say hopefully here because each packet has protocol overhead. You can determine the efficiency of this path by dividing the Bytes/sec by this counter to determine the average number of bytes transferred/packet. You can also divide this counter by Operations/sec to determine the average number of packets per operation, another measure of efficiency.

Read Operations Random/sec counts the rate at which, on a file-by-file basis, reads are made that are not sequential. If a read is made using a particular file handle, and then is followed by another read that is not immediately the contiguous next byte, this counter is incremented by one.

Read Packets/sec is the rate at which read packets are being placed on the network. Each time a single packet is sent with a request to read data remotely, this counter is incremented by one.

Server Disconnects counts the number of times a Server has disconnected your Redirector. See also Server Reconnects.

Server Reconnects counts the number of times your Redirector has had to reconnect to a server in order to complete a new active request. You can be disconnected by the Server if you remain inactive for too long. Locally even if all your remote files are closed, the Redirector will keep your connections intact for (nominally) ten minutes. Such inactive connections are called Dormant Connections. Reconnecting is expensive in time.

Server Sessions counts the total number of security objects the Redirector has managed. For example, a logon to a server followed by a network access to the same server will establish one connection, but two sessions.

Write Operations Random/sec is the rate at which, on a file-by-file basis, writes are made that are not sequential. If a write is made using a particular file handle, and then is followed by another write that is not immediately the next contiguous byte, this counter is incremented by one.

Write Packets/sec is the rate at which writes are being sent to the network. Each time a single packet is sent with a request to write remote data, this counter is incremented by one.

The IAS Accounting Clients performance object is installed by the Internet Authentication Service (IAS). IAS uses the Remote Authentication Dial-In User Service (RADIUS) protocol to perform remote authentication. IAS performance objects report activity for servers or clients, including user authentication, authorization, and accounting (usage).

Performance information for one particular instance of 'IAS Accounting Clients' object.

Instance name.

Shows the number of packets received from this client on the accounting port.

Shows the rate, in seconds, at which packets were received from this client on the accounting port.

Shows the number of RADIUS Accounting-Response packets sent to this client.

Shows the rate in seconds at which duplicate RADIUS Accounting-Request packets were received from this client.

Shows the number of packets that contained invalid Signature attributes.

Shows the rate, in seconds, at which packets that contained invalid Signature attributes were received.

Shows the number of incoming packets silently discarded for a reason other than being malformed, bad authenticators, or unknown types.

Shows the rate in seconds at which incoming packets were silently discarded for a reason other than being malformed, bad authenticators, or unknown types.

Shows the number of duplicate RADIUS Accounting-Request packets received from this client.

Shows the rate, in seconds, at which duplicate RADIUS Accounting-Request packets were received from this client.

Shows the number of malformed packets received. Bad authenticators or unknown types are not included.

Shows the rate, in seconds, at which malformed packets were received.

Shows the number of RADIUS Accounting-Request packets that were received and responded to but not recorded.

Shows the rate, in seconds, at which RADIUS Accounting-Request packets were received and responded to but not recorded.

Shows the number of packets received.

Shows the rate, in seconds, at which packets were received.

Shows the number of packets sent.

Shows the rate, in seconds, at which packets were sent.

Shows the number of packets of unknown type that were received. An unknown type is a RADIUS packet that contains an unrecognized entry in the Code field, used to identify the packet type. Consequently IAS does not support packets of unknown type.

Shows the rate, in seconds, at which packets of unknown type were received.

The number of RADIUS Accounting-Request packets received on the accounting port.

The average number of RADIUS Accounting-Request packets sent per second to the accounting port.

The number of RADIUS Accounting-Response packets received on the accounting port.

The average number of RADIUS Accounting-Response packets received per second on the accounting port.

The number of RADIUS packets that contain an invalid Message Authenticator attribute.

The average number of RADIUS packets per second that contain an invalid Message Authenticator attribute.

The number of incoming packets that are silently discarded for a reason other than 'malformed,' 'invalid Message Authenticator,' or 'unknown type'.

The average number of incoming packets per second that are silently discarded for a reason other than 'malformed,' 'invalid Message Authenticator,' or 'unknown type'.

The number of packets received from unknown addresses.

The average number of packets per second received from unknown addresses.

The number of packets containing malformed data received.

The average number of packets containing malformed data received per second.

The number of packets received.

The average number of packets received per second.

The number of requests destined for this server that have not yet timed out or received a response.

The number of request timeouts to this server.

The average number of request timeouts per second to this server.

The number of requests retransmitted to this server.

The average number of requests retransmitted per second to this server.

The number of unknown type (non-RADIUS) packets received.

The average number of unknown type (non-RADIUS) packets received per second.

The IAS Accounting Server performance object is installed by the IAS. IAS uses the RADIUS protocol to perform remote authentication. IAS performance objects report activity for servers or clients, including user authentication, authorization, and accounting (usage).

The number of packets received from this client on the accounting port.

The number of packets per second received from this client on the accounting port.

The number of RADIUS Accounting-Response packets sent to this client.

The number of RADIUS Accounting-Response packets per second sent to this client.

The number of packets which contained invalid Signature attributes.

The number of packets per second which contained invalid Signature attributes.

The number of incoming packets silently discarded for a reason other than malformed, bad authenticators, or unknown types.

The number of incoming packets per second silently discarded for a reason other than malformed, bad authenticators, or unknown types.

The number of duplicate RADIUS Accounting-Request packets received from this client.

The number of duplicate RADIUS Accounting-Request packets per second received from this client.

The number of packets received from unknown addresses.

The number of packets received per second from unknown addresses.

The number of malformed packets received. Bad authenticators or unknown types are not included.

The number of malformed packets per second received. Bad authenticators or unknown types are not included.

The number of RADIUS Accounting-Request packets which were received and responded to but not recorded.

The number of RADIUS Accounting-Request packets per second which were received and responded to but not recorded.

The number of packets received.

The number of packets per second received.

The number of packets sent.

The number of packets sent per second.

The time elapsed (in hundredths of a second) since the server configuration was reset.

The time elapsed (in hundredths of a second) since the server process was started.

The number of packets of unknown type which were received.

The number of packets per second of unknown type which were received.

The IAS Authentication Clients performance object is installed by IAS. IAS uses the RADIUS protocol to perform remote authentication. IAS performance objects report activity for servers or clients, including user authentication, authorization, and accounting (usage).

Performance information for one particular instance of 'IAS Authentication Clients' object.

Instance name.

Access-Accepts

Access-Accepts / sec.

Access-Challenges

Access-Challenges / sec.

Access-Rejects

Access-Rejects / sec.

Access-Requests

Access-Requests / sec.

Bad Authenticators

Bad Authenticators / sec.

Dropped Packets

Dropped Packets / sec.

Duplicate Access-Requests

Duplicate Access-Requests / sec.

Malformed Packets

Malformed Packets / sec.

Packets Received

Packets Received / sec.

Packets Sent

Packets Sent / sec.

Unknown Type

Unknown Type / sec.

The number of RADIUS Access-Accept packets received from this server.

The average number of RADIUS Access-Accept packets per second received from this server.

The number of RADIUS Access-Challenge packets received from this server.

The average number of RADIUS Access-Challenge packets per second received from this server.

The number of RADIUS Access-Reject packets received from this server.

The average number of RADIUS Access-Reject packets per second received from this server.

The number of RADIUS Access-Request packets sent to this server.

The average number of RADIUS Access-Request packets per second sent to this server.

The number of RADIUS packets that contain an invalid Message Authenticator attribute.

The average number of RADIUS packets per second that contain an invalid Message Authenticator attribute.

The number of incoming packets that are silently discarded for a reason other than 'malformed,' 'invalid Message Authenticator,' or 'unknown type'.

The average number of incoming packets per second that are silently discarded for a reason other than 'malformed,' 'invalid Message Authenticator,' or 'unknown type'.

The number of packets received from unknown addresses.

The average number of packets per second received from unknown addresses.

The number of packets containing malformed data received.

The average number of packets containing malformed data received per second.

The number of packets received.

The average number of packets received per second.

The number of requests destined for this server that have not yet timed out or received a response.

The number of request timeouts to this server.

The average number of request timeouts per second to this server.

The number of requests retransmitted to this server.

The average number of requests retransmitted per second to this server.

The number of unknown type (non-RADIUS) packets received.

The average number of unknown type (non-RADIUS) packets received per second.

The IAS Authentication Server performance object is installed by IAS. IAS uses the RADIUS protocol to perform remote authentication. IAS performance objects report activity for servers or clients, including user authentication, authorization, and accounting (usage).

The number of RADIUS Access-Accept packets sent to this client.

The number of RADIUS Access-Accept packets per second sent to this client.

The number of RADIUS Access-Challenge packets sent to this client.

The number of RADIUS Access-Challenge packets per second sent to this client.

The number of RADIUS Access-Reject packets sent to this client.

The number of RADIUS Access-Reject packets per second sent to this client.

The number of packets received on the authentication port from this client.

The number of packets per second received on the authentication port from this client.

The number of packets which contained invalid Signature attributes.

The number of packets per second which contained invalid Signature attributes.

The number of incoming packets silently discarded for a reason other than malformed, bad authenticators, or unknown types.

The number of incoming packets per second silently discarded for a reason other than malformed, bad authenticators, or unknown types.

The number of duplicate RADIUS Access-Request packets received from this client.

The number of duplicate RADIUS Access-Request packets per second received from this client.

The number of packets received from unknown addresses.

The number of packets received per second from unknown addresses.

The number of malformed packets received. Bad authenticators or unknown types are not included.

The number of malformed packets per second received. Bad authenticators or unknown types are not included.

The number of packets received.

The number of packets per second received.

The number of packets sent.

The number of packets sent per second.

The time elapsed (in hundredths of a second) since the server configuration was reset.

The time elapsed (in hundredths of a second) since the server process was started.

The number of packets of unknown type which were received.

The number of packets per second of unknown type which were received.

A table containing performance information for instances of 'IAS Remote Accounting Servers' objects.

Performance information for one particular instance of 'IAS Remote Accounting Servers' object.

Instance name.

The number of RADIUS Accounting-Request packets received on the accounting port.

The average number of RADIUS Accounting-Requests received per second on the accounting port.

The number of RADIUS Accounting-Response packets sent from this IAS server.

The average number of RADIUS Accounting-Responses sent per second.

The number of RADIUS packets that contain an invalid Message Authenticator attribute.

The average number of RADIUS packets per second that contain an invalid Message Authenticator attribute.

The number of incoming packets that are silently discarded for a reason other than 'malformed,' 'invalid Message Authenticator,' or 'unknown type'.

The average number of incoming packets per second that are silently discarded for a reason other than 'malformed,' 'invalid Message Authenticator,' or 'unknown type'.

The interval (in hundredths of a second) between the most recent request from a remote IAS server and its response.

The number of packets containing malformed data received.

The average number of packets containing malformed data received per second.

The number of packets received.

The average number of packets received per second.

The number of requests destined for this server that have not yet timed out or received a response.

The UDP port the proxy is using to send requests to this server.

The number of request timeouts to this server.

The average number of request timeouts per second to this server.

The number of requests retransmitted to this server.

The average number of requests retransmitted per second to this server.

The number of unknown type (non-RADIUS) packets received.

The average number of unknown type (non-RADIUS) packets received per second.

A table containing performance information for instances of 'IAS Remote Authentication Servers' objects.

Performance information for one particular instance of 'IAS Remote Authentication Servers' object.

Instance name.

The number of RADIUS Access-Accept packets sent.

The average number of RADIUS Access-Accept packets per second sent.

The number of RADIUS Access-Challenge packets sent.

The average number of RADIUS Access-Challenge packets per second sent.

The number of RADIUS Access-Reject packets sent to this client.

The average number of RADIUS Access-Reject packets per second sent.

The number of packets received on the authentication port.

The average number of packets per second received on the authentication port.

The number of RADIUS packets that contain an invalid Message Authenticator attribute.

The average number of RADIUS packets per second that contain an invalid Message Authenticator attribute.