03-13-2008 01:04 PM - edited 03-13-2019 05:04 PM
I'm new to AXL Serviceability - has anyone made the Perfmon stuff work? I keep getting an error: No Handler found for PerfmonListCounter
I've tried a variety of SOAPAction header values but I still get the error. Besides what's below, I've tried
"http://schemas.cisco.com/ast/soap/action/#PerfmonPort#PerfmonListCounter"
"http://10.10.10.12:8443/perfmonservice/services/#PerfmonPort#PerfmonListCounter"
"http://10.10.10.12:8443/perfmonservice/services/PerfmonPort"
The request looks like this:
POST /axl/ HTTP/1.0
Host:10.10.10.11:80
Authorization: Basic ZGV2Y2VydDpzaWx2ZXJiYWNr
Accept: text/*
Content-type: text/xml
SOAPAction: "CUCM:DB ver=6.0"
Content-length: 496
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <q1:PerfmonListCounter xmlns:q1="http://schemas.cisco.com/ast/soap/"><Host xsi:type="xsd:string">10.10.10.12</Host></q1:PerfmonListCounter></SOAP-ENV:Body> </SOAP-ENV:Envelope>
03-14-2008 06:47 AM
Hi,
To get handler you need to execute PerfmonOpenSession. Then you can add counter using PerfmonAddCounter.
--
regards,
PK
03-14-2008 06:58 AM
Thanks, I will try that. One quick question is that the documentation claims you can use either single transaction or session-based collection (page 2-9 in AXL Serviceability API Dev Guide). I was attempting single transaction. Is the documentation not correct, and single-transaction method is not available ?
03-14-2008 08:15 AM
You wanted to do PerfmonListCounter, but no counters was declared. So, ccm cannot list them.
--
regards,
PK
03-14-2008 09:31 AM
The docs say PerfmonListcounter soap operation returns a list of all objects, and only takes Host as a parameter. Supposedly you can use it to list everything available, but not to select a certain counter. This is from 6.0(1) CUCM Developers Guide.
Have you used other PerfmonPort operations successfully? I value your feedback on PerfmonPort.
03-14-2008 06:59 AM
was a duplicate
03-19-2008 09:05 PM
I found the problem. In this case instead of using /axl/ as the request-uri, (/axl/ is the AXLAPI.wsdl service def), use
https://10.10.10.12:8443/perfmonservice/services/PerfmonPort, which is the RisPort.wsdl service def.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: