Overview

Performance counters and information for managing the counters are available through two interfaces:

Cisco Real-Time Monitoring Tool
PerfMon API

The Cisco Real-Time Monitoring Tool (RTMT) provides all the counters in a tabular view to allow monitoring and management of all performance issues.

For information on how to install and configure RTMT and turn on monitoring services and monitor performance on Cisco Unified Communications Manager (Cisco Unified CM), see the Cisco Unified CM RTMT Administration Guide.

The Performance Monitoring API, also referred to as PerfMon, provides real-time event feeds to monitor the status and health of Cisco Unified CM. The PerfMon API is explained in this document.

Use the PerfMon WSDL:
https://ServerName:8443/perfmonservice2/services/PerfmonService?wsdl

Replace the ServerName with the Cisco Unified CM server name or IP address.

Performance Monitoring (PerfMon)

Performance monitoring provides real-time event information to monitor the status and health of Cisco Unified CM hardware and software.

PerfMon allows clients to perform the following tasks:

Collect and monitor PerfMon performance data either session-based or single-transaction
Retrieve a list of all PerfMon objects and counter names installed on a particular host
Retrieve a list of the current instances of a PerfMon object
Retrieve textual description of a PerfMon counter

This API returns a snapshot of the performance counters for all instances of an object on the specified host.

Session Based Performance Monitoring

Client programs use the perfmonOpenSession request to obtain a session handle. The client needs a session handle to do session-based PerfMon counter data collection. The session handle is a unique identifier the application reuses for subsequent requests.

Use perfmonOpenSession to open a session and create a unique session identifier which will be used to manage subsequent PerfMon API requests. perfmonOpenSession takes no parameters. perfmonOpenSession returns a single element named SessionHandle. SessionHandle is a character string of xsd:string type, and contains the value of the session handle. The session handle represents a unique identifier which is used once to guarantee no duplicate handles exist. The opened session handles are kept in the cache. If no activity occurs on a handle for 25 hours, the handle is removed and rendered invalid.

In session-based PerfMon data collection, use the following related operations:

1. perfmonOpenSession
2. perfmonAddCounter
3. perfmonRemoveCounter
4. perfmonCollectSessionData
5. perfmonCloseSession

After the client application gets a session handle, add a counter with perfmonAddCounterand then follow with perfmonCollectSessionData. This collects the performance data requested.

Clients can dynamically add and remove counters to the session handle by using perfmonAddCounter and perfmonRemoveCounter while the session handle is still open.

When the client no longer needs the session handle, use perfmonCloseSession and the session handle is removed from the cache.

Single Transaction Based Performance Monitoring

Performance counters that return percentage values require two or more samples to calculate performance counter changes.

Percentage counters can be retrieved in a single transaction, but will not be accurate.

Examples of Counters

The PerfMon API provides a large number of objects and counters to use in an application.

For an idea of the types of performance monitoring available to an application, below is a partial list of counters and their associated objects.

Object	Examples
Memory Object	% Page Usage, % VM Used, % Mem Used, Buffers Kbytes, Cached Kbytes, Free Kbytes, Free Swap Kbytes, HighFree, HighTotal, Low Total, Low Free, Page Faults Per Sec, Page Major Faults Per Sec, Pages, Pages Input, Pages Input Per Sec, Pages Output, Pages Output Per Sec, SlabCache, SwapCached, Shared Kbytes, Total Kbytes, Total Swap Kbytes, Total VM Kbytes, Used Kbytes, Used Swap Kbytes, Used VM Kbytes
Network Interface Object	Rx Bytes, Rx Packets, Rx Errors, Rx Dropped, Rx Multicast, Tx Bytes, Tx Packets, Tx Error, Tx Dropped, Total Bytes, Total Packets, Tx QueueLen
Processor Object	Irq %, Softirq %, IOwait %, User %, Nice %, System %, Idle %, % CPU Time

PerfMon perfmonAddCounter

The perfmonAddCounter operation adds an array of counters to a session handle.

To retrieve a list of possible counters for an object, use perfmonListCounter.

To retrieve a list of possible instances for an object, use perfmonListInstance.

To construct a counter name use the following format:
\\cucm hostname\object\counter.

Some objects have instances. If the value of MultiInstance returned by perfmonListCounter is true, then the object has instances. To construct a counter name with an instance use the following format:

\\cucm hostname\object(instance)\counter.

perfmonAddCounter Request Format

<!--PerfMon API - perfmonAddCounter - Request-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.cisco.com/ast/soap">
   <soapenv:Header/>
   <soapenv:Body>
      <soap:perfmonAddCounter>
         <soap:SessionHandle>9830a5d4-48b1-11e4-8000-000c29ff920f</soap:SessionHandle>
         <soap:ArrayOfCounter>
            <soap:Counter>
               <soap:Name>\\cucm3\Cisco CallManager\CallsActive</soap:Name>
            </soap:Counter>
         </soap:ArrayOfCounter>
      </soap:perfmonAddCounter>
   </soapenv:Body>
</soapenv:Envelope>

The perfmonAddCounter operation takes the following parameters:

Parameter	Description
SessionHandle	A unique session ID from the client, of type `SessionHandleType`. The session handle that the `perfmonOpenSession` request previously opened.
ArrayOfCounter	An array of at least one `Counter` element, of the type `ArrayOfCounterType`, containing the name of a `Counter` to be added to the session handle.

perfmonAddCounter Response Format

<!--PerfMon API - perfmonAddCounter - Response-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <ns1:perfmonAddCounterResponse xmlns:ns1="http://schemas.cisco.com/ast/soap"/>
   </soapenv:Body>
</soapenv:Envelope>

perfmonAddCounter returns a single response on success. If perfmonAddCounter fails to add one or more requested counters, a fault response is triggered. Some requested counters may get added successfully while others fail to be added. The Params element of the CallInfo element reports each failed counter name. Client programs can conclude counter names not listed in the fault message were added to the session handle successfully.

PerfMon perfmonCloseSession

The perfmonCloseSession operation closes the session handle that perfmonOpenSession previously opened.

perfmonCloseSession Request

<!--PerfMon API - perfmonCloseSession - Request-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.cisco.com/ast/soap">
   <soapenv:Header/>
   <soapenv:Body>
      <soap:perfmonCloseSession>
         <soap:SessionHandle>9830a5d4-48b1-11e4-8000-000c29ff920f</soap:SessionHandle>
      </soap:perfmonCloseSession>
   </soapenv:Body>
</soapenv:Envelope>

Parameter	Description
SessionHandle	A unique session ID from the client, of type `SessionHandleType`. The session handle that the `perfmonOpenSession` request previously opened.

If the same request is repeated, the session is already closed and does not exist.

perfmonCloseSession Response

<!--PerfMon API - perfmonCloseSession - Response-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <ns1:perfmonCloseSessionResponse xmlns:ns1="http://schemas.cisco.com/ast/soap"/>
   </soapenv:Body>
</soapenv:Envelope>

The perfmonCloseSession operation does not return data in the response.

PerfMon perfmonCollectCounterData

The perfmonCollectCounterData operation returns the perfmon data for all counters that belong to an object on a particular host. Unlike the session-based perfmon data collection, this operation collects all data in a single request and response transaction. For an object with multiple instances, data for all instances is returned.

perfmonCollectCounterData Request Format

<!--Perfmon API - perfmonCollectCounterData - Request-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.cisco.com/ast/soap">
   <soapenv:Header/>
   <soapenv:Body>
      <soap:perfmonCollectCounterData>
         <soap:Host>cucm3</soap:Host>
         <soap:Object>Cisco CallManager</soap:Object>
      </soap:perfmonCollectCounterData>
   </soapenv:Body>
</soapenv:Envelope>

Parameter	Description
Host	The host name or IP address of the target server from which the client wants to retrieve the counter information.
Object	The name of the perfmon object.

perfmonCollectCounterData Response Format

<!--PerfMon API - perfmonCollectCounterData - Response-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <ns1:perfmonCollectCounterDataResponse xmlns:ns1="http://schemas.cisco.com/ast/soap">
         <ns1:perfmonCollectCounterDataReturn>
            <ns1:Name>\\cucm3\Cisco CallManager\AnnunciatorOutOfResources</ns1:Name>
            <ns1:Value>0</ns1:Value>
            <ns1:CStatus>1</ns1:CStatus>
         </ns1:perfmonCollectCounterDataReturn>
         <ns1:perfmonCollectCounterDataReturn>
            <ns1:Name>\\cucm3\Cisco CallManager\AnnunciatorResourceActive</ns1:Name>
            <ns1:Value>0</ns1:Value>
            <ns1:CStatus>1</ns1:CStatus>
         </ns1:perfmonCollectCounterDataReturn>
         <ns1:perfmonCollectCounterDataReturn>
            <ns1:Name>\\cucm3\Cisco CallManager\AnnunciatorResourceAvailable</ns1:Name>
            <ns1:Value>48</ns1:Value>
            <ns1:CStatus>1</ns1:CStatus>
         </ns1:perfmonCollectCounterDataReturn>
         <ns1:perfmonCollectCounterDataReturn>
            <ns1:Name>\\cucm3\Cisco CallManager\AnnunciatorResourceTotal</ns1:Name>
            <ns1:Value>48</ns1:Value>
            <ns1:CStatus>1</ns1:CStatus>
         </ns1:perfmonCollectCounterDataReturn>

                 ...

         <ns1:perfmonCollectCounterDataReturn>
            <ns1:Name>\\cucm3\Cisco CallManager\VideoOnHoldResourceActive</ns1:Name>
            <ns1:Value>0</ns1:Value>
            <ns1:CStatus>1</ns1:CStatus>
         </ns1:perfmonCollectCounterDataReturn>
         <ns1:perfmonCollectCounterDataReturn>
            <ns1:Name>\\cucm3\Cisco CallManager\VideoOutOfResources</ns1:Name>
            <ns1:Value>0</ns1:Value>
            <ns1:CStatus>1</ns1:CStatus>
         </ns1:perfmonCollectCounterDataReturn>
      </ns1:perfmonCollectCounterDataResponse>
   </soapenv:Body>
</soapenv:Envelope>

The perfmonCollectCounterData operation returns an ArrayOfCounterInfo element, which is an array of CounterInfo elements. CounterInfoType is a structure with the following three element members.

Parameter	Description
Name	The name of the counter that was previously added to the session handle, of type `CounterNameType`, derived from `xsd:string`
Value	The value of the counter, of type `signed 64-bit integer`, `xsd:long`
CStatus	Indicates whether the value of the counter was successfully retrieved, of type `32-bit unsigned integer`, `xsd:unsignedInt`

Check CStatus before reading the Value element. If the CStatus response equals 0 or 1, the Value element contains a good counter value. Otherwise, a failure occurred in retrieving the counter value and the Value element is ignored. It is recommended to close the session and create a new session if CStatus has a value other than 0 or 1.

PerfMon perfmonCollectSessionData

The perfmonCollectSessionData operation collects the PerfMon data for all counters that have been added with perfmonAddCounter to the session handle returned from perfmonOpenSession.

perfmonCollectSessionData Request Format

<!--PerfMon API - perfmonCollectSessionData - Request-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.cisco.com/ast/soap">
   <soapenv:Header/>
   <soapenv:Body>
      <soap:perfmonCollectSessionData>
         <soap:SessionHandle>9830a5d4-48b1-11e4-8000-000c29ff920f</soap:SessionHandle>
      </soap:perfmonCollectSessionData>
   </soapenv:Body>
</soapenv:Envelope>

The perfmonCollectSessionData operation requires the SessionHandle containing the session handle that the perfmonOpenSession operation opened previously.

Parameter	Description
SessionHandle	A unique session ID from the client, of type `SessionHandleType`. The session handle that the `perfmonOpenSession` request previously opened.

perfmonCollectSessionData Response Format

<!--PerfMon API - perfmonCollectSessionData - Response-->
<!--Use perfmonOpenSession and perfmonAddCounter prior to this request-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <ns1:perfmonCollectSessionDataResponse xmlns:ns1="http://schemas.cisco.com/ast/soap">
         <ns1:perfmonCollectSessionDataReturn>
            <ns1:Name>\\cucm3\Cisco CallManager\CallsActive</ns1:Name>
            <ns1:Value>1</ns1:Value>
            <ns1:CStatus>0</ns1:CStatus>
         </ns1:perfmonCollectSessionDataReturn>
      </ns1:perfmonCollectSessionDataResponse>
   </soapenv:Body>
</soapenv:Envelope>

The perfmonCollectSessionData operation returns the ArrayOfCounterInfo element that contains the value and status of all counters that were previously added to the session handle. The type for ArrayOfCounterInfo element is ArrayOfCounterInfoType, and is an array of CounterInfo elements. CounterInfo element is of the type CounterInfoType which is a structure with the following three element members.

Parameter	Description
Name	The name of the counter previously added to the session handle, of type `CounterNameType`, derived from `xsd:string`.
Value	The value of the counter, of type `signed 64-bit integer`, `xsd:long`.
CStatus	Indicates whether the value of the counter was successfully retrieved, of type `32-bit unsigned integer`, `xsd:unsignedInt`.

PerfMon perfmonListCounter

The perfmonListCounter operation returns the list of available PerfMon objects and counters on a particular host.

perfmonListCounter Request Format

<!--PerfMon API - perfmonListCounter - Request-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.cisco.com/ast/soap">
   <soapenv:Header/>
   <soapenv:Body>
      <soap:perfmonListCounter>
         <soap:Host>cucm3</soap:Host>
      </soap:perfmonListCounter>
   </soapenv:Body>
</soapenv:Envelope>

The perfmonListCounter request takes the Cisco Unified CM server host name as its only parameter.

Parameter	Description
Host	Cisco Unified CM server host name from which to retrieve the counter information, of type `xsd:string`.

perfmonListCounter Response Format

<!--PerfMon API - perfmonListCounter - Response-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <ns1:perfmonListCounterResponse xmlns:ns1="http://schemas.cisco.com/ast/soap">
         <ns1:perfmonListCounterReturn>
            <ns1:Name>Cisco CAR DB</ns1:Name>
            <ns1:MultiInstance>true</ns1:MultiInstance>
            <ns1:ArrayOfCounter>
               <ns1:item>
                  <ns1:Name>CARDBSpaceUsed</ns1:Name>
               </ns1:item>
               <ns1:item>
                  <ns1:Name>CARTempDBSpaceUsed</ns1:Name>
               </ns1:item>
               <ns1:item>
                  <ns1:Name>FreeSharedMemory</ns1:Name>
               </ns1:item>
               <ns1:item>
                  <ns1:Name>RootDBSpaceUsed</ns1:Name>
               </ns1:item>
               <ns1:item>
                  <ns1:Name>UsedSharedMemory</ns1:Name>
               </ns1:item>
            </ns1:ArrayOfCounter>
         </ns1:perfmonListCounterReturn>
            ...

         <ns1:perfmonListCounterReturn>
            <ns1:Name>SAML SSO</ns1:Name>
            <ns1:MultiInstance>false</ns1:MultiInstance>
            <ns1:ArrayOfCounter>
               <ns1:item>
                  <ns1:Name>OAuthTokensActive</ns1:Name>
               </ns1:item>
               <ns1:item>
                  <ns1:Name>OAuthTokensExpired</ns1:Name>
               </ns1:item>
               <ns1:item>
                  <ns1:Name>OAuthTokensIssued</ns1:Name>
               </ns1:item>
               <ns1:item>
                  <ns1:Name>OAuthTokensRevoked</ns1:Name>
               </ns1:item>
               <ns1:item>
                  <ns1:Name>OAuthTokensValidated</ns1:Name>
               </ns1:item>
               <ns1:item>
                  <ns1:Name>SAMLRequests</ns1:Name>
               </ns1:item>
               <ns1:item>
                  <ns1:Name>SAMLResponses</ns1:Name>
               </ns1:item>
            </ns1:ArrayOfCounter>
         </ns1:perfmonListCounterReturn>
      </ns1:perfmonListCounterResponse>
   </soapenv:Body>
</soapenv:Envelope>

The perfmonListCounter operation returns information that describes the hierarchical structure of PerfMon objects and counters. The body entry includes an ArrayOfObjectInfo element.

The ArrayOfObjectInfo element is an array of ObjectInfo elements of the ObjectInfoType with the following elements:

Parameter	Description
Name	Name of the object.
MultiInstance	`true` of `false` indicates whether the object has more than one instance.
ArrayOfCounter	An array of `Counter` elements.

PerfMon perfmonListInstance

The perfmonListInstance operation returns a list of instances of a PerfMon object on a particular host. Instances of an object can dynamically change. This operation returns the most recent list.

perfmonListInstance Request Format

<!--PerfMon API - perfmonListInstance - Request-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.cisco.com/ast/soap">
   <soapenv:Header/>
   <soapenv:Body>
      <soap:perfmonListInstance>
         <soap:Host>cucm3</soap:Host>
         <soap:Object>Partition</soap:Object>
      </soap:perfmonListInstance>
   </soapenv:Body>
</soapenv:Envelope>

Parameter	Description
Host	The host name of the target server where the object resides.
Object	The name of the object.

perfmonListInstance Response Format

<!--PerfMon API - perfmonListInstance - Response-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <ns1:perfmonListInstanceResponse xmlns:ns1="http://schemas.cisco.com/ast/soap">
         <ns1:perfmonListInstanceReturn>
            <ns1:Name>Active</ns1:Name>
         </ns1:perfmonListInstanceReturn>
         <ns1:perfmonListInstanceReturn>
            <ns1:Name>Common</ns1:Name>
         </ns1:perfmonListInstanceReturn>
         <ns1:perfmonListInstanceReturn>
            <ns1:Name>Boot</ns1:Name>
         </ns1:perfmonListInstanceReturn>
         <ns1:perfmonListInstanceReturn>
            <ns1:Name>Inactive</ns1:Name>
         </ns1:perfmonListInstanceReturn>
         <ns1:perfmonListInstanceReturn>
            <ns1:Name>SharedMemory</ns1:Name>
         </ns1:perfmonListInstanceReturn>
         <ns1:perfmonListInstanceReturn>
            <ns1:Name>Swap</ns1:Name>
         </ns1:perfmonListInstanceReturn>
      </ns1:perfmonListInstanceResponse>
   </soapenv:Body>
</soapenv:Envelope>

The perfmonListInstance returns an element named ArrayOfInstance. Its type is ArrayOfInstanceType, which is an array of instance elements.

Parameter	Description
Name	The name of the instance of the requested object.

Note: ArrayOfInstanceType can have zero instance elements, in which case the requested object is not a multi-instance object.

PerfMon perfmonOpenSession

Client programs use the perfmonOpenSession request to obtain a session handle. The client needs a session handle to do session-based PerfMon counter data collection.

Refer to Session Based Performance Montioring for information on a scenario of related operations.

perfmonOpenSession Request Format

<!--PerfMon API - perfmonOpenSession - Request-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.cisco.com/ast/soap">
   <soapenv:Header/>
   <soapenv:Body>
      <soap:perfmonOpenSession/>
   </soapenv:Body>
</soapenv:Envelope>

The perfmonOpenSession operation takes no parameter.

perfmonOpenSession Response Format

<!--PerfMon API - perfmonOpenSession - Response-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <ns1:perfmonOpenSessionResponse xmlns:ns1="http://schemas.cisco.com/ast/soap">
         <ns1:perfmonOpenSessionReturn>9830a5d4-48b1-11e4-8000-000c29ff920f</ns1:perfmonOpenSessionReturn>
      </ns1:perfmonOpenSessionResponse>
   </soapenv:Body>
</soapenv:Envelope>

Parameter	Description
SessionHandle	A unique session ID from the client, of type `SessionHandleType`. The session handle that the `perfmonOpenSession` request previously opened.

PerfMon perfmonQueryCounterDescription

perfmonQueryCounterDescription returns the detailed, human-readable description of the requested counter.

Refer to perfmonAddCounter for information on creating a counter name.

perfmonQueryCounterDescription Request Format

<!--PerfMon API - perfmonQueryCounterDescription - Request-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.cisco.com/ast/soap">
   <soapenv:Header/>
   <soapenv:Body>
      <soap:perfmonQueryCounterDescription>
         <soap:Counter>\\cucm3\Cisco CallManager\CallsActive</soap:Counter>
      </soap:perfmonQueryCounterDescription>
   </soapenv:Body>
</soapenv:Envelope>

Parameter	Description
Counter	The name of the counter, of type `CounterNameType`.

perfmonQueryCounterDescription Response Format

<!--PerfMon API - perfmonQueryCounterDescription - Response-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <ns1:perfmonQueryCounterDescriptionResponse xmlns:ns1="http://schemas.cisco.com/ast/soap">
         <ns1:perfmonQueryCounterDescriptionReturn>This represents the number of voice or video streaming connections that are currently in use (active). In other words, the number of calls that actually have a voice path connected on this CallManager.</ns1:perfmonQueryCounterDescriptionReturn>
      </ns1:perfmonQueryCounterDescriptionResponse>
   </soapenv:Body>
</soapenv:Envelope>

Parameter	Description
perfmonQueryCounterDescriptionReturn	The detailed, human-readable description of the requested counter.

PerfMon perfmonRemoveCounter

The perfmonRemoveCounter operation removes an array of counters from a session handle.

Refer to perfmonAddCounter for information on creating a counter name.

perfmonRemoveCounter Request

<!--PerfMon API - perfmonRemoveCounter - Request-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.cisco.com/ast/soap">
   <soapenv:Header/>
   <soapenv:Body>
      <soap:perfmonRemoveCounter>
         <soap:SessionHandle>9830a5d4-48b1-11e4-8000-000c29ff920f</soap:SessionHandle>
         <soap:ArrayOfCounter>
            <!--1 or more repetitions:-->
            <soap:Counter>
               <soap:Name>\\cucm3\Cisco CallManager\CallsActive</soap:Name>
            </soap:Counter>
         </soap:ArrayOfCounter>
      </soap:perfmonRemoveCounter>
   </soapenv:Body>
</soapenv:Envelope>

Parameter	Description
SessionHandle	A unique session ID from the client, of type `SessionHandleType`. The session handle that the `perfmonOpenSession` request previously opened.
ArrayOfCounter	An array of `Counter` elements, of type `ArrayOfCounterType`. Each `Counter` element contains the name of a counter to be removed from the session handle.

perfmonRemoveCounter Response

<!--PerfMon API - perfmonRemoveCounter - Response-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <ns1:perfmonRemoveCounterResponse xmlns:ns1="http://schemas.cisco.com/ast/soap"/>
   </soapenv:Body>
</soapenv:Envelope>

The perfmonRemoveCounter operation returns a single response on success. If a perfmonRemoveCounter operation fails to remove one or more of the requested counters, a fault is returned. The Params element of the CallInfo element specifies each failed counter name. Client programs can conclude that counter names that do not appear in the fault message are removed successfully from the query handle.