I need a little clarity to your question. How many PG processes are running on the server? You can only have 2 PG processes on a single server. You can however have a PG with multiple PIMs. If you are working within those guidelines I would suggest verifying that the ISN servers are properly configured and you can ping the ISN servers from the PG.
I'm pretty sure there is no 2-PG limit on a node. Seems to me I've put more than that on one node in the past.
When I have had this problem of PIM's not even trying to activate, it's usually been because of a mismatch between the Logical Controller ID (LCID) in Setup vs. in the PG Explorer, or the Peripheral ID (PID) in Setup vs. in the PG Explorer. You might check to make sure they each match what they are supposed to match. Also, I believe you'd see errors either in the router log or in the OPC log if this is the case.
There actually is a "hard limitation" on two PG's per box and you have to edit the registry to get more to work. So, if this is lab environment then I would feel fine about making this change. In a production environment, I would highly recommend against this as it will allow you to have more than two PG's, but it still acts a bit flaky. Also, it is supported to have multiple PIM's so unless you are trying to add a PG of a new type, why not make your PG Generic and add multiple PIMs?
I have edited the registry with path HKLM\SOFTWARE\Cisco Systems,Inc\ICM\icm01\PG3A\MDS\Process
where icm01 is the ICM instance
and the keys
MDSPort from 44040 to 44050
StateXferPort from 44041 to 44051
(just changing MDSPort ONLY also causes the shutdown).
Do this for each extra PG that you have. Again, I must stress that this is for lab only.
i was adding this new 3rd PIM on an existing PG on a live sytem so i stopped one sideA added the PIM then started the services on sideA PIM3 was there but didn't activate. then went to SideB installed the new PIM also didn't acitvate.
if you go again to PIM configration you wuld see configuration is gone.
so the only way to make it work it to stop both sides at the same time, add the new PIM then activate and it will work.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...