PCP Auto Provsioning Stopped Working

[egordon25]

I am using Prime Collaboration Provisioning (PCP) version 11.0.  I have setup 11 domains,  each representing a site.  They are all built very similar using almost all of the same settings.  I have turned up and provisioned three sites. On the fourth site almost all of the users were provisioned but it stopped provisioning. I didn't notice at first because after it started I left it and let PCP do its work. It wasn't until I tried to provision the fifth site where I noticed that it would not provision any more users and that it did not provision some of the users from the fourth site.  It brought the users in from LDAP just fine but would not auto-provision them, as if there was a limit on the amount of users the server would auto-provision. I was able to manually provision a user. When I click on one of the users, it states that auto-provisioning is scheduled but nothing is happening. 

Does anyone know if there is a setting or something that would limit auto-provisioning or cause it to stop without giving any errors?

[dilip_g]

Hello,

there is actually no restriction on the number of users who can use Auto Service Provisioning.

Which OVA are you using and how much users are we talking about here ?

Have you already purchased PCP ? If yes, I recommed you raise a TAC case. You can also send an email to ask-primecollab@cisco.com with some screenshots and log messages so that we can understand what is exactly happening.

thanks

dilip

Technical Marketing, Cisco Prime Collaboration.

[egordon25]

Hello Digangad,

The OVA is cpc-provisioning-11.0.0-815-small.ova.

The amount of users total are about 750 for all 11 sites (domains). The amount of users for these specific sites that I started having trouble with are: fourth site: about 73 (auto-provisioned all but the last 8). Site five: about 57 users.

We have purchased PCP and I am running a TAC case on it. Was hoping this was something simple that someone has already come across.

Thanks,

Eric

[egordon25]

After running a TAC case, the auto-provisioning service was simply froze. TAC agent ran some commands in the CLI to restart services.

-logged in as root and used the commands below. 

-after services were restarted we had to delete the users in the domain.

-After the users were deleted we had to run an LDAP sync to bring the users back into the domain and auto-provisioning started as normal.

[root@cpcp ~]# cd /opt/cupm/bin
[root@cpcp bin]# /cpcmcontrol.sh status
-bash: /cpcmcontrol.sh: No such file or directory
[root@cpcp bin]# ./cpcmcontrol.sh status
httpd denotes httpd service.
nice.sh denotes Nice service.
startcupm.sh denotes Jboss service.
postmaster/su denotes Postgres service.

STAT PID USER COMMAND ELAPSED
===============================================
Ss 4128 root httpd 20-02:29:59
S 4105 root nice.sh 20-02:29:59
S 4076 root startcupm.sh 20-02:29:59
S 4072 root su 20-02:29:59
[root@cpcp bin]# ./cpcmcontrol.sh stop
Cisco Prime Collaboration Provisioning stop initiated....
^[[A]
[root@cpcp bin]# ./cpcmcontrol.sh stop
Cisco Prime Collaboration Provisioning stop initiated....
Please wait for a minute to allow the services to stop completely.
[root@cpcp bin]# ./cpcmcontrol.sh start
Cisco Prime Collaboration Provisioning start initiated...
Please run show application status cpcm to check status of start operation.
[root@cpcp bin]# ./cpcmcontrol.sh status
httpd denotes httpd service.
nice.sh denotes Nice service.
startcupm.sh denotes Jboss service.
postmaster/su denotes Postgres service.

STAT PID USER COMMAND ELAPSED
===============================================
Ss 1328 root httpd 02:32
S 1308 root nice.sh 02:32
S 1279 root startcupm.sh 02:32
S 1275 root su 02:32
[root@cpcp bin]#