What trace is best to see errors regarding PG disconnecting?

Unanswered Question
Jul 6th, 2010

What is a good trace use on ICM to look for specific errors to determine why vendor is saying PG is disconnecting?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Who is the "vendor" in this question?

Are you wanting to trace something on the Central Controller to see why a PG is disconnecting? How many PGs do you have? Is one of them problematic and the others OK?

The ccagent process on the Call Router talks to the pgagent process on the PG using the DMP (Device Management Protocol) over TCP/IP.

On the PG itself, you will easily see CC disconnects in the OPC log without increasing tracing using the following dumplog command (put your own dates in):

dumplog opc /bd 07/04/2010 /ed 07/05/2010 /m "DMP Out-Of-Service"

On the Central Controller, rttest is a useful program to tell you the state of the nation - when the CC last heard from each PG.

http://cisco.biz/en/US/products/sw/custcosw/ps1001/products_tech_note09186a00800ac69b.shtml

Since there is no procmon to increase the trace on ccagent, you should do it in the registry. Normally I use 0xffff (four f's) and see how that goes. Maybe wind it back if there is too much rubbish.

Regards,

Geoff

Actions

This Discussion